How to Properly Change a Datastore Configured within a VPG (ZVR 3.5 and greater)

KB Number:
00000186

Solution:

 

Purpose


 

An administrator may want to change a datastore setting configured within a VPG, such as a journal datastore, or a target datastore.  This article explains the steps necessary to do so, so as to avoid any negative effects on replication.

 

 

Affected Versions


 

Versions: 3.5 and greater

Hypervisors: VMWare

 

Complexity


 

Medium

 

 

Solution


 

In order to change datastores configured within a VPG, consider
the points below:

  • VM Recovery Datastore (‘Edit VPG’ screen, Replication tab, ‘advanced VM settings’ dialog)
    • This value determines the datastore that will hold the recovery VM’s .vmx file, and the backing files of RDM recovery volumes.
    • Should a cluster or a resource pool to be selected for a host, only datastores that are accessible by every ESX/ESXi host in the cluster or resource pool are displayed.
      When specifying the recovery datastore for a virtual machine with a storage cluster, specify a specific datastore in the cluster.
  • Datastore (‘Edit VPG’ screen, Replication tab)
    • This value determines the target datastore used by default for VMs subsequently configured within the VPG and their volumes.
    • Changing this value once VMs are already configured within a VPG will not affect the target datastore used for any of the already-protected VMs and their volumes.
  • Recovery Volume Location (‘Edit VPG’ screen, Storage tab)
    • This value determines the target datastore used for a specific volume configured within a protected VM.
    • Changing this value for a VM already configured within a VPG, results in a storage vMotion for the relevant volume.
  • Journal Datastore (‘Edit VPG’ screen, Replication tab, ‘Advanced Journal Settings’ dialog)
    • This value determines the datastore used for journal data for each VM within the VPG
    • The default value is the datastore used for recovery of each VM

 

See also


 

Preseeding Volumes

 


Hypervisor:
aws

1 Star2 Stars3 Stars4 Stars5 Stars (2 votes, average: 1.00 out of 5)
Loading...