Firstly I have to say that this post was born due to my frustration with VMware Data Recovery. I was lucky or unlucky enough to be target by few different bugs in all releases, up to 1.0.2.
VDR promises to deliver virtual machine disk-to-disk backup and recovery solution with integrated de-duplication that was before only found in expensive enterprise class products.
I use VDR as a backup solution for VMs that do not require more than a backup per month (Operational System, Application Binaries, etc…). Critical application data is backed up by the enterprise class backup system. VMware clearly states that VDR is not a replacement for VCP (VMware Consolidated Backup) or your traditional backup tool.
My intent here is to go through the steps from configuration to limitations, issues and troubleshooting. There is a large collection of documents on the net so the objective here is to put together a key research index for newbie's. I’m not going to re-invent the wheel when someone else already did all the work.
This is always the easy part when talking about VMware products. The virtual appliance is imported from a OVF and with some basic configuration is ready to begin backups. An IP must be configured and a VMDK must be added to the virtual appliance as a target for the de-duplicated data.
@vladan did a great job recording VDR installation process
Two good Step-by-Step posts about deployment from @ccostan
I use a NFS/CIFS enabled SAN so it was easy to decide what path to take to store backups and the de-duplication store. If you are not as fortunate you may consider using one of your old servers running OpenFiller or FreeNAS.
VMware highly recommends that you use virtual disks (VMDKs) or RDMs for dedupe stores since the performance behavior is well-understood and consistent.
How it Works
“Unlike VMware Consolidated Backup (VCB), which is an enabling technology and not an actual data backup product, VMware Data Recovery is a standalone product that creates hot backups of virtual machines to any virtual disk storage attached to an ESX/ESXi host, or to any NFS/CIFS network storage server or device and is not meant as a replacement for VMware Consolidated Backup.”
VDR was built using the VMware vStorage APIs for Data Protection (VADP) and implements a Virtual Appliance (CentOS) and a VI Client Plug-in. The deduplication method used is VMDK block based instead of file based. I am not a storage guy so I might be wrong here but I don’t see how block level deduplication could provide in anyway benefits comparable to file level dedup.
“What VMware decided to implement for VDR dedupe is (take a deep breath) - block based in-line destination deduplication. Deconstructing it means the following:
1. We discover data commonality at the disk block level as oppose to the file level.
2. It is done as we stream the backup data to the destination disk as opposed to a post-backup process.
3. The actual dedupe process occurs as we store the data on the destination disk as opposed to when we are scanning the source VM’s virtual disks prior to the backup.”
“We chose this dedupe architecture because it fit best with what we were trying to achieve with VDR and what the vSphere platform provided to us. What were these reasons? Stay tuned to this space……”
The following two posts from VMware employee Azmir Mohamed will provide you with more in-depth technical details on block based in-line destination deduplication technology.
VDR will not backup virtual machines with Fault Tolerance enabled
VDR does not support VC Linked mode
Virtual Machines with hardware version lower than 7 will take longer to be backed up.
The deduplication feature cannot be disabled so all backups done by VDR are deduplicated
Not compatible with VI3 hosts. VDR requires the presence of a VMware vCenter Server 4
VDR will not backup your VM if it is stored in a RDM not in virtual compatibility mode
VDR is available only for Essentials Plus, Advanced, Enterprise and Enterprise Plus
Each VDR appliance supports only 100 virtual machines
If you know additional limitations let me know and I will include here.
Issues and Troubleshooting
I had few issues with VDR plug-in not being able to communicate to the appliance and also with CIFS shares. As a result I had to re-deploy the appliance and reconfigure the network a number of times. Few of those times I was forced to delete the de-duplication store.
Even the recently baked 1.0.2 release presented similar bugs. Luckily the VMware community is always very involved and helping us to find the solutions.
Snapshot issues have also been identified. In short – VDR leave hidden snapshots behind during the backup process. You will find more information on Scott Lowe’s and Carlos Costanzo blogs.
As mentioned before VDR is still its early versions. VDR is a good step for VMware promising to deliver recovery solutions aligned with de-duplication before only found in expensive enterprise class products. However the product is not mature enough and should not be used as the only backup solution.
I’m still using VDR as a backup solution for VMs and VMDKs that does not require more than one backup per month (Operational System, Application Binaries, golden image etc…). The application data is backed up by our enterprise class backup system.
VMware Data Recovery 1.0.2 Release Notes
VMware Data Recovery Documentation
VMware Data Recovery FAQ
VMware Data Recovery Dedupe Store Setup Guideline
File Level Restore Usage
Thanks a lot for this howto, Andre. It would be more appropriate to create stuff like that as a documenten rather then in a discussion though.
If you found this or other information useful, please consider awarding points for "Correct" or "Helpful".
Wow, this is so helpful
Since I'm using vSphere Essentials, I'm thinking to purchase this separately, how can i do this ?
I love VMware, but their licensing model is driving me crazy. VDR would seem a perfect fit for our large rollout of remote sites. We are doing two host servers at each location with no shared storage. The only real licensing option is standard version, which does not allow the use of VDR.
VMware, please allow some flexibility with your licensing, not everyone fits into the molds that you have created, and we cannot re-design our business processes or enhance our budgets to fit within rigid guidelines..
Based on what I'm seeing here, it does not sound like VDR is ready to replace vRanger? We are looking at options since vRanger 4.0 seems to have several issues right now. We use a file and OS level backup solution for most of our vm's, but we also take full image backups with vRanger once a week, when we can get it to work. (Most of the issues came up when we upgraded to vcenter 4)
VDR seems to have potential for this weekly backup, but it appears to have some bugs? We run 300 vm's right now, it looks like it may take some management to run 3+ VDR appliances.
VDR does File level restore. I've tested it and I[ have done a video in the post too|http://www.vladan.fr/vmware-data-recovery-part-4-how-to-restore-files-inside-of-your-vm-video/].
It's an utility which you download together with VDR from Vmware website, and then copy that file inside of your VM to do a restore. Even if it's not a tool with GUI it's quite easy to manage...
Vladan SEGET - vExpert, MCSA 2003, IT professional and enthusiast.
www.vladan.fr - Virtualization ESX server… how-to, tutorials, videos….
You can follow me on Twitter: www.vladan.fr/twitter
Oh that's a good news
so in that video the VM is Windows VM, how about non WIndows VM such as Linux or Solaris ?
As far as I know Veeam is the only product who can restore individual files from Linux and a few other filesystems.
Veeam fires up a VM instance at the background inside a Windows VM to enable reading other filesystems. It is so clever, I wonder why others cannot do it. They may have been caught up Vranger, Symantec and esxbackup but I am not sure. Update the post if you know.