bitwise-sa
asked on
Backup failed with VSS Error
Good day to everyone here. I have a problem with my Backups. Everything was working fine but then IT had to take its place and now I am getting failed backups with Veritas 9.1.
This is what I have. 2 X Server 2003. Server1 is my File server and Veritas is loaded on. Server2 is my exchange server. If I restart Server2 My backups work for a week or 2 (But this is no real fix for the problem.) The servers is about 3 - 4 years old now.
This is what I get with my VSSADMIN LIST WRITERS:
Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1
Writer Instance Id: {b184e489-7125-4935-9b1a-c
State: [7] Failed
Last error: No error
Writer name: 'Microsoft Exchange Writer'
Writer Id: {76fe1ac4-15f7-4bcd-987e-8
Writer Instance Id: {f0e9432f-d0b6-4667-8248-6
State: [7] Failed
Last error: Retryable error
Writer name: 'FRS Writer'
Writer Id: {d76f5a28-3092-4589-ba48-2
Writer Instance Id: {78d46934-65d0-4e76-87ac-7
State: [7] Failed
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-7
Writer Instance Id: {3eed7a35-dcc9-42c0-bdd5-6
State: [1] Stable
Last error: No error
Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6
Writer Instance Id: {c75371a6-93dd-480b-881c-d
State: [7] Failed
Last error: No error
Writer name: 'Event Log Writer'
Writer Id: {eee8c692-67ed-4250-8d86-3
Writer Instance Id: {25bb2edc-8202-497b-8b91-5
State: [1] Stable
Last error: No error
Writer name: 'NTDS'
Writer Id: {b2014c9e-8711-4c5c-a5a9-3
Writer Instance Id: {2542c188-811f-44e0-bc88-1
State: [7] Failed
Last error: No error
Writer name: 'MSDEWriter'
Writer Id: {f8544ac1-0611-4fa5-b04b-f
Writer Instance Id: {a28fa0e2-110d-42df-9ffd-a
State: [1] Stable
Last error: No error
Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7
Writer Instance Id: {18aa84c2-91ea-4ddd-b4b2-f
State: [1] Stable
Last error: No error
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-4
Writer Instance Id: {9f389459-5597-4ace-8aae-0
State: [7] Failed
Last error: No error
As you can see there is No Errors but almost Every state is [7] Failed. This is the error Veritas gives me after the backup job fails:
Backup - Server2OFO: Initialization failure on: "\\Server2\Shadow?Copy?Com
OFO: Snapshot error (0xfffffed1): A failure occurred querying the Writer status.
My Server1 has a state of [1] and no errors so it’s fine.
The only thing Symantec can say is reboot the server...
Please help me as I need my backups working ASAP.
Thanks in Advance
This is what I have. 2 X Server 2003. Server1 is my File server and Veritas is loaded on. Server2 is my exchange server. If I restart Server2 My backups work for a week or 2 (But this is no real fix for the problem.) The servers is about 3 - 4 years old now.
This is what I get with my VSSADMIN LIST WRITERS:
Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1
Writer Instance Id: {b184e489-7125-4935-9b1a-c
State: [7] Failed
Last error: No error
Writer name: 'Microsoft Exchange Writer'
Writer Id: {76fe1ac4-15f7-4bcd-987e-8
Writer Instance Id: {f0e9432f-d0b6-4667-8248-6
State: [7] Failed
Last error: Retryable error
Writer name: 'FRS Writer'
Writer Id: {d76f5a28-3092-4589-ba48-2
Writer Instance Id: {78d46934-65d0-4e76-87ac-7
State: [7] Failed
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-7
Writer Instance Id: {3eed7a35-dcc9-42c0-bdd5-6
State: [1] Stable
Last error: No error
Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6
Writer Instance Id: {c75371a6-93dd-480b-881c-d
State: [7] Failed
Last error: No error
Writer name: 'Event Log Writer'
Writer Id: {eee8c692-67ed-4250-8d86-3
Writer Instance Id: {25bb2edc-8202-497b-8b91-5
State: [1] Stable
Last error: No error
Writer name: 'NTDS'
Writer Id: {b2014c9e-8711-4c5c-a5a9-3
Writer Instance Id: {2542c188-811f-44e0-bc88-1
State: [7] Failed
Last error: No error
Writer name: 'MSDEWriter'
Writer Id: {f8544ac1-0611-4fa5-b04b-f
Writer Instance Id: {a28fa0e2-110d-42df-9ffd-a
State: [1] Stable
Last error: No error
Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7
Writer Instance Id: {18aa84c2-91ea-4ddd-b4b2-f
State: [1] Stable
Last error: No error
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-4
Writer Instance Id: {9f389459-5597-4ace-8aae-0
State: [7] Failed
Last error: No error
As you can see there is No Errors but almost Every state is [7] Failed. This is the error Veritas gives me after the backup job fails:
Backup - Server2OFO: Initialization failure on: "\\Server2\Shadow?Copy?Com
OFO: Snapshot error (0xfffffed1): A failure occurred querying the Writer status.
My Server1 has a state of [1] and no errors so it’s fine.
The only thing Symantec can say is reboot the server...
Please help me as I need my backups working ASAP.
Thanks in Advance
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
No it's not. This is post-SP2.
ASKER
Ok. I am downloading it now. Do I have to restart the server after the installation??
I will be doing this tonight and give you some feedback. Thank you
I will be doing this tonight and give you some feedback. Thank you
Hi,
Check if you have sufficient disk space on each drive say atleast 30% as it would require space to save the snapshot.
A reboot will try to release the memory fragmentation which is also a possible reason for the VSS failing with
errors. If you have exchange running on this server then the memory fragmentation would be higher.
Apply that fix as recommended by honmapog.
bhanu
Check if you have sufficient disk space on each drive say atleast 30% as it would require space to save the snapshot.
A reboot will try to release the memory fragmentation which is also a possible reason for the VSS failing with
errors. If you have exchange running on this server then the memory fragmentation would be higher.
Apply that fix as recommended by honmapog.
bhanu
ASKER
Hi peeps,
I did install the fix last night and I had to restart the server. The backups are working (Usually when I restarted the server it is fixed for about 2 weeks..)
My server1 (File Server) is a bit low on disk space but Server2 (Exchange Server) has loads of space available.
I would like to find out:
In Veritas it said that Server2 has a VSS error. So is the problem with Server2 or can it be that Server1 has some kind of a problem with the VSS and therefore not use the Server2 VSS??
I did apply the fix to both server just in case.
I really hope this was the fix I was looking for. I will get back to you in a week or so to let you know if it is still stable.
Thank you for all your comments.
I did install the fix last night and I had to restart the server. The backups are working (Usually when I restarted the server it is fixed for about 2 weeks..)
My server1 (File Server) is a bit low on disk space but Server2 (Exchange Server) has loads of space available.
I would like to find out:
In Veritas it said that Server2 has a VSS error. So is the problem with Server2 or can it be that Server1 has some kind of a problem with the VSS and therefore not use the Server2 VSS??
I did apply the fix to both server just in case.
I really hope this was the fix I was looking for. I will get back to you in a week or so to let you know if it is still stable.
Thank you for all your comments.
ASKER
So far everything seems to be working 100%....
Thanks guys
Thanks guys
ASKER