cancel
Showing results for 
Search instead for 
Did you mean: 

Upgraded to R3, VSP Cannot Snap XP Volume, SQL databases skipped

mbjoe
Level 4

We recently upgraded our installation of Backup Exec 2010 to R3. After doing so one of our Windows XP machines is having trouble snapping the drive witht he AOFO option.

The files that we are unable to backup seem to all be SQL Databases on the machine, below are the errors we get. Again this was after upgrading to R3. The machine I'm trying to backup has AOFO agent installed and is a Windows XP machine. We would get the "Not Snappable" warning sometimes in the past but not every backup and the SQL databases were always fine pre-R3.

 

Backup- Server.Domain.comV-79-57344-34083 - AOFO: Initialization failure on: "C:". Advanced Open File Option used: Symantec Volume Snapshot Provider (VSP) for Windows Server 2000 only.

Snapshot provider error (0xE0008523): Symantec Volume Snapshot Provider (VSP) cannot snap the specified volume. Restart the target computer, and then run the job again.

Check the Windows Event Viewer for details.

Backup- \\Server.Domain.com\C:Unable to open the item \\Server.Domain.com\C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\master.mdf - skipped.

Unable to open the item \\Server.Domain.com\C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\msdbdata.mdf - skipped.

Unable to open the item \\Server.Domain.com\C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\mastlog.ldf - skipped.

Unable to open the item \\Server.Domain.com\C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\model.mdf - skipped.

Unable to open the item \\Server.Domain.com\C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\tempdb.mdf - skipped.

Unable to open the item \\Server.Domain.com\C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\msdblog.ldf - skipped.

Unable to open the item \\Server.Domain.com\C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\templog.ldf - skipped.

Unable to open the item \\Server.Domain.com\C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\modellog.ldf - skipped.

BackupV-79-57344-34110 - Note: Resource: "Server.Domain.com" is not snappable. Attempting to back up directly from the source volume.

 

4 REPLIES 4

pkh
Moderator
Moderator
   VIP    Certified

I think you don't need VSP on a XP machine.  Let AOFO choose the the technology that it wants to use (first option), rather than forcing it to use VSP.

By default, .mdf and .ldf files are automatically excluded from backup by AFE.  If you want to backup a SQL database you should use the SQL agent.

mbjoe
Level 4

The job is set up to automatically choose the AOFO technology.

Is there a way to specificly install the SQL Agent? When trying to use the wizard to deploy the agents I don't see an option for SQL.

Simon_B_
Level 6
Partner Accredited

Most importantly you need to have the SQL Agent Option licensed and installed on your BE server. The Remote Agent always has all options included - but they are only activated when properly licensed and configured on the BE Server.

To Backup the Databases without purchasing an SQL Agent you have 2 options:

  • In the SQL Server configure regular Database Dumps that are saved as *.bkf in the file system. Then these files will be backed up by BE
  • Set this registry key: http://www.symantec.com/business/support/index?page=content&id=TECH92375. With a pre script shutdown the MSSQL services prior to the backup, perform the backup and start the services again afterwards

Every other approach (flat file backup with started services, AOFO etc) will render your backups useless as the database files will NOT be consistent

mbjoe
Level 4

We do have the license set and enabled for the "Agent for Microsoft SQL Server", however the job still fails in backing up the SQL databases.

Lately the following error is also ocurring:

Snapshot provider error (0xE000851C): Cache files required for the Symantec Volume Snapshot Provider (VSP) snapshot could not be created. Check that there is at least 50 MB of free disk space, and review the settings for the snapshot that are reported in the job log.

I have it set to save the Cache file to an external drive with plenty of space so once again it doesn't make sense why we are getting the errors.