RM-V substitute
Posted: Wed Jul 10, 2013 8:20 am
Not sure if anyone tried to use RM-V, we have and it has a few issues. I am almost done with a powershell/powercli script that will replace RM-V. If there is interest I will make it available. It works based on the fact that your volume names and datastores names follow a consistent naming convention. If your datastores and volumes have no way of reconciling names programatically then my script will not work.
Basically what it does is:
Pass it a Remote Copy Group Name and some additional parameters and it will:
- enumerate the volumes in that RC Group then using logical to decipher the volume name into a datastore name
- snap the vms on those datastores (optionally quiescing them)
- then triggering the RC Sync (optionally stopping and restarting a sync in progress)
- Optionally also creating a backup snapshot on the local array with configurable expiration
- removing the VM level snapshots
- Generates a simple text file (for audit purposes) of what it did and which VMs were able to be quiesced.
Out current plan is to use this in place of RM-V due to the issues with RM_V and eventually replace our Commvault Snap Protect backups.
Basically what it does is:
Pass it a Remote Copy Group Name and some additional parameters and it will:
- enumerate the volumes in that RC Group then using logical to decipher the volume name into a datastore name
- snap the vms on those datastores (optionally quiescing them)
- then triggering the RC Sync (optionally stopping and restarting a sync in progress)
- Optionally also creating a backup snapshot on the local array with configurable expiration
- removing the VM level snapshots
- Generates a simple text file (for audit purposes) of what it did and which VMs were able to be quiesced.
Out current plan is to use this in place of RM-V due to the issues with RM_V and eventually replace our Commvault Snap Protect backups.