β06-27-2013 08:41 AM
Master/Media same server running windows 2008 R2
Netbackup 7.5.0.5
Web Server
SharePoint Foundation 2010
2008 R2 windows
SQL server for SharePoint
2008 R2 windows
Running SQL Visual Studio 2008
Ok I am tring to do a Sharepoint Backup and I keep getting errors non stop. I have the correct Admin ID, and Password for the Sharepoint SQL DB. I am running the backup on the Sharepoint server that has the websites etc on them.
I then tried to only back up 1 things and get this.
I am getting a error 2.
I have enable granualer recovery turned on, with Limit job per policy set to 1.
"Change to just allWebs for above example"
Backup Selections is setup for
Microsoft sharepoint resources:\
microsofte sharepoint resources:\AllWebs
Changing things around I get a error status 114, or a 130.
Any help would be great I read though the admin Guide for SharePoint so I have to be missing something.
Thanks
Solved! Go to Solution.
β06-27-2013 10:34 AM
Please run through this configuration checklist : ( GRT requires a lot ) usually a status 2 is permissions.
Question , from the Front end server, if you open the BAR and select for backup, do you see the sharepoint objects ? If you do not, and confirm all configuration is in the below, you will need to patch up to 7.5.0.6 which contains a fix for the sharepoint topology. Let's start with the checklist :
1. NetBackup 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/7.5.0.5 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.
β06-27-2013 10:34 AM
Please run through this configuration checklist : ( GRT requires a lot ) usually a status 2 is permissions.
Question , from the Front end server, if you open the BAR and select for backup, do you see the sharepoint objects ? If you do not, and confirm all configuration is in the below, you will need to patch up to 7.5.0.6 which contains a fix for the sharepoint topology. Let's start with the checklist :
1. NetBackup 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/7.5.0.5 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.
β06-27-2013 10:37 AM
I will run though the above, and test the BAR. I will report back once finished.
β06-27-2013 11:54 AM
Well so far I got a no GRT thanks to the above. Now to test the GRT. Looks like I missed a couple of steps some how.
β06-28-2013 05:22 AM
Awesome, so you were able to compelte a GRT backup ? Were you able to do a non-grt backup as well ?
If you have not further questions, don't forget to mark the solution