Forum Discussion

melissa_windows's avatar
melissa_windows
Level 3
12 years ago

backup partially successul with WRN - can't open file: System State:\System Files\System Files (WIN32 -536805667: Unknown error)

i encounter an error while backuping several Windows 2008R2 clients with error message :

 

WRN - can't open file: System State:\System Files\System Files (WIN32 -536805667: Unknown error)

 

Master server is Netbackup 7.1 on linux

Clients netbackup version is 7.5

Clients OS version is Windows 2008 R2

backup object is ALL_LOCAL_DRIVES

 

anyone have an idea

7.1.x and Earlier
Backing Up
Backup and Recovery
Error messages
Linux
NetBackup
  • mrbill14's avatar
    mrbill14
    12 years ago

    Glad to hear you got this one solved!

    On a slightly different note, I had a Windows 2008 R2 cluster that has a service that is clustered (Control-M scheduler).  As a clustered service, the service would follow (or roll over) the active node master.  (Whichever node was the master, this service would roll over to it.  Which means the other node doesn't have it, which would cause the backups to fail.)

    I found this script (I don't take credit for it) on the Microsoft Technet blogs which runs a powershell script that checks for any invalid or incorrect services (in the registry).  See attached.  (Posted it as a text file, will have to rename the file with a .ps1 extension.)  Also, you will probably have to set the PowerShell Execution Policy to unrestricted.  See second attachment for explanation.

    http://blogs.technet.com/b/askcore/archive/2010/06/18/ps-script-for-blog-enumeration-of-the-files-failed.aspx

    Thinking that this would have been helpful in your situation. (?)  I'm posting it here in case anybody else happens across this particular situation.

     

  • mrbill14's avatar
    mrbill14
    Level 3
    12 years ago

    Sorry for the lateness of the reply.

    No, after running the script, it doesn't require a reboot.

     

    Melissa:  The VSS errors are mostly on the root drive (C:), because that's where the System State files are...  not that VSS couldn't be the cause of other volumes not to "snapshot".  It's just usually the case that it's the root drive (with the System State) that causes the problems.

    Your error - "A failure occurred accessing the object list" - sounds like it's having a problem reading the drive or the file list has changed (dramatically) from the time it enumerated the drive and the time it is backing it up.

    Is this a clustered disk (part of a Windows cluster) or something?  Maybe the disk (E: drive) flipped over to the other host during the backup?

    Is this a SAN LUN?  Maybe the drive is getting knocked off line or the server is having problems connecting to it (especially under heavy loads - as Netbackup tends to load up the network - so, in the case of a iSCSI drive, maybe flooding the network?)...

  • Will_Restore's avatar
    Will_Restore
    Level 6
    12 years ago

    Try Windows backup without NetBackup

     

    wbadmin  start  systemstatebackup  -backupTarget:E: 

  • melissa_windows's avatar
    melissa_windows
    Level 3
    12 years ago

    I everybody.

     

    I solved the problem with symantec support.

    in bpbkar log we found :

    11:24:09.437: [7328.3380] <2> ov_log::V_GlobalLog: INF - Status 0x0000007B returned calling FindFirstFile for \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy259\program files (x86)\subversion/bin in brUtil::GenerateFileList

    The error 0x0000007B is defined by Microsoft as:
    ERROR_INVALID_NAME 123 (0x7B) - The filename, directory name, or volume label syntax is incorrect.

    http://www.symantec.com/business/support/index?page=content&id=TECH150097

     

    The imagepath for the svn service is not formated correctly as a valid windows path.

    I correct the path in registry and everything is ok and backup are successfull.

    thanks a lot to everyone

  • mrbill14's avatar
    mrbill14
    Level 3
    12 years ago

    Glad to hear you got this one solved!

    On a slightly different note, I had a Windows 2008 R2 cluster that has a service that is clustered (Control-M scheduler).  As a clustered service, the service would follow (or roll over) the active node master.  (Whichever node was the master, this service would roll over to it.  Which means the other node doesn't have it, which would cause the backups to fail.)

    I found this script (I don't take credit for it) on the Microsoft Technet blogs which runs a powershell script that checks for any invalid or incorrect services (in the registry).  See attached.  (Posted it as a text file, will have to rename the file with a .ps1 extension.)  Also, you will probably have to set the PowerShell Execution Policy to unrestricted.  See second attachment for explanation.

    http://blogs.technet.com/b/askcore/archive/2010/06/18/ps-script-for-blog-enumeration-of-the-files-failed.aspx

    Thinking that this would have been helpful in your situation. (?)  I'm posting it here in case anybody else happens across this particular situation.