Branch recovery CLI configuration example
The following examples show how to use the CLI to configure branch recovery on Core. The first output shows a LUN that is not configured with branch recovery. The example then shows how to start a schedule (with output), how to configure specific VMs, how to enable branch recovery, and output for a successfully recovered LUN.
The following output is from a new VMFS LUN, with branch recovery not enabled:
# show storage lun alias 200GiB branch-recovery
Branch Recovery configuration :
Enabled : no
Status : Not Enabled
Phase : Not Enabled
Progress : Not Enabled
Start date : Not Configured
Start time : Not Configured
#
Use the following command to start a branch recovery schedule:
# configure terminal
(config)# storage lun modify alias 200GiB branch-recovery schedule start-now
The output from the VMFS LUN now has a started schedule, but branch recovery remains disabled:
# show storage lun alias alias-vmfs_lun branch-recovery
Branch Recovery configuration :
Enabled : no
Status : not_started
Progress : 0 Bytes pushed
Start date : 2016/03/14
Start time : 15:01:16
#
The output does not list any VMs. If you have not defined them, all VMs are added by default. If you want to enable branch recovery for specific VMs on a specific LUN, use the following command:
(config) # storage lun modify alias 200GiB branch-recovery add-vm oak-sh000-vm1
VM names are discovered by prefetch and available for automatic completion. The default cap is set to 10. You can change the default with the storage lun modify alias 200GiB branch-recovery add-vm oak-sh486 cap 50 command.
Use the following command to show the result of configuring specific VMs:
# show storage lun alias 200GiB branch-recovery
Branch Recovery configuration :
Enabled : no
Status : not_started
Phase : not_started
Progress : 0 Bytes pushed
Start date : 2016/02/20
Start time : 10:32:59
VMs :
Name : oak-sh486-vm1
Status : Not Started
Cap : 10 %
Percent Complete : Branch recovery not started or not enabled on VM
Recovering data from : Branch recovery not started or not enabled on VM
#
When you are done configuring, scheduling, and adding the VMs, you can enable branch recovery for the LUNs by using the following command:
(config) # storage lun modify alias 200GiB branch-recovery enable
Notice that with branch recovery enabled, data blocks are actively being restored to the LUN. Use the following command to check the status of the recovery on a LUN:
# show storage lun alias 200GiB branch-recovery
Branch Recovery configuration :
Enabled : yes
Status : started
Phase : day
Progress : 3729920 Bytes pushed
Start date : 2016/02/20
Start time : 10:32:59
VMs :
Name : oak-sh486
Status : In-progress
Cap : 10 %
Percent Complete : 9 %
Recovering data from : Mon Feb 19 15:25 2016
#
When the recovery of the LUN is complete, you see the following output:
# show storage lun alias 200GiB branch-recovery
Branch Recovery configuration :
Enabled : yes
Status : complete
Progress : complete
Start date : 2014/02/20
Start time : 10:32:59
VMs :
Name : oak-sh486-vm1
Status : Complete
Cap : 10 %
Percent Complete : 100 %
Recovering data from : N/A