One way is to do a backup of the virtual machine via vCenter Server, either with GRT enabled or disbaled, depending on the servers profile. As far as I understand Backup Exec there are two ways of backing them up, I wonder what the recommendations are.
We have one vCenter Server and about 15 servers (all windows 2008 R2) which need to be backed up.
I'm evaluating Backup Exec 2012 as our new backup software and I wonder, what would be the best way to backup our virtual environment. Has anybody come across this issue before and is aware of a resolution or a work around?
When the backup job completes the consistency check the snapshot has gone and the backup fails. However the backup sevrer never tells the database server that it has completed the snapshot, so volsnap times out saying that the storage could not grow in time, and it deletes the snapshot. What I think is happening is that the backup job initaites a VSS snapshot on the database server, and then starts the conisitency check part of the backup. If I disable the consistency check component of the backup job then the job starts the backup component immediatly and the job completes successfully. I have changed the selection list of the job to only backup a small database on this server and the backup completes successfully and there is no entry from the volsnap source about deleting snapshots. Then at 2:22:20 PM the job completes with the following: Job ended: Friday, 27 December 2013 at 2:22:20 PM Completed status: Failedįinal error: 0xe00084af - The directory or file was not found, or could not be accessed.įor additional information regarding this error refer to link V-79-57344-33967 Internal database snapshot has split point LSN = 00002352:00019f74:0001 and first LSN = 00002352:00019f73:0001.Īt 2:22:06 PM the backup component of the job starts and finishes list the following warning: WARNING: "SVR-SQL-01\IMAGING" is a corrupt file. Elapsed time: 0 hours 27 minutes 13 seconds. Consider reducing the IO load on the system or choose a shadow copy storage volume that is not being shadow copied.Į: is the drive that the database file is located and I have checked and I/O load is low on that drive at the time of the snapshot.Īt 2:22:05 PM the SQL server logs this: DBCC CHECKDB (IMAGING) WITH physical_only executed by DOMAIN\BackupExec found 0 errors and repaired 0 errors. No user action is required.Īt this stage the backup job goes to 'Queued' on the job monitor in Backup Exec.Īt 2:08:03 PM event ID 25 from source volsnap logs this entry on the database server: The shadow copies of volume E: were deleted because the shadow copy storage could not grow in time. Transport mode 'san' was used for the disk 'S-MSSQL-2_5.vmdk'īackup Exec has discovered and protected 'C:' on virtual machine '\\'.īackup Exec has discovered and protected 'D:' on virtual machine '\\'.īackup Exec has discovered and protected 'E:' on virtual machine '\\'.īackup Exec has discovered and protected 'F:' on virtual machine '\\'.īackup Exec has discovered and protected 'G:' on virtual machine '\\'.īackup Exec has discovered and protected 'H:' on virtual machine '\\'.īackup Exec has discovered and protected 'Volume). Transport mode 'san' was used for the disk 'S-MSSQL-2_4.vmdk' Transport mode 'san' was used for the disk 'S-MSSQL-2_3.vmdk' Transport mode 'san' was used for the disk 'S-MSSQL-2_2.vmdk' Transport mode 'san' was used for the disk 'S-MSSQL-2_1.vmdk' Transport mode 'san' was used for the disk 'S-MSSQL-2.vmdk' One of those two servers is backupped fine, but not the other one.
We have a few MSSQL server wich are backupped.
I am looking for a solution for the following problem.