I have 6.1 on server and several Windows 2003 x64 Standard SP 2 servers. Most of them have successful backups, but two are failing regularly with these two errors:
I know that this is due to a problem with the Windows ntbackup.exe, but haven't been able to find a way to fix it. I have been able to manually run the ntbackup of the system state and can reset the vss writers, particularly the system writer, to the stable and no error state, but after running a backup the state changes to "[5] Waiting for completion".
just to be sure your backup either specifies all local drive so it gets a System State from the 2003 and you are not specifying a VSS in the backup selection as that is fro 2008.
If you are customer or partner, you should be able to see these urls.
Anyways, I am posting content of these urls.
Resolution
If an Avamar client reports system state failure, check to see if Windows is experiencing problems in actually creating the SystemState.bkf file. Try to create the system state manually, through Windows without using Avamar.
To do this, check the Avamar client log file for the command that is run to create the system state file (search the log for ntbackup.exe). Using a Windows command prompt, try to run the ntbackup command with the parameters in the log file and check to see if the .bkf file gets created.
To verify whether the file is being created, check the Windows Application Log for any messages:
Start > Run > Type "eventvwr".
Select Application Log.
You may need to View > Filter.
Select the Event source 'ntbackup' and press Apply > OK.
Make a note of any messages you find that are related to the System State. Include them in the case notes.
If the SystemState.bkf file *does* get created, make a note of its size. If it does not get created you must fix this before the Avamar client system state backup will be able to complete successfully.
Resolution
If running Windows 2000: 1. Make sure the client was installed with OTM. If not, reinstall the client with OTM and reboot. 2. Make sure there is at least 2.5GB of free disk space on the partition where the systemstate.bkf file is created.
If running Windows 2003 Server / XP: 1. Make sure the Volume Shadow Copy service is started on the Windows client (if Windows 2003 Server).
2. On Windows 2003 Server, we support VSS (Volume Shadow Copy Service). If you have installed OTM (Open Transaction Manager), uninstall it. To do this, go to Add/Remove programs and find the CDP Open Transaction Manager. For complete un-install a reboot will be needed.
I am also facing the same issue. Also I am not able to see all 3 urls.
We are receving below error in avamar:
2014-02-27 19:05:25 avtar Error <8535>: System State backup process failed! (Log #1) 2014-02-27 19:05:25 avtar Error <6197>: Windows System State backup failed (code 31) (Log #1)
As avamar is taking NT backup for system state in 2003. We checked logs on below path:
C:\Documents and Settings\Default User\Local Settings\Application Data\Microsoft\Windows NT\NTBackup\Data
After checking the logs I found following:
WARNING: Portions of "\Boot Files\C:\WINDOWS\system32\vssvc.exe" cannot be read. The backed up data is corrupt or incomplete.
This file will not restore correctly.
Error: Could not access portions of directory System State\COM+ Class Registration Database.
You may not have permission to open the file, or the directory may be missing or damaged.
Please contact the owner or administrator.
Error: Could not access portions of directory System State\Registry.
You may not have permission to open the file, or the directory may be missing or damaged.
TimQuan
6 Operator
•
1242 Posts
1156
0
Posted October 15th, 2013 20:00
This error is too general. Any other error?