Preferred backup method for VM's running SQL databases
Windows 2008r2 standard Master and Media servers running NBU 7.6.0.4
I'm trying to reclaim some disk space on our backup targets, and one area I see potentially significant savings may me in the backup of several VM's we have that run SQL databases. There are approximately 60 such servers in our environment.
So, what is happening is that the VM policies are backing up the VMDK file (VMware policy type), which is also capturing the volumes which contain the sql databases. But, we are also running daily MS-SQL-Server policies for each of the sql databases that reside on these servers, so we are capturing this data twice.
Since we have quite a few of these, and they are VM's, I'd like to exclude the database volumes from getting captured in the VMDK backup, in the policy. But, since these VM's are SQL servers, they do require the NBU agent to be installed, which means I could also use the standard exclusion lists in the client properties to do this as well (much more time and work).
Choice 1). Use the "exclude data disks" option and continue to back these sql servers up using a VMware policy
Choice 2). Move these SQL vm's into an MS-Windows policy type, and use the client's exclusion list to omit backup of *.ldf, *.ndf, *.mdf files.
Please let me know your thoughts.
Thanks all!
Todd
Todd,
VMware policy "Exclude Data Disks" should work, and is by far the cleanest method (single click to cover entire policy). But, all of your VMware VMs would have to be OK with only C: drive backup... if some of them need C: and D: (as an example), this method would not work, since D: is considered a data drive.
Another thing to be aware of ...
When using VMware policy on a SQL host without selecting SQL protection checkbox, the backup will trigger the whole stack of VSS providers (via VADP -> VMware Tools), which includes the SQL VSS provider. The resulting VSS provider invocation will update the Last Backup Date field for each database, as if a SQL backup had been taken, unaware that the VMware policy did not take a SQL backup. If your actual SQL backup method (NBU SQL Agent as an example), is a Full, then this will not matter, but if it is a Diff, it will result in a broken backup chain, since the Diff will be based off of a Last Backup Date that never occured.
To work prevent this, you can disable the SQL VSS Writer service on each SQL VM that is effected, as long as your actual SQL backup method does not depend on it (NBU SQL Agent does not use VSS unless Snapshot Client is selected).
Ken W