Ideally it may be worth periodically backing up Shareplex product and variable directories (also termed as proddir and vardir) periodically. However, it may be worth noting that there is no such concept in Shareplex like recovering up to the last transaction that happened on source. At most the backup of these directories may help preserve one-offs (in case of product directory) and tuning parameters (in case of data sub-directory within variable directory). The data sub-directory contains information about various tuning parameters as well as the login information for Shareplex user, the transformation routines, hints file, the conflict resolution files and oramsglist file. The config subdirectory within the vardir contains various config files created during the life of Shareplex and is also a very useful subdirectory to preserve. Preserving this directory may eliminate the painful effort involved in creating the config file once again, should the Shareplex directories be lost for any reason.
The paramdb and statusdb files located in /vardir/data directory of Shareplex are also a useful candidate when it comes to using a backup to salvage replication and are worth a special mention here. When statusdb is corrupted, the activation is lost. If there is a backup of statusdb, it is very easy for Support to recreate a new statusdb using the old back by amending the activation entry in it. Likewise when paramdb is corrupted, the backup provides an easy way out thereby a new paramdb can be recreated and the login and license key entries amended to reflect new values.