Data loss can happen at any time—it could be a natural disaster, cyber-attack, or human error. While you might not be able to predict what the cause of data loss will ultimately be, you can take proactive measures to secure and protect data. After all, it might be more expensive than you think. According to a Verizon study, even a small data breach with a 100 files or less can cost a business between $18,120 and $35,730.
With that in mind, have you ever wanted a BDR for Barracuda Intronis Backup? Why not set up your own? You may have customers looking for faster recovery times, and you more than likely already possess the tools to make this a reality.
How to set up BDR for Intronis Backup
Rather than backing up Windows server or PC images to a local NAS, take a Windows 10 PC with a large amount of storage and the Hyper-V role turned on. Set up a share on that PC called Backup, and have Intronis Backup image sent to that share.
Image backups utilize reverse increment technology, and the most recent backup is a .VHD file. This file can easily be booted in Hyper-V. Important — Intronis Backup needs the .VHD file to be left alone for future backups, so make a copy to a different directory when you want to boot the .VHD file.
In a customer environment, this can be a great way to quickly bring a failed server back online using the last backup image as long as the Windows 10 BDR system has enough RAM and CPU to handle the workload.
I have tested this successfully with a Windows 10 system having 32GB of RAM, i7 processor, and SSD storage. The guest server (within Hyper-V) bootup was fast, and the server had plenty of horsepower to operate on. I did have to run the four Microsoft Bootrec.exe commands to boot successfully. However, once you complete that process once, it’s a breeze to do in the future.
Another perk of this setup is while running the restored server via VHD, backups can continue to run (as long as you copied the VHD file to a new location on the drive before booting).
When you are finished fixing the failed physical server, you can reload the now fixed server with the Hyper-V role. Simply migrate the guest server back utilizing Hyper-V services, making a smooth cut-over back to the original or new hardware (with minimal downtime).
Photo: Olivier Le Moal / Shutterstock.