Disaster recovery (DR) describes the process of securing and protecting your enterprise from any major catastrophic events, such as power outages, hurricanes, severe thunderstorms, flooding, other acts of God, and even attempts to hack into your infrastructure. As perhaps the most critical form of security your enterprise needs, DR lets your mission-critical functions return to a state of normalcy after a disaster.
There are many components that can be used to help ensure the safety of your data and other information in the event of a disaster. But the most important way to be effective is to have a disaster recovery plan (DRP) that is always kept up-to-date. The key idea is to be able to be back up and running after a disaster has passed just as things were before. In order to make this happen, you must know where all the vulnerabilities of your unique enterprise are, consistently test and upgrade the DRP as needed, and know in prioritized manner how each machine and how all activities rank within your infrastructure.
Another crucial aspect of the DRP is knowing precisely how every single aspect of your enterprise would be affected in the event of a disaster. Your IT staff will need to know every operating procedure, exactly how much storage you have, exactly what kind it is, and exactly where it is all located.
Your IT team should also be in charge of putting together a contingency plan in the event your mission-critical functions do not come back online within a reasonable amount of time. This means understanding the level of integrity all your data has now, and being able to ascertain how much it has after a disaster has struck so it can be repaired if need be. Finally, your IT team should come up with a shorter term DRP that will allow them to get the essential framework back up while the continue to work on regaining access to remaining data, apps, software, cloud, and other virtual storage.
Using primary and secondary storage is table stakes when it comes to maintaining all of your important files, software, applications and other data. The base approach is to initially create your architecture and infrastructure with both, but if you do not yet have secondary (back up) storage, now is the time to install it. Here are a few things that both your primary and secondary storage should provide your IT team in the event of a disaster—and keep in mind, your secondary storage will protect everything you have stored in your enterprise cloud or anywhere else virtually.
Taking only a few seconds to create, snapshots should be your first line of defense, as these store blocks of data that have been altered, which won't affect the performance of your infrastructure, including your enterprise cloud. The process of creating and recovering from VM-level snapshots, such as those available on Tintri, reduce wide area network (WAN) usage by 95 percent. By testing your snapshots as soon as you have them available to you—and by testing them frequently using replica snapshots and local clones on your secondary or mirror site—you won't impact performance or production within your enterprise.
Using the Tintri Automation PowerShell Toolkit, which includes Cmdlets (command-let) and the Tintri vRealize Orchestrator Plugin when deploying your private enterprise cloud will create a streamlined infrastructure and enhanced agility while lowering your overhead and automating your workflows. This means you can set up a variety of snapshot policies to each individual virtual machine (VM) for disaster recovery replication purposes. This will allow you to experience zero recovery point objective (RPO), and less than 30 seconds of recovery point objective (RTO).
Using Amazon Web Services (AWS) or IBM Cloud Object Storage for your secondary storage, you'll be increasing the availability of all your data, software, apps, and any other information within your primary storage. When you use Tintri to connect to AWS or IBM secondary storage, everything is transferred and stored on a per-VM basis. That means your data can deduplicate (dedupe) and compress in the most efficient way for cloud computing environments, including your enterprise cloud. Connecting your primary footprint to AWS or IBM's secondary storage also allows you to configure your own policies on any schedule you like, with the retention period and replication target of your choice.
With Tintri Cloud Data Protection and Recovery for Data Centers, you can set RPOs as frequent as every minute of the day, or any other time period or schedule of your choice. This data protection for disasters also enables replication across every site you set up for using a remote disaster recovery location, or from a single source to as many as four different locations. You can choose which model best suits your enterprise cloud and the rest of your infrastructure.
Tintri covers everything you need to know about disaster recovery and recovery plans, from the use of snapshots and RESTful APIs to the use of AWS or IBM Cloud Object Storage and much more. Check out our “Essential Guide to Disaster Protection and Disaster Recovery” to learn more about how Tintri can simplify your data protection within virtualized spaces in this simple, easy-to-understand guide.
Unique control with VM-level actions for infrastructure functions including snapshots, replication and QoS make protection and performance certain in production, and accelerate test and development cycles.