Link to home
Create AccountLog in
Avatar of lloydabberton
lloydabbertonFlag for United Kingdom of Great Britain and Northern Ireland

asked on

Cannot backup System state Windows 2000 Server SP4

Dear All

I am getting errors backing up a Windows 2000 Server SP4 System State, when using Backup Exec 11d and NT BAckup.

With NT Backup I get;

 Error: You do not have permission to access portions of System State\Registry\software.
Please see the owner or administrator to get permission.
Warning: Unable to open the file \Registry\software - skipped.

With Symantec 11d I get;

79-57344-33916 - An error occurred retrieving System State files.

The System State file could not be backed up.

I have spoken to Symantec and they tell me its a Windows issue.

I have searched high and low and cannot find a real fix for this.

Nothing has changed on the server, the account that the backup runs (administrator)  is the same (and has the correct rights) to remotley backup the server, and all permissions on the server aswell as with the accounts has not changed.

I disabled AV and ran the backup with NT Backup and it still erroed. I am going to reboot the Windows 2000 SP4 server tonight and see if the backup works.

I also ran a test on the backup job for system state on Backup Exec and it ran.

I do not want to reformat the server, as I have read one or two posts like this, I really need to get this working.

What I will do is reboot the server tonight, I have also unchecked and rechecked the system state on tonight's backup job). I will let you know.

But does anyone know a real fix for this?

Many Thanks
ASKER CERTIFIED SOLUTION
Avatar of brian_vt_hokie
brian_vt_hokie
Flag of United States of America image

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
SOLUTION
Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Avatar of lloydabberton

ASKER

I did a reboot and the error went away. I think it was a memory issue.

Thanks
Reboot fixed it