System and method for managing data with service level agreements that may specify non-uniform copying of data
원문보기
IPC분류정보
국가/구분
United States(US) Patent
등록
국제특허분류(IPC7판)
G06F-007/00
G06F-011/14
G06F-017/30
출원번호
US-0947385
(2010-11-16)
등록번호
US-9858155
(2018-01-02)
발명자
/ 주소
Ashutosh, Ashutosh
Chang, David F.
Mutalik, Madhav
출원인 / 주소
Actifio, Inc.
대리인 / 주소
Wilmer Cutler Pickering Hale and Dorr LLP
인용정보
피인용 횟수 :
0인용 특허 :
86
초록▼
Systems and methods are disclosed for a system for managing data in accordance with service level agreements (SLAs) that specify schedules on a calendar basis for performing prescribed data management functions and for reducing inter-function redundancy. This system may include a data management eng
Systems and methods are disclosed for a system for managing data in accordance with service level agreements (SLAs) that specify schedules on a calendar basis for performing prescribed data management functions and for reducing inter-function redundancy. This system may include a data management engine for performing data management functions, including at least a snapshot function, and at least one back-up function. The data management engine may include a service level policy engine that receives SLAs in electronic form and which controls the scheduling of the data management functions. Each electronic SLA may be associated with a corresponding application and may specify at least one service level policy, each policy specifying a source pool, a destination pool, a copy frequency, a retention period and schedule information. A collection of policies is capable of expressing a non-uniform schedule for when a given function should be performed.
대표청구항▼
1. A system for managing data in accordance with a multiple policy service level agreement that comprises multiple service level policies that specify non-uniform schedules on a calendar basis for performing prescribed data management functions, said system comprising: a memory containing instructio
1. A system for managing data in accordance with a multiple policy service level agreement that comprises multiple service level policies that specify non-uniform schedules on a calendar basis for performing prescribed data management functions, said system comprising: a memory containing instructions for execution by the processor;a storage system for providing a data object; anda processor configured to initiate a plurality of data management functions based on a multiple policy service level agreement associated with the data object, wherein the processor is configured to: receive the multiple policy service level agreement, wherein the multiple policy service level agreement comprises a plurality of service level policies for the data object, the plurality of service level policies comprising: a first service level policy specifying a first data management schedule for a first data management function, comprising (i) a first destination pool for storing a first copy of the data object, (ii) a first copy frequency indicating the frequency of operation for the first service level policy, and (iii) a first retention period indicating how long a given copy for the first service level policy should be retained in the first destination pool before being allowed to expire;a second service level policy specifying a second data management schedule for the second data management function, comprising (i) a second destination pool for storing a second copy of the data object, (ii) a second copy frequency indicating the frequency of operation for the second service level policy, and (iii) a second retention period indicating how long a given copy for the second service level policy should be retained in the second destination pool before being allowed to expire; anda third service level policy specifying a third data management schedule for the second data management function, comprising (i) the second destination pool for storing a third copy of the data object, (ii) a third copy frequency indicating the frequency of operation for the third service level policy, wherein the third copy frequency is different than the second copy frequency, and (iii) a third retention period indicating how long a given copy for the third service level policy should be retained in the second destination pool before being allowed to expire,wherein: the different second and third copy frequencies define a non-uniform copy schedule for the second data management function; andthe first, second and third retention periods define different retention periods for copies generated by the first and second data management functions;determine when at least two of the first, second and third copy frequencies cause the first and second data management functions to be performed at a same time;in response to the determination, perform preparatory operations to satisfy the multiple policy service level agreement comprising generating a coherent image of data to be copied to the first destination pool, the second destination pool, or both, and wherein said preparatory operations are performed once, thereby avoiding redundant preparatory operations for the first and second data management functions; andschedule the first and second data management functions according to the first, second and third data management schedules to satisfy the requirements of the multiple policy service level agreement, including satisfying (a) the non-uniform schedule for the second data management function and (b) the multiple retention periods for the first and second data management functions. 2. The system of claim 1, wherein if two or more copy operations are scheduled to occur at the same instant between a source pool and the destination pool, only one of the two or more copy operations is performed, and that copy is associated with the longest retention period corresponding to the two or more scheduled copy operations. 3. The system of claim 1, wherein preparatory operations include collecting metadata about an application that uses the data object to store in conjunction with application data. 4. The system of claim 1, wherein preparatory operations include application quiescing operations. 5. The system of claim 4, wherein the application quiescing operations include freezing the application from further updating application data. 6. The system of claim 4, wherein the application quiescing operations include flushing the I/O cache of the application server of application data. 7. The system of claim 1, wherein scheduling the first and second data management functions according to the first, second and third data management schedules comprises performing a scheduled copy operation in order based on one of a longest retention period and a shortest copy frequency. 8. The system of claim 1, wherein: the first data management function is a snapshot function and the second data management function is a back-up function;the first destination pool is a snapshot pool for storing a snapshot copy of the data in the storage system; andthe second destination pool is a long-term archive storage pool for storing an archive copy of the data in the storage system. 9. A method for managing data in accordance with a multiple policy service level agreement that comprises multiple service level policies that specify non-uniform schedules on a calendar basis for performing prescribed data management functions, said method being executed by a processor configured to execute instructions stored in a memory that cause the processor to initiate a plurality of data management functions based on the multiple policy service level agreement associated with a data object, wherein the processor is configured to: receive the multiple policy service level agreement, wherein the multiple policy service level agreement comprises a plurality of service level policies for the data object, the plurality of service level policies comprising: a first service level policy specifying a first data management schedule for a first data management function, comprising (i) a first destination pool for storing a first copy of the data object, (ii) a first copy frequency indicating the frequency of operation for the first service level policy, and (iii) a first retention period indicating how long a given copy for the first service level policy should be retained in the first destination pool before being allowed to expire;a second service level policy specifying a second data management schedule for the second data management function, comprising (i) a second destination pool for storing a second copy of the data object, (ii) a second copy frequency indicating the frequency of operation for the second service level policy, and (iii) a second retention period indicating how long a given copy for the second service level policy should be retained in the second destination pool before being allowed to expire; anda third service level policy specifying a third data management schedule for the second data management function, comprising (i) the second destination pool for storing a third copy of the data object, (ii) a third copy frequency indicating the frequency of operation for the third service level policy, wherein the third copy frequency is different than the second copy frequency, and (iii) a third retention period indicating how long a given copy for the third service level policy should be retained in the second destination pool before being allowed to expire,wherein: the different second and third copy frequencies define a non-uniform copy schedule for the second data management function; andthe first, second and third retention periods define different retention periods for copies generated by the first and second data management functions;determine when at least two of the first, second and third copy frequencies cause the first and second data management functions to be performed at a same time;in response to the determination, perform preparatory operations to satisfy the multiple policy service level agreement comprising generating a coherent image of data to be copied to the first destination pool, the second destination pool, or both, and wherein said preparatory operations are performed once, thereby avoiding redundant preparatory operations for the first and second data management functions; andschedule the first and second data management functions according to the first, second and third data management schedules to satisfy the requirements of the multiple policy service level agreement, including satisfying (a) the non-uniform schedule for the second data management function and (b) the multiple retention periods for the first and second data management functions. 10. A non-transitory computer readable medium having executable instructions operable to cause an apparatus to: receive a multiple policy service level agreement, wherein the multiple policy service level agreement comprises a plurality of service level policies for a data object, the plurality of service level policies comprising: a first service level policy specifying a first data management schedule for a first data management function, comprising (i) a first destination pool for storing a first copy of the data object, (ii) a first copy frequency indicating the frequency of operation for the first service level policy, and (iii) a first retention period indicating how long a given copy for the first service level policy should be retained in the first destination pool before being allowed to expire;a second service level policy specifying a second data management schedule for the second data management function, comprising (i) a second destination pool for storing a second copy of the data object, (ii) a second copy frequency indicating the frequency of operation for the second service level policy, and (iii) a second retention period indicating how long a given copy for the second service level policy should be retained in the second destination pool before being allowed to expire; anda third service level policy specifying a third data management schedule for the second data management function, comprising (i) the second destination pool for storing a third copy of the data object, (ii) a third copy frequency indicating the frequency of operation for the third service level policy, wherein the third copy frequency is different than the second copy frequency, and (iii) a third retention period indicating how long a given copy for the third service level policy should be retained in the second destination pool before being allowed to expire,wherein: the different second and third copy frequencies define a non-uniform copy schedule for the second data management function; andthe first, second and third retention periods define different retention periods for copies generated by the first and second data management functions;determine when at least two of the first, second and third copy frequencies cause the first and second data management functions to be performed at a same time;in response to the determination, perform preparatory operations to satisfy the multiple policy service level agreement comprising generating a coherent image of data to be copied to the first destination pool, the second destination pool, or both, and wherein said preparatory operations are performed once, thereby avoiding redundant preparatory operations for the first and second data management functions; andschedule the first and second data management functions according to the first, second and third data management schedules to satisfy the requirements of the multiple policy service level agreement, including satisfying (a) the non-uniform schedule for the second data management function and (b) the multiple retention periods for the first and second data management functions. 11. The method of claim 9, wherein if two or more copy operations are scheduled to occur at the same instant between a source pool and the destination pool, only one of the two or more copy operations is performed, and that copy is associated with the longest retention period corresponding to the two or more scheduled copy operations. 12. The method of claim 9, wherein preparatory operations include collecting metadata about an application that uses the data object to store in conjunction with application data. 13. The method of claim 9, wherein preparatory operations include application quiescing operations. 14. The method of claim 9, wherein the application quiescing operations include freezing the application from further updating application data. 15. The method of claim 9, wherein the application quiescing operations include flushing the I/O cache of the application server of application data. 16. The method of claim 9, wherein scheduling the first and second data management functions according to the first, second and third data management schedules comprises performing a scheduled copy operation in order based on one of a longest retention period and a shortest copy frequency. 17. The method of claim 9, wherein: the first data management function is a snapshot function and the second data management function is a back-up function;the first destination pool is a snapshot pool for storing a snapshot copy of the data; andthe second destination pool is a long-term archive storage pool for storing an archive copy of the data. 18. The non-transitory computer readable medium of claim 10, wherein if two or more copy operations are scheduled to occur at the same instant between a source pool and the destination pool, only one of the two or more copy operations is performed, and that copy is associated with the longest retention period corresponding to the two or more scheduled copy operations. 19. The non-transitory computer readable medium of claim 10, wherein scheduling the first and second data management functions according to the first, second and third data management schedules comprises performing a scheduled copy operation in order based on one of a longest retention period and a shortest copy frequency. 20. The non-transitory computer readable medium of claim 10, wherein: the first data management function is a snapshot function and the second data management function is a back-up function;the first destination pool is a snapshot pool for storing a snapshot copy of the data; andthe second destination pool is a long-term archive storage pool for storing an archive copy of the data.
연구과제 타임라인
LOADING...
LOADING...
LOADING...
LOADING...
LOADING...
이 특허에 인용된 특허 (86)
Clifton Richard J. ; Chatterjee Sanjoy ; Larson John P. ; Richart Joseph R. ; Sagan Cyril E., Apparatus and method for backup of a disk storage system.
Yuval Ofek ; Zoran Cakeljic ; Samuel Krikler IL; Sharon Galtzur IL; Michael Hirsch IL; Dan Arnon ; Peter Kamvysselis, Apparatus and methods for copying, backing up, and restoring data using a backup segment size larger than the storage block size.
Farber David A. ; Lachman Ronald D., Data processing system using substantially unique identifiers to identify data items, whereby identical data items hav.
Belsan Jay S. (Nederland CO) Milligan Charles A. (Golden CO) O\Brien John T. (Louisville CO) Rudeseal George A. (Boulder CO), Data record copy system for a disk drive array data storage subsystem.
Bergant, Milena; Hayden, John M.; Tummala, Himabindu; Pasula Reddy, Santosh; Zhu, Daniel, Data storage server having common replication architecture for multiple storage object types.
Srinivasan, Sudhir; Vahalia, Uresh; Gupta, Uday K.; Armangau, Philippe, Data storage system and method for uninterrupted read-only access to a consistent dataset by one host processor concurrent with read-write access by another host processor.
Aggarwal Vijay K. ; Young Christopher R. ; Shah Himanshu C., Internet and related networks, a method of and system for substitute use of checksum field space in information processing datagram headers for obviating processing speed and addressing space limitat.
St. Pierre Edgar J. ; Gill Alton ; Mutalik Madhav ; Wallace John, Method and apparatus for backing up data before updating the data and for restoring from the backups.
Kuznetzov, Alexey N.; Tormasov, Alexander G.; Korotaev, Kirill S.; Monakhov, Dmitry I., Method and system for fast generation of file system snapshot bitmap in virtual environment.
White Michael Wayne ; Tomsula Patrick James ; Serls David, Method and system for providing additional addressable functional space on a disk for use with a virtual data storage subsystem.
Beardsley Brent C. (Tucson AZ) Micka William F. (Tucson AZ) Novick Yoram (Haifa ILX), Method and system for track transfer control during concurrent copy operations in a data processing storage subsystem.
Blea David Randall ; Blea Donald Reynold ; Haye Mark Alan ; Kern Ronald Maynard ; Shackelford David M. ; Thompson John G., Method for implementing point-in-time copy using a snapshot function.
Hitz David ; Malcolm Michael ; Lau James ; Rakitzis Byron, Method for maintaining consistent states of a file system and for creating user-accessible read-only copies of a file s.
Pence Jerry Wayne, Storage management system and method for increasing capacity utilization of nonvolatile storage devices using partially filled substitute storage devices for continuing write operations.
Beier Harley Al ; Kern Robert Frederic,GBX ; Moore David Wayne ; Ranson Karen Alicia ; Watts Vern Lee, Synchronizing recovery log having time stamp to a remote site for disaster recovery of a primary database having related hierarchial and relational databases.
Provenzano, Christopher A., System and method for creating deduplicated copies of data by sending difference data between near-neighbor temporal states.
Provenzano, Christopher A.; Roman, Mark A., System and method for creating deduplicated copies of data by tracking temporal relationships among copies and by ingesting difference data.
Provenzano, Christopher A.; Roman, Mark A., System and method for creating deduplicated copies of data by tracking temporal relationships among copies using higher-level hash structures.
Provenzano, Christopher A., System and method for creating deduplicated copies of data storing non-lossy encodings of data directly in a content addressable store.
Stager, Roger Keith; Johnston, Craig Anthony, System and method for eliminating duplicate data by generating data fingerprints using adaptive fixed-length windows.
Lubbers, Clark E.; Reiser, James M.; Korgaonkar, Anuja; Roberson, Randy L.; Bean, Robert G., System and method for generating point in time storage copy.
Provenzano, Christopher A., System and method for improved garbage collection operations in a deduplicated store by tracking temporal relationships among copies.
Ashutosh, Ashutosh; Chang, David F.; Mutalik, Madhav, System and method for performing a plurality of prescribed data management functions in a manner that reduces redundant access operations to primary storage.
Abercrombie, Philip J.; Mutalik, Madhav; Provenzano, Christopher A.; Roman, Mark A., System and method for performing backup or restore operations utilizing difference information and timeline state information.
※ AI-Helper는 부적절한 답변을 할 수 있습니다.