High Availability Sync Job Fails
Search and filter
KB Article ID: 10140
| Product: | High Availability |
| Product Version: | All |
| SharePoint Version: | All |
Details:
High Availability Sync job for two My Site databases failed at 50%, but showed as mirrored within the DR farm.
SYMPTOMS:
This error occurred when the user added an additional MySite database to an existing HA plan, which originally contained another MySite. The user configured the HA job to sync these MySite content databases, but the job ran until 50% and then failed. However, the user noticed that within the DR SQL server management studio, one of the the My Site databases was displayed as mirrored.
CAUSE:
The HA Sync job was unable to complete successfully because a Platform Backup incremental was run at the same time on the production Content Database. This caused the the Log Sequence Number to change, which resulted in the HA job failing during the ‘restoration’ of the MySite to the DR environment. Because it failed before completion, SQL never considered this item as ‘mirrored’.
SOLUTION:
As a best practice, AvePoint recommends not running HA jobs and Platform Backup jobs with the same Database(s) at the same time. The HA job will successfully complete when the Platform backup is not running at the same time.