Abstract:
Automatic Selection of Storage Volumes in a Data Storage System A method of selecting a target volume in a storage system is provided. The method comprises defining one or more parameters for a plurality of storage volumes in the storage system according to user preference; dynamically collecting information related to the parameters while the storage volumes are used; receiving a request to backup a first source volume in the storage system; and selecting or creating the target volume based on the collected information.

Description:
COPYRIGHT &amp; TRADEMARK NOTICES 
       [0001]    A portion of the disclosure of this patent document contains material, which is subject to copyright protection. The owner has no objection to the facsimile reproduction by any one of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyrights whatsoever. 
         [0002]    Certain marks referenced herein may be common law or registered trademarks of third parties affiliated or unaffiliated with the applicant or the assignee. Use of these marks is for providing an enabling disclosure by way of example and shall not be construed to limit the scope of this invention to material associated with such marks. 
       TECHNICAL FIELD 
       [0003]    The present invention relates generally to data storage systems and, more particularly, to automatic selection of target volumes in a data storage system. 
       BACKGROUND 
       [0004]    Various technologies (e.g., snapshot technology) may be used to backup data in a data storage system. Generally, in response to a request to backup a source volume in the data storage system, a storage controller selects another volume in the data storage system and configures the selected volume to store a backup of the source volume. The selected volume is referred to as a target volume. 
         [0005]    In one existing implementation, a target volume is selected, for example, based on future use patterns predicted by models or statistics (i.e., static information). In other words, the same information is used to select a target volume each time a backup request is received, regardless of user preference or changes in the data storage system. 
         [0006]    In another existing implementation, a target volume is selected, for example, from a set of same or similar capacity storage volumes. Typically, the target volume is selected from among these pre-configured volumes based on how closely the size of the backup data matches the amount of space available on a pre-configured volume. Unfortunately, once the target volume is selected, the selection or the size of the target volume cannot be dynamically configured later to better suit the backup request or the current state of the data storage system. 
         [0007]    Additionally, because the target volume is selected based on the size of the backup data and amount of space available on a pre-configured volume, the resulting configuration may be inefficient with respect to workload performance, power consumption, and other considerations. 
         [0008]    Systems and methods are needed to overcome the above-mentioned shortcomings. 
       SUMMARY 
       [0009]    The present disclosure is directed to systems and corresponding methods that facilitate automatic selection of target volumes in a data storage system. 
         [0010]    For purposes of summarizing, certain aspects, advantages, and novel features have been described herein. It is to be understood that not all such advantages may be achieved in accordance with any one particular embodiment. Thus, the claimed subject matter may be embodied or carried out in a manner that achieves or optimizes one advantage or group of advantages without achieving all advantages as may be taught or suggested herein. 
         [0011]    In accordance with one embodiment, a method of selecting a target volume in a storage system is provided. The method comprises defining one or more parameters for a plurality of storage volumes in the storage system according to user preference; dynamically collecting information related to the parameters while the storage volumes are used; receiving a request to backup a first source volume in the storage system; and selecting or creating the target volume based on the collected information. 
         [0012]    In accordance with another embodiment, a system comprising one or more logic units is provided. The one or more logic units are configured to perform the functions and operations associated with the above-disclosed methods. In accordance with yet another embodiment, a computer program product comprising a computer usable medium having a computer readable program is provided. The computer readable program when executed on a computer causes the computer to perform the functions and operations associated with the above-disclosed methods. 
         [0013]    One or more of the above-disclosed embodiments in addition to certain alternatives are provided in further detail below with reference to the attached figures. The invention is not, however, limited to any particular embodiment disclosed. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0014]    Embodiments of the present invention are understood by referring to the figures in the attached drawings, as provided below. 
           [0015]      FIG. 1  illustrates an exemplary data storage system, in accordance with one or more embodiments. 
           [0016]      FIG. 2  is a flow diagram of a method for selecting a target volume, in accordance with one embodiment. 
           [0017]      FIG. 3  is a flow diagram of a method for selecting a target volume, in accordance with one embodiment. 
           [0018]      FIGS. 4 and 5  are block diagrams of hardware and software environments in which a system of the present invention may operate, in accordance with one or more embodiments. 
       
    
    
       [0019]    Features, elements, and aspects of the invention that are referenced by the same numerals in different figures represent the same, equivalent, or similar features, elements, or aspects, in accordance with one or more embodiments. 
       DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS 
       [0020]    In the following, numerous specific details are set forth to provide a thorough description of various embodiments of the invention. Certain embodiments of the invention may be practiced without these specific details or with some variations in detail. In some instances, certain features are described in less detail so as not to obscure other aspects of the invention. The level of detail associated with each of the elements or features should not be construed to qualify the novelty or importance of one feature over the others. 
         [0021]    Referring to  FIG. 1 , in accordance with one embodiment, an exemplary storage system  100  comprises a storage controller  110  and one or more storage devices  120 . The storage devices  120  comprise one or more source volumes  122  for storing data and one or more target volumes  124  for storing backups of the source volumes  122 . 
         [0022]    Depending on configuration, the source volumes  122  and the target volumes  124  may comprise regular volumes, space efficient (SE) volumes, or a combination thereof. In a regular or fully provisioned volume, space is physically allocated on a one or more of the storage devices  120  when requested. In an SE or thin provisioned volume, space is virtually allocated on a repository volume when requested, and then physically allocated on one or more of the storage devices  120  when actually used. 
         [0023]    Referring to  FIGS. 1 and 2 , in accordance with one embodiment, the storage controller  110  defines one or more parameters according to user preference (P 200 ). The parameters may be defined, for example, to optimize workload performance, storage space, use case, power consumption, etc. In an alternative embodiment, the parameters may be defined according to default settings. 
         [0024]    Once the parameters are defined, the storage controller  110  dynamically collects and saves internal system information related to the parameters for each volume in the storage system  100  (P 210 ). If, for example, the parameters are defined to optimize workload performance, the storage controller  110  may collect information on the input/output (I/O) rate and the read-to-write ratio for each volume in the storage system  100 . 
         [0025]    As another example, if the parameters are defined to optimize space usage, the storage controller  110  may collect information on the space currently allocated, capacity, allocation rate, maximum space usage, and recent use patterns of the storage system  100 . Upon receiving a request to backup a source volume  122  (P 220 ), the storage controller  110  selects or creates a target volume  124  based on the collected information (P 230 ). 
         [0026]    Referring to  FIGS. 1 and 3 , in accordance with one embodiment, the storage controller  110  defines one or more parameters to optimize workload performance, storage space, use case, power consumption, or other objectives or system attributes relevant to the storage system  100  (P 300 ). Once the parameters are defined, the storage controller  110  dynamically collects and saves internal system information related to the parameters for each volume in the storage system  100  (P 310 ). 
         [0027]    Upon receiving a request to backup a source volume  122  (P 320 ), the storage controller  110  determines one or more characteristics of a target volume  124  that is best suited to store a backup of the source volume  122  based on the collected information and given configuration and hardware constraints (P 330 ). 
         [0028]    If the parameters are defined to optimize workload performance and the read-to-write ratio is high, for example, the target volume  124  may be determined to be an SE volume because an SE volume may be best suited to performing read operations. If the parameters are defined to optimize workload performance and the read-to-write ratio is low, for example, the target volume  124  may be determined to be a regular volume because a regular volume may be best suited to performing write operations. 
         [0029]    Once the characteristics of the target volume  124  are determined, the storage controller  110  determines whether a volume with the desired characteristics is available in the storage system  100  (P 340 ). If such a volume is available, the volume is selected as the target volume  124  (P 380 ). 
         [0030]    In some embodiments, if a plurality of volumes are identified that match the desired characteristics, additional volume attributes or characteristics may be considered to select the more suitable volume from among said plurality of volumes. Alternatively, if no volume is identified that satisfies all the desired characteristics, the most suitable volume that matches the highest number of the desired characteristics may be selected as the target volume. 
         [0031]    In certain embodiments, if a suitable volume is not identified, the storage controller  110  determines whether it is possible to modify an available volume to have the characteristics (P 350 ). If such a volume is available, the volume is modified (P 360 ) and selected as the target volume  124  (P 380 ). For example, if the target volume  124  is determined to be at least of a certain size, the storage controller  110  may resize a repository volume to the desired size and select the repository volume as storage pool for the target volume  124 . 
         [0032]    If there is no available volume that has or can be modified to have the characteristics, the storage controller  110 , where possible, creates a volume with the characteristics (P 370 ) and selects the volume as the target volume  124  (P 380 ). Accordingly, the target volume  124  may be thus selected from a pre-configured available volume, a dynamically configured available volume, or a newly created volume in the storage system  100 , as provided above (P 380 ). 
         [0033]    Advantageously, the above systems and methods may be implemented in accordance with one or more embodiments to use dynamic information to automatically select a target volume that is configured to best suit a particular backup request. In different embodiments, the invention may be implemented either entirely in the form of hardware or entirely in the form of software, or a combination of both hardware and software elements. 
         [0034]    For example, storage system  100  may be included in a controlled computing system environment that can be presented largely in terms of hardware components and software code executed to perform processes that achieve the results contemplated by the system of the present invention. 
         [0035]    Referring to  FIGS. 4 and 5 , a computing system environment in accordance with an exemplary embodiment is composed of a hardware environment  1110  and a software environment  1120 . The hardware environment  1110  comprises the machinery and equipment that provide an execution environment for the software; and the software provides the execution instructions for the hardware as provided below. 
         [0036]    As provided here, the software elements that are executed on the illustrated hardware elements are described in terms of specific logical/functional relationships. It should be noted, however, that the respective methods implemented in software may be also implemented in hardware by way of configured and programmed processors, ASICs (application specific integrated circuits), FPGAs (Field Programmable Gate Arrays) and DSPs (digital signal processors), for example. 
         [0037]    Software environment  1120  is divided into two major classes comprising system software  1121  and application software  1122 . System software  1121  comprises control programs, such as the operating system (OS) and information management systems that instruct the hardware how to function and process information. 
         [0038]    In one embodiment, storage controller  110  is implemented as application software  1122  executed on one or more hardware environments to create target volumes based on user preferences. Application software  1122  may comprise but is not limited to program code, data structures, firmware, resident software, microcode or any other form of information or routine that may be read, analyzed or executed by a microcontroller. 
         [0039]    In an alternative embodiment, the invention may be implemented as computer program product accessible from a computer-usable or computer-readable medium providing program code for use by or in connection with a computer or any instruction execution system. For the purposes of this description, a computer-usable or computer-readable medium may be any apparatus that can contain, store, communicate, propagate or transport the program for use by or in connection with the instruction execution system, apparatus or device. 
         [0040]    The computer-readable medium may be an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system (or apparatus or device) or a propagation medium. Examples of a computer-readable medium include a semiconductor or solid-state memory, magnetic tape, a removable computer diskette, a random access memory (RAM), a read-only memory (ROM), a rigid magnetic disk and an optical disk. Current examples of optical disks include compact disk read only memory (CD-ROM), compact disk read/write (CD-R/W) and digital video disk (DVD). 
         [0041]    Referring to  FIG. 4 , an embodiment of the application software  1122  may be implemented as computer software in the form of computer readable code executed on a data processing system such as hardware environment  1110  that comprises a processor  1101  coupled to one or more memory elements by way of a system bus  1100 . The memory elements, for example, may comprise local memory  1102 , storage media  1106  (i.e., storage devices  120 ), and cache memory  1104 . Processor  1101  loads executable code from storage media  1106  to local memory  1102 . Cache memory  1104  provides temporary storage to reduce the number of times code is loaded from storage media  1106  for execution. 
         [0042]    A user interface device  1105  (e.g., keyboard, pointing device, etc.) and a display screen  1107  can be coupled to the computing system either directly or through an intervening I/O controller  1103 , for example. A communication interface unit  1108 , such as a network adapter, may be also coupled to the computing system to enable the data processing system to communicate with other data processing systems or remote printers or storage devices through intervening private or public networks. Wired or wireless modems and Ethernet cards are a few of the exemplary types of network adapters. 
         [0043]    In one or more embodiments, hardware environment  1110  may not include all the above components, or may comprise other components for additional functionality or utility. For example, hardware environment  1110  can be a laptop computer or other portable computing device embodied in an embedded system such as a set-top box, a personal data assistant (PDA), a mobile communication unit (e.g., a wireless phone), or other similar hardware platforms that have information processing and/or data storage and communication capabilities. 
         [0044]    In some embodiments of the system, communication interface  1108  communicates with other systems by sending and receiving electrical, electromagnetic or optical signals that carry digital data streams representing various types of information including program code. The communication may be established by way of a remote network (e.g., the Internet), or alternatively by way of transmission over a carrier wave. 
         [0045]    Referring to  FIG. 5 , application software  1122  may comprise one or more computer programs that are executed on top of system software  1121  after being loaded from storage media  1106  into local memory  1102 . In a client-server architecture, application software  1122  may comprise client software and server software. For example, in one embodiment, client software is executed on a general computing system (not shown) and server software is executed on a server system (not shown). 
         [0046]    Software environment  1120  may also comprise browser software  1126  for accessing data available over local or remote computing networks. Further, software environment  1120  may comprise a user interface  1124  (e.g., a Graphical User Interface (GUI)) for receiving user commands and data. Please note that the hardware and software architectures and environments described above are for purposes of example, and one or more embodiments of the invention may be implemented over any type of system architecture or processing environment. 
         [0047]    It should also be understood that the logic code, programs, modules, processes, methods and the order in which the respective steps of each method are performed are purely exemplary. Depending on implementation, the steps can be performed in any order or in parallel, unless indicated otherwise in the present disclosure. Further, the logic code is not related, or limited to any particular programming language, and may comprise of one or more modules that execute on one or more processors in a distributed, non-distributed or multiprocessing environment. 
         [0048]    The present invention has been described above with reference to one or more features or embodiments. Those skilled in the art will recognize, however, that changes and modifications may be made to these embodiments without departing from the scope of the present invention. These and various other adaptations and combinations of the embodiments disclosed are within the scope of the invention and are further defined by the claims and their full scope of equivalents.