AppliedOperations32 min
Disaster recovery and business continuity
How mainframe sites survive losing a data centre or having data corrupted: RPO, RTO and business impact analysis, synchronous and asynchronous replication, backups and virtual tape, GDPS at concept level, consistent recovery of subsystems and batch, and realistic DR testing.
What you will be able to do
- Explain RPO, RTO and business impact analysis, and how they drive DR design and cost
- Compare synchronous replication, asynchronous replication and point-in-time backups, including what each does not protect against
- Describe at concept level how GDPS and consistency groups support a controlled site switch
- Plan for consistent recovery of subsystems and batch, and recognise common DR test failures
Lessons
- RPO, RTO and business impactDisaster recovery starts with two business questions: how much data can we afford to lose, and how long can we be down? A business impact analysis answers them per service, and…
- Replication, backups, tape and GDPSData reaches the recovery site in two broad ways: continuous disk replication, synchronous or asynchronous, and point-in-time backups to disk or (virtual) tape. Automation such…
- Recovering consistently and testing DRA DR site with the right disks is not yet a working business. Recovery needs a consistent restart of subsystems and batch, clear roles and runbooks, and regular realistic tests…
Track your progress and earn a certificate.
Free account, 15 quiz questions for this subject.