SharePoint backups fail with status 71.
Created: 22 Mar 2013 | 3 comments
Scary …!
One of the reasons that can cause this is the absence of FARMS key under
HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\NetBackup\BEDS\Engine\Sharepoint\
Sometime it may happen that the key is not present and will cause the backups to fail. The significance of this key is that it contains the information about the SharePoint farm.
This Key is created on SQL Backend Servers and contains the names of frontend servers that put their data on this backend server.
If you encounter such issue, you can use the following command to create the key and reattempt the backup.
bpresolver.exe query -c svw8scr5 -ct 8 -init_beds "Microsoft SharePoint Resources:\*"
Recently, while working on one of the cases, I used this command and it resolve the backup failure for us.
Blog Entry Filed Under:
Group Ownership:
Comments 3 Comments • Jump to latest comment
What else can cause this - my non-GRT backups are spawning child jobs which complete with 71 status...
Precisely what should the registry details be?
We have:
(Default) REG_SZ (WEBSERVER1,WEBSERVER2,CASERVER,APPSERVER)
SQLSERVER REG_SZ caserver.fully.qualified.domain.name
Should I run the bpresolver command above?
What NBU and SP version are you using?
Can you please send me bpresovler(from front end server - the client specified in policy), bpbkar (SQL Backend) and BEDS Wrapper (from front end server - the client specified in policy) logs?
Thanks and Regards.
~gk
Hey Callmebruce,
Is the issue resolved?
Regards,
Gaurav Kaushal
Thanks and Regards.
~gk
Would you like to reply?
Login or Register to post your comment.