VERITAS NetBackup Advanced Client - Add …docshare01.docshare.tips/files/28416/284169655.pdf ·...

N15273C

September 2005

VERITAS NetBackup™ 6.0 Advanced Client

Quick Start Guide

for UNIX, Windows, and Linux

Disclaimer

The information contained in this publication is subject to change without notice. VERITAS Software Corporation makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. VERITAS Software Corporation shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this manual.

VERITAS Legal Notice

Copyright © 2003 - 2005 VERITAS Software Corporation. All rights reserved. VERITAS, the VERITAS Logo, and NetBackup are trademarks or registered trademarks of VERITAS Software 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.

VERITAS Software Corporation 350 Ellis Street Mountain View, CA 94043 USA Phone 650-527-8000 Fax 650-527-2908 www.veritas.com

Third-Party Copyrights

For a list of third-party copyrights, see the NetBackup Release Notes appendix.

ii NetBackup Advanced Client Quick Start Guide

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .v

Advanced Client Assistance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .v

Chapter 1. Advanced Client Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

Snapshot Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Snapshot Policy Configuration Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Chapter 2. Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Logging Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Hardware Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Chapter 3. Configure a Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Select Advanced Client Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Advanced Client Dialog Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Basic Snapshot Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

FlashBackup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

NAS Snapshot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Instant Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Offhost Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Test Advanced Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Configuration Matrix for Backup Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

iii

Chapter 4. Frequently Asked Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Appendix A. Data Movers (UNIX Clients Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Test the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Third-Party Copy Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Mover.conf file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

3pc.conf file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Diagram of Third-Party Copy Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

iv NetBackup Advanced Client Quick Start Guide

Preface

This guide provides first-time instructions for installing and configuring NetBackup Advanced Client. For background and detailed reference, refer to the NetBackup Advanced Client System Administrator’s Guide.

It is assumed that you understand NetBackup concepts and have experience with NetBackup administration.

Advanced Client Assistance

From the NetBackup Administration Console

For help creating a policy with Advanced Client features, click on the Master Server name at the top of the left pane and click Create a Snapshot Backup Policy.

From the Web (www.support.veritas.com)

For an Advanced Client document containing an up-to-date list of supported operating systems and peripherals, a snapshot/OS compatibility matrix, and configuration notes on supported SAN devices, enter “Advanced client configuration” in the search field. The title of the document is:

NetBackup Advanced Client Configuration and Compatibility

v

Advanced Client Assistance

vi NetBackup Advanced Client Quick Start Guide

Advanced Client Features
1 In brief, Advanced Client features are the following:
Snapshot: a point-in-time disk version of the client’s data, for “hot” backups. NetBackup backs up the data from the snapshot, not directly from the client’s data. Client operations can continue without interruption during the backup. Snapshots are the basis for the other features of Advanced Client.

FlashBackup: combines the speed of raw-partition backups with the ability to restore individual files from the raw partition or drive.

Instant Recovery: makes backups available for quick recovery from a snapshot. Instant Recovery provides three additional types of restore: block-level restore, file promotion, and point in time rollback.

Offhost backup: performs the backup processing on a separate backup agent, greatly reducing the impact on the client’s computing resources ordinarily caused by a local backup. The backup agent can be a data mover (NetBackup Media Server, Third-Party Copy Device, or Network Attached Storage) or an alternate client.

Block level incremental backup (BLI): backs up only changed data blocks of Oracle and DB2 database files. Refer to the NetBackup Oracle or DB2 guide for more details.

Snapshot Selection Advanced Client has a range of snapshot methods for UNIX, Linux, and Windows clients. For most backups, NetBackup can select the snapshot method automatically. Or, you can select the snapshot method yourself by using Advanced Snapshot Options on the policy dialog. The snapshot methods are described in the NetBackup Advanced Client System Administrator’s Guide.

Snapshot Policy Configuration Wizard For help in setting up an Advanced Client policy and selecting a snapshot method, use the Snapshot Policy Configuration wizard in the Administration Console.

1

Terminology

Terminology Advanced Client

Add-on product that includes snapshot backup, FlashBackup, Instant Recovery, offhost backup, and block-level incremental backup.

Copy-on-Write (COW)

One of two types of snapshots (see also mirror). A copy-on-write snapshot creates a block-by-block “account” that describes which blocks in the client data have changed and which have not, from the instant the copy-on-write was activated. NetBackup uses this information to create the backup copy. Other terms and trade names sometimes used for copy-on-write snapshots are space-optimized snapshots, space-efficient snapshots, and checkpoints.

Data mover

The host or other device that manages an offhost backup on behalf of the client (see offhost backup).

Mirror

A disk that maintains an exact copy of another disk. All writes to the original disk are also made to the mirror. Other terms and trade names sometimes used for mirror are full volume mirror, split-mirror, BCV (EMC), and third mirror break-off.

NetBackup Media Server method

An offhost backup method in which data movement is performed by a media server.

Offhost backup

The off-loading of backup processing to a separate backup agent executing on another host. Advanced Client provides these offhost backup options: alternate client backup, NetBackup Media Server, Third-Party Copy Device, and Network Attached Storage.

Snapshot (formerly known as frozen image)

A stable point-in-time version of the client’s data prior to backup. A snapshot makes possible a “hot” backup, minimizing system downtime.

Snapshot method

A set of routines for creating a snapshot. You can select the method, or let NetBackup select it when the backup is started (auto method).

Snapshot mirror (VxVM)

A disk mirror created by the VERITAS Volume Manager (VxVM). This is an exact copy of a primary volume at a particular moment, reproduced on a physically separate device.

2 NetBackup Advanced Client Quick Start Guide

Terminology

Third-Party Copy Device

An offhost method that makes the backup by means of a data mover on the SAN, using the SCSI Extended Copy command. Third-party copy device also refers to the data mover itself, often implemented as part of a bridge, router, or storage device.

Chapter 1, Advanced Client Features 3

Terminology


Installation
2 UNIX
This procedure applies to the Solaris, HP-UX, AIX, and Linux platforms.

1. If you intend to back up clients configured with VxFS or VxVM, or clients in a clustered environment, make sure the file systems, volumes, and/or clustering are correctly configured.

For software requirements, refer to “Features and Required Software” in the NetBackup Advanced Client System Administrator’s Guide.

2. Install the NetBackup 6.0 Enterprise server and client software.

For the installation procedure, see the NetBackup Installation Guide for UNIX.

3. From the NetBackup options CD-ROM, use the NetBackup Add-On Product Software menu to install Advanced Client on the master/media server(s).

4. Distribute Advanced Client software to all currently defined clients by executing the following command:

/usr/openv/netbackup/bin/update_clients -Install_ADC

For complete instructions, and for notes on clustered environments, see the installation chapter of the NetBackup Adanced Client System Administrator’s Guide.

Windows Advanced Client is automatically installed with the Windows NetBackup Enterprise server and client software. The installation procedure is the same as that described in the NetBackup Installation Guide for Windows.

◆ If you intend to back up clients configured with VxVM or clients in a clustered environment, make sure the VxVM volumes and/or clustering are correctly configured.

5

Logging Directories

◆ For Instant Recovery backups of data configured on VxVM volumes on Windows, the VxVM volume names must be 12 characters or fewer.

◆ Provide the Advanced Client license key as required during the installation.

Logging Directories Create logging directories by running the following:

UNIX

/usr/openv/netbackup/logs/mklogdir

Windows

install_path\NetBackup\logs\mklogdir.bat

Hardware Configuration Verify the functionality of your network equipment and storage devices, including disk arrays, robots and tape drives, switches, hubs, host-bus adapters, routers and/or third-party copy devices.

◆ For NetBackup Media Server or Third-Party Copy offhost backup: to verify NetBackup access to your SAN devices, to configure HBA drivers, and to create NetBackup configuration files, refer to the SAN configuration chapter of the Advanced Client System Administrator’s Guide.

◆ For assistance with disk array configuration, refer to the “Array Related Snapshot Methods” section of the Snapshot Configuration Notes chapter of the Advanced Client System Administrator’s Guide.

◆ Install the proper versions of all required firmware and device drivers.

For a list of supported platforms, and for configuration help with particular devices, see “Advanced Client Assistance” on page v.


Configure a Backup
3 Select Advanced Client Options
Most Advanced Client options are selected from the policy Attributes tab:

Select policy type and other basic attributes

Select Advanced Client options

7

Select Advanced Client Options

Advanced Client Dialog Overview

Perform block level incremental backups

For backups of Oracle and DB2 database clients only. This option requires NetBackup database agent software.

Perform snapshot backups

The backup will be made from a snapshot image of the client data. This is required for most features of Advanced Client.

Note If Bare Metal Restore is installed, you must deselect Collect disaster recovery information for Bare Metal Restore in order to select Perform snapshot backups.

Retain snapshots for instant recovery

Enables instant recovery of this backup.

Perform offhost backup

Shifts the burden of backup processing to another host or device on the network.

Advanced Snapshot Options

For optional selection of the snapshot method. Can be set to auto, which means NetBackup chooses the method. The default for a new policy is auto.

Note For help with these options, see the following sections in this chapter. It is best to read “Basic Snapshot Backup” on page 9 before reading the other sections.



Basic Snapshot Backup This procedure highlights Advanced Client-related options. Other policy options must be configured just as for regular backups.

To create a policy for a snapshot backup:

1. Select the policy type.

MS-Windows-NT: for Windows 2000 or 2003 clients.

Standard: for UNIX clients (Solaris, HP-UX, AIX, Linux).

DB2: for DB2 clients (requires NetBackup DB2 database agent software).

MS-Exchange: for MS-Exchange clients (requires NetBackup MS-Exchange database agent software).

MS-SQL-Server: for MS-SQL-Server clients (requires NetBackup MS-SQL-Server database agent software).

Oracle: for Oracle clients (requires NetBackup Oracle database agent software).

FlashBackup: for UNIX clients (but not AIX or Linux). See “FlashBackup” on page 10.

FlashBackup-Windows: for Windows 2000 or 2003 clients. See “FlashBackup” on page 10.

2. Click Perform snapshot backups.

NetBackup selects an appropriate snapshot method when the backup starts.

To select the snapshot method yourself, use Advanced Snapshot Options. The snapshot method will be used for all clients in the policy. For example: if you select nbu_snap, all clients in the policy must be Solaris, because nbu_snap can make snapshots on Solaris clients only.

3. Configure the rest of the policy (other attributes, schedule, backup selections, clients).

Note The ALL_LOCAL_DRIVES entry is not supported in the Backup Selections list of any policy that uses Advanced Client features.

Chapter 3, Configure a Backup 9


FlashBackup To create a policy for FlashBackup:

1. Select FlashBackup as the policy type for UNIX clients (AIX and Linux are not supported), or FlashBackup-Windows for Windows clients. Perform snapshot backups must also be selected.

2. Use the Backup Selections tab to specify the drive letter or mounted volume (Windows) or the raw disk partition (UNIX) containing the files to back up.

Windows examples:

\\.\E:\\.\E:\mounted_volume

Note The drive must be designated exactly as shown above. Backing up the drive containing the Windows system files (usually the C drive) is not supported.

Solaris examples:

/dev/rdsk/c1t0d0s6/dev/vx/rdsk/volgrp1/vol1

HP-UX examples:

/dev/rdsk/c1t0d0/dev/vx/rdsk/volgrp1/vol1

Note:

◆ FlashBackup-Windows policies do not support the backup of Windows system-protected files (the System State, such as the Registry and Active Directory).

◆ If using the FlashBackup-Windows policy type and the VSP snapshot method, click Host Properties > Clients, select the client, then Actions > Properties, Windows Client > VSP to specify VSP settings for the client.

◆ UNIX clients only: some snapshot methods require extra disk space set aside as a cache. The cache must be a raw partition, designated in either of two ways:

◆ Click Host Properties > Clients, select the client, then Actions > Properties, UNIX Client > Client Settings. Specify the default cache for the client.

◆ Or, click Advanced Snapshot Options on the policy dialog, select nbu_snap (Solaris clients only) or VxFS_Snapshot as the method, and specify the cache device path.



NAS Snapshot

1. Select Standard as the policy type for UNIX clients (AIX and Linux are not supported), MS-Windows-NT for Windows clients, or Oracle for UNIX clients configured in an Oracle database.

2. Select Perform snapshot backups and Retain snapshots for instant recovery.

3. For Storage unit, select Any_available. For SnapVault, a special disk storage unit must be defined (see the NetBackup Advanced Client System Administrator’s Guide for SnapVault instructions).

4. Select Perform offhost backup and Use data mover. For Use data mover, pick Network Attached Storage.

5. On the Schedule Attributes tab, select Snapshots only.

6. On the Backup Selections tab, specify the mounted file system (UNIX) or share name (Windows), from the client perspective. For example:

◆ On UNIX, if the data resides in /vol/vol1 on the NDMP host, and is NFS mounted to /mnt2/home on the UNIX client, specify /mnt2/home.

◆ On Windows, if the data resides in /vol/vol1 on the NDMP host, and is CIFS mounted (mapped to) \\nas1\vol\vol1 on the Windows client, specify \\nas1\vol\vol1.

◆ For SnapVault: specify subvolumes (qtrees in Network Appliance Data ONTAP), not volumes.

Note:

◆ Both NetBackup for NDMP and Advanced Client software must be installed and licensed on the NetBackup server.

◆ The client data must reside on an NDMP host and be mounted on the client by means of NFS on UNIX or CIFS on Windows. The data must not be auto-mounted, but must be hard (or manually) mounted.

◆ For detailed configuration requirements, see the NAS chapter of the NetBackup Advanced Client System Administrator’s Guide.

◆ For a list of supported NAS vendors for NAS snapshots and SnapVault, refer to the NetBackup Advanced Client Configuration and Compatibility document (for access instructions, see “Advanced Client Assistance” on page v).



Instant Recovery To create a policy for a backup that enables Instant Recovery:

1. Select Perform snapshot backups and Retain snapshots for instant recovery on the policy Attributes tab.

A snapshot will be created and the data will be backed up to tape or other specified storage. For a restore, the data is retrieved from the snapshot.

2. To skip the backup to tape or other storage unit, select Snapshots only on the Schedule Attributes tab.

To make a snapshot of data on a NAS host, Snapshots only must be selected.

No backup to tape or other storage unit

Only a snapshot is created



Offhost Backup To shift backup processing to another host or device (reduce local network traffic):

1. Select Perform snapshot backups and Perform offhost backup on the policy Attributes dialog.

2. For a backup performed by an alternate client, click Use alternate client and enter the name of the alternate client. See the NetBackup Advanced Client System Administrator’s Guide for details.

3. To make the backup by means of a data mover, click Use data mover and choose one of the following:

NetBackup Media Server

Backup processing will be handled by a Solaris, HP, AIX, or Linux NetBackup media server (for Solaris, HP, AIX, and Linux clients only).


Backup processing will be handled by a third-party copy device (for Solaris, HP, AIX, and Linux clients only). This option may require additional configuration; see “Third-Party Copy Configuration Files” on page 22.

Network Attached Storage

The backup is performed by a NAS host (Network Attached Storage) using the NAS_Snapshot method. See “NAS Snapshot” on page 11 for policy configuration.

Note:

◆ For NetBackup Media Server and Third-Party Copy Device, the Any_available storage unit type is not supported. Specify a particular storage unit or group of storage units.

◆ For Third-Party Copy Device, disk storage units are not supported.

◆ For Third-Party Copy Device, you must create a mover.conf file as explained in the “Data Movers (UNIX Clients Only)” appendix.

◆ For Third-Party Copy Device: if VERITAS CommandCentral Storage (or SANPoint Control) does not support your environment, and one or more devices needed for the backup do not provide identification descriptors (SCSI E4 target descriptors), you may need to edit the 3pc.conf file as explained under “3pc.conf file” on page 23.


Test Advanced Client

Test Advanced Client

1. Make sure a standard backup works properly (policy configured without Advanced Client features).

2. Try a backup using the same policy but configured for snapshot backups (as described under “Basic Snapshot Backup” on page 9).

3. Try other Advanced Client features as required, running a backup after each has been added to the policy.

◆ For offhost backup, try the Use alternate client method first.

4. UNIX clients only: for offhost backup using a data mover, try the NetBackup Media Server method first.

Note The media server must be able to access the tape drive or other storage device. See “Offhost Backup” on page 13 and the “Data Movers (UNIX Clients Only)” appendix.

5. UNIX clients only: for a data mover backup using the Third-Party Copy Device method, make sure the third-party copy device and other SAN/Fibre Channel devices are configured correctly.

Note See the “Data Movers (UNIX Clients Only)” appendix for assistance.


Configuration Matrix for Backup Types

Configuration Matrix for Backup Types The following table shows the basic Advanced Client requirements for local snapshot backup, alternate client backup, and for data mover backup. Note that all Advanced Client backup methods require a snapshot.

Note For a table of Advanced Client features and supported client operating systems, refer to the NetBackup Advanced Client Configuration and Compatibility online pdf (see “Advanced Client Assistance” on page v for help accessing that document).

Local Snapshot

Alternate Client

DATA MOVER

NetBackup Media Server


Network Attached Storage

Software

◆ NetBackup 6.0 Enterprise

◆ Advanced Clienta

Hardware

No special requirements

Other

ALL_LOCAL_ DRIVES in

Backup Selections list not supported

Software



◆ OS/level on alternate client must be same as on primary client

Hardware

Client disk must be visible to alternate client

Other

Same as Local Snapshot, plus: ◆ Can use auto,

FlashSnap, VSS_Transportable, VVR, TimeFinder, ShadowImage, or BusinessCopy snapshot methods onlyb

Software



Hardware

◆ Client disk must be visible to client and media server

◆ Client disk must be SCSI or Fibre Channel device

◆ Client disk must support serialization or SCSI Inquiry Page Code 83c

Other

Same as Local Snapshot, plus:

◆ Any_available storage unit not supported

Software



◆ Vendor-supplied data mover license

Hardware

Same as Media Server method, plus:

◆ Need supported third-party copy data moverd

Other

Same as Media Server, plus: ◆ Must create mover.conf

file (use bpmoverinfo) ◆ May need to edit

3pc.conf filee

◆ Multiplexing not supported

Software



◆ NetBackup for NDMP

Hardware/Other

See the “NAS Snapshot

Configuration” chapter of the

NetBackup Advanced Client System

Administrator’s Guide for in-depth snapshot configuration details.

a. NetBackup database agent software required when backing up database clients.

b. See NetBackup Advanced Client System Administrator’s Guide for requirements.

c. See NetBackup Advanced Client System Administrator’s Guide for further restrictions.

d. Refer to NetBackup Advanced Client Configuration and Compatibility at www.support.veritas.com for a list of supported SAN devices (see “Advanced Client Assistance” on page v for instructions).

e. See “Third-Party Copy Configuration Files” on page 22 for requirements.


Configuration Matrix for Backup Types


Frequently Asked Questions
4 Q: Once I’ve installed Advanced Client on the master/media server, how do I install that software on the NetBackup clients?
A: For UNIX clients, use the update_clients command from the UNIX master server. The following command updates all configured UNIX clients with Advanced Client software once Advanced Client has been installed on the master server:

/usr/openv/netbackup/bin/update_clients -Install_ADC

For Windows PCs, Advanced Client software is automatically installed with the base NetBackup software, for server and clients.

Q: NetBackup already includes the VSP and VSS snapshot providers. Why do I need Advanced Client?

A: When used without Advanced Client, VSP and VSS do not guarantee that the backup is based on a snapshot. For snapshot-based backups, and for FlashBackup, Instant Recovery, and offhost backup over a SAN or by means of an alternate client, Advanced Client is required.

Q: What license do I need for making a snapshot, when an offhost backup is not required?

A: Advanced Client.

Q: What license do I need for making a snapshot of a database client?

A: Advanced Client plus the NetBackup database agent software for your database.

Q: What license do I need for making a snapshot of client data on an NDMP host (NAS filer)?

A: Both Advanced Client and NetBackup for NDMP.

17

Q: Does Advanced Client support backing up raw partitions/luns?

A: Yes.

Q: If my configuration utilizes a third-party copy data mover built into a Fibre Channel/SCSI router (bridge), do the tape drives or storage arrays need to be connected directly to this router?

A: No. The only restriction is that in a SAN environment the router needs to be visible to the NetBackup media server, to the storage device being backed up, and to the ultimate destination (such as the tape or disk drive).

Q: How can I configure offhost backup with FlashBackup?

A: Install Advanced Client, define the policy type as FlashBackup, and select the offhost method on the same policy Attributes tab.

Q: Should the mover.conf file be created in all offhost configurations?

A: No. The mover.conf file is only required for Third-Party Copy Device backups.

Q: When should the 3pc.conf file be created?

A: The 3pc.conf file is required for offhost backups using the NetBackup Media Server or Third-Party Copy Device method. NetBackup automatically creates this file. Under certain circumstances, you may have to edit the file when using the Third-Party Copy Device method, as explained under “Third-Party Copy Configuration Files” on page 22.

Q: Can I have a Solaris NetBackup master server and use an HP-UX, AIX, or Linux media server as a data mover?

A: Yes. And the converse is also supported.

Q: Do any of the snapshot methods support multiple data streams?

A: Yes. All snapshot methods support the creation of multiple data streams during backup. This is configured in the same way as for standard backups. Keep in mind that an XCOPY-based data mover (Third-Party Copy Device method) does not support multiplexing.

Q: Do any offhost data movement methods support multiplexing?

A: Yes. The alternate client and NetBackup Media Server methods support multiplexing. The Third-Party Copy Device method does not. This is not a NetBackup restriction but a limitation of the XCOPY protocol.


Q: What is device serialization and why do I need it?

A: Device serialization is the ability of a device (disk or tape drive) to return a serial number that uniquely identifies that device. NetBackup relies on device serialization when running the tape configuration wizard. Most disk drives also support serialization. Some disk arrays do not support it but do support identification descriptors.

Q: How does the SUN version of the Hitachi array differ from the Hitachi version?

A: From an operational standpoint the two arrays are exactly the same, including microcode.

Q: Do I need an Hitachi, HP, SUN, or EMC array to make offhost backups?

A: No. Most Advanced Client snapshot methods do not require these arrays. A simple storage array (JBOD) with no RAID controller can be used, such as when combined with VERITAS Volume Manager.

Q: Can the array-specific snapshot methods (EMC TimeFinder, Hitachi ShadowImage, HP BusinessCopy) be used either with or without offhost backup?

A: Yes. The array-specific snapshot methods are for making snapshots of EMC, Hitachi, or HP disk arrays. Offhost backup is for shifting data movement tasks away from the client to a separate entity such as a media server. The array snapshot methods can be used in conjunction with offhost backup, or without it.

Q: Are the array-specific snapshot methods (TimeFinder, ShadowImage, BusinessCopy) required for making offhost backups of supported disk arrays?

A: No. Depending on the file system and/or volume manager configuration of the client data, any Advanced Client snapshot method can be used for offhost backups of the arrays.

Q: Does Advanced Client support backup of Windows clients on disk arrays?

A: Yes. Advanced Client uses the Volume Shadow Copy Service of Windows 2003 for alternate client backups of Windows 2003 clients, where the client data is stored either on a supported disk array such as EMC or Hitachi or in a VERITAS Storage Foundation for Windows 4.1 or later volume. This feature also supports file system backup of a disk partition (such as E:\) and backup of Exchange databases.

Q: Where can I find more information related to OS and hardware support?

A: See “Advanced Client Assistance” on page v for instructions.

Chapter 4, Frequently Asked Questions 19


Data Movers (UNIX Clients Only)
A This appendix explains how to prepare for backups that use the NetBackup Media Server or Third-Party Copy Device method.
For assistance with the Network Attached Storage method, refer to the NetBackup Advanced Client System Administrator’s Guide.

Note The information in this appendix applies to backups of UNIX clients only.

Test the Network Do the following if you are using a data mover for offhost backup of UNIX clients.

Verify the hardware

Devices must be connected to and visible from the appropriate systems. The data mover must be able to access the tape drive or other storage device.

Configure the hardware

Make sure that NetBackup can see the hardware: use the sgscan command (Solaris), ioscan -nf (HP-UX), or lsdev -C (AIX). This is a critical step. For more detailed instructions, refer to the NetBackup Media Manager Device Configuration Guide.

Create configuration files (Third-Party Copy Device only)

◆ Create a /usr/openv/volmgr/database/mover.conf file on the media server by entering:

/usr/openv/netbackup/bin/admincmd/bpmoverinfo

See “Mover.conf file” on page 22 for more details on this command.

21

Third-Party Copy Configuration Files

◆ If a device needed for the backup does not provide an identification descriptor (E4 target), update the /usr/openv/volmgr/database/3pc.conf file with the world-wide port name for that device as explained under “3pc.conf file” on page 23. Identification descriptors are listed in the 3pc.conf file beginning with i= followed by a long number (see “Example 3pc.conf” on page 24).

Test the basic configuration

Test the hardware configuration to make sure NetBackup communicates with all devices properly. Use robtest to test the robotic library. Try a standard (non-Advanced Client) backup to test the tape libraries and communications with the client.

Configure and test Advanced Client

Once standard backups work properly, set up an Advanced Client policy and run an offhost backup using the NetBackup Media Server method. Then try the Third-Party Copy Device method, if applicable.

Third-Party Copy Configuration Files This section explains how to set up configuration files for third-party copy data mover backups.

Note If not using the Third-Party Copy Device offhost method, you can skip this section.

On the NetBackup media server:

◆ mover.conf identifies the third-party copy devices (data movers) that execute SCSI Extended Copy commands for the third-party copy backup. This file is easy to create, explained below.

◆ 3pc.conf contains a list of all disk and tape devices on the SAN that NetBackup can use for offhost backups. NetBackup automatically creates this file at the start of the backup. If some devices do not provide identification descriptors (see “Example 3pc.conf” on page 24 for examples) and CommandCentral Storage (or SANPoint Control) does not support your environment, editing the 3pc.conf file may be necessary (see “3pc.conf file” on page 23).

Mover.conf file To create the /usr/openv/volmgr/database/mover.conf file, enter the following on the media server:

/usr/openv/netbackup/bin/admincmd/bpmoverinfo



This command discovers third-party copy devices (data movers) on the SAN and creates a mover.conf file with appropriate entries for each device.

Example mover.conf file:

/dev/rmt/1cbn/dev/sg/c6t1l0/dev/sg/c6t1l1/dev/sg/c6t1l2/dev/sg/c6t4l0

Each of the above lines identifies a data mover.

Note:

◆ Before creating mover.conf, make sure all devices are visible. Some data movers can only be seen by running the following:

On Solaris

sgscan basic

On HP

ioscan -nf

On AIX

lsdev -C

◆ Some devices may be listed in mover.conf that are not actual data movers. NetBackup automatically scans each device in mover.conf until it encounters a device that is an actual data mover.

◆ Additional mover.conf configuration information can be found in the NetBackup Advanced Client System Administrator’s Guide.

3pc.conf file If some devices required for the backup do not provide identification descriptors (i=iddesc in the /usr/openv/volmgr/database/3pc.conf file), you may have to update the 3pc.conf file with world-wide port names for those devices, as follows.

1. Enter the following on the media server when no backups are in progress:

/usr/openv/netbackup/bin/bptpcinfo -a

This creates a /usr/openv/volmgr/database/3pc.conf file. This file identifies the client disks on the SAN that can be backed up and the robotic libraries/tape drives on which NetBackup can store the data.

Appendix A, Data Movers (UNIX Clients Only) 23


2. To add world-wide port numbers to the file, enter the following:

/usr/openv/netbackup/bin/admincmd/bpSALinfo -S SPC_server

The bpSALinfo command discovers world-wide port numbers for the devices and adds them to the 3pc.conf file. The bpSALinfo command requires VERITAS CommandCentral Storage (or SANPoint Control). SPC_server identifies the host where CommandCentral Storage/SANPoint Control is running.

Note If CommandCentral Storage/SANPoint Control does not support your environment, you must edit the 3pc.conf file manually as described in the SAN Configuration chapter of the NetBackup Advanced Client System Administrator’s Guide.

Below is an example /usr/openv/volmgr/database/3pc.conf file.

Example 3pc.conf

# devid [a=wwpn:lun] [c=client] [p=devpath] [P=clientpath] [s=sn] [l=lun] [w=wwpn] [W=wwpn] [i=iddesc]

0 p=/dev/rdsk/c0t0d0s2 s=FUJITSU:MAB3091SSUN9.0G:01K52665 l=0

1 p=/dev/rdsk/c0t10d0s2 s=FUJITSU:MAG3091LSUN9.0G:00446161 l=0

2 p=/dev/rdsk/c4t0d0s2 s=HP:OPEN-3:30436000000 l=0 a=500060E80276E401:0

3 p=/dev/rdsk/c4t3d1s2 s=HITACHI:OPEN-3-SUN:20461000300 l=1 i=10350060E800000000000004FED00000003 a=50060E80034FED00:1

4 p=/dev/rdsk/c4t1d0s2 s=HITACHI:OPEN-3-CM:20461000000 l=0 a=100000E00221C153:0

5 p=/dev/rdsk/c4t3d0s2 s=HITACHI:OPEN-9:60159003900 l=0 w=500060e802eaff12

world-wide port name identification descriptor

Please note:

◆ The identification descriptor (i=iddesc) is a means of designating a device on a SAN. The identification descriptor is not supported by all vendors. For this descriptor, the device must support a page code inquiry with a type 2 or 3 descriptor of less than 20 bytes. The NetBackup bptpcinfo command will detect the device’s identification descriptor and place it in the 3pc.conf file if the identification descriptor is available. Note: even when this descriptor is available, some third-party copy devices do not support its use.

◆ For a world wide name, use the world wide port name (WWPN), not the world wide node name (WWNN).

◆ To determine the WWPN of a device, look in the /var/adm/messages file on Solaris, or log into the appropriate host-bus adapter and/or Fibre Channel switch.


Diagram of Third-Party Copy Environment

◆ For configuration assistance, see the flowcharts in the SAN Configuration chapter of the NetBackup Advanced Client System Administrator’s Guide.

Diagram of Third-Party Copy Environment This diagram shows the Fibre Channel environment for Third-Party Copy Device backups using Advanced Client.

Advanced Client is installed on master server, media server, and clients

NetBackup master NetBackup media NetBackup server server client

FC switch

NetBackup creates 3pc.conf. 1

You create mover.conf2

Disk array and tape library must be visible on SAN to data mover and client.

LAN

Data mover with third-party copy engine

Hardware array:

May have an embedded data mover

Tape library: May have an embedded data mover

Fibre Channel SAN

1. See “Third-Party Copy Configuration Files” on page 22 for exceptions.

2. See “Mover.conf file” on page 22 (only needed for Third-Party Copy Device backups).

Appendix A, Data Movers (UNIX Clients Only) 25

Diagram of Third-Party Copy Environment


Index

Numerics 3pc configuration 213pc.conf file 22, 23

A Active Directory 10

and FlashBackup 10Advanced Client

access web info vconfigure policy 7feature overview 1

Advanced Snapshot Options dialog 1, 8, 9 ALL_LOCAL_DRIVES 9, 15 alternate client 13 Any_available storage unit 13

B Bare Metal Restore 8 block level incremental backup (BLIB) 1, 8 block-level restore 1 bpmoverinfo command 21, 22 bpSALinfo command 24 bptpcinfo command 23, 24

C cache for FlashBackup 10 CommandCentral Storage 13, 22, 24 configuration

requirements matrix 15snapshot wizard v, 1

copy-on-writedefined 2

D data mover 2, 21, 22

license 15 device file name for FlashBackup 10 directories for troubleshooting 6 drive letter for FlashBackup 10

E E4 target 22 Extended Copy command 3, 22

F FAQs 17 features, overview 1 Fibre Channel environment 25 file promotion 1 FlashBackup 1, 10

device file name 10 files to back up 10

frequently asked questions 17

H hardware requirements 15 hardware verification 21

I identification descriptor 13, 22, 23, 24 installation 5 instant recovery 1

backups to disk only 12 configuration 12 volume name restriction 6

ioscan -nf 23

L logging directories 6 lsdev -C 23

M mirror 2 mover.conf file 13, 21, 22

N NAS (Network Attached Storage) 13, 15, 17,

21 configure policy for 11 instant recovery option required 12 offhost backup type 13

27

nbu_snap snapshot method 10NDMP (see NAS)NetBackup Media Server method 2, 13Network Attached Storage (see NAS)network testing 21

O offhost backup 1, 2, 21

configuration 13NAS 13, 15, 21

P Perform block level incremental backups 8Perform offhost backup 8, 13Perform snapshot backups 8, 9peripherals (latest info on web) vpoint in time rollback 1policy

configuration 7types supported 9

promotion, file 1

R raw partition backup 10raw partition for FlashBackup cache 10Registry 10

and FlashBackup 10requirements 15restore

block-level 1file promotion 1rollback 1

Retain snapshots for instant recovery 8, 12rollback 1

S SANPoint Control 13, 22, 24Schedules tab (policy) 12SCSI Extended Copy command 22sgscan command 23

Shadow Copy Service (see VSS)Snapshot Configuration Wizard v, 1snapshots 1, 2

backup configuration 9mirror 2

SnapVault 11software requirements 15storage unit 21support web site (VERITAS) vsupported policy types 9System State 10

and FlashBackup 10system-protected files and FlashBackup 10

T terminology 2testing Advanced Client 14, 22third-party copy

device configuration 21third-party copy device 3, 13, 21, 22, 25troubleshooting

directories to create 6

U update_clients command 5Use alternate client 13Use alternate client feature 13

VVSS_Transportable methodVxFS_Snapshot method 10VxVM

volume name restriction 6

W web access to recent Advanced Client info vwizard for Advanced Client v, 1world wide name 24WWPN 24


Date post:	11-Mar-2018
Category:	Documents
Upload:	lyduong
View:	223 times
Download:	3 times

VERITAS NetBackup Advanced Client - Add …docshare01.docshare.tips/files/28416/284169655.pdf ·...

Documents