Backup Exec 10.x Microsoft SQL backups that have VSS for Advanced Open File Option (AOFO) enabled may not protect a database file due to an invalid path stored within SQL.

Article:TECH48894  |  Created: 2006-01-24  |  Updated: 2014-02-13  |  Article URL http://www.symantec.com/docs/TECH48894
Article Type
Technical Solution


Issue



Backup Exec 10.x Microsoft SQL backups that have VSS for Advanced Open File Option (AOFO) enabled may not protect a database file due to an invalid path stored within SQL.

or

SQL backups may fail with the following error if the database path has multiple backslashes


Error



 V-79-57344-851 - The path for this database is invalid because it contains extra backslash characters. You must remove the extra backslash characters before the database can be backed up.

Hex Error code - 0xe000353


Solution




The SQL issue described in this article is only encountered when the following conditions are met:

 
  • Microsoft SQL 2000 or SQL 2005 is being backed up by Backup Exec 10.x for Windows Servers.
  • The backup job reports that it is successful.
  • Advanced Open File Option (AOFO) is enabled for the backup job.
  • 'Automatically select open file technology' or 'Microsoft Volume Shadow Copy Service' is selected as the Advanced Open File Option configuration. (Figure 1)
  • The Microsoft SQL database being backed up was created manually by pointing to a directory path with superfluous additional backslashes (e.g. F:\mydb\data\\sales.mdf)
Figure 1
 

The SQL backup issue occurs due to an unexpected path being passed to Backup Exec. As a result, any database files that are being referenced by Microsoft SQL in this unusual way will be skipped but the backup will still report as successful. The byte count in the backup job will report the actual amount of data being backed up, so if all the database files are referenced in this manner then the byte count would be zero.

Permanent Fix

This issue has been addressed in the following Backup Exec Hotfixes:

Hot Fix 37 for Backup Exec 10.0.5484
 http://www.symantec.com/docs/TECH49002

Hot Fix 33 for Backup Exec 10.0.5520
 http://www.symantec.com/docs/TECH47342

Hot Fix 37 for Backup Exec 10.1.5629
 http://www.symantec.com/docs/TECH49014 


Note: These hotfixes will cause the backup job to fail if it runs into an invalid SQL database path. The workaround below will still need to be performed in order to correct this issue.



Workaround

Symantec strongly recommends that all customers performing SQL backups verify whether any databases have been created manually with an accidental repeated backslash.

For SQL 2000:

 
Open Enterprise Manager, and look in the properties of each database and see if any of the files (logs included) point to a directory path with multiple backslashes that are back to back (e.g. c:\mydb\\data\sales.mdf).  
 

 
Figure 2 and 3 show where to look within the properties of the database, and Figure 2 shows what an incorrect path would look like. If Enterprise Manager is not installed on the server, or is not accessible, following the directions under the SQL 2005 section can be used to determine if any databases have any additional backslashes and need to be corrected.
 

Figure 2
 

Figure 3
 


For SQL 2005:

 
Since SQL 2005 masks the repeated backslashes in the SQL user interface while still storing the inaccurate path in the database configuration table, it will be necessary to run the query below on the SQL server from a command prompt:
 

 
osql -S127.0.0.1 -E -d<database name> -Q"select * from sysfiles"
 

 
Run this query for each database in use and substitute the database name for '<database name>' in the query.
 

Note: If a 'bad' path is found to be stored for one of the SQL databases, then the first action should be to insure a complete backup. Therefore before correcting the database path, each problem database should be backed up in a separate backup job that does not have AOFO enabled. Afterwards, the byte count should be verified against expected outcomes. Once this is done, the database path stored within SQL can be corrected by following the procedure outlined in the Microsoft KB article below:

 http://support.microsoft.com/kb/224071/

 

Supplemental Materials

SourceUMI
ValueV-79-57344-851
Description

The path for this database is invalid because it contains extra backslash characters. You must remove the extra backslash characters before the database can be backed up.



Legacy ID



284887


Article URL http://www.symantec.com/docs/TECH48894


Terms of use for this information are found in Legal Notices