Do you need to keep some disaster recovery functions or backup data on premises? Would you benefit from a public cloud or hybrid cloud approach? CloudĬloud-based backup and disaster recovery solutions are becoming increasingly popular among organizations of all sizes. The next step in designing a disaster recovery plan is to evaluate deployment options. Defining workloads as Tier 1, Tier 2, or Tier 3 can help provide a framework for your disaster recovery plan. In the event of a disaster, the bank could allow that application to be down for several hours or even a day without having a major negative impact on the business. However, the bank’s employee time-tracking application is less important. Many organizations have multiple RTOs and RPOs that reflect the importance of each workload to their business.įor a major bank, the online banking system might be a critical workload-the bank needs to minimize time and data loss. Once you understand the key concepts, it’s time to apply them to your workloads. Some DRaaS offerings might provide tools to manage the disaster recovery processes or enable organizations to have those processes managed for them. A third party hosts and manages the infrastructure used for disaster recovery. Disaster recovery as a service (DRaaS) is a managed approach to disaster recovery.One last term might be helpful as you consider alternatives for managing your disaster recovery processes and your disaster recovery environment: The restore process is generally considered part of backup rather than disaster recovery. Restore is the process of transferring backup data to your primary system or data center.Once the disaster has passed and your primary data center is back up and running, you should be able to fail back seamlessly as well. Failback is the disaster recovery process of switching back to the original systems.You might fail over from your primary data center to a secondary site, with redundant systems that are ready to take over immediately. Failover is the disaster recovery process of automatically offloading tasks to backup systems in a way that is seamless to users.Or you might decide that losing five minutes or one hour of data would be acceptable. You might need to copy data to a remote data center continuously so that an outage will not result in any data loss. Recovery point objective (RPO) refers to the amount of data you can afford to lose in a disaster.But if a major online retailer loses its inventory system, even 10 minutes of downtime-and the associated loss in revenue-would be unacceptable. For example, if a public library loses its catalog system, it can likely continue to function manually for a few days while the systems are restored. The RTO might vary greatly from one type of business to another. As you look to set your RTO, you’ll need to consider how much time you’re willing to lose-and the impact that time will have on your bottom line. Recovery time objective (RTO) is the amount of time it takes to recover normal business operations after an outage.Understanding a few essential terms can help shape your strategic decisions and enable you to better evaluate backup and disaster recovery solutions.
0 Comments
Leave a Reply. |