NetBackup™ for Microsoft SharePoint Server Administrator's Guide
- Introducing NetBackup for SharePoint Server Server
- Installing NetBackup for SharePoint Server Server
- Planning the installation of NetBackup for SharePoint Server
- Verifying the operating system and platform compatibility
- NetBackup server and client requirements
- SharePoint software requirements
- Requirements for installing the SQL Server back-end servers in a cluster
- License for NetBackup for SharePoint Server
- Installing and configuring NFS for SharePoint Granular Recovery
- About installing and configuring Network File System (NFS) for SharePoint Granular Recovery
- Requirements for SharePoint Granular Recovery
- Configurations that are supported for SharePoint Granular Recovery
- About configuring Services for Network File System (NFS)
- Configuring a UNIX media server and Windows clients for backups and restores that use Granular Recovery Technology (GRT)
- Configuring a different network port for NBFSD
- Configuring NetBackup for SharePoint Server
- About configuring NetBackup for SharePoint Server
- About a SharePoint non-granular backup vs. a backup that uses Granular Recovery Technology (GRT)
- Configuring a SharePoint backup that uses Granular Recovery Technology (GRT)
- Configuring the logon account for the NetBackup Client Service for NetBackup for SharePoint Server
- Configuring the logon account for the NetBackup Legacy Network Service and the NetBackup Legacy Client Service
- Configuring SharePoint client host properties
- Configuring mappings for restores of a distributed applications, clusters, or virtual machines
- Reviewing the auto-discovered mappings in Host Management
- Performing a manual backup
- Configuring NetBackup for SharePoint Server backup policies
- About backup policies for granular backup and recovery of SharePoint Server
- About backup policies for SharePoint farm backup and recovery
- About backup policies for disaster recovery of SharePoint Server
- About VMware backup policies that protect SharePoint Server
- About configuring a backup policy for SharePoint
- Performing backups and restores of SharePoint Server and SharePoint Foundation
- About user-directed backups of SharePoint Server and SharePoint Foundation
- About restores of SharePoint Server and SharePoint Foundation
- Specifying the server, client, and the policy type for a SharePoint Server restore operation
- Restore options for SharePoint Server on the Microsoft SharePoint tab
- How the NetBackup Recovery Assistant restores SharePoint Server and SharePoint Foundation
- Restoring SharePoint Server and SharePoint Foundation
- Restoring the SharePoint Search Service Application
- About requirements for restores of individual SharePoint items using Granular Recovery Technology (GRT)
- Restoring individual SharePoint items from full database backups
- Recovering a SharePoint Web application in a farm with multiple front-end servers
- Restoring a deleted SharePoint list
- Redirecting a restore of a SharePoint web application within a farm
- Redirecting a restore of a SharePoint Web application to another farm
- Redirecting the restore of a SharePoint Server Web application content database to an alternate SQL Server instance
- Protecting SharePoint Server data with VMware backups
- Disaster recovery
- Troubleshooting
- About NetBackup for SharePoint Server debug logging
- About NetBackup status reports
- Restores to different SharePoint service pack or different cumulative update levels
- Modified system files or ghost files are not cataloged or restored during a site collection restore
- Troubleshooting SharePoint jobs that use Granular Recovery Technology (GRT)
- About troubleshooting SharePoint restore operations
- About NetBackup for SharePoint Server and client-side deduplication
- Troubleshooting VMware backups
Troubleshooting VMware backups
Note the following when you perform a VMware backup that protects an application:
The Application State Capture (ASC) job contacts the NetBackup client on the guest virtual machine and catalogs the application data for recovery.
One ASC job is created per VM, regardless of which applications are selected in policy.
ASC messages are filtered based on the ASC job details in the Activity monitor.
The ASC job can result in status 1 (partially success). For example, if SharePoint was protected, but it was the SQL Server that failed to be protected.
Failure results in the discovery job or parent job exiting with Status 1.
If you enable recovery for a particular application but that application does not exist on the VM, the ASC job returns Status 0.
bpfis is run and simulates a VSS snapshot backup. This simulation is required to gain logical information of the application.
Table: Issues with using a VMware policy to protect databases
Issue | Explanation |
|---|---|
A database backup fails. | Databases are cataloged and protected only if the configuration is supported for VMware backups. See Limitations of VMware application backups. NetBackup is installed on an excluded Windows boot disk. The ASC job detects this type of disk and treats it like an independent disk. Do not select the option if NetBackup is installed on the boot drive (typically C:). |
ASC job produces a status 1 (partially successful). | You selected databases for backup that exist on both supported and on unsupported disks. See "A database backup fails" for unsupported disk information. |
Full-text catalog files exist on the mounted folders. The databases are not cataloged. | |
The Application State Capture (ASC) job fails and the databases are not protected. | When the ASC job fails, the VMware snapshot or backup continues. Application-specific data cannot be restored. |
You disabled the option. | |
Database objects are on a VHD disk. No objects in the backup are not cataloged, including those that do not exist on the VHD. | |
You excluded any data disks from the VMware policy, on the Exclude disks tab. Be sure that any disks that you exclude do not contain database data. | |
The VMware disk layout has changed since the last discovery. In this situation, you must force NetBackup to rediscover virtual machines by lowering the value of the option. See the NetBackup for VMware Administrator's Guide. | |
You cannot use a VMware incremental policy to protect SharePoint Server. However, the VMware backup job is successful. | |
There is a Content database with no site collections present. To avoid this issue, remove the empty Content database or create a site collection in the Content database. The policy included SQL Servers that host multiple SharePoint farms. | |
You can recover the entire virtual machine from the backup, but you cannot recover the databases individually. | You did not select , which allows recovery of the databases from the virtual machine backups. |
VMware job fails with error 2804. | No media server was added in the list. |
GRT live browse error for a VMware image that supports the restore of application data. |
The is not a NetBIOS name (for example, display name or UUID). For example, a client name like Add an entry to the settings. The is the name of the application host. The front-end client name is the name of the component host. Alternatively for UNIX primary servers, add the |
The SQL snapshot preparation fails. | In the VMware policy, you select both Enable SharePoint Recovery and . Only select one of these recovery options. |