SQL Backup - Recommendations ?

[Dmont]

We're in the middle of redesigning our SQL backups and would like to integrate it fully into Veeam. We have two questions that I hope you can help us with:

1: Our databases are already encrypted via SQL - should the Veeam backup job also be encrypted or is encrypting already encrypted data going to cause an issue ?
2: What is the recommendation for transaction logs vs full backups, use Veeam only or in conjunction with SQL backups ?

Thanks in advance.

[Mildur]

Hi David,

How are you planning to perform backups; Image-level backups or using the Veeam MS SQL Plug-in?

1.) Encrypting the SQL data a second time will not cause any issues, at least not from a Veeam perspective. Please note that backup encryption with our Microsoft SQL Server plug-in is available starting with v13.

2.) I assume that by "SQL Backups" you mean the built-in backup feature of Microsoft SQL Server. Keep in mind that taking backups with another product will interfere with the transaction log chain. If you decide to use the transaction log backup feature from Veeam Backup & Replication, I recommend using Veeam Backup & Replication exclusively for both full and log backups.

If you already use encrypted databases, then I think you are already aware of the restore considerations: https://www.veeam.com/kb2006

Best regards,
Fabian

[PetrM]

Hello,

Adding my 2 cents:
1. I would not enable backup job encryption, as I don't see much benefit in encrypting the same instance of data twice. In some cases, encryption operations may increase CPU load on the source side, for example, on the database server in the case of the SQL plug-in, or on a proxy server in the case of image-level backups.

2. I do not recommend using third-party solutions. Please keep in mind that you can use the plug-in to create native SQL backups at the SQL Server level and even create SQL Server Agent jobs directly from the plug-in UI. However, if you mix image-level and plug-in/native SQL backups, make sure that one of the tools operates in Copy-Only mode. This prevents backup chain corruption in the event of interference between two different solutions.

Thanks!

[Dmont]

Thank you Mildur and PetrM, the information provided is exactly what I was hoping for.

I can confirm (point 2 from Mildur) that when I say "SQL Backups" that I mean the native, built-in, SQL backup feature of Microsoft SQL Server.

One additional point that I forgot to add when creating this thread - Our databases sit in a SQL Availability Group. Do you know if this adds complexity/issues when using Veeam as the primary backup product ?

Thanks again.

[PetrM]

Hi David,

Nope, this does not add any complexity. Please refer to our documentation:
-> VM image-level
-> Physical machines
-> Plug-in

Thanks!