Veritas NetBackup™ SAN

Client and Fibre Transport

Guide

UNIX, Windows, Linux

Release 8.3.0.1
Veritas NetBackup SAN Client and Fibre Transport
Guide
Last updated: 2020-09-10

Legal Notice
Copyright © 2020 Veritas Technologies LLC. All rights reserved.

Veritas and the Veritas Logo, and NetBackup are trademarks or registered trademarks of
Veritas Technologies LLC or its affiliates in the U.S. and other countries. Other names may
be trademarks of their respective owners.

This product may contain third party software for which Veritas is required to provide attribution
to the third party (“Third Party Programs”). Some of the Third Party Programs are available
under open source or free software licenses. The License Agreement accompanying the
Software does not alter any rights or obligations you may have under those open source or
free software licenses. Refer to the third party legal notices document accompanying this
Veritas product or available at:

https://www.veritas.com/about/legal/license-agreements

The product described in this document is distributed under licenses restricting its use, copying,
distribution, and decompilation/reverse engineering. No part of this document may be
reproduced in any form by any means without prior written authorization of Veritas Technologies
LLC and its licensors, if any.

THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED

CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED
WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR
NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH
DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. VERITAS TECHNOLOGIES LLC
SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN
CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS
DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS
SUBJECT TO CHANGE WITHOUT NOTICE.

The Licensed Software and Documentation are deemed to be commercial computer software
as defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19
"Commercial Computer Software - Restricted Rights" and DFARS 227.7202, et seq.
"Commercial Computer Software and Commercial Computer Software Documentation," as
applicable, and any successor regulations, whether delivered by Veritas as on premises or
hosted services. Any use, modification, reproduction release, performance, display or disclosure
of the Licensed Software and Documentation by the U.S. Government shall be solely in
accordance with the terms of this Agreement.

Veritas Technologies LLC

500 E Middlefield Road
Mountain View, CA 94043
http://www.veritas.com

Technical Support
Technical Support maintains support centers globally. All support services will be delivered
in accordance with your support agreement and the then-current enterprise technical support
policies. For information about our support offerings and how to contact Technical Support,
visit our website:

https://www.veritas.com/support

You can manage your Veritas account information at the following URL:

https://my.veritas.com

If you have questions regarding an existing support agreement, please email the support
agreement administration team for your region as follows:

Worldwide (except Japan) [email protected]

Japan [email protected]

Documentation
The latest documentation is available on the Veritas website:

https://sort.veritas.com/documents

Documentation feedback
Your feedback is important to us. Suggest improvements or report errors or omissions to the
documentation. Include the document title, document version, chapter title, and section title
of the text on which you are reporting. Send feedback to:

[email protected]

You can also see documentation information or ask a question on the Veritas community site:

http://www.veritas.com/community/

Veritas Services and Operations Readiness Tools (SORT)

Veritas Services and Operations Readiness Tools (SORT) is a website that provides information
and tools to automate and simplify certain time-consuming administrative tasks. Depending
on the product, SORT helps you prepare for installations and upgrades, identify risks in your
datacenters, and improve operational efficiency. To see what services and tools SORT provides
for your product, see the data sheet:

https://sort.veritas.com/data/support/SORT_Data_Sheet.pdf
 Contents

Chapter 1 Introducing SAN Client and Fibre Transport ............... 8

About NetBackup SAN Client and Fibre Transport ................................ 8
About Fibre Transport ..................................................................... 9
About Fibre Transport media servers ................................................ 10
About SAN clients ........................................................................ 10
About the Fibre Transport Service Manager ....................................... 11
About NetBackup Release Notes ..................................................... 11

Chapter 2 Planning your deployment .............................................. 12

Planning your SAN Client deployment .............................................. 12

SAN Client operational notes .......................................................... 13
About SAN Client storage destinations .............................................. 13
About SAN Client disk storage destinations ................................. 14
About SAN Client tape storage destinations ................................. 14
How to choose SAN Client and Fibre Transport hosts .......................... 15
About NetBackup SAN Client support for agents ................................. 15
About NetBackup SAN Client support for clustering ............................. 16
About NetBackup SAN Client support for Windows Hyper-V Server
........................................................................................... 16
About NetBackup SAN Client unsupported restores ............................. 17
About Fibre Transport throughput .................................................... 17
Converting a SAN media server to a SAN client .................................. 18

Chapter 3 Preparing the SAN ............................................................ 20

Preparing the SAN ........................................................................ 20

About zoning the SAN for Fibre Transport ......................................... 21
About zoning the SAN for Fibre Transport for a 16-gigabit target mode
HBA support .......................................................................... 23
About HBAs for SAN clients and Fibre Transport media servers ............. 25
About the 16-gigabit target mode HBAs for SAN clients and Fibre
Transport media servers .......................................................... 26
When selecting the HBA ports for SAN Client ..................................... 27
About supported SAN configurations for SAN Client ............................ 27
 Contents 5

Chapter 4 Licensing SAN Client and Fibre Transport ................ 29

About SAN Client installation .......................................................... 29

About the SAN Client license key ..................................................... 29
When upgrading SAN Client and Fibre Transport ................................ 29

Chapter 5 Configuring SAN Client and Fibre Transport ............. 31

Configuring SAN Client and Fibre Transport ....................................... 31
Configuring a Fibre Transport media server ....................................... 32
About the target mode driver ..................................................... 33
About nbhba mode and the ql2300_stub driver ............................. 34
About FC attached devices ....................................................... 34
How to identify the HBA ports ................................................... 35
About HBA port detection on Solaris ........................................... 36
About Fibre Transport media servers and VLANs .......................... 36
Starting nbhba mode ............................................................... 37
Marking the Fibre Transport media server HBA ports ..................... 38
Configuring the media server Fibre Transport services ................... 41
Configuring the media server Fibre Transport services for a
16-gigabit target mode HBA support ..................................... 45
Displaying the FTMS state for a 16-gigabit target mode HBA
support ........................................................................... 51
Identifying the HBA ports for a 16-gigabit target mode HBA support
..................................................................................... 52
Configuring SAN clients ................................................................. 52
About configuring firewalls for SAN clients ................................... 52
SAN client driver requirements .................................................. 53
Configuring the SAN client Fibre Transport service ........................ 54
Configuring SAN clients in a cluster .................................................. 55
Registering a SAN client cluster virtual name ............................... 56
Setting NetBackup configuration options by using the command
line ................................................................................ 57
About configuring Fibre Transport properties ...................................... 58
Configuring Fibre Transport properties .............................................. 59
Fibre Transport properties .............................................................. 60
About Linux concurrent FT connections ...................................... 63
About SAN client usage preferences ................................................ 64
Configuring SAN client usage preferences ......................................... 64
SAN client usage preferences ................................................... 65
 Contents 6

Chapter 6 Managing SAN clients and Fibre Transport .............. 67

Enabling or disabling the Fibre Transport services ............................... 67

Enabling or disabling the Fibre Transport services for a 16-gigabit
target mode HBA support ......................................................... 68
Rescanning for Fibre Transport devices from a SAN client .................... 68
Viewing SAN Client Fibre Transport job details ................................... 69
Viewing Fibre Transport traffic ......................................................... 70
Adding a SAN client ...................................................................... 71
Deleting a SAN client .................................................................... 71

Chapter 7 Disabling SAN Client and Fibre Transport ................. 72

About disabling SAN Client and Fibre Transport ................................. 72
Disabling a SAN client ................................................................... 72
Disabling a Fibre Transport media server .......................................... 73
Disabling a Fibre Transport media server for a 16-gigabit target mode
HBA support .......................................................................... 74

Chapter 8 Troubleshooting SAN Client and Fibre Transport

........................................................................................... 76

About troubleshooting SAN Client and Fibre Transport ......................... 77

SAN Client troubleshooting tech note ............................................... 77
Viewing Fibre Transport logs ........................................................... 77
About unified logging ..................................................................... 78
About using the vxlogview command to view unified logs .............. 79
Examples of using vxlogview to view unified logs .......................... 81
Stopping and starting Fibre Transport services ................................... 82
Stopping and starting Fibre Transport services for a 16-gigabit target
mode HBA support ................................................................. 83
Backups failover to LAN even though Fibre Transport devices available
........................................................................................... 84
Kernel warning messages when Veritas modules load ......................... 85
SAN client service does not start ..................................................... 85
SAN client Fibre Transport service validation ..................................... 85
SAN client does not select Fibre Transport ........................................ 86
Media server Fibre Transport device is offline ..................................... 87
No Fibre Transport devices discovered ............................................. 88

Appendix A AIX Specific Configuration Details ............................... 89

AIX Reference Information ............................................................. 89

Before you begin configuring NetBackup on AIX ................................. 89
 Contents 7

About AIX persistent naming support ................................................ 90

About configuring robotic control device files in AIX ............................. 90
About device files for SAN Clients on AIX .......................................... 90
About configuring tape drive device files in AIX ................................... 91
About non-QIC tape drives on AIX ............................................. 91
About no rewind device files on AIX ........................................... 91
Creating AIX no rewind device files for tape drives ........................ 92

Appendix B HP-UX Specific Configuration Details ......................... 95

HP-UX Reference Information ......................................................... 95
Before you begin configuring NetBackup on HP-UX ............................. 95
About HP-UX device drivers for legacy device files .............................. 96
About legacy robotic control device files ............................................ 96
About legacy tape drive device files .................................................. 96
About legacy pass-through paths for tape drives ................................. 97
Creating device files for SAN Clients on HP-UX .................................. 98
About configuring legacy device files ................................................ 98
Creating legacy SCSI and FCP robotic controls on HP-UX .............. 99
About creating legacy tape drive device files .............................. 106
Creating tape drive pass-through device files .............................. 106

Index .................................................................................................................. 112

 Chapter 1
Introducing SAN Client
and Fibre Transport
This chapter includes the following topics:

■ About NetBackup SAN Client and Fibre Transport

■ About Fibre Transport

■ About Fibre Transport media servers

■ About SAN clients

■ About the Fibre Transport Service Manager

■ About NetBackup Release Notes

About NetBackup SAN Client and Fibre Transport

SAN Client is a NetBackup optional feature that provides high-speed backups and
restores of NetBackup clients.
A SAN client is a special NetBackup client that can back up large amounts of data
rapidly over a SAN connection rather than a LAN. For example, a database host
can benefit from high-speed backups and restores. Fibre Transport is the name of
the NetBackup high-speed data transport method that is part of the SAN Client
feature.
The backup and restore traffic occurs over Fibre Channel (FC), and the NetBackup
server and client administration traffic occurs over the LAN.
For a NetBackup 52xx or 53xx appliance, Fibre Transport also provides high-speed
traffic to a NetBackup 5000 series appliance that supports Fibre Transport. The
5000 series appliance functions as the storage host for SAN client backups.
 Introducing SAN Client and Fibre Transport 9
About Fibre Transport

Figure 1-1 shows a SAN Client configuration.

Figure 1-1 A SAN Client configuration

SAN clients (database servers and

application hosts)

FT traffic zone

Fibre Transport media servers

Backup traffic zone

Disk and tape storage

About Fibre Transport

NetBackup Fibre Transport is a method of data transfer. It uses Fibre Channel and
a subset of the SCSI command protocol for data movement over a SAN rather than
TCP/IP over a LAN. It provides a high-performance transport mechanism between
NetBackup clients and NetBackup media servers.
Fibre Transport supports multiple, concurrent logical connections. The NetBackup
systems that support Fibre Transport contain Fibre Channel HBAs that are dedicated
to FT communication.
The NetBackup Fibre Transport service is active on both the SAN clients and the
NetBackup media servers that connect to the storage.
Throughout this documentation, Fibre Transport connections between NetBackup
clients and NetBackup servers are referred to as FT pipes.
 Introducing SAN Client and Fibre Transport 10
About Fibre Transport media servers

About Fibre Transport media servers

A NetBackup FT media server is a NetBackup media server on which the Fibre
Transport services are activated. NetBackup FT media servers accept connections
from SAN clients and send data to the disk storage.
The host bus adapters (HBAs) that accept connections from the SAN clients use
a special NetBackup target mode driver to process FT traffic.
The media server FT service controls data flow, processes SCSI commands, and
manages data buffers for the server side of the FT connection. It also manages the
target mode driver for the host bus adaptors.
Requires a license that activates the SAN Client feature
See “Configuring a Fibre Transport media server” on page 32.
See “Fibre Transport properties” on page 60.
See “About NetBackup SAN Client and Fibre Transport” on page 8.

About SAN clients

A NetBackup SAN client is a NetBackup client on which the Fibre Transport service
is activated. The SAN client is similar to the NetBackup SAN media server that is
used for the Shared Storage Option; it backs up its own data. However, the SAN
client is based on the smaller NetBackup client installation package, so it has fewer
administration requirements and uses fewer system resources.
Usually, a SAN client contains critical data that requires high bandwidth for backups.
It connects to a NetBackup media server over Fibre Channel.
The NetBackup SAN Client Fibre Transport Service manages the connectivity and
the data transfers for the FT pipe on the SAN clients. The SAN client FT service
also discovers FT target mode devices on the NetBackup media servers and notifies
the FT Service Manager about them.
http://www.veritas.com/docs/DOC5332
See “Configuring SAN clients” on page 52.
See “About configuring firewalls for SAN clients” on page 52.
See “SAN client driver requirements” on page 53.
See “Configuring the SAN client Fibre Transport service” on page 54.
 Introducing SAN Client and Fibre Transport 11
About the Fibre Transport Service Manager

About the Fibre Transport Service Manager

The FT Service Manager (FSM) resides on the NetBackup server that hosts the
NetBackup Enterprise Media Manager service. FSM interacts with the FT services
that run on SAN clients and on FT media servers. FSM discovers, configures, and
monitors FT resources and events. FSM runs in the same process as EMM.

About NetBackup Release Notes

For information about supported systems and peripherals, limitations, and operational
notes, see the NetBackup Release Notes:
http://www.veritas.com/docs/DOC5332
 Chapter 2
Planning your deployment
This chapter includes the following topics:

■ Planning your SAN Client deployment

■ SAN Client operational notes

■ About SAN Client storage destinations

■ How to choose SAN Client and Fibre Transport hosts

■ About NetBackup SAN Client support for agents

■ About NetBackup SAN Client support for clustering

■ About NetBackup SAN Client support for Windows Hyper-V Server

■ About NetBackup SAN Client unsupported restores

■ About Fibre Transport throughput

■ Converting a SAN media server to a SAN client

Planning your SAN Client deployment

Table 2-1 provides an overview of planning your deployment of SAN Client and
Fibre Transport.

Table 2-1 SAN Client deployment overview

Step Deployment task Section

Step 1 Read about best practices See “SAN Client operational notes” on page 13.
and operational notes
 Planning your deployment 13
SAN Client operational notes

Table 2-1 SAN Client deployment overview (continued)

Step Deployment task Section

Step 2 Determine the storage See “About SAN Client storage destinations”
destination on page 13.

Step 3 Determine the hosts to use See “How to choose SAN Client and Fibre
Transport hosts” on page 15.

Step 4 Prepare the SAN See “Preparing the SAN” on page 20.

Step 5 License SAN Client See “About the SAN Client license key”
on page 29.

Step 6 Read about NetBackup See “About NetBackup SAN Client support for
agents agents” on page 15.

Step 7 Read about SAN Client and See “About NetBackup SAN Client support for
Hyper-V Windows Hyper-V Server” on page 16.

Step 8 Configure SAN Client and See “Configuring SAN Client and Fibre Transport”
Fibre Transport on page 31.

Step 9 Convert a SAN media server See “Converting a SAN media server to a SAN
to a SAN Client client” on page 18.

SAN Client operational notes

The following items describe some operational items about which you should be
aware:
■ The NetBackup Client Encryption Option is not supported on UNIX and Linux
SAN clients.
■ Data compression or encryption can degrade Fibre Transport performance for
backups and restores.
If you use data compression or encryption for backups, Fibre Transport pipe
performance may degrade significantly for both backups and restores. In some
configurations, compression may reduce performance by up to 95% of
uncompressed performance.

About SAN Client storage destinations

You can use either disk or tape as a storage destination for the SAN Client and
Fibre Transport feature.
 Planning your deployment 14
About SAN Client storage destinations

NetBackup allows the storage devices to be connected to the FT media servers by

any means.

About SAN Client disk storage destinations

For disk storage, a NetBackup OpenStorage implementation provides the greatest
opportunity for high performance backups and restores. Those solutions can provide
enough bandwidth and read and write speed to accept the large volume of data
that the NetBackup Fibre Transport mechanism provides.
NetBackup media server deduplication is an OpenStorage implementation.
NetBackup client-side deduplication is not supported.

About SAN Client tape storage destinations

SAN Client can use tape as a destination storage unit. Some tape drives are fast
enough to read and write the large volume of data that the NetBackup Fibre
Transport mechanism provides.
With tape as a destination you can use multistreaming, which divides automatic
backups for a client into multiple jobs. Because the jobs are in separate data
streams, they can occur concurrently. The data streams can be sent over one or
more FT pipes to the FT media server. The media server multiplexes them together
onto one or more tape media volumes. For example, if you have a database server
that provides multiple streams of data, you can multistream those database backups
to an FT media server. The FT media server multiplexes the data streams onto the
media, increasing overall performance.
You can replace NetBackup SAN Media servers with SAN clients and continue to
back up to tape. A SAN Client uses fewer system resources, both disk space and
processor, than a SAN Media server.
To configure multistreaming, see the NetBackup Administrator's Guide, Volume I:
http://www.veritas.com/docs/DOC5332

SAN Client tape storage limitations

The following limitations exist for tape as a SAN Client storage destination:
■ Only FT backups from the same client are multiplexed in a particular MPX group.
■ FT backups from different clients are not multiplexed together in the same MPX
group.
■ You cannot multiplex different SAN clients to the same tape. Different clients
can still be backed up to the same FT media server, but they are written to
different tape drives in different MPX groups.
 Planning your deployment 15
How to choose SAN Client and Fibre Transport hosts

■ FT and LAN backups (from the same client or different clients) are not multiplexed
together in the same MPX group.
■ SAN Client does not support Inline Tape Copy over Fibre Transport; Inline Tape
Copy jobs occur over the LAN. The SAN Client features is designed for very
high speed backup and restore operations. Therefore, SAN Client excludes
backup options (such as Inline Tape Copy) that require more resources to
process and manage.

How to choose SAN Client and Fibre Transport

hosts
When you choose the systems to use for NetBackup Fibre Transport, be aware of
the following:
■ NetBackup SAN clients cannot also be NetBackup servers. Therefore, only
configure a NetBackup client to be a SAN client on systems on which only the
NetBackup client software is installed.
■ Do not use the NetBackup master server as an FT media server. Data transfer
consumes system resources and severely degrades NetBackup management
performance.

About NetBackup SAN Client support for agents

The SAN Client feature uses shared memory for data transfer. If you use a
NetBackup agent on a SAN client, the agent must have privileges to read and write
from that shared memory.
Ensure that the agent has the appropriate privileges, as follows:
■ On UNIX systems, install the NetBackup agent using the same user account
under which NetBackup is installed.
■ On Windows SAN clients, ensure that the NetBackup agent and the SAN Client
Fibre Transport Service use the same account (that is, Log On As). The account
must have Act as a part of the operating system privilege enabled. By default,
only the Local System account has the Act as a part of the operating system
privilege enabled.
SAN Client does not support the following type of agent backups:
■ Microsoft SharePoint
■ Enterprise Vault
 Planning your deployment 16
About NetBackup SAN Client support for clustering

■ Microsoft Exchange Database Availability Group (DAG) or Cluster Continuous

Replication (CCR) backups through a passive node of an Exchange cluster.

About NetBackup SAN Client support for

clustering
NetBackup supports SAN Clients in an application cluster. The following are the
requirements for the SAN Clients that are in an application cluster:
■ SAN Client must be installed on all failover nodes in the cluster.
■ The FT client service and the Veritas PBX service must run on all failover nodes.
■ The host computer operating system for each SAN client on each node must
detect the FT media server target mode drivers.
■ The NetBackup LOCAL_CACHE value must be NO on each SAN Client. By default,
the value is not specified, so you must configure the value.

Warning: Do not change the LOCAL_CACHE value on the FT media servers or

the master server.

See “Configuring SAN clients in a cluster” on page 55.

In the backup policy, you can use aliases or dynamic application cluster names for
the references to the SAN client computers. NetBackup updates SAN client
application cluster information every 5 minutes.

About NetBackup SAN Client support for Windows

Hyper-V Server
NetBackup SAN Client supports backups over Fibre Transport for the Windows
Hyper-V Server. Install the NetBackup client software on the Windows Hyper-V
Server and then configure the SAN Client on the Hyper-V Server. Do not install the
NetBackup client software or configure the SAN Client on the operating systems
within the Hyper-V virtual machines.
See “Configuring SAN clients” on page 52.
For backups, follow the procedures in the NetBackup™ for Hyper-V Administrator's
Guide to create a Hyper-V policy to back up the Hyper-V Server and its virtual
machines:
http://www.veritas.com/docs/DOC5332
 Planning your deployment 17
About NetBackup SAN Client unsupported restores

If SAN client and Fibre Transport are configured correctly, backups occur over Fibre
Transport.
NetBackup does not support Fibre Transport restores to the Windows Hyper-V
Server. Restores occur over the LAN.
See “About NetBackup SAN Client unsupported restores” on page 17.

About NetBackup SAN Client unsupported

restores
In most cases, if a backup uses the NetBackup Fibre Transport data transfer method,
a restore also occurs by the Fibre Transport method.
However, NetBackup may not support Fibre Transport restores for some NetBackup
options or for other products.
NetBackup does not support Fibre Transport restores for the following options:

FlashBackup restores SAN Client supports FlashBackup backups but restores occur
over the LAN.

Windows Hyper-V SAN Client supports backups over Fibre Transport but restores
restores occur over the LAN.

Depending on the options that you select when you configure the
backup policy, you can restore the virtual machines and also
individual files within the virtual machines.
See “About NetBackup SAN Client support for Windows Hyper-V
Server” on page 16.

About Fibre Transport throughput

The slowest speed of the following components may limit the Fibre Transport
throughput rate:
■ The speed capability of the SAN client.
The speed with which the client reads and writes to the file system or database
affects performance).
■ The read and write speed of the storage unit.
■ The bandwidth of the computer PCI I/O memory.
On the SAN clients, a non-PCI-X card on the PCI-X bus of the HBA reduces
the speed of the controlling bus. NetBackup FT performance may not be affected
 Planning your deployment 18
Converting a SAN media server to a SAN client

as much as on a media server, but performance may degrade to unacceptable

levels.
■ The speed of the Fibre Channel pipe that transports the data.
■ The topology of the Fibre Channel.
Bottlenecks may occur when multiple data streams are sent through a shared
element such as a trunk or an inter-switch link.

Converting a SAN media server to a SAN client

Table 2-2 provides an overview of how to convert a SAN media server to a SAN
client. The computer host name remains the same. This procedure assumes that
all NetBackup server run a release that supports the SAN Client feature.

Table 2-2 How to convert from a SAN media server to a SAN client

Step Task Instructions

Step 1 Delete the SAN media server Do the following:

■ In the NetBackup Administration Console,

in the left pane, select Media and Device
Management > Devices > Media Servers.
■ Select the host.
■ Select Actions > Enterprise Media Manager
Database > Remove Device Host.

Step 2 Uninstall the SAN media See the NetBackup Installation Guide for UNIX
server software and Windows:

http://www.veritas.com/docs/DOC5332

Step 3 Prepare for Fibre Transport Prepare the SAN for Fibre Transport and install
the HBAs on the Fibre Transport hosts and SAN
client hosts.

See “Preparing the SAN” on page 20.

Step 4 Connect the storage to the FT Connect the SAN media server storage device to
media server host the FT media server for the new SAN client. For
disk storage, mount the storage if necessary.

See “Preparing the SAN” on page 20.

 Planning your deployment 19
Converting a SAN media server to a SAN client

Table 2-2 How to convert from a SAN media server to a SAN client
(continued)

Step Task Instructions

Step 5 Install the NetBackup media Install the media server software on the hosts to
server software function as Fibre Transport media servers.

See the NetBackup Installation Guide for UNIX

and Windows:

http://www.veritas.com/docs/DOC5332

Step 6 Configure the FT media See “Configuring SAN Client and Fibre Transport”
servers on page 31.

Step 7 Install the NetBackup client Install the client software on the host that was the
software SAN media server.

See the NetBackup Installation Guide for UNIX

and Windows:

http://www.veritas.com/docs/DOC5332

Step 8 Configure the SAN client See “Configuring SAN Client and Fibre Transport”
on page 31.

Step 9 Configure alternate server Because the current host is no longer a media
restore server, configure an alternate server restore and
specify the FT media server as the Restore
server. NetBackup then uses the FT media server
to restore the images that were associated with
the SAN media server.

See Media host override in the General Server

properties of the Master Server Host Properties.

After all of the images that were associated with

the SAN media server expire, you can unconfigure
the alternate server restore.
 Chapter 3
Preparing the SAN
This chapter includes the following topics:

■ Preparing the SAN

■ About zoning the SAN for Fibre Transport

■ About zoning the SAN for Fibre Transport for a 16-gigabit target mode HBA
support

■ About HBAs for SAN clients and Fibre Transport media servers

■ About the 16-gigabit target mode HBAs for SAN clients and Fibre Transport
media servers

■ When selecting the HBA ports for SAN Client

■ About supported SAN configurations for SAN Client

Preparing the SAN

Table 3-1 shows the preparation steps and the order to perform them.

Table 3-1 SAN preparation overview

Step Procedure Section

Step 1 Zone the SAN See “About zoning the SAN for Fibre
Transport” on page 21.

Step 2 Install HBAs See “About HBAs for SAN clients and Fibre
Transport media servers” on page 25.

Step 3 Select HBA ports See “When selecting the HBA ports for SAN
Client” on page 27.
 Preparing the SAN 21
About zoning the SAN for Fibre Transport

Table 3-1 SAN preparation overview (continued)

Step Procedure Section

Step 4 Connect the fiber See “About supported SAN configurations for
SAN Client” on page 27.

About zoning the SAN for Fibre Transport

Before you can configure and use the NetBackup Fibre Transport (FT) mechanism,
the SAN must be configured and operational.
See “About supported SAN configurations for SAN Client” on page 27.
For SAN switched configurations, proper zoning prevents Fibre Transport traffic
from using the bandwidth that may be required for other SAN activity. Proper zoning
also limits the devices that the host bus adapter (HBA) ports discover; the ports
should detect the other ports in their zone only. Without zoning, each HBA port
detects all HBA ports from all hosts on the SAN. The potentially large number of
devices may exceed the number that the operating system supports.
Instructions for how to configure and manage a SAN are beyond the scope of the
NetBackup documentation. However, the following recommendations may help you
optimize your SAN traffic.
Table 3-2 describes the best practices for zoning the SAN on NetBackup appliances.

Table 3-2 Best practices for zoning the SAN on NetBackup appliances

Guideline Description

One initiator per zone, multiple targets Veritas recommends that you create zones with
acceptable. only a single initiator per zone. Multiple targets in
a single zone are acceptable, only if all of the
targets are similar.

Tape target resources should be in separate zones

from disk target resources, regardless of initiator.
However, both sets of resources may share the
same initiator.

Be aware of performance degradation If you use a single port as an initiator or a target

when a port is configured for multiple for multiple zones, this port can become a
zones. bottleneck for the overall performance of the
system. You must analyze the aggregate required
throughput of any part of the system and optimize
the traffic flow as necessary.
 Preparing the SAN 22
About zoning the SAN for Fibre Transport

Table 3-2 Best practices for zoning the SAN on NetBackup appliances
(continued)

Guideline Description

For fault tolerance, spread connectivity To ensure the availability of system connections,
across HBA cards and not ports. if you incorporate a multi-path approach to common
resources, pair ports on separate cards for like
zoning. This configuration helps you avoid the loss
of all paths to a resource in the event of a card
failure.

Zone the SAN based on WWN to It is recommended that you perform SAN zoning
facilitate zone migrations, if devices based on WWN. If switch port configurations or
change ports. cabling architectures need to change, the zoning
does not have to be recreated.

Table 3-3 describes the zones you should use for your SAN traffic.

Note: You must use physical port ID or World Wide Port Name (WWPN) when you
specify the HBA ports on NetBackup Fibre Transport media servers.
See “How to identify the HBA ports” on page 35.

Table 3-3 Fibre Channel zones

Zone Description

A Fibre Transport A Fibre Transport zone (or backup zone) should include only specific HBA ports of the hosts that
zone use Fibre Transport, as follows:

■ Ports on the FT media server HBAs that connect to the SAN clients. These ports use the
Veritas target mode driver.
See “About the target mode driver” on page 33.
■ Ports on the SAN client HBAs that connect to the media server ports that are in target mode.
The ports on the SAN clients use the standard initiator mode driver.
You must define the FT media server target ports by physical port ID or World Wide Port
Name (WWPN). The target mode driver WWPNs are not unique because they are derived
from the Fibre Channel HBA WWPN.
The NetBackup SAN clients should detect only the HBA ports that are in target mode on the
NetBackup media servers. They should not detect HBA ports in initiator mode on the NetBackup
media servers. They should not detect the FC HBAs on other hosts.
To promote multistream throughput, each SAN client should detect all target mode devices
of the media server HBA ports in the zone.
 Preparing the SAN 23
About zoning the SAN for Fibre Transport for a 16-gigabit target mode HBA support

Table 3-3 Fibre Channel zones (continued)

Zone Description

External storage If the storage is on a SAN, create an external storage zone. The zone should include the HBA
zone ports for the storage and the FT media server HBA ports that connect to the storage. All of the
ports in the storage zone use the standard initiator mode HBA driver.

About zoning the SAN for Fibre Transport for a

16-gigabit target mode HBA support
Before you can configure and use the NetBackup Fibre Transport (FT) mechanism,
the SAN must be configured and operational.
See “About supported SAN configurations for SAN Client” on page 27.
For SAN switched configurations, proper zoning prevents Fibre Transport traffic
from using the bandwidth that may be required for other SAN activity. Proper zoning
also limits the devices that the host bus adapter (HBA) ports discover; the ports
should detect the other ports in their zone only. Without zoning, each HBA port
detects all HBA ports from all hosts on the SAN. The potentially large number of
devices may exceed the number that the operating system supports.
Instructions for how to configure and manage a SAN are beyond the scope of the
NetBackup documentation. However, the following recommendations may help you
optimize your SAN traffic.
Table 3-4 describes the best practices for zoning the SAN on NetBackup appliances
and NBU FTMS with 16Gb HBA.

Table 3-4 Best practices for zoning the SAN on NetBackup appliances

Guideline Description

One initiator per zone, multiple targets Veritas recommends that you create zones with
acceptable. only a single initiator per zone. Multiple targets in
a single zone are acceptable, only if all of the
targets are similar.

Tape target resources should be in separate zones

from disk target resources, regardless of initiator.
However, both sets of resources may share the
same initiator.
 Preparing the SAN 24
About zoning the SAN for Fibre Transport for a 16-gigabit target mode HBA support

Table 3-4 Best practices for zoning the SAN on NetBackup appliances
(continued)

Guideline Description

Be aware of performance degradation If you use a single port as an initiator or a target

when a port is configured for multiple for multiple zones, this port can become a
zones. bottleneck for the overall performance of the
system. You must analyze the aggregate required
throughput of any part of the system and optimize
the traffic flow as necessary.

For fault tolerance, spread connectivity To ensure the availability of system connections,
across HBA cards and not ports. if you incorporate a multi-path approach to common
resources, pair ports on separate cards for like
zoning. This configuration helps you avoid the loss
of all paths to a resource in the event of a card
failure.

Zone the SAN based on WWN to It is recommended that you perform SAN zoning
facilitate zone migrations, if devices based on WWN. If switch port configurations or
change ports. cabling architectures need to change, the zoning
does not have to be recreated.

Note: To enable the SAN client 16-GB target mode driver support for HBA ports,
you must create zones with only one initiator and keep only one target mode per
zone.

Table 3-5 describes the zones you should use for your SAN traffic.

Note: You must use physical port ID or World Wide Port Name (WWPN) when you
specify the HBA ports on NetBackup Fibre Transport media servers.
See “How to identify the HBA ports” on page 35.
 Preparing the SAN 25
About HBAs for SAN clients and Fibre Transport media servers

Table 3-5 Fibre Channel zones

Zone Description

A Fibre Transport A Fibre Transport zone (or backup zone) should include only specific HBA ports of the hosts that
zone use Fibre Transport, as follows:

■ Ports on the FT media server HBAs that connect to the SAN clients. These ports use the
Veritas target mode driver.
See “About the target mode driver” on page 33.
■ Ports on the SAN client HBAs that connect to the media server ports that are in target mode.
The ports on the SAN clients use the standard initiator mode driver.
You must define the FT media server target ports by physical port ID or World Wide Port
Name (WWPN). The target mode driver WWPNs are not unique because they are derived
from the Fibre Channel HBA WWPN.
The NetBackup SAN clients should detect only the HBA ports that are in target mode on the
NetBackup media servers. They should not detect HBA ports in initiator mode on the NetBackup
media servers. They should not detect the FC HBAs on other hosts.
To promote multistream throughput, each SAN client should detect all target mode devices
of the media server HBA ports in the zone.

External storage If the storage is on a SAN, create an external storage zone. The zone should include the HBA
zone ports for the storage and the FT media server HBA ports that connect to the storage. All of the
ports in the storage zone use the standard initiator mode HBA driver.

About HBAs for SAN clients and Fibre Transport

media servers
The Fibre Channel host bus adapter (HBA) and driver requirements differ on the
SAN clients and on the NetBackup FT media servers, as follows:

HBAs on SAN clients The HBAs on the SAN clients can be any supported Fibre
Channel HBA. The HBA ports must operate in the default
initiator mode.
For the HBAs on the SAN client systems, do the following:

■ Install the drivers for the HBA.

■ Install the utilities for the HBA. Although not required for
NetBackup operation, the utilities may help to troubleshoot
connectivity problems.
 Preparing the SAN 26
About the 16-gigabit target mode HBAs for SAN clients and Fibre Transport media servers

HBAs on NetBackup FT The NetBackup media servers that host Fibre Transport
media servers require the following:

■ For the connections to the SAN clients, use a QLogic HBA

that NetBackup supports for Fibre Transport. For these
HBAs, you must configure them to use the NetBackup
target mode driver.
See “About nbhba mode and the ql2300_stub driver”
on page 34.
■ If you use SAN attached storage, you can use any
supported Fibre Channel HBA to connect to the storage.
For these HBAs, you should install the QLogic driver and
utilities. The HBA ports that connect to the storage must
remain in the default initiator mode.
■ The HBAs and their drivers must support 256K size
buffers for data transfer.

Note: To enable the SAN client 16-GB target mode driver support for HBA ports,
you must create zones with only one initiator and keep only one target mode per
zone. Each NetBackup client can have a zone with only one Fibre Transport media
server.

For information about supported HBAs, see the Hardware Compatibility List at the
following URL:
http://www.netbackup.com/compatibility
See “Preparing the SAN” on page 20.

About the 16-gigabit target mode HBAs for SAN

clients and Fibre Transport media servers
The Fibre Channel host bus adapter (HBA) and driver requirements differ on the
SAN clients and on the NetBackup FT media servers, as follows:

HBAs on SAN clients The HBAs on the SAN clients can be any supported Fibre
Channel HBA. The HBA ports must operate in the default
initiator mode.
For the HBAs on the SAN client systems, do the following:

■ Install the drivers for the HBA.

■ Install the utilities for the HBA. Although not required for
NetBackup operation, the utilities may help to troubleshoot
connectivity problems.
 Preparing the SAN 27
When selecting the HBA ports for SAN Client

HBAs on NetBackup FT The NetBackup media servers that host Fibre Transport
media servers require the following:

■ For the connections to the SAN clients, use a QLogic HBA

that NetBackup supports for Fibre Transport. For these
HBAs, you must configure them to use the NetBackup
target mode driver.
■ QLogic HBA can only be used as target. You can use
Emulex HBA to work as initiators, if initiator HBA is
needed.

For information about supported HBAs, see the Hardware Compatibility List at the
following URL:
http://www.netbackup.com/compatibility
See “Preparing the SAN” on page 20.

When selecting the HBA ports for SAN Client

You must have adequate HBA ports in the FT media servers to support the FT
pipes from the SAN clients. If you also use SAN attached storage, the media servers
must have enough HBA ports to connect to the shared storage.
You must determine which ports to use for FT connections between the NetBackup
media servers and the SAN clients, as follows:
■ Determine which Fibre Channel HBAs you want to use for FT connections on
the systems on which the NetBackup media servers are installed.
■ Determine which Fibre Channel ports you want to use for FT connections on
each SAN client.
All ports on QLogic HBAs must be either in target mode or initiator mode. You
cannot connect one port on an HBA to a SAN client and another port to the storage.

About supported SAN configurations for SAN

Client
NetBackup supports the following SAN configurations for Fibre Transport:
 Preparing the SAN 28
About supported SAN configurations for SAN Client

Node port (N_Port) switched Connect the NetBackup media servers and SAN clients to a
configuration SAN switch as follows:

■ Connect the HBA port on the NetBackup FT media server

to a Fibre Channel switch port.
■ Connect each SAN client HBA port to ports on the same
Fibre Channel switch.
■ Define the zones on the switch so that the client(s) and
server(s) are in the same zone. Be aware of the following:
■ You must define the NetBackup FT media server
target ports by physical port ID or World Wide Port
Name (WWPN). The target mode driver WWPNs are
not unique because they are derived from the Fibre
Channel HBA WWPN.
■ You can define SAN client ports by either port ID or
WWPN. However, if you use one method only, zone
definition and management is easier.

Fibre Channel arbitrated loop Use Fibre Channel arbitrated loop (FC-AL) to connect a
(FC-AL) configuration NetBackup FT media server HBA port directly to a NetBackup
SAN client HBA port.
Note: FC-AL hubs are not supported.
 Chapter 4
Licensing SAN Client and
Fibre Transport
This chapter includes the following topics:

■ About SAN Client installation

■ About the SAN Client license key

■ When upgrading SAN Client and Fibre Transport

About SAN Client installation

No special installation is required for the core NetBackup Fibre Transport
components. However, you must activate the feature by entering a license for the
feature.
See “About the SAN Client license key” on page 29.

About the SAN Client license key

On the NetBackup master server, enter the license that activates the SAN Client
feature.
If the license expires or is unavailable (such as in a disaster recovery situation),
backups and restores occur over the LAN.

When upgrading SAN Client and Fibre Transport

When you upgrade NetBackup, all components are upgraded including the SAN
client and Fibre Transport components.
 Licensing SAN Client and Fibre Transport 30
When upgrading SAN Client and Fibre Transport

For NetBackup upgrade installation instructions, see the NetBackup Installation

Guide for UNIX and Windows:
http://www.veritas.com/docs/DOC5332
 Chapter 5
Configuring SAN Client
and Fibre Transport
This chapter includes the following topics:

■ Configuring SAN Client and Fibre Transport

■ Configuring a Fibre Transport media server

■ Configuring SAN clients

■ Configuring SAN clients in a cluster

■ About configuring Fibre Transport properties

■ Configuring Fibre Transport properties

■ Fibre Transport properties

■ About SAN client usage preferences

■ Configuring SAN client usage preferences

Configuring SAN Client and Fibre Transport

To configure SAN Client and Fibre Transport, you must complete multiple procedures
on multiple computers.
All of the NetBackup hosts that you use for SAN Client and Fibre Transport must
be provisioned with host ID-based security certificates. The hosts must be able to
communicate with each other.
Table 5-1 shows the configuration steps and the order to perform them.
 Configuring SAN Client and Fibre Transport 32
Configuring a Fibre Transport media server

Table 5-1 SAN Client and Fibre Transport configuration process

Step Task Section

Step 1 Configure the FT media servers See “Configuring a Fibre Transport media server”
on page 32.

Step 2 Configure the SAN clients See “Configuring SAN clients” on page 52.

See “Configuring SAN clients in a cluster”

on page 55.

Step 3 Configure FT properties See “About configuring Fibre Transport properties”

on page 58.

Step 4 Configure SAN client usage preferences See “SAN client usage preferences” on page 65.

Configuring a Fibre Transport media server

Table 5-2 describes the process for configuring an FT media server.

Table 5-2 Process to configure an FT media server

Step Task Section

Step 1 Read the conceptual information about This information that may help you avoid serious problems.
configuring an FT media server
See “About Linux concurrent FT connections” on page 63.

See “About HBAs for SAN clients and Fibre Transport media
servers” on page 25.

See “About the target mode driver” on page 33.

See “About nbhba mode and the ql2300_stub driver”

on page 34.

See “About FC attached devices” on page 34.

See “How to identify the HBA ports” on page 35.

See “About HBA port detection on Solaris” on page 36.

See “About Fibre Transport media servers and VLANs”

on page 36.

Step 2 Start nbhba mode on the media server See “Starting nbhba mode” on page 37.

Step 3 Mark the HBA ports See “Marking the Fibre Transport media server HBA ports”
on page 38.

Step 4 Configure the FT services See “Configuring the media server Fibre Transport services”
on page 41.
 Configuring SAN Client and Fibre Transport 33
Configuring a Fibre Transport media server

Configuring a Fibre Transport media server with a

16-gigabit target mode HBA support
Table 5-3 Process to configure an FT media server with a 16-gigabit target
mode HBA support

Step Task Section

Step 1 Read the conceptual information about This information that may help you avoid serious problems.
configuring an FT media server
See “About Linux concurrent FT connections” on page 63.

See “About the target mode driver” on page 33.

See “About Fibre Transport media servers and VLANs”

on page 36.

Step 2 Configure the FT services See “Configuring the media server Fibre Transport services
for a 16-gigabit target mode HBA support” on page 45.

Step 3 Displaying the FTMS state for a See “Displaying the FTMS state for a 16-gigabit target mode
16-gigabit target mode HBA support HBA support” on page 51.

(Optional)

Step 4 Identifying the HBA ports for a 16-gigabit See “Identifying the HBA ports for a 16-gigabit target mode
target mode HBA support HBA support” on page 52.

(Optional)

About the target mode driver

On NetBackup FT media servers, QLogic Fibre Channel host bus adapter (HBA)
ports connect to the NetBackup SAN clients. Veritas provides a special target mode
driver for the ports on those HBAs. Those ports must operate in target mode; the
target mode driver replaces the default, initiator mode driver. Target mode applies
only to QLogic HBAs; the target mode configuration process affects only QLogic
HBA ports.
After the target mode driver binds to the HBA ports, those ports appear as two
ARCHIVE Python tape devices during SCSI inquiry. However, they are not tape
devices and do not appear as tape devices in NetBackup device discovery. Each
port appears as two tape devices because operating systems allow only one data
stream per port. Two pseudo tape devices for each port increases throughput.
See “About Linux concurrent FT connections” on page 63.
 Configuring SAN Client and Fibre Transport 34
Configuring a Fibre Transport media server

About nbhba mode and the ql2300_stub driver

The first step of the process to configure the media server HBA drivers is to start
nbhba mode. The nbhba mode binds the Veritas provided ql2300_stub driver to
all QLogic ISP2312 and ISP24xx HBA ports on the host.
The ql2300_stub driver prevents the standard initiator mode driver from binding
to the ports. If the QLogic driver binds to the HBA ports, the NetBackup nbhba
command cannot mark the ports that you want to operate in target mode. The target
mode driver also cannot bind to the HBA ports.
The ql2300_stub driver also lets NetBackup read and modify the device ID in
NVRAM of the QLogic ports. After you start nbhba mode and mark the ports of the
QLogic HBAs that connect to the SAN clients, those ports operate in target mode.
The computer exits nbhba mode when the FT server starts.

Note: For Linux operating systems, warning messages may be displayed in the
console or the system log when the ql2300_stub driver is loaded into the kernel.
See “Kernel warning messages when Veritas modules load” on page 85.

About FC attached devices

In nbhba mode, all devices that are attached to QLogic ISP2312 and ISP24xx HBA
ports are unavailable. If disk or tape devices are attached to QLogic HBAs, those
devices become unavailable. They remain unavailable until you exit nbhba mode
on that computer.

Warning: Do not configure HBAs on a computer that has a start device that is
attached to a QLogic ISP2312 or ISP24xx port. If you do, the computer may become
unbootable. If any critical file systems are mounted on any devices that are attached
to a QLogic HBA, the computer also may become unbootable. Before you begin
HBA configuration, dismount any file systems that are attached to a QLogic HBA.

To determine if devices are attached to QLogic HBAs, you should examine your
devices and your mounted file systems.
You can configure the QLogic HBAs on a different NetBackup media server that
does not contain a QLogic HBA connected start device. Then, you can install them
in the NetBackup FT media servers and configure the FT services. Afterward, you
should remove the nbhba driver from the media server on which you configured the
HBAs.
See “Disabling a Fibre Transport media server” on page 73.
 Configuring SAN Client and Fibre Transport 35
Configuring a Fibre Transport media server

The process also ends nbhba mode on that computer.

How to identify the HBA ports

If the computer on which you mark ports contains multiple HBAs, it may be difficult
to determine how the World Wide Names (WWNs) relate to the HBAs. The
NetBackup nbhba command that marks the HBA ports requires the port WWN. The
port WWN also may be known as the World Wide Port Name (WWPN).
To avoid problems, you can install all of the QLogic HBAs in a NetBackup media
server that has no other Fibre Channel HBAs installed. You can mark all HBA ports
and then install the HBAs in the appropriate NetBackup media servers.

Warning: A QLogic HBA may exist as a chipset on a motherboard. To avoid

problems, you should determine if the computer contains built-in QLogic ports.

If you cannot mark ports in a computer that has only the QLogic HBAs that you
want to mark, the following may help:
■ The HBA may identify the port WWNs on the card. Examine the HBA for the
WWNs.
■ The Fibre Channel switch may display WWNs for attached and operational HBA
ports.
■ The SAN utility software may provide the capability to list the WWNs of the HBA
ports.
■ On Solaris 10, you can list WWNs for native drivers by using the fcinfo
hba-port command.

■ The NetBackup nbhba command -l option lets you compare the port WWN
addresses easily. (The computer must be in nbhba mode.) For the QLA-234x
series, the port WWNs on the same card differ in the second byte and the sixth
byte. The following example shows two, two-port HBAs. Lines 1 and 2 are one
HBA; lines 3 and 4 are the other HBA.

/usr/openv/netbackup/bin/admincmd/nbhba -l
1 2312 21:00:00:E0:8B:83:9D:A1 "QLA2342 " 0 0 101
2 2312 21:01:00:E0:8B:A3:9D:A1 "QLA2342 " 1 0 101
3 2312 21:00:00:E0:8B:8F:28:7B "QLA2342 " 0 0 101
4 2312 21:01:00:E0:8B:AF:28:7B "QLA2342 " 1 0 101

This output also shows that the ports are in initiator mode. The second rightmost
column shows 0, and the rightmost column does not begin with 8.
 Configuring SAN Client and Fibre Transport 36
Configuring a Fibre Transport media server

■ If the HBA contains LEDs on the metal mounting bracket, the color changes to
green after you mark a port (yellow is initiator mode). (The computer must be
in nbhba mode.) You can see if you marked the ports in the correct card. If you
did not, you can return those ports to initiator mode and then mark other ports
until you mark the correct ones.

About HBA port detection on Solaris

On systems earlier than Solaris 10 Update 7, NetBackup detects the PCI bus and
allows ports on one bus only to be used for target mode.
The following is the port detection behavior on systems earlier than Solaris 10
Update 7:
■ The first choice is the bus with the most 2312 target mode ports.
■ If there are no 2312 target mode ports, the bus with the most 24xx target mode
ports is used.
■ Target mode ports on other busses are not used.
Beginning with Solaris 10 Update 7, target ports on more than one bus are supported
on Solaris 10.

About Fibre Transport media servers and VLANs

For an FT media server that has multiple network interfaces for VLANs, NetBackup
must recognize the primary network interface of the host before any other network
interfaces for the host. Each NetBackup host recognizes other NetBackup hosts
by using its Additional Servers list. The Additional Servers list appears in the
NetBackup Administration Console host properties Servers page for that host.
Ensure that the FT server’s primary host name appears before any other interface
names for that FT media server host. Do so in the Additional Servers lists of the
following NetBackup hosts:
■ The master server.
■ The FT media server.
■ All of the SAN clients that the FT media server backs up.
You may be able to use operating system commands to determine the primary
interface. UNIX-type operating systems have a hostname command, which displays
the short name of the primary interface. They also have a domainname command,
which shows the domain name of the primary interface. On Windows, you can use
the ipconfig -all command to display host and domain information.
 Configuring SAN Client and Fibre Transport 37
Configuring a Fibre Transport media server

See “Backups failover to LAN even though Fibre Transport devices available ”
on page 84.

Starting nbhba mode

Before you mark HBA ports, you must start nbhba mode, which binds the
ql2300_stub driver to the QLogic HBA ports.

To start nbhba mode, see the following:

■ To start nbhba mode on Linux
■ To start nbhba mode on Solaris
You must be the root user.
To start nbhba mode on Linux
1 Ensure that the HBAs are not connected to the SAN.
2 Invoke the nbftsrv_config -nbhba command and option. The computer
enters nbhba mode. The following is an example; output on your system may
differ:

/usr/openv/netbackup/bin/admincmd/nbftsrv_config -nbhba
Installing nbhba driver.
Are you sure you want to unload QLogic driver: qla2300? [y,n]
(y)

3 Answer y to unload the QLogic driver. The process continues as follows:

Removing qla2300

Note: For Linux operating systems, warning messages may be displayed in

the console or the system log when the ql2300_stub driver is loaded into the
kernel.
See “Kernel warning messages when Veritas modules load” on page 85.

4 Continue by marking the HBA ports.

See “Marking the Fibre Transport media server HBA ports” on page 38.
 Configuring SAN Client and Fibre Transport 38
Configuring a Fibre Transport media server

To start nbhba mode on Solaris

1 Ensure that the HBAs are not connected to the SAN.
2 Invoke the nbftsrv_config -nbhba command and option. The computer
enters nbhba mode. The following is an example; output on your system may
differ:

/usr/openv/netbackup/bin/admincmd/nbftsrv_config -nbhba
Installing nbhba driver.
Waiting for driver references to ql2300_stub to free up (this
may take some time).
The following driver aliases need to be removed:
qlc "pci1077,2312.1077.10a"
Would you like to run update_drv to remove these now? [y,n] (y)

3 Answer y to remove any driver aliases. The process continues as follows:

/usr/sbin/update_drv -v -d -i "pci1077,2312.1077.10a" qlc

Done copying driver into system directories.
Done adding driver.
MUST REBOOT TO COMPLETE INSTALLATION.

4 Reboot the host.

5 Continue by marking the HBA ports.
See “Marking the Fibre Transport media server HBA ports” on page 38.

Marking the Fibre Transport media server HBA ports

You must mark the ports on the QLogic HBAs that you want to operate in target
mode. The process modifies the port device IDs in NVRAM. When the FT server
starts, the NetBackup target mode driver binds automatically to the QLogic HBA
ports that you marked.
Before you mark ports, you must start nbhba mode.
See “Starting nbhba mode” on page 37.
The following procedures describe how to mark the HBA ports and if necessary
how to reverse this process and return the ports to the initiator mode driver:
■ To mark the HBA ports
■ To revert to the initiator mode driver
You must be the root user to make these changes.
 Configuring SAN Client and Fibre Transport 39
Configuring a Fibre Transport media server

To mark the HBA ports

1 Display the QLogic HBA ports on the media server by using the nbhba command
with the -l option. The following is an example; output on your system may
differ:

/usr/openv/netbackup/bin/admincmd/nbhba -l
1 2312 21:00:00:E0:8B:83:9D:A1 "QLA2342 " 0 0 101
2 2312 21:01:00:E0:8B:A3:9D:A1 "QLA2342 " 1 0 101
3 2312 21:00:00:E0:8B:8F:28:7B "QLA2342 " 0 0 101
4 2312 21:01:00:E0:8B:AF:28:7B "QLA2342 " 1 0 101

For the QLA-234x series, the port WWNs on the same card differ in the second
byte and the sixth byte. This output shows two, two-port HBAs. Lines 1 and 2
are one HBA; lines 3 and 4 are the other HBA. The HBAs are in initiator mode:
the second rightmost column shows 0, and the rightmost column does not
begin with 8.
Alternatively, use the nbhba -L option to produce verbose output, which lets
you identify the mode more easily.
2 Mark the ports by using the nbhba command. The following is the syntax:

/usr/openv/netbackup/bin/admincmd/nbhba -modify -wwn string

-mode target

For example, the following two commands change the two ports on one of the
HBAs from the example output in step 1:

nbhba -modify -wwn 21:00:00:E0:8B:8F:28:7B -mode target

nbhba -modify -wwn 21:01:00:E0:8B:AF:28:7B -mode target
 Configuring SAN Client and Fibre Transport 40
Configuring a Fibre Transport media server

3 Verify the changes by using the nbhba command and -L option to display the
HBA card ports on the server. The following is an example; output on your
system may differ:

/usr/openv/netbackup/bin/admincmd/nbhba -L
HBA Port #1
Device ID = 2312
World Wide Name = 21:00:00:E0:8B:83:9D:A1
Model Name = "QLA2342 "
Port = 0
Mode = initiator (designated for other use)(101)
HBA Port #2
Device ID = 2312
World Wide Name = 21:01:00:E0:8B:A3:9D:A1 "QLA2342
Model Name = "QLA2342 "
Port = 1
Mode = initiator (designated for other use)(101)
HBA Port #3
World Wide Name = 21:00:00:E0:8B:8F:28:7B
Slot = ""
Port = 0
Fibre Not Attached
Mode = target (designated for FT Server)(8101)
HBA Port #4
World Wide Name = 21:01:00:E0:8B:AF:28:7B
Slot = ""
Port = 1
Fibre Not Attached
Mode = target (designated for FT Server)(8101)

The nbhba -l option also produces the output that lets you identify the mode:

/usr/openv/netbackup/bin/admincmd/nbhba -l
1 2312 21:00:00:E0:8B:83:9D:A1 "QLA2342 " 0 0 101
2 2312 21:01:00:E0:8B:A3:9D:A1 "QLA2342 " 1 0 101
3 2312 21:00:00:E0:8B:8F:28:7B "QLA2342 " 0 1 8101
4 2312 21:01:00:E0:8B:AF:28:7B "QLA2342 " 1 1 8101

The rightmost two columns show the ports that are marked for target mode:
the second rightmost column shows 1, and the rightmost column begins with
8. The other digits in the rightmost column are not significant.
4 If necessary, transfer the HBAs to the appropriate media servers.
 Configuring SAN Client and Fibre Transport 41
Configuring a Fibre Transport media server

5 If necessary, connect the HBAs to the SAN.

6 Continue by configuring the FT services.
See “Configuring the media server Fibre Transport services” on page 41.
To revert to the initiator mode driver
◆ Invoke the nbhba command on the NetBackup FT server in which the HBA is
installed. The following is the command syntax:

/usr/openv/netbackup/bin/admincmd/nbhba -modify -wwn

world_wide_port_name -mode initiator

Configuring the media server Fibre Transport services

You must configure the media server FT services before you configure the SAN
clients. The FT server must run on the media servers so that the client operating
system discovers the target mode driver (the FT device). Two services (nbftsrvr
and nbfdrv64) comprise the NetBackup FT server that runs on media servers.
The nbftsrv_config script configures the media server for Fibre Transport. In this
process, the script does the following:
■ Installs the required drivers
■ Installs the FT server start-up scripts
■ Starts the FT server
When the FT server starts, the NetBackup target mode driver binds automatically
to the QLogic HBA ports that you marked. (The default QLogic driver is bound
already to the ports that are not marked.) The HBA ports operate in target mode
until you configure them to use the standard initiator mode again.
■ Ends the nbhba mode on the computer (if it was in nbhba mode)
Configure the FT services on every NetBackup media server that connects to SAN
clients.
For procedures, see the following:
■ To configure Fibre Transport services on Linux
■ To configure Fibre Transport services on Solaris
You must be the root user.
 Configuring SAN Client and Fibre Transport 42
Configuring a Fibre Transport media server

Note: After you configure the Fibre Transport media servers using the
nbftsrv_config and the nbftserver scripts, reload the target driver for the HBA
port on the NetBackup SAN clients that were used for backup and restore. This
step ensures that the client operating system detects the tape devices that the Fibre
Transport media servers export. Alternatively, you can restart the client computers
to reload the drivers and refresh the device tree.
 Configuring SAN Client and Fibre Transport 43
Configuring a Fibre Transport media server

To configure Fibre Transport services on Linux

1 Run the nbftsrv_config script. The following is an example; output on your
system may differ:

/usr/openv/netbackup/bin/admincmd/nbftsrv_config
Installing the Jungo driver and Fibre Transport Server.
The following automatic startup and shutdown scripts
(respectively) have been installed. They will cause the
NetBackup Fibre Transport Server daemon to be automatically shut
down and restarted each time the system boots.
/etc/rc.d/rc2.d/S21nbftserver
/etc/rc.d/rc3.d/S21nbftserver
/etc/rc.d/rc5.d/S21nbftserver
/etc/rc.d/rc0.d/K03nbftserver
/etc/rc.d/rc1.d/K03nbftserver
/etc/rc.d/rc6.d/K03nbftserver
It may be necessary to temporarily unload your QLogic drivers
to free up the ports for the nbhba drivers.
This is an optional step. If you choose not to do this, you may
not have access to all of the HBA ports until a subsequent
reboot.
Would you like to uninstall and reinstall your native QLogic
drivers now? [y,n] (y) y

2 The Qlogic drivers must be unloaded temporarily so that the stub driver
(ql2300_stub) can bind to the marked HBA ports during this session.
If you answer y, you do not have to reboot the computer during this configuration
process. However, any critical devices that are attached to QLogic HBAs in
the computer may be unavailable during this session. To ensure that the critical
devices remain available, answer n. Then, you must reboot when prompted.
The stub driver binds to the marked ports during the boot process, and the
default QLogic drivers bind to the unmarked ports.
If you answer n, go to step 5.
If you answer y, you are prompted again to unload each QLogic driver, as
follows:

Are you sure you want to unload QLogic driver: qla2300? [y,n]
(y) y
 Configuring SAN Client and Fibre Transport 44
Configuring a Fibre Transport media server

3 To unload the QLogic driver, answer y. The process continues as follows:

Removing qla2300
Adding qla2300.
Adding qla2xxx.
Would you like to start the SANsurfer agent (qlremote)? [y,n]
(y) y

4 If the QLogic SANsurfer agent was loaded, the configuration process asks if
you want to start the agent. To start the QLogic SANsurfer agent, answer y.
The process continues as follows:

Starting qlremote agent service

Started SANsurfer agent.
/etc/udev/permissions.d/50-udev.permissions updated with Jungo
WinDriver permissions.
NetBackup Fibre Transport Server started.
Would you like to make these changes persist after a reboot?
[y,n] (y) y

5 To ensure that the FT server always starts after a computer reboot, answer y.
The process continues as follows:

Running mkinitrd. Previous initrd image is saved at

/boot/initrd-2.6.9-11.ELsmp.img.05-21-07.11:24:03.

If you answered y in step 2, the FT services are started, and the target mode
driver binds to the marked HBA ports.
6 If you answered n in step 2, reboot the computer when prompted.
The FT services are started, and the target mode driver binds to the marked
HBA ports.
 Configuring SAN Client and Fibre Transport 45
Configuring a Fibre Transport media server

To configure Fibre Transport services on Solaris

1 Run the nbftsrv_config script. The following is an example; output on your
system may differ:

/usr/openv/netbackup/bin/admincmd/nbftsrv_config
Installing the Jungo driver and Fibre Transport Server.
Waiting for driver references to ql2300_stub to free up (this
may take some time).
The following automatic startup and shutdown scripts
(respectively) have been installed. They will cause the
NetBackup Fibre Transport Server daemon to be automatically shut
down and restarted each time the system boots.
/etc/rc2.d/S21nbftserver
/etc/rc0.d/K03nbftserver
Adding "pci1077,2312.1077.101" to qlc.
No third party drivers found with conflicting driver aliases.
Done copying driver into system directories.
Done adding driver.MUST REBOOT TO COMPLETE INSTALLATION.

2 Reboot the host.

The FT services are started, and the target mode driver binds to the marked
HBA ports.

Configuring the media server Fibre Transport services for a 16-gigabit

target mode HBA support
You must configure the media server FT services before you configure the SAN
clients. The FT server must run on the media servers so that the client operating
system discovers the target mode driver (the FT device). One service (nbftsrvr)
comprises of the NetBackup FT server that runs on media servers.
The nbftsrv_config script configures the media server for Fibre Transport. In this
process, the script does the following:
■ Installs the required drivers
■ Installs the FT server start-up scripts
■ Starts the FT server
When the FT server starts, the NetBackup target mode driver binds automatically
to the QLogic HBA ports. The HBA ports operate in target mode until you disable
FTMS.
Configure the FT services on every NetBackup media server that connects to SAN
clients.
 Configuring SAN Client and Fibre Transport 46
Configuring a Fibre Transport media server

For procedures, see the following:

■ To configure Fibre Transport services on Linux
You must be the root user.

Note: After you configure the Fibre Transport media servers using the
nbftsrv_config and the nbftserver scripts, reload the target driver for the HBA
port on the NetBackup SAN clients that were used for backup and restore. This
step ensures that the client operating system detects the tape devices that the Fibre
Transport media servers export. Alternatively, you can restart the client computers
to reload the drivers and refresh the device tree.
 Configuring SAN Client and Fibre Transport 47
Configuring a Fibre Transport media server

To configure Fibre Transport services on Linux

1 Run the nbftsrv_config script. The following is an example; output on your
system may differ:

/usr/openv/netbackup/bin/admincmd/nbftsrv_config -scst -install

Checking for SCST drivers and firmwares in the package. [yes]
Checking whether the server is not NetBackup Appliance. [yes]
Checking for kernel version 3.10.0-1062. [yes]
Checking for QLE2692 QLogic 16/32Gb HBA cards on the server. [yes]
DISCLAIMER:
-----------
NOTE:
1. When you install the SAN client with 16Gb HBA, the script stops
the original qla2xxx driver and updates the firmware
ql2500_fw.bin. Only QLE2562 and QLE2692 16Gb HBA models are
supported by this NetBackup version.
2. Ensure that there is no other process that uses the HBAs. If
there is an active process that uses qla2xxx, manually restart
the process after the installation completes.
3. If you use the SANsurfer agent during the deployment of the
environment, the script stops and restarts the SANsurfer agent
daemon (qlremote).
4. Stop all the backup jobs that use the FT user interface.

Do you acknowledge this disclaimer? [y,n] (n)y

 Configuring SAN Client and Fibre Transport 48
Configuring a Fibre Transport media server

2 The QLogic drivers are reloaded so that the HBA ports can be detected during
this session.

Proceeding to deploy SCST environment [ok]

Reload driver qla2xxx

Removing qla2xxx.
Load driver qla2xxx

HBA-Type Port WWN Status Supported Speeds Current Speed

QLE2692 21:00:f4:e9:d4:53:bb:c4 Online 8 Gbit, 16 Gbit, 32 Gbit
16 Gbit
QLE2692 21:00:f4:e9:d4:53:bb:c5 Linkdown 8 Gbit, 16 Gbit, 32 Gbit
unknown
QLE2692 21:00:00:24:ff:16:ce:9c Online 8 Gbit, 16 Gbit, 32 Gbit
16 Gbit
QLE2692 21:00:00:24:ff:16:ce:9d Linkdown 8 Gbit, 16 Gbit, 32 Gbit
unknown
QLE2562 21:00:00:24:ff:42:2d:78 Linkdown 1 Gbit, 2 Gbit, 4 Gbit,
8 Gbit unknown
QLE2562 21:00:00:24:ff:42:2d:79 Linkdown 1 Gbit, 2 Gbit, 4 Gbit,
8 Gbit unknown

NOTE:
The types of HBA cards listed are QLE2692 and QLE2562. Some of
the WWNs may be used to connect to an external storage and other
external devices.

Do you want to continue? [y,n] (n)y

 Configuring SAN Client and Fibre Transport 49
Configuring a Fibre Transport media server

3 Enter the port numbers and make sure of the operation warnings during this
session.

Please input the Port WWNs you want to use as the targets
(separated by commas like: wwn1,wwn2...):21:00:f4:e9:d4:53:bb:c4
The input is: 21:00:f4:e9:d4:53:bb:c4
The targets you defined: 21:00:f4:e9:d4:53:bb:c4
Do you want to redefine the targets? [y,n] (n)
Do you want to add additional targets? [y,n] (n)
The targets you defined: 21:00:f4:e9:d4:53:bb:c4
The targets you have defined contain 16Gb HBA cards.

NOTE:
1. Make sure that you do not use a WWN that is used to connect
to external storage.
2. Make sure to define the input WWNs as targets.
3. Make sure the WWNs can be zoned with WWNs of clients.
Do you want to continue to setup the WWNs as targets? [y,n] (n)y
 Configuring SAN Client and Fibre Transport 50
Configuring a Fibre Transport media server

4 The FTMS environment is deployed.

--------------------------------------------
FTMS environment installation started.
--------------------------------------------
Successfully created the dependent path: /var/lib/scst/pr.
Successfully created the dependent path:
/var/lib/scst/vdev_mode_pages.
Successfully backup the ql2500_fw.bin to ql2500_fw_original.bin.
Successfully copied
/usr/openv/netbackup/bin/driver/ql2500-firmware-8.04.00.bin to
/lib/firmware.
Successfully copied
/usr/openv/netbackup/bin/driver/ql2700-firmware-8.07.10.bin to
/lib/firmware.
Successfully created the new link /lib/firmware/ql2500_fw.bin.
Successfully created the new link /lib/firmware/ql2700_fw.bin.
Successfully copied
/usr/openv/netbackup/bin/driver/ql2500-firmware-8.04.00-LICENSE
to /usr/share/doc/ql2500-firmware-8.04.00.
Successfully copied
/usr/openv/netbackup/bin/driver/scst/qla2xxx.ko.3.10.0-1062.el7.x86_64
to /lib/modules/3.10.0-1062.el7.x86_64/extra/qla2xxx.ko.
Successfully copied
/usr/openv/netbackup/bin/driver/scst/qla2x00tgt.ko.3.10.0-1062.el7.x86_64
to /lib/modules/3.10.0-1062.el7.x86_64/extra/qla2x00tgt.ko.
Successfully copied
/usr/openv/netbackup/bin/driver/scst/scst.ko.3.10.0-1062.el7.x86_64
to /lib/modules/3.10.0-1062.el7.x86_64/extra/scst.ko.
Successfully copied
/usr/openv/netbackup/bin/driver/scst/scst_user.ko.3.10.0-1062.el7.x86_64
to /lib/modules/3.10.0-1062.el7.x86_64/extra/scst_user.ko.
Successfully created /etc/modprobe.d/qla2xxx_scst.conf.
Successfully copied /usr/openv/netbackup/bin/nbftsrvr to
/usr/openv/netbackup/bin/nbftsrvr_old.
Successfully copied
/usr/openv/netbackup/bin/goodies/nbftserver_scst to
/etc/rc.d/init.d/nbftserver.
Successfully linked /etc/rc.d/init.d/nbftserver
/etc/rc.d/rc2.d/S21nbftserver.
Successfully linked /etc/rc.d/init.d/nbftserver
/etc/rc.d/rc3.d/S21nbftserver.
Successfully linked /etc/rc.d/init.d/nbftserver
 Configuring SAN Client and Fibre Transport 51
Configuring a Fibre Transport media server

/etc/rc.d/rc5.d/S21nbftserver.
Successfully linked /etc/rc.d/init.d/nbftserver
/etc/rc.d/rc0.d/K03nbftserver.
Successfully linked /etc/rc.d/init.d/nbftserver
/etc/rc.d/rc1.d/K03nbftserver.
Successfully linked /etc/rc.d/init.d/nbftserver
/etc/rc.d/rc6.d/K03nbftserver.
Successfully enabled nbftserver.
Successfully created /etc/modules-load.d/scst.conf.
Enable target: 21:00:f4:e9:d4:53:bb:c4
Previous initramfs image is saved at
/boot/initramfs-3.10.0-1062.el7.x86_64.img.07-19-20.22:43:29.
Running dracut, it may take several minutes to complete...
/sbin/dracut succeeded
NetBackup Fibre Transport Server started.
-------------------------------
Driver qla2xxx is loaded
-------------------------------
Driver qla2x00tgt is loaded
-------------------------------
Driver scst is loaded
-------------------------------
Driver scst_user is loaded
--------------------------------------------
FTMS environment installation completed.

Displaying the FTMS state for a 16-gigabit target mode HBA support
The NetBackup nbftsrv_config command's -scst -state option informs you
about the state of the FTMS. The computer must have enabled FTMS for a 16Gb
target mode HBA support.
For example:

/usr/openv/netbackup/bin/admincmd/nbftsrv_config -scst -list_port

FTMS Target Ports List:

21:00:f4:e9:d4:53:bb:c4

FTMS deamon(nbftsrvr) state:

FTMS deamon (nbftsrvr) is running.

The command displays the defined FTMS target ports and the state of the FTMS
deamon.
 Configuring SAN Client and Fibre Transport 52
Configuring SAN clients

Identifying the HBA ports for a 16-gigabit target mode HBA support
The NetBackup nbftsrv_config command's -scst -list_port option helps you
identify the port World Wide Names (WWNs) or World Wide Port Names (WWPNs)
that are defined as targets. The computer must have enabled FTMS for a 16Gb
target mode HBA support.
For example:

/usr/openv/netbackup/bin/admincmd/nbftsrv_config -scst -list_port

HBA-Type Port WWN Status Current Set Mode Supported Current

Mode Speeds Speed

QLE2692 21:00: Online Target Target 8 Gbit, 16 16 Gbit

f4:e9:d4: Gbit
53:bb:c4

Note: The types of HBA cards that get listed are QLE2692 and QLE2562. The
QLogic HBA can only be used as a target. You can use Emulex HBA to work as
an initiator, if an initiator HBA is required.

Configuring SAN clients

Table 5-4 shows the steps to configure SAN clients.

Table 5-4 SAN Client and Fibre Transport configuration process

Step Task Section

Step 1 Configure firewalls on SAN clients See “About configuring firewalls for SAN clients”
on page 52.

Step 2 Configure SAN client drivers See “SAN client driver requirements” on page 53.

Step 3 Configure the SAN client FT service See “Configuring the SAN client Fibre Transport
service” on page 54.

About configuring firewalls for SAN clients

NetBackup SAN clients require connectivity to the NetBackup master server.
Therefore, you must ensure that any firewall (software or hardware) allows the
clients to communicate with the NetBackup master server.
 Configuring SAN Client and Fibre Transport 53
Configuring SAN clients

SAN client driver requirements

The operating systems of the NetBackup SAN clients may require device drivers
that allow SCSI pass-through methods for the Fibre Transport traffic.
If the SAN client operating system is configured correctly, it recognizes each media
server HBA port in target mode as two ARCHIVE Python devices.
Table 5-5 lists the driver requirements for each supported SAN client operating
system.

Table 5-5 SAN client operating system driver requirements

Operating system Driver requirements

AIX Client systems require the standard tape driver. The driver should
work without modification.

For information about how to configure the driver, see the

NetBackup Device Configuration Guide, available at the following
URL:

http://www.veritas.com/docs/DOC5332

HP-UX Client systems require the sctl driver and pass-through device
files.

For information about how to configure the driver, see the

NetBackup Device Configuration Guide, available at the following
URL:

http://www.veritas.com/docs/DOC5332

Linux Client systems require the SCSI Generic (sg) driver and
pass-through device files.

For information about how to configure the driver, see the

NetBackup Device Configuration Guide, available at the following
URL:

http://www.veritas.com/docs/DOC5332

Solaris You must modify the /kernel/drv/st.conf file so that Solaris

recognizes the FT devices on the NetBackup media servers.

For information about how to do so, see the NetBackup Device

Configuration Guide, available at the following URL:

http://www.veritas.com/docs/DOC5332

Windows A device driver is not required. The media server FT devices

appear in the Windows Device Manager "Other devices" section
as ARCHIVE Python SCSI Sequential Devices.
 Configuring SAN Client and Fibre Transport 54
Configuring SAN clients

Some operating systems require specific patch and driver updates. For information
about them, see the NetBackup Release Notes:
http://www.veritas.com/docs/DOC5332

Configuring the SAN client Fibre Transport service

You must enable the SAN Client Fibre Transport Service on the NetBackup clients
that you want to function as SAN clients. During this process, the SAN client
operating system discovers the FT devices on the FT media servers.

Warning: NetBackup SAN clients cannot also be NetBackup servers. Therefore,

only configure a client to be a SAN client on systems on which the NetBackup client
software only is installed.

See “Configuring SAN clients in a cluster” on page 55.

See “Registering a SAN client cluster virtual name” on page 56.
To configure a NetBackup client to be a SAN client
1 Verify that the Veritas PBX service is active on the client, as follows:
■ On UNIX and Linux systems, run theNetBackup bpps -x command and
verify that the pbx_exchange process is active.
■ On Windows systems, use the Computer Management console to verify
that the Veritas Private Branch Exchange service is active.

2 On the client, run the following command to enable the SAN Client Fibre
Transport Service (nbftclnt):
UNIX and Linux:
/usr/openv/netbackup/bin/bpclntcmd -sanclient 1

Windows:
install_path\NetBackup\bin\bpclntcmd.exe -sanclient 1

3 Do the following to start the SAN client FT service:

■ Linux: Boot the system, which also begins operating system device
discovery. (Alternatively, you can run the NetBackup bp.start_all
command to start the client FT service.)
■ AIX, HP-UX, and Solaris: Run the NetBackup bp.start_all command.
The command resides in the following directory:
/usr/openv/netbackup/bin
 Configuring SAN Client and Fibre Transport 55
Configuring SAN clients in a cluster

■ Windows: Boot the system, which also begins operating system device
discovery.

4 On the systems that were not booted in step 3, perform the action that forces
the SAN client operating system to discover devices.
The operating system must discover two FT devices for each media server
HBA port that is in target mode.
The SAN Client Fibre Transport Service (nbftclnt) validates the driver stack
functionality during device discovery. If validation fails, Fibre Transport is not
enabled on the client.
See “SAN client Fibre Transport service validation” on page 85.
After the client OS discovers the FT devices, the SAN client is registered with
NetBackup. You should not have to add the SAN client either manually or by
using the Device Configuration Wizard.
5 If the client system does not discover the FT devices, verify the following:
■ The Fibre Channel driver is installed on the SAN client.
■ The SAN client HBA port is active on the Fibre Channel switch.
■ The media server HBA port is active on the Fibre Channel switch.
■ The SAN client is logged into the Fibre Channel switch name server.
■ The FT media server is logged into the Fibre Channel switch name server.
■ The FT media server port is zoned with the SAN client port.
■ The zone is included in the active configuration.
Alternatively, you can try a scan operation for FT devices on a client system.
See “Rescanning for Fibre Transport devices from a SAN client” on page 68.

Configuring SAN clients in a cluster

The SAN Client FT service is not a cluster application. To protect the SAN clients
that are in a cluster, you must configure all of the SAN clients in the cluster correctly.
See “Setting NetBackup configuration options by using the command line”
on page 57.
See “Configuring SAN clients” on page 52.
 Configuring SAN Client and Fibre Transport 56
Configuring SAN clients in a cluster

Table 5-6 Process to configure a SAN client in a cluster

Step Action Description

Step 1 Install the NetBackup client See the NetBackup Installation Guide for UNIX
software on each failover and Windows:
node
http://www.veritas.com/docs/DOC5332

Step 2 Configure the SAN client on Ensure that the FT service is active on all of the
each failover node failover nodes.

See “About configuring firewalls for SAN clients”

on page 52.

See “SAN client driver requirements” on page 53.

See “Configuring the SAN client Fibre Transport

service” on page 54.

Step 3 Register the virtual node See “Registering a SAN client cluster virtual name”
name with the EMM server on page 56.

Step 4 Configure the NetBackup On each SAN Client in the cluster, set the
local cache NetBackup LOCAL_CACHE option to NO.

See “About NetBackup SAN Client support for

clustering” on page 16.

See “Setting NetBackup configuration options by

using the command line” on page 57.
Warning: Do not change the LOCAL_CACHE
value on the FT media servers or the master
server.

Registering a SAN client cluster virtual name

If you use a cluster to protect a client, you must register the cluster virtual name
with the NetBackup Enterprise Media Manager.
See “Configuring SAN clients in a cluster” on page 55.
To register a cluster virtual name
1 Add the virtual name to the EMM database. The following is the command
syntax:
nbemmcmd –addhost –machinename virtual_name –machinetype
app_cluster

The following is the path to the nbemmcmd command:

 Configuring SAN Client and Fibre Transport 57
Configuring SAN clients in a cluster

■ UNIX: /usr/openv/netbackup/bin/admincmd
■ Windows: install_path\Program
Files\VERITAS\NetBackup\bin\admincmd

2 For every client in the node, update the host so the virtual name is linked to
the client host name. The following is the command syntax:
nbemmcmd –updatehost –add_server_to_app_cluster –machinename
client_name –clustername virtual_name

Setting NetBackup configuration options by using the command line

Veritas recommends that you use the NetBackup Administration Console Host
Properties to configure NetBackup properties.
However, some properties cannot be set by using the Administration Console.
You can set those properties by using the following NetBackup commands:

For a NetBackup server: bpsetconfig

For a NetBackup client: nbsetconfig

Configuration options are key and value pairs, as shown in the following examples:
■ CLIENT_READ_TIMEOUT = 300

■ LOCAL_CACHE = NO

■ RESUME_ORIG_DUP_ON_OPT_DUP_FAIL = TRUE

■ SERVER = server1.example.com

You can specify some options multiple times, such as the SERVER option.
 Configuring SAN Client and Fibre Transport 58
About configuring Fibre Transport properties

To set configuration options by using the command line

1 In a command window or shell window on the host on which you want to set
the property, invoke the appropriate command. The command depends on the
operating system and the NetBackup host type (client or server), as follows:

UNIX On a NetBackup client:

/usr/openv/netbackup/bin/nbsetconfig

On a NetBackup server:

/usr/openv/netbackup/bin/admincmd/bpsetconfig

Windows On a NetBackup client:

install_path\NetBackup\bin\nbsetconfig.exe

On a NetBackup server:

install_path\NetBackup\bin\admincmd\bpsetconfig.exe

2 At the command prompt, enter the key and the value pairs of the configuration
options that you want to set, one pair per line.
You can change existing key and value pairs.
You can add key and value pairs.
Ensure that you understand the values that are allowed and the format of any
new options that you add.
3 To save the configuration changes, type the following, depending on the
operating system:
Windows: Ctrl + Z Enter
UNIX: Ctrl + D Enter

About configuring Fibre Transport properties

NetBackup Fibre Transport properties control how your SAN clients use the Fibre
Transport services for backups. NetBackup uses a hierarchy of properties to provide
increasingly granular control of how your clients use NetBackup Fibre Transport.
The following table describes the levels of property configuration in the Host
Properties of the NetBackup Administration Console.
 Configuring SAN Client and Fibre Transport 59
Configuring Fibre Transport properties

Table 5-7 Fibre Transport properties

Granularity Description

Global FT properties for all Global FT properties apply to all SAN clients. Global FT
SAN clients properties are configured on the master server.

Configure these properties in Host Properties > Master

Servers in the NetBackup Administration Console.

FT properties for a media FT properties for a media server or servers apply to the SAN
server or media servers clients that the media server or servers back up. The
properties override the global FT properties that are
configured on the master server.

Configure these properties in Host Properties > Media

Servers in the NetBackup Administration Console.

FT properties for a SAN client FT properties for a client or clients apply to the specific SAN
or SAN clients client or clientss. FT properties for SAN clients override the
media server FT properties.

Configure these properties in Host Properties > Clients in

the NetBackup Administration Console.

See “Configuring Fibre Transport properties” on page 59.

NetBackup provides one finer level of granularity for Fibre Transport. SAN client
usage preferences override the FT properties that you configure through Host
Properties.
See “SAN client usage preferences” on page 65.
See “Configuring SAN Client and Fibre Transport” on page 31.

Configuring Fibre Transport properties

NetBackup Fibre Transport properties control how your SAN clients use the Fibre
Transport services for backups. NetBackup uses a hierarchy of properties to provide
increasingly granular control of how your clients use NetBackup Fibre Transport.
See “About configuring Fibre Transport properties” on page 58.
 Configuring SAN Client and Fibre Transport 60
Fibre Transport properties

To configure NetBackup FT properties

1 In the NetBackup Administration Console, in the left pane, expand
NetBackup Management > Host Properties.
2 Depending on which level of properties you want to configure, do one of the
following:

To configure global FT properties Select Master Servers.

To configure FT properties for a media Select Media Servers.

server or servers

To configure FT properties for a client or Select Clients.

clients

3 Select the host or hosts to configure, as follows:

■ To configure the properties on one host, double-click the name of the host
in the right pane.
■ To configure properties for more than one host, select the hosts and then
on the Actions menu select Properties.

4 In the host properties dialog box, click Fibre Transport in the left pane.
5 Configure the properties.
See “Fibre Transport properties” on page 60.

Fibre Transport properties

NetBackup Fibre Transport properties control how your Fibre Transport media
servers and SAN clients use the Fibre Transport service for backups and restores.
The Fibre Transport properties apply to the host type that you select in the
NetBackup Administration Console, as follows:

Table 5-8 Host types for Fibre Transport properties

Host type Description

Master server Global Fibre Transport properties that apply to all SAN clients.

Media server The Fibre Transport Maximum concurrent FT connections

property applies to the FT media server or servers that you selected
in the NetBackup Administration Console.
 Configuring SAN Client and Fibre Transport 61
Fibre Transport properties

Table 5-8 Host types for Fibre Transport properties (continued)

Host type Description

Client The Fibre Transport properties apply to the SAN client or clients
that you selected in the NetBackup Administration Console. The
default values for clients are the global property settings of the master
server. Client properties override the global Fibre Transport
properties.

Figure 5-1 Fibre Transport host properties for a master server

Table 5-9 describes the Fibre Transport properties. All properties are not available
for all hosts. In this table, FT device is an HBA port on a Fibre Transport media
server. The port carries the backup and restore traffic. A media server may have
more than one FT device.
 Configuring SAN Client and Fibre Transport 62
Fibre Transport properties

Table 5-9 Fibre Transport dialog box properties

Property Description

Maximum concurrent FT This property appears only when you select an FT media server or servers in the
connections NetBackup Administration Console.

This property specifies the number of FT connections to allow to the selected

media server or media servers. A connection is equivalent to a job.
If no value is set, NetBackup uses the following defaults:

■ For NetBackup Appliance model 5330 and later: 32

■ For NetBackup Appliance model 5230 and later: 32
■ For NetBackup Fibre Transport media servers: 8 times the number of fast HBA
ports on the media server plus 4 times the number of slow HBA ports. A fast
port is 8 GB or faster, and a slow port is less than 8 GB.
You can enter up to the following maximum connections for the media server or
servers to use:

■ On a Linux FT media server host: 40.

It is recommended that you use 32 or fewer connections concurrently on Linux.
On Linux hosts, you can increase that maximum by setting a NetBackup touch
file, NUMBER_DATA_BUFFERS_FT.
See “About Linux concurrent FT connections” on page 63.
■ For NetBackup Appliance model 5330 and later: 40.
■ For NetBackup Appliance model 5230 and later: 40.
■ On a Solaris FT media server host: 64.

NetBackup supports 644 buffers per media server for Fibre Transport. To
determine the number of buffers that each connection uses, divide 644 by the
value you enter. More buffers per connection equal better performance for each
connection.

Use defaults from the master This property appears only when you select a client or client in the NetBackup
server configuration Administration Console.

This property specifies that the client follow the properties as they are configured
on the master server.

Preferred The Preferred property specifies to use an FT device if one is available within
the configured wait period in minutes. If an FT device is not available after the
wait period elapses, NetBackup uses a LAN connection for the operation.

If you select this option, also specify the wait period for backups and for restores.

For the global property that is specified on the master server, the default is
Preferred.
 Configuring SAN Client and Fibre Transport 63
Fibre Transport properties

Table 5-9 Fibre Transport dialog box properties (continued)

Property Description

Always The Always property specifies that NetBackup should always use an FT device
for backups and restores of SAN clients. NetBackup waits until an FT device is
available before it begins the operation.

However, an FT device must be online and up. If not, NetBackup uses the LAN.
An FT device may be unavailable because none are active, none have been
configured, or the SAN Client license expired.

Fail The Fail property specifies that NetBackup should fail the job if an FT device is
not online and up. If the FT devices are online but busy, NetBackup waits until a
device is available and assigns the next job to the device. An FT device may be
unavailable because none are active, none have been configured, or the SAN
Client license expired.

Never The Never property specifies that NetBackup should never use an FT pipe for
backups and restores of SAN clients. NetBackup uses a LAN connection for the
backups and restores.

If you specify Never for the master server, Fibre Transport is disabled in the
NetBackup environment. If you select Never, you can configure FT usage on a
per-client basis.

If you specify Never for a media server, Fibre Transport is disabled for the media
server.

If you specify Never for a SAN client, Fibre Transport is disabled for the client.

See “Configuring Fibre Transport properties” on page 59.

NetBackup provides one finer level of granularity for Fibre Transport. SAN client
usage preferences override the FT properties that you configure through Host
Properties.
See “About SAN client usage preferences” on page 64.

About Linux concurrent FT connections

NetBackup uses the Maximum concurrent FT connections Fibre Transport host
property to configure the number of concurrent connections to a Fibre Transport
media server, up to the total that is allowed per host.
See “Fibre Transport properties” on page 60.
If the total number of concurrent connections on Linux is too low for your purposes,
you can increase the total number of concurrent connections. The consequence is
that each client backup or restore job uses fewer buffers, which means that each
job is slower because of fewer buffers. To increase the number of concurrent
 Configuring SAN Client and Fibre Transport 64
About SAN client usage preferences

connections, reduce the number of buffers per connection. To do so, create the
following file and include one of the supported values from Table 5-10 in the file:
/usr/openv/netbackup/db/config/NUMBER_DATA_BUFFERS_FT

Table 5-10 shows the values that NetBackup supports for the
NUMBER_DATA_BUFFERS_FT file. NetBackup supports 644 buffers per media server
for Fibre Transport.

Table 5-10 Supported values for buffers per FT connection

NUMBER_DATA_BUFFERS_FT Total concurrent Total concurrent

connections: NetBackup connections: Linux FT
5230 and 5330 and later media server
appliances

16 40 40

12 53 53

10 64 64

If you want, you then can limit the number of connections for a media server or
media servers by using the Maximum concurrent FT connections of the Fibre
Transport host properties.

About SAN client usage preferences

SAN client usage preferences let you configure how a SAN client uses NetBackup
Fibre Transport for backups.
See “Configuring SAN client usage preferences” on page 64.
The usage preferences override the FT transport properties.
See “About configuring Fibre Transport properties” on page 58.

Configuring SAN client usage preferences

SAN client usage preferences let you configure how a specific client uses NetBackup
Fibre Transport for backups.
SAN client usage preferences override the NetBackup Fibre Transport properties.
 Configuring SAN Client and Fibre Transport 65
Configuring SAN client usage preferences

To configure SAN client usage preferences by using the Devices node

1 In the NetBackup Administration Console, in the left pane, expand Media
and Device Management > Devices.
2 Select SAN Clients.
3 Select a client or clients in the right pane.
4 On the Actions menu, select SAN Client Usage Preferences.
5 In the SAN Client Usage Preferences dialog box, configure the properties.

See “SAN client usage preferences” on page 65.

SAN client usage preferences

The following table describes the Fibre Transport usage preferences for SAN clients.

Table 5-11 SAN client Fibre Transport usage preferences

Property Description

Use defaults from the master This property specifies that the client follow the properties as they are configured
server configuration on the master server.
 Configuring SAN Client and Fibre Transport 66
Configuring SAN client usage preferences

Table 5-11 SAN client Fibre Transport usage preferences (continued)

Property Description

Preferred The Preferred property specifies to use an FT device if one is available within
the configured wait period in minutes. If an FT device is not available after the
wait period elapses, NetBackup uses a LAN connection for the operation.

If you select this option, also specify the wait period for backups and for restores.

For the global property that is specified on the master server, the default is
Preferred.

Always The Always property specifies that NetBackup should always use an FT device
for backups and restores of SAN clients. NetBackup waits until an FT device is
available before it begins the operation.

However, an FT device must be online and up. If not, NetBackup uses the LAN.
An FT device may not exist because none is active, none have been configured,
or the SAN Client license expired.

Fail The Fail property specifies that NetBackup should fail the job if an FT device is
not online and up. If the FT devices are online but busy, NetBackup waits until a
device is available and assigns the next job to the device. An FT device may not
exist because none is active, none have been configured, or the SAN Client
license expired.

Never The Never property specifies that NetBackup should never use an FT pipe for
backups and restores of SAN clients. NetBackup uses a LAN connection for the
backups and restores.
If you specify Never for the master server, Fibre Transport is disabled in the
NetBackup environment. If you select Never, you can configure FT usage on a
per-client basis.

If you specify Never for a media server, Fibre Transport is disabled for the media
server.

If you specify Never for a SAN client, Fibre Transport is disabled for the client.
 Chapter 6
Managing SAN clients and
Fibre Transport
This chapter includes the following topics:

■ Enabling or disabling the Fibre Transport services

■ Enabling or disabling the Fibre Transport services for a 16-gigabit target mode
HBA support

■ Rescanning for Fibre Transport devices from a SAN client

■ Viewing SAN Client Fibre Transport job details

■ Viewing Fibre Transport traffic

■ Adding a SAN client

■ Deleting a SAN client

Enabling or disabling the Fibre Transport services

You can enable or disable the FT services on NetBackup FT media servers.
The following are the services that compose the FT server:
■ The nbftsrvr service manages the server side of the FT pipe.
■ The nbfdrv64 service controls the target mode drivers on the media server.
The nbftsrvr service starts the nbfdrv64 service. If you stop one, the other stops.
If one ends abnormally, the other stops.
These services do not appear in the NetBackup Activity Monitor; they do appear
in the operating system process displays.
 Managing SAN clients and Fibre Transport 68
Enabling or disabling the Fibre Transport services for a 16-gigabit target mode HBA support

Warning: Do not use the UNIX kill -9 command and option to stop the nbfdrv64
process. It does not allow the process to stop gracefully, and the SAN clients cannot
detect the FT devices when the nbfdrv64 process dies. You then may have to
restart the client systems so they detect the FT devices again (after you restart
nbfdrv64).

To enable or disable FT services

1 In the NetBackup Administration Console on the master server, in the left
pane, expand Media and Device Management > Devices > Media Server.
2 Select an FT media server in the right pane.
3 Click either Actions > Enable FT Services or Actions > Disable FT Services.

Enabling or disabling the Fibre Transport services

for a 16-gigabit target mode HBA support
You can enable or disable the FT services on NetBackup FT media servers.
The following is the service that composes the FT server:
■ The nbftsrvr service manages the server side of the FT pipe.
This service does not appear in the NetBackup Activity Monitor; it does appear
in the operating system process displays.
To enable or disable FT services
1 In the NetBackup Administration Console on the master server, in the left
pane, expand Media and Device Management > Devices > Media Server.
2 Select an FT media server in the right pane.
3 Click either Actions > Enable FT Services or Actions > Disable FT Services.

Rescanning for Fibre Transport devices from a

SAN client
A rescan operation tries to find new FT devices from the client. If the scan detects
new FT devices, NetBackup adds them to the EMM database. A rescan operation
is a time- and compute-intensive operation. It may not discover new devices
(especially if the client system requires a restart and you do not restart it).
Depending on the operating system capabilities and the HBA driver and its settings,
the scan may search for new Fibre Channel devices.
 Managing SAN clients and Fibre Transport 69
Viewing SAN Client Fibre Transport job details

To rescan SAN clients

1 On Microsoft Windows clients, use the Windows Device Manager to scan for
hardware changes.
2 In the NetBackup Administration Console, in the left pane, expand Media
and Device Management > Devices > SAN Clients.
3 Select a client in the right pane.
4 Click Action > Rescan SAN Client FT Devices.
5 In the Rescan SAN Client dialog box, monitor the following status of the
operation:
■ Initiated
■ Client system must be restarted
■ Failure

6 If required, restart the client system.

Viewing SAN Client Fibre Transport job details

The NetBackup Administration Console Activity Monitor Jobs tab displays all of
the jobs that are in progress or have been completed.
The Transport column in the Jobs tab window shows the type of transport between
the SAN client and the NetBackup media server: FT for Fibre Transport or blank
for inactive or for a LAN.
The Detailed Status tab of the Job Details dialog shows more detailed information
about the job, including the following:
■ A Transport Type field in the header area shows the same information as the
Transport column in the Jobs tab.
■ Messages in the Status window show the status of jobs that use FT transport,
as follows:
■ Queuing for FT transport
■ Allocated FT transport
■ Opening FT connection
■ Closing FT connection

See “Viewing Fibre Transport traffic” on page 70.

 Managing SAN clients and Fibre Transport 70
Viewing Fibre Transport traffic

To view job details

◆ Double-click the job in the Jobs tab.
The Job Details dialog appears that contains detailed job information on a
Job Overview tab and a Detailed Status tab.

Viewing Fibre Transport traffic

You can view the current activity between FT media servers and SAN clients. The
following two views are available:

FT media server The media server view shows all of the inbound backup (and outbound
view restore) traffic for a selected FT media server.

Use this view to determine which SAN clients can send data to and
receive data from the selected media server.

See “To view FT activity from the media server perspective” on page 70.

SAN Client view The SAN client view shows all of the outbound backup (and inbound
restore) traffic for a selected client.

Use this view to determine which FT media servers can send data to
and receive data from the selected client.

See “To view FT activity from the client perspective” on page 70.

See “Viewing SAN Client Fibre Transport job details” on page 69.
To view FT activity from the media server perspective
1 In the NetBackup Administration Console, in the left pane, expand Media
and Device Management > Devices > Media Server.
2 Select an FT media server in the right pane.
3 Click Actions > View FT Connections.
The Media Server Fibre Transport View dialog box shows the connection
activity for the media server.
To view FT activity from the client perspective
1 In the NetBackup Administration Console, in the left pane, expand Media
and Device Management > Devices > SAN Clients.
2 Select a client in the right pane.
3 Click Actions > View FT Connections.
The SAN Client Fibre Transport View dialog box shows the connection activity
for the client.
 Managing SAN clients and Fibre Transport 71
Adding a SAN client

Adding a SAN client

If you configure a SAN client and it does not appear as a SAN client in your
NetBackup environment, you can add the client. To do so, use the NetBackup
Device Configuration Wizard or the NetBackup Administration Console.
The SAN client must be configured correctly and the SAN client FT service must
be active.
To add a SAN client by using the wizard
1 In the NetBackup Administration Console, in the left pane, select Media
and Device Management.
2 In the right pane, click Configure Storage Devices.
3 Follow the wizard screens.
4 If the SAN client does not appear on the SAN clients screen, click Add to add
it manually.
To add a SAN client by using the Administration Console
1 In the NetBackup Administration Console, in the left pane, select Media
and Device Management > Devices > SAN Clients.
2 Click Actions > New > New SAN Client.
3 In the New SAN Client dialog box, enter the name of the client and click OK.
NetBackup queries the client and adds it to the SAN Clients list in the
Administration Console window.

Deleting a SAN client

Use the following procedure to delete a SAN client from your NetBackup
configuration. The SAN client remains a NetBackup client, but it no longer functions
as a SAN client.
To delete a SAN client
1 Disable the SAN client services.
See “Disabling a SAN client” on page 72.
2 In the NetBackup Administration Console, in the left pane, select Media
and Device Management > Devices > SAN Clients.
3 Select a client in the right pane.
4 Click Edit > Delete.
 Chapter 7
Disabling SAN Client and
Fibre Transport
This chapter includes the following topics:

■ About disabling SAN Client and Fibre Transport

■ Disabling a SAN client

■ Disabling a Fibre Transport media server

■ Disabling a Fibre Transport media server for a 16-gigabit target mode HBA
support

About disabling SAN Client and Fibre Transport

You cannot uninstall the SAN Client and Fibre Transport components. However,
you can disable the SAN clients and the FT media servers.
See “Disabling a SAN client” on page 72.
See “Disabling a Fibre Transport media server” on page 73.

Disabling a SAN client

You can disable a SAN client. If you do, the client cannot backup over the SAN to
an FT media server.
See “About disabling SAN Client and Fibre Transport” on page 72.
After you disable a SAN client, you can remove it from your NetBackup environment.
See “Deleting a SAN client” on page 71.
 Disabling SAN Client and Fibre Transport 73
Disabling a Fibre Transport media server

To disable the NetBackup SAN client service on UNIX

1 To stop the service, run the following command on the client:
/usr/openv/netbackup/bin/nbftclnt -terminate

2 To configure the host so it does not start the SAN client service after a computer
restart, run the following command:
/usr/openv/netbackup/bin/bpclntcmd -sanclient 0

To disable the NetBackup SAN client service on Windows

1 Use Windows Computer Management to stop the NetBackup SAN Client
Service.
2 To configure the host so it does not start the SAN client service after a restart,
run the following command:
install_path\NetBackup\bin\bpclntcmd.exe -sanclient 0

Disabling a Fibre Transport media server

You can disable an FT media server and remove the operating system FT startup
scripts from the media server. The process also removes the nbhba driver and exits
nbhba mode. The media server then does not support NetBackup Fibre Transport.

See “About disabling SAN Client and Fibre Transport” on page 72.

Warning: On Solaris systems, /etc/driver_aliases file entries may remain after

you remove the FT services and the nbhba driver. The entries are in the form of
qla2300 "pci1077,xxx" or qla2300 "pciex1077,xxx. The entries are harmless;
however, if you attempt to remove them, the system may not boot. Sun Microsystems
recommends that you do not edit the /etc/driver_aliases file.
 Disabling SAN Client and Fibre Transport 74
Disabling a Fibre Transport media server for a 16-gigabit target mode HBA support

To disable an FT media server and remove drivers

1 On the FT media server, run the following script:
/usr/openv/netbackup/bin/admincmd/nbftsrv_config -d

2 Verify that the following startup scripts were removed:

On Linux systems, the following are the scripts:

/etc/rc.d/rc2.d/S21nbftserver
/etc/rc.d/rc3.d/S21nbftserver
/etc/rc.d/rc5.d/S21nbftserver
/etc/rc.d/rc0.d/K03nbftserver
/etc/rc.d/rc6.d/K03nbftserver
/lib/modules/ 2.6.*smp/kernel/drivers/misc/ql2300_stub.ko
/lib/modules/ 2.6.*smp/kernel/drivers/misc/windrvr6.ko

On Solaris systems, the following are the scripts:

/etc/rc2.d/S21nbftserver
/etc/rc0.d/K03nbftserver
/usr/kernel/drv/windrvr6.conf
/usr/kernel/drv/sparcv9/windrvr6
/usr/kernel/drv/sparcv9/ql2300_stub

3 If the startup scripts were not removed, delete them manually.

4 Run the following script:
/usr/openv/netbackup/bin/admincmd/nbftconfig -ds
ft_server_host_name

Disabling a Fibre Transport media server for a

16-gigabit target mode HBA support
You can disable an FT media server and remove the operating system FT startup
scripts from the media server. The process also removes the SCST and QLogic
drivers. The media server then does not support NetBackup Fibre Transport.
See “About disabling SAN Client and Fibre Transport” on page 72.
 Disabling SAN Client and Fibre Transport 75
Disabling a Fibre Transport media server for a 16-gigabit target mode HBA support

To disable an FT media server and remove drivers

1 On the FT media server, run the following script:
/usr/openv/netbackup/bin/admincmd/nbftsrv_config -scst -uninstall

2 Verify that the following startup scripts were removed:

scripts: (/etc/rc.d/)
/etc/rc.d/init.d/nbftserver
/etc/rc.d/rc2.d/S21nbftserver
/etc/rc.d/rc3.d/S21nbftserver
/etc/rc.d/rc5.d/S21nbftserver
/etc/rc.d/rc0.d/K03nbftserver
/etc/rc.d/rc1.d/K03nbftserver
/etc/rc.d/rc6.d/K03nbftserver
drivers: (lib/modules/xxx/extra)
qla2x00tgt.ko
qla2xxx.ko
scst.ko
scst_user.ko
firmwares: (/lib/firmware)
ql2700-firmware-8.07.10.bin and ql2700_fw.bin
ql2500-firmware-8.04.00.bin and q2500_fw.bin
folders:
/var/lib/scst/vdev_mode_pages
/var/lib/scst/pr
/usr/share/doc/ql2500-firmware-8.04.00
/etc/modules-load.d/scst.conf

3 If the startup scripts were not removed, delete them manually. After you remove
the files, rename ql2500_fw_original.bin to ql2500_fw.bin.
4 Run the following script:
/usr/openv/netbackup/bin/admincmd/nbftconfig -ds
ft_server_host_name

Note: If your /boot partition does not have enough disk space, manually delete
images like
initramfs-3.10.0-514.26.2.el7.x86_64.img.10-23-17.17:22:37 to get
more disk space.
 Chapter 8
Troubleshooting SAN
Client and Fibre Transport
This chapter includes the following topics:

■ About troubleshooting SAN Client and Fibre Transport

■ SAN Client troubleshooting tech note

■ Viewing Fibre Transport logs

■ About unified logging

■ Stopping and starting Fibre Transport services

■ Stopping and starting Fibre Transport services for a 16-gigabit target mode HBA
support

■ Backups failover to LAN even though Fibre Transport devices available

■ Kernel warning messages when Veritas modules load

■ SAN client service does not start

■ SAN client Fibre Transport service validation

■ SAN client does not select Fibre Transport

■ Media server Fibre Transport device is offline

■ No Fibre Transport devices discovered

 Troubleshooting SAN Client and Fibre Transport 77
About troubleshooting SAN Client and Fibre Transport

About troubleshooting SAN Client and Fibre

Transport
SAN Client and Fibre Transport troubleshooting information is available.
See “SAN Client troubleshooting tech note” on page 77.
See “Viewing Fibre Transport logs” on page 77.
See “Stopping and starting Fibre Transport services” on page 82.
See “Backups failover to LAN even though Fibre Transport devices available ”
on page 84.
See “SAN client service does not start” on page 85.
See “SAN client Fibre Transport service validation” on page 85.
See “SAN client does not select Fibre Transport” on page 86.
See “Media server Fibre Transport device is offline” on page 87.
See “No Fibre Transport devices discovered” on page 88.

SAN Client troubleshooting tech note

More troubleshooting information about SAN clients and Fibre Transport is available
on the Veritas Enterprise Support Web site in the following Tech Note:
http://www.veritas.com/docs/TECH51454
The Tech Note contents are updated when new information is available. The Tech
Note may contain more current information than this guide.

Viewing Fibre Transport logs

You can monitor Fibre Transport activity and status by viewing the log messages
that the FT processes generate. Veritas Unified Logging (VxUL) uses a standardized
name and file format for log files. An originator ID identifies the process that writes
the log messages.
Table 8-1 shows the VxUL originator IDs of the processes that log information about
FT activity.
 Troubleshooting SAN Client and Fibre Transport 78
About unified logging

Table 8-1 Fibre Transport originator IDs

Originator ID FT processes that use the ID

199 nbftsrvr and nbfdrv64. The media server Fibre Transport services.

For a 16-gigabit target mode HBA support only nbftsrvr is supported.

The media server Fibre Transport services.
Note: You can use only one of the two methods.

200 nbftclnt. The client Fibre Transport service.

201 The FT Service Manager. Runs in the Enterprise Media Manager

service.

To view and manage VxUL log files, you must use NetBackup log commands.
See “About unified logging” on page 78.
Configure the amount of information that is collected and its retention length on the
NetBackup master server in the Logging properties and Clean-up properties.
Information about how to configure logging and clean-up properties is available in
the NetBackup Administrator’s Guide, Volume I:
http://www.veritas.com/docs/DOC5332

About unified logging

Unified logging creates log file names and messages in a format that is standardized
across Veritas products. Only the vxlogview command can assemble and display
the log information correctly. Server processes and client processes use unified
logging.
Log files for originator IDs are written to a subdirectory with the name specified in
the log configuration file. All unified logs are written to subdirectories in the following
directory:

Windows install_path\NetBackup\logs

UNIX /usr/openv/logs

You can access logging controls in Logging host properties. You can also manage
unified logging with the following commands:

vxlogcfg Modifies the unified logging configuration settings.

 Troubleshooting SAN Client and Fibre Transport 79
About unified logging

vxlogmgr Manages the log files that the products that support unified logging
generate.

vxlogview Displays the logs that unified logging generates.

See “Examples of using vxlogview to view unified logs” on page 81.

About using the vxlogview command to view unified logs

Only the vxlogview command can assemble and display the unified logging
information correctly. The unified logging files are in binary format and some of the
information is contained in an associated resource file. These logs are stored in
the following directory. You can display vxlogview results faster by restricting the
search to the files of a specific process.

UNIX /usr/openv/logs

Windows install_path\NetBackup\logs

Table 8-2 Fields in vxlogview query strings

Field name Type Description Example

PRODID Integer or string Provide the product ID or the PRODID = 51216

abbreviated name of product.
PRODID = 'NBU'

ORGID Integer or string Provide the originator ID or the ORGID = 116

abbreviated name of the component.
ORGID = 'nbpem'

PID Long Integer Provide the process ID PID = 1234567

TID Long Integer Provide the thread ID TID = 2874950

STDATE Long Integer or string Provide the start date in seconds or STDATE = 98736352
in the locale-specific short date and
STDATE = '4/26/11 11:01:00
time format. For example, a locale
AM'
can have the format 'mm/dd/yy
hh:mm:ss AM/PM'

ENDATE Long Integer or string Provide the end date in seconds or ENDATE = 99736352
in the locale-specific short date and
ENDATE = '04/27/11 10:01:00
time format. For example, a locale
AM'
can have the format 'mm/dd/yy
hh:mm:ss AM/PM'
 Troubleshooting SAN Client and Fibre Transport 80
About unified logging

Table 8-2 Fields in vxlogview query strings (continued)

Field name Type Description Example

PREVTIME String Provide the hours in 'hh:mm:ss' PREVTIME = '2:34:00'

format. This field should be used
only with operators =, <, >, >=, and
<=

SEV Integer Provide one of the following possible SEV = 0

severity types:
SEV = INFO
0 = INFO

1 = WARNING

2 = ERR

3 = CRIT

4 = EMERG

MSGTYPE Integer Provide one of the following possible MSGTYPE = 1

message types:
MSGTYPE = DIAG
0 = DEBUG (debug messages)

1 = DIAG (diagnostic messages)

2 = APP (application messages)

3 = CTX (context messages)

4 = AUDIT (audit messages)

CTX Integer or string Provide the context token as string CTX = 78

identifier or 'ALL' to get all the
CTX = 'ALL'
context instances to be displayed.
This field should be used only with
the operators = and !=.

Table 8-3 Examples of query strings with dates

Example Description

(PRODID == 51216) && ((PID == 178964)|| ((STDATE == Retrieves the log file message for the
'2/5/15 09:00:00 AM') && (ENDATE == '2/5/15 NetBackup product ID 51216 between
12:00:00 PM')) 9AM and 12PM on 2015-05-02.
 Troubleshooting SAN Client and Fibre Transport 81
About unified logging

Table 8-3 Examples of query strings with dates (continued)

Example Description

((prodid = 'NBU') && ((stdate >= ‘11/18/14 Retrieves the log messages for the
00:00:00 AM’) && (endate <= ‘12/13/14 12:00:00 PM’))) || NetBackup product NBU between
((prodid = 'BENT') && ((stdate >= ‘12/12/14 00:00:00 2014-18-11 and 2014-13-12 and the log
AM’) && (endate <= ‘12/25/14 12:00:00 PM’))) messages for the NetBackup product
BENT between 2014-12-12 and
2014-25-12.

(STDATE <= ‘04/05/15 0:0:0 AM’) Retrieves the log messages that were
logged on or before 2015-05-04 for all
of the installed Veritas products.

Examples of using vxlogview to view unified logs

The following examples demonstrate how to use the vxlogview command to view
unified logs.

Table 8-4 Example uses of the vxlogview command

Item Example

Display all the vxlogview -p 51216 -d all

attributes of the log
messages

Display specific Display the log messages for NetBackup (51216) that show only the date, time, message
attributes of the log type, and message text:
messages
vxlogview --prodid 51216 --display D,T,m,x

Display the latest log Display the log messages for originator 116 (nbpem) that were issued during the last 20
messages minutes. Note that you can specify -o nbpem instead of -o 116:

# vxlogview -o 116 -t 00:20:00

Display the log Display the log messages for nbpem that were issued during the specified time period:
messages from a
specific time period # vxlogview -o nbpem -b "05/03/15 06:51:48 AM"
-e "05/03/15 06:52:48 AM"
 Troubleshooting SAN Client and Fibre Transport 82
Stopping and starting Fibre Transport services

Table 8-4 Example uses of the vxlogview command (continued)

Item Example

Display results faster You can use the -i option to specify an originator for a process:

# vxlogview -i nbpem

The vxlogview -i option searches only the log files that the specified process (nbpem)
creates. By limiting the log files that it has to search, vxlogview returns a result faster. By
comparison, the vxlogview -o option searches all unified log files for the messages that
the specified process has logged.
Note: If you use the -i option with a process that is not a service, vxlogview returns the
message "No log files found." A process that is not a service has no originator ID in the file
name. In this case, use the -o option instead of the -i option.

The -i option displays entries for all OIDs that are part of that process including libraries (137,
156, 309, etc.).

Search for a job ID You can search the logs for a particular job ID:

# vxlogview -i nbpem | grep "jobid=job_ID"

The jobid= search key should contain no spaces and must be lowercase.

When searching for a job ID, you can use any vxlogview command option. This example
uses the -i option with the name of the process (nbpem). The command returns only the
log entries that contain the job ID. It misses related entries for the job that do not explicitly
contain the jobid=job_ID.

Stopping and starting Fibre Transport services

Fibre Transport services run on both the FT media servers and SAN clients.
The following are the FT services that run on media servers:
■ The nbftsrvr service manages the server side of the FT pipe.
■ The nbfdrv64 service controls the target mode drivers on the media server.
The nbftsrvr service starts the nbfdrv64 service. If you stop one, the other stops.
If one ends abnormally, the other stops.
The nbftclnt FT service runs on SAN clients:
These services do not appear in the NetBackup Activity Monitor; they do appear in
the operating system process displays.
 Troubleshooting SAN Client and Fibre Transport 83
Stopping and starting Fibre Transport services for a 16-gigabit target mode HBA support

In normal operation, you should not have to start or stop the services. A Veritas
support engineer may direct you to stop and restart services for troubleshooting
purposes.
See “Enabling or disabling the Fibre Transport services” on page 67.
Alternatively, you can use the UNIX kill command without the -9 option to stop
the services. The NetBackup bp.kill_all command stops the FT services, but it
stops all other NetBackup services also.

Warning: Do not use the UNIX kill -9 command and option to stop the nbfdrv64
process. It does not allow the process to stop gracefully, and the SAN clients cannot
detect the FT devices when the nbfdrv64 process dies. You then may have to reboot
the client systems so they detect the FT devices again (after you restart nbfdrv64).

The NetBackup bp.start_all command starts all NetBackup services, including

the FT services.

Stopping and starting Fibre Transport services

for a 16-gigabit target mode HBA support
Fibre Transport services run on both the FT media servers and SAN clients.
The following are the FT services that run on media servers:
■ The nbftsrvr service manages the server side of the FT pipe.
The nbftclnt FT service runs on SAN clients:
These services do not appear in the NetBackup Activity Monitor; they do appear in
the operating system process displays.
In normal operation, you should not have to start or stop the services. A Veritas
support engineer may direct you to stop and restart services for troubleshooting
purposes.
See “Enabling or disabling the Fibre Transport services” on page 67.
Alternatively, you can use the UNIX kill command without the -9 option to stop
the services. The NetBackup bp.kill_all command stops the FT services, but it
stops all other NetBackup services also.
The NetBackup bp.start_all command starts all NetBackup services, including
the FT services.
 Troubleshooting SAN Client and Fibre Transport 84
Backups failover to LAN even though Fibre Transport devices available

Backups failover to LAN even though Fibre

Transport devices available
If a NetBackup FT media server has multiple network interfaces for VLANs, backups
may failover to LAN transport if the NetBackup host name order is configured
incorrectly.
See “About Fibre Transport media servers and VLANs” on page 36.
For all of the hosts that participate in the backups, examine their Additional Servers
lists on their NetBackup Administration Console host properties Servers pages.
Verify that the FT server’s primary host name appears before any other interface
names for that FT media server host in. If it does not, fix the incorrect host name
order as described in the following table.

Table 8-5 How to fix an incorrect host name order in NetBackup

Task Procedure

Stop the FT services on the media See “Enabling or disabling the Fibre Transport
server services” on page 67.

Delete the FT server from the Use the following NetBackup command to delete the
NetBackup EMM database host from the NetBackup EMM database as an FT
media server:

nbftconfig -deleteserver -Me hostname

The host remains in the EMM database as a

NetBackup media server.

Re-order the Additional Servers list If necessary, delete all of the network interface names
on each host of the FT media server from the Additional Servers
list. Then, add the primary host name first and then
the remainder of the host names in any order. The
Additional Servers list appears in the host properties
Servers page for that host.

See the NetBackup Administrator's Guide, Volume I:

http://www.veritas.com/docs/DOC5332

Start the FT services on the media See “Enabling or disabling the Fibre Transport
server services” on page 67.
 Troubleshooting SAN Client and Fibre Transport 85
Kernel warning messages when Veritas modules load

Table 8-5 How to fix an incorrect host name order in NetBackup (continued)

Task Procedure

Scan for FT devices from each SAN When the FT media server is discovered during the
client rescan operation, NetBackup adds it to the EMM
database as an FT media server.

See “Rescanning for Fibre Transport devices from a

SAN client” on page 68.

Kernel warning messages when Veritas modules

load
For Linux operating systems, warning messages similar to the following may appear
in the console or the system log when Veritas modules are loaded into the kernel:

kernel: ql2300_stub: module license 'Proprietary. Send bug

reports to [email protected]' taints kernel.
kernel: ql2300_stub: Version: XXn
kernel: ql2300_stub: $Revision: n.nn

The messages appear because the Veritas modules are proprietary. You can ignore
them.

SAN client service does not start

The nbftclnt service is the SAN Client service that runs on clients, If it does not
start on UNIX or Linux systems, one possible cause may be the NetBackup
configuration file. The following is the pathname of the file:
/usr/openv/netbackup/bp.conf

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.
 Troubleshooting SAN Client and Fibre Transport 86
SAN client does not select Fibre Transport

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 77.
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.

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.
 Troubleshooting SAN Client and Fibre Transport 87
Media server Fibre Transport device is offline

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

If NetBackup shows that a media server FT device is offline, the selected SAN client
cannot detect the target mode driver on that media server. FT device status appears
in the Media and Device Management > Devices > SAN Clients window of the
NetBackup Administration Console. (An FT device represents the HBA target mode
driver on a media server.)
An FT device may be offline because of the following:
■ The nbfdrv64 service on a media server is down. The nbfdrv64 service manages
the target mode drivers; if it is down, the FT device is not available.
■ The physical connections between the SAN client and the SAN switch fail or
were changed.
■ SAN zoning changes removed either the media server or the SAN client from
the zone.
■ The SAN client failed the FT service validation.
See “SAN client Fibre Transport service validation” on page 85.
If all media server FT devices for a client are offline, troubleshoot in the following
order:
■ Verify that the SAN client FT service validation passes.
■ Verify that the physical connections from the SAN client to the SAN switch are
correct.
■ Verify that the SAN zones are correct.
■ Verify that the nbfdrv64 service is active on each media server.
 Troubleshooting SAN Client and Fibre Transport 88
No Fibre Transport devices discovered

To determine if the nbfdrv64 service is down, use the operating system process
status command to examine the processes on the media server. Both nbftsrvr
and nbfdrv64 should be active.
See “Stopping and starting Fibre Transport services” on page 82.
If the services do not start, examine the log files for those services to determine
why they do not start.
See “Viewing Fibre Transport logs” on page 77.

No Fibre Transport devices discovered

If a "No FT devices discovered" message appears in the NetBackup logs on the
SAN client, the pass-through driver may not be configured on the SAN client.
For information about how to configure pass-through drivers, see the NetBackup
Device Configuration Guide, available at the following URL:
http://www.veritas.com/docs/DOC5332
 Appendix A
AIX Specific Configuration
Details
This appendix includes the following topics:

■ AIX Reference Information

■ Before you begin configuring NetBackup on AIX

■ About AIX persistent naming support

■ About configuring robotic control device files in AIX

■ About device files for SAN Clients on AIX

■ About configuring tape drive device files in AIX

AIX Reference Information

The following information is specific to AIX. Certain devices, such as tape or robotic
devices, have specific AIX configuration requirements. This AIX reference section
contains relevant information.

Before you begin configuring NetBackup on AIX

Observe the following points when you configure the operating system:
■ Verify that NetBackup supports your server platform and devices. Download
the NetBackup hardware and operating system compatibility lists.
http://www.netbackup.com/compatibility
■ Install and configure the IBM AIX Enhanced Device Driver (Atape device driver).
 AIX Specific Configuration Details 90
About AIX persistent naming support

■ Attach all peripherals and reboot the system before you configure the devices
in NetBackup. When the computer is rebooted, AIX creates the device files for
the attached peripherals.
■ For many configuration steps, you can use the smit System Management
Interface Tool. For more information, see the smit(1) man page.
■ To verify that the devices are configured correctly, use smit and
/usr/sbin/lsdev command.

■ To obtain error and debug information about devices and robotic software
daemons, the syslogd daemon must be active. See the AIX syslogd(1) man
page for more information.
After you configure the hardware, add the robots and the drives to NetBackup.

About AIX persistent naming support

NetBackup requires that you enable persistent naming support for the AIX device
files. Doing so ensures that the device targets and LUNs do not change after a
system restart.
To enable persistent naming support, use the AIX SMIT utility or the chdev command
to change the logical names of the devices. Change the logical names after the
initial device configuration in AIX. For more information, see the IBM documentation.

About configuring robotic control device files in

AIX
For IBM robotic libraries, Veritas supports the IBM AIX Enhanced Device Driver
(Atape device driver) for use with NetBackup. NetBackup discovers the device files
when you configure devices.
For information about the driver and how to configure device files, see the IBM
documentation.
For robotic libraries other than IBM, Veritas recommends that you use an operating
system other than AIX as the robotic control host.

About device files for SAN Clients on AIX

NetBackup SAN clients use tape drivers and SCSI pass-through methods for Fibre
Transport traffic to NetBackup FT media servers. An AIX SAN Client that uses the
standard tape driver can discover Fibre Transport targets on the FT media servers.
 AIX Specific Configuration Details 91
About configuring tape drive device files in AIX

The media server FT devices appear as ARCHIVE Python tape devices during SCSI
inquiry from the SAN client. However, they are not tape devices and do not appear
as tape devices in NetBackup device discovery.
During system startup, the AIX cfgmgr command configures all the devices that
are necessary to use the system. If a NetBackup SAN Client cannot discover the
FT devices, you can configure the device files on the client manually. Use the same
procedure that you use for tape devices.

About configuring tape drive device files in AIX

About non-QIC tape drives on AIX
Variable length block and fixed length block refer to how the operating system reads
from and writes to a tape. Variable-mode devices allow more flexibility to read
previously written tapes. Many tape devices can be accessed in either mode.
NetBackup assumes variable length for non-quarter inch cartridge (QIC) drives.
For more information, see the chdev(1) and smit(1) man pages and the system
management guide. The smit application is the most convenient way to change
from fixed to variable-length-block devices manually.

Warning: For NetBackup, you must configure non-QIC tape drives as

variable-length-block devices. Otherwise NetBackup can write data but may not be
able to read it correctly. During a read, you may see a not in tar format error.

When you add a non-QIC tape drive to NetBackup, NetBackup issues the chdev
command to configure the drive as a variable length block device. For reference,
the following is the command that NetBackup uses to configure a drive for variable
mode:

/usr/sbin/chdev -l Dev -a block_size=0

Dev represents the logical identifier for the drive (for example: rmt0 or rmt1).
Therefore, you do not have to configure the drive manually for variable mode.

About no rewind device files on AIX

By default, NetBackup uses no rewind device files. These SCSI device files are in
the /dev directory and have the following format:

/dev/rmtID.1
 AIX Specific Configuration Details 92
About configuring tape drive device files in AIX

ID is the logical identifier assigned to the device by the system. The .1 extension
specifies the no rewind, no retension on open device file.
Normally, AIX creates tape drive device files automatically at boot time. Alternatively,
you can run the AIX cfgmgr command, which should create the device files. If they
do not exist, you must create them for the tape drives.

Creating AIX no rewind device files for tape drives

NetBackup uses no rewind device files for tape drives and for NetBackup SAN
Clients. During system startup, the AIX cfgmgr command configures all the devices
that are necessary to use the system. If necessary, you can use the following
procedure to check for and create a no rewind device file.
To check for and create a no rewind device file
1 Display the I/O controllers in the system by using the following command:

/usr/sbin/lsdev -C | grep I/O

The following sample output shows that SCSI controller 1 (00-01) has been
assigned the logical identifier scsi0.

scsi0 Available 00-01 SCSI I/O Controller

2 Display the SCSI and Fibre Channel devices in the system by using the
following command. For SCSI devices, use scsi for the type; for Fibre Channel
Protocol devices, use fcp for the type.

/usr/sbin/lsdev -C -s type

The following example shows two disk drives and a tape drive:

hdisk0 Available 00-01-00-0,0 400 MB SCSI Disk Drive

hdisk1 Available 00-01-00-1,0 400 MB SCSI Disk Drive
rmt0 Available 00-01-00-3,0 Other SCSI Tape Drive

If the device files for the tape drives exist, they appear in the output as rmt0,
rmt1, and so on. The previous example output shows rmt0.
3 If a device file does not exist for the wanted tape drive, create it by using the
following command:

/usr/sbin/mkdev -c tape -s scsi -t ost -p controller -w id,lun

The following are the arguments for the command:

■ controller is the logical identifier of the drive’s SCSI adapter, such as scsi0,
fscsi0, or vscsi1.
 AIX Specific Configuration Details 93
About configuring tape drive device files in AIX

■ scsi_id is the SCSI ID of the drive connection.

■ lun is the logical unit number of the drive connection.
For example, the following command creates a device file for a non-IBM 8-mm
drive connected to controller scsi0 at SCSI address 5,0:

mkdev -c tape -s scsi -t ost -p scsi0 -w 5,0

4 To verify, display the SCSI device files by using the lsdev command, as follows:

/usr/sbin/lsdev -C -s scsi
hdisk0 Available 00-01-00-0,0 400 MB SCSI Disk Drive
hdisk1 Available 00-01-00-1,0 400 MB SCSI Disk Drive
rmt0 Available 00-01-00-3,0 Other SCSI Tape Drive
rmt1 Available 00-01-00-5,0 Other SCSI Tape Drive

The output shows that the rmt1 device file was created.
5 If the device files do not exist on an FCP controller, use the following command
to create them:

/usr/sbin/cfgmgr -l device

device is the controller number from step 1.

6 Ensure that the device is configured for variable-mode and extended file marks.
Use the chdev command, as follows (dev is the logical identifier for the drive
(for example, rmt1)).

/usr/sbin/chdev -l dev -a block_size=0

/usr/sbin/chdev -l dev -a extfm=yes

7 To configure the drive manually in NetBackup, enter the following device file
pathname:

/dev/rmt1.1

Example of creating a no rewind device file

This topic provides an example of how to create a no rewind device file on AIX for
NetBackup. Assume the device files for the wanted SCSI 8-mm tape drive (controller
1, SCSI ID 5) do not exist.
 AIX Specific Configuration Details 94
About configuring tape drive device files in AIX

To create a no rewind device file for SCSI ID 5

1 Determine the logical identifier for the SCSI controller as follows:

/usr/sbin/lsdev -C -c adapter | grep SCSI

The following output shows that scsi0 is the logical name for SCSI controller
1:

scsi0 Available 00-01 SCSI I/O Controller

2 Determine if the device files exist for any device at SCSI ID 5.

/usr/sbin/lsdev -C -s scsi

The following output shows that some device files exist for tape and disk.
However, a device files does not exist for the 8-mm tape drive at controller 1
(scsi0) and SCSI ID 5 (5,0):

hdisk0 Available 00-01-00-0,0 400 MB SCSI Disk Drive

hdisk1 Available 00-01-00-1,0 400 MB SCSI Disk Drive
rmt0 Available 00-01-00-3,0 Other SCSI Tape Drive

3 Create the device file by using the following command:

mkdev -c tape -t ost -s scsi -p scsi0 -w 5,0

4 Display the device files by issuing the following command:

/usr/sbin/lsdev -C -s scsi
hdisk0 Available 00-01-00-0,0 400 MB SCSI Disk Drive
hdisk1 Available 00-01-00-1,0 400 MB SCSI Disk Drive
rmt0 Available 00-01-00-3,0 Other SCSI Tape Drive
rmt1 Available 00-01-00-5,0 Other SCSI Tape Drive

5 To ensure that the tape device is configured for variable-mode and extended
file marks, use the following commands:

chdev -l rmt1 -a block_size=0

chdev -l rmt1 -a extfm=yes

6 To configure the drive manually in NetBackup, enter the following device file
pathname:

/dev/rmt1.1
 Appendix B
HP-UX Specific
Configuration Details
This appendix includes the following topics:

■ HP-UX Reference Information

■ Before you begin configuring NetBackup on HP-UX

■ About HP-UX device drivers for legacy device files

■ About legacy robotic control device files

■ About legacy tape drive device files

■ About legacy pass-through paths for tape drives

■ Creating device files for SAN Clients on HP-UX

■ About configuring legacy device files

HP-UX Reference Information

The following information is specific to HP-UX. Certain devices, such as tape or
robotic devices, have specific HP-UX configuration requirements. This HP-UX
reference section contains relevant information.

Before you begin configuring NetBackup on

HP-UX
Observe the following points when you configure the operating system:
 HP-UX Specific Configuration Details 96
About HP-UX device drivers for legacy device files

■ To verify that the devices are configured correctly, use the HP-UX sam utility
and the ioscan -f command.

About HP-UX device drivers for legacy device files

The following are the drivers supported:
■ The sctl driver for robotic control.

About legacy robotic control device files

For SCSI robotic control, NetBackup can use the /dev/sctl device files. The device
file names have the following format:
/dev/sctl/cCARDtTARGETlLUN c Major 0xIITL00

Where:
■ CARD is the card instance number of the adapter.

■ TARGET is the SCSI ID of the robotic control.

■ LUN is the SCSI logical unit number (LUN) of the robot.

■ Major is the character major number (from the lsdev command).

■ II are two hexadecimal digits that represent the card instance number.

■ T is a hexadecimal digit that represents the SCSI ID of robotic control.

■ L is a hexadecimal digit that represents the SCSI LUN of the robotic control.

A library may have more than one robotic device. Each robotic device requires a
device file.

About legacy tape drive device files

NetBackup requires the /dev/rmt device files to configure tape drives.
The device file names have the following format:
/dev/rmt/c#t#d#BESTnb

The following describe the device file names:

■ c# is the card instance number.

■ t# is the SCSI ID.

■ d# is the device LUN.

 HP-UX Specific Configuration Details 97
About legacy pass-through paths for tape drives

■ BEST indicates the highest density format and data compression the device
supports.
■ n indicates no rewind on close.

■ b indicates Berkeley-style close.

The following are examples of tape drive device files:

/dev/rmt/c7t0d0BESTnb
/dev/rmt/c7t1d0BESTnb
/dev/rmt/c7t4d0BESTnb
/dev/rmt/c7t5d0BESTnb

About legacy pass-through paths for tape drives

Although NetBackup requires the /dev/rmt device files to configure tape drives,
NetBackup uses pass-through device files for drive access.
On media servers, NetBackup automatically creates pass-through device files if
the appropriate/dev/rmt tape drive device files exist. NetBackup creates the
pass-through device files in the /dev/sctl directory.
NetBackup does not modify or delete any existing pass-through paths.
NetBackup does not detect the type of adapter cards that are installed in the system.
Therefore, NetBackup creates pass-through paths for tape drives connected to the
adapter cards that do not support pass through. These pass-through paths do not
cause problems.
Although NetBackup uses the pass-through device files during tape drive operations,
you specify the /dev/rmt device files when you configure the drives in NetBackup.
NetBackup then uses the appropriate pass-through device files.
Usually, you do not have to create pass-through paths for drives. However,
instructions to do so are provided for reference.
NetBackup SAN clients require legacy pass-through device files.

Note: Pass-through paths are not supported on HP-PB adapters such asHP28696A
- Wide SCSI or HP 28655A - SE SCSI.
 HP-UX Specific Configuration Details 98
Creating device files for SAN Clients on HP-UX

Creating device files for SAN Clients on HP-UX

NetBackup SAN clients use tape drivers and SCSI pass-through methods for Fibre
Transport traffic to NetBackup FT media servers. On HP-UX systems, NetBackup
SAN clients require the sctl driver and pass-through tape drive device files.
The following table describes the tasks that create the device files. Before you
create the device files, the NetBackup FT media server must be active and the SAN
must be zoned correctly.

Table B-1 SAN Client device file tasks

Step Action Description

Step 1 If the sctl driver is not the default See the HP-UX scsi_ctl(7) man
pass-through driver on your system, page.
install and configure the sctl driver.

Step 2 Create the pass-through paths required.

The media server FT devices appear as ARCHIVE Python tape devices during SCSI
inquiry from the SAN client. However, they are not tape devices and do not appear
as tape devices in NetBackup device discovery.
You can use legacy device files for SAN client pass-through paths for Fibre Transport
traffic to NetBackup media servers.

About configuring legacy device files

You can use legacy device files for the following:
■ Robotic control using SCSI or Fibre Channel Protocol control.
SCSI control includes Fibre Channel Protocol (FCP), which is SCSI over Fibre
Channel. A robotic device in a library moves the media between storage slots
and the drives in the library.
See “Creating legacy SCSI and FCP robotic controls on HP-UX” on page 99.
■ Tape drive read and write access.
See “About creating legacy tape drive device files” on page 106.
See “Creating tape drive pass-through device files” on page 106.
■ SAN client pass-through paths for Fibre Transport traffic to NetBackup media
servers.
 HP-UX Specific Configuration Details 99
About configuring legacy device files

Creating legacy SCSI and FCP robotic controls on HP-UX

You must create the robotic control device files for the sctl driver manually; they
are not created automatically when the system boots.
Before you create the device files, you must do the following:
■ Install and configure the sctl driver. For more information, see the HP-UX
scsi_ctl(7) man page.
The sctl driver may be the default pass-through driver on your system. If so,
you do not have to configure the kernel to use the sctl pass-through driver.
■ Install and configure the schgr device driver. For more information, see the
HP-UX autochanger(7) man page.
■ Attach the devices.
Examples of how to create the device files are available.
See “Example of how to create a sctl device file for SCSI (PA-RISC)” on page 100.
See “Example of how to create a sctl device file for FCP (PA-RISC)” on page 102.
See “Example of how to create sctl device files for FCP (Itanium)” on page 104.
To create sctl device files
1 Invoke the ioscan -f command to obtain SCSI bus and robotic control
information.
2 Examine the output for the card instance number and the SCSI ID and LUN
of the robotic device, as follows:
■ The instance number of the card is in the I column of the output.
■ The H/W Path column of the changer output (schgr) includes the SCSI ID
and LUN. Use the card's H/W Path value to filter the changer's H/W Path
entry; the SCSI ID and the LUN remain.

3 Determine the character major number of the sctl driver by using the following
command:

lsdev -d sctl

Examine the output for an entry that shows sctl in the Driver column.
4 Use the following commands to create the device file for the SCSI robotic
control:

mkdir /dev/sctl
cd /dev/sctl
/usr/sbin/mknod cCARDtTARGETlLUN c Major 0xIITL00
 HP-UX Specific Configuration Details 100
About configuring legacy device files

Where:
■ CARD is the card instance number of the adapter.

■ TARGET is the SCSI ID of the robotic control.

■ LUN is the SCSI logical unit number (LUN) of the robot.

■ Major is the character major number (from the lsdev command).

■ II are two hexadecimal digits that represent the card instance number.

■ T is a hexadecimal digit that represents the SCSI ID of robotic control.

■ L is a hexadecimal digit that represents the SCSI LUN of the robotic control.

Example of how to create a sctl device file for SCSI

(PA-RISC)
In this example, the following robots exist:
■ An ADIC Scalar 100 library is on a SCSI bus with an instance number of 7, SCSI
ID 2, and LUN 0.
■ The robotic control for an IBM ULT3583-TL library is on the same SCSI bus at
SCSI ID 3 and LUN 0.
 HP-UX Specific Configuration Details 101
About configuring legacy device files

To create SCSI robotic device files for HP-UX PA-RISC

1 Invoke the ioscan -f command, as follows:

ioscan -f
Class I H/W Path Driver S/W State H/W Type Description
=================================================================
ext_bus 7 0/7/0/1 c720 CLAIMED INTERFACE SCSI C896 Fast Wide LVD
target 10 0/7/0/1.0 tgt CLAIMED DEVICE
tape 65 0/7/0/1.0.0 stape CLAIMED DEVICE QUANTUM SuperDLT1
target 11 0/7/0/1.1 tgt CLAIMED DEVICE
tape 66 0/7/0/1.1.0 stape CLAIMED DEVICE QUANTUM SuperDLT1
target 12 0/7/0/1.2 tgt CLAIMED DEVICE
autoch 14 0/7/0/1.2.0 schgr CLAIMED DEVICE ADIC Scalar 100
target 13 0/7/0/1.3 tgt CLAIMED DEVICE
autoch 19 0/7/0/1.3.0 schgr CLAIMED DEVICE IBM ULT3583-TL
target 14 0/7/0/1.4 tgt CLAIMED DEVICE
tape 21 0/7/0/1.4.0 atdd CLAIMED DEVICE IBM ULT3580-TD1
target 15 0/7/0/1.5 tgt CLAIMED DEVICE
tape 19 0/7/0/1.5.0 atdd CLAIMED DEVICE IBM ULT3580-TD1

2 Examine the output for the card instance number and the SCSI ID and LUN
of the robotic device, as follows:
The card H/W Path is 0/7/0/1; the card instance number (I column) is 7. Apply
the H/W Path value as a mask. The ADIC robotic device (schgr) is at SCSI ID
2, LUN 0 on this bus. The IBM robotic device (schgr) is at SCSI ID 3, LUN 0
on this bus.
 HP-UX Specific Configuration Details 102
About configuring legacy device files

3 Determine the character major number of the sctl driver by using the following
command:

lsdev -d sctl
Character Block Driver Class
203 -1 sctl ctl

The output from this command shows that the character major number for the
sctl driver is 203.

4 The commands to create the device files follow. For the ADIC robot, the card
instance number is 7, the target is 2, and the LUN is 0. For the IBM robot, the
card instance number is 7, the SCSI ID is 3, and the LUN is 0.

cd /dev/sctl
/usr/sbin/mknod c7t2l0 c 203 0x072000
/usr/sbin/mknod c7t3l0 c 203 0x073000

If you add the robots to NetBackup manually, you specify the following for ADIC
robotic control and IBM robotic control respectively:

/dev/sctl/c7t2l0
/dev/sctl/c7t3l0

Example of how to create a sctl device file for FCP

(PA-RISC)
The following example shows how create a sctl device file for an HP VLS9000 robot.
NetBackup uses the device file for robotic control.
 HP-UX Specific Configuration Details 103
About configuring legacy device files

To create an FCP robotic device file for HP-UX PA-RISC

1 Invoke the ioscan -f command. The following output example is edited for
readability:

ioscan -f
Class I H/W Path Driver S/W State H/W Type Description
=============================================================================
fc 0 0/2/0/0 td CLAIMED INTERFACE HP Tachyon XL2 Fibre
Channel Mass Storage
Adapter
fcp 4 0/2/0/0.10 fcp CLAIMED INTERFACE FCP Domain
ext_bus 6 0/2/0/0.10.11.255.0 fcpdev CLAIMED INTERFACE FCP Device Interface
target 5 0/2/0/0.10.11.255.0.0 tgt CLAIMED DEVICE
autoch 2 0/2/0/0.10.11.255.0.0.0 schgr CLAIMED DEVICE HP VLS
tape 5 0/2/0/0.10.11.255.0.0.1 stape CLAIMED DEVICE HP Ultrium 4-SCSI
tape 6 0/2/0/0.10.11.255.0.0.2 stape CLAIMED DEVICE HP Ultrium 4-SCSI
tape 7 0/2/0/0.10.11.255.0.0.3 stape CLAIMED DEVICE HP Ultrium 4-SCSI

2 Examine the output for the card instance number and the SCSI ID and LUN
of the robotic device. In this example, the interface card instance number (the
I column) is 6. If you use the card's H/W Path value as a mask
(0/2/0/0.10.11.255.0), you see the following:
■ An HP VLS9000 robot is at SCSI ID 0, LUN 0.
■ Three Ultrium 4-SCSI drives are at SCSI ID 0 and LUN 1, LUN 2, and LUN
3.
 HP-UX Specific Configuration Details 104
About configuring legacy device files

3 Determine the character major number of the sctl driver by using the lsdev
command, as follows:

lsdev -d sctl
Character Block Driver Class
203 -1 sctl ctl

The output from this command shows that the character major number for the
sctl driver is 203.

4 The commands to create the device file for the HP VLS9000 robotic control
are as follows. The card instance number is 6, the target is 0, and the LUN is
0.

cd /dev/sctl
/usr/sbin/mknod c6t0l0 c 203 0x060000

If you add the robot to NetBackup manually, specify the following pathname
for robotic control:

/dev/sctl/c6t0l0

Example of how to create sctl device files for FCP (Itanium)

With Fibre Channel, the hardware paths are longer than with SCSI.
In this example, the following devices are attached to the host.
■ An HP EML E-Series robot with four HP drives (two LTO2 and two LTO3 drives).
A separate path exists for each drive pair. The robotic control is through card
instance 12 (0/4/1/1.2.12.255.0).
■ An HP VLS 6000 robot with six drives. The robot is partitioned into two virtual
libraries, three Quantum SDLT320 drives in one library and three HP LTO3
drives in the other library. Separate robotic control exists for each library.
 HP-UX Specific Configuration Details 105
About configuring legacy device files

To create FCP robotic device files for HP-UX Itanium

1 Invoke the ioscan -f command. The following is a command output excerpt
that shows the Fibre Channel devices on a host:

ext_bus 4 0/4/1/1.2.10.255.0 fcd_vbus CLAIMED INTERFACE FCP Device Interface

target 7 0/4/1/1.2.10.255.0.0 tgt CLAIMED DEVICE
tape 18 0/4/1/1.2.10.255.0.0.0 stape CLAIMED DEVICE HP Ultrium 3-SCSI
tape 20 0/4/1/1.2.10.255.0.0.1 stape CLAIMED DEVICE HP Ultrium 3-SCSI
ext_bus 13 0/4/1/1.2.11.255.0 fcd_vbus CLAIMED INTERFACE FCP Device Interface
target 8 0/4/1/1.2.11.255.0.0 tgt CLAIMED DEVICE
autoch 4 0/4/1/1.2.11.255.0.0.0 schgr CLAIMED DEVICE HP VLS
tape 22 0/4/1/1.2.11.255.0.0.1 stape CLAIMED DEVICE QUANTUM SDLT320
tape 23 0/4/1/1.2.11.255.0.0.2 stape CLAIMED DEVICE QUANTUM SDLT320
tape 24 0/4/1/1.2.11.255.0.0.3 stape CLAIMED DEVICE QUANTUM SDLT320
autoch 5 0/4/1/1.2.11.255.0.0.4 schgr CLAIMED DEVICE HP VLS
tape 25 0/4/1/1.2.11.255.0.0.5 stape CLAIMED DEVICE HP Ultrium 3-SCSI
tape 26 0/4/1/1.2.11.255.0.0.6 stape CLAIMED DEVICE HP Ultrium 3-SCSI
tape 27 0/4/1/1.2.11.255.0.0.7 stape CLAIMED DEVICE HP Ultrium 3-SCSI
ext_bus 12 0/4/1/1.2.12.255.0 fcd_vbus CLAIMED INTERFACE FCP Device Interface
target 6 0/4/1/1.2.12.255.0.0 tgt CLAIMED DEVICE
autoch 1 0/4/1/1.2.12.255.0.0.0 schgr CLAIMED DEVICE HP EML E-Series
tape 19 0/4/1/1.2.12.255.0.0.1 stape CLAIMED DEVICE HP Ultrium 2-SCSI
tape 21 0/4/1/1.2.12.255.0.0.2 stape CLAIMED DEVICE HP Ultrium 2-SCSI

2 Examine the output for the card instance number and the SCSI ID and LUN
of the robotic device.
In this example, the following devices are attached to this host:
■ The robotic control for the HP EML E-Series robot is through card instance
12 (0/4/1/1.2.12.255.0). Two of the drives are accessed through the same
path, and the other two are accessed through card instance 4
(0/4/1/1.2.10.255.0).
■ The robotic controls for the HP VLS 6000 robot partitions are through card
instance 13. Robotic control for one partition is at SCSI ID 0 and LUN 0.
Robotic control for the other partition is at SCSI ID 0 and LUN 4.
 HP-UX Specific Configuration Details 106
About configuring legacy device files

3 Determine the character major number of the sctl driver by using the following
command:

lsdev -d sctl
Character Block Driver Class
203 -1 sctl ctl

The output from this command shows that the character major number for the
sctl driver is 203.

4 The commands to create the devices file for the robotic controls are as follows:

cd /dev/sctl
/usr/sbin/mknod c12t0l0 c 203 0x0c0000
/usr/sbin/mknod c13t0l0 c 203 0x0d0000
/usr/sbin/mknod c13t0l4 c 203 0x0d0400

If you add the robots to NetBackup manually, you specify the following
pathnames for robotic control. The first device file is for the HP EML E-Series
robot. The second and third device files are for the VLS 6000 robot (two robotic
devices).

/dev/sctl/c12t0l0
/dev/sctl/c13t0l0
/dev/sctl/c13t0l4

About creating legacy tape drive device files

By default, HP-UX creates tape drive device files when the system is booted.
However, the tape driver must be installed and configured, and the devices must
be attached and operational.
Alternatively, you can create tape drive device files manually. To do so, use either
the HP-UX System Administration Manager (SAM) utility or the insf(1M) command.
For information, see the HP-UX documentation.

Creating tape drive pass-through device files

On media servers, NetBackup creates pass-through paths for tape drives
automatically. However, you can create them manually.
NetBackup also uses the tape drive pass-through device files for SAN Client.
Use one of the following two procedures:
■ Create pass-through tape drive device files
See “To create pass-through tape drive device files” on page 107.
 HP-UX Specific Configuration Details 107
About configuring legacy device files

■ Create SAN client pass-through device files

See “To create SAN client legacy pass-through device files” on page 109.
To create pass-through tape drive device files
1 Determine the devices that are attached to the SCSI bus by using the HP-UX
ioscan -f command, as follows:

ioscan -f
Class I H/W Path Driver S/W State H/W Type Description
=================================================================
ext_bus 7 0/7/0/ c720 CLAIMED INTERFACE SCSI C896 Fast Wide LVD
target 10 0/7/0/1.0 tgt CLAIMED DEVICE
tape 65 0/7/0/1.0.0 stape CLAIMED DEVICE QUANTUM SuperDLT1
target 11 0/7/0/1.1 tgt CLAIMED DEVICE
tape 66 0/7/0/1.1.0 stape CLAIMED DEVICE QUANTUM SuperDLT1
target 12 0/7/0/1.2 tgt CLAIMED DEVICE
autoch 14 0/7/0/1.2.0 schgr CLAIMED DEVICE ADIC Scalar 100
target 13 0/7/0/1.3 tgt CLAIMED DEVICE
autoch 19 0/7/0/1.3.0 schgr CLAIMED DEVICE IBM ULT3583-TL
target 14 0/7/0/1.4 tgt CLAIMED DEVICE
tape 21 0/7/0/1.4.0 atdd CLAIMED DEVICE IBM ULT3580-TD1
target 15 0/7/0/1.5 tgt CLAIMED DEVICE
tape 19 0/7/0/1.5.0 atdd CLAIMED DEVICE IBM ULT3580-TD1

This example output shows the following:

■ The robotic control for an ADIC Scalar 100 library is on a SCSI bus with an
instance number of 7. The SCSI ID is 2, and the LUN is 0. The robotic
control for an IBM ULT3583-TL library is on the same SCSI bus at SCSI
ID 3 and LUN 0.
■ The ADIC library contains two Quantum Super DLT drives. One has a SCSI
ID of 0 and a LUN of 0. The other has a SCSI ID of 1 and a LUN of 0.
■ The IBM library contains two IBM Ultrium LTO drives. One has a SCSI ID
of 4 and a LUN of 0. The other has a SCSI ID of 5 and a LUN of 0.
Use the IBM atdd driver when you configure IBM tape drives on HP-UX.
Configure atdd and BEST device paths according to the IBM driver
documentation. Do not configure atdd for robotic control of IBM robots. For
 HP-UX Specific Configuration Details 108
About configuring legacy device files

the latest recommended atdd driver version from IBM, check the Veritas
support Web site.

2 Create the pass-through device files for the tape drives, as follows:

cd /dev/sctl
/usr/sbin/mknod c7t0l0 c 203 0x070000
/usr/sbin/mknod c7t1l0 c 203 0x071000
/usr/sbin/mknod c7t4l0 c 203 0x074000
/usr/sbin/mknod c7t5l0 c 203 0x075000

When you use the HP-UX mknod command for tape drives, the target is the
SCSI ID of the tape drive. It is not the SCSI ID of the robotic control.
The previous commands create the following pass-through device files.

/dev/sctl/c7t0l0
/dev/sctl/c7t1l0
/dev/sctl/c7t4l0
/dev/sctl/c7t5l0

Although the pass-through device files for tape drives are used during
NetBackup operation, they are not used during NetBackup configuration. During
NetBackup tape drive configuration, use the following device files to configure
the tape drives.

/dev/rmt/c7t0d0BESTnb
/dev/rmt/c7t1d0BESTnb
/dev/rmt/c7t4d0BESTnb
/dev/rmt/c7t5d0BESTnb
 HP-UX Specific Configuration Details 109
About configuring legacy device files

To create SAN client legacy pass-through device files

1 Determine the devices that are attached to the SCSI bus by using the HP-UX
ioscan -f command, as follows:

ioscan -f
Class I H/W Path Driver S/W State H/W Type Description
=================================================================================
ext_bus 9 0/3/1/0.1.22.255.0 fcd_vbus CLAIMED INTERFACE FCP Device Interface
target 4 0/3/1/0.1.22.255.0.0 tgt CLAIMED DEVICE
tape 6 0/3/1/0.1.22.255.0.0.0 stape CLAIMED DEVICE ARCHIVE Python
tape 7 0/3/1/0.1.22.255.0.0.1 stape CLAIMED DEVICE ARCHIVE Python

This example output shows that the instance number of the Fibre Channel
HBA is 9. It also shows that the target mode drivers on the Fibre Transport
media server appear as ARCHIVE Python devices. One has a SCSI ID of 0
and a LUN of 0; the other has a SCSI ID of 0 and a LUN of 1.
From HP-UX 11i V3, agile device view is recommended and preferred. If the
ioscan -f command does not list any ARCHIVE Python device, refer to the
To create SAN client agile pass-through device files (HP-UX 11i V3 and later
versions) section to use agile device addressing method.
2 Determine the character major number of the sctl driver by using the following
command:

lsdev -d sctl
Character Block Driver Class
203 -1 sctl ctl

The output from this command shows that the character major number for the
sctl driver is 203.
3 Create the pass-through device files, as follows:

cd /dev/sctl
/usr/sbin/mknod c9t0l0 c 203 0x090000
/usr/sbin/mknod c9t0l1 c 203 0x090100

The following describes the device file name:

■ c9 defines the instance number of the interface card.

■ t0 defines the SCSI ID (the target).

 HP-UX Specific Configuration Details 110
About configuring legacy device files

■ l1 defines the LUN (the first character is the letter “l”).

4 Verify that the device files were created, as follows:

# ls -l /dev/sctl
total 0
crw-r--r-- 1 root sys 203 0x090000 Nov 1 13:19 c9t0l0
crw-r--r-- 1 root sys 203 0x090100 Nov 1 13:19 c9t0l1
 HP-UX Specific Configuration Details 111
About configuring legacy device files

To create SAN client agile pass-through device files (HP-UX 11i V3 and later
versions)
1 Determine the devices instance number, SCSI number and lun number by
using the HP-UX ioscan -kCtape -P wwid command as follows:

bash-4.4# ioscan -kCtape -P wwid

Class I H/W Path wwid
===============================
tape 133 64000/0xfa00/0xa0 SYMANTECFATPIPE 0.0 limbo.com
tape 142 64000/0xfa00/0xa9 SYMANTECFATPIPE 0.1 limbo.com

Only the devices with the SYMANTECFATPIPE keyword in the wwid field are the
devices to look for. This example output shows that the instance number of
the SAN client specific tapes are 133 and 142. Based on two numbers following
the SYMANTECFATPIPE keyword, they also show that the SCSI number of device
instance 142 is 0 and the lun number is 1. In the same way, the SCSI number
of device instance 133 is 0 and the lun number is 0.
2 Create the pass-through device files in the /dev/sctl/ directory as follows:

#cd /dev/sctl
#mksf -d estape -P -I 133 -v -r /dev/sctl/c133t0l0
making /dev/sctl/c133t0l0 c 12 0x0000a0
#mksf -d estape -P -I 142 -v -r /dev/sctl/c142t0l1
making /dev/sctl/c142t0l1 c 12 0x0000a9

Option -I is used to specify the instance number. Instances number are listed
with the ioscan command in step 1.
The last part of the command mksf is an absolute name of the pass-through
device.
/dev/sctl/ is the path where the pass-through device files must exist.

c142 defines the instance number of the tape device. t0 defines the SCSI ID
(the target). l1 defines the LUN (the first character is the letter "l").
3 Verify that the device files were created using the following command:

bash-4.4# ls -l /dev/sctl
total 0
crw-r----- 1 bin sys 12 0x0000a0 Jun 29 12:33 c133t0l0
crw-r----- 1 bin sys 12 0x0000a9 Jun 30 09:39 c142t0l1
 Index

A D
activity deployment planning 12
viewing SAN Client logs 77 device drivers
AIX for legacy device files 96
configuring robotic control device files for IBM device files
robots 90 creating for SAN clients on AIX 90
introduction 89 creating for SAN clients on HP-UX 98
smit tool 90 creating no rewind 92
tape drive configuration for legacy tape drives 96
make device files 91 no rewind 91
variable mode devices 91 disabling an FT media server 73–74
Always property in Fibre Transport host properties 63
Always property in SAN Client Usage Preferences 66 E
atdd driver
examples
HP-UX 108
no rewind device file 93

C F
chdev command 91
Fail property in Fibre Transport host properties 63
cluster
Fail property in SAN client usage perferences 66
about SAN Clients in clusters 16
Fibre Channel
configuring SAN clients in a cluster 55
HP-UX configuration example 102, 104
configuration guidelines
Fibre Transport
HP-UX 95
about Fibre Transport media servers 10
configuring
restores 17
legacy device files 98
viewing jobs details 69
robotic control device files for IBM robots in
viewing logs 77
AIX 90
viewing traffic information 70
creating
Fibre Transport (FT)
legacy SCSI and FCP robotic controls on
host properties 60
HP-UX 99
firewalls
legacy tape drive device files 106
about configuring for SAN clients 52
no rewind device files for tape drives 92
fixed length block 91
sctI device file for FCP (Itanium) 104
FlashBackup restores
sctI device file for FCP (PA-RISC) 102
over Fibre Transport 17
sctl device file for SCSI (PA-RISC) 100
FT media server
tape drive pass-through device files 106
disabling 73–74
creating device files
for SAN clients on AIX 90
for SAN clients on HP-UX 98 H
HP-UX
configuration guidelines 95
 Index 113

HP-UX (continued) R
creating legacy SCSI and FCP robotic controls 99 removing
SCSI robotic controls 96 FT media server 73–74
Hyper-V 16 removing an FT media server 73–74
restores over Fibre Transport 17
J robotic control device files
job ID search in unified logs 82 for IBM robots in AIX 90
robotic controls
SCSI
L HP-UX 96
legacy device files
configuring 98
device drivers supported 96 S
legacy pass-through paths SAN Client
for tape drives 97 configuring usage properties 64
legacy tape drive device files viewing jobs details 69
creating 106 SAN client usage perferences
legacy tape drives Always 66
device file names 96 Fail 66
logging Never 66
originator IDs 77 Preferred 66
viewing logs 77 Use defaults from the master server
configuration 65
SAN clients
M about 10
Maximum concurrent FT connections property in Fibre configuring drivers on AIX 90
Transport host properties 62 configuring drivers on HP-UX 98
schgr device driver
N HP-UX 99
nbhba driver SCSI
removing 73–74 robotic control
Never property in Fibre Transport host properties 63 HP-UX 96
Never property in SAN client usage perferences 66 sctl device file
no rewind device file example 93 creating for FCP (Itanium) 104
no rewind device files 91 creating for FCP (PA-RISC) 102
creating 92 creating for SCSI (PA-RISC) 100
smit command 91
O
operational notes 13 T
originator IDs 77 tape drive configuration
on AIX
make device files 91
P
tape drive pass-through device files
Preferred property in Fibre Transport host
creating 106
properties 62
tape drives
Preferred property in SAN Client Usage
creating no rewind device files 92
Preferences 66
legacy pass-through paths 97
target mode driver
removing 73–74
 Index 114

U
unified logging 78
format of files 79
Use defaults from the master server configuration
property 65
Use defaults from the master server configuration
property in Fibre Transport host properties 62

V
variable length block 91
variable-mode devices
on AIX 91
viewing Fibre Transport logs 77
vxlogview command 79
with job ID option 82

W
Windows Hyper-V 16