Skip to main content
  • EN

Veeam Agent backup failure due to VSS error.

 

When checked in Event logs, found an error for VSS “automatically choosing a diff-area volume processing endpreparesnapshots”. Has anybody worked on this without rebooting the server?

Hi @Naveen Kumar -

Are you using a standalone agent or using with VBR? A server reboot is always going to be the 1st suggestion. Have you looked at some suggestions in this KB to see if any help?

https://www.veeam.com/kb3099

Hello @coolsport00, this is with VBR.

 

Reboot as a 1st suggestion is good. But this being production server getting downtime every time is quite impossible.

@Naveen Kumar - I certainly understand that. 😊  VSS errors can be quite…..’buggy’? And sometimes a simple reboot will resolve it. If VSS error happens a lot, then something else may be going on. Did you look at the KB I shared above to see if anything in it helps? Here is a Forum post I found where you can check some things without rebooting:

https://forums.veeam.com/veeam-agent-for-windows-f33/vss-snapshot-error-t64067.html

Here is another KB which might help:

https://www.veeam.com/kb1980

Try running - vssadmin list writers

This will show you if any of them are in an error state and some can be fixed by restarting services but others need a reboot.

Thanks @coolsport00 , the KB shared looks different, will ask Wintel once.

 

No problem. Keep us posted!

@Chris.Childerhose , “FSRM Writer” was timed out, used to restart the service and run the backup. When backup runs FSRM Writer turns timed out again.

 

Wintel team has disabled the services, still seeing the VSS error in event log.

 

“automatically choosing a diff-area volume processing endpreparesnapshots”.

Sounds like you may need a support case for them to check the logs and determine the issue.  Not ideal but only course of action at this point.

Hello @Chris.Childerhose , case was logged, not much of a assistance. 

 

07142873

Hello @Chris.Childerhose , case was logged, not much of a assistance. 

 

07142873

Ok you will have to be patient and work with them on this.  The community is not support so we have no insight to cases.

Hello @coolsport00, this is with VBR.

 

Reboot as a 1st suggestion is good. But this being production server getting downtime every time is quite impossible.

@Naveen Kumar this assumption does not meet the required standards for IT administration. Every server needs to have a maintenance window. 

Regarding FSRM service I remember an oldest issue similar and I checked this https://www.veeam.com/kb1846 you can follow. 

I think issue is low space for shadow copies. Let us know keeped with this option.

 

 

Comment


Terms & Conditions