Hello --
We are running release 6.10 on an HP-UX cell manager. A typical backup involves going to a D2D, image, or VLS, incremental, library. After the initial backup is complete, a copy to LTO tape is subsequently done.
One of the client systems is a Microsoft Windows 2012 Standard x86_64 server that is running Microsoft SQL 2008R2 on it. The Full and Incremental backups that are done for the server includes the /CONFIGURATION and operating system, C:\, drive. Among the files that are included in these backups are the log files for the database server. These are not the .trn files that are affiliated with the database, rather these are the ones associated with the SQL Server application.
The database server does native Full, Differential, and Transaction log backups to another local drive. Weekly snapshots of the drive are done to two LeftHand systems, and are not included in the Data Protector backups.
I have been getting reports the database Differential backups periodically fail. I looked further into the issue, and according to colleagues that I have spoken to, it appears that Data Protector is using VSS handles. When I rescheduled the Data Protector full backup on a different night than the SQL Server Full backups, the SQL Differential backups completed successfully.
My questions are the following:
1. Am I correct in saying that Data Protector uses VSS handles during its backups?
2. If the above is true, what step(s) can I take to have Data Protector be able to do its backups without interfering with
the SQL Server jobs?
Thanks.