Make a Regional Disaster Recovery Plan
Preparing for potential disasters is key for large and small organizations alike. “Enterprises need a disaster recovery (DR) strategy to help minimize the impact of disruption and get the business back up and running,” says Marcel Hergaarden. And, “that strategy should include a backup site to which operations can temporarily switch over.”
In this article, Hergaarden describes key elements of a regional disaster recovery plan, including the following metrics:
- Recovery point objective (RPO), which is the maximum period of data you can afford to lose.
- Recovery time objective (RTO), which is the maximum period of time until you need to be back up and running.
He also looks at how a Kubernetes-based solution can help automate recovery processes. “The system administrator manually triggers the process, but once it’s in motion, applications and their configurations and namespaces are automatically replicated back to your production environment,” Hergaarden says.
Learn more at The New Stack.
Related content
-
Hyper-V failover with Azure Site Recovery
Back up Hyper-V with Azure Site Recovery and prepare for failover. -
Business continuity management
We take a look at the new business continuity service from Azure and show how to use it. -
Of Earthworms and System Administrators
I'm fascinated by the stories of disasters and near disasters related to me by my IT peers, especially those involving backups – or the lack of backups, as is so often the case. -
Recovering from a cyberattack in a hybrid environment
Restoring identity is an important part of disaster recovery, since it lays the foundation for restoring normality and regular operations. We look into contingency measures for hybrid directory services with Entra ID, the Graph API, and its PowerShell implementation. -
Exploring the Relax and Recoverbackup and rescue system
Relax and Recover (ReaR) generates an appropriate rescue image from a running system and also acts as a migration tool.