1 Copper

Availability Group in resolving state after recoverpoint restore in DR

I have a 4 node SQL Server cluster for read only distributed calls. All 4 nodes are on the same cluster and the same consistency group to be replicated to the DR site.

When we test recovery (EMC) onto the DR site, The AG will be in "resolving" state and the databases will be in pending recovery.

If I place all database files on the same drive on the primary replica, the AG comes on correctly when brought on the DR site.

Obviously, there is inconsistency across the drives that SQL Server discovers, but it does not make sense if all are on the same consistency group.

Any experience with this issue or suggestions would be appreciated.


Tags (2)
0 Kudos