Abstract:
A recovery system and method for performing site recovery utilizes recovery-specific metadata and files of protected clients at a primary site to recreate the protected clients at a secondary site. The recovery-specific metadata is collected from at least one component at the primary site, and stored with the files of protected clients at the primary site. The recovery-specific metadata and the files of the protected clients are replicated to the secondary site so that the protected clients can be recreated at the secondary site using the replicated information.
Abstract:
Virtual computing instance data that are stored across multiple storage volumes are replicated in a manner such that the write order is maintained. The frequency of the replication is set so that the recovery point objective defined for the VM data can be satisfied. The replication includes the steps of determining a set of logical storage volumes across which the virtual computing instance issues dependent write IOs, issuing a first command to the virtual computing instance to block new IOs and to block receipt of IO acknowledgements, issuing a command to create replicas of all the logical storage volumes in the set, and then issuing a second command to the virtual computing instance to unblock new IOs and unblock receipt of IO acknowledgements.
Abstract:
A cloud availability manager configured to execute a recovery workflow that fails over one or more virtual machines (VMs) to and from a cloud computing system. In doing so, the cloud availability manager typically performs multiple operations for each VMs. The operations involve making several application programming interface (API) calls to component APIs of management components within the cloud computing system. To avoid bringing down the entire cloud infrastructure, the cloud availability manager throttles the API calls to other components while executing a recovery workflow. The throttling spans multiple instances (nodes) of the cloud availability manager and involves cooperation from the other management components to ensure the throttling is fair across all tenants of the cloud computing system.
Abstract:
Virtual computing instance data that are stored across multiple storage volumes are replicated in a manner such that the write order is maintained. The frequency of the replication is set so that the recovery point objective defined for the VM data can be satisfied. The replication includes the steps of determining a set of logical storage volumes across which the virtual computing instance issues dependent write IOs, issuing a first command to the virtual computing instance to block new IOs and to block receipt of IO acknowledgements, issuing a command to create replicas of all the logical storage volumes in the set, and then issuing a second command to the virtual computing instance to unblock new IOs and unblock receipt of IO acknowledgements.
Abstract:
Examples maintain consistency of writes for a plurality of VMs during live migration of the plurality from a source host to a destination host. The disclosure intercepts I/O writes to a migrated VM at a destination host and mirrors the I/O writes back to the source host. This “reverse replication” ensures that the CG of the source host is up to date, and that the source host is safe to fail back to if the migration fails.
Abstract:
To prevent a user from initiating potentially dangerous virtual machine migrations, a storage migration engine is configured to be aware of replication properties for a source datastore and a destination datastore. The replication properties are obtained from a storage array configured to provide array-based replication. A recovery manager discovers the replication properties of the datastores stored in the storage array, and assigns custom tags to the datastores indicating the discovered replication properties. When storage migration of a virtual machine is requested, the storage migration engine performs or prevents the storage migration based on the assigned custom tags.
Abstract:
Exemplary methods, apparatuses, and systems include receiving a command to perform a failover workflow for a plurality of logical storage devices from a protected site to a recovery site. A first logical storage device within the plurality of logical storage devices is determined to be a stretched storage device. In response to the failover command, a site preference for the first logical storage device is switched from the protected site to the recovery site. The failover includes a live migration of a virtual machine that resides on the first logical storage device. The live migration is performed without interruption to one or more services provided by the virtual machine. The site preference for the first logical storage device is switched prior to performing the live migration of the virtual machine.
Abstract:
A storage migration engine and a recovery manager are provided that enable failover operations to be performed in situations where storage migration and array-based replication are involved. The storage migration engine stores information related to storage migrations directly into a source datastore and a destination datastore, which are then replicated over to a recovery site. The recovery manager uses the information stored in the recovered datastores to select which instance of virtual machine data is to be used to fail over to a virtual machine at the recovery site.
Abstract:
Systems and techniques are described for determining the status of migrating virtual machines. A described technique includes initiating a migration of one or more virtual machines from a source host that is located at a source site to a destination host that is located at a destination site. A determination is made that a fault has occurred during the migration of the one or more virtual machines. In response to determining that the error has occurred, a determination is made, for each virtual machine of the one or more virtual machines, whether the virtual machine has been fully migrated from the source host to the destination host.
Abstract:
Systems and techniques are described for determining the status of migrating virtual machines. A described technique includes initiating a migration of one or more virtual machines from a source host that is located at a source site to a destination host that is located at a destination site. A determination is made that a fault has occurred during the migration of the one or more virtual machines. In response to determining that the error has occurred, a determination is made, for each virtual machine of the one or more virtual machines, whether the virtual machine has been fully migrated from the source host to the destination host.