US8555278B2 - Method and system for migrating a selected set of virtual machines between volumes - Google Patents
Method and system for migrating a selected set of virtual machines between volumes Download PDFInfo
- Publication number
- US8555278B2 US8555278B2 US13/099,247 US201113099247A US8555278B2 US 8555278 B2 US8555278 B2 US 8555278B2 US 201113099247 A US201113099247 A US 201113099247A US 8555278 B2 US8555278 B2 US 8555278B2
- Authority
- US
- United States
- Prior art keywords
- volume
- virtual machines
- migrating
- virtual
- file system
- 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.)
- Active, expires
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0646—Horizontal data movement in storage systems, i.e. moving data in between storage devices or systems
- G06F3/0647—Migration mechanisms
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
- G06F3/0604—Improving or facilitating administration, e.g. storage management
- G06F3/0607—Improving or facilitating administration, e.g. storage management by facilitating the process of upgrading existing storage systems, e.g. for improving compatibility between host and storage device
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
- G06F3/067—Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
Definitions
- the present invention is generally related to digital computer, more particularly, to a system and method for periodically replicating data in volumes.
- Replication technology is primarily used for disaster recovery and data distribution.
- Continuous replication technology often includes RAID based replication schemes (e.g., disk mirroring, parity, or the like).
- Continuous replication maintains copies of the data as the data is being written to by applications.
- Periodic replication is another technique utilized to minimize data loss and improve the availability of data in which a point-in-time copy of data is replicated and stored at one or more remote sites or nodes. In the event of a site migration, failure of one or more physical disks storing data, or failure of a node or host data processing system associated with such a disk, the remote replicated data copy may be utilized.
- the replicated data enables a number of other uses, such as, for example, data mining, reporting, testing, and the like.
- the replicated data copy ensures data integrity and availability.
- replication technology is frequently coupled with other high-availability techniques, such as clustering, to provide an extremely robust data storage solution.
- Data storage required for applications such as file systems and databases are typically allocated from one or more storage devices that are maintained as a “volume.”
- the “volume” may serve as a logical interface used by an operating system to access data stored on one or more storage media using a single instance of a file system.
- a volume may act as an abstraction that essentially “hides” storage allocation and (optionally) data protection/redundancy from the application.
- An application can store its data on multiple volumes. The content of a volume is accessed using fixed sized data units called blocks.
- the data is distributed in number of data servers.
- the clients directly write data to the data servers with minimal points of interaction with any metadata server.
- the data servers typically have multiple LUNs (logical unit numbers) which have their own reserved storage space. Each LUN can have a large number of partitions, with the objects contained in these partitions.
- the files of distributed computer system file system are composed of the objects from any of the data server LUN partitions.
- the objects from various data servers are combined to form RAID groups.
- VHD In a virtual environment such as Hyper-V, performance of the virtual disk is best when fixed VHD is used as compared to dynamic VHD.
- Fixed VHD allocates all blocks in the file system when the VHD is created. Therefore, for example, a 24 GB fixed VHD will create a file that is about 24 GB. This is different from dynamic VHD which, for example, only allocates enough storage to store data that is actually written to the VHD.
- a 24 GB dynamic VHD may only occupy a few MB when it's created.
- Fixed VHD is good for performance, but it presents a challenge for an optimized replication process, where file system information is used to reduce the amount of data to be copied when a new mirror is added to a volume.
- Embodiments of the present invention provide a solution that enables an efficient, highly available, and highly scalable process for the replication of data for a distributed computer system including one or more virtual machines.
- Embodiments of the present invention implement an optimized scheme that can look into individual VHD files thru the file systems they host to truly eliminate copying white spaces.
- a method for migrating a selected set of virtual machines from a first volume to a second volume includes receiving a list of virtual machines which are not migrating from a first volume to a second volume, accessing a host file system usage map of a host machine that indicates active blocks out of a plurality of blocks of the host file system on the first volume, and accessing a plurality of virtual file system usage maps of a plurality of virtual machines that indicate active blocks of the virtual file systems out of a plurality of blocks of the first volume.
- a filter usage map that identifies the active blocks of the virtual machines which are not migrating is generated based on the virtual file system usage maps and the host file system usage map.
- the plurality of virtual machines are migrated from the first volume to the second volume, wherein the active blocks of the virtual file systems which are not migrating are skipped in accordance with the filter usage map. Subsequently, the metadata at the second volume is processed to properly reflect the virtual machines which were not migrated.
- the virtual machine is mounted by the host machine to access the host file system.
- the files comprising the virtual machines which are identified as not migrating are locked to prevent the fragmentation processing.
- the filter usage map comprises a bitmap.
- the list of virtual machines which are not migrating is received from a system administrator.
- the first volume is at a primary site and the second volume is a secondary site.
- the processing of metadata at the second volume is accomplished via a script mechanism.
- the second volume is size adjusted by a script mechanism to properly reflect the virtual machines which were not migrated.
- the present invention is implemented as a computer-readable storage medium having stored thereon, computer executable instructions that, if executed by a computer system cause the computer system to perform a method for migrating a selected set of virtual machines from a first volume to a second volume.
- the method includes receiving a list of virtual machines which are not migrating from a first volume to a second volume, accessing a host file system usage map of a host machine that indicates active blocks out of a plurality of blocks of the host file system on the first volume, and accessing a plurality of virtual file system usage maps of a plurality of virtual machines that indicate active blocks of the virtual file systems out of a plurality of blocks of the first volume.
- a filter usage map that identifies the active blocks of the virtual machines which are not migrating is generated based on the virtual file system usage maps and the host file system usage map.
- the plurality of virtual machines are migrated from the first volume to the second volume, wherein the active blocks of the virtual file systems which are not migrating are skipped in accordance with the filter usage map.
- the metadata at the second volume is processed to properly reflect the virtual machines which were not migrated.
- the virtual machine is mounted by the host machine to access the host file system.
- the present invention is implemented as a volume replication system, including a computer system having a processor coupled to a computer-readable storage media and executing computer-readable code which causes the computer system to implement a replication manager module.
- the replication manager module functions by receiving a list of virtual machines which are not migrating from a first volume to a second volume, accessing a host file system usage map of a host machine that indicates active blocks out of a plurality of blocks of the host file system on the first volume, and accessing a plurality of virtual file system usage maps of a plurality of virtual machines that indicate active blocks of the virtual file systems out of a plurality of blocks of the first volume.
- a filter usage map that identifies the active blocks of the virtual machines which are not migrating is generated based on the virtual file system usage maps and the host file system usage map.
- the plurality of virtual machines are migrated from the first volume to the second volume, wherein the active blocks of the virtual file systems which are not migrating are skipped in accordance with the filter usage map.
- the metadata at the second volume is processed to properly reflect the virtual machines which were not migrated.
- the virtual machine is mounted by the host machine to access the host file system.
- FIG. 1 illustrates a replication operation within a replication system environment according to one embodiment of the present invention.
- FIG. 2 shows a replication operation as implemented between virtual machines nodes and redundancy data server nodes in accordance with one embodiment of the present invention.
- FIG. 3 shows an exemplary virtual file system volume and replication volume 302 in accordance with one embodiment of the present invention.
- FIG. 4 shows a block diagram of an exemplary virtual environment, in accordance with one embodiment of the present invention.
- FIG. 5 shows an exemplary virtual file system including respective usage maps in accordance with one embodiment of the present invention.
- FIG. 6 shows a flowchart of the steps of a replication process in accordance with one embodiment of the present invention.
- FIG. 7 shows a diagram of a replication manager that implements certain aspects of the replication functionality in accordance with one embodiment of the present invention.
- FIG. 8 shows a diagram of a replication destination volume as instantiated on a physical device in accordance with one embodiment of the present invention.
- FIG. 9 shows an exemplary computer system according to one embodiment.
- FIG. 10 depicts a block diagram of a second computer system suitable for implementing certain functionality in accordance with one embodiment of the present invention.
- references within the specification to “one embodiment” or “an embodiment” are intended to indicate that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention.
- the appearance of the phrase “in one embodiment” in various places within the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments.
- various features are described which may be exhibited by some embodiments and not by others.
- various requirements are described which may be requirements for some embodiments but not other embodiments.
- Embodiments of the present invention implement an optimized method for new mirror/copy creation of volumes., such as, for example, SFW (Storage Foundation for WindowsTM) hosting a large collection of pre-allocated Hyper-V virtual machine image files (VHD), such as, for example, Hyper-V, while the virtual machines are in use.
- the optimized method includes using volume level change tracking and zero write suppression/emulation logic.
- embodiments of the present invention includes functionality for selectively migrating a subset of VHD files from the given volume onto new target volume, rather than copying over the entire volume. This migration can be implemented for various reasons, such as, for example, workload/space usage balancing on a given backend array, enhance performance of an application, and the like.
- embodiments of the present invention provide a solution that enables an efficient and highly scalable process for the replication of data for a distributed computer system including one or more virtual machines.
- Embodiments of the present invention can replicate a data volume optimally.
- the volume may have one or more virtual file systems belonging to one or more virtual machines.
- Embodiments of the present invention are optimized to function with highly scalable distributed computer systems having hundreds of virtual nodes and physical nodes, or more (e.g., cloud computing system, etc.).
- application data resides across a large number of data server nodes. These data server nodes can be physical nodes, virtual nodes, or a combination of the two.
- Clients interact with the distributed computer system by directly writing data to one or more of the virtual/physical data server nodes.
- the physical nodes e.g., data servers
- LUNs logical unit numbers
- a typical implementation would have the LUNs configured with multiple partitions.
- the files of the distributed computer system are composed of objects (e.g., data objects, etc.) which can be from any of the data server nodes, any of the LUNs and/or any of the partitions.
- objects e.g., data objects, etc.
- Embodiments of the present invention efficiently handle replication for the virtual nodes of the distributed computer system in a manner that is scalable and provides high availability. Additionally, embodiments of the present invention implement their application processes without taking the virtual nodes off-line.
- FIG. 1 is a block diagram depicting a network architecture 100 in which client systems 110 , 120 and 130 , as well as storage servers 140 A and 140 B are coupled to a network 150 in accordance with one embodiment of the present invention.
- the storage servers 140 A and 140 B can be used to instantiate one or more virtual machines.
- a storage server 140 A is further depicted as having storage devices 160 A( 1 )-(N) directly attached, and storage server 140 B is depicted with storage devices 160 B( 1 )-(N) directly attached.
- Storage servers 140 A and 140 B are also connected to a SAN fabric 170 , although connection to a storage area network is not required for operation of the disclosure.
- SAN fabric 170 supports access to storage devices 180 ( 1 )-(N) by storage servers 140 A and 140 B, and so by client systems 110 , 120 and 130 via network 150 .
- SAN fabric 170 also supports access to a storage array 190 , which is also shown as an example of a specific storage device. Certain functionality of embodiments of the present invention are implemented via a replication manager 195 , which is shown as instantiated on the server 140 B.
- Client computer systems 110 , 120 and 130 are communicatively coupled via the network 150 .
- Client systems 110 , 120 and 130 are able to access information on data server 140 A or 140 B using, for example, a web browser or other client software (not shown).
- client software not shown
- Such a client allows client systems 110 , 120 and 130 to access data hosted by storage server 140 A or 140 B or one of storage devices 160 A( 1 )-(N), 160 B( 1 )-(N), 180 ( 1 )-(N) or storage array 190 .
- FIG. 1 depicts the use of a network such as the Internet for exchanging data, but the present disclosure is not limited to the Internet or any particular network-based environment.
- FIG. 2 shows a data flow diagram 200 depicting the operation of an exemplary replication process in accordance with one embodiment of the present invention.
- a group of virtual machine data servers 210 host data that is accessed by a large number of client computer systems (e.g., clients 110 - 130 ).
- client computer systems e.g., clients 110 - 130
- the I/O data is forwarded to a replication manager 230 , which processes the I/O data and transfers it to a plurality of redundant data servers 220 .
- the FIG. 2 embodiment illustrates a scalable distributed computer system environment.
- the distributed computer system environment implements any of a number of different RAID redundancy schemes by forwarding data from the replication manager 230 to the plurality of redundancy data servers 220 .
- the client's I/O data specifically their write data (e.g., the similar holds true for the metadata written by one or more metadata servers) is generated, is received and stored on the virtual machines 210 .
- the virtual machines 210 then forward these data objects to the replication manager 230 .
- the replication manager 230 then forwards these data objects to the destination redundancy data servers according to the replication policy, such as, for example, the RAID policy. For example if the RAID policy for the file is RAID-1 then it just has to copy the data, whereas if the RAID policy is RAID-5 then it has to distribute the data, compute the parity, or even at times read the old data and merge the data before computing parity.
- FIG. 3 shows an exemplary virtual file system volume and replication volume 302 in accordance with one embodiment of the present invention.
- the file system volume comprises both a certain amount of used space 311 and a remaining amount of unused space, which is depicted as whitespace 312 .
- whitespace 312 a file system volume may only use a sub portion (e.g., used space 311 ) of the total number of blocks comprising the 24 GB fixed VHD.
- Embodiments of the present invention advantageously enable the use of fixed VHD for high I/O performance, while implementing an optimized replication process, where file system information is used to reduce the amount of data to be copied when a new mirror is added to a volume.
- Embodiments of the present invention implement the optimized replication process without taking the virtual file system volume off-line. This aspect greatly improves the availability of the application/data supported by the virtual file system volume.
- Embodiments of the present invention minimize the I/O traffic during a replication process by transferring only the used space 311 to create the replication volume 302 .
- the replication volume 302 will include used space 321 and whitespace 322 and will be mirror of the virtual file system volume 301 .
- FIG. 4 shows a block diagram of an exemplary virtual environment, in accordance with one embodiment of the present invention.
- Exemplary virtual environment 400 includes a host file system 405 , hypervisor 404 , and virtual machines 408 - 412 .
- Components of exemplary virtual environment 400 typically execute on or otherwise be part of a distributed computing system (e.g., servers 140 a and 140 b of FIG. 1 ).
- Hypervisor 404 interfaces with hardware 402 (e.g., of servers 140 a - b ) and provides resources and services to virtual machines 408 - 412 .
- hypervisor 404 is part of a trusted computing base (TCB).
- TBC trusted computing base
- Hypervisor 404 provides abstractions including emulated devices of resources in hardware 402 to virtual machines 408 - 412 .
- the virtual hard drives 414 a - c are emulated via the hypervisor 404 and the host file system 405 by using a physical volume 420 .
- the physical volume 420 can be, for example, one or more LUNs on server 140 A or 140 B, or one of storage devices 160 A( 1 )-(N), 160 B( 1 )-(N), 180 ( 1 )-(N) or storage array 190 .
- FIG. 5 shows exemplary virtual file systems 501 - 508 including respective usage maps 511 - 518 , in accordance with one embodiment of the present invention.
- FIG. 5 also shows a host file system 520 with its respective usage map 521 .
- the FIG. 5 embodiment shows the respective usage maps 511 - 518 of the virtual file systems 501 - 508 of multiple different virtual machines.
- the host file system usage map implements block level change tracking, zero region write suppression/emulation and zero filling of deleted file space functionalities. These functionalities allow fast mirror creations by only copying actual blocks in use.
- the respective usage maps 511 - 518 of the virtual file systems 501 - 508 comprise a volume level change tracking mechanism to detect changes to the volume in a persistent way. As described above, in one embodiment, the changes are recorded into bitmap.
- the replication manager then uses zero write detection/suppression logic, which functions by trapping attempts to write zero data into volume and suppressing such writes. The bitmap for the corresponding region is then reset. Similarly, any attempt to read a region marked as not in use will emulate a zero region read. The replication manager can then reclaim deleted/moved file space in the guests to keep the active region bits in the bitmap as small as possible.
- the replication manager when it is time to clone/copy the volume, creates a target volume and starts copying over data belonging to active bits in the bitmap in addition to any ongoing writes to achieve a fast copy of the volume with minimal data movement.
- the host file system may be supporting many more (e.g., 20 to 40, or even more).
- Embodiments of the present invention can determine which of the number of virtual machines have been active recently by checking its own respective host file system usage map 521 .
- the host file system usage map 521 will identify which virtual file system has been active (e.g., which blocks of the physical volume have been updated).
- the usage map comprises a bitmap where a bit being set indicates the corresponding block is in use.
- the replication manager can generate a merged usage map 540 .
- the replication manager 530 can access the host file system usage map 521 of the host machine and discover those active blocks out of a plurality of blocks of the host file system.
- the replication manager 530 can also access the virtual file system usage maps 511 - 518 of the virtual machines.
- the virtual file system usage maps 511 - 518 indicate the active blocks out of the total plurality of blocks of the virtual file systems.
- a merged usage map 540 can be generated by the replication manager.
- the merged usage map 540 identifies active blocks of the host file system (e.g., on the physical volume) that are associated with the virtual file systems.
- a given virtual machine needs to be mounted by the host machine in order for replication manager to access the virtual file system usage map.
- the virtual file system 511 would need to be mounted by the hypervisor and the host file system 520 in order to allow the replication manager 530 to access the usage map 511 of the virtual file system 501 .
- the virtual machine does not need to be mounted by the host machine to access the host file system.
- the replication manager 530 can more directly access the usage map 511 of the virtual file system 501 (e.g., via an API call, etc.).
- the replication manager uses a space optimized snapshot to maintain the accessibility of the virtual file system on the primary volume.
- this space optimized snapshot volume comprises a point-in-time image that the replication is based on.
- the replication manager uses the space optimized snapshot to access a virtual file system usage map of a virtual machine that indicates active blocks out of a plurality of blocks of the virtual file system.
- access to the virtual file system usage map can be implemented either by mounting the virtual disk files on the snapshot through a separate virtual machine or by using off-line tools or APIs which understand the virtual file format (e.g., VHD/VMDK etc formats, or the like).
- FIG. 6 shows a flowchart of the steps of a replication process 600 in accordance with one embodiment of the present invention.
- process 600 shows exemplary operating steps involved in implementing a partial migration of a set of pre-allocated virtual file systems from one volume to another volume.
- the replication process is performed on a data volume that includes multiple virtual file systems, where it is desired that only a subset of the virtual file systems on the volume are replicated and migrated.
- Process 600 begins in step 601 , where a partial migration is initiated.
- step 602 a list of VHD files associated with virtual machines which are not moving is received.
- This list can also include other large files associated with a virtual machine which will not change in size during the operation. For example, in a case where virtual file systems 507 and 508 are not moving, the list would identify their VHD files.
- This step leads to the generation of a copy bitmap that indicates the minimal set of blocks that need to be copied over to the second volume (e.g., target volume).
- step 603 the files of the virtual machines that are identified as not moving are locked down. In one embodiment, this includes enforcing a no defragmentation policy on these files. In one embodiment, this functionality is provided by a filter driver.
- usage maps are obtained for the files of the virtual machines that are identified as not moving.
- the usage map comprises a bitmap, as described above.
- the bitmap that identifies the virtual machines that are not moving to the second volume comprises a filter usage map, or filter bitmap.
- the filter usage map can be aligned to an appropriate region boundary if the region and the file system cluster sizes do not match. Thus only regions completely within the listed file will be set in the bitmap.
- a replication and migration operation is initiated from the first volume to the second volume.
- the replication manager creates a second target volume and starts copying over data belonging to active bits in the bitmap in addition to any ongoing writes to achieve a fast copy of the volume with minimal data movement.
- step 606 a replication and migration operation is started between the first volume and the second volume.
- the filter usage map is used to identify data objects from the virtual machines that are defined as not moving. These data objects are skipped during the replication and migration operation.
- any new writes or writes generated by the migration operation will consult the filter usage map, and if the region is in the filter usage map, it will not be written to or copied over into the second volume.
- we will have a new target volume with file system metadata similar to the original volume but with all the data belonging to the skipped VHD files not written, for example, the VHD files for the virtual file systems 507 - 508 , in a case where virtual file systems 507 and 508 are not moving.
- the operation should complete faster than the full volume replication or migration.
- step 608 the metadata at the 2 nd volume is processed to properly reflect those virtual machines which were not moved.
- the new volume will be cleaned up of dangling metadata of files belonging to the virtual machines which did not get moved over.
- this can be implemented by using a volume level scripting scheme.
- any needed resizing of the new volume with selected VM images can be accomplished with a similar volume scripting mechanism.
- the volume will contain the VM files which were selectively moved and will be of the requested size specified by, for example, a system administrator.
- process 600 could be orchestrated within a scheme such as storage VMotionTM, in which case the virtual machines could be moved from one active volume to another active volume in co-operation with the Hypervisor.
- Such selective virtual machine migration can also be carried out on virtual machines which are offline directly by a SFWTM storage layer and appropriate Hypervisor APIs calls could be made later to indicate their new location to the Hypervisor.
- FIG. 7 shows a diagram of a replication manager 700 that implements certain aspects of the replication functionality in accordance with one embodiment of the present invention.
- the replication manager 700 is a software component or module that when instantiated, implements the functionality of the replication processes of embodiments of the present invention.
- the replication manager 700 includes a host file system accessing module 701 that functions by accessing the host file system to read the usage maps the host file system.
- a virtual file system accessing module 702 is included and functions by accessing the virtual file system of a virtual machine and reading the usage map of the virtual file system.
- a filter usage map generating module is included and is used for merging the information from the host file system usage map with the information from the virtual file system usage map along with a list of the virtual machines which are not moving.
- a file system replication module is included for replicating data blocks comprising the virtual file system in accordance with the filter usage map.
- FIG. 8 shows a diagram of a replication destination volume as instantiated on a physical device in accordance with one embodiment of the present invention.
- the replication destination volume can be implemented as, for example, one or more LUNs on server 140 A or 140 B, or one of storage devices 160 A( 1 )-(N), 160 B( 1 )-(N), 170 ( 1 )-(N) or storage array 190 .
- the active blocks of the host file system e.g., on the physical volume
- the active blocks of the host file system that are associated with the virtual file systems are transferred to the replication destination and are used to create the replicated file systems 801 - 806 .
- the replicated file systems 801 - 806 are mirrors of the virtual file systems 501 - 506 , minus the data objects of the virtual machines which do not get moved (e.g., file systems 507 - 508 ).
- the volume metadata 840 is the metadata for the volume which is later harmonized by a metadata processing operation to properly reflect the virtual machines that do not get moved.
- FIG. 9 shows an exemplary computer system 900 according to one embodiment.
- Computer system 900 depicts the components of a basic computer system providing the execution environment for certain hardware-based and software-based functionality for the above described embodiments.
- computer system 900 can be a system upon which the replication manager 700 is instantiated.
- Computer system 900 can be implemented as, for example, a server computer system, workstation computer system, desktop computer system, or laptop computer system.
- computer system 900 can be implemented as a handheld device.
- Computer system 900 typically includes at least some form of computer-readable media (e.g., computer-readable storage medium 901 ).
- Computer-readable media can be a number of different types of available media that can be accessed by computer system 900 and can include, but is not limited to, computer storage media.
- computer system 900 typically includes processing unit 903 and a computer-readable storage medium 901 .
- memory 901 can be volatile (e.g., such as DRAM, etc.), non-volatile (e.g., such as ROM, flash memory, etc.) or some combination of the two.
- the memory 901 can comprise other devices besides solid-state devices, such as, for example, magnetic disk-based media, optical media, or the like.
- computer system 900 can include other mass storage systems (e.g., removable 905 and/or non-removable 907 ) such as magnetic or optical disks or tape.
- computer system 900 can include input devices 911 and/or output devices 909 (e.g., such as a display).
- Computer system 900 can further include communication connections 913 to other devices, computers, networks, servers, etc. using either wired or wireless media. As all of these devices are well known in the art, they need not be discussed in detail.
- the computer system 900 can have some, most, or all of its functionality supplanted by a distributed computer system having a large number of dispersed computing nodes, such as would be the case where the functionality of the computer system 900 is partly or wholly executed using a cloud computing environment.
- FIG. 10 depicts a block diagram of a second computer system 1010 suitable for implementing certain functionality in accordance with one embodiment of the present invention.
- Computer system 1010 includes a bus 1012 which interconnects major subsystems of computer system 1010 , such as a central processor 1014 , a system memory 1017 (typically RAM, but which may also include ROM, flash RAM, or the like), an input/output controller 1017 , an external audio device, such as a speaker system 1020 via an audio output interface 1022 , an external device, such as a display screen 1024 via display adapter 1026 , serial ports 1027 and 1030 , a keyboard 1032 (interfaced with a keyboard controller 1033 ), a storage interface 1034 , a floppy disk drive 1037 operative to receive a floppy disk 1037 , a host bus adapter (HBA) interface card 1035 A operative to connect with a Fiber Channel network 1090 , a host bus adapter (HBA) interface card 1035 B operative to
- mouse 1046 or other point-and-click device, coupled to bus 1012 via serial port 1027
- modem 1047 coupled to bus 1012 via serial port 1030
- network interface 1047 coupled directly to bus 1012 .
- Bus 1012 allows data communication between central processor 1014 and system memory 1017 , which may include read-only memory (ROM) or flash memory (neither shown), and random access memory (RAM) (not shown), as previously noted.
- the RAM is generally the main memory into which the operating system and application programs are loaded.
- the system memory 1017 instantiates a replication manager module 1050 which implements the continuous replication functionality described above.
- the ROM or flash memory can contain, among other code, the Basic Input-Output system (BIOS) which controls basic hardware operation such as the interaction with peripheral components.
- BIOS Basic Input-Output system
- Applications resident with computer system 1010 are generally stored on and accessed via a computer-readable medium, such as a hard disk drive (e.g., fixed disk 1044 ), an optical drive (e.g., optical drive 1040 ), a floppy disk unit 1037 , or other storage medium. Additionally, applications can be in the form of electronic signals modulated in accordance with the application and data communication technology when accessed via network modem 1047 or interface 1047 .
- a computer-readable medium such as a hard disk drive (e.g., fixed disk 1044 ), an optical drive (e.g., optical drive 1040 ), a floppy disk unit 1037 , or other storage medium.
- applications can be in the form of electronic signals modulated in accordance with the application and data communication technology when accessed via network modem 1047 or interface 1047 .
- Storage interface 1034 can connect to a standard computer-readable medium for storage and/or retrieval of information, such as a fixed disk drive 1044 .
- Fixed disk drive 1044 may be a part of computer system 1010 or may be separate and accessed through other interface systems.
- Modem 1047 may provide a direct connection to a remote server via a telephone link or to the Internet via an internet service provider (ISP).
- ISP internet service provider
- Network interface 1047 may provide a direct connection to a remote server via a direct network link to the Internet via a POP (point of presence).
- Network interface 1047 may provide such connection using wireless techniques, including digital cellular telephone connection, Cellular Digital Packet Data (CDPD) connection, digital satellite data connection or the like.
- CDPD Cellular Digital Packet Data
- FIG. 10 Many other devices or subsystems (not shown) may be connected in a similar manner (e.g., document scanners, digital cameras and so on). Conversely, all of the devices shown in FIG. 10 need not be present to practice the present disclosure.
- the devices and subsystems can be interconnected in different ways from that shown in FIG. 10 .
- the operation of a computer system such as that shown in FIG. 10 is readily known in the art and is not discussed in detail in this application.
- Code to implement the present disclosure can be stored in computer-readable storage media such as one or more of system memory 1017 , fixed disk 1044 , optical disk 1042 , or floppy disk 1037 .
- the operating system provided on computer system 1010 may be MS-DOS®, MS-WINDOWS®, OS/ 2 ®, UNIX®, Linux®, or another known operating system.
- a signal can be directly transmitted from a first block to a second block, or a signal can be modified (e.g., amplified, attenuated, delayed, latched, buffered, inverted, filtered, or otherwise modified) between the blocks.
- a signal can be directly transmitted from a first block to a second block, or a signal can be modified (e.g., amplified, attenuated, delayed, latched, buffered, inverted, filtered, or otherwise modified) between the blocks.
- modified signals e.g., amplified, attenuated, delayed, latched, buffered, inverted, filtered, or otherwise modified
- a signal input at a second block can be conceptualized as a second signal derived from a first signal output from a first block due to physical limitations of the circuitry involved (e.g., there will inevitably be some attenuation and delay). Therefore, as used herein, a second signal derived from a first signal includes the first signal or any modifications to the first signal, whether due to circuit limitations or due to passage through other circuit elements which do not change the informational and/or final functional aspect of the first signal.
Abstract
Description
Claims (20)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/099,247 US8555278B2 (en) | 2011-05-02 | 2011-05-02 | Method and system for migrating a selected set of virtual machines between volumes |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/099,247 US8555278B2 (en) | 2011-05-02 | 2011-05-02 | Method and system for migrating a selected set of virtual machines between volumes |
Publications (2)
Publication Number | Publication Date |
---|---|
US20120284707A1 US20120284707A1 (en) | 2012-11-08 |
US8555278B2 true US8555278B2 (en) | 2013-10-08 |
Family
ID=47091154
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/099,247 Active 2031-11-02 US8555278B2 (en) | 2011-05-02 | 2011-05-02 | Method and system for migrating a selected set of virtual machines between volumes |
Country Status (1)
Country | Link |
---|---|
US (1) | US8555278B2 (en) |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9686171B1 (en) * | 2013-07-22 | 2017-06-20 | Veritas Technologies | Systems and methods for attributing input/output statistics networks to region-mapped entities |
US9727257B2 (en) | 2015-02-05 | 2017-08-08 | Red Hat, Inc. | Maintaining relative references when unlinking volumes from a volume chain |
CN107203480A (en) * | 2016-03-17 | 2017-09-26 | 华为技术有限公司 | A kind of data prefetching method and device |
US20180232249A1 (en) * | 2017-02-15 | 2018-08-16 | International Business Machines Corporation | Virtual machine migration between software defined storage systems |
US10621146B2 (en) * | 2014-09-25 | 2020-04-14 | Netapp Inc. | Synchronizing configuration of partner objects across distributed storage systems using transformations |
US11119801B2 (en) | 2019-03-28 | 2021-09-14 | International Business Machines Corporation | Migrating virtual machines across commonly connected storage providers |
Families Citing this family (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8706869B2 (en) * | 2011-06-14 | 2014-04-22 | International Business Machines Corporation | Distributed cloud placement software |
US9372827B2 (en) * | 2011-09-30 | 2016-06-21 | Commvault Systems, Inc. | Migration of an existing computing system to new hardware |
US8990815B1 (en) * | 2012-02-01 | 2015-03-24 | Symantec Corporation | Synchronizing allocated blocks of virtual disk files across primary and secondary volumes by excluding unused blocks |
US10437681B2 (en) * | 2013-10-30 | 2019-10-08 | Trilio Data, Inc. | Method and apparatus of managing application workloads on backup and recovery system |
US9317380B2 (en) | 2014-05-02 | 2016-04-19 | International Business Machines Corporation | Preserving management services with self-contained metadata through the disaster recovery life cycle |
US9766930B2 (en) | 2014-06-28 | 2017-09-19 | Vmware, Inc. | Using active/passive asynchronous replicated storage for live migration |
US9760443B2 (en) | 2014-06-28 | 2017-09-12 | Vmware, Inc. | Using a recovery snapshot during live migration |
US9588796B2 (en) * | 2014-06-28 | 2017-03-07 | Vmware, Inc. | Live migration with pre-opened shared disks |
US9672120B2 (en) | 2014-06-28 | 2017-06-06 | Vmware, Inc. | Maintaining consistency using reverse replication during live migration |
US10671545B2 (en) | 2014-06-28 | 2020-06-02 | Vmware, Inc. | Asynchronous encryption and decryption of virtual machine memory for live migration |
US9898320B2 (en) | 2014-06-28 | 2018-02-20 | Vmware, Inc. | Using a delta query to seed live migration |
US10185637B2 (en) | 2015-02-16 | 2019-01-22 | International Business Machines Corporation | Preserving management services with distributed metadata through the disaster recovery life cycle |
CN104951354B (en) * | 2015-06-08 | 2017-12-08 | 北京大学 | A kind of scheduling virtual machine algorithm security verification method based on dynamic migration |
WO2017014809A1 (en) * | 2015-07-18 | 2017-01-26 | Hewlett-Packard Development Company, L.P. | Data volume migration in distributed storage systems |
US10423588B2 (en) | 2015-08-25 | 2019-09-24 | International Business Machines Corporation | Orchestrated disaster recovery |
US10409521B1 (en) * | 2017-04-28 | 2019-09-10 | EMC IP Holding Company LLC | Block-based backups for large-scale volumes |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6618736B1 (en) * | 2001-03-09 | 2003-09-09 | Ensim Corporation | Template-based creation and archival of file systems |
US20070067766A1 (en) * | 2001-09-28 | 2007-03-22 | Yoram Tal | Infrastructure for the automation of the assembly of schema maintenance scripts |
US20080127182A1 (en) * | 2006-11-29 | 2008-05-29 | Newport William T | Managing Memory Pages During Virtual Machine Migration |
US20110119427A1 (en) * | 2009-11-16 | 2011-05-19 | International Business Machines Corporation | Symmetric live migration of virtual machines |
US8332847B1 (en) * | 2008-01-10 | 2012-12-11 | Hewlett-Packard Development Company, L. P. | Validating manual virtual machine migration |
-
2011
- 2011-05-02 US US13/099,247 patent/US8555278B2/en active Active
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6618736B1 (en) * | 2001-03-09 | 2003-09-09 | Ensim Corporation | Template-based creation and archival of file systems |
US20070067766A1 (en) * | 2001-09-28 | 2007-03-22 | Yoram Tal | Infrastructure for the automation of the assembly of schema maintenance scripts |
US20080127182A1 (en) * | 2006-11-29 | 2008-05-29 | Newport William T | Managing Memory Pages During Virtual Machine Migration |
US8332847B1 (en) * | 2008-01-10 | 2012-12-11 | Hewlett-Packard Development Company, L. P. | Validating manual virtual machine migration |
US20110119427A1 (en) * | 2009-11-16 | 2011-05-19 | International Business Machines Corporation | Symmetric live migration of virtual machines |
Cited By (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9686171B1 (en) * | 2013-07-22 | 2017-06-20 | Veritas Technologies | Systems and methods for attributing input/output statistics networks to region-mapped entities |
US10621146B2 (en) * | 2014-09-25 | 2020-04-14 | Netapp Inc. | Synchronizing configuration of partner objects across distributed storage systems using transformations |
US11442903B2 (en) | 2014-09-25 | 2022-09-13 | Netapp Inc. | Synchronizing configuration of partner objects across distributed storage systems using transformations |
US11921679B2 (en) | 2014-09-25 | 2024-03-05 | Netapp, Inc. | Synchronizing configuration of partner objects across distributed storage systems using transformations |
US9727257B2 (en) | 2015-02-05 | 2017-08-08 | Red Hat, Inc. | Maintaining relative references when unlinking volumes from a volume chain |
CN107203480A (en) * | 2016-03-17 | 2017-09-26 | 华为技术有限公司 | A kind of data prefetching method and device |
CN107203480B (en) * | 2016-03-17 | 2020-11-17 | 华为技术有限公司 | Data prefetching method and device |
US20180232249A1 (en) * | 2017-02-15 | 2018-08-16 | International Business Machines Corporation | Virtual machine migration between software defined storage systems |
US10747581B2 (en) * | 2017-02-15 | 2020-08-18 | International Business Machines Corporation | Virtual machine migration between software defined storage systems |
US11119801B2 (en) | 2019-03-28 | 2021-09-14 | International Business Machines Corporation | Migrating virtual machines across commonly connected storage providers |
Also Published As
Publication number | Publication date |
---|---|
US20120284707A1 (en) | 2012-11-08 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8555278B2 (en) | Method and system for migrating a selected set of virtual machines between volumes | |
US10162722B2 (en) | Virtual machine aware replication method and system | |
EP2731013B1 (en) | Backing up method, device, and system for virtual machine | |
US8326803B1 (en) | Change tracking of individual virtual disk files | |
US10503604B2 (en) | Virtual machine data protection | |
US8799222B2 (en) | Host based software block level replication using metadata indicating changed data objects at source and secondary nodes | |
US8473462B1 (en) | Change tracking for shared disks | |
US8346727B1 (en) | Optimized image archiving | |
US9354907B1 (en) | Optimized restore of virtual machine and virtual disk data | |
JP5631400B2 (en) | Proxy backup of virtual disk image file on NAS device | |
US10296428B2 (en) | Continuous replication in a distributed computer system environment | |
US8799557B1 (en) | System and method for non-volatile random access memory emulation | |
US8812677B2 (en) | Data processing method and apparatus for remote storage system | |
US8572338B1 (en) | Systems and methods for creating space-saving snapshots | |
US10459806B1 (en) | Cloud storage replica of a storage array device | |
US8954435B2 (en) | Method and system for reclaiming storage on a shared storage device or independent of the mount state of a file system | |
US10509705B2 (en) | Application protection through a combined functionality failure manager | |
US8924442B2 (en) | Method and system for implementing high availability storage on thinly provisioned arrays | |
US20240078198A1 (en) | Instant recovery as an enabler for uninhibited mobility between primary storage and secondary storage | |
US8429125B2 (en) | Conversion of physical computers to virtualized environments method and system | |
US20130024428A1 (en) | Method and system for a fast full style system check using multithreaded read ahead | |
US10162542B1 (en) | Data protection and incremental processing for multi-span business applications | |
US11301156B2 (en) | Virtual disk container and NVMe storage management system and method | |
US11221786B2 (en) | Fast recovery in recoverpoint using direct storage access | |
US11334441B2 (en) | Distribution of snaps for load balancing data node clusters |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: SYMANTEC CORPORATION, CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:JANAKIRAMAN, VISWESVARAN;REEL/FRAME:026212/0350 Effective date: 20110429 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
AS | Assignment |
Owner name: VERITAS US IP HOLDINGS LLC, CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:SYMANTEC CORPORATION;REEL/FRAME:037697/0412 Effective date: 20160129 |
|
AS | Assignment |
Owner name: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS COLLATERAL AGENT, CONNECTICUT Free format text: SECURITY INTEREST;ASSIGNOR:VERITAS US IP HOLDINGS LLC;REEL/FRAME:037891/0726 Effective date: 20160129 Owner name: BANK OF AMERICA, N.A., AS COLLATERAL AGENT, NORTH CAROLINA Free format text: SECURITY INTEREST;ASSIGNOR:VERITAS US IP HOLDINGS LLC;REEL/FRAME:037891/0001 Effective date: 20160129 Owner name: BANK OF AMERICA, N.A., AS COLLATERAL AGENT, NORTH Free format text: SECURITY INTEREST;ASSIGNOR:VERITAS US IP HOLDINGS LLC;REEL/FRAME:037891/0001 Effective date: 20160129 Owner name: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS COLLATE Free format text: SECURITY INTEREST;ASSIGNOR:VERITAS US IP HOLDINGS LLC;REEL/FRAME:037891/0726 Effective date: 20160129 |
|
AS | Assignment |
Owner name: VERITAS TECHNOLOGIES LLC, CALIFORNIA Free format text: MERGER AND CHANGE OF NAME;ASSIGNORS:VERITAS US IP HOLDINGS LLC;VERITAS TECHNOLOGIES LLC;REEL/FRAME:038455/0752 Effective date: 20160329 |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
AS | Assignment |
Owner name: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT, DELAWARE Free format text: SECURITY INTEREST;ASSIGNOR:VERITAS TECHNOLOGIES LLC;REEL/FRAME:054370/0134 Effective date: 20200820 |
|
AS | Assignment |
Owner name: VERITAS US IP HOLDINGS, LLC, CALIFORNIA Free format text: TERMINATION AND RELEASE OF SECURITY IN PATENTS AT R/F 037891/0726;ASSIGNOR:WILMINGTON TRUST, NATIONAL ASSOCIATION, AS COLLATERAL AGENT;REEL/FRAME:054535/0814 Effective date: 20201127 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 8 |