Normally SQL Server identifies its installations with a combination that includes the name of the host on which the installation resides plus an instance name. If you omit the instance name then NetBackup assumes that the installation is the default installation on the host. For example, a single host may contain several SQL Server installations, such as, TIGER, TIGER\ACCOUNTING, and TIGER\WAREHOUSE. However, a clustered instance of SQL Server resides jointly on multiple hosts and is identified with a virtual name.
Backups for a host are cataloged under the client name that is specified in the client properties for that host. Ordinarily, the client name is the same as the host name on which SQL Server resides. Normally, this name is the host's NetBIOS name (such as TIGER). However, some backup administrators prefer to identify the client to NetBackup in other ways. For example, an administrator might use the IP name (for example, 20.81.74.123) or the fully qualified domain name (tiger.apexworks.com). Or, an administrator might use an alternate network interface that is attached to the host (tiger1.apexworks.com). For clustered SQL instances, the client name is the virtual SQL Server name that is used for the virtual SQL Server installation.
In most cases when you browse for backup images using the NetBackup Microsoft SQL Client, you only need to specify the SQL Server host name. Specify this name in the Backup History Options dialog box.
NetBackup then displays the backup images for all of the instances on that host. However, to ensure that NetBackup displays the backup images you want, consider the following special cases:
Retrieval of backups on a network interface not having the same name as the host name (such as tiger1 or tiger.apexworks.com).
In this case, the backup images are stored under the network interface name and not the NetBIOS name. To retrieve these images, you should specify the host name in the SQL Host field and the network interface name in the Source Client field.
Retrieving backups from a UNIX (or Linux) server.
This scenario may present a problem because UNIX names are case sensitive, whereas Windows names are not. In this case, NetBackup tries to retrieve the backup images by specifying the client name with all upper case characters or all lower case characters. If the UNIX client name has mixed uppercase and lowercase characters, you must provide the client name in the Source Client field.
The NetBackup client name is a qualified domain name.
To retrieve backup images specify the SQL Host as the NetBIOS name and the Source Client as the fully qualified domain name.
The NetBackup client name is an IP address.
To retrieve backup images specify the SQL Host as the NetBIOS name and the Source Client as the IP address:
Retrieval of the backups that were backed up from a SQL Server cluster.
This scenario does not present any special problem because the images are stored under the cluster name. Provide the SQL Host name as the virtual name and use the default value for the Source Client.
More Information