The synchronize standby feature (Sync) of the Dbvisit StandbyMP resolves the unrecoverable transaction log gap in standby. This can happen under these circumstances.
Adhoc transaction log backups are taken in the primary, breaking the log chain between the primary and standby.
An ad-hoc full backup was taken with tail log backup that breaks the log chain.
One or more transaction log backup files are lost in standby before getting applied in standby.
The Sync feature, in summary, does the following:
Take a differential backup of the primary database based on the backup taken on primary that was used to create the DR
Transfer the differential backup to standby.
Restore the database backup on standby.
Delete unwanted transaction log backups that are present on standby.
Resume the automated update.
Sync feature can be based only on the backup used to create the standby database. If another non-copy-only backup was taken in the meantime, Sync feature can’t be used and standby database has to be recreated from the scratch
To initiate the Sync process, select “Synnchronize” from the right ACTIONS pane:
There are no options available, click start to initiate the process:
Once the process starts, you will be able to see the task in the taskbar and also see the details:
Once task is finished, log shipping can continue normally.
Below is an example of failed Sync task due to non-copy-only backup being taken on primary:
Comments