Netbackup, Sharepoint, GRT with restore error status 37
Created: 02 Jan 2013 | Updated: 20 Jan 2013 | 23 comments
This issue has been solved. See solution.
Hello there,
Sharepoint Backup with GRT enabled completes successfully.
restore failed with error 37, there is no other details about the failure!
we have Symantec Netbackup 7.1.0.3
Please advise where should i invistigate?
Discussion Filed Under:
Comments 23 Comments • Jump to latest comment
hi,
could you give us more detail?
what is the storage unit that you are using for Backups?
form where did you trigger the restore job?
please check the T/N , which give more info about the EC 37
http://www.symantec.com/business/support/index?pag...
could you give us more detail?
we have 5 servers for the sharepoint 2010:
front servers: sr1001spw001, sr1001spw002
application server: sr1001spa001
SQL Cluster (virtual server sr1001csql2010): nodes sr1001sql011, sr1001sql012
what is the storage unit that you are using for Backups?
Symantec Deduplication
form where did you trigger the restore job?
from the Master server
regarding the link you have posted, it is not valid for my case
i do not see the error
Operation requested by an invalid server
could you provide the restore log from the location /usr/openv/netbackup/user_ops/<userid>/logs
and also bpcd and bprd logs of master server at the time of restore job as attachment.
Thanks Nagalla for your support, the master and media servers are installed on windows based servers.
can you specify what logs to check?
I believe my issue is in configuring servers list somewhere.
hi ,
make sure that you have the bpcd and bprd log directories created in master server. I am sure about your master server is Window or Unix
Keep Verobse = 5
for Unix:-
/usr/openv/netbackup/logs/bpcd
/usr/openv/netbackup/logs/bprd
for windows:-
Installpath/veritas/netbackup/logs/bpcd
Installpath/veritas/netbackup/logs/bprd
then open up your java conosle of Master server and trigger the restore job., while click on the restore log, you will have option to specify the Progress log..
by default it will be
/usr/openv/netbackup/user_ops/<userid>/logs --->for unix
Installpath/veritas/netbackup/logs/<userid>/logs --> for windows
please provide all these 3 logs
please find attached logs, please let me know if you have any question.
Have you completed the Distributed Application Mappings section on the Master Servers Host Properties - it says it is for Exchange but it is for SharePoint as well
Hope this helps - will take a look at your logs
Authorised Symantec Consultant
Don't forget to give a "Thumbs Up" or mark as "Solution" if someones advice has helped you.
Distributed Application Mapping has been configured,
SharePoint front servers are mapped with sql backend and cluster virtual server, and with the indexing server.
Do you have the logs from yesterday when you tried the restore (010213.log) or have you tried it today - if so at what time?
I do see:
14:48:48.374 [7144.5124] <16> is_redirected_restore_allowed: One or more input parameters are invalid.
So maybe it is the Distributed Application Mappings that are needed, the No.Restrictions file on the Master can also help
Authorised Symantec Consultant
Don't forget to give a "Thumbs Up" or mark as "Solution" if someones advice has helped you.
I have tried the restore one hour or less before i upload the logs.
Distributed application mapping has been configured.
I am not sure what do you mean by the No.Restrictions file.. i have not read about it in sharepoint admin guide, could you please explain?
hi
From bprd log
01:03:19.077 [6340.2024] <16> free_allocated_resources: Free resource allocations failed.
Nagalla
Perfectly normal - source ports are random. The destination port is the only important one: 1556.
Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links
Marianne,
Thank you very much..
There is no firewalls between the servers in our case.
I will add more details, this may help
Master server is: sr1001bck001
SharePoint Front servers: sr1001spw001 and sr1001spw002
SharePoint application server: sr1001spa001
SQL servers: sr1001sql011 and sr1001sql012, Cluster virtual server is: sr1001csql2010
On your master server create a file named No.Restrictions (this is case sensitive) under the path:
\program files\veritas\netbackup\db\altnames\
This allows redirected restores when requested from clients - which is in effect how SharePoint works as it redirects the restores to the components of the Farm
If you are not happy to leave it in place just rename it after you have re-tried your restore.
If you could setup a folder named tar under the logs directory on the front end farm server and then re-try the restore telling us the time it started and finished and then re-upload the logs again so that we can pin point the restore and what is happening.
Also note that you should only do restores from the Master Server or the Front End Farm Server
Authorised Symantec Consultant
Don't forget to give a "Thumbs Up" or mark as "Solution" if someones advice has helped you.
the No.Restrictions file was created long time ago for SQL backup policies.
I am aware about the source limitations, restore should be run from Master or Front end server.
I am not sure about the tar folder, could you explain more please?
We see reference to hostname centraladmin.services.musanada.net in bprd log:
The final result is that 'centraladmin' is seen as actual destination name. Restore ends with status 48:
If 'centraladmin' is your Windows Admin Console, please check if 'configured client name' was at any point changed. Important that it must ALWAYS be the local hostname, unless you really want to redirect the restore to this machine.
Use 'All Programs', Symantec NetBackup -> Backup Archive and Restore window on 'centraladmin',
Open File -> NetBackup Client Properties.
Check Client Name.
Ensure that it is indeed 'centraladmin'.
Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links
Hello Marriane,
Sorry for being late, I was in a training, anyway, many thanks for your support.
I have checked Netbackup Client Properties and the Client Name is configured properly (local hostname).
Centraladmin is the SharePoint administration console.
I prefer regenerating the logs and check again, please advise what logs shall I upload here?
Many thanks in advance.
any help?
do have beds under logs. (on front end server) . Please elaborate on which content are you trying leverage GRT
Is it from Central Admin or Shared Service Admin WebSite. If yes then just an update GRT are not supported on this sites
Also can you try to execute restore from Front end server with user who has sharepoint admin privileges and is configured as service account for NBU
Also check if with this account you can see and expand sharepoint resources under BAR
With multiple servers in farm ensure network registry is enabled between front end and back end servers
Cheers !!!
EV Outlook Client Add-ins
Thanks all for your support, the error for case is resolved,
it was a reverse lookup record issue, there are multiple sites that share the same ip address so the netbackup could not locate the correct name.
i have a different error now, however, i will give it a try and if i could not fix it then i will open a new case here.
for this case i will mark Marianne's answer as a solution as she enlightened the central admin issue which guided us to the resolution.
Many thanks again.
Would you like to reply?
Login or Register to post your comment.