US20120221529A1 - Virtual machine data replication - Google Patents
Virtual machine data replication Download PDFInfo
- Publication number
- US20120221529A1 US20120221529A1 US13/414,119 US201213414119A US2012221529A1 US 20120221529 A1 US20120221529 A1 US 20120221529A1 US 201213414119 A US201213414119 A US 201213414119A US 2012221529 A1 US2012221529 A1 US 2012221529A1
- Authority
- US
- United States
- Prior art keywords
- backup
- data block
- file
- virtual machine
- data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
- 230000010076 replication Effects 0.000 title abstract description 15
- 238000000034 method Methods 0.000 claims abstract description 48
- 230000004044 response Effects 0.000 claims description 8
- 238000011156 evaluation Methods 0.000 claims description 6
- 230000003247 decreasing effect Effects 0.000 abstract 1
- 230000006870 function Effects 0.000 description 11
- 238000012545 processing Methods 0.000 description 11
- 238000010586 diagram Methods 0.000 description 10
- 230000008569 process Effects 0.000 description 8
- 238000004590 computer program Methods 0.000 description 7
- 238000004891 communication Methods 0.000 description 3
- 238000013144 data compression Methods 0.000 description 3
- 239000007787 solid Substances 0.000 description 3
- 230000008901 benefit Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 2
- 238000007906 compression Methods 0.000 description 2
- 230000006835 compression Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000013468 resource allocation Methods 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 238000010276 construction Methods 0.000 description 1
- 238000007796 conventional method Methods 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000013524 data verification Methods 0.000 description 1
- 230000006837 decompression Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 230000000737 periodic effect Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000011664 signaling Effects 0.000 description 1
- 210000003813 thumb Anatomy 0.000 description 1
- 238000010200 validation analysis Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
- G06F11/1469—Backup restoration techniques
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1415—Saving, restoring, recovering or retrying at system level
- G06F11/1438—Restarting or rejuvenating
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1479—Generic software techniques for error detection or fault masking
- G06F11/1482—Generic software techniques for error detection or fault masking by means of middleware or OS functionality
- G06F11/1484—Generic software techniques for error detection or fault masking by means of middleware or OS functionality involving virtual machines
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
Definitions
- the present disclosure relates to computer data backup, and in particular, to a system and method for performing block-level backups of virtual machine, wherein backed up data is stored in de-duplicated form in a hierarchical directory structure.
- data backup is a critical component of computer-based systems.
- the term “backup” may refer to the act of creating copies of data, and may refer to the actual backed-up copy of the original data.
- the original data typically resides on a hard drive, or on an array of hard drives, but may also reside on other forms of storage media, such as solid state memory.
- Data backups are necessary for several reasons, including disaster recovery, restoring data lost due to storage media failure, recovering accidentally deleted data, and repairing corrupted data resulting from malfunctioning or malicious software.
- a virtual machine is a software abstraction of an underlying physical (i.e., hardware) machine which enables one or more instances of an operating system, or even one or more operating systems, to run concurrently on a physical host machine.
- Virtual machines have become popular with administrators of data centers, which can contain dozens, hundreds, or even thousands of physical machines.
- the use of virtual servers greatly simplifies the task of configuring and administering servers in a large scale environment, because a virtual machine may be quickly placed into service without incurring the expense of provisioning a hardware machine at a data center.
- Virtualization is highly scalable, enabling servers to be allocated or deallocated in response to changes in demand. Support and administration requirements may be reduced because virtual servers are readily monitored and accessed using remote administration tools and diagnostic software.
- a virtual server consists of three components.
- the first component is virtualization software configured to run on the host machine which performs the hardware abstraction, often referred to as a hypervisor.
- the second component is a data file which represents the filesystem of the virtual machine, which typically contains the virtual machine's operating system, applications, data files, etc.
- a virtual machine data file may be a hard disk image file, such as, without limitation, a Virtual Machine Disk Format (VMDK) format file.
- VMDK Virtual Machine Disk Format
- the third component is the physical machine on which the virtualization software executes.
- a physical machine may include a processor, random-access memory, internal or external disk storage, and input/output interfaces, such as network, storage, and desktop interfaces (e.g., keyboard, pointing device, and graphic display interfaces.)
- Virtual machine files may be backed up as images, or replications of the complete virtual machine file.
- Such backup schemes may logically divide and store the virtual machine file into a number of smaller logical blocks which taken together constitute a “snapshot” of an entire filesystem as it existed at the time the backup was performed. While such systems are well-suited for restoring an entire filesystem, such systems may have drawbacks. For example, during a restoration procedure an entire filesystem may need to be transferred from a backup device to a destination device, even though only a subset of the destination blocks may have changed since the last backup was performed. In another example, it may be desirable to restore a virtual machine back to a state which existed at a particular point in time.
- a backup system which performs virtual server backups with increased efficiency and effectiveness while permitting the restoration of only that data which was modified since the last backup, and/or the last restoration, would be a welcome advance.
- the present disclosure is directed to a method of performing selective restoration of a volume level backup set, or archive.
- the volume level backup set, or archive may include a virtual machine file, e.g., a VMDK file.
- the backup set includes a plurality of fixed-sized blocks representative of a virtual machine file (e.g., a virtual disk file and/or a VMDK file) and an index file indicative, at least in part, of the positions of the individual fixed size blocks within the archive.
- a virtual machine file e.g., a virtual disk file and/or a VMDK file
- index file indicative, at least in part, of the positions of the individual fixed size blocks within the archive.
- the disclosed method processes 1 MB fixed-length blocks of data of a virtual machine file.
- a unique identifier such as without limitation, an MD5 hash, is created for this block data.
- the 1 MB of data can be compressed, or left uncompressed.
- the 1 MB of data is stored as a single file.
- the file name is based at least in part on the hash value of the 1 MB data block.
- the hash of this file is saved in a separate index file for later use to retrieve, validate, and rebuild the backup data.
- the data blocks are stored at a storage destination, in a unique directory structure consisting of 256 first level directories designated as 00-FF, each having 256 second level directories designated as 00-FF within, comprising 65,536 directories in total.
- the 1 MB compressed (or uncompressed) data files are stored in the directory structure based on the first four bytes of the hash, e.g.,
- the first four bytes of data for the file name are “0022”.
- the file is stored in directory “./00/22/”.
- the .gz extension indicates the file is compressed.
- Subsequent backups are performed having as a destination the same storage location.
- Data blocks are generated using the above unique hash.
- a file query is made to the storage location to see if there is already a file existing with the same hash. If the file does not exist, the source data is written into the directory hierarchy with the hash as the file name and an index file is updated. If the file exists, then only the index file is updated for the current backup being run.
- the directory structure will accumulate data blocks from all backups sent thereto.
- a separate index file is created for each backup, and is used to keep track of the blocks of data for, e.g., re-assembling data block of the original source during restoration.
- a routine may be scheduled to run on an ad-hoc or periodic basis that reads the data within a stored file, and validates the data in the file to verify a match to the hash file name. If the data does not match, the block is considered suspect, and is slated to be deleted. All associated backups that include this data block are flagged as “bad”. The index file corresponding to backups so flagged may additionally or alternatively include a “bad” flag.
- the data blocks may be evaluated to determine whether the data contained therein exhibits a predefined (“special”) data pattern.
- a special data pattern may include a particular or repeating pattern, a data block consisting entirely of zero (OOH) bytes.
- OOH zero
- a special hash is generated that represents the special data block containing the particular data pattern.
- the special hash may be hard-coded, defined in a database, and/or defined in a configuration file. Since the contents of a special data block is predefined, it is only necessary to record the fact that the data block is special. It is unnecessary to store the actual contents of a special block.
- the index file is updated accordingly and the backup proceeds, in this manner, resources are conserved since special blocks, e.g., null blocks, do not consume space on the storage device, do not use communication bandwidth during backup and restoration procedures, do not require as much computational resources, and so forth.
- special blocks e.g., null blocks
- a software service is configured to execute on a virtual machine host server.
- the host server is programmed to look for new backups of a virtual machine, which may be performed on a scheduled basis.
- a first restoration writes every data block comprising the backup set onto the virtual disk. If a subsequent backup is performed or identified, the disclosed method then determines which, if any, new unique data blocks that have been backed up. The later (more recent) backed up data blocks are then overlaid over the original previously restored virtual machine image. In this manner, a remote backup set is kept up-to-date and ready to be activated with minimal compressed or uncompressed data being transferred over the network (e.g., LAN/WAN).
- the network e.g., LAN/WAN
- the disclosed method may exhibit reduced network utilization, fewer disk I/O operations, and reduced execution times than prior art restoration and replication methods.
- an index file may be consulted (e.g., data read therefrom) to determine which data blocks comprise the specified backup set.
- the target virtual machine file is reconstructed from the component data blocks thereof at the source machine.
- Each data block is written to the target virtual machine file such that the original virtual machine file is recreated as it existed when the backup set was initially created.
- a virtual machine file or a data block thereof may be flagged as having been restored from a previous backup. Such as flag may be referred to as a “previous restore” flag.
- a previous restore flag may be read to determine whether a subject virtual machine file and/or data block thereof was previously restored from a backup set. If so, restoration of the subject virtual machine file and/or data block is skipped, thereby eliminating the processing and transfer of redundant and/or duplicative data blocks.
- a method in accordance with the present disclosure may permit multi-user access to read data from compressed and/or de-duplicated backup data files and allow for single file or directory restore.
- an entire virtual disk backup can be read for restoration, replication, or archived to offline storage such as optical media or magnetic tape.
- a method in accordance with the present disclosure for restoring to a first storage device a virtual machine file data from a second storage device containing a backup set of the virtual machine data file, wherein, the backup set includes at least one backup datablock and an index file includes the steps of identifying a backup data block of the backup set corresponding to a target data block of the virtual machine file.
- a corresponding target data block is evaluated to determine whether it has changed since a previous restoration.
- the backup data block is written to the target data block in response to an evaluation that the corresponding target data block has changed since a previous restoration.
- a method in accordance with the present disclosure for restoring to a first storage device a virtual machine file data from a second storage device containing a backup set of the virtual machine data file, wherein the backup set includes at least one backup datablock and an index file includes the steps of identifying a backup data block of the backup set corresponding to a target data block of the virtual machine file.
- a corresponding target data block is evaluated to determine whether it has changed since a previous backup.
- the backup data block is written to the target data block in response to an evaluation that the corresponding target data block has changed since a previous backup
- FIG. 1 shows a block diagram of an embodiment of a virtual machine backup system in accordance with the present disclosure
- FIG. 2 is a block diagram illustrating a directory hierarchy of an embodiment of a virtual machine backup in accordance with the present disclosure.
- FIG. 3 is a block diagram of an embodiment of a virtual machine backup method in accordance with the present disclosure
- FIG. 4A is a flowchart of an embodiment of an aspect of a virtual machine data replication method in accordance with the present disclosure
- FIG. 4B is a flowchart of an embodiment of another aspect of a virtual machine data replication method in accordance with the present disclosure.
- FIG. 5 illustrates a block diagram of an embodiment of a virtual machine data replication method in accordance with the present disclosure.
- the present invention may be described herein in terms of functional block components, code listings, optional selections, page displays, and various processing steps. It should be appreciated that such functional blocks may be realized by any number of hardware and/or software components configured to perform the specified functions.
- the present invention may employ various integrated circuit components, e.g., memory elements, processing elements, logic elements, look-up tables, and the like, which may carry out a variety of functions under the control of one or more microprocessors or other control devices.
- the software elements of the present invention may be implemented with any programming or scripting language such as C, C++, C#, Java, COBOL, assembler, PERL, Python, PHP, or the like, with the various algorithms being implemented with any combination of data structures, objects, processes, routines or other programming elements.
- the object code created may be executed by any computer having an Internet Web Browser, on a variety of operating systems including Windows, Macintosh, and/or Linux.
- the present invention may employ any number of conventional techniques for data transmission, signaling, data processing, network control, and the like.
- the present invention may be embodied as a method, a data processing system, a device for data processing, and/or a computer program product. Accordingly, the present invention may take the form of an entirely software embodiment, an entirely hardware embodiment, or an embodiment combining aspects of both software and hardware. Furthermore, the present invention may take the form of a computer program product on a computer-readable storage medium having computer-readable program code means embodied in the storage medium. Any suitable computer-readable storage medium may be utilized, including hard disks, CD-ROM, DVD-ROM, optical storage devices, magnetic storage devices, semiconductor storage devices (e.g., USB thumb drives) and/or the like.
- These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means that implement the function specified in the flowchart block or blocks.
- the computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions that execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks.
- any databases, systems, or components of the present invention may consist of any combination of databases or components at a single location or at multiple locations, wherein each database or system includes any of various suitable security features, such as firewalls, access codes, encryption, de-encryption, compression, decompression, and/or the like.
- FIG. 1 illustrates a representative operating environment 100 for an example embodiment of a virtual machine backup system 105 having the capability to perform a file-level restoration in accordance with the present disclosure.
- Representative operating environment 100 includes virtual machine backup system 105 which can be a personal computer (PC) or a server, which further includes at least one system bus 150 which couples system components, including at least one processor 110 ; a system memory 115 which may include random-access memory (RAM); at least one storage device 130 , such as without limitation one or more hard disks, CD-ROMs or DVD-ROMs, or other non-volatile storage devices, such as without limitation flash memory devices; and a data network interface 140 .
- Virtual machine backup system 105 includes the capability of performing a method of virtual machine backup and/or restoration as disclosed herein.
- System bus 150 may include any type of data communication structure, including without limitation a memory bus or memory controller, a peripheral bus, a virtual bus, a software bus, and/or a local bus using any bus architecture such as without limitation PCI, USB or IEEE 1394 (Firewire).
- Data network interface 140 may be a wired network interface such as a 100Base-T Fast Ethernet interface, or a wireless network interface such as without limitation a wireless network interface compliant with the IEEE 802.1.1 (i.e., WiFi), GSM, or CDMA standard.
- Virtual machine backup system 105 may be operated in a networked environment via data network interface 140 , wherein system 105 is connected to one or more virtual machine hosts 160 by a data network 180 , such as a local area network or the Internet, for the transmission and reception of data, such as without limitation backing up and restoring virtual machine data files as will be further described herein.
- a data network 180 such as a local area network or the Internet
- Each of the one or more virtual machine hosts 160 may include one or more virtual machines 170 operating therein, as will be appreciated by the skilled artisan.
- Virtual machine backup system 105 includes a virtual machine data replication module 120 that is configured to perform a method of file restoration as described herein.
- virtual machine data replication module 120 includes a set of programmable instructions adapted to execute on processor 100 for performing the disclosed method of virtual machine data replication.
- a method for restoring a virtual disk file or virtual machine file, e.g., a VMDK file, from a plurality of datablocks stored within a directory hierarchy is presented herein.
- the plurality of datablocks may be of equal size, e.g., about 1 MB in size, or may be of varying size.
- the present disclosure provides a method for restoring files from a virtual machine image backup.
- the virtual machine image backup may include a plurality of fixed-size data blocks representative of corresponding blocks of the source virtual machine file, and an index file that may include, without limitation, a list of data blocks, a unique identifier (e.g., a hash value) that uniquely identify a data block, date and time of backup, and source and destination locations.
- a unique identifier e.g., a hash value
- a virtual machine file 420 slated for backup may be stored on a storage device, such as without limitation, hard disk 410 . While it is contemplated that hard disk 410 may be included within a virtual machine host, is it to be understood that a virtual machine file 420 may be stored on a hard disk array, such as a storage-area network (SAN), a redundant array of independent disks (RAID), network-attached storage (NAS) and/or on any storage medium now or in the future known.
- SAN storage-area network
- RAID redundant array of independent disks
- NAS network-attached storage
- the virtual machine file 420 is logically divided into a number of fixed-length blocks 430 of like size.
- a blocksize of 1 MB is used, however, it is to be understood that a blocksize of less than 1 MB, or greater than 1 MB, may be used within the scope of the disclosed method.
- the blocksize is determined at least in part by a correlation between performance and blocksize. Other parameters affecting blocksize may include, without limitation, a data bus speed, a data bus width, a virtual machine file size, a processor speed, a storage device bandwidth, and a network throughput. If the size of a virtual machine does not precisely equal a multiple of a chosen fixed blocksize, the remainder may be padded with e.g., zeros, nulls, or any other fill pattern, to achieve a set of equal-sized blocks.
- An individual backup data file 445 is created from each fixed-length block 430 of the virtual machine file 420 .
- individual backup data file 445 may be given a temporary filename, and/or stored in a temporary location, e.g., /var/tmp/block000001.dat.
- a hash is generated according to the contents of each individual backup data file.
- a 4,096 bit MD5 hash is used to create the hash value from the contents thereof.
- the resultant hash value is stored in an index file corresponding to the current backup session which store for later use during, e.g., data restoration.
- the index file may include, without limitation, a list of data blocks comprising the backup set, hash values corresponding thereto, a date and time of backup, a source location, and a destination location.
- a collection of hash values representative of a backup of virtual machine file, and data associated therewith, may be stored in an index file 455 .
- Such a collection, together with the individual backup data files comprising the backed-up virtual machine file 420 is known as a “backup set.”
- the data block 430 may be compressed during a compression step 432 using any suitable manner of data compression, including without limitation, LZW, zip, gzip, rar, and/or bzip.
- LZW low-power data compression
- zip zip
- gzip zip
- rar rar
- bzip bzip
- lossless data compression is used however in certain embodiments lossy data compression may advantageously be used.
- the hash value may be regarded as a unique block identifier, or a unique identifier of a backup data file 455 .
- a non-temporary (“archival”) filename of the backup data file may be generated, at least in part, from the hash value, as illustrated in step 434 .
- the filename of a backup data file 455 may be created by appending a hexadecimal representation of the hash value to a file prefix and/or to an appropriate file extension.
- Each backup data file 455 comprising the virtual machine file therefore has a unique filename based upon the hash value.
- a hierarchical directory structure 300 is provided on a backup storage device, e.g., storage device 130 , for storing the backup data files.
- the disclosed structure has at a first level thereof a plurality of directories 320 et seq. (e.g., folders).
- Each first level directory contains therein a plurality of second level directories 330 .
- the hierarchy includes 256 first level directories, wherein each first level directory includes 256 second level directories, for a total number of 65,536 directories.
- the first level and second level directories may be named in accordance with a sixteen bit hexadecimal value, e.g., 00-FF.
- a plurality of first level directories may be named in accordance with the series ./00, ./01, ./02 . . . ./FF while a second level of directories may be named ./00/01, ./00/02/ . . . ./00/FF.
- directory mapping schemes are envisioned within the scope of the present disclosure, such as without limitation, a directory hierarchy having fewer than two levels, a directory hierarchy having greater than two levels, a directory hierarchy having a directory naming convention that includes fewer than a sixteen bit hexadecimal value, a directory hierarchy having a directory naming convention that includes greater than a sixteen bit hexadecimal value, and/or a directory hierarchy having a directory naming convention that includes an alternative naming encoding, such as octal, ASCII85, and the like.
- An initial backup may be performed wherein all blocks comprising a source (e.g., original) virtual machine file on a source device are stored on a backup device as a backup set.
- Each data block may be stored as a file.
- a source device may be a hard disk drive, however, other source devices, such as without limitation, solid state memory, are contemplated within the scope of the present disclosure.
- a backup device may be a hard disk drive, tape drive, solid state drive, or any other suitable data storage device.
- a corresponding index file is created substantially concurrently with storing the source data on the backup device.
- each data block may be tagged with a timestamp, e.g., date and time, which may be stored within metadata of a file containing the data block.
- the disclosed method of performing data replication 200 starts with the step 205 , which may include initialization, housekeeping, resource allocation (e.g., memory allocation, opening I/O channels, instantiation), and the like.
- the desired backup set, and a desired destination location is selected.
- the backup set and/or destination selection may be performed by any suitable manner of selection, including without limitation, via a user interface (e.g., a web-based interface), via an application programming interface (API), remote procedure calls (RPC), and the like.
- the set of datablocks comprising the backup set are identified.
- Index file 455 may be consulted (e.g., data read therefrom) to determine which data blocks comprise the specified backup set.
- the target virtual machine file is reconstructed from the component data blocks thereof at the destination, which may be the original source virtual machine file represented by the backup set, and/or a different, or new, virtual machine file.
- a datablock is copied from its storage directory 330 within the backup directory hierarchy 300 .
- Each data block is written to the target virtual machine file such that the original virtual machine file is recreated as it existed when the backup set was initially created.
- the data block is flagged as having been restored from a previous backup. Such as flag may be referred to as a “previous restore” flag.
- a data element in a virtual machine file, a data block, or in metadata thereof may indicate a virtual machine file or a data block thereof was restored from a previous backup.
- a timestamp associated with the datablock may be set to a predetermined value to indicate a virtual machine file or a data block thereof was restored from a previous backup, e.g., a timestamp seconds field may be set to “33”.
- Step 230 a determination is made as to whether all the component datablocks of the backup set have been copied to the destination. If datablocks remain to be copied, the process iterates with the step 220 . If it is determined all datablocks have been copied, the process concludes with the step 235 .
- Step 235 may include reporting to a user, or calling program, statistics indicative of the restoration process, such as without limitation, number of blocks copied, amount of data processed, execution time, and the like.
- a subsequent restoration procedure 250 of a virtual machine file in accordance with the present disclosure is presented wherein a previous restore flag may be read to determine whether a given virtual machine file and/or data block thereof was previously restored from a backup set.
- initialization, housekeeping, resource allocation e.g., memory allocation, opening I/O channels), and the like, may be performed.
- the desired backup set, and a desired destination location is selected.
- the backup set and/or destination selection may be performed by any suitable manner of selection, including without limitation, via an user interface (e.g., a web-based interface), via an application programming interface (API), remote procedure calls (RPC), and the like.
- the set of datablocks comprising the backup set are identified. Index file 455 may be consulted to determine which data blocks comprise the specified backup set.
- a candidate backup datablock for restoration to the destination location is evaluated to determine whether the corresponding block at the destination location has changed since a previous backup.
- a “previous restore” flag 460 may be tested to make this determination.
- a previous restore flag 460 may include a timestamp of the destination block.
- the timestamp may be tested to determine whether the seconds field is set to a predetermined value, e.g., “33”, thus indicating the corresponding virtual machine file and/or datablock was previously restored from a backup set (e.g., unchanged.)
- identification of a changed destination data block may be performed by comparing a hash value of the destination data block, which may be from an initially-restored virtual machine file, to the hash value of the corresponding data block of the identified backup set. If the hash values do not match, it is assumed the data block changed from the initially-restored file to the current backup set. If the hash values of the destination and backup datablocks match, it is assumed the corresponding destination datablock is unchanged from a previous restoration.
- step 275 If in the step 275 , it is determined the destination datablock has changed from a previously-restored version, the data block from the current backup set is copied over the corresponding block in the destination virtual machine file in the step 280 .
- a previous restore flag 460 of the just-written destination datablock is set to a predetermined value indicating the datablock is unchanged, e.g., has been previously restored from a backup datablock. Additionally or alternatively, upon completion of a restoration, a timestamp associated with the virtual machine file and/or a data block thereof may be reset.
- a previous restore flag 460 associated with the virtual machine file and/or a data block thereof may additionally or alternatively be set, e.g., a timestamp seconds field may be set to “33”.
- a determination is made as to whether all the candidate datablocks of the backup set have been evaluated for possible copying to the destination. If datablocks remain to be processed, execution iterates with the step 270 . If it is determined all datablocks have been process, execution concludes with the step 295 .
- Step 295 may include reporting to a user, or calling program, statistics indicative of the restoration process, such as without limitation, number of blocks copied, total block processed, amount of data processed, execution time, and the like.
- step 275 it is determined that the destination datablock has not changed from a previous restoration, it is assumed the subject data block is unchanged, and therefore, the data block is skipped (e.g., not copied from the backup set to the destination virtual machine) and processing iterates with the step 270 .
- image-level (e.g., a virtual machine image) restoration and file-level (e.g., one or more individual files within a virtual machine) restoration may be performed by the disclosed method.
- a data verification step may be performed wherein, for each identified changed data block, a hash value (e.g., an MD5 hash) of the stored datablock is computed and compared to a stored (e.g., previously-computed) hash value for the respective stored data block. If the computed hash value for any identified changed data block does not match the stored hash value, a complete virtual machine restoration is performed, e.g., all blocks of the virtual machine backup set are copied over the corresponding blocks of the destination virtual machine file. If the computed hash value for any identified changed data block correctly matches the stored hash value, only the identified changed blocks are copied over the corresponding blocks of the destination virtual machine file.
- a hash value e.g., an MD5 hash
- a file-level restoration in accordance with the present disclosure may be performed by identifying which data block(s) contain at least a portion of a file to be restored. For each block thus identified, a hash value check is performed as described hereinabove to determine which of the block(s) is changed with respect to the initially-restored version of the target virtual machine. Only those blocks which contain changed data are copied to the virtual machine file.
- the present disclosure is also directed to a computer-based apparatus and a computing system configured to perform a method of data replication as described herein. Also disclosed is computer-readable media comprising a set of instructions of performing a method of data replication as described herein.
Abstract
Description
- The present application claims the benefit of and priority to U.S. Provisional Application Ser. No. 61/168,315, filed on Apr. 10, 2009, entitled “VIRTUAL MACHINE DATA BACKUP”; U.S. Provisional Application Ser. No. 61/168,318, filed on Apr. 10, 2009, entitled “VIRTUAL MACHINE FILE-LEVEL RESTORATION”; and U.S. Provisional Application Ser. No. 61/172,435, filed on Apr. 24, 2009, entitled “VIRTUAL MACHINE DATA REPLICATION”; the entirety of each are hereby incorporated by reference herein for all purposes.
- 1. Technical Field
- The present disclosure relates to computer data backup, and in particular, to a system and method for performing block-level backups of virtual machine, wherein backed up data is stored in de-duplicated form in a hierarchical directory structure.
- 2. Background of Related Art
- Continuing advances in storage technology allow vast amounts of digital data to be stored cheaply and efficiently. However, in the event of a failure or catastrophe, equally vast amounts of data can be lost. Therefore, data backup is a critical component of computer-based systems. As used herein, the term “backup” may refer to the act of creating copies of data, and may refer to the actual backed-up copy of the original data. The original data typically resides on a hard drive, or on an array of hard drives, but may also reside on other forms of storage media, such as solid state memory. Data backups are necessary for several reasons, including disaster recovery, restoring data lost due to storage media failure, recovering accidentally deleted data, and repairing corrupted data resulting from malfunctioning or malicious software.
- A virtual machine (VM) is a software abstraction of an underlying physical (i.e., hardware) machine which enables one or more instances of an operating system, or even one or more operating systems, to run concurrently on a physical host machine. Virtual machines have become popular with administrators of data centers, which can contain dozens, hundreds, or even thousands of physical machines. The use of virtual servers greatly simplifies the task of configuring and administering servers in a large scale environment, because a virtual machine may be quickly placed into service without incurring the expense of provisioning a hardware machine at a data center. Virtualization is highly scalable, enabling servers to be allocated or deallocated in response to changes in demand. Support and administration requirements may be reduced because virtual servers are readily monitored and accessed using remote administration tools and diagnostic software.
- In one aspect, a virtual server consists of three components. The first component is virtualization software configured to run on the host machine which performs the hardware abstraction, often referred to as a hypervisor. The second component is a data file which represents the filesystem of the virtual machine, which typically contains the virtual machine's operating system, applications, data files, etc. A virtual machine data file may be a hard disk image file, such as, without limitation, a Virtual Machine Disk Format (VMDK) format file. Thus, for each virtual machine, a separate virtual machine file is required. The third component is the physical machine on which the virtualization software executes. A physical machine may include a processor, random-access memory, internal or external disk storage, and input/output interfaces, such as network, storage, and desktop interfaces (e.g., keyboard, pointing device, and graphic display interfaces.)
- Virtual machine files may be backed up as images, or replications of the complete virtual machine file. Such backup schemes may logically divide and store the virtual machine file into a number of smaller logical blocks which taken together constitute a “snapshot” of an entire filesystem as it existed at the time the backup was performed. While such systems are well-suited for restoring an entire filesystem, such systems may have drawbacks. For example, during a restoration procedure an entire filesystem may need to be transferred from a backup device to a destination device, even though only a subset of the destination blocks may have changed since the last backup was performed. In another example, it may be desirable to restore a virtual machine back to a state which existed at a particular point in time. A backup system which performs virtual server backups with increased efficiency and effectiveness while permitting the restoration of only that data which was modified since the last backup, and/or the last restoration, would be a welcome advance.
- The present disclosure is directed to a method of performing selective restoration of a volume level backup set, or archive. The volume level backup set, or archive, may include a virtual machine file, e.g., a VMDK file. In one embodiment, the backup set includes a plurality of fixed-sized blocks representative of a virtual machine file (e.g., a virtual disk file and/or a VMDK file) and an index file indicative, at least in part, of the positions of the individual fixed size blocks within the archive. Such a backup is described in the commonly-owned, concurrently-filed U.S. patent application Ser. No. 12/758,345 entitled “VIRTUAL MACHINE DATA BACKUP”, the entirety of which is hereby incorporated by reference herein for all purposes.
- The disclosed method processes 1 MB fixed-length blocks of data of a virtual machine file. A unique identifier, such as without limitation, an MD5 hash, is created for this block data. The 1 MB of data can be compressed, or left uncompressed. The 1 MB of data is stored as a single file. The file name is based at least in part on the hash value of the 1 MB data block. The hash of this file is saved in a separate index file for later use to retrieve, validate, and rebuild the backup data. The data blocks, whether in compressed or uncompressed form, are stored at a storage destination, in a unique directory structure consisting of 256 first level directories designated as 00-FF, each having 256 second level directories designated as 00-FF within, comprising 65,536 directories in total. The 1 MB compressed (or uncompressed) data files are stored in the directory structure based on the first four bytes of the hash, e.g.,
-
- “./00/22/T.002249a8a218ef8a4da87550f388942d.gz”.
- The first four bytes of data for the file name are “0022”. The file is stored in directory “./00/22/”. The .gz extension indicates the file is compressed.
- Subsequent backups are performed having as a destination the same storage location. Data blocks are generated using the above unique hash. A file query is made to the storage location to see if there is already a file existing with the same hash. If the file does not exist, the source data is written into the directory hierarchy with the hash as the file name and an index file is updated. If the file exists, then only the index file is updated for the current backup being run.
- Over time the directory structure will accumulate data blocks from all backups sent thereto. A separate index file is created for each backup, and is used to keep track of the blocks of data for, e.g., re-assembling data block of the original source during restoration.
- The use of a hash also provides a self-checking mechanism which enables self-validation of the data within the stored file. A routine may be scheduled to run on an ad-hoc or periodic basis that reads the data within a stored file, and validates the data in the file to verify a match to the hash file name. If the data does not match, the block is considered suspect, and is slated to be deleted. All associated backups that include this data block are flagged as “bad”. The index file corresponding to backups so flagged may additionally or alternatively include a “bad” flag.
- In an embodiment, the data blocks (e.g., the 1 MB data blocks) may be evaluated to determine whether the data contained therein exhibits a predefined (“special”) data pattern. For example with limitation, a special data pattern may include a particular or repeating pattern, a data block consisting entirely of zero (OOH) bytes. In this instance, a special hash is generated that represents the special data block containing the particular data pattern. The special hash may be hard-coded, defined in a database, and/or defined in a configuration file. Since the contents of a special data block is predefined, it is only necessary to record the fact that the data block is special. It is unnecessary to store the actual contents of a special block. Thus, for each data block identified as special, the index file is updated accordingly and the backup proceeds, in this manner, resources are conserved since special blocks, e.g., null blocks, do not consume space on the storage device, do not use communication bandwidth during backup and restoration procedures, do not require as much computational resources, and so forth. This provides an efficient way to skip special (e.g., null) data in a given backup set.
- In one embodiment, a software service is configured to execute on a virtual machine host server. The host server is programmed to look for new backups of a virtual machine, which may be performed on a scheduled basis. A first restoration writes every data block comprising the backup set onto the virtual disk. If a subsequent backup is performed or identified, the disclosed method then determines which, if any, new unique data blocks that have been backed up. The later (more recent) backed up data blocks are then overlaid over the original previously restored virtual machine image. In this manner, a remote backup set is kept up-to-date and ready to be activated with minimal compressed or uncompressed data being transferred over the network (e.g., LAN/WAN). Only those datablocks which changed since the most recent full restoration will be restored during subsequent restorations, thereby efficiently restoring backup sets, reducing restoration times, and reducing computing resource usage. The disclosed method may exhibit reduced network utilization, fewer disk I/O operations, and reduced execution times than prior art restoration and replication methods.
- During an initial restoration of a virtual machine file, an index file may be consulted (e.g., data read therefrom) to determine which data blocks comprise the specified backup set. The target virtual machine file is reconstructed from the component data blocks thereof at the source machine. Each data block is written to the target virtual machine file such that the original virtual machine file is recreated as it existed when the backup set was initially created. Additionally or alternatively, a virtual machine file or a data block thereof may be flagged as having been restored from a previous backup. Such as flag may be referred to as a “previous restore” flag. During a subsequent restoration of a virtual machine file, a previous restore flag may be read to determine whether a subject virtual machine file and/or data block thereof was previously restored from a backup set. If so, restoration of the subject virtual machine file and/or data block is skipped, thereby eliminating the processing and transfer of redundant and/or duplicative data blocks.
- A method in accordance with the present disclosure may permit multi-user access to read data from compressed and/or de-duplicated backup data files and allow for single file or directory restore. In addition an entire virtual disk backup can be read for restoration, replication, or archived to offline storage such as optical media or magnetic tape.
- In an embodiment, a method in accordance with the present disclosure for restoring to a first storage device a virtual machine file data from a second storage device containing a backup set of the virtual machine data file, wherein, the backup set includes at least one backup datablock and an index file, includes the steps of identifying a backup data block of the backup set corresponding to a target data block of the virtual machine file. A corresponding target data block is evaluated to determine whether it has changed since a previous restoration. The backup data block is written to the target data block in response to an evaluation that the corresponding target data block has changed since a previous restoration.
- In another embodiment, a method in accordance with the present disclosure for restoring to a first storage device a virtual machine file data from a second storage device containing a backup set of the virtual machine data file, wherein the backup set includes at least one backup datablock and an index file, includes the steps of identifying a backup data block of the backup set corresponding to a target data block of the virtual machine file. A corresponding target data block is evaluated to determine whether it has changed since a previous backup. The backup data block is written to the target data block in response to an evaluation that the corresponding target data block has changed since a previous backup
- The above and other aspects, features, and advantages of the present disclosure will become more apparent in light of the following detailed description when taken in conjunction with the accompanying drawings in which:
-
FIG. 1 shows a block diagram of an embodiment of a virtual machine backup system in accordance with the present disclosure; -
FIG. 2 is a block diagram illustrating a directory hierarchy of an embodiment of a virtual machine backup in accordance with the present disclosure; and -
FIG. 3 is a block diagram of an embodiment of a virtual machine backup method in accordance with the present disclosure; -
FIG. 4A is a flowchart of an embodiment of an aspect of a virtual machine data replication method in accordance with the present disclosure; -
FIG. 4B is a flowchart of an embodiment of another aspect of a virtual machine data replication method in accordance with the present disclosure; and -
FIG. 5 illustrates a block diagram of an embodiment of a virtual machine data replication method in accordance with the present disclosure. - Particular embodiments of the present disclosure are described hereinbelow with reference to the accompanying drawings; however, it is to be understood that the disclosed embodiments are merely examples of the disclosure, which may be embodied in various forms. Well-known functions or constructions are not described in detail to avoid obscuring the present disclosure in unnecessary detail. Therefore, specific structural and functional details disclosed herein are not to be interpreted as limiting, but merely as a basis for the claims and as a representative basis for teaching one skilled in the art to variously employ the present disclosure in virtually any appropriately detailed structure in the discussion contained herein, the terms user interface element and/or button are understood to be non-limiting, and include other user interface elements such as, without limitation, a hyperlink, clickable image, and the like.
- Additionally, the present invention may be described herein in terms of functional block components, code listings, optional selections, page displays, and various processing steps. It should be appreciated that such functional blocks may be realized by any number of hardware and/or software components configured to perform the specified functions. For example, the present invention may employ various integrated circuit components, e.g., memory elements, processing elements, logic elements, look-up tables, and the like, which may carry out a variety of functions under the control of one or more microprocessors or other control devices.
- Similarly, the software elements of the present invention may be implemented with any programming or scripting language such as C, C++, C#, Java, COBOL, assembler, PERL, Python, PHP, or the like, with the various algorithms being implemented with any combination of data structures, objects, processes, routines or other programming elements. The object code created may be executed by any computer having an Internet Web Browser, on a variety of operating systems including Windows, Macintosh, and/or Linux.
- Further, it should be noted that the present invention may employ any number of conventional techniques for data transmission, signaling, data processing, network control, and the like.
- It should be appreciated that the particular implementations shown and described herein are illustrative of the invention and its best mode and are not intended to otherwise limit the scope of the present invention in any way. Examples are presented herein which may include sample data items (e.g., names, dates, etc) which are intended as examples and are not to be construed as limiting. Indeed, for the sake of brevity, conventional data networking, application development and other functional aspects of the systems (and components of the individual operating components of the systems) may not be described in detail herein. Furthermore, the connecting lines shown in the various figures contained herein are intended to represent example functional relationships and/or physical or virtual couplings between the various elements. It should be noted that many alternative or additional functional relationships or physical or virtual connections may be present in a practical electronic data communications system.
- As will be appreciated by one of ordinary skill in the art, the present invention may be embodied as a method, a data processing system, a device for data processing, and/or a computer program product. Accordingly, the present invention may take the form of an entirely software embodiment, an entirely hardware embodiment, or an embodiment combining aspects of both software and hardware. Furthermore, the present invention may take the form of a computer program product on a computer-readable storage medium having computer-readable program code means embodied in the storage medium. Any suitable computer-readable storage medium may be utilized, including hard disks, CD-ROM, DVD-ROM, optical storage devices, magnetic storage devices, semiconductor storage devices (e.g., USB thumb drives) and/or the like.
- The present invention is described below with reference to block diagrams and flowchart illustrations of methods, apparatus (e.g., systems), and computer program products according to various aspects of the invention. It will be understood that each functional block of the block diagrams and the flowchart illustrations, and combinations of functional blocks in the block diagrams and flowchart illustrations, respectively, can be implemented by computer program instructions. These computer program instructions may be loaded onto a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions that execute on the computer or other programmable data processing apparatus create means for implementing the functions specified in the flowchart block or blocks.
- These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means that implement the function specified in the flowchart block or blocks. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions that execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks.
- Accordingly, functional blocks of the block diagrams and flowchart illustrations support combinations of means for performing the specified functions, combinations of steps for performing the specified functions, and program instruction means for performing the specified functions. It will also be understood that each functional block of the block diagrams and flowchart illustrations, and combinations of functional blocks in the block diagrams and flowchart illustrations, can be implemented by either special purpose hardware-based computer systems that perform the specified functions or steps, or suitable combinations of special purpose hardware and computer instructions.
- One skilled in the art will also appreciate that, for security reasons, any databases, systems, or components of the present invention may consist of any combination of databases or components at a single location or at multiple locations, wherein each database or system includes any of various suitable security features, such as firewalls, access codes, encryption, de-encryption, compression, decompression, and/or the like.
- The scope of the invention should be determined by the appended claims and their legal equivalents, rather than by the examples given herein. For example, the steps recited in any method claims may be executed in any order and are not limited to the order presented in the claims. Moreover, no element is essential to the practice of the invention unless specifically described herein as “critical” or “essential,”
-
FIG. 1 illustrates arepresentative operating environment 100 for an example embodiment of a virtualmachine backup system 105 having the capability to perform a file-level restoration in accordance with the present disclosure.Representative operating environment 100 includes virtualmachine backup system 105 which can be a personal computer (PC) or a server, which further includes at least onesystem bus 150 which couples system components, including at least oneprocessor 110; asystem memory 115 which may include random-access memory (RAM); at least onestorage device 130, such as without limitation one or more hard disks, CD-ROMs or DVD-ROMs, or other non-volatile storage devices, such as without limitation flash memory devices; and adata network interface 140. Virtualmachine backup system 105 includes the capability of performing a method of virtual machine backup and/or restoration as disclosed herein.System bus 150 may include any type of data communication structure, including without limitation a memory bus or memory controller, a peripheral bus, a virtual bus, a software bus, and/or a local bus using any bus architecture such as without limitation PCI, USB or IEEE 1394 (Firewire).Data network interface 140 may be a wired network interface such as a 100Base-T Fast Ethernet interface, or a wireless network interface such as without limitation a wireless network interface compliant with the IEEE 802.1.1 (i.e., WiFi), GSM, or CDMA standard. - Virtual
machine backup system 105 may be operated in a networked environment viadata network interface 140, whereinsystem 105 is connected to one or more virtual machine hosts 160 by adata network 180, such as a local area network or the Internet, for the transmission and reception of data, such as without limitation backing up and restoring virtual machine data files as will be further described herein. Each of the one or more virtual machine hosts 160 may include one or morevirtual machines 170 operating therein, as will be appreciated by the skilled artisan. - Virtual
machine backup system 105 includes a virtual machinedata replication module 120 that is configured to perform a method of file restoration as described herein. In an embodiment, virtual machinedata replication module 120 includes a set of programmable instructions adapted to execute onprocessor 100 for performing the disclosed method of virtual machine data replication. In particular, a method for restoring a virtual disk file or virtual machine file, e.g., a VMDK file, from a plurality of datablocks stored within a directory hierarchy is presented herein. The plurality of datablocks may be of equal size, e.g., about 1 MB in size, or may be of varying size. - The present disclosure provides a method for restoring files from a virtual machine image backup. The virtual machine image backup may include a plurality of fixed-size data blocks representative of corresponding blocks of the source virtual machine file, and an index file that may include, without limitation, a list of data blocks, a unique identifier (e.g., a hash value) that uniquely identify a data block, date and time of backup, and source and destination locations.
- Referring to
FIGS. 2 and 3 , avirtual machine file 420 slated for backup may be stored on a storage device, such as without limitation,hard disk 410. While it is contemplated thathard disk 410 may be included within a virtual machine host, is it to be understood that avirtual machine file 420 may be stored on a hard disk array, such as a storage-area network (SAN), a redundant array of independent disks (RAID), network-attached storage (NAS) and/or on any storage medium now or in the future known. - The
virtual machine file 420 is logically divided into a number of fixed-length blocks 430 of like size. In one embodiment, a blocksize of 1 MB is used, however, it is to be understood that a blocksize of less than 1 MB, or greater than 1 MB, may be used within the scope of the disclosed method. In one aspect, the blocksize is determined at least in part by a correlation between performance and blocksize. Other parameters affecting blocksize may include, without limitation, a data bus speed, a data bus width, a virtual machine file size, a processor speed, a storage device bandwidth, and a network throughput. If the size of a virtual machine does not precisely equal a multiple of a chosen fixed blocksize, the remainder may be padded with e.g., zeros, nulls, or any other fill pattern, to achieve a set of equal-sized blocks. - An individual backup data file 445 is created from each fixed-
length block 430 of thevirtual machine file 420. In an embodiment, individual backup data file 445 may be given a temporary filename, and/or stored in a temporary location, e.g., /var/tmp/block000001.dat. A hash is generated according to the contents of each individual backup data file. In an embodiment, a 4,096 bit MD5 hash is used to create the hash value from the contents thereof. The resultant hash value is stored in an index file corresponding to the current backup session which store for later use during, e.g., data restoration. The index file may include, without limitation, a list of data blocks comprising the backup set, hash values corresponding thereto, a date and time of backup, a source location, and a destination location. A collection of hash values representative of a backup of virtual machine file, and data associated therewith, may be stored in anindex file 455. Such a collection, together with the individual backup data files comprising the backed-upvirtual machine file 420 is known as a “backup set.” - Additionally or alternatively, the data block 430 may be compressed during a
compression step 432 using any suitable manner of data compression, including without limitation, LZW, zip, gzip, rar, and/or bzip. Preferably, lossless data compression is used however in certain embodiments lossy data compression may advantageously be used. - The hash value may be regarded as a unique block identifier, or a unique identifier of a
backup data file 455. A non-temporary (“archival”) filename of the backup data file may be generated, at least in part, from the hash value, as illustrated instep 434. For example, the filename of a backup data file 455 may be created by appending a hexadecimal representation of the hash value to a file prefix and/or to an appropriate file extension. Each backup data file 455 comprising the virtual machine file therefore has a unique filename based upon the hash value. - A
hierarchical directory structure 300 is provided on a backup storage device, e.g.,storage device 130, for storing the backup data files. The disclosed structure has at a first level thereof a plurality ofdirectories 320 et seq. (e.g., folders). Each first level directory contains therein a plurality ofsecond level directories 330. In an embodiment, the hierarchy includes 256 first level directories, wherein each first level directory includes 256 second level directories, for a total number of 65,536 directories. The first level and second level directories may be named in accordance with a sixteen bit hexadecimal value, e.g., 00-FF. Thus, for example, a plurality of first level directories may be named in accordance with the series ./00, ./01, ./02 . . . ./FF while a second level of directories may be named ./00/01, ./00/02/ . . . ./00/FF. Other directory mapping schemes are envisioned within the scope of the present disclosure, such as without limitation, a directory hierarchy having fewer than two levels, a directory hierarchy having greater than two levels, a directory hierarchy having a directory naming convention that includes fewer than a sixteen bit hexadecimal value, a directory hierarchy having a directory naming convention that includes greater than a sixteen bit hexadecimal value, and/or a directory hierarchy having a directory naming convention that includes an alternative naming encoding, such as octal, ASCII85, and the like. - An initial backup may be performed wherein all blocks comprising a source (e.g., original) virtual machine file on a source device are stored on a backup device as a backup set. Each data block may be stored as a file. A source device may be a hard disk drive, however, other source devices, such as without limitation, solid state memory, are contemplated within the scope of the present disclosure. A backup device may be a hard disk drive, tape drive, solid state drive, or any other suitable data storage device. A corresponding index file is created substantially concurrently with storing the source data on the backup device. Additionally or alternatively, each data block may be tagged with a timestamp, e.g., date and time, which may be stored within metadata of a file containing the data block.
- With reference to
FIGS. 4A , 4B, and 5, the disclosed method of performingdata replication 200 starts with thestep 205, which may include initialization, housekeeping, resource allocation (e.g., memory allocation, opening I/O channels, instantiation), and the like. In thestep 210 the desired backup set, and a desired destination location, is selected. In an embodiment, the backup set and/or destination selection may be performed by any suitable manner of selection, including without limitation, via a user interface (e.g., a web-based interface), via an application programming interface (API), remote procedure calls (RPC), and the like. In thestep 215, the set of datablocks comprising the backup set are identified.Index file 455 may be consulted (e.g., data read therefrom) to determine which data blocks comprise the specified backup set. The target virtual machine file is reconstructed from the component data blocks thereof at the destination, which may be the original source virtual machine file represented by the backup set, and/or a different, or new, virtual machine file. In thestep 220, a datablock is copied from itsstorage directory 330 within thebackup directory hierarchy 300. Each data block is written to the target virtual machine file such that the original virtual machine file is recreated as it existed when the backup set was initially created. In thestep 225, the data block is flagged as having been restored from a previous backup. Such as flag may be referred to as a “previous restore” flag. For example, and without limitation, a data element in a virtual machine file, a data block, or in metadata thereof, may indicate a virtual machine file or a data block thereof was restored from a previous backup. In another non-limiting example, a timestamp associated with the datablock may be set to a predetermined value to indicate a virtual machine file or a data block thereof was restored from a previous backup, e.g., a timestamp seconds field may be set to “33”. In thestep 230, a determination is made as to whether all the component datablocks of the backup set have been copied to the destination. If datablocks remain to be copied, the process iterates with thestep 220. If it is determined all datablocks have been copied, the process concludes with thestep 235. Step 235 may include reporting to a user, or calling program, statistics indicative of the restoration process, such as without limitation, number of blocks copied, amount of data processed, execution time, and the like. - With particular reference now to
FIG. 4B , asubsequent restoration procedure 250 of a virtual machine file in accordance with the present disclosure is presented wherein a previous restore flag may be read to determine whether a given virtual machine file and/or data block thereof was previously restored from a backup set. In thestep 255, initialization, housekeeping, resource allocation (e.g., memory allocation, opening I/O channels), and the like, may be performed. In thestep 260 the desired backup set, and a desired destination location, is selected. In an embodiment, the backup set and/or destination selection may be performed by any suitable manner of selection, including without limitation, via an user interface (e.g., a web-based interface), via an application programming interface (API), remote procedure calls (RPC), and the like. In thestep 265, the set of datablocks comprising the backup set are identified.Index file 455 may be consulted to determine which data blocks comprise the specified backup set. - In the
steps flag 460 may be tested to make this determination. For example, and without limitation, a previous restoreflag 460 may include a timestamp of the destination block. The timestamp may be tested to determine whether the seconds field is set to a predetermined value, e.g., “33”, thus indicating the corresponding virtual machine file and/or datablock was previously restored from a backup set (e.g., unchanged.) In another envisioned embodiment, identification of a changed destination data block may be performed by comparing a hash value of the destination data block, which may be from an initially-restored virtual machine file, to the hash value of the corresponding data block of the identified backup set. If the hash values do not match, it is assumed the data block changed from the initially-restored file to the current backup set. If the hash values of the destination and backup datablocks match, it is assumed the corresponding destination datablock is unchanged from a previous restoration. - If in the
step 275, it is determined the destination datablock has changed from a previously-restored version, the data block from the current backup set is copied over the corresponding block in the destination virtual machine file in thestep 280. In thestep 285, a previous restoreflag 460 of the just-written destination datablock is set to a predetermined value indicating the datablock is unchanged, e.g., has been previously restored from a backup datablock. Additionally or alternatively, upon completion of a restoration, a timestamp associated with the virtual machine file and/or a data block thereof may be reset. A previous restoreflag 460 associated with the virtual machine file and/or a data block thereof may additionally or alternatively be set, e.g., a timestamp seconds field may be set to “33”. In thestep 290, a determination is made as to whether all the candidate datablocks of the backup set have been evaluated for possible copying to the destination. If datablocks remain to be processed, execution iterates with thestep 270. If it is determined all datablocks have been process, execution concludes with thestep 295. Step 295 may include reporting to a user, or calling program, statistics indicative of the restoration process, such as without limitation, number of blocks copied, total block processed, amount of data processed, execution time, and the like. - However, if in the
step 275 it is determined that the destination datablock has not changed from a previous restoration, it is assumed the subject data block is unchanged, and therefore, the data block is skipped (e.g., not copied from the backup set to the destination virtual machine) and processing iterates with thestep 270. By eliminating the transfer of redundant or duplicative datablocks in this manner, a virtual machine can be restored or replicated with increased efficiency and speed. It is envisioned that image-level (e.g., a virtual machine image) restoration and file-level (e.g., one or more individual files within a virtual machine) restoration may be performed by the disclosed method. - A data verification step may be performed wherein, for each identified changed data block, a hash value (e.g., an MD5 hash) of the stored datablock is computed and compared to a stored (e.g., previously-computed) hash value for the respective stored data block. If the computed hash value for any identified changed data block does not match the stored hash value, a complete virtual machine restoration is performed, e.g., all blocks of the virtual machine backup set are copied over the corresponding blocks of the destination virtual machine file. If the computed hash value for any identified changed data block correctly matches the stored hash value, only the identified changed blocks are copied over the corresponding blocks of the destination virtual machine file.
- in embodiments, a file-level restoration in accordance with the present disclosure may be performed by identifying which data block(s) contain at least a portion of a file to be restored. For each block thus identified, a hash value check is performed as described hereinabove to determine which of the block(s) is changed with respect to the initially-restored version of the target virtual machine. Only those blocks which contain changed data are copied to the virtual machine file.
- The present disclosure is also directed to a computer-based apparatus and a computing system configured to perform a method of data replication as described herein. Also disclosed is computer-readable media comprising a set of instructions of performing a method of data replication as described herein.
- While several embodiments of the disclosure have been shown in the drawings and/or discussed herein, it is not intended that the disclosure be limited thereto, as it is intended that the disclosure be as broad in scope as the art will allow and that the specification be read likewise. Therefore, the above description should not be construed as limiting, but merely as exemplifications of particular embodiments. The claims can encompass embodiments in hardware, software, or a combination thereof. Those skilled in the art will envision other modifications within the scope and spirit of the claims appended hereto.
Claims (18)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/414,119 US20120221529A1 (en) | 2009-04-10 | 2012-03-07 | Virtual machine data replication |
Applications Claiming Priority (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16831809P | 2009-04-10 | 2009-04-10 | |
US16831509P | 2009-04-10 | 2009-04-10 | |
US17243509P | 2009-04-24 | 2009-04-24 | |
US12/758,371 US8135748B2 (en) | 2009-04-10 | 2010-04-12 | Virtual machine data replication |
US13/414,119 US20120221529A1 (en) | 2009-04-10 | 2012-03-07 | Virtual machine data replication |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/758,371 Continuation US8135748B2 (en) | 2009-04-10 | 2010-04-12 | Virtual machine data replication |
Publications (1)
Publication Number | Publication Date |
---|---|
US20120221529A1 true US20120221529A1 (en) | 2012-08-30 |
Family
ID=42935159
Family Applications (5)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/758,326 Active 2031-02-19 US8682862B2 (en) | 2009-04-10 | 2010-04-12 | Virtual machine file-level restoration |
US12/758,371 Active 2030-09-16 US8135748B2 (en) | 2009-04-10 | 2010-04-12 | Virtual machine data replication |
US12/758,245 Abandoned US20100262797A1 (en) | 2009-04-10 | 2010-04-12 | Virtual machine data backup |
US13/414,119 Abandoned US20120221529A1 (en) | 2009-04-10 | 2012-03-07 | Virtual machine data replication |
US14/215,192 Abandoned US20140201156A1 (en) | 2009-04-10 | 2014-03-17 | Virtual machine file-level restoration |
Family Applications Before (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/758,326 Active 2031-02-19 US8682862B2 (en) | 2009-04-10 | 2010-04-12 | Virtual machine file-level restoration |
US12/758,371 Active 2030-09-16 US8135748B2 (en) | 2009-04-10 | 2010-04-12 | Virtual machine data replication |
US12/758,245 Abandoned US20100262797A1 (en) | 2009-04-10 | 2010-04-12 | Virtual machine data backup |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/215,192 Abandoned US20140201156A1 (en) | 2009-04-10 | 2014-03-17 | Virtual machine file-level restoration |
Country Status (1)
Country | Link |
---|---|
US (5) | US8682862B2 (en) |
Cited By (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20120284559A1 (en) * | 2011-05-02 | 2012-11-08 | International Business Machines Corporation | Coordinated disaster recovery production takeover operations |
US8442952B1 (en) * | 2011-03-30 | 2013-05-14 | Emc Corporation | Recovering in deduplication systems |
CN103761168A (en) * | 2014-01-26 | 2014-04-30 | 上海爱数软件有限公司 | Method for mounting backup virtual machine based on nfs volume |
CN103856503A (en) * | 2012-11-29 | 2014-06-11 | 北京华胜天成科技股份有限公司 | Processing method of file data of NAS cluster system and NAS cluster system |
US8850130B1 (en) | 2011-08-10 | 2014-09-30 | Nutanix, Inc. | Metadata for managing I/O and storage for a virtualization |
US8863124B1 (en) | 2011-08-10 | 2014-10-14 | Nutanix, Inc. | Architecture for managing I/O and storage for a virtualization environment |
US8997097B1 (en) | 2011-08-10 | 2015-03-31 | Nutanix, Inc. | System for implementing a virtual disk in a virtualization environment |
US9009106B1 (en) | 2011-08-10 | 2015-04-14 | Nutanix, Inc. | Method and system for implementing writable snapshots in a virtualized storage environment |
US9262212B2 (en) | 2012-11-02 | 2016-02-16 | The Boeing Company | Systems and methods for migrating virtual machines |
US9354912B1 (en) | 2011-08-10 | 2016-05-31 | Nutanix, Inc. | Method and system for implementing a maintenance service for managing I/O and storage for a virtualization environment |
US9361189B2 (en) | 2011-05-02 | 2016-06-07 | International Business Machines Corporation | Optimizing disaster recovery systems during takeover operations |
CN106339634A (en) * | 2016-08-30 | 2017-01-18 | 中国民生银行股份有限公司 | Data protection method and device of terminal equipment |
US9652265B1 (en) | 2011-08-10 | 2017-05-16 | Nutanix, Inc. | Architecture for managing I/O and storage for a virtualization environment with multiple hypervisor types |
US9747287B1 (en) | 2011-08-10 | 2017-08-29 | Nutanix, Inc. | Method and system for managing metadata for a virtualization environment |
US9772866B1 (en) | 2012-07-17 | 2017-09-26 | Nutanix, Inc. | Architecture for implementing a virtualization environment and appliance |
US9817686B2 (en) | 2014-12-09 | 2017-11-14 | The Boeing Company | Systems and methods for securing virtual machines |
CN109164988A (en) * | 2018-08-30 | 2019-01-08 | 上海交通大学 | Processor-based virtual machine snapshot method and system |
CN110362432A (en) * | 2019-07-23 | 2019-10-22 | 深信服科技股份有限公司 | A kind of backup method, device, equipment and storage medium |
US10467103B1 (en) | 2016-03-25 | 2019-11-05 | Nutanix, Inc. | Efficient change block training |
CN111104392A (en) * | 2019-12-12 | 2020-05-05 | 京东数字科技控股有限公司 | Database migration method and device, electronic equipment and storage medium |
Families Citing this family (162)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101375284B (en) | 2004-10-25 | 2012-02-22 | 安全第一公司 | Secure data parser method and system |
US8285817B1 (en) * | 2006-03-20 | 2012-10-09 | Netapp, Inc. | Migration engine for use in a logical namespace of a storage system environment |
US8060476B1 (en) | 2008-07-14 | 2011-11-15 | Quest Software, Inc. | Backup systems and methods for a virtual computing environment |
US8135930B1 (en) | 2008-07-14 | 2012-03-13 | Vizioncore, Inc. | Replication systems and methods for a virtual computing environment |
US8046550B2 (en) | 2008-07-14 | 2011-10-25 | Quest Software, Inc. | Systems and methods for performing backup operations of virtual machine files |
US8307177B2 (en) | 2008-09-05 | 2012-11-06 | Commvault Systems, Inc. | Systems and methods for management of virtualization data |
US8429649B1 (en) | 2008-09-25 | 2013-04-23 | Quest Software, Inc. | Systems and methods for data management in a virtual computing environment |
WO2010054297A1 (en) * | 2008-11-07 | 2010-05-14 | Compellent Technologies | Thin import for a data storage system |
US8930423B1 (en) * | 2008-12-30 | 2015-01-06 | Symantec Corporation | Method and system for restoring encrypted files from a virtual machine image |
US8996468B1 (en) | 2009-04-17 | 2015-03-31 | Dell Software Inc. | Block status mapping system for reducing virtual machine backup storage |
US8478801B2 (en) * | 2009-05-20 | 2013-07-02 | Vmware, Inc. | Efficient reconstruction of virtual disk hierarchies across storage domains |
JP5227887B2 (en) * | 2009-05-21 | 2013-07-03 | 株式会社日立製作所 | Backup management method |
JP5254141B2 (en) * | 2009-07-14 | 2013-08-07 | 富士通株式会社 | Archive device, data storage program, and data storage method |
US9778946B2 (en) | 2009-08-07 | 2017-10-03 | Dell Software Inc. | Optimized copy of virtual machine storage files |
US8655844B1 (en) | 2009-09-30 | 2014-02-18 | Emc Corporation | File version tracking via signature indices |
US8701193B1 (en) | 2009-09-30 | 2014-04-15 | Emc Corporation | Malware detection via signature indices |
US8326839B2 (en) * | 2009-11-09 | 2012-12-04 | Oracle International Corporation | Efficient file access in a large repository using a two-level cache |
US10210162B1 (en) * | 2010-03-29 | 2019-02-19 | Carbonite, Inc. | Log file management |
US8516023B1 (en) * | 2010-06-03 | 2013-08-20 | Netapp, Inc. | Context based file system |
US11449394B2 (en) | 2010-06-04 | 2022-09-20 | Commvault Systems, Inc. | Failover systems and methods for performing backup operations, including heterogeneous indexing and load balancing of backup and indexing resources |
US9569446B1 (en) | 2010-06-08 | 2017-02-14 | Dell Software Inc. | Cataloging system for image-based backup |
US9507670B2 (en) * | 2010-06-14 | 2016-11-29 | Veeam Software Ag | Selective processing of file system objects for image level backups |
US9244969B1 (en) | 2010-06-30 | 2016-01-26 | Emc Corporation | Virtual disk recovery |
US9497257B1 (en) | 2010-06-30 | 2016-11-15 | EMC IP Holding Company LLC | File level referrals |
US9239860B1 (en) * | 2010-06-30 | 2016-01-19 | Emc Corporation | Augmenting virtual directories |
CN103270516B (en) | 2010-08-18 | 2016-10-12 | 安全第一公司 | System and method for securing virtual machine computing environments |
US8898114B1 (en) | 2010-08-27 | 2014-11-25 | Dell Software Inc. | Multitier deduplication systems and methods |
US9037547B1 (en) * | 2010-09-15 | 2015-05-19 | Symantec Corporation | Backup time deduplication of common virtual disks from virtual machine backup images |
US20120084272A1 (en) * | 2010-10-04 | 2012-04-05 | International Business Machines Corporation | File system support for inert files |
CN102457567B (en) * | 2010-11-08 | 2015-01-21 | 中标软件有限公司 | Mirror image backup/recovery method and tool of web management mode |
US8694685B2 (en) * | 2011-02-25 | 2014-04-08 | International Business Machines Corporation | Migrating virtual machines with adaptive compression |
US8516506B2 (en) * | 2011-03-29 | 2013-08-20 | Denso International America, Inc. | Method and system for restoring an application in a dynamically linked environment |
JP5501280B2 (en) * | 2011-03-31 | 2014-05-21 | 株式会社日立ソリューションズ | Information processing system, backup management method, and program |
US9311328B2 (en) * | 2011-04-22 | 2016-04-12 | Veritas Us Ip Holdings Llc | Reference volume for initial synchronization of a replicated volume group |
US9244933B2 (en) * | 2011-04-29 | 2016-01-26 | International Business Machines Corporation | Disk image introspection for storage systems |
US8745003B1 (en) * | 2011-05-13 | 2014-06-03 | Emc Corporation | Synchronization of storage using comparisons of fingerprints of blocks |
US8782003B1 (en) | 2011-05-13 | 2014-07-15 | Emc Corporation | Synchronization of storage using log files and snapshots |
US8868882B2 (en) | 2011-06-08 | 2014-10-21 | Microsoft Corporation | Storage architecture for backup application |
US8849769B1 (en) * | 2011-06-30 | 2014-09-30 | Emc Corporation | Virtual machine file level recovery |
US9158632B1 (en) | 2011-06-30 | 2015-10-13 | Emc Corporation | Efficient file browsing using key value databases for virtual backups |
US8849777B1 (en) | 2011-06-30 | 2014-09-30 | Emc Corporation | File deletion detection in key value databases for virtual backups |
US8843443B1 (en) | 2011-06-30 | 2014-09-23 | Emc Corporation | Efficient backup of virtual data |
US9311327B1 (en) | 2011-06-30 | 2016-04-12 | Emc Corporation | Updating key value databases for virtual backups |
US8949829B1 (en) | 2011-06-30 | 2015-02-03 | Emc Corporation | Virtual machine disaster recovery |
US9229951B1 (en) | 2011-06-30 | 2016-01-05 | Emc Corporation | Key value databases for virtual backups |
US8930320B2 (en) * | 2011-09-30 | 2015-01-06 | Accenture Global Services Limited | Distributed computing backup and recovery system |
CN103186570B (en) * | 2011-12-28 | 2017-08-18 | 富泰华工业(深圳)有限公司 | Data source query system and method based on cloud server |
WO2013102227A1 (en) * | 2011-12-29 | 2013-07-04 | Vmware, Inc. | N-way synchronization of desktop images |
US8893147B2 (en) | 2012-01-13 | 2014-11-18 | Ca, Inc. | Providing a virtualized replication and high availability environment including a replication and high availability engine |
US9311375B1 (en) | 2012-02-07 | 2016-04-12 | Dell Software Inc. | Systems and methods for compacting a virtual machine file |
US9280380B2 (en) * | 2012-02-29 | 2016-03-08 | Red Hat Israel, Ltd. | Management of I/O reqeusts in virtual machine migration |
US9417811B2 (en) | 2012-03-07 | 2016-08-16 | International Business Machines Corporation | Efficient inline data de-duplication on a storage system |
US8930747B2 (en) | 2012-03-30 | 2015-01-06 | Sungard Availability Services, Lp | Private cloud replication and recovery |
US9628438B2 (en) | 2012-04-06 | 2017-04-18 | Exablox | Consistent ring namespaces facilitating data storage and organization in network infrastructures |
US20130268774A1 (en) * | 2012-04-06 | 2013-10-10 | Security First Corp. | Systems and methods for securing and restoring virtual machines |
US8776236B2 (en) * | 2012-04-11 | 2014-07-08 | Northrop Grumman Systems Corporation | System and method for providing storage device-based advanced persistent threat (APT) protection |
US8839031B2 (en) | 2012-04-24 | 2014-09-16 | Microsoft Corporation | Data consistency between virtual machines |
US8930751B2 (en) | 2012-04-24 | 2015-01-06 | Microsoft Corporation | Initializing replication in a virtual machine |
US9646020B2 (en) * | 2012-05-02 | 2017-05-09 | Microsoft Technology Licensing, Llc | Integrated format conversion during disk upload |
US8977828B2 (en) | 2012-06-21 | 2015-03-10 | Ca, Inc. | Data recovery using conversion of backup to virtual disk |
US8850146B1 (en) | 2012-07-27 | 2014-09-30 | Symantec Corporation | Backup of a virtual machine configured to perform I/O operations bypassing a hypervisor |
US8938481B2 (en) * | 2012-08-13 | 2015-01-20 | Commvault Systems, Inc. | Generic file level restore from a block-level secondary copy |
JP2014044553A (en) * | 2012-08-27 | 2014-03-13 | Fujitsu Ltd | Program, information processing device, and information processing system |
US9697093B2 (en) | 2012-09-05 | 2017-07-04 | Veritas Technologies Llc | Techniques for recovering a virtual machine |
US9323759B1 (en) * | 2012-09-28 | 2016-04-26 | Emc Corporation | Multiprocess divided file system backup |
US9465927B2 (en) * | 2012-10-02 | 2016-10-11 | Disney Enterprises, Inc. | Validating input by detecting and recognizing human presence |
US9032248B1 (en) * | 2012-10-04 | 2015-05-12 | Amazon Technologies, Inc. | Memory write tracking for virtual machines |
US9354907B1 (en) | 2012-10-26 | 2016-05-31 | Veritas Technologies Llc | Optimized restore of virtual machine and virtual disk data |
US9092161B2 (en) * | 2012-12-05 | 2015-07-28 | Red Hat Israel, Ltd. | Selection of allocation policy and format for virtual machine disk images |
US9223597B2 (en) | 2012-12-21 | 2015-12-29 | Commvault Systems, Inc. | Archiving virtual machines in a data storage system |
US20140181038A1 (en) | 2012-12-21 | 2014-06-26 | Commvault Systems, Inc. | Systems and methods to categorize unprotected virtual machines |
US20140196039A1 (en) | 2013-01-08 | 2014-07-10 | Commvault Systems, Inc. | Virtual machine categorization system and method |
US20140201151A1 (en) | 2013-01-11 | 2014-07-17 | Commvault Systems, Inc. | Systems and methods to select files for restoration from block-level backup for virtual machines |
US9286110B2 (en) * | 2013-01-14 | 2016-03-15 | Commvault Systems, Inc. | Seamless virtual machine recall in a data storage system |
US20140317411A1 (en) * | 2013-04-18 | 2014-10-23 | Intronis, Inc. | Deduplication of data |
US9552382B2 (en) | 2013-04-23 | 2017-01-24 | Exablox Corporation | Reference counter integrity checking |
CN104216793B (en) * | 2013-05-31 | 2017-10-17 | 国际商业机器公司 | Application Backup, the method and apparatus recovered |
EP3008647A4 (en) | 2013-06-12 | 2017-01-25 | Exablox Corporation | Hybrid garbage collection |
WO2014205286A1 (en) * | 2013-06-19 | 2014-12-24 | Exablox Corporation | Data scrubbing in cluster-based storage systems |
US20140380242A1 (en) * | 2013-06-24 | 2014-12-25 | International Business Machines Corporation | Displaying data protection levels |
US9454549B1 (en) | 2013-06-28 | 2016-09-27 | Emc Corporation | Metadata reconciliation |
US9424056B1 (en) * | 2013-06-28 | 2016-08-23 | Emc Corporation | Cross site recovery of a VM |
US9934242B2 (en) | 2013-07-10 | 2018-04-03 | Exablox Corporation | Replication of data between mirrored data sites |
US9354908B2 (en) | 2013-07-17 | 2016-05-31 | Veritas Technologies, LLC | Instantly restoring virtual machines by providing read/write access to virtual disk before the virtual disk is completely restored |
US9965490B2 (en) * | 2013-07-31 | 2018-05-08 | Oracle International Corporation | Method and system for creating a virtual file system from a unified archive |
US9710386B1 (en) | 2013-08-07 | 2017-07-18 | Veritas Technologies | Systems and methods for prefetching subsequent data segments in response to determining that requests for data originate from a sequential-access computing job |
US9092248B1 (en) | 2013-08-21 | 2015-07-28 | Symantec Corporation | Systems and methods for restoring distributed applications within virtual data centers |
US9858154B1 (en) * | 2013-08-23 | 2018-01-02 | Acronis International Gmbh | Agentless file backup of a virtual machine |
US20150074536A1 (en) | 2013-09-12 | 2015-03-12 | Commvault Systems, Inc. | File manager integration with virtualization in an information management system, including user control and storage management of virtual machines |
US20150106334A1 (en) * | 2013-10-15 | 2015-04-16 | PHD Virtual Technologies | Systems and methods for backing up a live virtual machine |
US10248556B2 (en) | 2013-10-16 | 2019-04-02 | Exablox Corporation | Forward-only paged data storage management where virtual cursor moves in only one direction from header of a session to data field of the session |
US9367562B2 (en) * | 2013-12-05 | 2016-06-14 | Google Inc. | Distributing data on distributed storage systems |
US9985829B2 (en) | 2013-12-12 | 2018-05-29 | Exablox Corporation | Management and provisioning of cloud connected devices |
US9774582B2 (en) | 2014-02-03 | 2017-09-26 | Exablox Corporation | Private cloud connected device cluster architecture |
WO2015120071A2 (en) | 2014-02-04 | 2015-08-13 | Exablox Corporation | Content based organization of file systems |
US9542404B2 (en) * | 2014-02-17 | 2017-01-10 | Netapp, Inc. | Subpartitioning of a namespace region |
US10169121B2 (en) | 2014-02-27 | 2019-01-01 | Commvault Systems, Inc. | Work flow management for an information management system |
US9811427B2 (en) | 2014-04-02 | 2017-11-07 | Commvault Systems, Inc. | Information management by a media agent in the absence of communications with a storage manager |
US9396071B1 (en) * | 2014-06-11 | 2016-07-19 | Emc Corporation | System and method for presenting virtual machine (VM) backup information from multiple backup servers |
US9563520B2 (en) * | 2014-07-11 | 2017-02-07 | Quantum Corporation | File level recovery using virtual machine image level backup with selective compression |
US20160019317A1 (en) | 2014-07-16 | 2016-01-21 | Commvault Systems, Inc. | Volume or virtual machine level backup and generating placeholders for virtual machine files |
US11249858B2 (en) | 2014-08-06 | 2022-02-15 | Commvault Systems, Inc. | Point-in-time backups of a production application made accessible over fibre channel and/or ISCSI as data sources to a remote application by representing the backups as pseudo-disks operating apart from the production application and its host |
US9852026B2 (en) | 2014-08-06 | 2017-12-26 | Commvault Systems, Inc. | Efficient application recovery in an information management system based on a pseudo-storage-device driver |
US10360110B2 (en) | 2014-08-06 | 2019-07-23 | Commvault Systems, Inc. | Point-in-time backups of a production application made accessible over fibre channel and/or iSCSI as data sources to a remote application by representing the backups as pseudo-disks operating apart from the production application and its host |
US10565159B2 (en) | 2014-08-12 | 2020-02-18 | International Business Machines Corporation | Archiving data sets in a volume in a primary storage in a volume image copy of the volume in a secondary storage |
US9417968B2 (en) | 2014-09-22 | 2016-08-16 | Commvault Systems, Inc. | Efficiently restoring execution of a backed up virtual machine based on coordination with virtual-machine-file-relocation operations |
US9710465B2 (en) | 2014-09-22 | 2017-07-18 | Commvault Systems, Inc. | Efficiently restoring execution of a backed up virtual machine based on coordination with virtual-machine-file-relocation operations |
US9436555B2 (en) | 2014-09-22 | 2016-09-06 | Commvault Systems, Inc. | Efficient live-mount of a backed up virtual machine in a storage management system |
US10776209B2 (en) | 2014-11-10 | 2020-09-15 | Commvault Systems, Inc. | Cross-platform virtual machine backup and replication |
US9983936B2 (en) | 2014-11-20 | 2018-05-29 | Commvault Systems, Inc. | Virtual machine change block tracking |
US9430272B2 (en) | 2014-12-17 | 2016-08-30 | Microsoft Technology Licensing, Llc | Efficiently providing virtual machine reference points |
US9547555B2 (en) | 2015-01-12 | 2017-01-17 | Microsoft Technology Licensing, Llc | Change tracking using redundancy in logical time |
US10078555B1 (en) * | 2015-04-14 | 2018-09-18 | EMC IP Holding Company LLC | Synthetic full backups for incremental file backups |
US10168947B2 (en) * | 2015-05-07 | 2019-01-01 | Vmware, Inc. | Virtual file system with vnode reconstruction capability |
US10284433B2 (en) * | 2015-06-25 | 2019-05-07 | International Business Machines Corporation | Data synchronization using redundancy detection |
US20160378452A1 (en) * | 2015-06-29 | 2016-12-29 | Mediatek Inc. | Policy-Based Compression of Machine Code Generated by a Virtual Machine |
US10705917B2 (en) * | 2015-06-30 | 2020-07-07 | Veritas Technologies Llc | Consolidated full backup of a restored virtual machine |
US9766825B2 (en) | 2015-07-22 | 2017-09-19 | Commvault Systems, Inc. | Browse and restore for block-level backups |
US10474654B2 (en) | 2015-08-26 | 2019-11-12 | Storagecraft Technology Corporation | Structural data transfer over a network |
US10157103B2 (en) | 2015-10-20 | 2018-12-18 | Veeam Software Ag | Efficient processing of file system objects for image level backups |
US10467153B2 (en) | 2015-12-31 | 2019-11-05 | Razer (Asia-Pacific) Pte. Ltd. | Methods for controlling a computing device, computer-readable media, and computing devices |
US10296368B2 (en) | 2016-03-09 | 2019-05-21 | Commvault Systems, Inc. | Hypervisor-independent block-level live browse for access to backed up virtual machine (VM) data and hypervisor-free file-level recovery (block-level pseudo-mount) |
US10565067B2 (en) | 2016-03-09 | 2020-02-18 | Commvault Systems, Inc. | Virtual server cloud file system for virtual machine backup from cloud operations |
US9846553B2 (en) | 2016-05-04 | 2017-12-19 | Exablox Corporation | Organization and management of key-value stores |
CN106202173B (en) * | 2016-06-26 | 2019-11-12 | 厦门天锐科技股份有限公司 | A kind of intelligent rearrangement and system of file repository storage |
US11281624B1 (en) * | 2016-09-28 | 2022-03-22 | Amazon Technologies, Inc. | Client-based batching of data payload |
US11204895B1 (en) | 2016-09-28 | 2021-12-21 | Amazon Technologies, Inc. | Data payload clustering for data storage systems |
US10747630B2 (en) | 2016-09-30 | 2020-08-18 | Commvault Systems, Inc. | Heartbeat monitoring of virtual machines for initiating failover operations in a data storage management system, including operations by a master monitor node |
US10162528B2 (en) | 2016-10-25 | 2018-12-25 | Commvault Systems, Inc. | Targeted snapshot based on virtual machine location |
US10152251B2 (en) | 2016-10-25 | 2018-12-11 | Commvault Systems, Inc. | Targeted backup of virtual machine |
US10678758B2 (en) | 2016-11-21 | 2020-06-09 | Commvault Systems, Inc. | Cross-platform virtual machine data and memory backup and replication |
US10409988B2 (en) | 2017-01-20 | 2019-09-10 | Hewlett Packard Enterprise Development Lp | Escalated remediation |
US10942893B2 (en) * | 2017-01-30 | 2021-03-09 | Walmart Apollo, Llc | Systems and methods for a specialized computer file system |
US10740193B2 (en) | 2017-02-27 | 2020-08-11 | Commvault Systems, Inc. | Hypervisor-independent reference copies of virtual machine payload data based on block-level pseudo-mount |
US10331528B2 (en) | 2017-03-02 | 2019-06-25 | Hewlett Packard Enterprise Development Lp | Recovery services for computing systems |
US20180276085A1 (en) | 2017-03-24 | 2018-09-27 | Commvault Systems, Inc. | Virtual machine recovery point generation |
US10387073B2 (en) | 2017-03-29 | 2019-08-20 | Commvault Systems, Inc. | External dynamic virtual machine synchronization |
CN107273183A (en) * | 2017-06-12 | 2017-10-20 | 上海优刻得信息科技有限公司 | Disk bleach-out process, device, system and the server of loaded virtual machine mirror image |
US10664352B2 (en) | 2017-06-14 | 2020-05-26 | Commvault Systems, Inc. | Live browsing of backed up data residing on cloned disks |
US10776197B1 (en) * | 2017-06-27 | 2020-09-15 | EMC IP Holding Company LLC | Detect and triage data integrity issue for virtual machine |
CN108052342A (en) * | 2017-12-12 | 2018-05-18 | 杭州华为数字技术有限公司 | Partition table restorative procedure, device and electronic equipment |
US10877928B2 (en) | 2018-03-07 | 2020-12-29 | Commvault Systems, Inc. | Using utilities injected into cloud-based virtual machines for speeding up virtual machine backup operations |
US10936442B2 (en) * | 2018-07-06 | 2021-03-02 | EMC IP Holding Company LLC | Simultaneous file level recovery from multiple backups using a proxy virtual machine |
US11200124B2 (en) | 2018-12-06 | 2021-12-14 | Commvault Systems, Inc. | Assigning backup resources based on failover of partnered data storage servers in a data storage management system |
US11347707B2 (en) | 2019-01-22 | 2022-05-31 | Commvault Systems, Inc. | File indexing for virtual machine backups based on using live browse features |
US10872069B2 (en) * | 2019-01-22 | 2020-12-22 | Commvault Systems, Inc. | File indexing for virtual machine backups in a data storage management system |
US10996974B2 (en) | 2019-01-30 | 2021-05-04 | Commvault Systems, Inc. | Cross-hypervisor live mount of backed up virtual machine data, including management of cache storage for virtual machine data |
US10768971B2 (en) | 2019-01-30 | 2020-09-08 | Commvault Systems, Inc. | Cross-hypervisor live mount of backed up virtual machine data |
US11625304B2 (en) * | 2019-04-26 | 2023-04-11 | EMC IP Holding Company LLC | Efficient method to find changed data between indexed data and new backup |
US11249791B2 (en) | 2019-04-30 | 2022-02-15 | Acronis International Gmbh | System and method of selectively restoring a computer system to an operational state |
CN112925750A (en) * | 2019-12-06 | 2021-06-08 | 伊姆西Ip控股有限责任公司 | Method, electronic device and computer program product for accessing data |
US11467753B2 (en) | 2020-02-14 | 2022-10-11 | Commvault Systems, Inc. | On-demand restore of virtual machine data |
US11442768B2 (en) | 2020-03-12 | 2022-09-13 | Commvault Systems, Inc. | Cross-hypervisor live recovery of virtual machines |
US11099956B1 (en) | 2020-03-26 | 2021-08-24 | Commvault Systems, Inc. | Snapshot-based disaster recovery orchestration of virtual machine failover and failback operations |
JP7100085B2 (en) * | 2020-05-12 | 2022-07-12 | 株式会社日立製作所 | Security system, host system and backup method |
US11748143B2 (en) | 2020-05-15 | 2023-09-05 | Commvault Systems, Inc. | Live mount of virtual machines in a public cloud computing environment |
US11656951B2 (en) | 2020-10-28 | 2023-05-23 | Commvault Systems, Inc. | Data loss vulnerability detection |
CN112395132A (en) * | 2020-11-13 | 2021-02-23 | 苏州元核云技术有限公司 | Method, system and computer storage medium for file backup |
CN112612576B (en) * | 2020-12-23 | 2022-08-30 | 新华三大数据技术有限公司 | Virtual machine backup method and device, electronic equipment and storage medium |
US20220342773A1 (en) * | 2021-04-21 | 2022-10-27 | EMC IP Holding Company LLC | Globally unique way to identify a resource |
CN114629924B (en) * | 2022-04-13 | 2024-02-13 | 北京赛博云睿智能科技有限公司 | Method for synchronous operation of service data by container |
CN115348005A (en) * | 2022-08-11 | 2022-11-15 | 北京特纳飞电子技术有限公司 | Apparatus and method for data processing |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20080250085A1 (en) * | 2007-04-09 | 2008-10-09 | Microsoft Corporation | Backup system having preinstalled backup data |
Family Cites Families (34)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6959384B1 (en) * | 1999-12-14 | 2005-10-25 | Intertrust Technologies Corporation | Systems and methods for authenticating and protecting the integrity of data streams and other data |
CN1411580A (en) * | 2000-01-10 | 2003-04-16 | 连接公司 | Administration of differential backup system in client-server environment |
AU2001265075A1 (en) * | 2000-05-26 | 2001-12-11 | Infolibria, Inc. | High performance efficient subsystem for data object storage |
US20020147735A1 (en) * | 2000-11-22 | 2002-10-10 | Intra Inc. | Method and system for optimizing file loading in a data communication network |
US6871271B2 (en) * | 2000-12-21 | 2005-03-22 | Emc Corporation | Incrementally restoring a mass storage device to a prior state |
US7043637B2 (en) * | 2001-03-21 | 2006-05-09 | Microsoft Corporation | On-disk file format for a serverless distributed file system |
US6912645B2 (en) * | 2001-07-19 | 2005-06-28 | Lucent Technologies Inc. | Method and apparatus for archival data storage |
US6745192B1 (en) * | 2001-08-03 | 2004-06-01 | Networks Associates Technology Inc. | System and method for providing a multi-tiered hierarchical transient message store accessed using multiply hashed unique filenames |
US7134041B2 (en) | 2001-09-20 | 2006-11-07 | Evault, Inc. | Systems and methods for data backup over a network |
US6948039B2 (en) * | 2001-12-14 | 2005-09-20 | Voom Technologies, Inc. | Data backup and restoration using dynamic virtual storage |
US7152078B2 (en) * | 2001-12-27 | 2006-12-19 | Hitachi, Ltd. | Systems, methods and computer program products for backup and restoring storage volumes in a storage area network |
US7093086B1 (en) | 2002-03-28 | 2006-08-15 | Veritas Operating Corporation | Disaster recovery and backup using virtual machines |
US6865655B1 (en) * | 2002-07-30 | 2005-03-08 | Sun Microsystems, Inc. | Methods and apparatus for backing up and restoring data portions stored in client computer systems |
JP4777651B2 (en) * | 2002-08-23 | 2011-09-21 | イグジット−キューブ,インク. | Computer system and data storage method |
US20040078641A1 (en) * | 2002-09-23 | 2004-04-22 | Hewlett-Packard Company | Operating system-independent file restore from disk image |
US7620786B2 (en) * | 2003-09-12 | 2009-11-17 | Lsi Corporation | Storage recovery using a delta log |
CA2543746C (en) * | 2003-10-27 | 2018-01-16 | Archivas, Inc. | Policy-based management of a redundant array of independent nodes |
US7555732B2 (en) * | 2004-03-12 | 2009-06-30 | Steven Van der Hoeven | Apparatus method and system for a data entry interface |
JP2005301497A (en) * | 2004-04-08 | 2005-10-27 | Hitachi Ltd | Storage management system, restoration method and its program |
US7657581B2 (en) * | 2004-07-29 | 2010-02-02 | Archivas, Inc. | Metadata management for fixed content distributed data storage |
US7284150B2 (en) * | 2004-09-22 | 2007-10-16 | International Business Machines Corporation | System and method for reliably storing data and providing efficient incremental backup and asynchronous mirroring by preferentially handling new data |
US7756833B2 (en) * | 2004-09-22 | 2010-07-13 | Microsoft Corporation | Method and system for synthetic backup and restore |
US7873782B2 (en) * | 2004-11-05 | 2011-01-18 | Data Robotics, Inc. | Filesystem-aware block storage system, apparatus, and method |
US8959299B2 (en) * | 2004-11-15 | 2015-02-17 | Commvault Systems, Inc. | Using a snapshot as a data source |
US7366859B2 (en) | 2005-10-06 | 2008-04-29 | Acronis Inc. | Fast incremental backup method and system |
US20070208918A1 (en) | 2006-03-01 | 2007-09-06 | Kenneth Harbin | Method and apparatus for providing virtual machine backup |
US20080104146A1 (en) * | 2006-10-31 | 2008-05-01 | Rebit, Inc. | System for automatically shadowing encrypted data and file directory structures for a plurality of network-connected computers using a network-attached memory with single instance storage |
US7917469B2 (en) * | 2006-11-08 | 2011-03-29 | Hitachi Data Systems Corporation | Fast primary cluster recovery |
US8117409B2 (en) * | 2006-11-22 | 2012-02-14 | Hitachi, Ltd. | Method and apparatus for backup and restore in a dynamic chunk allocation storage system |
US7856437B2 (en) * | 2007-07-31 | 2010-12-21 | Hewlett-Packard Development Company, L.P. | Storing nodes representing respective chunks of files in a data store |
TWI476610B (en) * | 2008-04-29 | 2015-03-11 | Maxiscale Inc | Peer-to-peer redundant file server system and methods |
US8060476B1 (en) * | 2008-07-14 | 2011-11-15 | Quest Software, Inc. | Backup systems and methods for a virtual computing environment |
US8037032B2 (en) * | 2008-08-25 | 2011-10-11 | Vmware, Inc. | Managing backups using virtual machines |
WO2010036889A1 (en) * | 2008-09-25 | 2010-04-01 | Bakbone Software, Inc. | Remote backup and restore |
-
2010
- 2010-04-12 US US12/758,326 patent/US8682862B2/en active Active
- 2010-04-12 US US12/758,371 patent/US8135748B2/en active Active
- 2010-04-12 US US12/758,245 patent/US20100262797A1/en not_active Abandoned
-
2012
- 2012-03-07 US US13/414,119 patent/US20120221529A1/en not_active Abandoned
-
2014
- 2014-03-17 US US14/215,192 patent/US20140201156A1/en not_active Abandoned
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20080250085A1 (en) * | 2007-04-09 | 2008-10-09 | Microsoft Corporation | Backup system having preinstalled backup data |
Cited By (40)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8442952B1 (en) * | 2011-03-30 | 2013-05-14 | Emc Corporation | Recovering in deduplication systems |
US9361189B2 (en) | 2011-05-02 | 2016-06-07 | International Business Machines Corporation | Optimizing disaster recovery systems during takeover operations |
US20120284556A1 (en) * | 2011-05-02 | 2012-11-08 | International Business Machines Corporation | Coordinated disaster recovery production takeover operations |
US8522068B2 (en) * | 2011-05-02 | 2013-08-27 | International Business Machines Corporation | Coordinated disaster recovery production takeover operations |
US8549348B2 (en) * | 2011-05-02 | 2013-10-01 | International Business Machines Corporation | Coordinated disaster recovery production takeover operations |
US9983964B2 (en) | 2011-05-02 | 2018-05-29 | International Business Machines Corporation | Optimizing disaster recovery systems during takeover operations |
US20120284559A1 (en) * | 2011-05-02 | 2012-11-08 | International Business Machines Corporation | Coordinated disaster recovery production takeover operations |
US9575784B1 (en) | 2011-08-10 | 2017-02-21 | Nutanix, Inc. | Method and system for handling storage in response to migration of a virtual machine in a virtualization environment |
US9747287B1 (en) | 2011-08-10 | 2017-08-29 | Nutanix, Inc. | Method and system for managing metadata for a virtualization environment |
US8997097B1 (en) | 2011-08-10 | 2015-03-31 | Nutanix, Inc. | System for implementing a virtual disk in a virtualization environment |
US9009106B1 (en) | 2011-08-10 | 2015-04-14 | Nutanix, Inc. | Method and system for implementing writable snapshots in a virtualized storage environment |
US9052936B1 (en) | 2011-08-10 | 2015-06-09 | Nutanix, Inc. | Method and system for communicating to a storage controller in a virtualization environment |
US9256475B1 (en) | 2011-08-10 | 2016-02-09 | Nutanix, Inc. | Method and system for handling ownership transfer in a virtualization environment |
US9256374B1 (en) | 2011-08-10 | 2016-02-09 | Nutanix, Inc. | Metadata for managing I/O and storage for a virtualization environment |
US9256456B1 (en) | 2011-08-10 | 2016-02-09 | Nutanix, Inc. | Architecture for managing I/O and storage for a virtualization environment |
US11853780B2 (en) | 2011-08-10 | 2023-12-26 | Nutanix, Inc. | Architecture for managing I/O and storage for a virtualization environment |
US9354912B1 (en) | 2011-08-10 | 2016-05-31 | Nutanix, Inc. | Method and system for implementing a maintenance service for managing I/O and storage for a virtualization environment |
US8850130B1 (en) | 2011-08-10 | 2014-09-30 | Nutanix, Inc. | Metadata for managing I/O and storage for a virtualization |
US9389887B1 (en) * | 2011-08-10 | 2016-07-12 | Nutanix, Inc. | Method and system for managing de-duplication of data in a virtualization environment |
US11314421B2 (en) | 2011-08-10 | 2022-04-26 | Nutanix, Inc. | Method and system for implementing writable snapshots in a virtualized storage environment |
US11301274B2 (en) | 2011-08-10 | 2022-04-12 | Nutanix, Inc. | Architecture for managing I/O and storage for a virtualization environment |
US9619257B1 (en) | 2011-08-10 | 2017-04-11 | Nutanix, Inc. | System and method for implementing storage for a virtualization environment |
US9652265B1 (en) | 2011-08-10 | 2017-05-16 | Nutanix, Inc. | Architecture for managing I/O and storage for a virtualization environment with multiple hypervisor types |
US10359952B1 (en) | 2011-08-10 | 2019-07-23 | Nutanix, Inc. | Method and system for implementing writable snapshots in a virtualized storage environment |
US8863124B1 (en) | 2011-08-10 | 2014-10-14 | Nutanix, Inc. | Architecture for managing I/O and storage for a virtualization environment |
US10747570B2 (en) | 2012-07-17 | 2020-08-18 | Nutanix, Inc. | Architecture for implementing a virtualization environment and appliance |
US11314543B2 (en) | 2012-07-17 | 2022-04-26 | Nutanix, Inc. | Architecture for implementing a virtualization environment and appliance |
US9772866B1 (en) | 2012-07-17 | 2017-09-26 | Nutanix, Inc. | Architecture for implementing a virtualization environment and appliance |
US10684879B2 (en) | 2012-07-17 | 2020-06-16 | Nutanix, Inc. | Architecture for implementing a virtualization environment and appliance |
US9262212B2 (en) | 2012-11-02 | 2016-02-16 | The Boeing Company | Systems and methods for migrating virtual machines |
CN103856503A (en) * | 2012-11-29 | 2014-06-11 | 北京华胜天成科技股份有限公司 | Processing method of file data of NAS cluster system and NAS cluster system |
CN103761168A (en) * | 2014-01-26 | 2014-04-30 | 上海爱数软件有限公司 | Method for mounting backup virtual machine based on nfs volume |
CN103761168B (en) * | 2014-01-26 | 2017-06-13 | 上海爱数信息技术股份有限公司 | It is a kind of that the method for carrying backup virtual machine is wrapping with based on nfs |
US9817686B2 (en) | 2014-12-09 | 2017-11-14 | The Boeing Company | Systems and methods for securing virtual machines |
US10558484B2 (en) | 2014-12-09 | 2020-02-11 | The Boeing Company | Systems and methods for securing virtual machines |
US10467103B1 (en) | 2016-03-25 | 2019-11-05 | Nutanix, Inc. | Efficient change block training |
CN106339634A (en) * | 2016-08-30 | 2017-01-18 | 中国民生银行股份有限公司 | Data protection method and device of terminal equipment |
CN109164988A (en) * | 2018-08-30 | 2019-01-08 | 上海交通大学 | Processor-based virtual machine snapshot method and system |
CN110362432A (en) * | 2019-07-23 | 2019-10-22 | 深信服科技股份有限公司 | A kind of backup method, device, equipment and storage medium |
CN111104392A (en) * | 2019-12-12 | 2020-05-05 | 京东数字科技控股有限公司 | Database migration method and device, electronic equipment and storage medium |
Also Published As
Publication number | Publication date |
---|---|
US20100262585A1 (en) | 2010-10-14 |
US20140201156A1 (en) | 2014-07-17 |
US8682862B2 (en) | 2014-03-25 |
US8135748B2 (en) | 2012-03-13 |
US20100262586A1 (en) | 2010-10-14 |
US20100262797A1 (en) | 2010-10-14 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8135748B2 (en) | Virtual machine data replication | |
US11947809B2 (en) | Data management system | |
US9348702B2 (en) | System and method for incremental virtual machine backup using storage system functionality | |
US9946603B1 (en) | Mountable container for incremental file backups | |
US9740565B1 (en) | System and method for maintaining consistent points in file systems | |
US8924354B2 (en) | Block level data replication | |
US8117410B2 (en) | Tracking block-level changes using snapshots | |
US9996429B1 (en) | Mountable container backups for files | |
EP2013974B1 (en) | Data compression and storage techniques | |
US8315985B1 (en) | Optimizing the de-duplication rate for a backup stream | |
US20140040192A1 (en) | Seeding replication | |
EP2691847B1 (en) | System and method for maintaining consistent points in file systems using a prime dependency list | |
US10210169B2 (en) | System and method for verifying consistent points in file systems | |
US10078555B1 (en) | Synthetic full backups for incremental file backups | |
US11372726B2 (en) | Method and system for adaptive incrementally updated backups with dynamic data file detection | |
US11580015B2 (en) | Garbage collection for a deduplicated cloud tier using functions | |
US20240061749A1 (en) | Consolidating snapshots using partitioned patch files | |
US11513907B2 (en) | Method and system for resuming interrupted database backup operations using checkpoints | |
US11360699B1 (en) | Method and system for improved write performance in erasure-coded storage systems | |
CN113728302B (en) | Cloud layered garbage collection for de-duplication | |
US11593215B2 (en) | Method and system for generating immutable backups with configurable retention spans | |
US11599559B2 (en) | Cloud image replication of client devices | |
Osuna et al. | Implementing IBM storage data deduplication solutions |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: PHD VIRTUAL TECHNOLOGIES, PENNSYLVANIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ROSIKIEWICZ, JAMES;MCKELVEY, RONALD T;MITTELL, ALEXANDER D;REEL/FRAME:027821/0414 Effective date: 20100409 |
|
AS | Assignment |
Owner name: SILICON VALLEY BANK, CALIFORNIA Free format text: SECURITY AGREEMENT;ASSIGNOR:PHD VIRTUAL TECHNOLOGIES INC.;REEL/FRAME:029877/0619 Effective date: 20130213 |
|
AS | Assignment |
Owner name: WF FUND IV LIMITED PARTNERSHIP (C/O/B AS WELLINGTO Free format text: SECURITY AGREEMENT;ASSIGNOR:PHD VIRTUAL TECHNOLOGIES, INC.;REEL/FRAME:029940/0143 Effective date: 20130306 |
|
AS | Assignment |
Owner name: PHD VIRTUAL TECHNOLOGIES, INC., PENNSYLVANIA Free format text: RELEASE OF SECURITY INTEREST;ASSIGNOR:SILICON VALLEY BANK;REEL/FRAME:032448/0563 Effective date: 20131205 |
|
AS | Assignment |
Owner name: PHD VIRTUAL TECHNOLOGIES, INC., PENNSYLVANIA Free format text: RELEASE OF SECURITY INTEREST;ASSIGNOR:WF FUND IV LIMITED PARTNERSHIP (C/O/B WELLINGTON FINANCIAL LP AND WELLINGTON FINANCIAL FUND IV);REEL/FRAME:032482/0116 Effective date: 20140319 |
|
AS | Assignment |
Owner name: SQUARE 1 BANK, NORTH CAROLINA Free format text: SECURITY INTEREST;ASSIGNOR:PHD VIRTUAL TECHNOLOGIES INC.;REEL/FRAME:032507/0091 Effective date: 20140319 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |
|
AS | Assignment |
Owner name: UNITRENDS, INC., SOUTH CAROLINA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:PACIFIC WESTERN BANK, AS SUCCESSOR IN INTEREST TO SQUARE 1 BANK;REEL/FRAME:044713/0081 Effective date: 20180119 |
|
AS | Assignment |
Owner name: DATTO, LLC, CONNECTICUT Free format text: CHANGE OF NAME;ASSIGNOR:DATTO, INC.;REEL/FRAME:065385/0256 Effective date: 20230804 |