Semi-related, not trying to hijack the thread: I am looking to make a case for the VMWare agent vs. the RAWS agent methodology for our backup strategy.
Aside from the above advantages - and without having any deduplication licenses - Are there any space savings recognized by using the VMWare agent / VM backup method in place of a basic RAWS backup?
(ie. Backing up the same Windows server using both methods, will one backup-set be decidedly smaller?)
Not having the VMWare license or a budget for it, I have not been able to benchmark the two methods for identifying any differences.
Also, is there any advantage to having the VMWare license for VMWare level backups in conjunction with the Application & Database license? If using the VMWare level backup method provides the ability to restore individual files, then we should be able to restore SQL database files if needed?
Or, (I'm guessing here) the VM level backup will not truncate the SQL logs during the backup, so any SQL data file backed up using the VMWare method might not be restorable, unless the database was backed up by SQL and then the SQL generated database.bak file could be restored independantly.
And - Same question regarding Exchange DBs - If using only VMWare level backups do we lose the ability to perform GRT restores?
Solved! Go to Solution.
Thank you for the insight.
What about potential space savings? Are there any differences in space usage for VM backups vs RAWS backups? (Assuming all Full Backups, Thick-Provisioned VMDKs and Simple Disaster Recovery...)