Unsolved
1 Rookie
•
34 Posts
0
3667
February 16th, 2021 02:00
Unable to perform the ASR backup: cannot obtain the VSS MBS status
Hello,
I always receive this error:
0117:save: Unable to perform the ASR backup: cannot obtain the VSS MBS status.
176571:save: Step (4 of 5) for PID-14436: Unable to complete the backup of the disaster recovery save sets. See the savegrp log to track the closure steps of the backup.
176572:save: Error occurred during the backup of the disaster recovery save sets.
I have seen that similar issue was posted before. I want to add that the client is windows server 2012R2 and NW is v19 for both client and backup server. I saw that you mentioned problem of incompatibility. but I don't see a suggested solution. how to fix this?
Thanks
No Events found!
bingo.1
2.4K Posts
0
February 16th, 2021 05:00
Maybe this KB article may help: KB000525826
For file systems with a huge number of files it might be that an inactivity timeout hits before the the actual backup starts - causing this error.
hend_bs
1 Rookie
•
34 Posts
0
February 18th, 2021 23:00
Hi,
Thank you for your reply.
However searching by the article number you provided me I was only able to find this KB: https://www.dell.com/support/kbdoc/en-us/000034673/networker-file-system-backups-using-parallel-save-streams-and-level-diff-or-incr-fails-err-5057-file-handle-is-stale?lang=en
Just an info inactivity time out parameter is always set to 0 in our configuration, in case that is what you are suggesting me to modify?
bingo.1
2.4K Posts
0
February 19th, 2021 03:00
It seems that the doc I mentioned has been deleted. Please have a look at
KB000055913
Networker: Backup is failing with error: "Unable to perform the ASR backup: cannot obtain emitter status."
The issue is that the problem seems to occur when the NW client is building up the worklist. At this point in time no backup phase has been started yet - consequently there is no backup timeout monitoring active.
In general, there are several reasons why NW takes so long to build up the worklist. The most obvious of them are ...
- missing rights (covered by the KB article mentioned above)
- too many (usually very small) files on the system drive. This might happen if you have installed a powerful application on the system drive. Unfortunately the default location.
Please carefully check the other process-relevant logs - they might tell you more.