I have recently upgrade from BE9.1 to BE11d on Windows 2000SP4. When backing up my SQL servers (i have 2 SQL2K servers) i am receiving the error "The path for this database is invalid because it contains extra backslash characters". I have checked the relevant databases and I can find no extra backslashes. If i exclude one of the failing databases from the job it then decides to fail on another database instead.
As stated in my original post I have checked all my databases and none of them contain double slashes. In fact If I exclude one of the failing db's from the backup then the error moves to another db that was fine until then.
That is very strange. Cant say I've seen this before without there being an extra \ in the path. If you do a "select * from sysfiles" in the query analyzer on that DB, what is returned? Does it happen on system db's or just user db's?
If you job is set to use AOFO, try turning that off as a test to see if VSS may be causing a problem.
I am having the exact same problem. The database in question is a named instance of MSDE that is used with SharePoint Team Services. The server and instance are called:
The error I get is:
Backup- http://hypnos\Team DB 1 (HYPNOS\SHAREPOINT\STS_hypnos_1) V-79-57344-34110 - AOFO: Initialization failure on: "HYPNOS". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS). Snapshot provider error (0xE0000353): 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.
I've been through the sysfiles tables of all the databases on this instance, and none of them have double slashes in them.
I have this same problem with both MSDE databases and MSEE (SQL 2005) created by and used for Windows Server Update Services. I also have Veritas Support that I pay for but they told me it was a Microsoft problem. Microsoft says it is a Veritasproblem. Veritas says it will only leave my case open for 24 hours from now. I guess I am in trouble. If anyone solves this I would sure appreciate knowing about it!
This document describes the problem, and how to fix the "\\" in the SQL path. It is not a Symantec fix.
The hotfixes listed in this doc are what is causing the jobs to fail with invalid path error. Prior to these hotfixes being released, the job would succeed regardless of the path. This caused potential restore issues. Symantec developed a fix that verified the path, causing a failure if a bad path was found. This fix is in 11d as well. The only way to get a successful backup is to find the invalid path and fix it. There are two places to check this. In the Master database sysaltfiles table and in the sysfiles table on the db itself. If the path comes back okay in both locations, you may need to contact Symantec Support to make them aware of this issue.
The Hotfix does NOT make it possible to backup databases with the double backslash configuration.
The Hotfix causes Backup Exec to "fail" the backup job...just as is stated in the technote: Document ID: 284887 http://support.veritas.com/docs/284887 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.
Here is the exact text: 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.
Until the path configuration is changed in the manner Jeff Zankofsky suggested the backups will continue to fail...just as the Hotfixes and BE 11 are designed to function.
I have to admit I have seen this error and it drove me nuts. In selecting the database for backup there is no double backslash.
If I remove the database the backup was fine. add it back and failure "double backslash".
I did however find the cause.
Using Enterprise Manager (for SQL) I found the database and log path had a double backslash in the path. Take note of the database path, log path and database owner. Just detach the database and reattach it removing the double backslash in the path and your backup will work.