Issue:
I recently ran into a unique issue while assisting a client with their replicated Vault. The Vault Backup was failing and when I checked the ADMS Console, I saw this message:
When I cleared the previous message, I saw the following issue:
Attempting to migrate the libraries would fail with this error:
The next clue was when I checked the Replication Status Summary. In this case, the two problem libraries status showed as “Subscribed,” but not “Active” as the rest of the libraries did.
Then when checking the Replication Monitor in SMS, the Replication Snapshot for both libraries showed that they had never started, while all other libraries showed they had completed. The following message indicated an issue with the synchronization:
Causes:
This led me to the next indicator for what the root problem may actually be as we can see in the following image.
Seeing that the Snapshot Agent had never run, I checked the Publication Properties to see if I could find what had prevented the Snapshot Agent from running. In this case, the Snapshot Agent appeared to have never been created, but there was no clear reason why or how that had occurred.
Solution:
The solution to this issue was to create the missing Snapshot Agents for each of the problem libraries. Once that was done, the libraries were able to be replicated and after the replication had completed, the libraries could then be migrated, which in turn allowed the Vault Backup Task to run as expected.
This was a particularly unusual case since as far as anyone knew the replication and backups had been running successfully since the original setup of the replicated environment. I was not involved with the setting up of the environment, so there may have been other factors that led to this issue that I’m not aware of and therefore cannot add for context to this article.
However, I hope that the information in this article may save someone else the time it took to track down this issue since I was unable to find mention of any similar issues in my online searches or conversations with colleagues.
Happy Troubleshooting everyone!
About the Author
Follow on Linkedin More Content by Heath White
