Unsolved
This post is more than 5 years old
1 Rookie
•
42 Posts
0
1092
April 7th, 2015 08:00
System64 exceptions
I am getting system64 and system32 exceptions in both VSS and file system backups. Below are a few lines from one of the activity logs.
2015-04-07 03:00:56 avtar Error <5139>: File access share error "C:\Windows\System64\catroot2\edb.log" (code 32: The process cannot access the file because it is being used by another process). (Log #2)
2015-04-07 03:00:56 avtar Error <5139>: File access share error "C:\Windows\System64\catroot2\{127D0A1D-4EF2-11D1-8608-00C04FC295EE}\catdb" (code 32: The process cannot access the file because it is being used by another process). (Log #2)
2015-04-07 03:00:56 avtar Error <5139>: File access share error "C:\Windows\System64\catroot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" (code 32: The process cannot access the file because it is being used by another process). (Log #2)
2015-04-07 03:00:57 avtar Error <5139>: File access share error "C:\Windows\System64\config\RegBack\DEFAULT" (code 32: The process cannot access the file because it is being used by another process). (Log #2)
2015-04-07 03:00:57 avtar Error <5139>: File access share error "C:\Windows\System64\config\RegBack\SAM" (code 32: The process cannot access the file because it is being used by another process). (Log #2)
2015-04-07 03:00:57 avtar Error <5139>: File access share error "C:\Windows\System64\config\RegBack\SECURITY" (code 32: The process cannot access the file because it is being used by another process). (Log #2)
2015-04-07 03:00:57 avtar Error <5139>: File access share error "C:\Windows\System64\config\RegBack\SOFTWARE" (code 32: The process cannot access the file because it is being used by another process). (Log #2)
2015-04-07 03:00:57 avtar Error <5139>: File access share error "C:\Windows\System64\config\RegBack\SYSTEM" (code 32: The process cannot access the file because it is being used by another process). (Log #2)
There are about 80 exceptions in all. Is this going to be a problem for restore? If not, how can I avoid these exceptions? I still have a few clients that are having the same error but with the C:\Windows\System32 folder.
0 events found
ionthegeek
2 Intern
•
2K Posts
0
April 7th, 2015 09:00
This issue normally occurs if VSS is not working correctly on the client system. Do you see an error related to VSS failing to take a snapshot near the top of the log?
MShadow
1 Rookie
•
42 Posts
0
April 7th, 2015 10:00
It looks like a lot of the writers are "waiting for completion".
pawankumawat
355 Posts
0
April 7th, 2015 10:00
Hi,
Check backup logs and see of you can find something similar to this -
avtar Info <10662>: Unable to create volume snapshot; backup proceeding with original (non-snapshot) volume content. Some file content may not be backed up.
Please check if VSSadmin list writers command returns all writers in stable state with no error.
Make sure volume shadow copy service is not stopped or disabled on the client. You can also try to run a test backup after restarting the Volume shadow copy service.
Regards,
Pawan
MShadow
1 Rookie
•
42 Posts
0
April 7th, 2015 10:00
I don't see any VSS issues. Rather, I see this...
2015-04-07 03:00:09 avtar Info <6074>: VSS snapshot set creation successful
ionthegeek
2 Intern
•
2K Posts
0
April 7th, 2015 10:00
The Volume Shadow Copy service is an on-demand service that is started automatically by the OS as needed. The service will stop on its own after a few minutes. It's important to ensure that it's not disabled but the service not being started is normal.