Using replicas with incremental backup

When you use a replica as an incremental backup of a VOB, you still back up the original VOB. You set up a replica of the original VOB in the same local area network, and schedule frequent unidirectional synchronizations. If you restore the original VOB from backup, the replica serves as an incremental backup by supplying changes made since the last backup.

This strategy reduces the frequency of backups at the original replica. It avoids some of the procedures described in Restoring a replica from backup, but still requires saving information about triggers, locks, and major pool changes. It also has the same limitations as unreplicated recovery from backup: a view and a VOB may not be consistent with each other after VersionVault recovery. It can, however, reduce the frequency of backups enough to fit into normal maintenance schedules.

The backup replica must be registered with a different registry host.