VERITAS NetBackup ServerFree Agent 4.
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.
Contents About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Related Manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Frozen Image Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Copy-on-Write Snapshot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Mirror . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Client Deinstall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Chapter 4. SAN Configuration for ServerFree Agent . . . . . . . . . . . . . . . . . . . . . . . . . 41 SAN Configuration Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Supported Peripherals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration at a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Configuring a Frozen Image Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Configuring a Backup Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Configuration Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Hitachi and HP Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Selecting a Mirror Disk for the Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Volume Manager Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Disk Label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Disk Types . . .
Standard Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 Chapter 10. Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Gathering Information and Checking Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 Contacting VERITAS Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 Important Notes . . . . . . . . . . . . . . .
About This Guide This guide explains how to install, configure, and use VERITAS NetBackup ServerFree Agent. Audience This guide is intended for the NetBackup system administrator and assumes a thorough working knowledge of both UNIX and NetBackup administration. Organization ◆ The “Introduction” is an overview of the product’s capabilities, with background information on frozen images and offhost backup. ◆ “Configuration Checklist” reviews the basic steps for configuring ServerFree Agent.
Related Manuals ◆ “ServerFree Agent Commands” provides information about several commands. Related Manuals ◆ NetBackup Release Notes for UNIX and Windows Describes supported platforms and provides operating notes not found in the manuals or in the online help. ◆ NetBackup DataCenter Installation Guide for UNIX Explains how to install NetBackup DataCenter for UNIX.
Accessibility Accessibility NetBackup contains features that make the user interface easier to use by people who are visually impaired and by people who have limited dexterity. Accessibility features include: ◆ Support for assistive technologies such as screen readers and voice input (Windows servers only) ◆ Support for keyboard (mouseless) navigation using accelerator keys and mnemonic keys For more information, see the NetBackup system administrator’s guide.
Conventions Notes and Cautions Note This is a Note. Notes are used to call attention to information that makes using the product easier or helps in avoiding problems. Caution This is a Caution. Cautions are used to warn about situations that could cause data loss. Key Combinations Some keyboard command sequences use two or more keys at the same time. For example, holding down the Ctrl key while pressing another key. Keyboard command sequences are indicated by connecting the keys with a plus sign.
Getting Help Terms The terms listed in the table below are used in the VERITAS NetBackup documentation to increase readability while maintaining technical accuracy. Term Definition Microsoft Windows, Windows Terms used as nouns to describe a line of operating systems developed by Microsoft, Inc. A term used as an adjective to describe a specific product or noun.
Getting Help 1. Open http://www.support.veritas.com/ in your web browser. 2. Click Contact Support. The Contacting Support Product List page appears. 3. Select a product line and then a product from the lists that appear. The page will refresh with a list of technical support phone numbers that are specific to the product you just selected. ServerFree Agent Information on the Web The VERITAS support web site includes a variety of articles and notes on ServerFree Agent.
1 Introduction This chapter describes NetBackup ServerFree Agent and contains the following topics.
Overview Overview NetBackup ServerFree Agent provides data protection services for frozen image data, and supports offhost backup over Fibre Channel networks (in addition to conventional backups to locally attached devices). Frozen Image Services A frozen image is a stable disk copy of the client’s data made prior to backup. Such a copy is important on active file systems and Oracle databases, where updates to files or tables can occur at any time.
Overview Backup Agent for Offhost Backup NetBackup master server LAN / WAN NetBackup client Backup agent Local disks of client data SCSI storage Fibre Channel/SAN Disks of client data on SAN Robot on SAN The backup agent can be either a NetBackup media server or a third-party copy device that implements the SCSI Extended Copy command. Note that many types of devices are designed to act as backup agents, such as routers, bridges, robotic libraries, and disk arrays.
Terminology Terminology This section introduces terms used with NetBackup 4.5 ServerFree Agent. Backup agent (see also Third-Party Copy Device) A general term for the host that manages the backup on behalf of the NetBackup client. In NetBackup 4.5, this is either the NetBackup media server or a third-party copy device. BCV The mirror disk in an EMC primary-mirror array configuration (see mirror). BCV stands for “Business Continuance Volume.
Terminology File list The list of files to be backed up for a NetBackup policy. For ServerFree Agent, the files in a file list must be part of a file system or raw device that was designated as a frozen image source. File system Has two different meanings. ◆ When referring to a product, such as the ufs (Sun Solaris) or VxFS (VERITAS) file system, it refers to the management and allocation schemes on which the entire file tree is structured.
Terminology ◆ A type of frozen image made on a mirror disk (see also snapshot). At an appropriate moment, all further writes to the primary disk are held back from the mirror, thus causing the mirror to be “split” from the primary. As a result of the split, the mirror becomes a “frozen” image of the primary. The frozen image can then be backed up.
Terminology Snapshot mirror An exact copy of a primary volume at a particular moment, reproduced on a physically separate device. Snapshot mirrors are created by the VERITAS Volume Manager (VxVM). Standard device Refers to the primary disk in an EMC primary-mirror disk array (see primary disk). Third-Party Copy Device This term has two meanings: ◆ A backup agent on the SAN that operates on behalf of backup applications.
Features Volume group A logical grouping of disks, created with the VERITAS Volume Manager, to allow more efficient use of disk space. VxFS This is the VERITAS extent-based File System (VxFS), designed for high performance and large volumes of data. VxVM This is the VERITAS Volume Manager (VxVM), which provides logical volume management that can be used in SAN environments. Features NetBackup 4.5 ServerFree Agent provides the following services and features.
Features ◆ vxvm (Solaris and HP-UX), for frozen images of client data configured over VERITAS Volume Manager volumes, using VERITAS Volume Manager 3.1 or later snapshot mirrors. Extended Frozen Image Services (Array Integration Option) ◆ TimeFinder (Solaris and HP-UX), for frozen images with EMC Symmetrix Disk Arrays (with TimeFinder SYMAPI). ◆ ShadowImage (Solaris and HP-UX), for frozen images with Hitachi Data Systems disk arrays with ShadowImage (HOMRCF).
Requirements Requirements NetBackup 4.5 ServerFree Agent requires the following components: ◆ A master server with NetBackup ServerFree Agent server software installed. ◆ Clients running either Solaris 2.6, 7, 8, or 9, or HP-UX 11.00 or 11i, with NetBackup ServerFree Agent client software installed. Note Certain operating system and device patches (such as for the host bus adapter) may be required for both servers and clients.
Restrictions - fsclone: media server requires access to the primary or active disk. - vxvm: access requirements depend on layout of the volume group. Media server must be able to access all disks that make up the snap mirror volume. ◆ If you are using the Extended Frozen Image Services (Array Integration) option, the NetBackup clients must be able to access the mirror (secondary) disk containing the frozen image of the client’s data. The NetBackup clients must also be able to access the primary disk.
Frozen Image Overview Frozen Image Overview Large active databases or file systems that must be available around-the-clock are difficult to back up without incurring a penalty. Often, the penalty takes one of two forms: ◆ The entire database is taken offline or the file system is unmounted, to allow time for the backup, resulting in suspension of service and inconvenience to users.
Frozen Image Overview Copy-on-Write Snapshot A copy-on-write snapshot is a detailed account of data as it existed at a certain moment. Unlike a mirror, explained in the next section, a copy-on-write snapshot is not really a copy of the data, but a particular “record” of it. The copy-on-write snapshot process works as follows: when a frozen image is required, any unfinished transactions or changes to the source data are allowed to complete, but new changes are temporarily stalled.
Frozen Image Overview Copy-on-write snapshot process Source data s0 s1 s2 s3 s4 s5 s6 s7 s8 s9 s10 Writes delayed s0 s1 s2 1 Image of source data is frozen; snapshot driver is activated 2 s3 s4 s5 s6 s7 s8 s9 s10 New write requests (represented by arrows) to s4, s7, s8 are held by snapshot driver Result of snapshot 3 Snapshot driver writes contents of blocks s4, s7, and s8 to cache (“copy on write”) Snapshot cache c0 c1 c2 c3 c4 4 Snapshot driver keeps a record of the writes
Frozen Image Overview Backing up a snapshot-type frozen image Source s0 s1 Source data, modified after snapshot s2 s3 s4 s5 s6 Backup of snapshot: s7 s8 s9 1 Backup reads source data from s0, s1, s2, s3 s10 Cache c0 s0 s1 s2 c1 s3 c2 s4 c3 s5 2 At s4, snapshot driver tells backup to read c0 instead of s4 c4 s6 s7 s8 s9 3 Next, the backup reads s5 and s6 from the source. s10 Cache c0 c1 c2 c3 4 At s7 and s8, snapshot driver tells backup to read c1, c2 instead of s7, s8.
Frozen Image Overview source data 3 until it comes to another changed block. Cache is read again 4 as the snapshot driver dictates. The backup, when finished, is an exact copy of the source as it existed the moment the snapshot driver was activated. In NetBackup ServerFree Agent, the nbu_snap and fsclone frozen image methods provide support for copy-on-write snapshot frozen images. These are included in the Core Frozen Image Services option.
Frozen Image Overview Since mirroring requires an exact, complete copy of the primary on a separate device (equal in size to the disk being mirrored), it consumes more disk space than a copy-on-write snapshot.
Processing Before and After the Frozen Image Note If additional disk drives are available and virtual volumes have already been configured with the VERITAS Volume Manager 3.1 or later, choose a mirror frozen image method. Processing Before and After the Frozen Image NetBackup performs several vital functions prior to creating a frozen image, as outlined below and in the following text.
Processing Before and After the Frozen Image Transactions affect all levels of the storage management stack (file system, volume manager, and so forth), generating further transactions as a request is handed off to the next level of the stack. From the viewpoint of the file system, for instance, an I/O request issued by a database application constitutes a transaction and may be split into many disk references, all of which must be complete for the original request to be fulfilled.
Processing Before and After the Frozen Image Dialog for Quiesce/Unquiesce Database Application 1 Quiesce. Frozen Image Consumer (NetBackup) 2 Finish transactions. 3 Quiesce acknowledge. 4 Quiesce stack, ... In quiesce mode .... 5 Unquiesce. trigger frozen image. 6 Out of quiesce mode. Continue processing. Quiescing the Stack The storage management stack is a layered arrangement of software elements.
Local Backup of Frozen Image (Local Host) Volume Manager As in a file system, the volume manager’s data caching may have to be flushed and disabled until the frozen image is created. As long as volume manager caching is enabled, data required for a consistent image may be lingering in volume manager cache rather than being available on disk when the frozen image is created.
Offhost Backup Overview Offhost Backup Overview The primary goal of NetBackup ServerFree Agent is to move I/O processing off the NetBackup client (application host) to either of the following: ◆ A backup agent executing on another server ◆ A fibre-channel attached third-party copy device Note that the disk(s) containing the client’s data must be “shared,” that is, visible to both the NetBackup client and the NetBackup media server. The disk(s) can be connected locally, or through a SAN.
Offhost Backup Overview Offhost Backup Methods NetBackup ServerFree Agent supports two offhost backup methods: NetBackup Media Server and Third-Party Copy Device. NetBackup Media Server In this offhost backup method, the NetBackup media server performs the data movement. The figure “NetBackup Media Server” shows the basic components used in the NetBackup Media Server method. A NetBackup media server handles the backup processing and sends the backup data over Fibre Channel to the storage device.
Offhost Backup Overview Third-Party Copy Device In this offhost backup method, a third-party copy device performs the I/O processing of the backup (data movement). Choose this option if processing time on the NetBackup client is critical and off-loading backup processing to a third-party copy device may save time. Figure “Third-Party Copy” shows the basic components used in the Third-Party Copy Device method. A third-party copy device (not a component of NetBackup) handles the backup data movement.
Offhost Backup Overview Offhost Backup Without a SAN Offhost backup does not require a fibre channel SAN. You can configure a multi-ported SCSI disk array on a LAN or WAN (as shown below) to support a NetBackup media server offhost backup. The NetBackup media server performs the data movement. NetBackup Media Server with Multi-Ported Disk Array (No SAN) NetBackup master server LAN / WAN 1 2 4 3 NetBackup client SCSI SCSI NetBackup media server Disk array Storage 1.
Offhost Backup Overview Offhost Backup: All the Options A multi-ported disk array can be combined with fibre channel to support either a NetBackup media server or third-party copy backup.
Tables of Features and Required Software Tables of Features and Required Software The following table shows the types of backup you can configure with ServerFree Agent, and the corresponding NetBackup features and requirements. The table on the following page shows the software and hardware requirements for each frozen image method.
Tables of Features and Required Software The following table describes each frozen image method and its requirements. Note Note that ServerFree Agent’s frozen image methods and offhost backup methods perform mapping of the underlying file system and volume structure being backed up. This mapping has been verified for the I/O system components listed in this table under “Data Type Supported.
Tables of Features and Required Software Frozen Image Methods and Requirements Frozen Image Method Type Mirror TimeFinder Data Type Supported (for file list and frozen image source entries) File systems: - (Solaris or HP) ufs (Solaris) VxFS Online JFS (HP only) Raw partitions: ShadowImage Mirror VxVM volumes BusinessCopy Mirror (Solaris or HP) VxFS Online JFS (HP only) VxVM volumes - Contact EMC for Symapi EMC TimeFinder Symapi - Extended Frozen Image Services (NetBackup add-on product)
Tables of Features and Required Software 30 NetBackup ServerFree Agent System Administrator’s Guide
2 Configuration Checklist This chapter reviews the basic steps for configuring ServerFree Agent. Each step includes a reference to other parts of this manual for detailed information. This checklist covers all phases of ServerFree Agent, from hardware setup to NetBackup policy and client configuration. Once these steps are complete, you should be ready to run a backup using frozen image and offhost backup methods.
Checklist Checklist ▼ For installation: 1. Install NetBackup DataCenter 4.5 server and client software. For detailed instructions, refer to the NetBackup DataCenter Installation Guide. 2. Install NetBackup ServerFree Agent software. Select the required options under the NetBackup Add-On Product Software menu, as follows. - Core Frozen Image Services. This is required for using the default frozen image capabilities of ServerFree Agent, and is also required for doing offhost backup.
Checklist For details on supported platforms and peripherals, see “ServerFree Agent Information on the Web” on page xiv. 6. Install and configure other software required by NetBackup. This may include VERITAS Volume Manager (VxVM) or VERITAS File System (VxFS), depending on the type of backup you want to perform. ▼ - For software requirements, refer to the “Tables of Features and Required Software” in the Introduction of this manual.
Checklist 13. Configure an offhost backup method, as follows. - Click Policies in the NetBackup Administration Console. Open the New (or Change) Policy dialog. Select NetBackup Media Server or Third-Party Copy Device for the offhost backup method. Then click Apply. Note For Policy storage unit, do NOT select Any_available. ▼ For troubleshooting help: For help with particular NetBackup status codes, refer to the NetBackup Troubleshooting Guide.
3 Installation This chapter explains how to install NetBackup ServerFree Agent software. Prerequisites ◆ NetBackup DataCenter 4.5 or later server software must be installed on the master/media servers. For performing local (not offhost) backups, the master/media server can be running any supported UNIX platform. For offhost backups, the NetBackup media server must be installed on Solaris 2.6, 7, 8, or 9, or HP-UX 11.00 or 11i.
Installing NetBackup ServerFree Agent cd /cd_rom_directory Where cd_rom_directory is the path to the directory where you can access the CD-ROM. It may be necessary to mount this directory. 5. To install NetBackup 4.5 software on the NetBackup master server and clients, execute the following: ./install The Installation Options menu appears. 6. Select NetBackup Add-On Product Software. A second menu appears. Select one or more of the following options: - Core Frozen Image Services.
Installing NetBackup ServerFree Agent Distributing ServerFree Agent Software to Clients Note If the master server is a Solaris or HP-UX system and the master server is also a client, you do not have to distribute ServerFree Agent software to the master. This distribution is done automatically when you load the software from the media (see previous step). However, you must distribute the software as explained below to all other clients that will be using ServerFree Agent.
When Upgrading from NetBackup 4.0V or Solaris Solaris8 othersparc or HP9000-800 HP-UX11.00 myhp - Execute the following command (all on one line): /usr/openv/netbackup/bin/update_clients -Install_VFMS -ClientList file Where file is the name of the file that you created in the previous step. Note ServerFree Agent software cannot be distributed to clients by means of the NetBackup Administration Console. 3.
De-installing NetBackup ServerFree Agent De-installing NetBackup ServerFree Agent Server Deinstall On the master server where you initially loaded the NetBackup ServerFree Agent software, do the following: 1. Check the Activity Monitor in the NetBackup Administration Console to make sure no NetBackup ServerFree Agent backups are active or running (the State field should read Done). 2.
De-installing NetBackup ServerFree Agent rm -f /usr/kernel/drv/snapctl rm -f /usr/kernel/drv/snapctl.
4 SAN Configuration for ServerFree Agent Due to the complex and rapidly changing nature of SAN configuration, this chapter describes SAN issues pertaining to NetBackup ServerFree Agent only. Please note the following assumptions: - You have considerable technical expertise in both SAN and NetBackup configuration. - Your hardware environment is already configured and functional, including switches, hubs, optional bridges or third-party copy devices, robots, tape drives, and disk arrays.
SAN Configuration Diagram SAN Configuration Diagram The following diagram shows the devices and configuration files described by the procedures in this chapter. This diagram shows devices configured behind a third-party copy device (bridge) as well as directly attached to the SAN (through the switch). Offhost backup configuration files on media server: 3pc.conf file: Contains tape and client disk info used by third-party copy device. NetBackup media server NetBackup client HBA HBA mover.
Offhost Configuration Requirements Supported Peripherals A complete list of ServerFree Agent supported peripherals can be found on the VERITAS support web site. For instructions, refer to “ServerFree Agent Information on the Web” on page xiv. Offhost Configuration Requirements NetBackup ServerFree Agent has two offhost backup methods: NetBackup Media Server and Third-Party Copy Device.
Offhost Configuration Requirements Diagram for NetBackup Media Server In this offhost backup method, the NetBackup media server handles the backup processing and sends the backup data over Fibre Channel to the storage device. Note If you have a multi-ported SCSI disk array, a fibre channel SAN is not required. See “Offhost Backup Without a SAN” on page 25. NetBackup Media Server NetBackup master server LAN / WAN 3pc.conf file on media server: Contains client disk information.
Offhost Configuration Requirements Diagram for Third-Party Copy Device In this offhost backup method, a third-party copy device performs the I/O processing of the backup (data movement).The 3pc.conf file describes the disks to be backed up and the tape devices for data storage. Be sure to use the flowcharts and accompanying instructions provided under “Offhost Configuration Flowcharts” on page 47. Third-Party Copy 3pc.conf file on media server: Contains tape and client disk information.
Offhost Configuration Requirements Diagram for Third-Party Copy Device - Remote In this configuration, the NetBackup media server and the disks containing the client data are on different fibre-channel networks (due to zoning or LUN-masking). The media server can communicate with the NetBackup client by means of the LAN, but does not have access to the client’s disks located on a different fibre channel network (or zone). In this case, the 3pc.
Offhost Configuration Flowcharts Offhost Configuration Flowcharts The following four charts show the process for setting up configuration files for offhost backup. The instructions for each chart are included later in this chapter. Chart I: Verify SAN Device Visibility For instructions, see “Verify NetBackup Access to SAN Devices” on page 51. Run bptpcinfo -a -o - N All OS device paths visible? Go to Chart II.
Offhost Configuration Flowcharts Chart II: Verify OS Device Paths Visibility For instructions, see “Making OS device paths visible” on page 51. N Tape devices visible? On Solaris: Correct the st.conf file Y Disks visible? N On Solaris: Correct the sd.conf file Y Third-party copy device visible? N Go to www.support.veritas.com for help enabling the third-party copy device. N Go to www.support.veritas.com for help discovering LUNs and world-wide names.
Offhost Configuration Flowcharts Chart III: Solaris only: Configure HBA Drivers For instructions, see “Solaris only: Configure HBA Drivers for Offhost Backup” on page 57. Storage target IDs bound to worldwide name? Y Done. Go to Chart IV. N Refer to “Device Checklist” on page 56 for SCSI target IDs (in device pathname) and world-wide names. Update HBA configuration file with target world-wide port name bindings. (Go to www.support.veritas.com for help.) Reboot. Go to Chart I.
Offhost Configuration Flowcharts Chart IV: Create the Offhost Backup Configuration Files For instructions, see “Create Offhost Backup Configuration Files” on page 58. Run bptpcinfo to create the 3pc.conf file NetBackup Media Server method? Y Done. No further 3pc.conf configuration needed. N Edit following in 3pc.conf file: Identification descriptors (i=)? Y Does mover support i=? Y Done. No further 3pc.conf configuration needed. N Enter (w=) in 3pc.conf file with value in “Device Checklist.
Verify NetBackup Access to SAN Devices Verify NetBackup Access to SAN Devices Note It is assumed that NetBackup and all device drivers are installed, and that devices are properly connected and powered up. ▼ Verify OS device path visibility 1. On the media server, run the bptpcinfo command. The following sends the output to the screen, using -o - (note the space before the final hyphen).
Verify NetBackup Access to SAN Devices ▼ Verify passthru device path visibility 8. For HP-UX: Enter the following to list all passthru devices: ioscan -nf a. If all devices now appear, enter the following to regenerate HP-UX special files: insf -e Then go to step 10 on page 53. b. If some devices do not appear in the ioscan output, check hardware connections to the devices that are not appearing. Then repeat step 8. Note On HP-UX, there is a limit of eight devices per target.
Verify NetBackup Access to SAN Devices If you are unsure how to acquire the SCSI target and LUN values for your configuration, see “ServerFree Agent Information on the Web” on page xiv for help with particular devices. For instance, if your tape drives are configured behind a bridge, router or other fibre-channel device, you may need to telnet into the device to determine the target ID and LUN for each tape drive. c. When finished updating the sg.links, sg.conf, and st.
Verify NetBackup Access to SAN Devices c. Click the Connectivity tab to find the world-wide port name of the device (Port WWN). Repeat these steps for each device. 13. Update the “Device Checklist” on page 56 with the world-wide port names of your devices. Note It is important to record this information! It will be needed again, to complete the configuration. 14. For Solaris: continue with “Solaris only: Configure HBA Drivers for Offhost Backup” on page 57.
Verify NetBackup Access to SAN Devices ◆ Add entries in the /usr/openv/volmgr/bin/driver/sg.links file so that the necessary /dev/sg/* nodes are created. Note that the target and LUNs in the address part of the sg.links entries are hexadecimal, but are decimal in the sg/c\N0tmln part of the entries. Also, make sure there are tabs between the columns, not spaces.
Verify NetBackup Access to SAN Devices Device Checklist Use this checklist or one like it to record information about each of your SAN devices. Some of this information is provided by the bptpcinfo command (such as device pathname and serial number), and some has to be obtained by other means as explained in these procedures. It is vital that the information be recorded accurately.
Solaris only: Configure HBA Drivers for Offhost Backup Solaris only: Configure HBA Drivers for Offhost Backup Fibre channel devices should be bound to specific SCSI target IDs by modifying the driver configuration files for your host bus adapter (HBA). This binding ensures that the host HBA and the third-party copy device are in agreement as to the target and LUN values for each device.
Create Offhost Backup Configuration Files Create Offhost Backup Configuration Files To set up offhost backup, you must create these configuration files on the media server (described in the following sections): ◆ /usr/openv/volmgr/database/3pc.conf ◆ /usr/openv/volmgr/database/mover.conf Note These files are needed only for the Third-Party Copy Device or NetBackup Media Server backup methods. If not using either of these backup methods, you do not need to create these files. The 3pc.conf and mover.
Create Offhost Backup Configuration Files Example 3pc.conf file Below is an example 3pc.conf file, followed by descriptions of each field. Example 3pc.
Create Offhost Backup Configuration Files nport ID (n=npid) The fibre channel n-port ID, which identifies the device on the SAN. This value is usually not required. If you cannot use i=, or w= and l=, refer to “ServerFree Agent Information on the Web” on page xiv to obtain configuration notes including information on the nport ID. lun (l=lun) The device’s logical unit number.
Create Offhost Backup Configuration Files Determining Requirements The following determines which values are required in the 3pc.conf file. identification descriptor The identification descriptor is optional, and is not supported by all vendors. (To produce 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 (explained below) will detect the device’s identification descriptor and place it in the 3pc.
Create Offhost Backup Configuration Files mover.conf Description The /usr/openv/volmgr/database/mover.conf file identifies the third-party copy devices that NetBackup can use for the Third-Party Copy Device backup method. This file is not needed for the NetBackup Media Server method. If your site has only one third-party copy device, use the bpmoverinfo command (see “Create the mover.conf File” on page 67) to create the mover.conf file. The bpmoverinfo command makes the appropriate entry in the mover.
Create Offhost Backup Configuration Files - “dev type 3h CNSi” indicates a Chaparral device. Its device path in this example is /dev/sg/c6t4l0. ◆ An alternative: the mover.conf file can consist of one line specifying the device by means of the /dev/rmt/device_file_name, where device_file_name specifies the actual file name of the device. Note that the tape device you specify must be the same as the device that NetBackup selects for the backup.
Create Offhost Backup Configuration Files END END tells NetBackup to stop searching the mover.conf file for third-party copy devices for the current third-party copy backup. If there are two or more third-party copy devices in the mover.conf file, NetBackup tries them sequentially, starting with the first one listed in the file, until one is found that can successfully move the data.
Create Offhost Backup Configuration Files Note The storage_unit_name in this file name must exactly match the name of the storage unit as it appears in the “Policy storage unit” field of the Change Policy dialog. Mover File: Order of Searching NetBackup looks for an appropriate mover.conf file in the following order: 1. mover.conf.policy_name 2. mover.conf.storage_unit_name 3. mover.conf Create the 3pc.conf File The /usr/openv/volmgr/database/3pc.
Create Offhost Backup Configuration Files Note For the NetBackup Media Server offhost backup method, no more configuration is needed. The 3pc.conf file only needs the device ID, device path (p=), and serial number (s=) of each device. You can skip the rest of this chapter. 2.
Create Offhost Backup Configuration Files If the 3pc.conf file does not have an identification descriptor for each device (or the descriptor is not supported by the third-party copy device), enter the world-wide port name (w=) for each device. (Obtain the world-wide port name from your “Device Checklist” on page 56.) - Create the mover.conf File This section describes how to create a list of the available third-party copy devices in a mover.
Create Offhost Backup Configuration Files Example mover.conf file for a site with one third-party copy device LAN / WAN NetBackup client mover.conf file contains this third-party copy device: NetBackup media server /dev/sg/c6t1l0 Fibre Channel/SAN Third-party copy device /dev/sg/c6t1l0 Client disks on SAN robot0 robot1 storage unit name: storage unit name: TLD_robot0 TLD_robot1 In the above example, all offhost backups will use third-party copy device /dev/sg/c6t1l0 specified in the mover.
Create Offhost Backup Configuration Files Example mover.conf.policy_name file for site with third-party copy capability in disk array LAN / WAN NetBackup client NetBackup media server mover.conf.array_1 file contains this third-party copy device: /dev/sg/c6t1l0 Fibre Channel/SAN robot0 Disk array with third-party copy. Array contains the client data to back up.
Create Offhost Backup Configuration Files Example mover.conf.storage_unit_name files for two third-party copy devices file name: mover.conf.TLD_robot0 contains: /dev/sg/c6t1l0 LAN / WAN NetBackup client NetBackup media server file name: mover.conf.TLD_robot00 contains: /dev/sg/c6t4l0 file name: mover.conf.
Create Offhost Backup Configuration Files Note The storage_unit_name portion of the mover.conf.storage_unit_name file name must exactly match the actual name of the storage unit. See under “Configuring a Backup Method” on page 79 for an example Change Policy dialog showing a storage unit name in the Policy storage unit field.
Create Offhost Backup Configuration Files 72 NetBackup ServerFree Agent System Administrator’s Guide
5 NetBackup Configuration This chapter explains how to configure NetBackup ServerFree Agent for making frozen image and offhost backups. For a detailed discussion of NetBackup configuration (apart from ServerFree Agent issues), see the NetBackup DataCenter System Administrator’s Guide for UNIX.
Prerequisites Prerequisites Before proceeding with this chapter, make sure the following steps have been completed. ◆ The following must be installed on the NetBackup master server and clients (refer to the “Installation” chapter): - NetBackup 4.5. - The “Core Frozen Image Services” product, for using frozen images and offhost backup. - The “Offhost and SAN Data Movement Services” product, for offhost backup.
Configuration at a Glance Configuration at a Glance The configuration sections in this chapter do the following: 1. Help you choose a frozen image method. The frozen image method is configured for a particular client, not for a policy. Note Use of a frozen image method does not require offhost backup. You can use a frozen image method to capture a frozen image of locally available data (file systems, raw devices, volumes, and databases). 2.
Configuring a Frozen Image Method Configuring a Frozen Image Method This procedure explains how to configure a frozen image method. You must do this if either of the following apply: ◆ You are configuring an offhost backup. ◆ You want to capture a frozen image of locally available data (not offhost). This procedure involves designating a frozen image source.
Configuring a Frozen Image Method The Frozen Image Client Configuration dialog appears.† Click New. Select frozen image source type. Select (or enter) the file system, raw partition, or volume containing the data you want to back up. Select a frozen image method. Enter parameter values required by the frozen image method (if any). 6. Click New. A blank entry appears at the bottom of the Frozen Image Source list. 7. Select the Frozen image source type (file system, or raw partition or logical volume). 8.
Configuring a Frozen Image Method 9. Select a frozen image method from the picklist. Note You cannot apply more than one method to the same frozen image source. For guidance on nbu_snap, fsclone, and vxvm, refer to the “Core Frozen Image Services”chapter. For TimeFinder, ShadowImage, and BusinessCopy, refer to the “Extended Frozen Image Services (Array Integration Option)” chapter. 10.
Configuring a Backup Method Configuring a Backup Method This procedure explains how to select a backup method for an existing NetBackup policy. 1. Start the NetBackup Administration Console by entering the following: /usr/openv/netbackup/bin/jnbSA & 2. Expand Policies in the left pane. 3. Double click on the name of the policy. The Change Policy dialog appears, showing the Attributes tab. Select the offhost backup method. Select appropriate storage unit or storage unit group.
Configuring a Backup Method NetBackup Media Server Backup processing will be handled offhost, by a NetBackup media server. Third-Party Copy Device Backup processing will be handled offhost, by a third-party copy device. 5. If you selected Third-Party Copy Device or NetBackup Media Server as the backup method, specify a particular policy storage unit or group of storage units in the Policy storage unit pull-down menu. Note Do not select Any_available.
Configuration Tips Configuration Tips Maximum Pathname Length For frozen image backups, the maximum pathname length is 1000 characters (as opposed to 1023 characters for backups that do not use a frozen image method). This is because the frozen image is created on a new mount point which is added to the beginning of the file path. If this new mount point plus the original file path exceeds 1023 characters, the backup fails with a status code 1, “the requested operation was partially successful.
Configuration Tips For more information on Cross mount points, refer to the NetBackup DataCenter System Administrator’s Guide for UNIX. Example 1: Basic File List Entries Refer to the following diagram. If the policy file list contains /usr/file1 and /usr/file2, specify the mounted file system /usr as the frozen image source. If the file list also contains /var/config, you must create another frozen image source that designates the mounted file system /var.
Configuration Tips Example 2: Symbolic Links As in standard NetBackup, if an entry in the file list is a symbolic (soft) link to another file, ServerFree Agent backs up the link, not the file to which the link points. To back up the file’s data, the file list must also include the file path to the actual data. Likewise, to make a frozen image of the data, the frozen image source should be the mounted file system that contains the actual data. Refer to the following diagram.
Configuration Tips Example 3: Multiple Clients in Policy Policy: Jungle Clients in this policy: File list for policy Jungle* /dir1 /dir2/file7 /dev/rdsk/c0t0d0s1 /lily1/file1 /dev/vx/rdsk/volgrp1/vol1 Tiger and Lily Tiger contains these mounted file systems and raw partition: /dir1 /dir2 /dev/rdsk/c0t0d0s1 Lily contains this mounted file system and Volume Manager volume: /lily1 /dev/vx/rdsk/volgrp1/vol1 Define these frozen image sources for Tiger: /dir1 /dir2 /dev/rdsk/c0t0d0s1 Define these frozen imag
Configuration Tips FlashBackup Policies When applying a frozen image method to a client in a FlashBackup policy, note the following: ◆ The nbu_snap and vxvm frozen image methods are valid for clients in a FlashBackup policy. The fsclone frozen image method, however, is not valid for clients in a FlashBackup policy. Although the Frozen Image Client Configuration dialog allows you to select fsclone for such clients, the backup will fail.
Configuration Tips 86 NetBackup ServerFree Agent System Administrator’s Guide
6 Core Frozen Image Services This chapter provides additional information about the nbu_snap, fsclone, and vxvm frozen image methods (the Core Frozen Image Services option).
Core Frozen Image Services: Overview Core Frozen Image Services: Overview The following three frozen image methods require installation of the “Core Frozen Image Services” product. These methods are hardware independent: the client data may be on any disk supported by NetBackup. ◆ nbu_snap (Solaris only) The nbu_snap frozen image method is for making copy-on-write snapshot frozen images (for ufs or VERITAS VxFS file systems).
Creating a Snapshot Mirror of the vxvm Frozen Image Source Creating a Snapshot Mirror of the vxvm Frozen Image Source To use the vxvm frozen image method, you must create a snapshot mirror of the frozen image source before making a backup.
Cache for nbu_snap (Parameter Value field) Cache for nbu_snap (Parameter Value field) Note the following regarding the cache for nbu_snap, specified in the Parameter Value field of the Frozen Image Client Configuration display: ◆ The cache specifies a raw disk partition: either a logical volume or physical disk. This is used for storing the portions of the frozen image source that are changed by incoming write requests while the snapshot is in progress.
Extended Frozen Image Services (Array Integration Option) 7 This chapter provides in-depth configuration instructions for the “Extended Frozen Image Services” option (also known as the Array Integration option). These instructions are for setting up the disk arrays and configuring Volume Manager. For help configuring a frozen image method, refer to “Configuring a Frozen Image Method” on page 76.
Configuration Checklist Configuration Checklist This checklist includes major caveats and important information. READ THIS TABLE before setting up your disk arrays for Extended Frozen Image Services. The right column refers to sources for more information. CHECK THE FOLLOWING ! Refer to these topics for help If you want your client data configured over Volume Manager volumes, make sure your arrays and operating system are supported by Volume Manager (VxVM).
Overview Overview This section describes the frozen image methods provided in the Extended Frozen Image Services option, explains the need for data mirroring, and introduces terms used in this chapter. The Frozen Image Methods The “Extended Frozen Image Services” option allows you to configure mirror-type frozen image backups. The client data to back up must reside on one of the following types of disk arrays: EMC Symmetrix, Hitachi Data Systems, or Hewlett Packard XP.
Overview As shown in the following table, each of these methods must be used for its own array-type. Match Frozen Image Method to Type of Array To Use Extended Frozen Image Use this frozen image method: Services to back up the following: EMC Symmetrix disk arrays TimeFinder Hitachi disk arrays ShadowImage HP XP disk arrays BusinessCopy ◆ These frozen image methods cannot be switched: for example, selecting TimeFinder to back up an Hitachi array will cause the backup to fail.
Overview Client Data Must Be Mirrored When NetBackup makes a mirror-type frozen image, the client data on the primary disk must be mirrored on a secondary disk prior to the backup.
Disk Configuration Requirements ◆ Hitachi and HP: Primary and secondary are called primary volume and secondary volume. Disk Configuration Requirements Contact the array’s support technicians for help in configuring arrays to your specifications. Access to Disk Arrays ◆ NetBackup clients must have access to both primary and secondary disks (via SCSI or fibre channel, or both). If the clients do not have access to both primary and secondary disks, the backup will fail.
Disk Configuration Requirements Configuration 2: Array on Fibre Channel LAN NetBackup client NetBackup media server Fibre Channel Fibre Channel Switch Fibre Channel Arrays mirror disk primary disk Configuration 3: Array Behind Bridge; Bridge on Fibre Channel LAN NetBackup client Fibre Channel NetBackup media server Switch Fibre Channel Fibre Channel Bridge SCSI Arrays primary disk mirror disk Chapter 7, Extended Frozen Image Services (Array Integration Option) 97
Configuring Primary and Secondary Disks Multiple Connectivity to EMC Array: Common Serial Number mode EMC Symmetrix disk arrays with multiple connections from NetBackup clients and media servers (multiple SCSI or both fibre channel and SCSI) must be configured in Common Serial Number Mode.
Configuring Primary and Secondary Disks EMC Symmetrix For an EMC Symmetrix disk array on the NetBackup client, you need to create device groups, add primary and mirror (secondary) devices to the groups, and associate or pair the primaries with the secondaries. Once associated, the secondary disks must be synchronized with the primary disks. During synchronization, the primary disks are copied to the secondaries. Use the following commands.
Configuring Primary and Secondary Disks Pairs, or associates, the primary with the mirror, and synchronizes the mirror with the primary. If there are multiple primaries and mirrors, they are paired according to the order in which they were added to the group. 5. Show the output. symmir -g nbfim_test query When the above commands are successfully entered, NetBackup can execute frozen image requests involving primary device 02A and its associated mirror 08C.
Configuring Primary and Secondary Disks Following are two example files. Note that entries must be separated by spaces. Except for comment lines (#), the file must contain the HORCM_MON, HORCM_CMD, HORCM_DEV, and HORCM_INST parameters, followed by appropriate entries (explained below). Entries must be space delimited Example 1: configuration file /etc/horcm0.conf for three primary disks Host where the configuration file resides. Port name for this instance.
Configuring Primary and Secondary Disks HORCM_CMD Enter values for the following: ◆ cmd_dev_file: the command device file(s) for the array. For example, /dev/rdsk/c2t8d14s2. You can use the NetBackup bptpcinfo command to determine the command device file, as follows: bptpcinfo -d /dev/rdsk -o- | grep CM Below is sample output showing a command device file for an Hitachi device and for an HP device.
Configuring Primary and Secondary Disks ◆ Target ID: the SCSI or fibre channel target ID number of the disk, configured by means of the array’s dedicated console (not from a NetBackup host). ◆ LUN: the SCSI or fibre channel logical unit number of the disk, configured by means of the array’s dedicated console (not from a NetBackup host). ◆ MU: a numeric mirror descriptor for cascading disks (default 0). If you are not using cascading disks, this value may be left blank.
Configuring Primary and Secondary Disks Example 2: configuration file /etc/horcm1.conf, for three secondary disks Contains same parameters (HORCM_MON, etc.) as in config file for primary disks. Disk-related entries refer to the secondary disks.
Configuring Primary and Secondary Disks where x is the instance number of each configuration file. For the above example files, the command would be: /bin/horcmstart.sh 0 1 The daemons must be running in order to configure your primary and secondary disks.
Configuring Primary and Secondary Disks Resulting output: Group wiltest wiltest wiltest wiltest wiltest wiltest PairVol dev1 dev1 dev2 dev2 dev3 dev3 L/R L R L R L R Port# CL1-A CL2-A CL1-A CL2-A CL1-A CL2-A TID 8 16 8 16 8 16 LU-M 0 0 32 0 1 0 33 0 2 0 34 0 Seq# 60159 60159 60159 60159 60159 60159 LDEV# 0 43 1 44 2 45 P/S P-VOL S-VOL P-VOL S-VOL SMPL SMPL Status PAIR PAIR PSUS SSUS - % 100 100 99 99 - P-LDEV# 43 0 44 1 - M W - 2.
Configuring Primary and Secondary Disks LU-M LU indicates the SCSI or fibre channel logical unit number of the disk, configured by means of the array’s dedicated console (not from a NetBackup host). M is the numeric mirror descriptor for cascading disks. A cascading disk has more than one mirror (secondary) associated with a given primary. Seq# This is the unit serial number of the array. LDEV# Logical device number of the disk.
Configuring Primary and Secondary Disks ▼ Configure the arrays, depending on your requirements The next steps depend on the results of the pairdisplay listings and the requirements of your site. ◆ If all required disks are correctly paired (status of PAIR), the primary-secondary configuration is finished. ◆ If required disks are paired but currently split (PSUS, SSUS), or if they are not paired at all (SMPL), you must resynchronize or configure them, respectively.
Configuring Primary and Secondary Disks paircreate -g wiltest -d dev3 -vl 2. Enter the following to view the result: pairdisplay -g wiltest -d dev3 -CLI -fc When the synchronization starts, the Status column reads COPY. When it is nearly completed, the Status column reads PAIR (see the % column for percentage completion). If disks are paired but need to be split or reconfigured: 1.
Configuring Primary and Secondary Disks Note When making a frozen image on a mirror disk, NetBackup first splits the mirror disk from the primary. If your disk configuration demands that, of the three mirror disks, one or two particular disks must remain synchronized with the primary, do not select either of those disks for the frozen image backup.
Volume Manager Configuration Volume Manager Configuration Disk Label On Solaris only: If client data is configured in Volume Manager volumes, be sure to label all secondary devices using the format command (label option). Labeling the secondary disks prevents Volume Manager from marking the disks as disabled (if they are split from their primary disks) during a system reboot. While a secondary disk is synchronized with its primary, the secondary is invisible to Volume Manager.
Volume Manager Configuration Example VxVM Disk Groups: the Good and the Bad Disk arrays on SAN Fibre Channel EMC Symmetrix Hitachi HP P1 M1 P3 M3 P5 M5 P2 M2 P4 M4 P6 M6 P = primary disk in array M = mirror (secondary) disk in array Consider the following VxVM disk groups: Disk group: P1, P2 Good: group contains only primary devices, of same vendor. Disk group: P3, M3 Bad: group contains a secondary (mirror) disk. Disk group: P1, P3, P5 Bad: group contains disks of different vendors.
Volume Manager Configuration When Using Volume Manager and Extended Frozen Image Services For each of these Volume Manager volumes: /dev/vx/rdsk/dg/emc-vol /dev/vx/rdsk/dg/hds-vol /dev/vx/rdsk/dg/hp-vol Hitachi array EMC array HP array select this frozen image method: TimeFinder ShadowImage BusinessCopy Disk Group Clones When using Extended Frozen Image Services with client data configured over a Volume Manager volume, NetBackup creates a temporary disk group (clone) of the disks containing the m
Volume Manager Configuration Disk Group Cloning Example: Client data is in: - file system /fs_1 - configured over VxVM volume /dev/vx/rdsk/dg_1/vol01 vol01 on vol01 on primary_disk1 mirror_disk1 VxVM disk group dg_1 on primary_disk1. NetBackup creates a temporary VxVM disk group (clone) clone_dg_1_clone on mirror_disk1. In the above example, NetBackup removes the VxVM disk group clone_dg_1_clone after the backup has completed.
Best Practices Best Practices The recommendations in this section apply primarily to the use of the Extended Frozen Image Services and Volume Manager, except where noted. NetBackup Access to Arrays In connection with the information listed under “Access to Disk Arrays” on page 96, note the following recommendation: ◆ The NetBackup media server only needs read access to the secondary disks in the array; it does not need access to the primary disks.
Best Practices When the frozen image process is started, NetBackup reserves or “locks” the secondary (mirror) disk for that backup job, denying any other backup jobs access to that disk. If a second backup job requests a frozen image involving data on the same disk before the first job is complete, access is denied and the second job fails.
Best Practices Backup Policies in Conflict: Two Backups Accessing Same Volume secondary disk (mirror) Backup policy A Backup policy B File list: File list: /dev/vx/rdsk/dg/vol_1 /dev/rdsk/cxtxdxs2 /dev/vx/rdsk/dg/vol_1 Backup policy A starts job to back up /vol_1; mirror is locked to make frozen image. Backup policy B attempts to back up /vol_1 and requests frozen image: mirror is already locked—access denied. The above diagram shows /dev/vx/rdsk/dg/vol_1 on a single disk.
Best Practices Backup Policies in Conflict: Two Backups Accessing Volume s Distributed on Same Disks secondary disks (mirrors) A Backup policy A /dev/rdsk/cxt0dxs2 File list: /dev/vx/rdsk/dg/vol_1 B /dev/rdsk/cxt1dxs2 Backup policy B File list: /dev/vx/rdsk/dg/vol_2 Backup policy A starts to back up /vol_1; both disks A and B are locked to make a frozen image of /vol_1. Backup policy B attempts to back up /vol_2 and requests frozen image: disks A and B are already locked—access denied.
Migrating from NetBackup for EMC Migrating from NetBackup for EMC When upgrading from NetBackup 3.4 for EMC to Extended Frozen Image Services in NetBackup 4.5, note the following: ◆ Your NetBackup client must be reconfigured by an EMC support technician to have access to both the primary (standard) disks AND to the secondary disks (BCVs). NetBackup media server needs access to only the secondary (BCV) disks.
Migrating from NetBackup for EMC In the following diagram, note that the machine running as the backup host is eliminated, replaced by the media server. Extended Frozen Image Services: Clients Must Access Primary (Standard) and BCVs NetBackup master server LAN / WAN EMC Symmetrix NetBackup SCSI client SCSI standard disk BCV disk NetBackup media server Fibre Channel For TimeFinder in NetBackup 4.
8 Notes on Offhost Backup This chapter provides notes and restrictions regarding offhost (server-free) backup. For an introduction to offhost backup, refer to Chapter 1, “Introduction.
Disk Requirements for Offhost Backup Disk Requirements for Offhost Backup For offhost backups (NetBackup Media Server or Third-Party Copy Device offhost backup method), the client’s data must be on one or more disks that meet the following criteria: ◆ The disk must be either a SCSI or Fibre Channel device. ◆ The disk must be visible to both the NetBackup client and to the NetBackup media server.
9 Using NetBackup The following topics are covered in this chapter: ◆ Performing a Backup ◆ Performing a Restore 123
Performing a Backup Performing a Backup Note For the EMC TimeFinder, Hitachi ShadowImage, or HP BusinessCopy frozen image method, the client data to be backed up must reside on a mirror disk made by the corresponding vendor (EMC, Hitachi, or HP). Assistance from the disk array vendor’s technical support may also be required. Refer to the chapter titled “Extended Frozen Image Services (Array Integration Option).
Performing a Restore Performing a Restore FlashBackup Policy You can use the NetBackup Administration Console on the client to restore individual files or directories (or a raw partition) in a FlashBackup policy. See the NetBackup FlashBackup System Administrator’s Guide for instructions. Standard Policy You can use the NetBackup Administration Console on the client to restore a file system, raw partition, or volume in a Standard policy. See the NetBackup User’s Guide for instructions.
Performing a Restore 126 NetBackup ServerFree Agent System Administrator’s Guide
10 Troubleshooting This chapter covers the following topics. ◆ Gathering Information and Checking Logs ◆ Important Notes ◆ Installation Problem ◆ Removing a Frozen Image ◆ Removing a VxVM Volume Clone ◆ VfMS Error Conditions ◆ Process Diagrams for Offhost Backup Note For detailed information on the correct use of frozen images and offhost backup, refer to “Configuration Tips” in the “NetBackup Configuration” chapter.
Gathering Information and Checking Logs Gathering Information and Checking Logs You can resolve many problems on your own by setting up the appropriate logs, reproducing the problem, and then checking the logs. For an in-depth description of NetBackup logs, refer to Chapter 3 of the NetBackup Troubleshooting Guide - UNIX. ◆ To create detailed log information, put VERBOSE in the bp.conf file on the NetBackup master and client.
Important Notes Contacting VERITAS Customer Support Before calling customer support, please gather as much log information as possible.
Installation Problem Installation Problem If you receive the following message during installation: /usr/openv/netbackup/bin/version not found. Add-On Product Installation Aborted. you have tried to install the ServerFree Agent add-on software before installing the base NetBackup 4.5 software. Removing a Frozen Image NetBackup ordinarily removes frozen images after the ServerFree Agent backup completes.
Removing a Frozen Image b. To remove a leftover snapshot, enter /usr/openv/netbackup/bin/driver/snapoff snap1 ... snapn For more information on the snap driver commands, refer to the “ServerFree Agent Commands” appendix of this guide. For vxvm: a. Enter the following to display unsynchronized mirror disks: vxprint -g diskgroup b. Enter the following to resynchronize the mirror disks: vxassist -g diskgroup -v volume snapback For fsclone: a.
Removing a VxVM Volume Clone For Hitachi and HP arrays (ShadowImage, BusinessCopy): pairresync -g groupname -d dev_name For more information about EMC, Hitachi, and HP arrays and about resynchronizing disks, refer to the chapter “Extended Frozen Image Services (Array Integration Option).” Removing a VxVM Volume Clone A form of frozen image that might need manual deletion is a VxVM volume clone. See “Disk Group Clones” on page 113 for a description of disk clones.
Removing a VxVM Volume Clone In this example, clone_wil_test_clone was created for a frozen image backup that was configured with Extended Frozen Image Services. If a backup failed with log entries similar to those included above, the clone must be manually deleted. 2.
VfMS Error Conditions VfMS Error Conditions Note For explanations of NetBackup error codes, refer to the “NetBackup Status Codes and Messages” chapter in the NetBackup Troubleshooting Guide. For VfMS errors in the /usr/openv/netbackup/logs/online_util log, refer to the following for an explanation of the VfMS error codes.
VfMS Error Conditions VfMS Method Errors Frozen Image Method: nbu_snap 0 - no error 1 - memory allocation error 2 - error in parsing string 3 - system error 4 - cannot open snap driver 5 - cannot turn snapshot on 6 - cannot turn snapshot off 7 - invalid argument Frozen Image Method: vxvm 0 - no error 1 - memory allocation error 2 - error in parsing string 3 - system error 4 - error opening a file 7 - invalid argument 8 - no available mirror to use as a frozen image 9 - file system resides on non-VxVM volum
VfMS Error Conditions 1 - memory allocation error 2 - error in parsing string 3 - system error 4 - error opening a file 5 - cannot split device 6 - cannot synchronize device 7 - invalid argument 8 - Illegal operation; invalid device 9 - Illegal operation; device is not a primary 10 - no BCV device for the standard device 11 - state of mirrored device is invalid for attempted operation 12 - General software API error 13 - Internal data or logic error 14 - Entry point not found File Mapping Method: dsk 1 - f
VfMS Error Conditions 2 - failed on fset_get 3 - invalid argument 4 - memory allocation error 5 - system call error 6 - cannot get inode information from special file 7 - file type does not match file system type 8 - map offset must be a multiple of 512 9 - file is too big File Mapping Method: vxfs 1 - failed to open fs_open 2 - failed on fset_get 3 - invalid argument 4 - memory allocation error 5 - system call error 6 - cannot get dnode information from special file 7 - file type does not match 8 - map of
VfMS Error Conditions 4 - no volume for device 6 - volume not active 7 - no plex for the volume 8 - invalid argument 9 - system call error 10 - no vxvm notify received 11 - vxvm configuration call failed 12 - RAID5 in degraded mode 100 - library not loadable 101 - Entry point not found 102 - library not initialized 103 - O/S call failed 104 - VxVM not installed 105 - unsupported VxVM version Online Services Error Codes 0 - the requested operation was successfully completed 6 - the backup failed to back up
VfMS Error Conditions 69 - invalid filelist specification 77 - execution of the specified system command returned a nonzero status 158 - failed accessing daemon lock file 227 - no entity was found Offhost Backup and Data Movement Error Codes 9 - an extension package is needed, but was not installed 20 - invalid command parameter 21 - socket open failed 23 - socket read failed 24 - socket write failed 25 - cannot connect on socket 26 - client/server handshaking failed 43 - unexpected message received 83 -
Process Diagrams for Offhost Backup Process Diagrams for Offhost Backup NetBackup Media Server: Copy-On-Write Process The following diagram shows the major components for making a backup using the NetBackup Media Server method with a copy-on-write snapshot frozen image. Numbers refer to descriptions on the next page.
Process Diagrams for Offhost Backup 1. The NetBackup master server or client initiates the backup, causing the NetBackup request daemon bprd to start the scheduler, bpsched. bpsched processes the policy configurations depending on the initiator of the backup (scheduled, immediate manual, or user directed). Refer to Appendix A of the NetBackup Troubleshooting Guide for more information on this stage of the backup operation. 2.
Process Diagrams for Offhost Backup NetBackup Media Server: Mirror Process The following diagram shows the major components for making a backup using the NetBackup Media Server method with a mirror frozen image. Numbers refer to descriptions on the next page.
Process Diagrams for Offhost Backup 1. The NetBackup master server or client initiates the backup, causing the NetBackup request daemon bprd to start the scheduler, bpsched. bpsched processes the policy configurations depending on the initiator of the backup (scheduled, immediate manual, or user directed). Refer to Appendix A of the NetBackup Troubleshooting Guide for more information on this stage of the backup operation. 2.
Process Diagrams for Offhost Backup Third-Party Copy Device: Copy-On-Write Process The following diagram shows the major components for making a backup using the NetBackup Third-Party Copy Device method with a copy-on-write snapshot frozen image. Numbers refer to descriptions on the next page.
Process Diagrams for Offhost Backup 1. The NetBackup server or client initiates the backup, causing the NetBackup request daemon bprd to start the scheduler, bpsched. bpsched processes the policy configurations depending on the initiator of the backup (scheduled, immediate manual, or user directed). Refer to Appendix A of the NetBackup Troubleshooting Guide for more information on this stage of the backup operation. 2.
Process Diagrams for Offhost Backup Third-Party Copy Device: Mirror Process The following diagram shows the major components for making a backup using the NetBackup Third-Party Copy Device method with a mirror frozen image. Numbers refer to descriptions on the next page.
Process Diagrams for Offhost Backup 1. The NetBackup server or client initiates the backup, causing the NetBackup request daemon bprd to start the scheduler, bpsched. bpsched processes the policy configurations depending on the initiator of the backup (scheduled, immediate manual, or user directed). Refer to Appendix A of the NetBackup Troubleshooting Guide for more information on this stage of the backup operation. 2.
Process Diagrams for Offhost Backup 148 NetBackup ServerFree Agent System Administrator’s Guide
A ServerFree Agent Commands This appendix describes commands used with NetBackup ServerFree Agent. The following are special conventions used in the command descriptions. ◆ Brackets [ ] mean that the enclosed command line component is optional. For example, assume that a command has the following format: command [arg1] The user can either choose arg1 or omit it. ◆ A vertical bar (or pipe) symbol | separates optional arguments.
bptpcinfo(1M) bptpcinfo(1M) NAME bptpcinfo - discovers SAN devices and creates a 3pc.conf file. SYNOPSIS /usr/openv/netbackup/bin/bptpcinfo [-a] [-c] [-h] [-u] [-v] [-x client_name] [-d disk_device_directory] [-t tape_device_directory] [-p physical_device] [-o output_file_name] [-o -] DESCRIPTION The bptpcinfo command lists all source and destination devices on the SAN, such as disk and tape drives and third-party copy devices, and provides information about each device (one line per device).
bptpcinfo(1M) -v Specifies verbose mode, causing bptpcinfo to list information on its discovery progress. The information is written to the screen, not to the 3pc.conf file. Note You should select the -v option only to track problems in device discovery and then delete that information from the 3pc.conf file. If left in the 3pc.conf file, the verbose information will cause the backup to fail.
bptpcinfo(1M) Example 2 Discover all source and destination devices on the SAN, and send the output to the screen.
bptpcinfo(1M) Example 4 Create a 3pc.conf file that describes all devices on the SAN, and send the output to an alternate file: /usr/openv/netbackup/bin/bptpcinfo -a -o /usr/openv/volmgr/database/3pc_alt1.conf NOTES ◆ The bptpcinfo command should be run when no backups are in progress. If a device is being used (or is reserved) by a backup, the bptpcinfo command may not be able to obtain information on the device, thus omitting the device from the output.
bpmoverinfo(1M) bpmoverinfo(1M) NAME bpmoverinfo - discovers the third-party copy devices available on the SAN and creates a mover.conf file. SYNOPSIS /usr/openv/netbackup/bin/admincmd/bpmoverinfo [-u] [-h] [- output_file_name] [-o -] DESCRIPTION The bpmoverinfo command discovers the devices on the SAN that can operate as third-party copy devices (data movers), and by default writes the information to file /usr/openv/volmgr/database/mover.conf.
bpdgclone(1M) bpdgclone(1M) NAME bpdgclone - creates or removes clones of Volume Manager (VxVM) volumes.
bpdgclone(1M) -f Specifies an output file. This file contains a list of pathnames of the primary disks over which the target volume is configured. Use this option to discover the primary disks that make up the target volume. NOTES ◆ A clone should not be removed while the frozen image backup using that clone is still in progress. Barring any system failures, NetBackup will remove the clone when the backup completes.
Solaris snapctl Driver Solaris snapctl Driver The snap driver is invoked by NetBackup under either of the following circumstances (Solaris systems only): ◆ If the nbu_snap frozen image method is configured for the frozen image source that is being backed up. ◆ If the client is in a FlashBackup policy and no frozen image method is configured (Allow frozen image clients on the New/Change Policy display is not checked).
Solaris snapctl Driver If snapoff is successful, a message of the following form will be displayed: snap 1 disabled snap 2 disabled ... snap n disabled If snapoff fails, an explanatory message is displayed. Error codes are identified in /usr/include/sys/errno.h.
Solaris snapctl Driver ◆ free is the number of 512-byte blocks available. ◆ busy is the number of 512-byte blocks that have been written to. When a cache is full, any write to a snapped partition or snapped file system associated with that cache will cause the snapshot to fail and the snapshot will no longer be readable or writable. Reads or writes to the snapped partition will remain unaffected.
Solaris snapctl Driver 160 NetBackup ServerFree Agent System Administrator’s Guide
Index manual 124, 125 messages 128 of snapshot 15 offhost configuration 79 prerequisites 122 raw partition 122 SCSI offhost 25 techniques (overview) 12 upgrading from 4.0V 38 user-directed 124 Backup Policy Configuration wizard 74, 84 BCV 95, 119, 120 best practices 115 block device file (vs character) 90, 122 bp.
overflow 157 partition 85 requirements 90 size 157 specifying raw partition for 90 CACHE=entry 85 Change Policy dialog 79 Chaparral 63 character device file (vs block) 90, 122 checking logs 128 checkpoint removing 131 removing (VxFS) 131 class (see policy) client configuration overview 75 client data prerequisites for offhost backup 122 client option (on bptpcinfo) 46, 66 Client Properties dialog 76 clone removing 131, 132 clone (VxVM disk group) 113, 132, 155 clone, in VxFS file system 88 Common Serial Num
block vs.
lock file system 18, 20 logical volume (as raw partition) 90 logs 128 VfMS errors in 134 loop (Fibre Channel) 4 LUN 53, 60 NetBackup for EMC upgrading from 119 NetBackup Media Server defined 6, 9 network diagram of 23, 44 process overview 27, 140 selecting 80 nport 60 M manual backup 124 manuals x mapping 22 defined 5 information 141, 143, 145, 147 Maximum jobs per client 85 Maximum multiplexing per drive 85 maximum pathname length 74, 81 Media multiplexing 85 media server (see NetBackup Media Server) mes
types supported 8 policy_name (on mover.conf file) 64, 67, 69, 129 poll 101 port name using SANPoint Control 53 primary to mirror association 98 Q quiesce 13, 18 R RAID Manager daemons 104 RAID-5 88 RAID5 117 raw partition as frozen image source 81 block vs.
st.conf 51, 55 stack quiescing 20 standard (primary) disk 95 status code 11 132 storage checkpoint (see fsclone frozen image method) storage devices 74 storage unit 64, 67, 80, 84 storage_unit_name (on mover.conf file) 129 storage_unit_name version of mover.
world-wide port name 60 when upgrading from 4.
168 NetBackup ServerFree Agent System Administrator’s Guide
