Veritas Netbackup Shared Storage Guide

Veritas NetBackup™

Shared Storage Guide

UNIX, Windows, Linux

Release 6.5

12308346

2

Veritas NetBackup Shared Storage Guide

Copyright © 2007 Symantec Corporation. All rights reserved. NetBackup 6.5 Symantec, the Symantec logo, and NetBackup are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners. Portions of this software are derived from the RSA Data Security, Inc. MD5 Message-Digest Algorithm. Copyright 1991-92, RSA Data Security, Inc. Created 1991. All rights reserved. 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 Symantec Corporation and its licensors, if any. THIS 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, SYMANTEC CORPORATION 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” and “commercial computer software documentation” as defined in FAR Sections 12.212 and DFARS Section 227.7202. Symantec Corporation 20330 Stevens Creek Blvd. Cupertino, CA 95014 www.symantec.com Printed in the United States of America.

3

Third-party legal notices Third-party software may be recommended, distributed, embedded, or bundled with this Veritas product. Such third-party software is licensed separately by its copyright holder. All third-party copyrights associated with this product are listed in the accompanying release notes.

Licensing and registration Veritas NetBackup is a licensed product. See the NetBackup Installation Guide for license installation instructions.

Technical support For technical assistance, visit http://entsupport.symantec.com and select phone or email support. Use the Knowledge Base search feature to access resources such as TechNotes, product alerts, software downloads, hardware compatibility lists, and our customer email notification service.

Contents

Chapter 1

Introduction

Section I

OpenStorage disk option

Chapter 2

Introduction Overview ................................................................................................................15

Vendor controls the storage ...............................................................................17

NetBackup Release Notes ...................................................................................17

Chapter 3

Installing the storage appliance Installing the disk storage appliance ................................................................19

Installing the vendor’s OpenStorage plug-in ..................................................20

Chapter 4

Licensing OpenStorage

Chapter 5

Configuring OpenStorage Creating a storage server in NetBackup ...........................................................23

Adding storage server credentials ....................................................................25

Creating an OpenStorage disk pool ...................................................................27

Creating a storage unit ........................................................................................29

Usage recommendations ............................................................................31

Creating a backup policy .....................................................................................33

NetBackup catalog backups ........................................................................33

Restores .........................................................................................................33

Optimized duplication .........................................................................................34

Chapter 6

Managing OpenStorage Managing disk pools ............................................................................................37

Changing disk pool properties ...................................................................37

Adding volumes to an OpenStorage disk pool .........................................39

Changing disk pool or volume state ..........................................................40

Merging disk pools .......................................................................................41

Deleting a disk pool .....................................................................................42

Obtaining disk pool and volume status ....................................................43

6

Managing OpenStorage server credentials ..................................................... 44

Managing storage servers .................................................................................. 45

Viewing storage servers .............................................................................. 45

Deleting a storage server ............................................................................ 46

Obtaining storage server status ................................................................ 46

Managing OpenStorage data movers ............................................................... 47

Monitoring storage capacity and usage ........................................................... 48

Viewing disk reports ........................................................................................... 49

Viewing NetBackup logs ..................................................................................... 50

Troubleshooting OpenStorage .......................................................................... 51

Vendor plug-in errors ................................................................................. 51

Vendor plug-in not installed ...................................................................... 52

Unable to access storage ............................................................................. 52

Section II

SharedDisk option

Chapter 7

Introduction Overview ............................................................................................................... 55

NetBackup Release Notes ................................................................................... 56

Chapter 8

Preparing the SAN and the array Preparing the SAN ............................................................................................... 57

Zoning the SAN ............................................................................................ 58

Installing HBAs for SharedDisk ................................................................ 58

Connecting the media servers and the array .......................................... 58

Installing array software on media servers ..................................................... 59

Configuring the disk array ................................................................................. 59

Adding array host entries ........................................................................... 59

Allocating LUNs for NetBackup ................................................................ 60

Adding LUN entries to the sd.conf file ..................................................... 61

Chapter 9

Licensing SharedDisk

Chapter 10

Configuring SharedDisk Specifying the mount point directory .............................................................. 65

Creating a storage server in NetBackup ........................................................... 66

Adding disk array logon credentials ................................................................. 68

Formatting the LUNs in a disk array ................................................................ 70

Creating a SharedDisk disk pool ....................................................................... 72

Enclosure method of SharedDisk disk pool creation ............................. 73

Volumes method of SharedDisk disk pool creation ............................... 74

7

Creating a storage unit ........................................................................................75

Usage recommendations ............................................................................79

Creating a backup policy .....................................................................................80

Restores .........................................................................................................80

Chapter 11

Managing SharedDisk Managing disk pools ............................................................................................81

Changing disk pool properties ...................................................................81

Adding volumes to a SharedDisk disk pool ..............................................83

Changing disk pool or volume state ..........................................................87

Merging disk pools .......................................................................................88

Deleting a disk pool .....................................................................................89

Obtaining disk pool and volume status ....................................................90

Managing disk array logon credentials ............................................................91

Managing storage servers ..................................................................................92

Viewing storage servers ..............................................................................92

Adding a SharedDisk storage server .........................................................93

Removing a SharedDisk storage server from disk pool access .............93

Deleting a storage server ............................................................................94

Obtaining storage server status .................................................................95

Monitoring storage capacity and usage ...........................................................95

Viewing disk reports ............................................................................................96

Viewing NetBackup logs .....................................................................................97

Troubleshooting SharedDisk .............................................................................98

SharedDisk troubleshooting checklist ......................................................98

Determining masked LUNs ......................................................................107

Checking out a SharedDisk disk volume ................................................107

Disk failure ..................................................................................................108

Section III

Shared Storage Option

Chapter 12

Introduction Overview ..............................................................................................................113

SAN media server .......................................................................................114

A SAN is not required for Shared Storage Option ................................114

Sample Shared Storage Option configuration with SAN components 114

NetBackup Release Notes .................................................................................115

Chapter 13

Licensing the Shared Storage Option

Chapter 14

Configuring the Shared Storage Option

8

Configuration tasks ........................................................................................... 119

Installing and configuring drivers .................................................................. 121

Verifying connectivity ...................................................................................... 121

Configuring Shared Storage Option in NetBackup ......................................121

Configuring Shared Storage Option devices in NetBackup ................. 122

Adding Shared Storage Option configuration options ........................ 122

Configuring NetBackup storage units and backup policies ................ 122

Verifying your Shared Storage Option configuration ................................. 123

Chapter 15

Using the Shared Storage Option Using the Device Monitor with Shared Storage Option .............................. 127

The Drive Status pane ...............................................................................127

Changing the operating mode for a shared drive ................................. 128

Adding or changing a comment for a shared drive .............................. 128

Performing drive cleaning functions for a shared drive ..................... 128

Shared Storage Option summary reports ...................................................... 128

Adding configuration options .......................................................................... 129

Chapter 16

Shared Storage Option Reference Terms and concepts .......................................................................................... 131

Shared Storage Option components ............................................................... 132

NetBackup EMM ......................................................................................... 132

Example Shared Storage Option configuration .................................... 133

Scan host ..................................................................................................... 134

Device allocation host ...............................................................................135

Chapter 17

Troubleshooting the Shared Storage Option Hardware configuration guidelines ................................................................ 137

Configuration guidelines .................................................................................. 138

Operating system help ...................................................................................... 139

Common configuration issues with Shared Storage Option ....................... 139

Frequently asked questions about Shared Storage Option ......................... 140

Section IV SAN Client and Fibre Transport Chapter 18

Introduction Overview ............................................................................................................. 145

SAN client ...................................................................................................146

FT media servers ........................................................................................ 146

FT Service Manager ................................................................................... 146

Clustering ............................................................................................................ 146

9

NetBackup Release Notes .................................................................................147

Chapter 19

Preparing the SAN Zoning your SAN ................................................................................................149

Installing HBAs for Fibre Transport ...............................................................150

HBAs on SAN clients .................................................................................150

HBAs on NetBackup FT media servers ...................................................150

Selecting the ports .............................................................................................151

Connecting the Fibre .........................................................................................151

N_Port switched configuration ................................................................151

Direct connect FC-AL configuration .......................................................152

Chapter 20

Installing SAN clients and Fibre Transport Installing PBX on the SAN clients ...................................................................154

Upgrading SAN clients and Fibre Transport .................................................154

Uninstalling SAN clients and Fibre Transport ..............................................155

Disabling the SAN client service .............................................................155

Removing the FT services and drivers ...................................................155

Chapter 21

Configuring SAN clients and Fibre Transport Configuring the FT media server .....................................................................157

Configuring the HBAs ...............................................................................158

Configuring the FT services .....................................................................163

Configuring firewalls on SAN clients .............................................................166

Configuring SAN client drivers .......................................................................166

AIX ................................................................................................................166

HP-UX ..........................................................................................................166

Linux ............................................................................................................167

Solaris ..........................................................................................................167

Windows ......................................................................................................167

Configuring the SAN client FT service ...........................................................167

Configuring SAN clients in a cluster .......................................................169

Configuring FT properties ................................................................................169

Configuring global FT properties for SAN clients ................................170

Configuring FT properties for media servers ........................................170

Configuring FT properties for SAN clients ............................................171

Configuring SAN client FT usage preferences ......................................171

Fibre Transport properties .......................................................................173

Chapter 22

Managing SAN clients and Fibre Transport Managing FT services ........................................................................................175

10

Enabling or disabling the FT services ..................................................... 175

Rescanning SAN clients ............................................................................ 176

Viewing FT job details ....................................................................................... 177

Viewing FT pipe activity ................................................................................... 177

Adding a SAN client .......................................................................................... 178

Deleting a SAN client ........................................................................................ 179

Troubleshooting Fibre Transport ................................................................... 179

SAN client service does not start ............................................................ 179

Stopping and starting FT services ..........................................................180

Media server FT device is offline ............................................................. 180

No FT devices discovered ......................................................................... 181

SAN client FT service validation ............................................................. 181

SAN client does not select Fibre Transport ........................................... 182

Viewing FT logs .......................................................................................... 183

For more troubleshooting information .................................................. 183

Index

185

Chapter

1

Introduction This guide describes how to install, configure, and use shared storage and Fibre Transport with NetBackup. Shared storage NetBackup provides several options that allow you to share storage among multiple NetBackup media servers: ■

The OpenStorage disk option allows multiple NetBackup media servers to share intelligent disk appliance storage. For more information, see “OpenStorage disk option” on page 13.

■

The SharedDisk option allows multiple NetBackup media servers to share disk array storage. For more information, see “SharedDisk option” on page 53.

■

The Shared Storage Option allows multiple NetBackup media servers to share individual tape drives (stand-alone drives or drives in a robotic library). For more information, see “Shared Storage Option” on page 111.

SAN Client and NetBackup Fibre Transport NetBackup also provides a separately licensed option for high-speed data transport. NetBackup Fibre Transport provides high-performance I/O backup rates for NetBackup client systems by using a Storage Area Network (SAN) for data transport. You can use NetBackup Fibre Transport with disk storage in NetBackup. For more information, see “SAN Client and Fibre Transport” on page 143.

12 Introduction

Section

OpenStorage disk option

■

“Introduction” on page 15

■

“Installing the storage appliance” on page 19

■

“Licensing OpenStorage” on page 21

■

“Configuring OpenStorage” on page 23

■

“Managing OpenStorage” on page 37

I

14

Chapter

2

Introduction The NetBackup OpenStorage disk option provides an API between NetBackup

and disk storage. The API allows NetBackup to use disk appliances from

third-party vendors for backup storage.

NetBackup aggregates the disk into pools of storage you can use for backups.

NetBackup manage the storage as logical entities (disk pools).

For more information about OpenStorage, see:

■

“Overview” on page 15

■

“Vendor controls the storage” on page 17

■

“NetBackup Release Notes” on page 17

For information about how to configure and use OpenStorage, see:

■

“Licensing OpenStorage” on page 21

■

“Installing the storage appliance” on page 19

■

“Configuring OpenStorage” on page 23

■

“Managing OpenStorage” on page 37

Overview OpenStorage is a NetBackup API that allows NetBackup to communicate with intelligent disk appliances. Disk appliance vendors provide the storage, and they provide a software plug-in that you install on NetBackup media servers. The NetBackup media servers use the plug-in to communicate with the disk appliance. To determine a disk appliance’s capabilities, NetBackup uses the plug-in to query the storage appliance. Capabilities can include single-instance storage, optimized off-host duplication, and so on.

16 Introduction

Overview

Disk appliances typically are hardware and software solutions. The disk appliance vendors participate in the Symantec OpenStorage Partner Program. Symantec qualifies their storage solutions for the OpenStorage API. OpenStorage provides the following capabilities: ■

Share disks. Multiple NetBackup media servers can access the same disk volume concurrently.

■

Balance load and performance. NetBackup balances backup jobs and storage usage among the media servers and disk pools. For each backup job, NetBackup chooses the least full disk volume and least used media server.

■

NetBackup can use the disk appliance capabilities, which may include optimized off-host duplication and single-instance storage capabilities.

Figure 2-1

OpenStorage configuration

Load-balanced NetBackup media servers (data movers) have vendor plug-in installed

Any connectivity (directly attached, SAN, LAN)

Disk appliance (storage server

The terms that are used in OpenStorage include: ■

Data mover: An entity that moves data between the primary storage (the NetBackup client) and the storage server. In OpenStorage, NetBackup media servers function as the data movers.

■

Storage server: An entity that writes data to and reads data from disk storage. A storage server is the entity that has a mount on the file system on the storage. The disk appliance functions as the storage server.

■

Disk volume: A logical unit of disk storage.

■

Disk pool: A collection of disk volumes that are administered as an entity.

Introduction Vendor controls the storage

Vendor controls the storage NetBackup determines when backup images are created, copied, or deleted. Images cannot be moved, expired, or deleted on the storage unless NetBackup instructs the appliance to do so through the API. However, NetBackup does not control the storage or the storage format. NetBackup has no knowledge of how the backup images are stored; the disk appliance controls where the images reside on storage and in what form. Symantec does not control which appliance capabilities the vendor exposes through the OpenStorage API. Similarly, Symantec and NetBackup have no control over the communication between the vendor plug-in and the storage server. The vendor determines the API or protocol to use between the plug-in and the storage server.

NetBackup Release Notes For information about supported systems and peripherals, limitations, and operational notes, see the NetBackup Release Notes.

17

18 Introduction NetBackup Release Notes

Chapter

3

Installing the storage appliance The following provides guidance for when you install the storage appliance: ■

“Installing the disk storage appliance” on page 19

■

“Installing the vendor’s OpenStorage plug-in” on page 20

Installing the disk storage appliance Before you can configure OpenStorage in NetBackup, you must install and configure the disk storage appliance in your backup environment. The appliance is known in NetBackup as a storage server. The appliance must be operational before you can use it for backups. Specifically, do the following: ■

Add the appliance to your environment.

■

Install the vendor software packages on all NetBackup media servers that connect to the appliance. For more information, see “Installing the vendor’s OpenStorage plug-in” on page 20.

■

Perform vendor-specific steps to configure the appliance. Use the vendor’s processes and procedures to configure the appliance so that it works with your environment. To configure the storage, you may be required to: ■

Assign the appliance a name. NetBackup uses the name to identify the appliance.

■

Divide the appliance into one or more logical units of space. NetBackup refers to these logical units as disk volumes. NetBackup aggregrates the disk volumes into disk pools.

Instructions for how to install and configure the appliance are beyond the scope of the NetBackup documentation. For instructions, refer to the vendor documentation.

20 Installing the storage appliance Installing the vendor’s OpenStorage plug-in

Installing the vendor’s OpenStorage plug-in The storage vendor’s release package includes a plug-in that installs on the NetBackup media servers that connect to the storage server. The NetBackup media servers use the plug-in to communicate with the disk appliance. Install the plug-in on all NetBackup media servers that connect to the appliance. To install the plug-in, follow the vendor’s installation instructions. The vendor’s installation process may register the storage server and the plug-in with NetBackup and add the logon credentials. If not, you must perform these steps manually. Note: credentials must be defined even if the storage server does not require credentials. For procedures, see the following: ■

“Creating a storage server in NetBackup” on page 23

■

“Adding storage server credentials” on page 25

Chapter

4

Licensing OpenStorage No special installation is required for the NetBackup components of OpenStorage. However: ■

The NetBackup master server and all NetBackup media servers that use the feature must be at NetBackup 6.5 or later.

■

You must activate the feature by entering the OpenStorage Disk Option license key on the NetBackup master server.

The license key only enables the functionality in NetBackup. You must purchase a storage vendor’s product and install the storage vendor’s NetBackup plug-in. You may have one license key that activates NetBackup and all of your add-on products. Alternatively, you may have a separate license key for NetBackup and for each add-on product such as the OpenStorage Disk Option. If you remove the OpenStorage Disk Option license key or if it expires: ■

You cannot create the disk pools or the storage units that use the disk pools.

■

NetBackup jobs that attempt to use the disk pools or the storage units that are based on the disk pools fail. The error message indicates that the feature is not licensed.

■

NetBackup does not delete the disk pools or the storage units that are based on the disk pools. You can use them again if you enter a valid license key.

22 Licensing OpenStorage

Chapter

5

Configuring OpenStorage The following are the tasks to configure NetBackup to use OpenStorage: ■

“Creating a storage server in NetBackup” on page 23

■

“Adding storage server credentials” on page 25

■

“Creating an OpenStorage disk pool” on page 27

■

“Creating a storage unit” on page 29

■

“Creating a backup policy” on page 33

■

“Optimized duplication” on page 34

Creating a storage server in NetBackup A storage server is an entity that mounts the storage and writes data to and reads data from the disk storage. For OpenStorage, the disk appliance is the storage server. Create in this context means to add the disk appliance as a storage server. For each OpenStorage appliance, only one storage server exists. The storage server owns exclusive access to the storage. The NetBackup media servers that connect to the storage server function as data movers. A data mover moves data to be protected from primary storage to the storage server. The storage vendor’s plug-in installation process may also configure the storage server in NetBackup. (The vendor plug-in is installed on each NetBackup media server (that is, data mover) that connects to the storage.) If so, you do not have to configure the storage server in NetBackup. To determine if the storage server is defined in the NetBackup database already, see “To determine if a disk appliance is configured as a storage server already” on page 24.

24 Configuring OpenStorage

Creating a storage server in NetBackup

Figure 5-1

OpenStorage storage server

NetBackup media servers are data movers. The vendor plug-in is installed.

The disk appliance is the storage server.

To determine if a disk appliance is configured as a storage server already ◆

Run the following nbdevquery command on the NetBackup master server: nbdevquery -liststs

The command lists all storage servers already configured. By default, NetBackup configures all media servers as BasicDisk storage servers. Therefore, all media servers in your environment should appear as BasicDisk servers, as in the following example: nbdevquery -liststs

V6.5 tree.symantecs.org BasicDisk 5

V6.5 flower.symantecs.org BasicDisk 5

V6.5 water.symantecs.org BasicDisk 5

If the disk appliance does not appear in the command output as an OpenStorage storage server, create it. To create an OpenStorage storage server in NetBackup ◆

Run the following nbdevconfig command on the master server or on one of the media servers: nbdevconfig -creatests -storage_server storage_server -stype

server_type -st storage_type -media_server media_server

The following are the options and arguments: ■

-storage_server storage_server is the name of the disk appliance.

■

-stype server_type is a string that identifies the storage server type. The storage vendor provides the string that identifies the server type.

■

-st storage_type is a numeric value that specifies the OpenStorage server properties. The storage vendor provides the value. For OpenStorage, the default is 9 (network attached, formatted disk). The value is obtained by adding together the numeric values of the following properties. Whether the disk is formatted and how it is attached are mutually exclusive and complementary.

Configuring OpenStorage Adding storage server credentials

■

1 - formatted disk. The disk is formatted as part of the vendor-specific preparation; NetBackup does not format the disk.

■

2 - raw disk. The disk is not formatted; NetBackup formats the disk.

■

4 - direct attached. Direct attached means that the storage server and media server are the same NetBackup host.

8 - network attached. Network attached means the storage server is physically distinct from the NetBackup media server. It does not imply LAN data movement nor does it preclude Fibre Channel as the transport for data movement. The default value is valid for all participating OpenStorage vendors when this document was published. If the vendor does not provide the value, use 9. ■

■

-media_server media_server is the name of a NetBackup media server that connects to the storage server. The media server queries the storage server for its capabilities. The vendor plug-in must be installed on the media server. If the plug-in resides on more than one media server, you can specify any one of them.

The nbdevconfig command and the nbdevquery command reside in the following directory: UNIX: /usr/openv/netbackup/bin/admincmd Windows: install_path\Program Files\VERITAS\NetBackup\bin\admincmd For more information, see NetBackup Commands for UNIX and Linux or NetBackup Commands for Windows.

Adding storage server credentials The disk appliance (the storage server) may require logon credentials. NetBackup requires that the credentials be entered on each NetBackup media server that connects to the storage server. When you add the credentials, NetBackup: ■

Saves the credentials so the media server can log into the storage server. Note: If the storage server does not require logon credentials, you must enter dummy credentials so that NetBackup configures the media server as a data mover.

■

Configures the media server as a data mover. A data mover is an entity that moves data between the primary storage (the NetBackup client) and the storage server (the disk appliance).

25

26 Configuring OpenStorage Adding storage server credentials

NetBackup does not monitor connectivity between data movers and storage servers. However, when you add the credentials on each media server, NetBackup configures and maintains an access path between the media server and the storage server. The storage vendor’s plug-in installation process may create the logon credentials on each NetBackup media server that connects to the storage server. (See “To determine if the storage server credentials are configured already” on page 26.) If that process does not create the logon credentials, you must add them. Figure 5-2

Media servers are OpenStorage data movers

NetBackup media servers are data movers. Storage server logon credentials are configured and the vendor plug-in is installed on each.

Disk appliance is the storage server.

To determine if the storage server credentials are configured already ◆

Run the following command on the NetBackup master server: tpconfig –dsh –all_hosts –stype server_type

server_type is a vendor-provided string that identifies the storage server type. The command lists the media servers for which the storage server credentials are configured already for that storage type. If the media servers do not appear in the command output, use the following procedure to add them. To add storage server credentials to a media server ◆

Use the NetBackup tpconfig utility to add the storage server credentials. Enter the same credentials on each NetBackup media server on which the vendor’s plug-in is installed. The following is the command syntax: tpconfig -add -storage_server server_name -stype server_type

-sts_user_id user_id -password password -st storage_type

The following describe the options that require arguments: ■

-storage_server server_name. The host name of the storage server.

Configuring OpenStorage Creating an OpenStorage disk pool

■

-stype server_type. A string that identifies the storage server type. The storage vendor provides the string.

■

-sts_user_id user_id. The user name to use to log into the storage server. If the storage server does not require logon credentials, enter dummy credentials.

■

-password password. The password to use to log into the storage server. If the storage server does not require logon credentials, enter dummy credentials.

■

The -st storage_type is a numeric value that specifies the storage server properties. The storage vendor provides the value. For OpenStorage, the default is 9 (network attached, formatted disk). The value is obtained by adding together the numeric values of the following properties. Whether the disk is formatted and how it is attached are mutually exclusive and complementary. ■

1 - formatted disk. The disk is formatted as part of the vendor-specific preparation; NetBackup does not format the disk.

■

2 - raw disk. The disk is not formatted; NetBackup formats the disk.

■

4 - direct attached. Direct attached means that the storage server and media server are the same NetBackup host.

8 - network attached. Network attached means the storage server is physically distinct from the NetBackup media server. It does not imply LAN data movement nor does it preclude Fibre Channel as the transport for data movement. The default value is valid for all participating OpenStorage vendors when this document was published. If the vendor does not provide the value, use 9. ■

The tpconfig command resides in the following directory: UNIX: /usr/openv/volmgr/bin Windows: install_path\Program Files\VERITAS\Volmgr\bin For more information, see NetBackup Commands for UNIX and Linux or NetBackup Commands for Windows.

Creating an OpenStorage disk pool An OpenStorage disk pool represents disk volumes in the underlying disk appliance. NetBackup aggregates the disk volumes into pools of storage you can use for backups.

27

28 Configuring OpenStorage Creating an OpenStorage disk pool

Figure 5-3

OpenStorage disk pools

Disk appliance

DP_Gold_OpenStorage

DP_Silver_OpenStorage

A disk pool is the storage destination of a NetBackup storage unit. Use the Disk Pool Configuration Wizard to create a disk pool. When you create a disk pool, you specify: ■

The storage server.

■

The disk volumes to include in the pool.

■

The disk pool properties. Properties include the name, the high water mark, the low water mark, and a comment that describes the disk pool. For more information, see “Disk pool properties” on page 82.

You do not specify data mover names when you create a disk pool. When you add storage server credentials to NetBackup media servers, NetBackup configures the media servers as data movers. You can allow or disallow data mover access to the disk pool when you configure a NetBackup storage unit. Symantec recommends that disk pool names be unique across your enterprise. When NetBackup sends backup data to a disk pool, NetBackup selects disk volumes based on available capacity and predicted size of the backup. NetBackup tries to write backup data to a single volume. If necessary, backup images span disk volumes in a disk pool. Backup images do not span across multiple disk pools. To create an OpenStorage disk pool by using the wizard 1

In the NetBackup Administration Console tree, select the master server or Media and Device Management.

2

From the list of wizards in the Details pane, click Configure Disk Pool and follow the wizard instructions. For help, see the wizard help.

Configuring OpenStorage Creating a storage unit

Creating a storage unit

Create one or more storage units that reference the disk pool.

The Disk Pool Configuration Wizard lets you create a storage unit; therefore,

you may have created a storage unit when you created a disk pool. To determine

if storage units exist for the disk pool, see the NetBackup Management >

Storage > Storage Units window of the Administration Console.

For disk pool storage unit recommendations, see “Usage recommendations” on

page 31.

To create a storage unit from the Actions menu 1

In the NetBackup Administration Console, select NetBackup Management > Storage > Storage Units.

2

Click Actions > New > Storage Unit.

The OpenStorage vendor name is included in the disk type name

To restrict access to specific media servers, select them here

3

Complete the fields in the New Storage Unit dialog box.

The following are the configuration options for a disk pool storage unit.

29

30 Configuring OpenStorage Creating a storage unit

Storage unit name Enter a unique storage unit name for the new storage unit. The name can

describe the type of storage. The storage unit name is the name used to specify a

storage unit for policies and schedules. The storage unit name cannot be

changed after creation.

Storage unit type

Select Disk as the storage unit type.

Disk type

For an OpenStorage storage unit, select OpenStorage (VendorName).

VendorName is a string provided by the storage vendor that identifies the

vendor or storage.

Disk pool Select the disk pool that contains the storage for this storage unit.

All disk pools of the specified Disk type appear in the Disk pool list. If no disk

pools are configured, no disk pools appear in the list.

Media server

The Media server setting specifies the NetBackup media servers that can move

data to and from the storage server for this storage unit. (For OpenStorage,

NetBackup media servers function as data movers.)

Only the media servers that are configured as data movers for the OpenStorage

implementation appear in the media server list. If a media server does not

appear in the list, verify that the software plug-in is installed and that logon

credentials are created.

Specify the media server or servers as follows:

■

To allow any server in the media server list to access the storage server (default), select Use any available media server.

■

To restrict the media servers that can function as data movers for this storage unit, select Only use the following media servers. Then, select the media servers to allow.

NetBackup selects the media server to use when the policy runs. Maximum concurrent jobs The Maximum concurrent jobs setting specifies the maximum number of jobs that NetBackup can send to a disk storage unit at one time. (Default: 1 job. The job count can range from 0 to 256.) This setting corresponds to the Maximum concurrent write drives setting for a Media Manager storage unit. NetBackup queues jobs until the storage unit is available. If three backup jobs are ready to be sent to the storage unit and Maximum concurrent jobs is set to

Configuring OpenStorage Creating a storage unit

two, the first two jobs start and the third job waits. If a job contains multiple copies, each copy applies toward the Maximum concurrent jobs count. The number to enter depends on the available disk space and the server's ability to run multiple backup processes. You can use maximum concurrent jobs to balance the load between disk storage units. A higher number of concurrent jobs means that the disk can be busier than if the number is lower. Caution: A Maximum concurrent jobs setting of 0 disables the storage unit. For information about how NetBackup balances storage unit and media server load, see “Maximum concurrent jobs” in: ■

NetBackup Administrator’s Guide for UNIX and Linux, Volume I

■

NetBackup Administrator’s Guide for Windows, Volume I

Maximum fragment size Specify the largest fragment size that NetBackup can create to store backups.

The default maximum fragment size for a disk storage unit is 524,287

megabytes. To specify a maximum fragment size other than the default, enter a

value from 20 megabytes to 524,287 megabytes.

Backups to disk are usually fragmented to ensure that the backup does not

exceed the maximum size that the file system allows.

If an error occurs in a backup, the entire backup is discarded. The backup

restarts from the beginning, not from the fragment where the error occurred.

(An exception is for backups for which checkpoint and restart is enabled. In that

case, fragments before and including the last checkpoint are retained; the

fragments after the last checkpoint are discarded.)

Usage recommendations For usage recommendations, see the following:

Multiple storage units You can use multiple storage units for one disk pool to separate your backup traffic and still write all data to the same disk pool. You do not need to partition the storage because all storage units use the same pool of storage. Example 1 For example, if you use the NetBackup Fibre Transport option, you can separate the NetBackup SAN client traffic from the regular NetBackup client traffic in your environment:

31

32 Configuring OpenStorage Creating a storage unit

■

Define a storage unit (such as STU-FT). Select the disk pool. Select Only use the following media servers. Select the FT media servers that connect to the SAN clients.

■

Create a backup policy for the SAN clients and select the STU-FT storage unit.

■

Define another storage unit (such as STU-LAN). Select the same disk pool. Select Only use the following media servers. Select the media servers with LAN connectivity to the regular clients.

■

Create a backup policy for the regular clients and select the STU-LAN storage unit.

This scenario assumes that the SAN clients are a small subset of your client base. It also assumes that the media servers with LAN connectivity to the regular clients also have SAN connectivity to the storage. Example 2 Even without a SAN, you can separate your backup traffic similarly and still write all of the data to the same disk pool. For example, you can send the backups from your most important clients to a media server that is dedicated for the most important backups: ■

Define a storage unit (such as STU-CRITICAL). Select the disk pool. Select Only use the following media servers. Select one (or a subset) of the media servers.

■

Create a backup policy for the critical clients and select the STU-CRITICAL storage unit.

■

Define another storage unit (such as STU-NORMAL). Select the same disk pool. Select Only use the following media servers. Select a different subset of the media servers.

■

Create a backup policy for the regular clients and select the STU-NORMAL storage unit.

Maximum concurrent job setting You can use the multiple concurrent jobs settings on storage units to assign backup priority for important clients. For example, two storage units use the same set of media servers. One of the storage units has a higher concurrent job setting than the other. More client backups occur for the storage unit with the higher concurrent job setting.

Configuring OpenStorage Creating a backup policy

Creating a backup policy

Backup policies define the rules that NetBackup follows to back up clients.

Use normal NetBackup processes to configure backups to OpenStorage storage

units. That is, specify the appropriate storage unit in your backup policies.

Alternatively, specify a lifecycle policy that uses an OpenStorage storage unit as

the backup or duplication destination.

To create a policy, see “Policies” in the NetBackup Administrator’s Guide for

UNIX and Linux, Volume I or the NetBackup Administrator’s Guide for Windows, Volume I. Monitor backup progress To monitor backup progress, use the Detailed Status tab of the Job Details dialog box. It shows the media server that functions as the data mover between the client and the storage server. If the media server cannot start or complete the job, NetBackup retries the job after the job retry period elapses. (Configure the job retry interval by using the master server Global Attributes Job retry delay host property.) If you select more than one media server in the storage unit Media server field, NetBackup may retry the job with a different media server.

NetBackup catalog backups Symantec recommends that you do not send catalog backups to an OpenStorage disk pool because of the complexity of disaster recovery. BasicDisk storage units or tape storage units offer an easier bootstrapping mechanism. If you do send NetBackup catalog backups to an OpenStorage disk pool, you must rebuild the NetBackup device database at the recovery site: ■

The disk volumes IDs may differ on an appliance at the disaster recovery site from the IDs of the primary appliance.

■

If the NetBackup device database does not contain the correct disk pool and volume information for the backup images, NetBackup may not be able to locate the images from which to restore data.

Restores Use normal NetBackup processes to restore data from backups.

To perform the restore, NetBackup chooses one of the media servers that can

move data to and from the storage server.

33

34 Configuring OpenStorage Optimized duplication

Optimized duplication

If an OpenStorage disk appliance has the capability to copy the data on one appliance to another appliance of the same type, NetBackup can use that capability. The following are the requirements for optimized duplication: ■

The vendor must expose the off-host data movement capability in their plug-in.

■

Both the source and the destination disk pools must be the same OpenStorage vendor type.

■

One or more NetBackup media servers must connect to the source appliance and the destination appliance.

To configure optimized, off-host duplication: ■

Use a storage lifecycle policy. Configure the backup destination as a disk pool on one appliance and configure the duplication destination as a disk pool on another appliance. To create a lifecycle policy, see “Storage Lifecycle Policies” in the NetBackup Administrator’s Guide for UNIX and Linux or the NetBackup Administrator’s Guide for Windows.

■

Use a Vault policy for duplication between disk pools on the appliances. To create a Vault policy, see the NetBackup Vault Administrator’s Guide.

■

Use the NetBackup bpduplicate command for duplication between disk pools on the appliances. For more information about the bpduplicate command, see NetBackup Commands for UNIX and Linux or the NetBackup Commands for Windows.

A NetBackup media server initiates and manages the duplication between appliances. If the media server has connectivity to the destination appliance, it confirms the image copy occurred. NetBackup maintains records of the image copies and their locations in the NetBackup catalog. Some benefits of optimized, off-host duplication are: ■

Reduces the workload on the NetBackup media servers. More back ups can be performed.

■

Faster duplication. Duplication can occur in the background, simultaneously with ongoing backup jobs.

■

Reduced bandwidth. If the appliances support single instance store capabilities, the copy process may send only changed blocks.

■

Capacity management can be based on the value of the data. Least important data can be deleted from a primary disk pool, but only after duplication of that data.

The following are limitations:

Configuring OpenStorage Optimized duplication

■

The first failure of an optimized copy causes subsequent duplications to revert to regular duplication.

■

The copy operation uses the maximum fragment size of the source storage unit, not the setting for the destination storage unit. The optimized duplication copies the image fragments as is. The duplication does not resize and reshuffle the images into a different set of fragments on the destination storage unit.

■

To confirm the image copy, a media server must have connectivity to the destination appliance.

35

36 Configuring OpenStorage Optimized duplication

Chapter

6

Managing OpenStorage The following are tasks to manage the OpenStorage disk option: ■

“Managing disk pools” on page 37

■

“Managing OpenStorage server credentials” on page 44

■

“Managing storage servers” on page 45

■

“Managing OpenStorage data movers” on page 47

■

“Monitoring storage capacity and usage” on page 48

■

“Viewing disk reports” on page 49

■

“Viewing NetBackup logs” on page 50

■

“Troubleshooting OpenStorage” on page 51

Managing disk pools The following are tasks to manage disk pools: ■

“Changing disk pool properties” on page 37

■

“Adding volumes to an OpenStorage disk pool” on page 39

■

“Changing disk pool or volume state” on page 40

■

“Merging disk pools” on page 41

■

“Deleting a disk pool” on page 42

■

“Obtaining disk pool and volume status” on page 43

Changing disk pool properties You can change the high and the low water marks of a disk pool and change the comment that is associated with the disk pool.

38 Managing OpenStorage Managing disk pools

To change disk pool properties 1

In the NetBackup Administration Console tree, select Media and Device Management > Devices > Disk Pools.

2

Select the disk pool you want to change in the details pane.

3

Click Edit > Change.

4

In the Change Disk Pool dialog box, change properties.

Disk pool properties The following are the disk pool properties: ■

The disk pool name.

■

The storage server name.

■

The disk volumes that comprise the disk pool.

■

The total amount of space available in the disk pool.

Managing OpenStorage Managing disk pools

■

The total raw, unformatted size of the storage in the disk pool. For OpenStorage, the disk appliance may or may not expose the raw size of the storage.

■

A comment that is associated with the disk pool.

■

The high water mark for the disk pool. (The default is 98%.) The high water mark is a threshold that indicates the storage is full. It applies to both the individual disk volumes in the pool and the disk pool, as follows:

■

■

Individual volumes. When a disk volume reaches the high water mark, NetBackup writes the data to another disk volume in the pool.

■

Disk pool. When all volumes are at the high water mark, the disk pool is full. When a disk pool approaches the high water mark, NetBackup reduces the number of jobs that are allowed to write to the pool. NetBackup does not assign new jobs to a storage unit in which the disk pool is full.

The low water mark for the disk pool. (The default is 80%.) When the capacity of the disk pool returns to the low water mark, NetBackup again assigns jobs to the storage unit. Capacity is regained as backup images expire. The low water mark setting cannot be greater than or equal to the high water mark setting.

Adding volumes to an OpenStorage disk pool If you add disk volumes to the storage appliance, NetBackup does not add those volumes to an OpenStorage disk pool automatically. To use the additional disk volumes in an existing disk pool, you must add those volumes to the disk pool. (By default, NetBackup automatically increases disk pool capacity if the capacity of the underlying disk volumes increases. Similarly, NetBackup decreases the capacity of a disk pool if the underlying disk volume capacity decreases.) The NetBackup storage units that use the disk pool automatically use the additional storage capacity. You do not have to change the storage units. Note: Be careful when you add volumes to a disk pool. For data integrity, NetBackup does not allow volumes to be deleted from a disk pool. Because backup images may span disk volumes, a volume may contain valid image fragments. To remove a disk volume, you must delete all valid backup images and then delete the disk pool.

39

40 Managing OpenStorage

Managing disk pools

To add volumes to an OpenStorage disk pool 1

Create a disk pool from the new disk volumes on the storage server. For procedures, see “Creating an OpenStorage disk pool” on page 27.

2

Change the state of the two disk pools to DOWN. The following is the command syntax: nbdevconfig -changestate -stype server_type -dp disk_pool_name

-state DOWN

For the OpenStorage server type (server_type), the storage vendor provides the string that identifies the server type. 3

Merge the disk pools. The following is the command syntax. The primary disk pool is the one you want to retain; nbdevconfig deletes the secondary disk pool after the merge. nbdevconfig –mergedps -primarydp disk_pool_name -secondarydp

disk_pool_name

4

Change the state of the primary disk pool to UP. The following is the command syntax: nbdevconfig -changestate -stype server_type -dp disk_pool_name

-state UP

The nbdevconfig command resides in the following directory: UNIX: /usr/openv/netbackup/bin/admincmd Windows: install_path\Program Files\VERITAS\NetBackup\bin\admincmd For more information, see NetBackup Commands for UNIX and Linux or NetBackup Commands for Windows.

Changing disk pool or volume state Pool and volume states are UP or DOWN. You can change the state of a disk pool

or volume.

To change the state to DOWN, the disk pool must not be busy. If backup jobs are

assigned to the disk pool, the state change fails. Cancel the backup jobs or wait

until the jobs complete.

Note: For data integrity, NetBackup does not allow volumes to be deleted from a disk pool. Because backup images may span disk volumes, a volume may contain valid image fragments. To remove a disk volume, you must delete all valid backup images and then delete the disk pool. To change the disk pool state by using the Device Monitor 1

In the NetBackup Administration Console, select Media and Device Management > Device Monitor.

Managing OpenStorage Managing disk pools

2

Select the Disk Pools tab.

3

Select the disk pool.

4

Select either Actions > Up or Actions > Down.

To change the disk pool state by using the nbdevconfig command ◆

The following is the command syntax: nbdevconfig -changestate -stype server_type -dp disk_pool_name

-state state

For the storage server type (server_type), the storage vendor provides the

string that identifies the server type.

state is either UP or DOWN.

To change the disk volume state 1

Determine the name of the disk volume. The following command lists all volumes in the specified disk pool: nbdevquery -listdv -stype server_type -dp disk_pool_name

For the storage server type (server_type), the storage vendor provides the string that identifies the server type. 2

Change the disk volume state; the following is the command syntax: nbdevconfig -changestate -stype server_type -dp disk_pool_name

–dv vol_name -state state

For the storage server type (server_type), the storage vendor provides the

string that identifies the server type.

state is UP or DOWN.

NetBackup jobs still read from and write to a disk pool that has a downed

volume, but the downed volume is unavailable.

The nbdevconfig command and the nbdevquery command reside in the following directory: UNIX: /usr/openv/netbackup/bin/admincmd Windows: install_path\Program Files\VERITAS\NetBackup\bin\admincmd For more information, see NetBackup Commands for UNIX and Linux or NetBackup Commands for Windows.

Merging disk pools You can merge existing OpenStorage disk pools.

NetBackup updates the catalog records to show the correct location of the

backup images in those disk pools.

Prerequisites:

41

42 Managing OpenStorage

Managing disk pools

■

The volumes in the two disk pools must have unique names. OpenStorage requires that vendors use unique names for disk volumes in a disk appliance.

■

All volumes must be from the same storage server.

■

If the secondary disk pool is referenced by storage units, you must delete those storage units.

To merge disk pools 1

Change the state of each disk pool to DOWN; the following is the command syntax: nbdevconfig -changestate -stype server_type -dp disk_pool_name

-state DOWN

For the storage server type (server_type), the storage vendor provides the

string that identifies the server type.

If backup jobs are assigned to a disk pool, the state change fails. Cancel the

backup jobs or wait until the jobs complete.

2

Merge the disk pools. The following is the command syntax. The primary disk pool is the one you want to retain; nbdevconfig deletes the secondary disk pool after the merge. nbdevconfig –mergedps –stype server_type -primarydp

disk_pool_name -secondarydp disk_pool_name

3

Change the state of the primary disk pool to UP. The following is the command syntax: nbdevconfig -changestate -stype server_type -dp disk_pool_name

-state UP

The nbdevconfig command resides in the following directory: UNIX: /usr/openv/netbackup/bin/admincmd Windows: install_path\Program Files\VERITAS\NetBackup\bin\admincmd For more information, see NetBackup Commands for UNIX and Linux or NetBackup Commands for Windows.

Deleting a disk pool If you delete a disk pool, NetBackup removes it from your configuration.

If a disk pool is the storage destination of a storage unit, you must first delete

the storage unit.

Caution: Do not delete a disk pool that contains unexpired NetBackup images; if you do, data loss may occur.

Managing OpenStorage Managing disk pools

To delete a disk pool 1

In the NetBackup Administration Console tree, select Media and Device Management > Devices > Disk Pools.

2

Select a disk pool

3

Click Edit > Delete.

4

In the Delete Disk Pool dialog box, verify that the disk pool is the one you want to delete and then click OK.

Obtaining disk pool and volume status Use the NetBackup nbdevquery command to obtain the status of NetBackup disk pools and volumes in those disk pools. Table 6-1

nbdevquery disk pool options

Option

Description

-dv disk_volume

Used with -listdv, it shows the properties of the specified disk volume.

-l

Produces the parsable output, one line of output per disk volume with no headers. The first field indicates the version of the output as an aid to create scripts. By default, nbdevquery uses the -l option.

-listdp

Shows all disk pools. To show the properties of a specific disk pool, also use the -dp disk_volume option.

-listdv

Shows a summary of all disk volumes. To show the properties of a specific disk volume, also use the -dv disk_volume option.

-stype server_type

Use this option with the following two options: ■

With -listdp, shows all disk pools of the specified storage type.

■

With -listdv, shows all disk pools of the specified storage type and their disk volumes.

For OpenStorage, the storage vendor provides the string that identifies the server type.

-U

Produces an output format that is more human-readable.

43

44 Managing OpenStorage

Managing OpenStorage server credentials

Table 6-1

nbdevquery disk pool options

Option

Description

-D

Produces an output format that provides more information than the -U option but has less formatting.

Managing OpenStorage server credentials Use the NetBackup tpconfig utility to manage existing credentials in NetBackup. To list all OpenStorage credentials tpconfig –dsh –all_hosts

The command lists the media servers for which the storage server credentials are configured already for all OpenStorage servers. To list OpenStorage credentials for a specific type of storage server tpconfig –dsh –all_hosts –stype server_type

For the OpenStorage server type (server_type), the storage vendor provides the string that identifies the server type. To change the password credential for an OpenStorage storage server tpconfig -update -storage_server server_name -stype server_type

-sts_user_id user_id -password new_password

The server_name is the name of the OpenStorage storage server.

For the OpenStorage server type (server_type), the storage vendor provides the

string that identifies the server type.

Note: If the OpenStorage server logon credentials change, you must change the credentials on every NetBackup media server that connects to the storage server. To delete OpenStorage credentials for a storage server tpconfig -delete -storage_server server_name -stype server_type

-sts_user_id user_id

For the OpenStorage server type (server_type), the storage vendor provides the

string that identifies the server type.

The tpconfig command resides in the following directory:

UNIX: /usr/openv/volmgr/bin

Managing OpenStorage Managing storage servers

Windows: install_path\Program Files\VERITAS\Volmgr\bin For more information, see NetBackup Commands for UNIX and Linux or NetBackup Commands for Windows.

Managing storage servers For OpenStorage, a storage server is the disk appliance. The storage server owns

exclusive access to the storage.

You can do the following to manage the storage servers that exist in your

environment:

■

“Viewing storage servers” on page 45

■

“Deleting a storage server” on page 46

■

“Obtaining storage server status” on page 46

Viewing storage servers To view a list of storage servers already configured, use the nbdevquery command. To view configured storage servers ◆

Run the following nbdevquery command on the NetBackup master server: nbdevquery -liststs

The command lists all storage servers already configured.

To list only a specific OpenStorage server type, use the -stype server_type

option and argument. The storage vendor provides the string to use for

server_type.

The -U option provides more detailed information.

By default, NetBackup configures all media servers as BasicDisk storage servers.

Therefore, all media servers in your environment should appear as BasicDisk

servers, as in the following example:

nbdevquery -liststs

V6.5 tree.symantecs.org BasicDisk 5

V6.5 flower.symantecs.org BasicDisk 5

V6.5 water.symantecs.org BasicDisk 5

The nbdevquery command resides in the following directory: UNIX: /usr/openv/netbackup/bin/admincmd Windows: install_path\Program Files\VERITAS\NetBackup\bin\admincmd For more information, see NetBackup Commands for UNIX and Linux or NetBackup Commands for Windows.

45

46 Managing OpenStorage Managing storage servers

Deleting a storage server If you delete a storage server, NetBackup removes it from your configuration. If a disk pool is configured from the disk volumes that the storage server manages, you cannot delete the storage server. Caution: Do not delete a storage server if its storage contains unexpired NetBackup images; if you do, data loss may occur. To delete a storage server ◆

Use the following command: nbdevconfig -deletests -storage_server storage_server -stype server_type

The -storage_server storage_server is the storage server name. The storage vendor provides the string that identifies the server type (-stype). The nbdevconfig command resides in the following directory: UNIX: /usr/openv/netbackup/bin/admincmd Windows: install_path\Program Files\VERITAS\NetBackup\bin\admincmd For more information, see NetBackup Commands for UNIX and Linux or NetBackup Commands for Windows.

Obtaining storage server status The NetBackup nbdevquery command lets you obtain the status of storage servers.

Table 6-2

nbdevquery storage server options

Option

Description

-liststs

Shows all storage servers.

-storage_server server_name

Shows the information about the specified storage server. Must be used with the -liststs option.

Managing OpenStorage Managing OpenStorage data movers

Table 6-2

nbdevquery storage server options

Option

Description

-stype server_type

Use this option with the following two options: ■

With -liststs, shows all storage servers of the specified storage type.

■

With -storage_server, shows all storage servers that are at the specified host.

For OpenStorage, the storage vendor provides the string that identifies the server type.

For more information about the nbdevquery command, see the NetBackup Commands for UNIX and Linux or NetBackup Commands for Windows manual.

Managing OpenStorage data movers In OpenStorage, NetBackup media servers function as the data movers. A data mover is an entity that moves data between the primary storage (the NetBackup client) and the storage server. For an existing OpenStorage environment in NetBackup, you can: ■

Retire a media server as a data mover. See “To retire an OpenStorage data mover” on page 47.

■

Add a media server as a data mover. See “To add an OpenStorage data mover” on page 48.

To configure a media server as a data mover, see: ■

“Installing the vendor’s OpenStorage plug-in” on page 20

■

“Adding storage server credentials” on page 25

To retire an OpenStorage data mover 1

For every storage unit that specifies that data mover (that is, media server), clear the checkbox that specifies the media server. This step is not required if the storage unit is configured to use any available media server.

2

Delete the credentials on the media server to be retired. The following is the command syntax: tpconfig -delete -storage_server server_name -stype server_type

-sts_user_id user_id

The following describe the options that require arguments: ■

-storage_server server_name. The host name of the storage server.

47

48 Managing OpenStorage

Monitoring storage capacity and usage

■

-stype server_type. A string that identifies the storage server type. The storage vendor provides the string.

■

-sts_user_id user_id. The user name to use to log into the storage server. If the storage server does not require logon credentials, enter dummy credentials.

If the host failed and is unavailable, you can use the tpconfig device configuration utility in menu mode to delete the credentials. However, you must run the tpconfig utility on a UNIX or Linux NetBackup server. For procedures, see the NetBackup Administrator’s Guide for UNIX and Linux, Volume II. To add an OpenStorage data mover 1

Install and configure the NetBackup media server software. For procedures, see the NetBackup Installation Guide for UNIX and Linux or the NetBackup Installation Guide for Windows.

2

Install the OpenStorage vendor software plug-in on the media server For procedures, see “Installing the vendor’s OpenStorage plug-in” on page 20.

3

Connect the NetBackup media server to the OpenStorage appliance.

4

Create the storage server logon credentials on the media server. For procedures, see “Adding storage server credentials” on page 25.

5

Verify that the new media server appears in every storage unit that points to a disk pool on that OpenStorage disk appliance. The storage unit dialog box includes a media servers list. For every storage unit that is configured to use any available media server, the new data mover is allowed access to the storage server automatically.

6

For every storage unit that specifies Use one of the following media servers, update the storage unit so it uses the correct data movers. This step is not required if the storage unit is configured to use any available media server.

Monitoring storage capacity and usage To monitor storage capacity and usage, see: ■

The NetBackup Disk Pool status report. For more information, see “Viewing disk reports” on page 49.

■

Media and Device Management > Devices > Disk Pools.

Managing OpenStorage Viewing disk reports

■

The NetBackup License Keys dialog box. Open the dialog box by selecting Help > License Keys in the NetBackup Administration Console. Display the summary by clicking Summary of active capacity-based license features. The summary displays the storage capacity for which you are licensed and the capacity used. It does not display the amount of physical storage space.

The NetBackup Operations Manager also provides information about storage capacity and usage. For more information, see the NetBackup Operations Manager Guide.

Viewing disk reports The NetBackup disk reports include information about the disk pools, disk storage units, disk logs, images that are stored on disk media, and storage capacity. To view disk reports 1

In the NetBackup Administration Console tree, expand NetBackup Management > Reports > Disk Reports.

2

Select the name of a disk report.

3

In the right pane, select the report settings.

4

Click Run Report.

Table 6-3 shows the disk reports.

Table 6-3

Disk reports

Report

Description

Images on Disk

The Images on Disk report generates the image list present on the disk storage units that are connected to the media server. The report is a subset of the Images on Media report; it shows only disk-specific columns. The report provides a summary of the storage unit contents. If a disk becomes bad or if a media server crashes, this report can let you know what data is lost.

Disk Logs

The Disk Logs report displays the media errors or the informational messages that are recorded in the NetBackup error catalog. The report is a subset of the Media Logs report; it shows only disk-specific columns.

49

50 Managing OpenStorage

Viewing NetBackup logs

Table 6-3

Disk reports

Report

Description

Disk Storage Unit

The Disk Storage Unit Status report displays the state of disk storage units in the current NetBackup configuration. For disk pool capacity, see Media and Device Management > Devices > Disk Pools. Multiple storage units can point to the same disk pool. When the report query is by storage unit, the report counts the capacity of disk pool storage multiple times.

Disk Pool Status

The Disk Pool Status report displays the state of disk pool storage units. This report displays only when an Enterprise Disk Option license is installed.

Viewing NetBackup logs You can monitor NetBackup disk-related activity and status by viewing the NetBackup log files. Some NetBackup commands or processes write messages to their own log files. Other processes use Veritas unified log (VxUL) files. VxUL uses a standardized name and file format for log files. An originator ID (OID) identifies the process that writes the log messages. For information about the logs, see Table 6-4 Messages that begin with a sts_ prefix relate to the interaction with the storage vendor software plug-in. Most interaction occurs on the NetBackup media servers. Table 6-4

NetBackup logs

Activity

VxUL OID

Processes that use the ID

Backups and restores

N/A

Messages appear in the log files for the following processes: ■

bpbrm backup and restore manger

■

bpdbm database manager

■

bpdm disk manager

■

bptm for I/O operations

Backups and restores

117

The nbjm job manager.

Device configuration

111

The nbemm process.

Managing OpenStorage Troubleshooting OpenStorage

Table 6-4

NetBackup logs

Activity

VxUL OID

Processes that use the ID

Device configuration

178

The Disk Service Manager process that runs in the Enterprise Media Manager (EMM) process.

Device configuration

202

The Storage Server Interface process that runs in the Remote Manager and Monitor Service. RMMS runs on media servers. If the Storage Server Interface logs indicate problems with the Veritas Frozen Image (VxFI) service, examine the VxFI log files for detailed trace information:

Device configuration

230

■

UNIX: /user/openv/netbackup/logs/bpfis

■

Windows: install_path\VERITAS\NetBackup\logs \bpfis

The Remote Disk Service Manager interface (RDSM) that runs in the Remote Manager and Monitor Service. RMMS runs on media servers.

To view and manage VxUL log files, you must use NetBackup log commands. For information about how to use and manage logs on NetBackup servers, see the NetBackup Troubleshooting Guide.

Troubleshooting OpenStorage To troubleshoot back up and restore problems, you must determine if a problem resides in the vendor's plug-in, in the storage server, or in NetBackup. Examine the bpdm and the bptm log files for the messages that contain a sts_ prefix, which indicate a call to a plug-in. For more help, see the following topics: ■

“Vendor plug-in errors” on page 51

■

“Vendor plug-in not installed” on page 52

■

“Unable to access storage” on page 52

Vendor plug-in errors Vendor plug-ins may provide error codes or messages to NetBackup. If so, NetBackup logs a message about the error, primarily in the bptm and the bpdm log files on the NetBackup media server. Examine the log files for any lines that contain “sts_” or “stspi_” strings; these identify calls to vendor plug-in software.

51

52 Managing OpenStorage Troubleshooting OpenStorage

Vendor plug-in not installed If a storage unit uses a media server on which the vendor plug-in is not installed, jobs fail with NetBackup status code 174. Usually, this problem occurs only if the plug-in was removed from the media server after initial configuration. The following are examples of the messages that appear. Messages may not appear consecutively in the log file. Critical bptm (pid=13908) sts_get_server_prop_byname failed: error

2060009 object not claimed by a plug-in

Critical bptm (pid=13908) bp_sts_open_server failed: error 2060009

object not claimed by a plug-in

media manager - system error occurred (174)

Unable to access storage If NetBackup cannot access the storage, one possible cause is that the storage

server was created with the incorrect nbdevconfig -st value. For example, a

value of 9 (typical for OpenStorage) is the wrong value for an AdvancedDisk

storage server (typically 5).

For information about the storage server values, see “Creating a storage server

in NetBackup” on page 23.

To determine the configured value, use the following nbdevquery command:

nbdevquery -liststs –U

The following output shows the storage. The storage type is incorrect for

AdvancedDisk, but may be correct for OpenStorage.

Storage Server : daily

Storage Server Type : AdvancedDisk

Storage Type : Formatted Disk, Network Attached

To resolve an incorrect storage type problem 1

Delete all storage units that use disk pools that use the storage server.

2

Delete all disk pools that use the storage server.

3

Delete the storage server.

4

Recreate the storage server.

5

Recreate the disk pools.

6

Recreate the storage units.

Section

SharedDisk option

■

“Introduction” on page 55

■

“Preparing the SAN and the array” on page 57

■

“Licensing SharedDisk” on page 63

■

“Configuring SharedDisk” on page 65

■

“Managing SharedDisk” on page 81

II

54

Chapter

7

Introduction NetBackup SharedDisk allows multiple NetBackup media servers to share disk array storage. NetBackup aggregates the disk into pools of storage you can use for backups. NetBackup manages the storage as a logical entity (a disk pool). For more information about SharedDisk, see: ■

“Overview” on page 55

■

“NetBackup Release Notes” on page 56

For information about how to configure and use SharedDisk, see:

■

“Preparing the SAN and the array” on page 57

■

“Licensing SharedDisk” on page 63

■

“Configuring SharedDisk” on page 65

■

“Managing SharedDisk” on page 81

Overview NetBackup SharedDisk provides the following benefits: ■

Deploy and use easily. NetBackup discovers the storage and uses familiar NetBackup storage units and backup policies to use the storage.

■

Increase storage unit capacity by adding disks. Only add what you need, when you need it, and then update the NetBackup disk pools. Logical units of storage span physical boundaries, so you do not have to create new NetBackup storage units or change the backup policies.

■

Balance load and performance. NetBackup balances backup jobs and storage usage among the media servers and disk pools. For each backup job, NetBackup chooses the least full disk volume and least used media server.

56 Introduction

NetBackup Release Notes

■

Job failover. Media server failures do not prevent backup or restore operations. If a media server fails, backup and restore activity is routed through another media server.

The terms that are used in SharedDisk include: ■

Data mover: An entity that moves data between the primary storage (the NetBackup client) and the storage server. In SharedDisk, NetBackup media servers function as data movers.

■

Storage server: An entity that writes data to and reads data from disk storage. A storage server is the entity that has a mount on the file system on the storage. In SharedDisk, NetBackup media servers function as both storage servers and data movers.

■

Disk volume: A logical unit of disk storage.

■

Disk pool: A collection of disk volumes that are administered as an entity.

■

Enclosure: A disk array. You can create a NetBackup disk pool from all of the storage in an enclosure or only some of the storage.

NetBackup Release Notes For information about supported systems and peripherals, limitations, and operational notes, see the NetBackup Release Notes.

Chapter

8

Preparing the SAN and the array Before you can configure and use the SharedDisk storage option, the SAN and the disk array must be configured and operational. If the array includes a management service or process, it must be operational also. HP CommandView EVA is an example of an array management service. Instructions for how to configure and manage disk arrays are beyond the scope of the NetBackup documentation. However, you must do the following to prepare the array so that NetBackup can discover the storage on the array and then use the storage: ■

Prepare the SAN by creating the necessary zones between the disk array and the HBAs on the media servers.

■

Configure the disk array by using vendor specific utilities.

■

Install the array software on NetBackup media servers.

The tasks for preparing the SAN and the array are separate from the tasks to install and configure NetBackup. A network administrator or storage administrator can prepare the array, and a NetBackup administrator can install and manage NetBackup.

Preparing the SAN Before you can configure and use the SharedDisk storage option, the SAN must be configured, zoned, and operational. Instructions for how to configure a SAN are beyond the scope of the NetBackup documentation. However, the following subsections explain what is required for the SAN.

58 Preparing the SAN and the array

Preparing the SAN

Zoning the SAN Symantec recommends that you create a backup storage zone that includes only the NetBackup media servers and the array. A backup storage zone prevents that traffic from using the bandwidth that may be required for other SAN activity. The HBA ports on the media servers must be hard or soft zoned to the array.

Installing HBAs for SharedDisk On the NetBackup media servers that share the storage, do the following: ■

Install the HBA in each media server that connects to the array.

■

Install the HBA vendor’s Fibre Channel drivers for the HBA.

■

Install the HBA vendor’s Fibre Channel utilities for the HBA if required.

If you use the NetBackup Fibre Transport option with SharedDisk storage, the Fibre Transport HBA requirements may affect your HBA configuration. For more information, see “Installing HBAs for Fibre Transport” on page 150.

Connecting the media servers and the array The disk array must be in the same SAN on which NetBackup media servers are installed. The operating systems of the NetBackup media server computers must recognize the array. The following are the major steps to connect the Fibre: ■

Connect a Fibre Channel HBA port on each NetBackup media server to a Fibre Channel switch port.

■

Connect the disk array to a Fibre Channel switch port.

■

Define the zones on the SAN so that the media server HBA ports and the disk array are in the same zone. You should configure SAN zones before you bind HBA ports. Doing so prevents possible corruption of data that may occur if multiple HBAs gain access to the same storage device.

■

Bind the media server HBA ports to the disk array volumes or LUNs. Use persistent bindings when you bind the ports to the LUNs. Note: When you bind the media server HBA ports to disk array volumes or LUNs, you must use persistent bindings. If you do not, NetBackup access to the array may fail, backups may not occur, and data may be lost. Exception: Persistent bindings are not required for Leadville drivers.

Preparing the SAN and the array Installing array software on media servers

Installing array software on media servers Install the array vendor’s command line interfaces on each NetBackup media server that shares the array. NetBackup uses the array vendor software to manage the storage. In some cases, NetBackup uses the command line interface to: ■

Configure the arrays

■

Mask and unmask the LUNs when a media server accesses the storage.

Note: All media servers that are connected to the array must be the same operating system type and use the same file system.

Which software and version to install For guidance about which vendor software and version to install on the NetBackup media servers, see TechNote 288176 (NetBackup Disk Array Setup) on the Symantec support Web site: http://entsupport.symantec.com/docs/288176

The TechNote also contains information about how to create host entries and

how to allocate LUNs for each supported disk array.

The Tech Note lets us update disk array information when support for new disk

arrays is added and supported array software versions change between

NetBackup releases.

Configuring the disk array To configure the disk array for NetBackup, you must: ■

Add array host entries

■

Allocate LUNs for NetBackup

■

Add LUN entries to the sd.conf file (Solaris only)

Use the vendor-specific tools to configure the array. Instructions for how to configure the array are beyond the scope of the NetBackup documentation. For guidance, see the following subsections.

Adding array host entries You must add host entries on the array so that the NetBackup media servers can access the array. Different array vendors use different names for the host

59

60 Preparing the SAN and the array Configuring the disk array

entries. In all cases, the host entries contain the following three key pieces of information: ■

The name of the host (that is, the name of the NetBackup media server host). The host name must be a valid IP host name. To be more specific, the name or friendly name of the host entry on the array must match the DNS name of the host. (A friendly name is a more human-readable name than a string used to identify a device or a host.)

■

The World Wide Port Name (WWPN) of the HBA port on the media server. The WWPN identifies the port through which you want the media server to access the array.

■

The type of host operating system (such as Solaris).

You must create an entry for each NetBackup media server that shares the array. If you cluster the NetBackup media servers, the host entries must be configured with the host names of the nodes (not the virtual names). NetBackup uses gethostname to identify the row in the array masking table to enable exclusive access to a LUN.

Guidance for adding host entries How to add host entries is beyond the scope of the NetBackup documentation. For guidance, see TechNote 288176 (NetBackup Disk Array Setup) on the Symantec support Web site: http://entsupport.symantec.com/docs/288176

The TechNote also contains information about how to allocate LUNs for each supported disk array and which version of the array vendor’s command line interfaces to install on the NetBackup media servers. The Tech Note lets us update disk array information when support for new disk arrays is added and supported array software versions change between NetBackup releases.

Allocating LUNs for NetBackup You must allocate LUNs on the array for use by NetBackup. To do so, use the following prefix when you name the LUNs: LUN prefix:

nbusd_

Use a meaningful suffix to complete each LUN name. For example, use the name of the NetBackup disk pool and perhaps a number to make the name unique.

Preparing the SAN and the array Configuring the disk array

Note: LUN names within an array must be unique; if they are not, you cannot create a NetBackup disk pool from the storage on the array. Symantec recommends that you use a unique name for each LUN that you allocate to NetBackup, even if the LUNs are on different arrays. If you merge disk pools later, each LUN name must be unique. Some arrays do not allow specific name prefixes. By default, NetBackup uses all of the LUNs for storage on those arrays. You can use only some of the LUNs for NetBackup storage. However, to format those LUNs and to create a disk pool from them is more difficult than for LUNs with the nbusd_ prefix.

Guidance for choosing LUNs NetBackup balances jobs and workload. NetBackup tries to fill disk volumes at the same rate. Therefore, Symantec recommends that volumes in a disk pool be of similar size and speed, as follows: ■

Do not include small volumes and large volumes in the same disk pool.

■

Do not include slow volumes and fast volumes in the same disk pool.

Guidance for naming LUNs How to name LUNs is beyond the scope of the NetBackup documentation. For guidance, see TechNote 288176 (NetBackup Disk Array Setup) on the Symantec support Web site: http://entsupport.symantec.com/docs/288176

The TechNote also contains information about how to create host entries and which version of the array vendor’s command line interfaces to install on the NetBackup media servers. The Tech Note lets us update disk array information when support for new disk arrays is added and supported software versions change between NetBackup releases.

Adding LUN entries to the sd.conf file Solaris systems only. On Solaris systems, add sufficient LUN entries to the sd.conf file to allow NetBackup to import new LUNs to the host dynamically. If the server is rebooted, most HBAs do not require the sd.conf file to be updated to show new devices. However, Veritas Frozen Image (VxFI) needs to import devices dynamically without a reboot. VxFI is the NetBackup component that manages access to the storage on the disk array. Therefore, you must

61

62 Preparing the SAN and the array Configuring the disk array

update the sd.conf file to allow additional LUN entries and then reboot the

host after you update the sd.conf file.

If problems occur when you format LUNs, Symantec recommends that you open

LUNs 0-15 on all targets (0-15). Also open LUNs 0-15 if NetBackup device

discovery does not discover the disk array storage.

Chapter

9

Licensing SharedDisk No special installation is required for the SharedDisk storage option. However: ■

The NetBackup master server and all NetBackup media servers that use the feature must be at NetBackup 6.5 or later.

■

You must activate the feature by entering the Flexible Disk Option license key on the NetBackup master server.

You may have one license key that activates NetBackup and all of your add-on products. Alternatively, you may have a separate license key for NetBackup and for each add-on product such as SharedDisk. When you choose the systems to use for the NetBackup master and media servers, be aware of the following: ■

All NetBackup media servers that connect to the disk array must be the same system type (such as all Solaris).

■

Do not include the master server or EMM server in the list of media servers that use the array. Data transfer consumes system resources and severely degrades EMM performance. (Normally, the EMM server runs on the master server, but it can run on any NetBackup media server.)

If you remove the Flexible Disk Option license key or if it expires: ■

You cannot create the disk pools or the storage units that use the disk pools.

■

NetBackup jobs that attempt to use the disk pools or the storage units that are based on the disk pools fail. The error message indicates that the feature is not licensed.

■

NetBackup does not delete the disk pools or the storage units that are based on the disk pools. You can use them if you enter a valid license key.

64 Licensing SharedDisk

Chapter

10

Configuring SharedDisk The following are the tasks to configure NetBackup to use SharedDisk: ■

“Specifying the mount point directory” on page 65

■

“Creating a storage server in NetBackup” on page 66

■

“Adding disk array logon credentials” on page 68

■

“Formatting the LUNs in a disk array” on page 70

■

“Creating a SharedDisk disk pool” on page 72

■

“Creating a storage unit” on page 75

■

“Creating a backup policy” on page 80

■

“Creating a backup policy” on page 80

If problems occur when you configure the SharedDisk storage option, see “SharedDisk troubleshooting checklist” on page 98.

Specifying the mount point directory By default, NetBackup uses nbushareddisk as the mount point for SharedDisk storage. The mount point is the directory on each media server where NetBackup mounts the file system on the disk array. You can specify a different mount point directory. The mount point must be the same on all NetBackup media servers that access the array. If you back up a media server that uses mount points to any disk storage that contains backup images, do not cross mount points. (The policy Cross mount points attribute specifies whether to cross mount points.) If the policy crosses mount points, the NetBackup backup images that reside on that disk storage are backed up. The NetBackup BasicDisk disk type and the Enterprise Disk Option disk types use mount points for disk storage.

66 Configuring SharedDisk Creating a storage server in NetBackup

To specify the mount point directory 1

In the NetBackup Administration Console, expand NetBackup Management > Host Properties.

2

Select Master Server in the tree pane.

3

In the Details pane, double-click on the name of the master server.

4

In the Master Server Properties dialog box, click SharedDisk in the tree pane.

5

Enter the default mount point for the file system on the disk array.

Creating a storage server in NetBackup A storage server is an entity that mounts the storage and writes data to and reads data from the disk storage. For SharedDisk, NetBackup media servers function as both storage servers and data movers. (A data mover moves data to be protected from primary storage to the storage server.) Create in this context means to configure as a storage server a NetBackup media server that connects to the array. In SharedDisk, multiple storage servers can exist. The storage servers share the storage equally. The array vendor’s command line interfaces must be installed on every NetBackup media server that functions as a storage server. Note: You must configure as a SharedDisk storage server every NetBackup media server that connects to the storage. The media server also must have the array vendor’s command line interfaces installed. Figure 10-1

SharedDisk storage servers

NetBackup media servers are both storage servers and data movers. Disk array CLIs are installed.

Disk array

Configuring SharedDisk Creating a storage server in NetBackup

To determine if a media server is configured as a storage server already ◆

Run the following nbdevquery command on the NetBackup master server: nbdevquery -liststs

The command lists all storage servers already configured. By default, NetBackup configures all media servers as BasicDisk storage servers. Therefore, all media servers in your environment should appear as BasicDisk servers, as in the following example: nbdevquery -liststs

V6.5 tree.symantecs.org BasicDisk 5

V6.5 flower.symantecs.org BasicDisk 5

V6.5 water.symantecs.org BasicDisk 5

If the media server does not appear in the command output as a SharedDisk storage server, configure the media server as a storage server. To create a SharedDisk storage server in NetBackup ◆

Run the following nbdevconfig command on the master server or on one of the media servers: nbdevconfig -creatests -storage_server storage_server -stype

SharedDisk [-st storage_type] -media_server media_server

The following are the options and arguments: ■

-storage_server storage_server is the name of a NetBackup media server that connects to the storage. The media server must have the array vendor’s command line interfaces installed.

■

-stype SharedDisk specifies the storage server type.

■

-st storage_type is a numeric value that specifies the server properties. For SharedDisk, the default is 6 (direct attached, raw disk). Required only if you want to use a value other than the default. The value is obtained by adding together the numeric values of the following properties. Whether the disk is formatted and how it is attached are mutually exclusive and complementary. ■

1 - formatted disk. The disk is formatted as part of the vendor-specific preparation; NetBackup does not format the disk.

■

2 - raw disk. The disk is not formatted; NetBackup formats the disk.

■

4 - direct attached. Direct attached means that the storage server and the media server are the same NetBackup host.

■

8 - network attached. Network attached means the storage server is physically distinct from the NetBackup media server. It does not imply LAN data movement nor does it preclude Fibre Channel as the transport for data movement.

67

68 Configuring SharedDisk Adding disk array logon credentials

■

-media_server media_server specifies the NetBackup media server that performs the operation. Use the same name as the storage server name.

The nbdevconfig command and the nbdevquery command reside in the following directory: UNIX: /usr/openv/netbackup/bin/admincmd Windows: install_path\Program Files\VERITAS\NetBackup\bin\admincmd For more information, see NetBackup Commands for UNIX and Linux or NetBackup Commands for Windows.

Adding disk array logon credentials You must enter the credentials that NetBackup uses to log into a disk array. If the array contains multiple, separately named processing units (storage processors), you must enter the credentials for each unit. The disk array must be installed and prepared before you add array logon credentials. Note: For EMC CLARiiON, by default NetBackup creates global scope administrative user credentials. To create local scope credentials, you must use the Navisphere security file (created by using the EMC naviseccli command). If the security file exists, NetBackup uses it; the security file can contain a global or local administrative user. If you use the security file, you still must add logon credentials in NetBackup. NetBackup uses the disk array host name you add because the array host name is not stored in the security file. To add disk array logon credentials 1

In the NetBackup Administration Console, expand Media and Device Management > Credentials.

2

Select Disk Array Hosts.

3

Click Actions > New > Disk Array Host.

Configuring SharedDisk Adding disk array logon credentials

4

Enter the host name in the dialog box.

5

In the Add Disk Array Host dialog box, add the credentials:

6

■

Credentials. Select the host type for the disk array.

■

Username. Enter the user name that NetBackup uses to log into the array.

■

Password. Enter the password that NetBackup uses to log into the array.

■

Confirm password. To confirm the password, re-enter the password that NetBackup uses to log into the array.

■

(Windows systems.) Port number. For the port number, select (or enter) the port number over which to communicate with the array. If no specific port is required, select or enter 0.

■

(UNIX systems.) Connect using port number. To use a specific port number to connect, select this option, then enter the port number over which to communicate with the array. If no specific port is required, select or enter 0.

After you add credentials, stop and then start the NetBackup services on: the NetBackup master server and on each NetBackup media server that accesses the disk array. You can use the NetBackup Administration Console

69

70 Configuring SharedDisk Formatting the LUNs in a disk array

Activity Monitor to stop and start the services. Alternatively, you can use the following commands in sequence: ■

UNIX: /usr/openv/netbackup/bin/bp.kill_all

/usr/openv/netbackup/bin/bp.start_all

■

Windows: install_path\VERITAS\Netbackup\bin\bpdown.exe

install_path\VERITAS\Netbackup\bin\bpup.exe

Formatting the LUNs in a disk array For SharedDisk storage, use the NetBackup nbshareddisk command to format the LUNs that NetBackup can use for storage. The nbshareddisk command invokes the format utility for the file system. By default, the nbshareddisk command discovers and formats only the LUNs that begin with the nbusd_ prefix. For the arrays that do not let you specify the nbusd_ LUN prefix for disk volumes, nbshareddisk discovers all of the LUNS on an array. To use only some of the LUNs on the array, format only those LUNs. “To format LUNs” on page 70 explains how to format all LUNs or only some of the LUNs. If you format only some of the LUNs, you must use the volumes method when you create a disk pool. With the volumes method, you select disk volumes rather than the entire array. For more information, “Creating a SharedDisk disk pool” on page 72. Caution: This procedure displays all LUNs on an array that are allocated to NetBackup, even LUNs already in use by NetBackup. Do not format LUNs that are already in use by NetBackup; if you do, data loss may occur. The nbshareddisk command resides in the following directory: UNIX: /usr/openv/netbackup/bin/admincmd Windows: install_path\Program Files\VERITAS\NetBackup\bin\admincmd To format LUNs Invoke the nbshareddisk command on one of the storage servers that is connected to the array. 1

Use the nbshareddisk command with the list option to determine the arrays for which NetBackup has logon credentials. The output includes the unique enclosure identifier (UEID), which identifies arrays. The UEID of the array is used in step 2.

nbshareddisk list

Configuring SharedDisk Formatting the LUNs in a disk array

Enclosure list:

Vendor Array Name Enclosure ID

------------------------------------------------------------------NETAPP ndmpfiler1 UEID##NETAPP##LUN##0a505b7c HP HPEVA4000 UEID##HP##HSV##5000-1FE1-5007-0020 EMC 000182601092 UEID##EMC##SYMMETRIX##000182601092 EMC APM00044701641 UEID##EMC##CLARIION##APM00044701641

If the array does not appear in the list, see “6. Verify LAN connectivity to the disk array” on page 101. 2

Use the nbshareddisk list command to write the unique device identifiers (UDIDs) of the LUNs to a text file. The following is the command syntax:

nbshareddisk list –ueid unique_enclosure_id > filename

The command writes only LUNs that have the nbusd_ prefix to the file. If the array does not let you specify the nbusd_ LUN prefix, all LUNs appear in the output file. The UDIDs are used when you format the LUNs in step 5.

For example, the following command writes the UDID of the LUNs in the

specified enclosure to file formatlist.txt:

nbshareddisk list –ueid UEID##HP##HSV##5000-1FE1-5007-0020 >

formatlist.txt

3

To add UDIDs from more than one array to the output file, repeat step 2 for each additional array. However, use the append operator (>>) rather than the redirection operator to append the output to the end of the file.

4

Examine the text file to verify that the LUNs in the file are the ones you want to format. If you do not see all of the UDIDs you expected to, ensure that the LUNs on the array use the nbusd_ prefix. For arrays that do not allow the nbusd_ LUN prefix, delete the UDIDs that you do not want to format. Only delete lines from the file, do not add lines to the file. Caution: Do not format LUNs that are in use by NetBackup already; if you do, data loss may occur.

5

Use the nbshareddisk format command to format the LUNs on the array. The following is the command syntax: nbshareddisk format –udid_file filename

Other options are: ■

-fstype native | vxfs. Format the LUNs with file system native to the media server operating system or the Veritas File System. The default is native.

71

72 Configuring SharedDisk Creating a SharedDisk disk pool

-noPrompt. Suppresses the format prompt. If you format more than one UDID, the nbshareddisk command prompts you to format each one. Because the format process may be time-consuming, you can use the -noPrompt option to suppress the prompt. Then, you do not have to monitor the formatting process. However, use the -noPrompt option with caution. For example, the following command reads the UDIDs from the formatlist.txt file. It then formats the disk volumes with the Veritas File System:

■

nbshareddisk format –udid_file formatlist.txt –fstype vxfs

After you format the LUNs, you can create disk pools.

Creating a SharedDisk disk pool A SharedDisk disk pool represents LUNS on a disk array that are allocated to NetBackup. NetBackup aggregates the LUNs into pools of storage you can use for backups. Figure 10-2

SharedDisk disk pools

LUNs

Gold_SharedDisk_Pool Disk array

Silver_SharedDisk_Pool

A disk pool is the storage destination of a NetBackup storage unit. Two methods exist to create SharedDisk disk pools: ■

The enclosure method creates one disk pool from all of the storage that is allocated to NetBackup on one array. This method is the easiest to accomplish. It also is easier to add volumes to the disk pool later.

■

The volumes method lets you create a disk pool by selecting specific disk volumes. The disk volumes can be in one enclosure or in multiple enclosures. However, adding volumes later is more difficult than for disk pools created by the enclosure method.

Configuring SharedDisk Creating a SharedDisk disk pool

Note: If the array does net let you specify the nbusd_ LUN prefix for disk volumes, NetBackup discovers all of the storage on the array. To use only some of the storage on the array, you must use the volumes method to create a disk pool. Which process you use affects how you add volumes to that disk pool in the future. Therefore, you should note which method you use for each disk pool you create. When you create a disk pool, you specify: ■

The NetBackup media servers that share the storage. The media servers must be configured as storage servers. They also function as data movers.

■

The disk array that contains the storage (enclosure method) or the disk volumes on the array(s) to include in the disk pool (volumes method)

■

The disk pool properties. Properties include the name, the high water mark, the low water mark, and a comment that describes the disk pool. For more information, see “Disk pool properties” on page 82.

Symantec recommends that disk volume names and disk pool names be unique

across your enterprise.

Before you create a SharedDisk disk pool, LUNs on the disk array must be

allocated for use by NetBackup. The LUNs must be formatted.

When NetBackup sends backup data to a disk pool, NetBackup selects disk volumes based on available capacity and predicted size of the backup. NetBackup tries to write backup data to a single volume. If necessary, backup images span disk volumes in a disk pool. Backup images do not span across multiple disk pools.

Enclosure method of SharedDisk disk pool creation The enclosure method creates one SharedDisk disk pool from the LUNs that have

the nbusd_ prefix on the enclosure. A one-to-one mapping exists between the

array storage that is allocated to NetBackup and the disk pool. The enclosure

name becomes the disk pool name.

For the arrays that do not let you specify the nbusd_ prefix, NetBackup creates

a disk pool from all of the LUNs on the array.

Use the Disk Pool Configuration Wizard to create a disk pool from an enclosure.

To create a SharedDisk disk pool from an enclosure 1

In the NetBackup Administration Console tree, select the master server or Media and Device Management.

73

74 Configuring SharedDisk

Creating a SharedDisk disk pool

2

From the list of wizards in the Details pane, click Configure Disk Pool and follow the wizard instructions.

For help, see the Disk Pool Configuration Wizard online help.

Volumes method of SharedDisk disk pool creation With the volumes method, you create a disk pool by specifying the disk volumes to include in the disk pool. The disk volumes can be in one enclosure or in multiple enclosures. You can use this method to create: ■

More than one disk pool from an enclosure.

■

A disk pool that spans enclosures.

Also, you can specify a name for the disk pool (unlike the enclosure disk pool

creation method). However, disk pool expansion is more difficult than with the enclosure method. If you cannot use the nbusd_ prefix to name LUNs, the volumes method lets you specify only some of the storage on a disk array. To use the volumes method to create a disk pool 1

On a SharedDisk storage server, preview the volumes that the storage server detects and write the output to a file. The output file includes both formatted volumes and unformatted volumes for all arrays that connect to the storage server. The file is used as input when you create the disk pool. The following is the command syntax: nbdevconfig –previewdv –storage_server storage_server –stype

SharedDisk -media_server media_server > filename

The following are the options:

■

-storage_server storage_server specifies the storage server name.

■

-stype SharedDisk specifies the storage server type.

-media_server media_server specifies the media server that

performs the operation. Use the same name as the storage server. For example, the following command creates a file of volumes named Gold_Volumes.txt from volumes detected by storage server A: ■

nbdevconfig –previewdv –storage_server A –stype SharedDisk -media_server A > Gold_Volumes.txt

2

Edit the file of volume names; remove the volumes that you do not want in the disk pool. Ensure that the volumes you want to use are formatted. To create multiple disk pools, make a copy of the file for each disk pool you want to create. Name each file so that it identifies each disk pool. Edit the

Configuring SharedDisk Creating a storage unit

files so each one contains only those volumes you want in each disk pool. Use those files as the inputs in step 3. 3

Create a disk pool from the volumes that are listed in the file. The following is the command syntax: nbdevconfig –createdp –dp disk_pool_name –storage_servers

storage_server [storage_server ...] –stype SharedDisk –dvlist

filename

The following are the options: ■

-dp disk_pool_name specifies the disk pool.

■

-storage_servers storage_server specifies the storage servers. Specify all of the servers that share the disk pool.

■

-stype SharedDisk specifies the storage server type.

-dvlist filename specifies the file of volume names. For example, the following command creates a Gold_SharedDisk_Pool disk pool. Servers A, B, and C are the storage servers for the disk pool. The file that contains the list of disk volumes is Gold_Volumes.txt. ■

nbdevconfig –createdp –dp Gold_SharedDisk_Pool –storage_servers A B C –stype SharedDisk –dvlist Gold_Volumes.txt

You also can specify other options, as follows:

4

■

-comment, a comment that describes the disk pool.

■

-hwm, the high water mark (the default is 98%)

■

-lwm, the low water mark (the default is 80%)

■

-M, the master server (the default is the current master server)

■

-media_server server_name, the storage server that performs the

operation

To create multiple disk pools, repeat step 3 for each disk pool you want to create. Each disk pool must have a separate input file. The disk pool volumes must be unique; that is, a volume cannot appear in more than one input file.

The nbdevconfig command resides in the following directory: UNIX: /usr/openv/netbackup/bin/admincmd Windows: install_path\Program Files\VERITAS\NetBackup\bin\admincmd For more information, see NetBackup Commands for UNIX and Linux or NetBackup Commands for Windows.

Creating a storage unit Create one or more storage units that reference the disk pool.

The Disk Pool Configuration Wizard lets you create a storage unit; therefore,

you may have created a storage unit when you created a disk pool. To determine

75

76 Configuring SharedDisk

Creating a storage unit

if storage units exist for the disk pool, see the NetBackup Management >

Storage > Storage Units window of the Administration Console.

For disk pool storage unit recommendations, see “Usage recommendations” on

page 79.

To create a storage unit from the Actions menu 1

In the NetBackup Administration Console, select NetBackup Management > Storage > Storage Units.

2

Click Actions > New > Storage Unit.

To restrict access to specific media servers, select them here

3

Complete the fields in the New Storage Unit dialog box.

The following are the configuration options for a disk pool storage unit. Storage unit name Enter a unique storage unit name for the new storage unit. The name can describe the type of storage. The storage unit name is the name used to specify a storage unit for policies and schedules. The storage unit name cannot be changed after creation.

Configuring SharedDisk Creating a storage unit

Storage unit type Select Disk as the storage unit type. Disk type For a SharedDisk storage unit, select SharedDisk. Disk pool Select the disk pool that contains the storage for this storage unit. All disk pools of the specified Disk type appear in the Disk pool list. If no disk pools are configured, no disk pools appear in the list. To specify or change the properties of the disk pool, click Properties and then do the following: ■

Select or enter the high water mark for the disk pool. (The default is 98%.) The high water mark is a threshold that indicates the storage is full. It applies to both the individual disk volumes in the pool and the disk pool, as follows: ■

Individual volumes. When a disk volume reaches the high water mark, NetBackup writes the data to another disk volume in the pool.

■

Disk pool. When all volumes are at the high water mark, the disk pool is full. When a disk pool approaches the high water mark, NetBackup reduces the number of jobs that are allowed to write to the pool. NetBackup does not assign new jobs to a storage unit in which the disk pool is full.

■

Select or enter the low water mark for the disk pool. (The default is 80%.) When the capacity of the disk pool returns to the low water mark, NetBackup again assigns jobs to the storage unit. Capacity is regained as backup images expire. The low water mark setting cannot be greater than or equal to the high water mark setting.

■

Enter a comment that is associated with the disk pool.

Media server

The Media server setting specifies the NetBackup media servers that can move

data to and from the disk pool for this storage unit. Only the media servers that

are configured as storage servers appear in the media servers list.

The NetBackup media servers on which the disk array vendor’s software are

installed function as both storage servers and data movers. If a server does not

appear in the list, verify that the logon credentials are created.

Specify the media server or servers as follows:

■

To allow any server in the media server list to access the disk storage (default), select Use any available media server.

77

78 Configuring SharedDisk Creating a storage unit

■

To restrict the media servers that can access the disk storage, select Only use the following media servers. Then, select the media servers to allow. The selection list includes only the media servers that are configured as storage servers for the disk pool.

NetBackup selects the media server to use when the policy runs. Maximum concurrent jobs

The Maximum concurrent jobs setting specifies the maximum number of jobs

that NetBackup can send to a disk storage unit at one time. (Default: 1 job. The

job count can range from 0 to 256.) This setting corresponds to the Maximum

concurrent write drives setting for a Media Manager storage unit.

NetBackup queues jobs until the storage unit is available. If three backup jobs

are ready to be sent to the storage unit and Maximum concurrent jobs is set to

two, the first two jobs start and the third job waits. If a job contains multiple

copies, each copy applies toward the Maximum concurrent jobs count.

The number to enter depends on the available disk space and the server's ability

to run multiple backup processes.

You can use maximum concurrent jobs to balance the load between disk storage

units. A higher number of concurrent jobs means that the disk can be busier

than if the number is lower.

Caution: A Maximum concurrent jobs setting of 0 disables the storage unit. For information about how NetBackup balances storage unit and media server load, see “Maximum concurrent jobs” in: ■

NetBackup Administrator’s Guide for UNIX and Linux, Volume I

■

NetBackup Administrator’s Guide for Windows, Volume I

Maximum fragment size Specify the largest fragment size that NetBackup can create to store backups.

The default maximum fragment size for a disk storage unit is 524,287

megabytes. To specify a maximum fragment size other than the default, enter a

value from 20 megabytes to 524,287 megabytes.

Backups to disk are usually fragmented to ensure that the backup does not

exceed the maximum size that the file system allows.

If an error occurs in a backup, the entire backup is discarded. The backup

restarts from the beginning, not from the fragment where the error occurred.

(An exception is for backups for which checkpoint and restart is enabled. In that

case, fragments before and including the last checkpoint are retained; the

fragments after the last checkpoint are discarded.)

Configuring SharedDisk Creating a storage unit

Usage recommendations For usage recommendations, see the following:

Multiple storage units You can use multiple storage units for one disk pool to separate your backup traffic and still write all data to the same disk pool. You do not need to partition the storage because all storage units use the same pool of storage. Example 1 For example, if you use the NetBackup Fibre Transport option, you can separate the NetBackup SAN client traffic from the regular NetBackup client traffic in your environment: ■

Define a storage unit (such as STU-FT). Select the disk pool. Select Only use the following media servers. Select the FT media servers that connect to the SAN clients.

■

Create a backup policy for the SAN clients and select the STU-FT storage unit.

■

Define another storage unit (such as STU-LAN). Select the same disk pool. Select Only use the following media servers. Select the media servers with LAN connectivity to the regular clients.

■

Create a backup policy for the regular clients and select the STU-LAN storage unit.

This scenario assumes that the SAN clients are a small subset of your client base. It also assumes that the media servers with LAN connectivity to the regular clients also have SAN connectivity to the storage. Example 2 Even without a SAN, you can separate your backup traffic similarly and still write all of the data to the same disk pool. For example, you can send the backups from your most important clients to a media server that is dedicated for the most important backups: ■

Define a storage unit (such as STU-CRITICAL). Select the disk pool. Select Only use the following media servers. Select one (or a subset) of the media servers.

■

Create a backup policy for the critical clients and select the STU-CRITICAL storage unit.

■

Define another storage unit (such as STU-NORMAL). Select the same disk pool. Select Only use the following media servers. Select a different subset of the media servers.

79

80 Configuring SharedDisk

Creating a backup policy

■

Create a backup policy for the regular clients and select the STU-NORMAL storage unit.

Maximum concurrent job setting You can use the multiple concurrent jobs settings on storage units to assign backup priority for important clients. For example, two storage units use the same set of media servers. One of the storage units has a higher concurrent job setting than the other. More client backups occur for the storage unit with the higher concurrent job setting.

Creating a backup policy Backup policies define the rules that NetBackup follows to back up clients. Use normal NetBackup processes to configure backups to SharedDisk storage units. That is, specify the appropriate storage unit in your backup policies. Alternatively, specify a lifecycle policy that uses an OpenStorage storage unit as the backup or duplication destination. To create a policy, see “Policies” in the NetBackup Administrator’s Guide for UNIX and Linux, Volume I or the NetBackup Administrator’s Guide for Windows, Volume I. Monitor backup progress To monitor backup progress, use the Detailed Status tab of the Job Details dialog box. It shows the media server that functions as the data mover between the client and the storage server. If the media server cannot start or complete the job, NetBackup retries the job after the job retry period elapses. (Configure the job retry interval by using the master server Global Attributes Job retry delay host property.) If you select more than one media server in the storage unit Media server field, NetBackup may retry the job with a different media server.

Restores Use normal NetBackup processes to restore data from backups.

To perform the restore, NetBackup chooses one of the media servers that can

move data to and from the disk pool.

Chapter

11

Managing SharedDisk The following are tasks to manage the SharedDisk storage option: ■

“Managing disk pools” on page 81

■

“Managing disk array logon credentials” on page 91

■

“Managing storage servers” on page 92

■

“Monitoring storage capacity and usage” on page 95

■

“Viewing disk reports” on page 96

■

“Viewing NetBackup logs” on page 97

■

“Troubleshooting SharedDisk” on page 98

Managing disk pools The following are tasks to manage disk pools: ■

“Changing disk pool properties” on page 81

■

“Adding volumes to a SharedDisk disk pool” on page 83

■

“Changing disk pool or volume state” on page 87

■

“Merging disk pools” on page 88

■

“Deleting a disk pool” on page 89

■

“Obtaining disk pool and volume status” on page 90

Changing disk pool properties You can change the high and the low water marks of a disk pool and change the

comment that is associated with the disk pool.

You also can add media servers that are allowed to access the disk pool.

82 Managing SharedDisk Managing disk pools

To change disk pool properties 1

In the NetBackup Administration Console tree, select Media and Device Management > Devices > Disk Pools.

2

Select the disk pool you want to change in the details pane.

3

Click Edit > Change.

4

In the Change Disk Pool dialog box, change properties.

Disk pool properties The following are the disk pool properties: ■

The disk pool name.

■

The media servers that connect to the disk array. All media servers must be the same system type (such as all Solaris).

■

The total amount of space available in the disk pool.

■

The total raw, unformatted size of the storage in the disk pool.

■

The number of volumes in the disk pool.

Managing SharedDisk Managing disk pools

■

A comment that is associated with the disk pool.

■

The high water mark for the disk pool. (The default is 98%.) The high water mark is a threshold that indicates the storage is full. It applies to both the individual disk volumes in the pool and the disk pool, as follows:

■

■

Individual volumes. When a disk volume reaches the high water mark, NetBackup writes the data to another disk volume in the pool.

■

Disk pool. When all volumes are at the high water mark, the disk pool is full. When a disk pool approaches the high water mark, NetBackup reduces the number of jobs that are allowed to write to the pool. NetBackup does not assign new jobs to a storage unit in which the disk pool is full.

The low water mark for the disk pool. (The default is 80%.) When the capacity of the disk pool returns to the low water mark, NetBackup again assigns jobs to the storage unit. Capacity is regained as backup images expire. The low water mark setting cannot be greater than or equal to the high water mark setting.

Adding volumes to a SharedDisk disk pool If your storage administrator allocates more LUNs in an array to NetBackup, you must add those volumes to a disk pool. NetBackup does not add those volumes to a SharedDisk disk pool automatically. (By default, NetBackup automatically increases disk pool capacity if the capacity of the underlying disk volumes increases. Similarly, NetBackup decreases the capacity of a disk pool if the underlying disk volume capacity decreases.) The NetBackup storage units that use the disk pool automatically use the additional storage capacity. You do not have to change the storage units. How you add volumes depends on how the disk pool was created: ■

If you used the enclosure method to create the disk pool, see “Adding volumes to a SharedDisk disk pool: enclosure method” on page 84.

■

If you used the volumes method to create the disk pool, see “Adding volumes to a SharedDisk disk pool: volumes method” on page 86.

83

84 Managing SharedDisk Managing disk pools

Note: The volumes must be allocated for NetBackup and they must be formatted. NetBackup does not allow volumes to be formatted after you add them to a disk pool. Also, NetBackup does not let you delete volumes after you add them to a disk pool. Therefore, if the volumes were not formatted, you cannot use them and cannot delete them from the disk pool. You must then delete the entire disk pool.

Note: Be careful when you add volumes to a disk pool. For data integrity, NetBackup does not allow volumes to be deleted from a disk pool. Because backup images may span disk volumes, a volume may contain valid image fragments. To remove a disk volume, you must delete all valid backup images and then delete the disk pool.

Adding volumes to a SharedDisk disk pool: enclosure method If you created a SharedDisk disk pool by the enclosure method, add volumes to the disk pool by inventorying the disk pool. The inventory: ■

Queries the disk array for volume information.

■

Displays the LUNs with the nbusd_ prefix in the Inventory Disk Pool dialog box. If the array does not allow specific LUN prefixes, the inventory discovers all LUNS on the array.

You can either update the configuration (that is, import the new disk volumes) or decline the update if it does not correctly show the actual configuration. To add SharedDisk volumes by using Inventory Disk Pool 1

In the NetBackup Administration Console tree, select Media and Device Management > Devices > Disk Pools.

Managing SharedDisk Managing disk pools

2

Click Actions > inventory Disk Pool.

3

In the Inventory Disk Pool dialog box, select the disk pool and then click Start Inventory. The default selection is the disk pool that was selected in the Administration Console.

4

To update the disk pool configuration with the new information, click Update Configuration. Update Configuration is enabled only after the inventory has completed. If the results do not correctly show the actual configuration, do not update the configuration. Do the following: ■

Verify that the new LUNs use the nbusd_ prefix.

■

Verify that the new LUNs are the size allocated by the storage administrator.

■

Use the nbshareddisk command to determine on which array the new LUNs reside.

85

86 Managing SharedDisk Managing disk pools

Adding volumes to a SharedDisk disk pool: volumes method If you created a SharedDisk disk pool by the volumes method, add volumes to the disk pool by using the nbdevconfig command. First, create a new, temporary disk pool and then merge it into the original disk pool. If you created a disk pool by the enclosure method, you can use the volumes method to expand the storage of the disk pool. However, you must then always use the volumes expansion method for future expansion. Use the NetBackup nbdevconfig command to merge disk pools. Invoke the commands from a NetBackup media server that is configured as a storage server. The following are the prerequisites: ■

Both disk pools must use the same set of NetBackup media servers to share the storage.

■

The volumes in the temporary disk pool must have different names than the volumes in the original disk pool.

■

All of the disk volumes must have the same file system.

■

The new disk volumes must be formatted.

To add SharedDisk volumes by using nbdevconfig 1

On a SharedDisk storage server, preview the volumes in an array and write the output to a file. The output file includes both formatted volumes and unformatted volumes. The file is used as input when you create the disk pool. The following is the command syntax: nbdevconfig –previewdv –storage_server storage_server –stype

SharedDisk -media_server media_server > filename

The following are the options: ■

-storage_server storage_server specifies the storage server.

■

-stype SharedDisk specifies the storage server type.

■

-media_server media_server specifies the media server that performs the operation. Use the same name as the storage server.

2

Edit the file created in the previous step and remove all but the new volumes. The file is used as the input when you create the disk pool.

3

Create a disk pool from the volumes that are listed in the file. The following is the command syntax: nbdevconfig –createdp –dp disk_pool_name –storage_servers

storage_server [storage_server ...] –stype SharedDisk –dvlist

filename

The following are the options:

■

-dp disk_pool_name specifies the disk pool.

Managing SharedDisk Managing disk pools

4

■

-storage_servers storage_server specifies the storage servers. Specify all of the servers that share the disk pool.

■

-stype SharedDisk specifies the storage server type.

■

-dvlist filename specifies the file of volume names.

Change the state of each disk pool to DOWN; the following is the command syntax: nbdevconfig -changestate -stype SharedDisk -dp disk_pool_name

-state DOWN

If backup jobs are assigned to a disk pool, the state change fails. Cancel the backup jobs or wait until the jobs complete. 5

Merge the disk pools. The following is the command syntax. The primary disk pool is the one you want to retain; nbdevconfig deletes the secondary disk pool after the merge. nbdevconfig –mergedps –stype SharedDisk -primarydp

disk_pool_name -secondarydp disk_pool_name

6

Change the state of the primary disk pool to UP. The following is the command syntax: nbdevconfig -changestate -stype SharedDisk -dp disk_pool_name

-state UP

The nbdevconfig command resides in the following directory: UNIX: /usr/openv/netbackup/bin/admincmd Windows: install_path\Program Files\VERITAS\NetBackup\bin\admincmd For more information, see NetBackup Commands for UNIX and Linux or NetBackup Commands for Windows.

Changing disk pool or volume state Pool and volume states are UP or DOWN. You can change the state of a disk pool

or volume.

To change the state to DOWN, the disk pool must not be busy. If backup jobs are

assigned to the disk pool, the state change fails. Cancel the backup jobs or wait

until the jobs complete.

Note: For data integrity, NetBackup does not allow volumes to be deleted from a disk pool. Because backup images may span disk volumes, a volume may contain valid image fragments. To remove a disk volume, you must delete all valid backup images and then delete the disk pool.

87

88 Managing SharedDisk Managing disk pools

To change the disk pool state by using the Device Monitor 1

In the NetBackup Administration Console, select Media and Device Management > Device Monitor.

2

Select the Disk Pools tab.

3

Select the disk pool.

4

Select either Actions > Up or Actions > Down.

To change the disk pool state by using the nbdevconfig command ◆

The following is the command syntax: nbdevconfig -changestate -stype SharedDisk -dp disk_pool_name

-state state

state is either UP or DOWN. To change the disk volume state 1

Determine the name of the disk volume. The following command lists all volumes in the specified disk pool: nbdevquery -listdv -stype SharedDisk -dp disk_pool_name

2

Change the disk volume state; the following is the command syntax: nbdevconfig -changestate -stype SharedDisk -dp disk_pool_name

–dv vol_name -state state

state is UP or DOWN.

NetBackup jobs still read from and write to a disk pool that has a downed

volume, but the downed volume is unavailable.

The nbdevconfig command and the nbdevquery command reside in the following directory: UNIX: /usr/openv/netbackup/bin/admincmd Windows: install_path\Program Files\VERITAS\NetBackup\bin\admincmd For more information, see NetBackup Commands for UNIX and Linux or NetBackup Commands for Windows.

Merging disk pools You can merge existing SharedDisk disk pools.

NetBackup updates the catalog records to show the correct location of the

backup images in those disk pools.

Note: After you merge SharedDisk disk pools, you must use the volumes method to add volumes to the disk pool. This restriction also applies if you used the enclosure method to create the disk pools.

Managing SharedDisk Managing disk pools

Prerequisites: ■

The volumes in the two disk pools must have unique names.

■

Both disk pools must use the same set of NetBackup media servers to share the storage.

■

If the secondary disk pool is referenced by storage units, you must delete those storage units.

To merge disk pools 1

Change the state of each disk pool to DOWN; the following is the command syntax: nbdevconfig -changestate -stype SharedDisk -dp disk_pool_name

-state DOWN

If backup jobs are assigned to a disk pool, the state change fails. Cancel the backup jobs or wait until the jobs complete. 2

Merge the disk pools. The following is the command syntax. The primary disk pool is the one you want to retain; nbdevconfig deletes the secondary disk pool after the merge. nbdevconfig –mergedps –stype SharedDisk -primarydp

disk_pool_name -secondarydp disk_pool_name

3

Change the state of the primary disk pool to UP. The following is the command syntax: nbdevconfig -changestate -stype SharedDisk -dp disk_pool_name

-state UP

The nbdevconfig command resides in the following directory: UNIX: /usr/openv/netbackup/bin/admincmd Windows: install_path\Program Files\VERITAS\NetBackup\bin\admincmd For more information, see NetBackup Commands for UNIX and Linux or NetBackup Commands for Windows.

Deleting a disk pool If you delete a disk pool, NetBackup removes it from your configuration.

If a disk pool is the storage destination of a storage unit, you must first delete

the storage unit.

Caution: Do not delete a disk pool that contains unexpired NetBackup images; if you do, data loss may occur.

89

90 Managing SharedDisk

Managing disk pools

To delete a disk pool 1

In the NetBackup Administration Console tree, select Media and Device Management > Devices > Disk Pools.

2

Select a disk pool

3

Click Edit > Delete.

4

In the Delete Disk Pool dialog box, verify that the disk pool is the one you want to delete and then click OK.

Obtaining disk pool and volume status Use the NetBackup nbdevquery command to obtain the status of NetBackup disk pools and volumes in those disk pools. Table 11-1

nbdevquery disk pool options

Option

Description

-dv disk_volume

Used with -listdv, it shows the properties of the specified disk volume.

-l

Produces the parsable output, one line of output per disk volume with no headers. The first field indicates the version of the output as an aid to create scripts. By default, nbdevquery uses the -l option.

-listdp

Shows all disk pools. To show the properties of a specific disk pool, also use the -dp disk_volume option.

-listdv

Shows a summary of all disk volumes. To show the properties of a specific disk volume, also use the -dv disk_volume option.

-stype server_type

Use this option with the following two options: ■

With -listdp, shows all disk pools of the specified storage type.

■

With -listdv, shows all disk pools of the specified storage type and their disk volumes.

Use SharedDisk for the server_type argument.

-U

Produces an output format that is more human-readable.

Managing SharedDisk Managing disk array logon credentials

Table 11-1

nbdevquery disk pool options

Option

Description

-D

Produces an output format that provides more information than the -U option but has less formatting.

Managing disk array logon credentials For SharedDisk storage, the currently configured disk array credentials are shown in the Media and Device Management > Credentials > Disk Array Hosts view. You can add, change, or delete the credentials that NetBackups uses to access the arrays in your NetBackup environment. To add array logon credentials 1

In the NetBackup Administration Console, expand Media and Device Management > Credentials.

2

Select Disk Array Hosts.

3

Click Actions > New > Disk Array Host.

4

Enter the host name in the dialog box.

5

In the New Disk Array Host dialog box, enter the credentials.

To change array logon credentials 1

In the NetBackup Administration Console, expand Media and Device Management > Credentials > Disk Array Host.

2

Select a disk array host.

3

Click Edit > Change.

4

In the Change Disk Array Host dialog box, change the credentials.

To delete array logon credentials 1

In the NetBackup Administration Console, expand Media and Device Management > Credentials > Disk Array Host.

2

Select a disk array host.

3

Click Edit > Delete. The disk array host is deleted; no confirmation dialog appears.

91

92 Managing SharedDisk Managing storage servers

Managing storage servers

For SharedDisk, NetBackup media servers function as both storage servers and

data movers. The storage servers share the storage equally.

You can do the following to manage the storage servers that exist in your

environment:

■

“Viewing storage servers” on page 92

■

“Adding a SharedDisk storage server” on page 93

■

“Removing a SharedDisk storage server from disk pool access” on page 93

■

“Deleting a storage server” on page 94

■

“Obtaining storage server status” on page 95

Viewing storage servers To view a list of storage servers already configured, use the nbdevquery command. To view configured storage servers ◆

Run the following nbdevquery command on the NetBackup master server: nbdevquery -liststs

The command lists all storage servers already configured.

To list only SharedDisk storage servers, use the -stype SharedDisk option

and argument.

The -U option provides more detailed information.

By default, NetBackup configures all media servers as BasicDisk storage servers.

Therefore, all media servers in your environment should appear as BasicDisk

servers, as in the following example:

nbdevquery -liststs

V6.5 tree.symantecs.org BasicDisk 5

V6.5 flower.symantecs.org BasicDisk 5

V6.5 water.symantecs.org BasicDisk 5

The nbdevquery command resides in the following directory: UNIX: /usr/openv/netbackup/bin/admincmd Windows: install_path\Program Files\VERITAS\NetBackup\bin\admincmd For more information, see NetBackup Commands for UNIX and Linux or NetBackup Commands for Windows.

Managing SharedDisk Managing storage servers

Adding a SharedDisk storage server You can add a SharedDisk storage server to an existing SharedDisk configuration. The NetBackup media server also becomes a data mover. To add a SharedDisk storage server 1

Install and configure the NetBackup media server software. For procedures, see the NetBackup Installation Guide for UNIX and Linux or the NetBackup Installation Guide for Windows.

2

Connect the NetBackup media server to the disk array. For procedures, see “Connecting the media servers and the array” on page 58.

3

Install the disk array software on the media server. For procedures, see “Installing array software on media servers” on page 59.

4

Add the media server to the host entry list on the disk array. For procedures, see “Adding array host entries” on page 59.

5

If no other storage servers were configured, you must change the state of all disk pools on the storage to UP. The following is the command syntax: nbdevconfig -changestate -stype SharedDisk -dp disk_pool_name

-state UP

6

Verify that the new media server appears in every storage unit that points to a disk pool on that disk array. The storage unit dialog box includes a media servers list.

7

For every SharedDisk storage unit that specifies Use one of the following media servers, update the storage unit so it uses the correct media servers. This step is not required if the storage unit is configured to use any available media server.

The nbdevconfig command resides in the following directory: UNIX: /usr/openv/netbackup/bin/admincmd Windows: install_path\Program Files\VERITAS\NetBackup\bin\admincmd For more information, see NetBackup Commands for UNIX and Linux or NetBackup Commands for Windows.

Removing a SharedDisk storage server from disk pool access You can remove a SharedDisk storage server so that it no longer can access a disk pool. If NetBackup jobs exist that use that storage server, you cannot remove it. A SharedDisk storage server is also a media server.

93

94 Managing SharedDisk Managing storage servers

Caution: If you remove the only storage server, data may be lost. NetBackup cannot access the disk pool and the backup images on the disk pool. To remove a SharedDisk storage server from disk pool access 1

For every storage unit that specifies the storage server (media server) in Use one of the following media servers, clear the checkbox that specifies the media server. This step is not required if the storage unit is configured to use any available media server.

2

If only one storage server exists, you must change the state of all disk pools on the array to DOWN before you can remove the storage server. To so so, use the following command: nbdevconfig -changestate -stype SharedDisk -dp disk_pool_name

-state DOWN

3

Remove the storage server. The following is the command syntax: nbdevconfig -changedp -stype SharedDisk -dp disk_pool_name -del_storage_servers storage_server

The nbdevconfig command resides in the following directory: UNIX: /usr/openv/netbackup/bin/admincmd Windows: install_path\Program Files\VERITAS\NetBackup\bin\admincmd For more information, see NetBackup Commands for UNIX and Linux or NetBackup Commands for Windows.

Deleting a storage server If you delete a storage server, NetBackup removes it from your configuration. The media server is not deleted from your configuration. To delete the media server, use the NetBackup nbemmcmd command. If a disk pool is configured from the disk volumes that the storage server manages, you cannot delete the storage server. Caution: Do not delete a storage server if its storage contains unexpired NetBackup images; if you do, data loss may occur. To delete a storage server ◆

Use the following command: nbdevconfig -deletests -storage_server storage_server -stype SharedDisk

The -storage_server storage_server is the storage server name.

Managing SharedDisk Monitoring storage capacity and usage

The nbdevconfig command resides in the following directory: UNIX: /usr/openv/netbackup/bin/admincmd Windows: install_path\Program Files\VERITAS\NetBackup\bin\admincmd For more information, see NetBackup Commands for UNIX and Linux or NetBackup Commands for Windows.

Obtaining storage server status The NetBackup nbdevquery command lets you obtain the status of storage servers.

Table 11-2

nbdevquery storage server options

Option

Description

-liststs

Shows all storage servers.

-storage_server server_name

Shows the information about the specified storage server. Must be used with the -liststs option.

-stype server_type

Use this option with the following two options: ■

With -liststs, shows all storage servers of the specified storage type.

■

With -storage_server, shows all storage servers that are at the specified host.

For more information about the nbdevquery command, see the NetBackup Commands for UNIX and Linux or NetBackup Commands for Windows manual.

Monitoring storage capacity and usage To monitor storage capacity and usage, see: ■

The NetBackup Disk Pool status report. For more information, see “Viewing disk reports” on page 96.

■

Media and Device Management > Devices > Disk Pools.

■

The NetBackup License Keys dialog box. Open the dialog box by selecting Help > License Keys in the NetBackup Administration Console. Display the summary by clicking Summary of active capacity-based license features. The summary displays the storage capacity for which you are licensed and the capacity used. It does not display the amount of physical storage space.

95

96 Managing SharedDisk Viewing disk reports

The NetBackup Operations Manager also provides information about storage capacity and usage. For more information, see the NetBackup Operations Manager Guide.

Viewing disk reports The NetBackup disk reports include information about the disk pools, disk storage units, disk logs, images that are stored on disk media, and storage capacity. To view disk reports 1

In the NetBackup Administration Console tree, expand NetBackup Management > Reports > Disk Reports.

2

Select the name of a disk report.

3

In the right pane, select the report settings.

4

Click Run Report.

Table 11-3 shows the disk reports. Table 11-3

Disk reports

Report

Description

Images on Disk

The Images on Disk report generates the image list present on the disk storage units that are connected to the media server. The report is a subset of the Images on Media report; it shows only disk-specific columns. The report provides a summary of the storage unit contents. If a disk becomes bad or if a media server crashes, this report can let you know what data is lost.

Disk Logs

The Disk Logs report displays the media errors or the informational messages that are recorded in the NetBackup error catalog. The report is a subset of the Media Logs report; it shows only disk-specific columns.

Disk Storage Unit

The Disk Storage Unit Status report displays the state of disk storage units in the current NetBackup configuration. For disk pool capacity, see Media and Device Management > Devices > Disk Pools. Multiple storage units can point to the same disk pool. When the report query is by storage unit, the report counts the capacity of disk pool storage multiple times.

Managing SharedDisk Viewing NetBackup logs

Table 11-3

Disk reports

Report

Description

Disk Pool Status

The Disk Pool Status report displays the state of disk pool storage units. This report displays only when an Enterprise Disk Option license is installed.

Viewing NetBackup logs You can monitor NetBackup disk-related activity and status by viewing the NetBackup log files. Some NetBackup commands or processes write messages to their own log files. Other processes use Veritas unified log (VxUL) files. VxUL uses a standardized name and file format for log files. An originator ID (OID) identifies the process that writes the log messages. For information about the logs, see Table 11-4 Messages that begin with a sts_ prefix relate to the interaction with the storage vendor software plug-in. Most interaction occurs on the NetBackup media servers. Table 11-4

NetBackup logs

Activity

VxUL OID

Processes that use the ID

Backups and restores

N/A

Messages appear in the log files for the following processes: ■

bpbrm backup and restore manger

■

bpdbm database manager

■

bpdm disk manager

■

bptm for I/O operations

Backups and restores

117

The nbjm job manager.

Device configuration

111

The nbemm process.

Device configuration

178

The Disk Service Manager process that runs in the Enterprise Media Manager (EMM) process.

97

98 Managing SharedDisk

Troubleshooting SharedDisk

Table 11-4

NetBackup logs

Activity

VxUL OID

Processes that use the ID

Device configuration

202

The Storage Server Interface process that runs in the Remote Manager and Monitor Service. RMMS runs on media servers. If the Storage Server Interface logs indicate problems with the Veritas Frozen Image (VxFI) service, examine the VxFI log files for detailed trace information:

Device configuration

230

■

UNIX: /user/openv/netbackup/logs/bpfis

■

Windows: install_path\VERITAS\NetBackup\logs \bpfis

The Remote Disk Service Manager interface (RDSM) that runs in the Remote Manager and Monitor Service. RMMS runs on media servers.

To view and manage VxUL log files, you must use NetBackup log commands. For information about how to use and manage logs on NetBackup servers, see the NetBackup Troubleshooting Guide.

Troubleshooting SharedDisk ■

“SharedDisk troubleshooting checklist” on page 98

■

“Determining masked LUNs” on page 107

■

“Checking out a SharedDisk disk volume” on page 107

■

“Disk failure” on page 108

SharedDisk troubleshooting checklist The following checklist may help you troubleshoot if you have problems when you configure and use the SharedDisk storage option: “1. Verify NetBackup installation and license keys” on page 99 “2. Verify the array vendor software installation” on page 99 “3. Verify that the EMM server recognizes the media servers” on page 99 “4. Verify that the disk array credentials are configured” on page 100 “5. Restart NetBackup services” on page 101 “6. Verify LAN connectivity to the disk array” on page 101 “7. Verify that the array host list includes the NetBackup servers” on page 102 “8. Verify that the array can query the LUNs” on page 103

Managing SharedDisk Troubleshooting SharedDisk

“9. Verify SAN connectivity to the disk array” on page 104 “10. Verify that the media servers are configured as storage server(s)” on page 106 “11. Verify that everything works in your environment” on page 107 “12. For more troubleshooting information” on page 107 “13. Contact NetBackup support” on page 107

1. Verify NetBackup installation and license keys The NetBackup master server and all NetBackup media servers that use the feature must be at NetBackup 6.5 or later. You must activate the feature by entering the appropriate license key in NetBackup. If you have configuration problems, verify that: ■

The NetBackup servers are at the correct release levels

■

The license key is installed on the NetBackup master server.

For more information, see “Licensing SharedDisk” on page 63.

2. Verify the array vendor software installation The Veritas Frozen Image (VxFI) service is the NetBackup component that manages access to the storage on the disk array. VxFI uses the disk array vendor’s command line interfaces to: configure the arrays and mask and unmask the LUNs when a media server accesses the storage. The array vendor software must be installed on each NetBackup media server that accesses the storage. If you have configuration or storage access problems, verify that the disk array vendor’s command line interfaces are installed. For more information, see “Installing array software on media servers” on page 59. Also, verify that a supported version of the disk array vendor’s command line interface is installed on each media server. To determine supported versions, check the NetBackup hardware compatibility list (HCL). You can find the HCL at the NetBackup support site: http://entsupport.symantec.com

3. Verify that the EMM server recognizes the media servers To verify that the EMM server recognizes each media server, use the following command. If you have more than one NetBackup master server, use the -masterserver option to identify the master server. nbemmcmd –listhosts

Each media server should appear in the output.

99

100 Managing SharedDisk

Troubleshooting SharedDisk

The following is example output: The following hosts were found:

master masterserver.symantecs.org

server masterserver.symantecs.org

disk_array oven3a

disk_array orach

disk_array cx5002

media mediaserver.symantecs.org

Command completed successfully.

The command output shows which servers are registered with the NetBackup EMM server. The master server and the EMM server are installed on the same host, so the server appears twice. If a media server does not appear, add it by using the nbemmcmd command. The following is the syntax: nbemmcmd -addhost -machinename hostname -machinetype media

Other options let you specify more detailed information.

The nbemmcmd command resides in the following directories:

■

UNIX: /usr/openv/netbackup/bin/admincmd

■

Windows: install_path\VERITAS\Netbackup\bin\admincmd

For command usage, see NetBackup Commands for UNIX and Linux or NetBackup Commands for Windows.

4. Verify that the disk array credentials are configured Verify that the logon credentials are configured for each disk array. To do so, use the following command: tpconfig –ddiskarrays

The following is example output: ==================================================================

Disk Array Host Name: oven3a

Disk Array Type: NetApp(5)

User Id: root

Required Port: 0

==================================================================

Disk Array Host Name: orach

Disk Array Type: HP EVA(0)

User Id: administrator

Required Port: 0

==================================================================

Disk Array Host Name: cx5002

Disk Array Type: EMC CLARiiON(1)

User Id: admin

Required Port: 0

Managing SharedDisk Troubleshooting SharedDisk

If a disk array host does not appear, add the credentials. For procedures, see “Adding disk array logon credentials” on page 68. (Alternatively, you can use the tpconfig command.) Note: This command verifies only that credentials are configured; it does not verify that the credentials are correct. The tpconfig command resides in the following directories: ■

UNIX: /usr/openv/volmgr/bin/

■

Windows: install_path\VERITAS\Volmgr\bin

For command usage, see NetBackup Commands for UNIX and Linux or NetBackup Commands for Windows.

5. Restart NetBackup services After you add credentials, stop and then start the NetBackup services on the NetBackup master server. Also stop and start the services on each NetBackup media server that accesses the disk array. You can use the NetBackup Administration Console Activity Monitor to stop and start the services. Alternatively, you can use the following commands in sequence: ■

UNIX: /usr/openv/netbackup/bin/bp.kill_all

/usr/openv/netbackup/bin/bp.start_all

■

Windows: install_path\VERITAS\Netbackup\bin\bpdown.exe

install_path\VERITAS\Netbackup\bin\bpup.exe

6. Verify LAN connectivity to the disk array To verify LAN connectivity to the disk array, use the following command: nbshareddisk list

Verify that each disk array (enclosure) appears in the command output. If all of the disk arrays appear in the output, LAN connectivity to the disk arrays exists. The following is example output: Enclosure list:

Vendor Array Name Enclosure ID

------------------------------------------------------------------------NETAPP oven3a UEID##NETAPP##LUN##1042386

HP HPEVA4000 UEID##HP##HSV##5000-1FE1-5007-0020

HP VRTS.EVA UEID##HP##HSV##5000-1FE1-5004-5660

EMC 000187910258 UEID##EMC##SYMMETRIX##000187910258

EMC APM00044701641-cx500 UEID##EMC##CLARIION##APM00044701641

If a disk array does not appear in the output:

101

102 Managing SharedDisk Troubleshooting SharedDisk

■

Verify that the disk array logon credentials exist. For procedures, see “4. Verify that the disk array credentials are configured” on page 100.

■

Verify that the disk array vendor’s command line interfaces are installed on each media server. (Not required for NetApp.) Also, verify that the supported versions of the disk array vendor’s command line interfaces are installed on each media server. For more information, see “2. Verify the array vendor software installation” on page 99.

■

Examine nbshareddisk command logs for messages about failures. The following are the log file pathnames: Windows: install_path\VERITAS\NetBackup\logs\admin UNIX: /usr/openv/netbackup/logs/admin To obtain useful information, you may have to increase the NetBackup logging levels.

The nbshareddisk command resides in the following directories: ■

UNIX: /usr/openv/netbackup/bin/admincmd

■

Windows: install_path\VERITAS\Netbackup\bin\admincmd

For command usage, see NetBackup Commands for UNIX and Linux or NetBackup Commands for Windows.

7. Verify that the array host list includes the NetBackup servers To verify that the disk array host list includes each NetBackup server that accesses the array, use the following command: nbshareddisk list -hosts

Each NetBackup media server that accesses the array must in the host list. Host names must be valid IP host names. For all array vendors, the host entries must match the DNS hostname of the media server. The host list also is known as a WWN map. The following is example output: Enclosure ID Host Name HBA WWPN

----------------------------------------------------------------1042386 MediaServerA 10000000c943c971

1042386 MediaServerB 10000000c9439ef7

5000-1FE1-5007-0020 MediaServerA 10000000c943c971

5000-1FE1-5007-0020 MediaServerB 10000000c9439ef7

000187910258 MediaServerA 10000000c943c971

000187910258 MediaServerB 10000000c9439ef7

APM00044701641 MediaServerA 10000000C943C971

APM00044701641 MediaServerB 10000000C9439EF7

Managing SharedDisk Troubleshooting SharedDisk

Depending on how your environment is configured, additional hostnames may

be in the list also.

If a media server is not in the list, do the following:

■

Verify that the SAN zone includes the HBA and array port WWPNs. The array ports must be hard or soft zoned to the NetBackup media server and NetBackup client HBA ports. For more information, see “Zoning the SAN” on page 58.

■

Add the host entries. For more information, see “Adding array host entries” on page 59.

■

Examine the array disk plug-in logs for messages about failures. The following are the log file pathnames: Windows: install_path\VERITAS\NetBackup\logs\adsts.log UNIX: /usr/openv/netbackup/logs/adsts.log To obtain useful information, you may have to increase the NetBackup logging levels.

The nbshareddisk command resides in the following directories: ■

UNIX: /usr/openv/netbackup/bin/admincmd

■

Windows: install_path\VERITAS\Netbackup\bin\admincmd

For command usage, see NetBackup Commands for UNIX and Linux or NetBackup Commands for Windows.

8. Verify that the array can query the LUNs Verify that each disk array (enclosure) can display the LUNs that were allocated to NetBackup. The following is the command syntax. It displays the LUNs with their unique device identifier (UDID) for the specified disk array. nbshareddisk list –ueid unique_enclosure_ID

The following is an example command and output: nbshareddisk list –enclosure UEID##EMC##CLARIION##APM00044701641

Device Name Size (KB) Device Id

----------------------------------------------------------------------------------------------------------------------nbusd_winb5 5242880

UDID##DGC##CLARIION##APM00044701641##60:06:01:60:2C:96:12:00:D8:CD:C0:49:7D:4E:DB:11

nbusd_winb3 5242880

UDID##DGC##CLARIION##APM00044701641##60:06:01:60:2C:96:12:00:D6:CD:C0:49:7D:4E:DB:11

nbusd_winb4 5242880

UDID##DGC##CLARIION##APM00044701641##60:06:01:60:2C:96:12:00:D7:CD:C0:49:7D:4E:DB:11

nbusd_winb1 5242880

UDID##DGC##CLARIION##APM00044701641##60:06:01:60:2C:96:12:00:D4:CD:C0:49:7D:4E:DB:11

103

104 Managing SharedDisk Troubleshooting SharedDisk

nbusd_winb2 5242880

UDID##DGC##CLARIION##APM00044701641##60:06:01:60:2C:96:12:00:D5:CD:C0:49:7D:4E:DB:11

If the array does not support LUN prefix names, all LUNs on the array should

appear in the command output.

If the correct UDIDs do not appear in the output, verify the array configuration

as follows:

■

Verify that the LUNs were allocated to NetBackup by using the nbusd_ prefix. For more information, see “Allocating LUNs for NetBackup” on page 60.

■

Examine the array disk plug-in logs for messages about failures. The following are the log file pathnames: Windows: install_path\VERITAS\NetBackup\logs\adsts.log UNIX: /usr/openv/netbackup/logs/adsts.log To obtain useful information, you may have to increase the NetBackup logging levels.

The nbshareddisk command resides in the following directories: ■

UNIX: /usr/openv/netbackup/bin/admincmd

■

Windows: install_path\VERITAS\Netbackup\bin\admincmd

For command usage, see NetBackup Commands for UNIX and Linux or NetBackup Commands for Windows.

9. Verify SAN connectivity to the disk array To verify SAN connectivity to a disk array, do the following: ■

Format a LUN on the array.

■

Mount and unmount the LUNs

If you can format a LUN and mount and unmount a LUN, SAN connectivity to the disk array is verified. I/O operation also is verified.

Format a LUN If possible, format a small LUN on the array. The format operation can be a time-consuming process. Caution: If you format a LUN on which data exists, the format operation erases that data. For example, the following command formats two LUNs. The LUNs are listed in the arrayudidlist.txt file: nbshareddisk format -udid_file arrayudidlist.txt

Managing SharedDisk Troubleshooting SharedDisk

Preparing to process LUNs/UDIDs:

UDID##DGC##CLARIION##APM00044701641##60:06:01:60:2C:96:12:00:E2:CD:

C0:49:7D:4E:DB:11

UDID##DGC##CLARIION##APM00044701641##60:06:01:60:2C:96:12:00:E0:CD:

C0:49:7D:4E:DB:11

Imported resource

[UDID##DGC##CLARIION##APM00044701641##60:06:01:60:2C:96:12:00:E2:CD

:C0:49:7D:4E:DB:11] at local device path [/dev/rdsk/c3t4d0].

Device [/dev/rdsk/c3t4d0] formatted successfully with file-system

type [ufs] and VM type [].

Unmounted formatted resource [/dev/dsk/c3t4d0s2],

[UDID##DGC##CLARIION##APM00044701641##60:06:01:60:2C:96:12:00:E2:CD

:C0:49:7D:4E:DB:11].

Deported resource

[UDID##DGC##CLARIION##APM00044701641##60:06:01:60:2C:96:12:00:E2:CD

:C0:49:7D:4E:DB:11].

Imported resource

[UDID##DGC##CLARIION##APM00044701641##60:06:01:60:2C:96:12:00:E0:CD

:C0:49:7D:4E:DB:11] at local device path [/dev/rdsk/c3t4d0].

Device [/dev/rdsk/c3t4d0] formatted successfully with file-system

type [ufs] and VM type [].

Unmounted formatted resource [/dev/dsk/c3t4d0s2],

[UDID##DGC##CLARIION##APM00044701641##60:06:01:60:2C:96:12:00:E0:CD

:C0:49:7D:4E:DB:11].

Deported resource

[UDID##DGC##CLARIION##APM00044701641##60:06:01:60:2C:96:12:00:E0:CD

:C0:49:7D:4E:DB:11].

If the format fails: ■

(Solaris only.) Verify that the appropriate LUN entries were added to the sd.conf file. The LUN entries allow NetBackup to import LUNs to the host. For more information, see “Adding LUN entries to the sd.conf file” on page 61.

■

Examine the array disk plug-in logs for messages about failures. The following are the log file pathnames: Windows: install_path\VERITAS\NetBackup\logs\adsts.log UNIX: /usr/openv/netbackup/logs/adsts.log To obtain useful information, you may have to increase the NetBackup logging levels.

Mount and unmount the LUNs To mount a LUN, it must be formatted and offline. To unmount a LUN, it must be formatted and online.

The command to mount a LUN also performs other operations that help verify

connectivity.

105

106 Managing SharedDisk Troubleshooting SharedDisk

To mount and then unmount a specific LUN 1

Mount the LUN by using the nbshareddisk command. The following is the command syntax: nbshareddisk online –udid UDID##nn#nn##nn

The following is an example: nbshareddisk online –udid

UDID##DGC##CLARIION##APM00044701641##60:06:01:60:2C:96:12:00:E2:CD:C0:49:7D:4E:DB:11

List of online mount points

-----------------------------------------------------------------------------------Udid Mount point

-----------------------------------------------------------------------------------UDID##DGC##CLARIION##APM00044701641##60:06:01:60:2C:96:12:00:E2:CD:C0:49:7D:4E:DB:11

/nbusd_b8fd784dd4df57e6

2

Unmount the LUN by using the nbshareddisk command. The following is the command syntax (the command produces no output): UNIX: nbshareddisk offline -device mount_point Windows: nbshareddisk offline -device C:\nbussod\mnt_point\

Ensure that you use the trailing back slash on the Windows command line. The following is an example: nbshareddisk offline -device /nbusd_b8fd784dd4df57e6

The nbshareddisk command resides in the following directories: ■

UNIX: /usr/openv/netbackup/bin/admincmd

■

Windows: install_path\VERITAS\Netbackup\bin\admincmd

For command usage, see NetBackup Commands for UNIX and Linux or NetBackup Commands for Windows.

10. Verify that the media servers are configured as storage server(s) Verify that each NetBackup that connects to the array is configured as a storage server. To do so, use the following command nbdevquery -liststs -stype SharedDisk

V6.5 tree.symantecs.org SharedDisk 6

V6.5 flower.symantecs.org SharedDisk 6

V6.5 water.symantecs.org SharedDisk 6

The command output shows which media servers are configured as SharedDisk storage servers. If a storage server does not appear, create the storage server. To do so, see “Creating a storage server in NetBackup” on page 66. The nbdevquery command resides in the following directory: UNIX: /usr/openv/netbackup/bin/admincmd Windows: install_path\Program Files\VERITAS\NetBackup\bin\admincmd

Managing SharedDisk Troubleshooting SharedDisk

11. Verify that everything works in your environment Verify that your network environment functions correctly. Verify that the

NetBackup services are active on all NetBackup servers.

Ensure that you have read the NetBackup SharedDisk documentation and any

vendor specific documentation.

12. For more troubleshooting information More troubleshooting information about SharedDisk and its components such as VxFI is available on the Symantec Enterprise Support Web site in the following Tech Note: http://entsupport.symantec.com/docs/288177

The Tech Note contents are updated when new information is available. The Tech Note may contain more current information than this guide.

13. Contact NetBackup support If you performed all of steps in this checklist and problems still exist, contact NetBackup Technical Support. The following is the address for the site: http://entsupport.symantec.com

Determining masked LUNs The NetBackup nbfirescan command scans for SCSI disk devices and displays

the results.

The nbfirescan command resides in the Veritas Frozen Image directory as

follows:

■

install_path\Common Files\Symantec Shared\VxFI\4\Bin (Windows)

■

/usr/openv/netbackup/bin (UNIX)

For more information about the nbfirescan command, see the NetBackup Commands for UNIX and Linux or NetBackup Commands for Windows manual.

Checking out a SharedDisk disk volume The storage in an array is exposed to a NetBackup media server dynamically. That is, Veritas Frozen Image (VxFI) masks the storage when a media server performs I/O and then unmasks the storage when not required. (VxFI is the NetBackup component that manages access to the storage on the disk array.) You can check out a disk volume manually to determine what NetBackup wrote on the file system on the LUNs.

107

108 Managing SharedDisk

Troubleshooting SharedDisk

To check out a disk volume 1

Determine the name of the disk volume. The following is the command syntax: nbdevquery -listdv -stype SharedDisk -dp disk_pool_name

2

Change the disk volume state to DOWN so that NetBackup does not assign jobs to it. The following is the command syntax: nbdevconfig -changestate –stype SharedDisk -dp disk_pool_name

–dv vol_name -state DOWN

This command does not stop currently active jobs; they complete their I/O. 3

Wait for all active jobs that use that volume to complete. Use the NetBackup Administration Console Activity Monitor to monitor the jobs.

4

Determine the UDID of the disk volume. The following is the command syntax to display all of the disk volumes in an enclosure: nbshareddisk list -ueid unique_enclosure_id

5

Expose (mask) the LUN to a media server and then mount it. The following is the command syntax: nbshareddisk online -udid UDID##nn#nn##nn

6

Browse the file system.

7

Unmount the LUN. The following is the command syntax: UNIX: nbshareddisk offline -device mount_point

Windows: nbshareddisk offline -device C:\nbussod\mnt_point\

Ensure that you use the trailing back slash on the Windows command line.

8

Unmaske the LUN from the media server. The following is the command syntax: nbshareddisk mask -udid UDID##nn#nn##nn

9

Change the disk volume to UP so that NetBackup can use it. The following is the command syntax: nbdevconfig -changestate –stype SharedDisk -dp disk_pool_name

–dv vol_name -state UP

Disk failure A disk failure in an array that is configured to provide redundancy should not affect NetBackup disk pool operation. If recovery mechanisms do not protect a disk that fails, the backup images on that disk are lost. Operating system read and write errors may occur for the volume that represents the disk. NetBackup cannot use that volume because of the errors, and NetBackup jobs may fail. To prevent NetBackup from trying to read from or write to the disk, you must change the volume state to DOWN in NetBackup. If the volume represents other

Managing SharedDisk Troubleshooting SharedDisk

disks that still function, those disks are not available because the volume state is DOWN. You may be able to read from the volume by mounting it manually, in which case you may be able to recover image fragments from any disks that did not fail. If you replace the failed disk, you can allocate that new disk to NetBackup, as follows: ■

In NetBackup, expire backup images on the downed volume so the image records are removed from the NetBackup catalog.

■

Use the array software utilities to delete the volume from the array.

■

Allocate the new disk and any other disks that were in the volume to NetBackup. You must use a different name for the LUN than was used for the original volume.

■

Add that LUN to an existing disk pool or create a new disk pool from that LUN.

Because NetBackup does not let you delete volumes from a disk pool, the downed volume remains in the disk pool. The downed volume does not affect disk pool functionality.

109

110 Managing SharedDisk Troubleshooting SharedDisk

Section

III

Shared Storage Option

■

“Introduction” on page 113

■

“Licensing the Shared Storage Option” on page 117

■

“Configuring the Shared Storage Option” on page 119

■

“Using the Shared Storage Option” on page 127

■

“Shared Storage Option Reference” on page 131

■

“Troubleshooting the Shared Storage Option” on page 137

112

Chapter

12

Introduction The Shared Storage Option allows multiple NetBackup media servers to share individual tape drives (stand-alone drives or drives in a robotic library). NetBackup automatically allocates and unallocates the drives as backup and restore operations require. For more information about Shared Storage Option, see: ■

“Overview” on page 113

■

“NetBackup Release Notes” on page 115

For information about how to install, configure, and use Shared Storage Option, see: ■

“Licensing the Shared Storage Option” on page 117

■

“Configuring the Shared Storage Option” on page 119

■

“Using the Shared Storage Option” on page 127

■

“Shared Storage Option Reference” on page 131

■

“Troubleshooting the Shared Storage Option” on page 137

Overview The Shared Storage Option is a separately licensed and separately priced NetBackup software option. This software option is the Shared Drives option, and the license key is the Shared Storage Option key. The Shared Storage Option is available with both NetBackup Server and NetBackup Enterprise Server. Shared Storage Option is require only if multiple hosts share drives. For example, multiple NDMP hosts may share one or more drives. Shared Storage Option requires appropriate hardware connectivity, such as Fibre Channel hubs or switches, SCSI multiplexors, or SCSI-to-fibre bridges. For more information, see “Frequently asked questions about Shared Storage Option” on page 140.

114 Introduction

Overview

SAN media server NetBackup Enterprise Server topic.

Shared Storage Option can use a NetBackup SAN media server, which is a media

server that can back up its own data only. SAN media servers cannot back up

data that resides on other clients.

A SAN is not required for Shared Storage Option You can use Shared Storage Option in: ■

Fibre Channel SANs

■

Environments that do not use Fibre Channel, such as SCSI switches or multi-initiator configurations

Shared Storage Option does not load firmware in SAN devices or communicate with hub or switch APIs. Shared Storage Option can communicate with hub or switch APIs if you use the NetBackup shared_drive_notify script.

Sample Shared Storage Option configuration with SAN components Figure 12-1 shows typical SAN components in a shared drive configuration.

Introduction NetBackup Release Notes

Figure 12-1

Example Shared Storage Option configuration

Master server with Shared Storage

SCSI robot and Fibre Channel drives

SCSI (UNIX, Linux, or Windows Platform)

Fibre Channel Host bus adapter Hub (arbitrated loop) or

Fibre Channel

Fibre Channel

switch (fabric) SCSI bridge Fibre Channel

Host bus adapter

SCSI Media server with Shared Storage (UNIX, Linux, or Windows Platform)

Native Fibre Channel robot and drives *

SCSI robot and drives

* Some robots have integrated bridges, but native Fibre Channel devices do not.

NetBackup Release Notes For information about supported systems and peripherals, limitations, and operational notes, see the NetBackup Release Notes.

115

116 Introduction NetBackup Release Notes

Chapter

13

Licensing the Shared Storage Option No special installation is required for the Shared Storage Option. When NetBackup software is installed, the Shared Storage Option software also is installed. However, you must activate the feature by entering the Shared Storage Option license key on the NetBackup master server. Also install the key on each NetBackup media server that shares drives. For NetBackup installation instructions, see: ■

NetBackup Installation Guide for UNIX and Linux

■

NetBackup Installation Guide for Windows

You may have one license key that activates NetBackup and all of your add-on products. Alternatively, you may have a separate license key for NetBackup and for each add-on product such as the Shared Storage Option.

118 Licensing the Shared Storage Option

Chapter

14

Configuring the Shared Storage Option To configure your hardware for use with Shared Storage Option, you must do the following ■

Configure your SAN environment.

■

Attach robots and drives.

■

Ensure that all of the servers recognize the shared devices. Device recognition may depend on operating system configuration: ■

On UNIX or Linux servers, you may have to modify configuration files, such as the sg driver on Solaris systems.

■

On Windows servers, Windows recognizes devices automatically. However, in some instances you may have to install device drivers.

Configuration tasks Some of the following tasks may be optional depending on your hardware: ■

Determine the physical location of each drive within the robot. Location usually is shown on the connectors to the drives or in the vendor documentation. This task may not be required if NetBackup device discovery accurately determines drive location within the robot.

■

Connect all drives and all robots.

■

Install SAN connecting hardware (for example, bridges, switches, or hubs).

■

If fibre is part of your configuration and you use a SCSI-to-fibre bridge, determine the SCSI-to-Fibre Channel mapping for your tape devices.

120 Configuring the Shared Storage Option

Configuration tasks

Hard-wired SCSI IDs are converted to Fibre Channel logical unit numbers (LUNs) that the hosts read. To ensure correct drive assignments, you should know which LUNs map to which physical SCSI IDs. Use persistent LUN mapping if possible. Familiarity with the hardware and various vendor configuration tools help you accomplish this task. See the vendor documentation for your bridge. ■

Record the physical configuration. When you set up an Shared Storage Option configuration, record your hardware information. Record the adapter, SCSI addresses, World Wide Names (WWNs), and Fibre Channel LUNs to which you connected each drive. Also, record the version levels of firmware and drivers.

■

Install and configure the appropriate drivers. See your vendor documentation for instructions.

■

On UNIX or Linux servers, create any device files that are needed. Depending on the operating system, these files may be created automatically by using a reconfiguration boot (boot -r). Create the device files for each drive; use the Fibre Channel LUNs of the drives and adapters in the device file names. Add the names of the device files to your notes to complete the correlation between device files and physical drive location. Use the NetBackup Device Configuration Guide and the man pages that are available with the operating system.

■

On UNIX servers, customize the operating system by modifying the appropriate system configuration files. This task requires knowledge of the system files that use the Shared Storage Option environment and their formats. For example, on Sun Solaris systems you may need to modify the sg, st, and HBA driver files. Modify the HBA driver files to bind Fibre Channel devices (WWN) to a specific target ID. For procedures, see the operating system documentation.

■

For instructions on how to configure the HBA on Windows servers, see the HBA documentation from the vendor.

■

Use any available hardware configuration interface to configure and ensure that the configuration is what you expect. For example, on Windows servers you can use the HyperTerminal interface to configure SCSI-to-fibre bridges. Use the following order when you configure and verify the hardware: ■

Robot and shared drives

■

Bridges

■

Hub or switches

■

Hosts

Configuring the Shared Storage Option Installing and configuring drivers

■

If errors occur and you suspect the operating system, refer to the operating system logs as described in your operating system documentation.

Installing and configuring drivers On the media server systems, install and configure drivers and modify the appropriate system configuration files. For guidance about the NetBackup requirements, see the NetBackup Device Configuration Guide.

Verifying connectivity Test your hardware configuration before you configure Shared Storage Option in NetBackup. This task is very important and is often overlooked. Note the following points: ■

Verify that all of your servers (master and media) are able to communicate with one another. Perform a ping from each server to every other server. Be sure to ping by host name to verify that the name resolution methods function properly.

■

Use the NetBackup bpclntcmd utility to resolve IP addresses into host names. For more information, see the NetBackup Troubleshooting Guide and the NetBackup Commands for UNIX and Linux or the NetBackup Commands for Windows.

■

Use operating system and NetBackup commands and tools to verify that the devices are configured correctly. Make sure that the operating system detects the devices on the SAN before you configure the Shared Storage Option. If the configuration does not work in the operating system, it does not work for the Shared Storage Option. For example, on Solaris systems you can use the mt -f tapename status command to determine tape drive status.

■

For more information and examples, see the appropriate operating system chapter in the NetBackup Device Configuration Guide.

Configuring Shared Storage Option in NetBackup You must configure your shared drives, storage units, and backup policies.

121

122 Configuring the Shared Storage Option Configuring Shared Storage Option in NetBackup

Configuring Shared Storage Option devices in NetBackup Symantec recommends that you use the Device Configuration Wizard to configure shared drives. The wizard guides you through the steps to configure shared drives. Start the wizard from the Media and Device Management window of the NetBackup Administration Console or from the Getting Started wizard. Be sure to review the limitations of the wizard before starting. To start the Device Configuration Wizard 1

In the NetBackup Administration Console, select Media and Device Management.

2

Click Configure Storage Devices.

Adding Shared Storage Option configuration options You can fine tune your configuration by adding Shared Storage Option options to the Media Manager configuration file. For descriptions of all of the available vm.conf entries, see “The Media Manager configuration file (vm.conf)” in the NetBackup Administrator's Guide for UNIX and Linux, Volume II or the NetBackup Administrator's Guide for Windows, Volume II.

Configuring NetBackup storage units and backup policies You must configure storage units and policies for your shared drives. If you used the Device Configuration Wizard to configure the shared drives, you may have configured storage units and policies already. For more information, see the NetBackup Administrator's Guide for UNIX and Linux, Volume I or the NetBackup Administrator's Guide for Windows, Volume I.

Configuring storage units for each media server In each storage unit definition, logically define the robot and the shared drives for that media server. For the Maximum concurrent drives used for backup, specify the total number of all shared drives in the robot. When you configure storage units, select a single media server. Alternatively, you can allow NetBackup to select the media server to use at the time of the backup. For example, you can configure a single storage unit that any media server that shares the storage unit can use.

Configuring the Shared Storage Option Verifying your Shared Storage Option configuration

Configuring a backup policy for each media server How you define a policy for a media server depends on your media server license, as follows. A license for a regular media server provides the greatest flexibility; a license for a NetBackup SAN media server is more restrictive. ■

For a media server that is licensed for Shared Storage Option, the policy can back up the media server and any other NetBackup clients.

■

For a NetBackup SAN media server, only the SAN media server can be backed up.

For a policy for the clients that you want to back up anywhere in your configuration, you can choose any available storage unit. Alternatively, you can use storage unit groups (prioritized storage units).

Verifying your Shared Storage Option configuration In an Shared Storage Option configuration, a shared drive must have the same logical name (drive name) on all of the NetBackup media servers. If the drive resides in a robotic library, it also must use the same drive number in the library. This section describes some tools you can use to verify your configuration. How you verify that your configuration is set up correctly depends on your devices and how you configured Shared Storage Option, as follows: ■

If you have serialized devices, Symantec recommends that you use the Device Configuration Wizard. The wizard verifies your configuration.

■

If you have non-serialized devices, see the Veritas support site for a tech note with instructions about how to verify your configuration. The tech note title is “Verifying a Shared Storage Option (SSO) Configuration with Non-Serialized Devices.“

■

If you have serialized devices but you did not use the Device Configuration wizard, use the following procedure to verify your configuration.

The verification procedures uses the NetBackup scan and tpconfig commands. These commands are located in the following directory: ■

usr/openv/volmgr/bin (UNIX and Linux)

■

install_path\VERITAS\Volmgr\bin (Windows)

In the following example the ADIC robotic library has six drives, but only drives

5 and 6 are configured on this particular host.

Perform the verification on all of the NetBackup servers in your configuration.

Ensure that each shared drive has the same logical drive name and same drive number ID on each media server that shares the drive.

123

124 Configuring the Shared Storage Option Verifying your Shared Storage Option configuration

To verify a manually-configured Shared Storage Option configuration 1

Execute tpconfig -d or tpconfig -dl. For NDMP devices, use tpautoconf -probe -ndmp_host_name host_list. The output from tpconfig shows the logical names NetBackup assigns to tape drives. The following example shows drive number 5 is named QUANTUM.DLT7000.000 and drive number 6 is named QUANTUM.DLT7000.001: Id

DriveName Type Residence Drive Path Status *************************************************************** 0 QUANTUM.DLT7000.000 dlt TLD(0) DRIVE=5 /dev/st/nh3c0t5l0 UP 1 QUANTUM.DLT.7000.001 dlt TLD(0) DRIVE=6 /dev/st/nh3c0t1l0 UP Currently defined robotics are:

TLD(0) robotic path = /dev/sg/h3c0t0l0

EMM server = norway

2

Execute the scan command. The scan output shows the robot and the drive properties. The following is example output: ************************************************************

*********************** SDT_TAPE ************************

*********************** SDT_CHANGER ************************

*********************** SDT_OPTICAL ************************

************************************************************

Device Name : "/dev/sg/h3c0t0l0"

Passthru Name: "/dev/sg/h3c0t0l0"

Volume Header: ""

Port: -1; Bus: -1; Target: -1; LUN: -1

Inquiry : "ADIC Scalar 100 3.10"

Vendor ID : "ADIC "

Product ID : "Scalar 100 "

Product Rev: "3.10"

Serial Number: "ADIC009K0340314"

WWN : ""

WWN Id Type : 0

Device Identifier: ""

Device Type : SDT_CHANGER

NetBackup Robot Type: 6

Removable : Yes

Device Supports: SCSI-2

Number of Drives : 6

Number of Slots : 50

Number of Media Access Ports: 10

Drive 1 Serial Number : "PXB03S0979"

Drive 2 Serial Number : "PXB03S0913"

Drive 3 Serial Number : "CXA04S2051"

Drive 4 Serial Number : "PXA31S1787"

Configuring the Shared Storage Option Verifying your Shared Storage Option configuration

Drive 5 Serial Number : "PXA37S3261"

Drive 6 Serial Number : "PXA50S2276"

Flags : 0x0

Reason: 0x0

-----------------------------------------------------------Device Name : "/dev/st/nh3c0t5l0"

Passthru Name: "/dev/sg/h3c0t5l0"

Volume Header: ""

Port: -1; Bus: -1; Target: -1; LUN: -1

Inquiry : "QUANTUM DLT7000 2561"

Vendor ID : "QUANTUM "

Product ID : "DLT7000 "

Product Rev: "2561"

Serial Number: "PXA37S3261"

WWN : ""

WWN Id Type : 0

Device Identifier: ""

Device Type : SDT_TAPE

NetBackup Drive Type: 9

Removable : Yes

Device Supports: SCSI-2

Flags : 0x4

Reason: 0x0

-----------------------------------------------------------Device Name : "/dev/st/nh3c0t1l0"

Passthru Name: "/dev/sg/h3c0t1l0"

Volume Header: ""

Port: -1; Bus: -1; Target: -1; LUN: -1

Inquiry : "QUANTUM DLT7000 296B"

Vendor ID : "QUANTUM "

Product ID : "DLT7000 "

Product Rev: "296B"

Serial Number: "PXA50S2276"

WWN : ""

WWN Id Type : 0

Device Identifier: ""

Device Type : SDT_TAPE

NetBackup Drive Type: 9

Removable : Yes

Device Supports: SCSI-2

Flags : 0x4

Reason: 0x0

3

For each tape drive in the tpconfig output, do the following: ■

Use the device file name from the tpconfig output to locate the tape drive in the scan output. The example tpconfig output in step 1 shows device file pathnames /dev/st/nh3c0t5l0 and /dev/st/nh3c0t1l0.

■

Determine the serial number of the drive in the scan output. “Tape” in the device type field identifies a tape drive.

125

126 Configuring the Shared Storage Option Verifying your Shared Storage Option configuration

The example scan output in step 2 shows that the drive /dev/st/nh3c0t5l0 serial number is PXA37S3261 and the drive /dev/st/nh3c0t1l0 serial number is PXA50S2276. ■

Verify that the serial number for the drive matches the serial number in the output from the robot section of scan. “Changer” in the device type field identifies a robot. In the previous examples, the serial numbers match.

Chapter

15

Using the Shared Storage Option You can use the NetBackup Administration Console Device Monitor to obtain information about your Shared Storage Option configuration and manage your shared drives. See the following: ■

“Using the Device Monitor with Shared Storage Option” on page 127

■

“Shared Storage Option summary reports” on page 128

You can adjust media and device operation by adding options in the Media Manager configuration file. See “Adding configuration options” on page 129. For more information about the Device Monitor, see the NetBackup Administrator’s Guide, Volume I.

Using the Device Monitor with Shared Storage Option See the following related Device Monitor topics: ■

“The Drive Status pane” on page 127

■

“Changing the operating mode for a shared drive” on page 128

■

“Adding or changing a comment for a shared drive” on page 128

■

“Performing drive cleaning functions for a shared drive” on page 128

The Drive Status pane The Control and Device Host columns contain shared drive information.

128 Using the Shared Storage Option Shared Storage Option summary reports

Changing the operating mode for a shared drive For a shared drive, the change mode dialog contains a list of all paths to the selected drive. You can choose any number of paths to which the mode change applies.

Adding or changing a comment for a shared drive For a shared drive, the change drive comment dialog box contains: ■

A list of all paths to the selected drive

■

The current drive comment for each combination.

You can choose any number of paths to which the changes apply.

Performing drive cleaning functions for a shared drive See the following table for the available drive cleaning functions and their use with shared drives. Drive cleaning function

Shared drive usage

Clean Now

In the list of hosts that share the drive, you can choose only one host on which the function applies.

Reset Mount Time

In the list of hosts that share the drive, you can choose any number of hosts on which the function applies.

Set Cleaning Frequency

Supported for shared drives.

Shared Storage Option summary reports The following topic applies only to NetBackup Enterprise Server. The following two reports contain the following information about the drives and hosts. ■

■

The Shared Drive Summary shows: ■

Drive name

■

Device allocation host

■

Number of registered hosts

■

Drive reservation status

■

Hosts that reserve the drive

■

Current scan host

The Device Allocation Host Summary shows:

Using the Shared Storage Option Adding configuration options

■

Device allocation host

■

Host name of the registered host

■

Number of registered and reserved drives

■

Availability status

■

Scan ability factor

■

Scan status (if the host is scan host for at least one SSO drive)

To view summary reports 1

In the NetBackup Administration Console, select Media and Device Management > Device Monitor.

2

Select Actions > View Status of Shared Drives.

3

In the Status of Shared Drives dialog, select a device allocation host (or hosts) from the list.

4

Use Add >> to move the host to the list of hosts to scan.

5

Click OK. The Shared Drive Summary and Device Allocation Host Summary appear in the two lower panes of the dialog.

Adding configuration options You can fine tune your configuration by adding Shared Storage Option options to the vm.conf Media Manager configuration file.

For more information, see “Additional Configuration” in the NetBackup

Administrator’s Guide for UNIX and Linux, Volume II or NetBackup

Administrator’s Guide for Windows, Volume II.

129

130 Using the Shared Storage Option Adding configuration options

Chapter

16

Shared Storage Option Reference For reference, see the following subsections.

Terms and concepts Table 16-1 describes terms and concepts. Table 16-1

Shared Storage Option terms and concepts

Backup Exec Shared Storage Option

The Veritas NetBackup Shared Storage Option is not the same as the Veritas Backup Exec Shared Storage Option. The Backup Exec SSO does not include support for UNIX servers and uses a different method for drive arbitration.

SAN media servers

A NetBackup SAN media server backs up its own data to shared drives. It cannot backup data on other NetBackup hosts or clients. Symantec licenses NetBackup SAN media servers.

Shared drive

When the Shared Storage Option is installed, a tape drive that is shared among hosts is termed a shared drive. For the drives that are attached to NDMP hosts, each NDMP attach host is considered an additional host.

132 Shared Storage Option Reference

Shared Storage Option components

Table 16-1

Shared Storage Option terms and concepts

To share robotic libraries without You can share robotic tape libraries among multiple using the Shared Storage Option NetBackup media servers by using any of the following methods. These capabilities are not related to Shared Storage Option and should not be confused with Shared Storage Option. ■

NetBackup allows different drives within the same robotic library to be configured on different media servers. This capability is termed shared library support. Robot types that support shared library are ACS, TL8, TLD, TLH, TLM.

■

Some robot vendors also let you partition libraries. One partitioned view of the robotic library includes one set of drives, while the other view has a different set of drives in the library. Partitions lets two robotic control daemons on different control hosts manage the robotic library — possibly each for a different NetBackup master and media server environment.

■

Use multiple NetBackup master servers that share a common media and device management domain. This means that the master servers use the same EMM server.

Shared Storage Option components The NetBackup Enterprise Media Manager (EMM) manages media information. The Enterprise Media Manager also is the device allocator (DA) for shared drives.

NetBackup EMM To coordinate network-wide allocation of tape drives, EMM manages all shared tape requests in a SAN. EMM responds to requests from multiple instances of NetBackup master servers, media servers, NetBackup SAN media servers, or Veritas Storage Migrator. For shared drive configurations, the host that is configured as the EMM server is also known as the device allocation host. For more information, see “Device allocation host” on page 135.

Shared Storage Option Reference Shared Storage Option components

EMM maintains shared drive and host information. Information includes a list of hosts that are online and available to share a drive and which host currently has the drive reserved. The Media Manager device service ltid requests shared drive information changes.

Example Shared Storage Option configuration The following figure shows an example of a shared drive configuration. See the NetBackup Troubleshooting Guide for a process flow diagram of Shared Storage Option components. Host B

Host A

EMM Server

Scan host

Device allocation host

Robot TLD (0) (avrd)

(vmd)

(ltid) (vmd)

Robot control

Hardware

(avrd)

Control

(ltid) (nbemm / DA)

Path

Host adapter

Host adapter DRV1

DRV2 Data path

Data path Data path

Data path

Hardware connection

In this figure, Host A is ■

Connected to drives DRV1 and DRV2 through SAN hardware.

■

The first host in the environment to come online with a non-zero scan ability factor. Therefore, it is the initial scan host for its drives. For more information, see “Scan host” on page 134.

In this figure, Host B: ■

Is connected to drives DRV1 and DRV2 through SAN hardware.

■

Is configured to be the EMM server, which is also the device allocation host (see “Device allocation host” on page 135).

133

134 Shared Storage Option Reference Shared Storage Option components

■

Controls the robotics. Except for ACS or TLM robot types, only one robot control host exists for each robot.

■

Could be optionally configured as a Highly Available (HA) server.

Scan host Each shared drive has a host that is identified as the scan host. A scan host is the host from which the automatic volume recognition process (avrd) scans unassigned drives. (The robotic daemons scan assigned drives.) A scan host must have data-path access to the drive. Before NetBackup release 6.0, instances of ltid on the hosts that were not scan hosts created remote device management interface (rdevmi) processes on the scan hosts. These processes communicate with the other hosts that shared the drive. They ran on the scan hosts as slave processes of the non-scan hosts’ ltid. In NetBackup release 6.0 and later, instances of rdevmi that run on NetBackup 5.x servers communicate through a proxy with the EMM server. These processes receive drive status information from the EMM server. This status information is used to maintain the shared drive information centrally in the EMM database. The EMM database contains the shared drive information; that information includes the scan host. Media servers receive drive status information from the EMM server. For NetBackup 5.x media servers, remote device management interface processes (rdevmi) communicate through a proxy with the EMM server.

How the scan host is determined EMM determines scan hosts; a scan host may be different for each shared drive. The first host in the environment to come online with a non-zero scan ability factor is the initial scan host for its drives. NetBackup 5.x device hosts register with the nbemm process; they pass a list of shared drives to nbemm. The nbemm process returns the name of the currently assigned scan host for each drive to each NetBackup 5.x host. To configure the scan ability factor of media servers, use the nbemmcmd. For more information, see the NetBackup Commands for UNIX and Linux or NetBackup Commands for Windows guide.)

The scan host can change A scan host is assigned for a shared drive until some interruption occurs. For example, one of the following occurs: ■

The socket connection, the host, the drive, the drive path, or the network goes down.

Shared Storage Option Reference Shared Storage Option components

■

The drive is logically placed in the Down mode.

EMM then chooses a new scan host. The scan host temporarily changes to hosts

that request tape mounts while the mount is in progress. Scan host changes

occur so only one host at a time has access to the drive path.

Drive paths for the scan host If a drive has multiple paths that are configured on the selected scan host, EMM selects a scan path as follows: ■

The first local device path it finds in its database in the UP state.

■

The first NDMP-attached drive path it finds in its database in the UP state.

Device allocation host The device allocation host is another name for the EMM server, when the EMM server performs device allocation tasks for Shared Storage Option. EMM manages the following: ■

All drive allocations

■

All configured devices

■

All media servers and their current status (online, offline).

135

136 Shared Storage Option Reference Shared Storage Option components

Chapter

17

Troubleshooting the Shared Storage Option This section includes the following: ■

Lists of guidelines (“Hardware configuration guidelines” on page 137 and “Configuration guidelines” on page 138).

■

Operating system references (“Operating system help” on page 139).

■

Common problems (“Common configuration issues with Shared Storage Option” on page 139).

■

FAQs that may help you resolve any Shared Storage Option issues (“Frequently asked questions about Shared Storage Option” on page 140).

Hardware configuration guidelines ■

If you use SAN hardware from multiple vendors, problems may occur. Always use a SAN configuration and firmware levels that the hardware vendor supports.

■

Consult SAN device, HBA, and operating system documentation to determine how to configure operating system tape drivers and passthru drivers to detect your SAN devices.

■

Check your hub timer settings.

■

Use hard arbitrated loop physical addresses rather than soft addresses. Consult with hardware suppliers to verify the recommended usage of their products.

■

Check the firmware levels of all your Fibre Channel hardware (for example, bridges). Use the most recent firmware level that is known to operate with other SAN hardware devices.

138 Troubleshooting the Shared Storage Option Configuration guidelines

■

Try to duplicate SAN issues and problems using commands and utilities on the host operating system.

■

Test both backup and restore capabilities. Backup jobs may complete successfully, but the data may be corrupted. For example, incorrect switch settings may cause problems.

■

Ensure your hardware and SAN configuration are operational and stable before adding Shared Storage Option software. Test backup and restore capabilities with dedicated tape drives before configuring them as shared drives.

■

For large configurations, begin drive sharing with a few tape drives and two or three media servers (or NetBackup SAN media servers).

■

Configuration and troubleshooting processes are easier on smaller configurations. If possible, create multiple and independent Shared Storage Option configurations with subsets of servers sharing subsets of SAN-attached drives.

■

Use the correct boot order for your Fibre Channel hardware, as follows. Some devices take a while to completely boot. Watch for any indicator lights to become green. ■

Robots or drives

■

Bridges

■

Hubs or switches

■

Hosts

Configuration guidelines Because of the potential for device identification problems in an Shared Storage Option configuration, Symantec recommends the following: ■

Use the Device Configuration Wizard to configure Shared Storage Option.

■

With the Device Configuration wizard, you should configure all shared drives from one host (usually the master server). Launch the wizard only once with the current host set to the master server. You then indicate a list of media servers or NetBackup SAN media servers (in the Device Hosts screen). The wizard configures devices on all of the media servers you selected, and these hosts read the shared configuration information.

Troubleshooting the Shared Storage Option Operating system help

Operating system help

If errors occur during the installation or configuration of the shared devices and you suspect problems with the operating system, refer to the following: ■

Operating system logs, as described in the operating system documents.

■

NetBackup logs.

■

Operating system man pages (UNIX or Linux servers only).

■

The NetBackup Device Configuration Guide.

Common configuration issues with Shared Storage Option ■

Incompatible or outdated firmware or drivers in a hub, switch, HBA, or bridge.

■

The JNI HBA fail-over value was not set to zero to avoid I/O hangs (a bridge or HBA vendor fix).

■

An HBA with SCSI-3 protocol that is not compatible with the operating system drivers.

■

Cluster configurations that are not supported.

■

Devices that only work on a Fibre Channel arbitrated loop.

■

Did not verify that Shared Storage Option has been enabled on each server. To enable Shared Storage Option, enter the Shared Storage Option license key).

■

Did not verify that Shared Storage Option has been installed correctly. You can check keys by using the license key dialog available from the NetBackup Help menu on Windows, UNIX, and Linux servers.

■

Did not configure all of Shared Storage Option from the master server. All configuration should be done from the master server, not from a media server (or SAN media server).

■

Did not configure the same robot control host on every host. Remember that except for ACS and TLM robot types, only one host controls the robot.

■

In the Device Configuration wizard, you did not select the appropriate device hosts, including the host with robotic control.

■

Created inconsistent configurations by using tpconfig to configure Shared Storage Option rather than the Device Configuration wizard. The wizard coordinates configuration with all hosts that share the drives.

139

140 Troubleshooting the Shared Storage Option

Frequently asked questions about Shared Storage Option

■

Fibre Channel connections to the drives and the robots cause increased complexity in a NetBackup device configuration. On some operating systems, the use of SCSI-to-fibre bridges may result in inconsistencies in the device paths when you reboot a host. After a reboot of the host, the device configuration should be verified.

■

Inconsistent names across all systems that share the drives.

■

Did not test the drive paths on every media server.

■

Did not define NetBackup storage units for each media server or did not define a storage unit that allows any media server.

■

If you interrupt the data path while backup data is transferred, the NetBackup job fails. It can fail with media write errors or it may hang and have to be terminated manually.

■

Did not use Berkeley-style close on the tape path (UNIX or Linux servers only)

■

For more information on the following configuration tasks, see the Solaris chapter of the NetBackup Device Configuration Guide. Forgot to add tape configuration list entries in /kernel/drv/st.conf (if needed). Did not define configuration entries for expanded targets and LUNs in sg.links and sg.conf files. If you see problems with the entries in the /etc/devlink.tab file (created from sg.links). Check the following: ■

The first entry uses hexadecimal notation for the target and LUN. The second entry uses decimal notation for the target and LUN.

Use a single tab character between the entries not a space or a space and a tab character. Did not configure the operating system to force load the sg/st/fcaw drivers. ■

Frequently asked questions about Shared Storage Option Q. What combinations of SAN hardware components are supported for Shared Storage Option? A. Shared Storage Option works with many hardware combinations. Symantec has an open policy on hardware support for Shared Storage Option. Consult your hardware suppliers to verify the interoperability of their products. A list of SAN components that have been tested with NetBackup is available on the Symantec support Web site:

Troubleshooting the Shared Storage Option Frequently asked questions about Shared Storage Option

http://entsupport.symantec.com

Q. If NetBackup allocates four drives to a server and it finishes with two of the drives, does NetBackup reallocate the two drives if another server requests drives? Or does NetBackup wait until the backup schedule that uses the four drives is completely finished before it reallocates the drives? A. The two available drives are reallocated and used. NetBackup monitors drive status and notifies the NetBackup scheduler of drive availability. Q. Does NetBackup Shared Storage Option use IP protocol or SCSI protocol? A. Both. IP protocol is used to provide coordination between servers. Shared Storage Option uses SCSI protocol (SCSI reserve) as an added layer of protection.

141

142 Troubleshooting the Shared Storage Option Frequently asked questions about Shared Storage Option

Section

IV

SAN Client and Fibre Transport

■

“Introduction” on page 145

■

“Preparing the SAN” on page 149

■

“Installing SAN clients and Fibre Transport” on page 153

■

“Configuring SAN clients and Fibre Transport” on page 157

■

“Managing SAN clients and Fibre Transport” on page 175

144

Chapter

18

Introduction NetBackup SAN Client and Fibre Transport provide a high-performance transport mechanism between NetBackup clients and NetBackup media servers. For more information, see: ■

“Overview” on page 145

■

“Clustering” on page 146

■

“NetBackup Release Notes” on page 147

For information about how to install and use SAN clients and Fibre Transport, see: ■

“Preparing the SAN” on page 149

■

“Installing SAN clients and Fibre Transport” on page 153

■

“Configuring SAN clients and Fibre Transport” on page 157

■

“Managing SAN clients and Fibre Transport” on page 175

Overview NetBackup Fibre Transport is a method of data transfer that 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 supports multiple, concurrent logical connections. The NetBackup systems that support Fibre Transport contain Fibre Channel HBAs that are dedicated to FT communication. NetBackup server and client administration occurs over the LAN not the SAN. Throughout this documentation, Fibre Transport connections between NetBackup clients and NetBackup servers are referred to as FT pipes.

146 Introduction

Clustering

SAN client A NetBackup SAN client is a NetBackup client on which the Fibre Transport service is activated. The SAN client is similar to the SAN media server that is used for the Shared Storage Option. 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 is a system that has critical data that requires high bandwith for backups. A SAN client backs up its own data. 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. A standard HBA initiator-mode driver resides on the SAN clients.

FT 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. On the FT media servers, 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 pipe. It also manages the target mode driver for the host bus adaptors.

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

Clustering The SAN client can be in a cluster and can host clustered applications. The FT client service and the Symantec PBX service must run on all failover nodes. The SAN client OS on every node must detect the FT media server target mode driver.

Introduction NetBackup Release Notes

Backup policy references to client machines can be to aliases or dynamic application cluster names. SAN client application cluster information is updated every 5 minutes.

NetBackup Release Notes For information about supported systems and peripherals, limitations, and operational notes, see the NetBackup Release Notes.

147

148 Introduction NetBackup Release Notes

Chapter

19

Preparing the SAN Before you can configure and use the NetBackup Fibre Transport mechanism, the SAN must be configured and operational. Instructions for how to configure and manage a SAN are beyond the scope of the NetBackup documentation. However, the following subsections explain what is required for the SAN so that the SAN is prepared to work with the FT mechanism. The tasks to prepare the SAN are separate from the tasks to install and configure NetBackup. A network administrator or storage administrator can prepare the SAN, and a NetBackup administrator can install and manage NetBackup.

Zoning your SAN The Fibre Transport (FT) devices on the NetBackup media servers are the resources that operating systems monitor and manage. The FT devices on the media servers appear as pseudo tape devices to the SAN clients. Without zoning, each NetBackup SAN client host bus adapter (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. You must use physical port ID or World Wide Port Name (WWPN) to specify the media server HBA ports that connect to the SAN clients. The target mode device names on the media servers are not unique because they are derived from the HBA WWPN. To promote multistream throughput, each SAN client in a zone should detect all target mode devices of the media server HBA ports in the zone. If the storage is connected to a SAN, Symantec recommends that you create a backup storage zone that includes only the NetBackup media servers and the storage. A backup storage zone prevents that traffic from using the bandwidth that may be required for other SAN activity. Therefore, you should plan and define your SAN zones so that:

150 Preparing the SAN

Installing HBAs for Fibre Transport

■

The NetBackup media servers and the storage are in a zone.

■

The NetBackup SAN clients and the NetBackup media servers are in a separate zone. That is, 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 HBAs on other hosts.

Installing HBAs for Fibre Transport The Fibre Channel host bus adapter (HBA) and driver requirements differ on the

SAN clients and on the NetBackup FT media servers.

For information about supported HBAs, see the NetBackup Release Notes.

HBAs on SAN clients The HBAs on the SAN clients can be any supported Fibre Channel HBA. 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.

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

For the connections to the SAN clients, a supported QLogic HBA. For these HBAs, you must configure them to use the NetBackup target mode driver. For instructions, see “Configuring the FT media server” on page 157.

■

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 default driver and utilities. If you use QLogic HBAs to connect to the storage, you should install the QLogic driver for the HBA. The HBA ports that connect to the storage must remain in the default initiator mode.

Preparing the SAN Selecting the ports

Selecting the ports

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

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.

Connecting the Fibre NetBackup supports the following for Fibre Transport: ■

Node port (N_Port) switched configuration

■

Direct connect Fibre Channel arbitrated loop (FC-AL) configuration

To connect the NetBackup media servers and SAN clients to your SAN, follow the procedures in one of the following subsections.

N_Port switched configuration The following is an overview of how to connect the media servers and clients to a SAN switch: 1

Connect the HBA port on the NetBackup FT media server to a Fibre Channel switch port.

2

Connect each SAN client HBA port to ports on the same Fibre Channel switch.

3

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 clients by either port ID or WWPN. However, if you use one method only, zone definition and management is easier.

151

152 Preparing the SAN Connecting the Fibre

Direct connect FC-AL configuration You can use Fibre Channel Arbitrated Loop (FC-AL) to connect a NetBackup media server HBA port directly to a NetBackup SAN client HBA port. Note: FC-AL hubs are not supported.

Chapter

20

Installing SAN clients and Fibre Transport No special installation is required for the core NetBackup Fibre Transport components. The components are installed when you install NetBackup media servers and clients. However: ■

The NetBackup master server and all NetBackup media servers that use the feature must be at NetBackup 6.5 or later.

■

You must activate the feature by entering the SAN Client license key on the NetBackup master server. If the NetBackup Enterprise Media Manager server runs on a host other than the master server, also install the license key on that host. Normally, the EMM server runs on the NetBackup master server host, but it can run on any NetBackup media server. If the license key expires or is unavailable (such as in a disaster recovery situation), backups and restores occur over the LAN.

■

You must install the Symantec PBX service on the SAN clients that are UNIX and Linux systems. For instructions, see “Installing PBX on the SAN clients” on page 154.

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 a SAN-attached media server. Data transfer consumes system resources and severely degrades NetBackup management performance.

154 Installing SAN clients and Fibre Transport Installing PBX on the SAN clients

■

Do not use the host on which the NetBackup Enterprise Media Manager server runs as a SAN-attached media server. Data transfer consumes system resources and severely degrades EMM performance. Normally, the EMM server runs on the NetBackup master server host, but it can run on any NetBackup media server.

For NetBackup installation instructions, see: ■

NetBackup Installation Guide for UNIX and Linux

■

NetBackup Installation Guide for Windows

For information about upgrades and uninstalls, see: ■

“Upgrading SAN clients and Fibre Transport” on page 154

■

“Uninstalling SAN clients and Fibre Transport” on page 155

Installing PBX on the SAN clients Applies to UNIX and Linux clients only. PBX is installed automatically on Windows clients. You must install the Symantec Private Branch eXchange (PBX) service on each UNIX or Linux SAN client. PBX provides socket communication between the NetBackup SAN client and the NetBackup master server and EMM server. Install PBX from the Infrastructure Core Services CD that is included in your NetBackup installation package. For more information about PBX, see the documentation on the Infrastructure Core Services CD. To install PBX

1

Insert the Infrastructure Core Services CD into the CD drive.

2

Mount the CD and run the installics program on the root directory of the CD.

3

Choose the option to install PBX.

Upgrading SAN clients and Fibre Transport When you upgrade NetBackup, all components are upgraded including the SAN

client and Fibre Transport components.

For NetBackup upgrade installation instructions, see:

■

NetBackup Installation Guide for UNIX and Linux

■

NetBackup Installation Guide for Windows

Installing SAN clients and Fibre Transport Uninstalling SAN clients and Fibre Transport

Uninstalling SAN clients and Fibre Transport

You can: ■

Disable the SAN client FT service. To do so, see “Disabling the SAN client service” on page 155.

■

Convert a NetBackup FT media server to a NetBackup media server. To do so, see “Removing the FT services and drivers” on page 155.

Disabling the SAN client service You can disable the SAN Client Fibre Transport Service. If you do, the NetBackup client then does not function as a SAN client. To disable the NetBackup SAN client service 1

Run the following command on the client: UNIX and Linux: /usr/openv/netbackup/bin/bpclntcmd -sanclient 1

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

2

Boot the computer.

The command resides in the following directories:

■

/usr/openv/netbackup/bin (UNIX and Linux)

■

install_path\VERITAS\NetBackup\bin (Windows)

Removing the FT services and drivers You can remove the operating system start-up scripts and the NetBackup nbhba

driver from an FT media server. The FT media server then does not support

NetBackup Fibre Transport.

To do so, use the nbftsrv_config -d command and option. The process also

removes the nbhba driver and exits nbhba mode.

After you run the nbftsrv_config -d command, verify that the following

start-up scripts were removed:

■

Linux: /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

155

156 Installing SAN clients and Fibre Transport Uninstalling SAN clients and Fibre Transport

■

Solaris: /etc/rc2.d/S21nbftserver

/etc/rc0.d/K03nbftserver

/usr/kernel/drv/windrvr6.conf

/usr/kernel/drv/sparcv9/windrvr6

/usr/kernel/drv/sparcv9/ql2300_stub

If they were not removed, delete them.

The nbftsrv_config script resides in the following directory:

/usr/openv/netbackup/bin/admincmd

Caution: 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.

Chapter

21

Configuring SAN clients and Fibre Transport The SAN must be zoned and operational before you configure NetBackup Fibre Transport. The following are the tasks to configure NetBackup Fibre Transport on the NetBackup media servers and the SAN clients. Do the following tasks in order: ■

“Configuring the FT media server” on page 157

■

“Configuring firewalls on SAN clients” on page 166

■

“Configuring SAN client drivers” on page 166

■

“Configuring the SAN client FT service” on page 167

■

“Configuring global FT properties for SAN clients” on page 170

Configuring the FT media server 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. On NetBackup FT media servers, QLogic Fibre Channel host bus adapter (HBA) ports are used to connect to the NetBackup SAN clients. Those ports must operate in target mode; NetBackup provides a special target mode driver for those ports. The target mode driver replaces the default, initiator mode driver. (The target mode driver (a NetBackup FT device) appears as an ARCHIVE Python tape device during SCSI inquiry. However, it is not a tape device and does not appear as a tape device in NetBackup device discovery.) The following are the two main parts of FT media server configuration:

158 Configuring SAN clients and Fibre Transport Configuring the FT media server

■

The HBA configuration installs a driver that lets NetBackup read and modify the device ID in NVRAM of the QLogix 234x HBA ports. You must modify the HBA ports that you want to operate in target mode. The ports must be on a supported QLogic HBA. During this process, the computer is in nbhba mode. For the procedures, see “Configuring the HBAs” on page 158.

■

The FT services configuration installs drivers, start-up scripts, and configures the operating system to start the FT server. When the FT server starts, the NetBackup target mode driver binds to the ports that are marked. Also, the nbhba mode ends. For the procedures, see “Configuring the FT services” on page 163.

Configuring the HBAs To configure the HBAs for target mode, you mark the ports of the QLogic HBAs that you want to operate in target mode. For procedures, see the following two sections: ■

“Starting nbhba mode” on page 161

■

“Marking the HBA ports” on page 162

Caution: Before you configure the HBAs, read the following subsections. They provide information that may help you avoid serious problems. Before you configure the HBAs, read the following important introductory sections: ■

“FC attached devices” on page 158

■

“How to identify the HBA ports” on page 159

■

“The HBAs that connect to the storage” on page 160

FC attached devices Caution: Do not configure HBAs on a computer that has a boot device that is attached to a QLogic 234x HBA. 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. In nbhba mode, all devices that are attached to QLogic 234x 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.

Configuring SAN clients and Fibre Transport Configuring the FT media server

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 boot device. Then, you can install them in the NetBackup FT media servers and configure the FT services. To remove the nbhba driver from the media server on which you configured the HBAs, see “Removing the FT services and drivers” on page 155. The process also ends nbhba mode on that computer.

How to identify the HBA ports The NetBackup nbhba command that marks the HBA ports requires the port World Wide Name (WWN). (The port WWN also may be known as the World Wide Port Name (WWPN).) If the computer on which you mark ports contains multiple HBAs, it may be difficult to determine how the WWNs relate to the HBAs. 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. Caution: 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 include 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.

■

Solaris 10 native drivers let you list WWNs by using the fcinfo hba-port command.

■

The output of the NetBackup nbhba -l command may provide enough information to determine different cards. (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

159

160 Configuring SAN clients and Fibre Transport Configuring the FT media server

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. The -L option provides verbose output, as in the following example: /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

Device ID = 2312

World Wide Name = 21:00:00:E0:8B:8F:28:7B

Model Name = "QLA2342 "

Port = 0

Mode = initiator (designated for other use)(101)

HBA Port #4

Device ID = 2312

World Wide Name = 21:01:00:E0:8B:AF:28:7B

Model Name = "QLA2342 "

Port = 1

Mode = initiator (designated for other use)(101)

■

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.

The HBAs that connect to the storage The HBA ports that connect to the storage must use the default initiator mode driver. Those ports can be on any supported Fibre Channel HBA. Target mode applies only to QLogic HBAs; the target mode configuration process affects only QLogic HBA ports. If you also use QLogic HBAs to connect to the storage, those HBA ports must remain in the default, initiator mode.

Configuring SAN clients and Fibre Transport Configuring the FT media server

Starting nbhba mode The NetBackup nbhba command marks the ports for the target mode driver. The command functions only in nbhba mode. Therefore, you must start nbhba mode before you can mark ports. In nbhba mode, a NetBackup driver (ql2300_stub) binds to all QLogic 234x HBA ports in the computer. The 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. In nbhba mode, all devices that are attached to QLogic HBA ports are unavailable. To start nbhba mode, see: ■

“To start nbhba mode on Linux” on page 161

■

“To start nbhba mode on Solaris” on page 161

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

4

Go to “Marking the HBA ports” on page 162.

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"

161

162 Configuring SAN clients and Fibre Transport

Configuring the FT media server

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

Go to “Marking the HBA ports” on page 162.

Marking the 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. For procedures, see: ■

“To mark ports” on page 162

■

“To revert to the initiator mode driver” on page 163

You must be the root user. To mark ports 1

Invoke the nbhba command with the -l option to display the QLogic HBA ports on the server. The following is an example; output on your system may differ: /usr/openv/netbackup/bin/admincmd/nbhba 1 2312 21:00:00:E0:8B:83:9D:A1 "QLA2342 2 2312 21:01:00:E0:8B:A3:9D:A1 "QLA2342 3 2312 21:00:00:E0:8B:8F:28:7B "QLA2342 4 2312 21:01:00:E0:8B:AF:28:7B "QLA2342

-l

" 0 " 1 " 0 " 1

0 0 0 0

101

101

101

101

This output shows two, two-port HBAs in initiator mode: the second rightmost column shows 0, and the rightmost column does not begin with 8. 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:83:9D:A1 -mode target

nbhba -modify -wwn 21:01:00:E0:8B:A3:9D:A1 -mode target

3

To verify the changes, display the list of the HBA cards on the server. The following is an example; output on your system may differ:

Configuring SAN clients and Fibre Transport Configuring the FT media server

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

-l

" 0 " 1 " 0 " 1

1 1 0 0

8101

8101

101

101

The rightmost two columns show that the ports 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.

5

If necessary, connect the HBAs to the SAN.

6

Go to “Configuring the FT services” on page 163.

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 FT services Two services (nbftsrvr and nbfdrv64) comprise the NetBackup FT server that runs on media servers. You must configure the operating system on the NetBackup FT media servers so the FT services start up. You must configure the FT media server start-up before you configure the SAN clients. The FT server must run on the media servers so that the client operating systems discovers the target mode driver (the FT device). The nbftsrv_config script configures FT server start-up. In this process, the script: ■

Ends the nbhba mode on the computer (if it was in nbhba mode)

■

Installs the required drivers

■

Installs the FT server start-up scripts

■

Starts the FT server on Linux

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. Configure the FT services on every NetBackup media server that connects to SAN clients. For procedures, see: ■

“To configure FT services on Linux” on page 164

163

164 Configuring SAN clients and Fibre Transport Configuring the FT media server

■

“To configure FT services on Solaris” on page 165

You must be the root user. To configure FT 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

3

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

Adding qla2300.

Configuring SAN clients and Fibre Transport Configuring the FT media server

165

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.

To configure FT 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.

166 Configuring SAN clients and Fibre Transport

Configuring firewalls on SAN clients

2

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

Configuring firewalls on SAN clients NetBackup SAN clients require connectivity to the NetBackup master server and

the NetBackup Enterprise Media Manager server.

Therefore, you must ensure that any firewall (software or hardware) allows the

clients to communicate with the NetBackup master server and the EMM server.

Normally, the NetBackup master server hosts the EMM server, so you may only

have to allow communication with one system.

Configuring SAN client drivers SAN clients use tape drivers and SCSI pass-through methods (except Microsoft Windows) for Fibre Transport traffic to NetBackup FT media servers. You may have to configure the SAN client operating systems so they use the proper driver and pass-through paths. The SAN client operating system must recognize the media server FT devices as ARCHIVE Python tape devices. How to configure operating system drivers and paths is beyond the scope of the NetBackup documentation. However, for guidance about the NetBackup requirements, see the following subsections and the NetBackup Device Configuration Guide. Some operating systems require specific patch and driver updates. For information about them, see the NetBackup Release Notes.

AIX On AIX systems, NetBackup Fibre Transport uses the standard tape driver. It should work without modification, and AIX should detect the target mode drivers on the FT media servers.

HP-UX HP-UX SAN client systems require the sctl pass-through driver and device files. For information about how to configure HP-UX systems, see the NetBackup Device Configuration Guide.

Configuring SAN clients and Fibre Transport Configuring the SAN client FT service

Linux Linux SAN clients require the SCSI Generic (sg) driver and pass-through device files. For information about how to configure the pass-through driver on Linux systems, see the NetBackup Device Configuration Guide.

Solaris On Solaris SAN clients, you must configure the Solaris operating system so that it recognizes the FT devices on the NetBackup media servers. For information about how to do so, see the NetBackup Device Configuration Guide.

Windows Symantec recommends that you install the Symantec Device Drivers for Veritas

NetBackup Windows Servers.

If the Symantec device drivers are installed, the Windows SAN clients should

recognize the media server FT devices as ARCHIVE Python devices. If they are

not installed, the Windows SAN client may categorize the FT devices as

unknown. If the devices are unknown, the SAN client FT service writes to the

SCSI ports of the unknown devices.

For information about how to install the Symantec drivers, see the NetBackup

Device Configuration Guide.

Also, ensure that your HBAs use the correct driver revision level. For driver

revision levels, see the NetBackup Release Notes.

Configuring the SAN client FT 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. Caution: 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. To configure a NetBackup client to be a SAN client

1

Verify that the Symantec PBX service is active on the client:

■

On UNIX and Linux systems, run the bpps -x command and verify that the pbx_exchange process is active.

167

168 Configuring SAN clients and Fibre Transport Configuring the SAN client FT service

■

2

On Windows systems, use the Computer Management console to verify that the Symantec Private Branch Exchange service is active.

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\VERITAS\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 bp.start_all command to start the client FT service.)

■

AIX, HP-UX, and Solaris: run the bp.start_all command. The command resides in the following directory: /usr/openv/netbackup/bin

■

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. For more information, see “SAN client FT service validation” on page 181. 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 that the: ■

Fibre Channel driver is installed on the SAN client.

■

SAN client HBA port is active on the Fibre Channel switch.

■

Media server HBA port is active on the Fibre Channel switch.

■

SAN client is logged into the Fibre Channel switch name server.

■

FT media server is logged into the Fibre Channel switch name server.

■

FT media server port is zoned with the SAN client port.

Zone is included in the active configuration.

Alternatively, you can try a scan operation for FT devices on a client

system. For procedures, see “Rescanning SAN clients” on page 176.

■

Configuring SAN clients and Fibre Transport Configuring FT properties

Configuring SAN clients in a cluster The SAN client FT service is not a cluster application. To protect a SAN client with a cluster, you must configure NetBackup so that FT connections exist to every node. First, install the NetBackup client software on each failover node. Second, configure the SAN client on each node according to the instructions in this chapter. Ensure that the FT service is active on all of the failover nodes. Finally, on the NetBackup master server, use the nbemmcmd command to register the virtual node with the clients, as follows: To define NetBackup clustered clients 1

Add the virtual name to the EMM database: nbemmcmd –addhost –machinename virtual_name –machinetype

app_cluster

2

Add the virtual name to all clients in the node. For every client in the node, run the following command. nbemmcmd –updatehost –add_server_to_app_cluster –machinename

client_name –clustername virtual_name

The SAN client service is not a clustered application. Therefore, SAN client commands and user interface operations only apply to the physical node name and not the virtual one. The nbemmcmd resides in: ■

UNIX: /usr/openv/netbackup/bin/admincmd

■

Windows: install_path\Program Files\VERITAS\NetBackup\bin\admincmd

Configuring FT properties You can configure Fibre Transport properties for your NetBackup environment: ■

Global FT properties for SAN clients. See “Configuring global FT properties for SAN clients” on page 170.

■

FT properties for media servers. See “Configuring FT properties for media servers” on page 170.

■

FT properties for SAN clients. See “Configuring FT properties for SAN clients” on page 171 Alternatively, you can configure FT properties for clients by following the instructions in “Configuring SAN client FT usage preferences” on page 171.

169

170 Configuring SAN clients and Fibre Transport

Configuring FT properties

Configuring global FT properties for SAN clients NetBackup master server FT properties apply to all SAN clients unless you override them for specific clients. The properties include: ■

When to use an FT connection

■

How long to wait for an available FT pipe before NetBackup uses a LAN connection

To configure global FT properties for SAN clients 1

In the NetBackup Administration Console, expand NetBackup Management > Host Properties.

2

Select Master Servers.

3

In the Details pane, double-click on the name of the master .

4

In the host properties dialog box, click Fibre Transport in the tree pane.

5

Configure the properties. For a description of the properties, see “Fibre Transport properties” on page 173.

Configuring FT properties for media servers You can configure the maximum number of FT connections that are allowed for a specific media server or for specific media servers. To configure FT properties for media servers 1

In the NetBackup Administration Console, expand NetBackup Management > Host Properties.

2

Select Media Servers.

3

In the Details pane, double-click on the name of the media server for which you want to configure properties. To configure properties for more than one media server, select the media servers and then click Action > Properties.

4

In the host properties dialog box, click Fibre Transport in the tree pane.

5

Configure the property. For a description of the property, see “Maximum concurrent FT connections” on page 174.

Configuring SAN clients and Fibre Transport Configuring FT properties

Configuring FT properties for SAN clients FT properties for SAN clients override the global FT properties for the SAN clients that are configured on the master server. You can configure SAN client properties by following these procedures or the procedures in “Configuring SAN client FT usage preferences” on page 171. Configure client FT properties only if you want to override the global properties for specific clients. The properties include: ■

When to use an FT connection

■

How long to wait for an available FT pipe before NetBackup uses a LAN connection

■

Whether to use the global FT properties for SAN clients that are specified on the master server. By default, the global properties are used.

To configure FT properties for SAN clients 1

In the NetBackup Administration Console, expand NetBackup Management > Host Properties.

2

Select Clients.

3

In the Details pane, double-click on the name of the client for which you want to configure properties. To configure properties for more than one client, select the clients and then click Action > Properties.

4

In the host properties dialog box, click Fibre Transport in the tree pane.

5

Configure the properties. For a description of the properties, see “Fibre Transport properties” on page 173.

Configuring SAN client FT usage preferences SAN client usage preferences override the global FT properties for the SAN clients that are configured on the master server. You can configure the usage preferences by following these procedures or the procedures in “Configuring FT properties for SAN clients” on page 171. Configure client FT usage preferences only if you want to override the global properties for specific clients. The properties include: ■

When to use an FT connection

■

How long to wait for an available FT pipe before NetBackup uses a LAN connection

171

172 Configuring SAN clients and Fibre Transport Configuring FT properties

■

Whether to use the global FT properties for the SAN clients that are specified on the master server. By default, the global properties are used.

To configure FT usage preferences for a client by using the Devices node 1

In the NetBackup Administration Console, expand Media and Device Management > Devices.

2

Select SAN Clients in the tree pane.

3

Select a client in the Details pane.

4

Selection Actions > SAN Client Usage Preferences.

5

In the Fibre Transport Usage Preferences dialog box, configure the properties.

For a description of the usage preferences, see the following. ■

“Use defaults from the master server configuration” on page 174

■

“Preferred” on page 173

■

“Always” on page 174

■

“Never” on page 174

Configuring SAN clients and Fibre Transport Configuring FT properties

Fibre Transport properties The Fibre Transport master server properties apply to the SAN clients whose

preferences have not been set explicitly.

The Fibre Transport media server property applies to the SAN clients for

selected media servers.

The Fibre Transport client properties apply to the selected SAN clients. The

defaults for clients are the property settings of the master server.

An FT device is the target mode driver on a NetBackup FT media server. An FT

pipe is the logical connection that carries backup and restore data between an

FT media server and a SAN client.

For more information about NetBackup Fibre Transport, see the NetBackup

Shared Storage Guide.

Figure 21-1

Master server Fibre Transport host properties

Preferred The Preferred property specifies to use an FT pipe if an FT device 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.

173

174 Configuring SAN clients and Fibre Transport Configuring FT properties

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 pipe always 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 active and available. If no FT device exists, NetBackup uses the LAN. 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.

Maximum concurrent FT connections Media server property only. The Maximum concurrent FT connections property specifies the number of FT

connections to allow to a media server.

The default is four times the number of HBA target ports (maximum of 16).

Use defaults from the master server configuration Client property only. The Use defaults from the master server configuration property specifies to use the properties that are configured on the master server.

Chapter

22

Managing SAN clients and Fibre Transport The following are tasks for managing NetBackup Fibre Transport and SAN clients: ■

“Managing FT services” on page 175

■

“Viewing FT job details” on page 177

■

“Viewing FT pipe activity” on page 177

■

“Adding a SAN client” on page 178

■

“Deleting a SAN client” on page 179

■

“Troubleshooting Fibre Transport” on page 179

Managing FT services You can do the following to manage the Fibre Transport (FT) connections in your NetBackup environment: ■

Enable or disable FT services on media servers

■

Rescan SAN clients to update connection information

Enabling or disabling the FT 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.

176 Managing SAN clients and Fibre Transport Managing FT services

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.

Caution: 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). To enable or disable FT services 1

In the NetBackup Administration Console, expand Media and Device Management > Devices.

2

Select Media Server in the tree pane.

3

Select an FT media server in the Details pane.

4

Click either Actions > Enable FT Services or Actions > Disable FT Services.

Rescanning SAN clients You can initiate an operating system level scan of a SAN client and update 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 reboot and you do not reboot it). Depending on the operating system capabilities and the HBA driver and its settings, the scan may search for new Fibre Channel devices. To rescan SAN clients 1

In the NetBackup Administration Console, expand Media and Device Management > Devices.

2

Select SAN Clients in the tree pane.

3

Select a client in the Details pane.

4

Click Action > Rescan SAN Client FT Devices.

5

In the Rescan SAN Client dialog box, monitor the status of the operation: ■

Initiated

■

Client system must be rebooted

■

Failure

Managing SAN clients and Fibre Transport Viewing FT job details

Viewing FT 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: ■

Queuing for FT transport

■

Allocated FT transport

■

Opening FT connection

■

Closing FT connection

To view job details Double-click on 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 FT pipe activity You can view the current activity between FT media servers and SAN clients. The following two views are available: ■

The media server view shows all of the inbound backup (and outbound 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.

■

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.

To view FT pipe activity from the media server perspective 1

In the NetBackup Administration Console, expand Media and Device Management > Devices.

177

178 Managing SAN clients and Fibre Transport Adding a SAN client

2

Select Media Server in the tree pane.

3

Select an FT media server in the Details pane.

4

Click View > FT Connections. The Media Server Fibre Transport View dialog box shows the connection activity for the media server.

To view FT pipe activity from the client perspective 1

In the NetBackup Administration Console, expand Media and Device Management > Devices.

2

Select SAN Clients in the tree pane.

3

Select a client in the Details pane.

4

Click View > FT Connections. The SAN Client Fibre Transport View dialog box shows the connection activity for the 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 Administration Console. The SAN client must be configure 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, select Media and Device Management.

2

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

Managing SAN clients and Fibre Transport Deleting a SAN client

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 FT service must be inactive. To disable the FT service, see

“Disabling the SAN client service” on page 155.

To delete a SAN client

1

In the NetBackup Administration Console, select Media and Device

Management > Devices > SAN Clients.

2

Select a client in the details pane.

3

Click Edit > Delete.

Troubleshooting Fibre Transport For troubleshooting help, see the following: ■

“SAN client service does not start” on page 179

■

“Stopping and starting FT services” on page 180

■

“Media server FT device is offline” on page 180

■

“No FT devices discovered” on page 181

■

“SAN client FT service validation” on page 181

■

“SAN client does not select Fibre Transport” on page 182

■

“Viewing FT logs” on page 183

■

“For more troubleshooting information” on page 183

SAN client service does not start If the SAN Client Fibre Transport Service (nbftclnt) does not start on UNIX or Linux systems, one possible cause may be the NetBackp configuration 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.

179

180 Managing SAN clients and Fibre Transport Troubleshooting Fibre Transport

Stopping and starting FT 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 following FT service runs on SAN clients:

■

nbftclnt

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

Symantec support engineer may direct you to stop and restart services for

troubleshooting purposes.

For information about how to stop and start services, see “Enabling or disabling

the FT services” on page 175.

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.

Caution: 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.

Media server FT device is offline If NetBackup shows that a media server FT device is offline, it means that 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: ■

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.

Managing SAN clients and Fibre Transport Troubleshooting Fibre Transport

■

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. For an explanation of this issue, see “SAN client FT service validation” on page 181.

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.

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

To try to start the services, see “Stopping and starting FT services” on page 180.

If the services do not start, examine the log files for those services to determine

why they do not start. For information about how to view the log files, see “Viewing FT logs” on page 183.

No FT devices discovered If a “No FT devices discovered” message appears in the NetBackup logs on the SAN clien, 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.

SAN client FT service validation The SAN Client Fibre Transport Service (nbftclnt) validates the client system’s kernel and driver stack when it starts and during device discovery. Validation verifies that the kernel and the drivers are at supported levels. If validation succeeds, the SAN client supports FT pipe transfers; FT pipe transfer can occur. If validation fails: ■

The SAN Client Fibre Transport Service writes check driver messages in its log file.

181

182 Managing SAN clients and Fibre Transport

Troubleshooting Fibre Transport

■

NetBackup sets the FT device status to offline for all FT devices in the client’s SAN zone. (For other clients in the zone that pass the validation, the FT devices are online.)

■

FT pipe transfers cannot occur.

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 - check driver

VerifyCheckConditions:failed on ; <System Error

Message>

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.

For information about the nbftclnt log file, see “Viewing FT logs” on page 183. 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.

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

Managing SAN clients and Fibre Transport Troubleshooting Fibre Transport

■

To add a fully qualified doman name alias: nbemmcmd -machinealias -addalias -alias

servername.fully.qualified -machinename shortservername

-machinetype media

Viewing FT logs You can monitor Fibre Transport activity and status by viewing the log messages that the FT processes generate. Veritas unified log (VxUL) files use a standardized name and file format for log files. An originator ID identifies the process that writes the log messages. The following are the VxUL originator IDs of the processes that log information about FT activity:

Originator ID

FT processes that use the ID

199

nbftsrvr and nbfdrv64. The media server Fibre Transport services.

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. For information about how to use and manage VxUL logs on NetBackup servers, see the NetBackup Troubleshooting Guide. 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. For more information, see the NetBackup Administrator’s Guide, Volume I.

For more troubleshooting information More troubleshooting information about SAN clients and Fibre Transport is available on the Symantec Enterprise Support Web site in the following Tech Note: http://entsupport.symantec.com/docs/288437

The Tech Note contents are updated when new information is available. The

Tech Note may contain more current information than this guide.

If you need to contact NetBackup Technical Support, the following is the address

for the site:

http://entsupport.symantec.com

183

184 Managing SAN clients and Fibre Transport Troubleshooting Fibre Transport

Index

A ACS or TLM robot types 134

activity

viewing BMR logs 183

Always property in Fibre Transport host

properties 174

Arbitrated Loop Physical Address (ALPA) 137

B bpclntcmd utility 121

C configuring 157

devices 119

D device

configuration wizard 122, 138

drivers 119, 120

files 120

device allocation host 133, 135

device driver install wizard, Windows 167

Disk Type storage unit setting 30, 77

E examples

SAN components 114

SSO components configuration 133

F fibre channel

arbitrated loop 114

hub 114

switch 114

switched fabric 114

Fibre Transport

host properties

Always 174

Maximum concurrent fibre transport connections 174

Never 174

Preferred 173

Use defaults from the master server

configuration 174

firmware levels 120, 137

G get_license_key command 117

H HyperTerminal 120

L license key SSO for Tape 117

license keys 113

logging

originator IDs 183

viewing logs 183

M maximum concurrent drives for backup 122

Maximum concurrent FT connections property 174

Media Server storage unit setting 30, 77

N nbemm 132

nbemm/DA, definition 132

nbhba driver 157

removing 155

NearStore storage units

logging information 50, 97

Never property in Fibre Transport host

properties 174

186 Index

O

U

OpenStorage storage unit 15

originator IDs 183

overview of

shared drives 113

Use defaults from the master server configuration

property 174

P Preferred property in Fibre Transport host

properties 173

R rdevmi 134

removing 155

robot

sharing without SSO 132

S SAN media server 114, 131

SAN Shared Storage Option (see SSO)

scan host 133, 134

SCSI-to-fibre

bridges 120

Servers

SAN media server 114

shared drives (see SSO)

shared drives, definition 131

shared library support 132

shared robots, without SSO 132

shared storage option, key 113

shared_drive_notify script 114

SSO

definition 113

device allocation host 132, 135

Device Allocation Host Summary 128

hardware requirements 113

scan host 133, 134

Shared Drive Summary 128

supported SAN hardware 140

terminology 131

Storage Area Network (SAN) 113, 119, 131, 137

supported

SAN hardware 140

T target mode driver 155, 157

tested SAN components 140

V

Veritas Backup Exec 131

Veritas Storage Migrator 132

viewing FT logs 183

W wizard device configuration 138

shared drive configuration 122