seapro220 wrote:Whenever I first started out trying to understand the Veeam backup process, I changed my backup strategy to only using VBR. What I determined was that for incremental or transactional logging, the VBR job was breaking the SQL restore points - and making that process unusable. I changed my VBR job to NOT flush, but that didn't work. Since then, I'm utilizing the following process -
1. weekly full and rollup of server. that way I have a 'server' image for restores.
2. daily trans,incremental, and weekly sql backup processes. I process them locally on my sql box, but offload them them nightly.
This process provides my ability in SQL to use the Management tools for trans/incremental, and full backup restores for a week at a time.
Not to be 'long in the tooth' - but because of how the file is taken, via VBR, the only process of restore is to restore it as a 'flat' file, and use the SQL mgmt tools to import/create a new db. Kinda sucks and perhaps there's a better way - but I dont think so.
bob.baird.xedo wrote:We are now looking at using Veeam B&R to backup our VM's and I'm curious as to what settings we need to make in the backup jobs to ensure the database backup "chains" wont get broken by the Veeam backup.
foggy wrote:You can successfully restore single database files from backups created by Veeam B&R, no problems with that. Please review the topic above for general recommendations on backing up SQL Server with Veeam B&R.
Users browsing this forum: No registered users and 1 guest