For performing maintenance operations on a local datastore in the cloud site evacuate all incoming replications and replication data placed on that datastore. To evacuate the replications from the datastore at once, apply an alternative storage policy for all incoming replications that reside on the datastore.
Note:
- Evacuating a datastore invalidates all VMware Cloud Director Availability backups created priorly and they cannot restore the replications.
To ensure restoring from a backup is successful, create a backup every time the replications are moved from one datastore to another. For information about restoring, see Restore the appliances in the cloud.
- Evacuating a datastore might take several hours until completed and depends on the amount of data for transferring.
- Since VMware Cloud Director Availability 4.4 evacuating replicas from individual members of datastore clusters is supported. Replications on a member datastore can move only to a different (for example, temporary) storage policy, they cannot be rebalanced within the other member datastores within the same cluster. After maintenance completes, the replications can be moved back from the temporary location to the original datastore cluster.
Prerequisites
- Verify that before evacuating, any replications that are already failed over or migrated are stopped.
- Verify that before evacuating, any replications that already completed a test failover are cleaned up.
Procedure
Results
What to do next
You can track the progress of the Change storage profiles task by clicking System Tasks in the left pane.