We're studying the impact of migrating a big SQLServer (ERP/High transactional profile) from a physical server to a virtual one (Several TB of databases).

We've been happy Veeam users for years now, and we are already using Veeam to backup some small SQLServer Vmware VM, with periodic log backup (every hour).

All is working perfectly, but in case of our big sqlserver, I would have somme reserves, regarding the capacity of veeam to backup huge amount of logs.

In Veeam, the process of log backup uses a temporary local disk space to copy log files, before sending them to the veeam proxy server.Today, we configure this temporary local disk space to redirect to another local disk (SQLTempLogPath in registry).

Our big sqlserver is able to generate between 1GB and 30GB per hour (in normal condition), and even 100GB/200GB of logs when DBA launch special REORGANIZE index operations...

So what would happen to my Veeam Log Backup :=> Several long minutes to duplicate locally all the logs=> and others several long minutes to send them by the network to the veeam server.

Does someone already experiment such a case in production ?Do you know if there is a way to bypass the local log copy ?