Tuesday, 27 October 2015 00:00

Making Virtual Server Recovery-In-Place Viable

Rate this item
(0 votes)

Backup technology for virtualized environments has become increasingly more advanced. Many organizations have implemented backup applications which are specifically designed to efficiently backup data in a virtualized environment without causing any disruption to application performance. In addition, some backup applications, like Veeam, now allow for data residing on a disk based backup target to be used as a boot device to support instant VM recoveries.

Boot From Backup

Generically referred to as “recovery-in-place”, this feature gives administrators the option to point a VM to the backup data residing on a disk partition (typically a backup appliance) so that a failed VM can be more quickly recovered. The idea is to use the backup data as a temporary boot area until a full data restore can be completed on to a primary storage resource.

Storage IO Mismatch

On its face, this looks like a great idea – backup storage also facilitating near instant VM recoveries. But the challenge is most disk backup appliances are tuned to handle backup workloads, not the random IO that production applications produce. The other issue is that most disk backup appliances are designed for storage capacity efficiency. They are often configured with high density (4 TB) drives that run at slow (5400 RPMs) speeds. Between these two factors, the added latency could make for very poor application response times.

Lastly, many disk backup appliances are now using some form of data deduplication. While this is a great way to efficiently store backup data on disk, if deduplication processes are running while production data is mounted on a disk backup appliance, storage IO throughput may come to a grinding halt. Especially when the above two factors are also in play.

Balanced Hybrid Backup

One way to circumvent these issues is to consider low cost storage technologies that provide a mix of SSD resources along with high speed disk drives. Some of these offerings are similar to the hybrid flash arrays on the market but are available at a fraction of the cost. These systems can be used as a disk backup target to facilitate rapid backups while also serving as a platform to support data recovery-in-place capabilities. For example, a small portion of SSD could be allocated to backup data for business critical VMs. That way if a VM needed to be quickly recovered, this area could be used to support production workloads and the above latency issued could be avoided.

These storage systems could also be used in conjunction with existing deduplication disk backup appliances. Backup managers could stage certain business critical data sets to the hybrid array first and then schedule a secondary backup job to the dedupe appliance to support extended retention on disk.

Reference: http://storageswiss.com/2014/06/04/making-virtual-server-recovery-in-place-viable/

Last modified on Tuesday, 27 October 2015 10:46
Data Recovery Expert

Viktor S., Ph.D. (Electrical/Computer Engineering), was hired by DataRecoup, the international data recovery corporation, in 2012. Promoted to Engineering Senior Manager in 2010 and then to his current position, as C.I.O. of DataRecoup, in 2014. Responsible for the management of critical, high-priority RAID data recovery cases and the application of his expert, comprehensive knowledge in database data retrieval. He is also responsible for planning and implementing SEO/SEM and other internet-based marketing strategies. Currently, Viktor S., Ph.D., is focusing on the further development and expansion of DataRecoup’s major internet marketing campaign for their already successful proprietary software application “Data Recovery for Windows” (an application which he developed).

1 comment

  • Comment Link Jimmy Friday, 10 March 2017 01:17 posted by Jimmy

    Hello, I enjoy reading through your article post.
    I wanted to write a little comment to support you.

Leave a comment

Make sure you enter the (*) required information where indicated. HTML code is not allowed.