Bug #74410 Need a Restore point on the Slave database to rollback after a DR test

• Submitted: 15 Oct 2014 22:04
• Reporter: sanjay kumar Raghavendra
• Status: Open
• Category: MySQL Server: Replication
• Severity: S4 (Feature request)
• Version: 5.7
• OS: Linux (RHEL 6)
• CPU Architecture: Any

[15 Oct 2014 22:04] sanjay kumar Raghavendra

Description:
Need a feature in MySQL Replication to create a Restore point on the Slave database instance. This feature will let the DBAs open the database in RW mode for few hours for testing. Once the testing is done, we can rollback to restore point and let replication resume.

The advantages I see with this feature are:

1.During a DR test,  I’d like to be able to open the database in RW 
mode for just a short duration (say 4-6 hrs). Once that testing is 
done, I’d like to flip it back to RO mode. Currently, we have to take 
a dump from Master copy and restore in Slave and then re-setup replication. This consumes significant amount of time. It gets more complicated if the database footprint and/or the size of the databases grows.

2.Testing – Most of the time, the test environments don’t have 
equivalent production data or the size due to security reasons. In 
such cases, it would make sense to have the testing tool connect 
directly to slave copy and do extensive testing for a specific duration. Once testing is done, flip the DB back to RO mode and let it automatically sync-up with Master.

How to repeat:
-

Suggested fix:
Will need a restore point in the slave database to be able to revert after the DR testing is done.