The environment has R16.5 Update 1 CA ARCserve Central Virtual Standby using a Local Virtual Standby Policy.
If the Virtualization selected in the Remote VSB policy is VMware, then the maximum recovery point snapshots is 29.
If the Virtualization selected in the Remote VSB policy is Microsoft Hyper-V, then the maximum recovery point snapshots is 24.
The steps below provide a way by which we can limit the number of the Recovery Point snapshots using registry tweaks.
1. If the source is a standalone D2D Server or managed by a CA Central Protection Manager, goto the source D2D node and on the Windows run prompt, type: Regedit to open up the Windows Registry Editor. Go to HKEY_LOCAL_MACHINE\SOFTWARE\CA\CA ARCserve D2D
You need to create a New String Value called MaximumSnapshotsforVS. The string value is case sensitive and needs to be created directly under the ARCserve D2D Registry Key. Once created, double click on the new string and set the numeric value between 1 and 29 for VMware ESXI or 1 and 24 for Hyper-V
In this example, the value has been set to 5
2. If the source is a Host Based VM Backup Node, then open the registry on the Host Based VM Backup D2D Proxy Node. Go to the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\CA\CA ARCserve D2D\ vSphereVMInstUUID
3. There will be sub directories under this registry key named after the UUID for every VMware Virtual Guest Server specified in your Local Virtual Standby Policy:
4.To identify which UUID represents which VIrtual Machine, go to the CA Central Hostt Based VM Backup Manager, right click on the VM node and select 'Login D2D'. This will open the URL which will display the UUID for the VM node.
5. You then need to create the Registry String Value under the UUID Key as follows:
Once created, double click on the new string and set the numeric value between 1 and 29 for VMware ESXI or 1 and 24 for Hyper-V.
In this example it will retain the last 5 Bootable Snap Shot Points for the Virtual Standby VM.