We recently upgraded snapdrive and SMSQL to the latest versions: -
SnapManager for Microsoft SQL Server v7.1
Since upgrading the versions of these two products (upgraded all our servers) our remote verification is continually failing. Whereas before upgrading it was working fine.
I have searched the Internet for more information on the errors we are receiving, but am having no luck finding an answer or the cause!
Our configuration: -
We have a live site (SiteA) and DR site (SiteB - containing SnapMirror of volumes in SiteA). We perform a remote verification of servers backed up in SiteA, via mounting the SnapMirror snapshots in the DR site to a verification server in SiteB.
Since upgrading, SMSQL is consistently complaining about not being able to use SnapMirror destination volumes for verification as the mirror is not healthy. It then tries to connect to the source volume, but fails as the source is in a different site.
Below is a snippet of the backup / verification log :-
[10:29:14.523] [SERVER] Remote verification failed with an error, Error code: 0x80004005
[10:29:14.523] [SERVER] Error Code: 0x80004005
We are getting identical errors for all servers that perform a remote verification to the remote verification server in SiteB. I am struggling to troubleshoot where the issue lies. The SnapMirrors are in a healthy state as far as I can tell. I do not see why SMSQL cannot mount the snapshots from the snapmirror volumes.
Any help or advice on this matter would be greatly appreciated.