Hi. Welcome to Ingram Micro.

Please choose your role, so we can direct you to what you’re looking for.

If you’d like to learn more about Ingram Micro global initiatives and operations, visit ingrammicro.com.

Are you doing disaster recovery wrong?

Learn how to overcome disaster recovery challenges once and for all

January 17, 2020

Most organizations have some form of backup in place to give the illusion they’re protected in the event of disaster. Unfortunately, when disasters do happen, the reality is that recovery is often messy, time-consuming and costly in every sense of the word.

4 disadvantages of traditional disaster recovery (DR)
It’s expensive—Consider going through all the effort of building a data center and then facing the decision to build a second one for backup and recovery. An organization must purchase hardware, software, pay for the physical space to house everything and more.

It’s slow—When disasters occur, it’s critical that recovery happens quickly. Unfortunately, there’s often a lot of configuration needed with compute instances and networking before things are back up. It can take days and multiple steps for an environment to be stable enough for use.

Replatforming issues—Where native AWS services are involved, replatforming to EC2, S3, etc. will be necessary. This process is time-consuming and complex.

It’s unproven—Testing the DR process with a simulated disaster can be quite valuable. However, many traditional DR solutions don’t allow for non-disruptive testing. Rather than interrupt employees and the production environment, most organizations hope for the best when it comes to the efficacy of their backups.
 

VMware Cloud (VMC) on AWS: DR done right
VMware has an answer for organizations seeking effective DR solutions. Named VMware Site Recovery, it uses:

  • VMware Cloud on AWS as the target DR site. As a robust public cloud offering, AWS has several inherent benefits. Since Amazon has many geographically dispersed data centers, data is well protected in different regions. Additionally, Amazon maintains robust data center security standards along with redundant power to ensure their servers are secure and always accessible. By leveraging VMC on AWS, organizations can avoid putting together a separate data center (along with all the associated costs) for DR, saving time and money.
  • Site Recovery Manager (SRM) for DR orchestration, automation and testing. During failovers, SRM automatically powers on VMs, runs scripts, maps networks, and spins up compute nodes if needed. To test that a DR plan is effective, Site Recovery allows for non-disruptive testing.
  • vSphere Replication to replicate data from the main site to the DR target. Because both workloads are on VMware, there’s no need for replatforming.

All said, VMC on AWS gives organizations a truly effective DR solution that can be trusted to meet or exceed Recovery Time Objectives (RTOs) of business-critical applications. If you’d like more information on how to build effective DR solutions for your customers, please contact the appropriate VMware Market Development Executive for your territory: