I've looked around the forums and I haven't found anything on the current version of Veeam and I'm curious what the current thinking is on using Veeam for database backups. From the documentation I've read, it seems that it will now take transaction log backups after the full snapshot so it does support point in time database restores to whatever interval we want (15 minutes in our case). It does not seem to allow different log backup times for different databases. More of a one size fits all approach. Our networking team is pushing hard for us to use Veeam for our database backups as they constantly complain about the disk space usage of growing databases and backups. Since Veeam takes snapshots that are only the changes in the VM from the last snapshot, they save a lot of disk space and they see this as a big win for database backups. I'm less comfortable with giving up native SQL Server backups. It means I will have to depend completely on the networking team to test restores, etc. I'm also concerned about what happens if one of the snapshots in the chain is lost or corrupted. Does that make the backup unusable?I might very well be overly paranoid about this but I'd love to hear opinions from the community.Thanks,-Tom
↧