Feature Request: SQL Logfile handling

[Clemens Bertram]

Hello Veeam-Support,

we are evaluating Veeam Backup and Replication as single Backup-Solution.
During our Tests we had some minor or major handling issues:

1. Move VM to different Job
--> Log-File Backup issues
"Failed to prepare guest for SQL Server transaction log backup Details: Job ZZZZZZZZ owns SQL Server transaction logs backup"

By Design --> Veeam KB 2029 provides an Workaround.

But we have to wait at least one Day for the next Log-File Backup! --> Veeam Support stated that this behavior is intended. But Enterprise SQL-DB's can be quiet Log intensive!

2. Log-Files stored temporarily on the Source VM

By Default the Log-Files are stored on the Source VM until they get transferd to the Backup-Repository.
https://helpcenter.veeam.com/backup/how ... ackup.html

To cope with this solution we have to map large Disks to SQL-Server VM's




Will SQL-Backup redesigned for future Releases?


Kind Regards

[foggy]

But we have to wait at least one Day for the next Log-File Backup! --> Veeam Support stated that this behavior is intended. But Enterprise SQL-DB's can be quiet Log intensive!

Discussed in adjacent thread.

2. Log-Files stored temporarily on the Source VM

You can redirect logs to another local disk via registry, might help.

[Clemens Bertram]

Hi Foggy,

sorry but the value 0 is not possible.We discussed that with the Support.
The Value "0" would fix our Problem.


We configured the different Log-Backup Location.
But the problem is that the Logfiles stay on the same VM. Redirection to an Network-Share would be an solution.

Greetings
Clemens

[foggy]

sorry but the value 0 is not possible.We discussed that with the Support.
The Value "0" would fix our Problem.

Answered in another thread.

We configured the different Log-Backup Location.
But the problem is that the Logfiles stay on the same VM. Redirection to an Network-Share would be an solution.

Understood, feature request accepted.