Follow these steps in the source Core's registry to perform this replication tweak:
Quest does not provide support for problems that arise from improper modification of the registry. The Windows registry contains information critical to your computer and applications. Make sure you back up the registry before modifying it. For more information on the Windows Registry Editor and how to back up and restore it, refer to Microsoft Article ID 256986 “Description of the Microsoft Windows registry” at Microsoft Support.
*Note: Remember that for a set of recovery points to be read, a base image must be included in the replication. Otherwise, if just replicating incrementals, they will be replicated as orphans as they are missing a base image to be able to be read when trying to mount their data.
**Note: You need to consider that the Core registry keys have timestamps entered in UTC and 24 hour format. So, if your Core server's time zone is EST, for example, then when entering the time in the registry's string key it needs to be entered with 5 hours ahead of what the recovery point time is. Also, to ensure this works fine, enter the time with a few minutes before of what the timestamp of the recovery point was. For instance, if the date and time of the recovery point was March 4th 2021, 3:03pm in EST, you should input in the registry string key 2021-03-04T20:00 (discard the rest of the numbers the string value had). This to ensure the Core picks up this recovery point and doesn't skip to the next.
***Note: You will need to navigate to HKLM\SOFTWARE\AppRecovery\Core\Replication\RemoteCores\Slaves\[core ID]\PairingStatus\[number]\AgentInfo and see the value of the string key called DisplayName, that way you will identify which is the number for the agent in the hive PairingStatus that you're looking forward to replicate from a later date and time.
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center