If the client host name is listed as a SERVER the nbftclnt service does not

If the client host name is listed as a server the

This preview shows page 77 - 79 out of 105 pages.

If the client host name is listed as a SERVER , the nbftclnt service does not start. If a SERVER entry exists for the client, remove the entry and then start the client service. The client host name should be listed as CLIENT_NAME only. SAN client Fibre Transport service validation The SAN Client Fibre Transport Service (nbftclnt) validates the client system’s kernel and driver stack when it starts and during device discovery. Validation verifies that the kernel and the drivers are at supported levels. If validation succeeds, the SAN client supports FT pipe transfers; FT pipe transfer can occur. If validation fails, FT pipe transfer cannot occur. To manage the validation failure, the following occurs: The SAN Client Fibre Transport Service writes check driver messages in its log file. NetBackup sets the FT device status to offline for all FT target devices in the client’s SAN zone. (For other clients in the zone that pass the validation, the FT devices are online.) To see the FT device status from the client, select the client in the Media and Device Management > Devices > SAN Clients window in the NetBackup Administration Console . The check driver messages in the nbftclnt log file are similar to the following: VerifyCheckConditions:failed on < OS Device Name > - check driver VerifyCheckConditions:failed on < OS Device Name >; < System Error Message > The following describes the variables in the messages: OS Device Name is the device name the SAN Client uses to open the OS device driver. System Error Message can be any OS-dependent system error message for a failure that is associated with the request. See “Viewing Fibre Transport logs” on page 70. If validation fails, install the correct operating system version, operating system patches, or driver version. For supported kernel and driver levels, see the NetBackup Release Notes . 77 Troubleshooting SAN Client and Fibre Transport SAN client Fibre Transport service validation
SAN client does not select Fibre Transport If either of the following are true, a SAN client may not be able to select Fibre Transport during a backup or restore operation: The FT media server host operating system domainname command returns fully qualified domain names and NetBackup is configured to use short names. The FT media server host operating system domainname command fails because of: DNS, NIS, or network problems and NetBackup is configured to use fully qualified domain names. If so, the backup or restore may fail or it may occur over the LAN rather than the SAN. To work around this problem, add an alias for the FT media server to the EMM database. The following are the command syntaxes: To add a short name alias: nbemmcmd -machinealias -addalias -alias shortservername -machinename servername.fully.qualified -machinetype media To add a fully qualified domain name alias: nbemmcmd -machinealias -addalias -alias servername.fully.qualified -machinename shortservername -machinetype media Media server Fibre Transport device is offline

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture