Compatibility of Log Shipping in MSSQL and Transaction Log Backup in VEEAM

[mkugler]

I am curious to know whether it is possible to use transaction log backup in VEAAM while still having the possibility to configure log shipping in MSSQL (for the same database that are backed up via VEEAM of course) in order to have VEEAM doing the backup and use the built in replication mechanism in MSSQL to have a standby database at the same time.

My concern is that either truncating the logs via VEEAM during the backup breaks the replication in MSSQL's log shipping or the backup chain is broken in VEEAM so that I can no longer do a point in time recovery in VEEAM or in the worst case neither the backup nor the replication really works.

So if both features do not play nicely togehter is there a possibility in VEEAM to do the replication via the backup of the transaction logs? Or is it at least possible to schedule a recovery in a standby database to test at least the recoverability of the database backups and log files?

Thanks in advance

[foggy]

Hi Max, using multiple tools to handle transaction logs is strongly not recommended. Only a single tool should be used for that, others should operate in copy only mode. For Veeam B&R, there's the corresponding option in the job settings, in case you use native Microsoft SQL Server tools for log shipping. Alternatively, you can do both backup and replication via Veeam B&R and test backups/replicas using recovery verification techniques available there. Thanks!

[nmdange]

You should use SQL Server AlwaysOn Availability Groups to get the database on the standby server, rather than legacy transaction log shipping. AGs are compatible with Veeam backing up the SQL Server transaction logs. And they allow for automatic failover, a lot more useful for HA/DR!