- Posts: 17
- Liked: 1 time
- Joined: Apr 13, 2016 2:42 pm
- Full Name: Sebastian S
I was wondering if there is a document for best practices for SQL Server or tipps. We have a backup Job that runs for almost a year by now, but I should look for best practices within Veeam Backup & Replication, Options that the staff of Veeam would recommend.
I looked through the Forum and found this link:
veeam-backup-replication-f2/is-there-a- ... hilit=best practice SQL
Sadly I couldn't make much out of it, because I couldn't find the best practice guide in solution architecture and I don't know if this is the right Whitepaper I am searching for.
Then I found this Whitepaper:
http://veeampdf.s3.amazonaws.com/guide/ ... ke2qyJM%3D
which looked promising at the beginning but when I think about best practices I always think of a solution or recommendation, but this pdf just explains the different Options without giving a clear recommendation which Option should be used. It was helpful in understanding the General Options, but still it Looks like there is no best practice provided by Veeam itself.
Following Options are selected right now:
Backup proxy -> Automatic Selection
Restore Points to Keep -> 7
Configure secondary destinations for this Job is enabled
Storage Advanced Options:
Backup Mode -> Incremental without synthetic full backups
Active full backup: Enabled every first monday monthly
Data reduction: all three Options enabled
Compression Level: optimal / Local target
Changed block tracking: both Options within the tab vSphere enabled
Enable application-aware processing: enabled
Applications -> Require successful processing
Transaction Logs -> Process Transaction logs with this Job
SQL -> Truncate logs
Oracle -> Archived Logs: do not delete
Options I didn't mention were disabled. So far I only know that Application Aware processing must be enabled and that the recommended Options also work with SQL Server. What gives me some headaches are the truncation logs. One Option is that Veeam does the backup for us and the other Option is that we can do our own SQL backups. I bet the better Option is letting Veeam handle this.
What should be changed, what have I missed?
- Posts: 345
- Liked: 91 times
- Joined: Dec 13, 2015 11:33 pm
- Product Manager
- Posts: 5136
- Liked: 443 times
- Joined: May 19, 2015 1:46 pm
- Veeam Software
- Posts: 17931
- Liked: 1512 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
Users browsing this forum: No registered users and 13 guests