Forum Discussion

David_Perrin's avatar
David_Perrin
Level 5
18 years ago

Errors backing up V3.0 WSUS databases

We have 3 machines running WSUS V3.0, and BackupExec will not back any of them up.  Two of the servers get tthe error, 'Unable to attach to  Server\WSUS.  V-79-5734-33932 - Unable to attach to a resource...' 

The third gets an 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 teh database can be backed up.'

I found a solution for this later problem which involved running SQL Enterprise Manager, but SQL is actually not installed ont this machine, so that solution is no good.

The suggestion for correctin the former problem was to stop the SQL Server VSS Writer service, which I have done, but the problem still occurs.

Any Ideas?
11.x and Earlier
Backup and Recovery
Backup Exec

14 Replies

Sort By
  • Max1E06's avatar
    Max1E06
    Level 2
    18 years ago
    I have the same exact problem here.  I basically had to stop backing up the WSUS 3.0 database.  I keep waiting for a  hotfix or something from Symantec so that BE will properly handles this.  Have you had any success getting this to work?

    Message Edited by Max1E06 on 07-10-200711:31 AM

  • David_Perrin's avatar
    David_Perrin
    Level 5
    18 years ago
    Thank you for the reply, Max.

    No, I have not had any success with this.  Since we installed WSUS V3.0 the problem has persisted. 

    I installed all the hot fixes that were available hoping this problem would be resolved, but it is not.   Every nightly (partial) and weekend (full) backup is reporting the same errors.  A long time ago (before version 10), I  separated my SQL backup from the normal job so it does not use the OFO, and all the other databases are backed up with no problem, except the WSUS databases.

    Message Edited by David Perrin on 07-10-200711:37 AM

  • David_Perrin's avatar
    David_Perrin
    Level 5
    18 years ago
    Well, at least I know I'm not the only person having this problem with the WSUS database.

    Any ideas, Symantec?
  • Hywel_Mallett's avatar
    Hywel_Mallett
    Level 6
    18 years ago
    I know it doesn't help you at all, but I backup a WSUS database with no problem? My WSUS database is on an SQL 2005 server. Are you using Windows Database, or whatever they call MSDE now?
  • David_Perrin's avatar
    David_Perrin
    Level 5
    18 years ago
    I believe all 3 are using MSDE, and two of the 3 were upgrades.

    Message Edited by David Perrin on 07-16-200701:07 PM

  • Johnny_B's avatar
    Johnny_B
    Level 3
    18 years ago

    In my case this error started after we removed WSUS.   Apparently BE was still looking to process this MSDE database which no longer existed.  There were never any errors while WSUS database was active.

    After months of annoyance I stumbled upon a solution.  It turned out that my BE selection lists were at fault.  Even though the WSUS database had long been removed, the BE selection list must have still referred to it.  Mind you, no where in the selection list was this reference evident.  I’ve had similar phantom references with selection lists in the past.

    Out of desperation I created new backup lists and associated them with the appropriate jobs.  Immediately after deploying the new lists, the errors stopped.

    I hope my experience can shed some light on your issues.

    Message Edited by Johnny B on 07-17-200708:07 PM