Veritas NetBackup™ for Microsoft SharePoint Server Administrator's Guide
- Introducing NetBackup for SharePoint Server
- About NetBackup for SharePoint Server
- Features of NetBackup for SharePoint
- SharePoint Server backup operations
- About the contents of a SharePoint Server backup and a SharePoint Foundation backup
- SharePoint Server restore operations
- Limitations on SharePoint Server backups and restores
- NetBackup File System Daemon
- Installing NetBackup for SharePoint Server
- Planning the installation of NetBackup for SharePoint
- Verifying the operating system and platform compatibility
- NetBackup server and client requirements
- SharePoint server software requirements
- Requirements for installing the SQL back-end servers in a cluster
- About the license for NetBackup for SharePoint
- 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) on Windows 2012, 2012 R2, or 2016
- About configuring Services for Network File System (NFS) on Windows 2008 and 2008 R2
- 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
- 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
- Configuring the logon account for the NetBackup Legacy Network Service for NetBackup for SharePoint
- Configuring SharePoint client host properties
- Configuring mappings for restores of a distributed application, cluster, or virtual machine
- Reviewing the auto-discovered mappings in Host Management
- Performing a manual backup
- Configuring NetBackup for SharePoint 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 a SharePoint database
- 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
- Restore options for SharePoint Server on the General 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 instance
- Redirecting individual SharePoint items to a file path (SharePoint 2010)
- Protecting SharePoint Server data with VMware backups
- Disaster recovery
- Troubleshooting
- About NetBackup for SharePoint debug logging
- About NetBackup status reports
- Restores to different SharePoint service pack or different cumulative update levels
- Troubleshooting SharePoint jobs that use Granular Recovery Technology (GRT)
- About troubleshooting SharePoint restore operations
- About NetBackup for SharePoint and client-side deduplication
- Troubleshooting VMware backups and restores of SharePoint Server
Reviewing the auto-discovered mappings in Host Management
In certain scenarios, a NetBackup host shares a particular name with other hosts or has a name that is associated with a cluster. To successfully perform backups and restores with NetBackup for SharePoint, you must approve each valid Auto-Discovered Mapping that NetBackup discovers in your environment. These mappings appear in the Host Management properties on the master server. You can also use the nbhostmgmt command to manage the mappings. See the Security and Encryption Guide for more details on Host Management properties.
Examples of the configurations that have multiple host names include:
A host is associated with its fully qualified domain name (FQDN) and its short name or its IP address.
For SharePoint Server, the nodes in a clustered back-end SQL Server are associated with the virtual name of the SQL Server.
If you have a clustered back-end SQL Server, you must map the node names to the virtual name of the cluster if the following apply:
If the backup policy includes the cluster name (or virtual name)
If the NetBackup client is installed on more than one node in the cluster
If the NetBackup Client is only installed on one node, then no mapping is necessary.
To approve the auto-discovered mappings for a cluster
- In the NetBackup Administration Console, expand Security Management > Host Management.
- At the bottom of the Hosts pane, click the Mappings for Approval tab.
The list displays the hosts in your environment and the mappings or additional host names that NetBackup discovered for those hosts. A host has one entry for each mapping or name that is associated with it.
For example, for a cluster with hosts
client01.lab04.comandclient02.lab04.com, you may see the following entries:Host
Auto-discovered Mapping
client01.lab04.com
client01
client01.lab04.com
clustername
client01.lab04.com
clustername.lab04.com
client02.lab04.com
client02
client02.lab04.com
clustername
client02.lab04.com
clustername.lab04.com
- If a mapping is valid, right-click on a host entry and click Approve.
For example, if the following mappings are valid for
client01.lab04.com, then you approve them.Auto-discovered Mapping
Valid name for
client01
The short name of the client
clustername
The virtual name of the cluster
clustername.lab04.com
The FQDN of the virtual name of the cluster
- When you finish approving the valid mappings for the hosts, click on the Hosts tab at the bottom of the Hosts pane.
For hosts
client01.lab04.comandclient02.lab04.com, you see Mapped Host Names/IP Addresses that are similar to the following:Host
Mapped Host Names/IP Addresses
client01.lab04.com
client01.lab04.com, client01, clustername, clustername.lab04.com
client02.lab04.com
client02.lab04.com, client02, clustername, clustername.lab04.com
- If you need to add a mapping that NetBackup did not automatically discover, you can add it manually.
Click on the Hosts tab, then right-click in the Hosts pane and click Add Shared or Cluster Mappings. For example, provide the name of the virtual name of the cluster. Then click Select Hosts to choose the node names in the cluster to which you want to map that virtual name.
In Table: Example mapped host names for a single front-end SharePoint server with a clustered back-end SQL Server FCI is a SQL Server failover cluster instance.
Table: Example mapped host names for a single front-end SharePoint server with a clustered back-end SQL Server
Environment | ||
|---|---|---|
FCI (cluster with two nodes) | Physical name of Node 1 | SQL Server cluster virtual name |
Physical name of Node 2 | SQL Server cluster virtual name |