Abstract:
Exemplary methods, apparatuses, and systems include receiving a device discovery command from a recovery manager running on a management server within a first or second datacenter. In response to the device discovery command, device identifiers for one or more logical storage devices within the first datacenter are requested. In response to the request, a device discovery response including a first identifier is received. The received device discovery response is modified to include the first device identifier as the identifier for both an underlying logical storage device and as an identifier for a peer logical storage device. The modified response is returned to the recovery manager in response to the device discovery command.
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:
Exemplary methods, apparatuses, and systems include receiving a command from a recovery manager running on a management server within a first or second datacenter. In response to the command, device identifiers for one or more logical storage devices within the first datacenter are requested. In response to the request, a first device identifier for a first logical storage device within the first datacenter and a peer device identifier for a second logical storage device within the second datacenter are received. Data is replicated from the first logical storage device to the second logical storage device. The first and second logical storage devices are in an active-passive configuration, the first logical storage device storing the replicated data being active and the second logical storage device storing the replicated data being passive. The command with the peer device identifier is sent to the underlying storage.
Abstract:
A recovery manager discovers replication properties of datastores stored in a storage array, and assigns custom tags to the datastores indicating the discovered replication properties. A user may create storage profiles with rules using any combination of these custom tags describe replication properties. The recovery manager protects a storage profile using a policy-based protection mechanism. Whenever a new replicated datastore is provisioned, the datastore is dynamically tagged with the replication properties of their underlying storage, and will belong to one or more storage profiles. The recovery manager monitors storage profiles for new datastores and protects the newly provisioned datastore dynamically, including any or all of the VMs stored in the datastore.
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.