We have been using Veeam for about two years now and so fare we like the software very much.
We do however have enormous issues with Veeam when we are trying to do a backup of our physical SQL cluster (failover).
The job fails with the following error:
Code: Select all
Error: The system cannot find the file specified.
Failed to open I/O device
Failed to open emulated disk.
Failed to open disk for read.
Failed to upload disk.
Agent failed to process method {DataTransfer.SyncDisk}.Code: Select all
The shadow copies of volume L: were deleted because the shadow copy storage could not grow in time. Consider reducing the IO load on the system or choose a shadow copy storage volume that is not being shadow copied.we created a support case (case ID: 03607055) and got a few points and possible work arounds.
The two servers are "twins" so to speak and the volumes are as follow:
Server 1 (The one that has the Vonsnap error)
C:\ - 156 GB (OS Win 2012 fully patched)
D:\ - 2,4 TB (High Prio DB's) (Free space 26%)
L:\ - 2,5 TB (High Prio DB's logs) (Free space 41%)
S:\ - 17,2 TB (Low Prio DB's) (Free space 27%)
X:\ - 5,4 TB (Low Prio DB's logs) (Free space 44%)
Server 2
C:\ - 156 GB (OS Win 2012 fully patched)
D:\ - 2,4 TB (High Prio DB's) (Free space 37%)
L:\ - 2,5 TB (High Prio DB's logs) (Free space 79%)
S:\ - 17,2 TB (Low Prio DB's) (Free space 16%)
X:\ - 5,4 TB (Low Prio DB's logs) (Free space 44%)
The Veeam backupjob has been configured as a SQL failover job - https://www.veeam.com/kb2463
Backup Mode: Entire computer
When we run the job (around 500-700 MB/s), the Volsnap error occurs on the L:\ after about 8-9 hours. The Veeam backup job is handling the volumes in this order: C:\ -> D:\ -> S:\ -> L:\ -> X:\.
As you can read the Veeam job is not processing the volumes in an alphabetic order. If the job could handle the volumes in alphabetic order, then our problem would be resolved. This how is not possible according to Veeam support.
Backup mode: Volume
We then tried to use volume backup instead, first try was just D, L, S, X - But the Volsnap happened again.
We then decided to split the job in two (as instructed by Veeam Support). This however resolves the issue with volsnap, but introduces another issue with the SQL log backup.
The first job is processing D:\ and L:\ the second job is processing S:\ and X:\. - It's the second job that fails with the warning:
Code: Select all
Failed to prepare guest for SQL Server transaction log backup Details: Another job is currently backing up SQL transaction logsAll we want is backup of the SQL DB and the logs (there is about 300 DB's in total)
Has anybody experienced the same challenge? If so, did you resolve it and how?
Best regards
Christian
