Backing up your enterprise data and applications is a no-brainer. Most everyone has experienced that moment of panic when a hardware failure sinks in and you realize the project you’ve been working on is never coming back. When we’re talking about an entire company’s IT infrastructure, an outage means dozens or hundreds of projects with hefty downtime costs.
You might have a backup plan in place, but backups are not disaster recovery (and disaster recovery is not ideal for backup, either). Backup is intended as a long-term, low cost solution for storing data, applications, configurations, etc. Disaster recovery is designed to get only the most critical portions of your IT infrastructure back online as fast as possible.
That means storage and bandwidth costs tend to be higher with DR, but recovery times are measured in minutes rather than hours or days. Let’s take a look at the other ways the two methods differ.
One of the questions that we are constantly asked is "How do I migrate my existing machines to the cloud?" Several vendors have answered this question by developing software solutions to aid in this process, but they can be very costly and complicated to implement. Fortunately, there is a simple and free method that has been adopted by practically all virtualization platforms: OVF.
As a busy sysadmin, finding the time to package up and transfer a virtual machine can be difficult enough, so the last thing you want is for the import to fail. Below are some best practices to avoid the most common issues we see when exporting OVF files.