05-07-2013 07:45 AM
Hi all,
I have a problem with my sharepoint policie, since I upgraded my NBU master and clients from 7.1.0.4 to 7.5, this policie was running some days and other days it exit with status 2 "none of the requested files were backed up(2)", at the first error I restarted NBU client service and restart policie, it was runned ok for two days, but second day after this, today I had problem again, now I´m verifying logs but didn´t find the error.
Can anybody help me?
Thanks.
Solved! Go to Solution.
06-04-2013 07:08 AM
What was your solution ? Did the tech note / eeb I mentioned help ?
05-07-2013 08:17 AM
Usually a status 2 is a permission issue, however the fact that is is intermittent is odd. Since you recently upgrade, I would go through the following configuration check list. ( especially #2 and #3 )
What version so sharepoint and service pack are you running ?
If you still see the error after going through the check list, please upload the spswrapper for review on the day of occurrence. It could be possible you are running into : http://www.symantec.com/docs/TECH202784
1. Net Backup Client version should be the same as the Master Server, and should be installed on all servers in the SharePoint farm, even SQL backend. For SharePoint 2010 SP 1 or GRT you must be on 7.1.0.4 or higher.
2. The NetBackup Client service should be started by a Domain Account. (MUST be in format“domain\user”)
(additional services are needed for GRT, please see GRT Section)
3. The domain account in Step 2 must have the following privileges and permissions:
a. "Replace a process level token" and "Debug Programs" (Administrator Tools - Local Security Policy - Local Policies - User Rights Assignment) for all servers in the SharePoint farm, backend SQL included.
b. Local Administrator rights on all servers in the SharePoint farm.
c. Within SharePoint Central Administrator, the Domain Account is specified as a SharePoint Farm
Administrator
d. The System Administrator role on the SQL Server for the SharePoint databases.
4. At a minimum, you must have at least .NET Framework 3.5 installed on all servers in the SharePoint Farm.
5. Ports 13782 (bpcd) and 13724 (vnetd) between all Servers in the SharePoint farm and between the Media Server and Master. The ports must be opened bi-directionally.
6. Under Host Properties - Clients on the Master server, under the Windows Client - SharePoint section, make sure that the Domain Account from step 2 is specified there, with the syntax as follows: DOMAIN\Username (not just the Username). Do this for every client/server member of the SharePoint farm.
7. Create a "beds" directory under <install path>\NetBackup\logs\ on each of the SharePoint farm servers (SQL included)
8. Under Host Properties - Master Server, there is a Distributed Applications section. For the first field, put in the name of the Front end server in the SharePoint policy, and in the 2nd field, the name of the SQL server hosting the SharePoint databases.
9. From the Front End web server specified in the policy, Right click on the NetBackup Backup, Archive, and Restore (BAR) GUI and select "Run as Administrator" . You should be able to see Microsoft SharePoint Resources objects there. If you do not see objects, check the farm topology and make sure you have not missed any of the steps on that server.
7. In the first policy (non-granular), the client selection is a Front End Web server for the SharePoint portal. The backup selection for your first policy should be: "Microsoft SharePoint Resources:\"
8. Make sure you do not have the "Enable Granular Recovery" box checked.
9. In the client selection, the frontend server should be specified.
10. You may now test you SharePoint Backup.
Addition steps for SharePoint GRT
For setting up GRT backups of SharePoint, the Media server (if it is a Windows box) and the SQL server need to be running Windows 2003 R2 (or greater) with the following hot fix applied: http://support.microsoft.com/kb/947186.
- In addition The Media server doing the backup/restore operations MUST have NFS Server components installed and running, as outlined in the SharePoint Administration Guide for NetBackup.
- The Frontend and Backend servers must have Client for NFS
See Tech Note for details on NFS - http://www.symantec.com/docs/TECH76684.
-The backups can only be Full backups, and must be taken to a disk storage unit, not tape. Be sure that the policy reflects this as well as having the "Enable Granular Recovery" box checked. Please see the following tech note which lists what type of disk storage types are support for GRT - http://www.symantec.com/docs/TECH187917
- Since GRT only supports Disk, backups can be staged off to tape media at a later time, but the initial backup must be to disk. If you stage the backup image to tape, you must duplicate the image back to disk before a restore can be attempted. For best performance, Symantec recommends that the disk storage unit being used as a target for GRT backups be located locally on the media server as direct SCSI or SAN attached disks. The use of disk storage units that write to network based file systems ( NFS or CIFS ) is not recommended. Performance degradation or read errors may result when the media server presents the backup image via NFS to the client or proxy client if the NFS exported image itself is residing on a network file system ( NFS or CIFS ).
- In addition to the Netbackup Client service, the Netbackup Legacy Client Service and Legacy Network services should be service should be started by a Domain Account. Please refer to #2 and #3 above.
- For GRT Restores, you must run the BAR from the Front end server.
- In addition to 13782 (bpcd) , 13724 (vnetd) the 111 ( port map) , and 7394 (nbfsd ) need to be open.
05-07-2013 08:45 AM
Also set the NetBackup Legacy Network Service account (note: dont mix this up with the Legacy Client one) to use your SharePoint Admin Account and re-start that one
It is odd that it is intermittent but give that a try
05-07-2013 09:56 AM
Hi Dyneshia, in your recomendations, only ports in firewall I had different configurations, I had not done it in outbound config, did it now.
Mark, I did what you recommended with NetBackup Legacy Network service, it was stopped and manual, now it is running and with the same user as client NBU on all servers of Sharepoint farm.
I need to wait tonight to see if it will running ok, tomorrow I post here results.
Thank you very much.
05-08-2013 03:55 AM
Good morning people, unfortunately my job shows me the same error, status 2.
05-08-2013 04:57 AM
Are you NetBackup services set to automatic startup?
I have seen issues where something only work if they are set as Automatic, even if they are running.
05-08-2013 05:28 AM
Yes Mark, all of services are automatic startup, on master server and clients.
05-08-2013 06:20 AM
I had been reading on client attributes\help context that by default "Windows open file backup" is enabled on clinets, I made an experience and removed my sharepoint server in dialog box "Clients", it was listed there.
I try to re-run policie and it running ok, but I still have a doubt about bpcd log, there are a line as follow...
"ReadKeyfile: keyfile C:\Program Files\Veritas\NetBackup\bin\keyfile.dat does not exist", and I don´t know why this if I do not using encryption option in police or client.
I have attached my client bpcd log for analise.
Thanks.
05-09-2013 08:07 AM
You can ignore that message.
Back to the issue, are you stating you disabled WOFB and it is now working ? Or are you still having an issue ?
From my orginal post :
What version so sharepoint and service pack are you running ?
If you still see the error after going through the check list, please upload the spswrapper for review on the day of occurrence. It could be possible you are running into : http://www.symantec.com/docs/TECH202784
05-10-2013 08:09 AM
Hi Dyneshia,
Our Sharepoint is 2010.
How can I upload the spswrapper and what is this?
I have been trying to download the maintenance pack 7.5.0.6 on that link but there is only 7.5.0.5 there.
How can I get MP75.0.6?
Thanks.
05-10-2013 09:38 AM
The spswrapper is a log file, located on your Front end server :
\NetBackup\logs\beds
The final fix is in 7.5.0.6 , however you can request Etrack 3055770 once you are at 7.5.0.5.
7.5.0.6 has not been released.
05-10-2013 02:00 PM
Article URL http://www.symantec.com/docs/TECH88187
I tried to set this up on one server and found a couple syntax errors:
there should be a space before encoding in first line
and space before enabled in the fourth line
*edit*
Even with those fixes (syntax has been confirmed on Microsoft site) we are not seeing any logs in the beds\spps directory At least we are not seeing any more xml errors.
05-12-2013 09:27 AM
There is no spps directory under beds.
Increase your verbosity and confirm the beds directory is listed in the logs directory.
If the spswrapper is not getting created, then there is still a configuration issue or you may be running into a etrack
05-16-2013 07:39 AM
Thank you guys for help, I openned a case on symantec and have been dealing with an engineer, as soon as possible, when I have solution I´ll post here, ok.
05-16-2013 08:40 AM
Verneti, please post followup when you get an answer. I am interested & sure others are as well!
Dyneshia, no such log created here. I am going to try on another system and see if that works. I am disappointed that Technote 88187 has been around so long and is not correct.
05-16-2013 11:48 AM
Vernetie - you may reference TECH202784
05-16-2013 11:56 AM
Thank you Dyneshia, I passed this information to Bruno.
06-04-2013 07:08 AM
What was your solution ? Did the tech note / eeb I mentioned help ?
06-04-2013 07:17 AM
Hi Dyneshia,
I still haven´t solutuion, I opened a case in Symantec, so they are analysing logs, the engineer who is help me told me that the EEB to fix this problem isn´t ok yet.
So, when I have solution I´ll post here, ok?
Thanks.
06-06-2013 12:25 PM
Hi Dyneshia,
As you mentioned, I opened a case at Symantec, send some logs and the engineer Bruno was discussing with backlog, I don´t know why but in the last saturday my policie start to run normally and since that are ok.
I didn´t need to apply EEB to fix the problem.
Thanks very much.