I have a primary replica and one secondary. Multiple availability databases. Secondary replica is located at DR site.
For DR testing, is it possible to failover to the secondary replica, make (test) data changes on the secondary (now primary) replica and then failback but without moving back the test data?
I was thinking this may be possible through suspending data movement i.e.
- Suspend data movement
- Failover to secondary (DR server) replica
- Insert test data
- Failback to primary without synchronizing test data
- Resume data movement