Veritas NetBackup™ for Microsoft SharePoint Server Administrator's Guide
- Introducing NetBackup for SharePoint Server
- Installing NetBackup for SharePoint Server
- Installing and configuring NFS for SharePoint Granular Recovery
- About configuring Services for Network File System (NFS)
- Configuring NetBackup for SharePoint Server
- Configuring a SharePoint backup that uses Granular Recovery Technology (GRT)
- Configuring SharePoint client host properties
- Configuring NetBackup for SharePoint backup policies
- About configuring a backup policy for SharePoint
- Adding schedules to a NetBackup for SharePoint policy
- Creating a backup selections list for a SharePoint Server policy
- 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
- Protecting SharePoint Server data with VMware backups
- About protecting an application database with VMware backups
- About configuring a VMware backup that protects SharePoint Server
- Disaster recovery
- About NetBackup for SharePoint debug logging
- About NetBackup status reports
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 NetBackup Administrator's Guide, Volume I 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
client02.lab04.com, you may see the following entries:
- 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.
Valid name for
The short name of the client
The virtual name of the cluster
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.
client02.lab04.com, you see Mapped Host Names/IP Addresses that are similar to the following:
Mapped Host Names/IP Addresses
client01.lab04.com, client01, clustername, clustername.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
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