Get ready to test drive StoreGrid's Disk Image AutoMerge

If you are a system administrator dealing with a multitude of incremental files for restoring a system during a crash or serious about maximizing disk usage and looking for rapid data recovery, StoreGrid’s Automated Synthetic Disk Image AutoMerge feature could provide the right answer, an exciting feature, our engineering team is working hard on to include it in our forthcoming Service Provider Edition v4.2.5 release.

StoreGrid’s already existing Disk Imaging capabilities delivers continuous incremental backup of complete live systems to a local or remote online data center. In case any disaster strikes, restore remotely within minutes from any point-in-time incremental to a hardware independent physical or virtual server either local or at remote data center.

StoreGrid’s Disk Image Backup protects your Windows server systems by combining disk imaging technology and StoreGrid Block Tracking Technology to capture only the delta changes that has occurred on your system after the first full disk image backup.

Here’s a graphical illustration to understand the Disk Image Backup feature in StoreGrid.

The Synthetic Disk Image AutoMerge feature

The Synthetic Disk Image AutoMerge feature will leverage the already existing disk image backup and bare metal recovery capabilities of StoreGrid. Currently StoreGrid’s instant restore capabilities ensures the rapid recovery of volumes recovered fully in minutes. The same capability will have users directly boot up a system and have it up and running from the merged VHD images within a few minutes, offering practically no downtime.

How does the AutoMerge work?

There are two parameters to the AutoMerge feature.

1. Version file count – an offset value to trigger the AutoMerge in the server.

2. Retention count – the no of latest incrementals to be retained in the server.

To explain this much better, as an example, let us say that the user wants the AutoMerge to be triggered when the no of versions reach 7 and the no of incrementals to be retained in the server as 3.

In the above illustration, the first merge is triggered when the no of versions reach 7. The full backup and the incrementals are merged as a consolidated VHD and the remaining 3 incrementals retained in the server.The next merge happens as and when the version count again reaches 7 to give merged VHD # 2 which is the consolidated VHD # 1 with versions 5, 6 and 7. After the merge, the versions are deleted to retain only 3 incrementals.

The Synthetic Disk Image AutoMerge feature is specifically designed with today’s business models in mind, which use environments where data storage and network bandwidth are a premium, where gigs of data flow between remote locations, requiring large storage capacities and huge investments to cover bandwidth costs. Here are some of the benefits users can expect out of this:

  • Less Time and Space – The time and space requirements are lower since volume changes are periodically merged on top of existing full/synthetic backups.
  • Easy and Instant Restores – System restore times are dramatically slashed, as StoreGrid gets crashed systems up and running from any of its latest merged VHD.
  • No separate conversion tool needed — StoreGrid also eliminates the need for any separate conversion tools for converting the image  as StoreGrid stores the backups as VHD format which itself is bootable in Virtual Servers like Hyper- V, VirtualBox.
  • More ROI with huge savings – Huge savings on resources, bandwidth usage, maximum utilization of disk storage and faster recoveries, resulting in more dollars saved.
  • Complete Automation of Disk Backup Management – Avoid the hassle of  keeping track of multiple full backups with easy management and user triggered settings.

 We are convinced that the Synthetic Disk Image AutoMerge feature will greatly benefit your business. So stay tuned for our StoreGrid v4.2.5 release…

Share and Enjoy

  • Facebook
  • Twitter
  • Delicious
  • LinkedIn
  • StumbleUpon
  • Add to favorites
  • Email
  • RSS
  • ciaran

    Is this feature now available in 4.2.5? If so can you tell me where to find it???