Important Terms Master ServerThe master server manages data protection operations.

. Any computer that has NetBackup server software installed can be designated as the master server. There can be only one master server per storage domain. The NetBackup master server is responsible for the following functions: Containing the backup configurations and policies Running the scheduler that initiates automated backups Maintaining catalogs that track the location and contents of all backups Communicating with media servers to initiate backup and restore processes Providing both a command line interface and a graphical user interface to administer NetBackup Enterprise Media Manager Server (NetBackup 6)NetBackup Enterprise Server 6.0 introduced the Enterprise Media Manager (EMM) server, which centrally manages Media Manager data that had previously been distributed across multiple media servers. There can be only one EMM server per storage domain. The master server can also be designated as the EMM server. The NetBackup EMM server is responsible for the following functions: Managing a consolidated media and device database for the NetBackup storage domain Maintaining run-time status information, NDMP credentials, and a managed server list Media ServerA media server can be any standalone server running NetBackup server software that receives requests for backup and restore operations from the master server. (A master server can Enterprise Backup Solution with Symantec NetBackup Enterprise Server implementation guide 9 also be configured as a media server.) A storage domain can contain multiple media servers. Media servers perform the following functions: Communicate with the master server and EMM server (beginning with NetBackup 6) to initiate backup and restore operations on its attached storage devices Communicate with NetBackup clients during a backup or restore operation Monitor the status of storage devices Provide robotic control NOTE: There can be only one robotic control host per library. ClientNetBackup clients are servers that have NetBackup client software installed. With the proper conditions set, a client can perform the following functions: Perform backups over the LAN through a media server Validate connection requests from the NetBackup server Support compression of the backup stream Support include and exclude lists Storage UnitA storage unit consists of the media server and tape devices where NetBackup stores files and data. If a storage unit contains two drives and one is busy, NetBackup can use the other drive without administrator intervention. A NetBackup storage unit is a storage device attached to a NetBackup server. To send backups to a storage device, the administrator needs to define storage units using the Device Configuration Wizard. Two types of storage units can be used in an EBS environment: Media Manager storage units This type of storage unit encompasses the tape robots, standalone tape drives, and optical disk devicesall of which are under the control of Media Manager or EMM. Media Manager or EMM controls the allocation and mounting of media (called volumes) in the storage devices. Disk storage units

A disk type of storage unit consists of a directory on a disk that stores data. NetBackup permits an unlimited number of disk storage units. Media Manager/Enterprise Media Manager Media Manager or Enterprise Media Manager (EMM), which are components of NetBackup, manages the robots, tape drives, and removable media. Media Manager or EMM primarily uses four tools: The Device Configuration Wizard, which guides you through device configuration in a step-by-step manner. The Volume Configuration Wizard, which guides you through volume configuration in a step-by-step manner. The Media and Device Management graphical interface, which allows you to reconfigure storage devices and volumes separately. The Device Monitor graphical interface, which displays pending requests for volumes and allows you to control and manage devices. EBS-Specific Requirements EBS with Symantec NetBackup Enterprise Server requires the Shared Storage Option to be installed on all media servers. One server must be designated as the master server, while the others will be designated as media servers. Refer to Symantec documentation for details on the minimum requirements of each server: http://support.veritas.com. Virtual Library System (VLS) When configuring the HP StorageWorks Virtual Library System (VLS) for use in an EBS environment with Symantec NetBackup, HP VLS must be selected as the library emulation. NetBackup requires the use of this emulation in all HP StorageWorks VLS products for device support purposes. Enterprise Backup Solution with Symantec NetBackup Enterprise Server implementation guide 10 Shared Storage Option The Shared Storage Option (SSO) allows individual tape drives to be dynamically shared between multiple NetBackup media servers. Each media server can access any of the shared drives as needed and each server owns the drive it has active. The shared drives are automatically allocated and deallocated as backup and restore operations dictate. NetBackup provides the Device Configuration Wizard to make configuring shared drives fast and easy. Using this wizard helps eliminate common mistakes that are made when SSO configuration is done manually. The wizard should be run on all media servers. The wizard: Performs device discovery Adds robotic libraries and shares drives to the Media Manager configuration Creates storage units Allows use of device persistency services Allows NetBackup to use device serialization (if supported by the robot or tape device)

2 Installation and Configuration

Before installing your backup software, refer to the HP StorageWorks EBS Design Guide for assistance in setting up your hardware.

Installation Checklist
If the answer to each of the following questions is yes, then all components on the SAN are logged in and configured properly. Are all hardware components at the minimum supported firmware revision (HBA, Fibre Channel switch, router, Interface Manager (IM), tape library drives, tape library robot)? Is the minimum patch level support for the operating system installed? Are the minimum supported drivers installed (HBA, tape drives)?

 Is the tape library online? Are all tape and robotic devices mapped and configured on the router or in Command View TL? Is the router correctly logged into the Fibre Channel switch? Is the host server correctly logged into the Fibre Channel switch? If the Fibre Channel switches are cascaded or meshed, are all Interswitch Link (ISL) ports correctly logged in? Are the router and the host server HBA in the same switch zone (by World Wide Name (WWN) or Port)? Does the host server detect all of the tape and robotic devices intended to be used? NOTE: HP recommends placing devices in host-centric zones and then making them available to the server. Host-centric zoning is implemented by creating a specific zone for each server or host and adding only those storage elements that will be utilized by that host. Host-centric zoning prevents a server from detecting any other devices on the SAN, including other servers. Host-centric zoning also simplifies the device discovery process.

Installation Best Practices

Follow the HP StorageWorks EBS Compatibility Matrix and the HP StorageWorks Enterprise Backup Solution Design Guide. The matrix of hardware, software, and firmware is updated monthly and helps customers and support personnel maintain their EBS environment. It is not necessary to immediately update an environment to the latest revision on the matrix. However, be aware of updates and changes if any problems occur that may be related to newer or older software, driver, and/or firmware versions. The design guide describes currently supported EBS hardware configurations and how to efficiently and effectively provide shared tape library backup in a heterogeneous SAN environment. Use SCSI RESERVE/RELEASE. SCSI RESERVE/RELEASE is enabled by default in Symantec NetBackup Enterprise Server. Use the Device Configuration Wizard. This wizard coordinates device configuration among all the hosts in a shared storage environment. It is essential that all hosts be configured properly with the appropriate device name, index, robot drive number, media, and drive type. NOTE: Using the Device Configuration Wizard allows NetBackup to use drive serialization. If the library/drives are configured manually, serialization will not be used and may cause issues. Limit rebooting during backup windows.
Enterprise Backup Solution with Symantec NetBackup Enterprise Server implementation guide 13

Rebooting servers in a SAN environment during the backup operations of another server can cause job failures and/or configuration errors. When rebooting is necessary, verify the tape device configuration of the host remains unchanged when maintenance or reboot is complete. Re-run the configuration wizard if necessary. For mixed media environments, refer to the HP StorageWorks Implementating Mixed Media in HP StorageWorks Tape Libraries Implementation Guide by selecting the Technical documentation link at http://www.hp.com/go/ebs.

Installing Symantec NetBackup Enterprise Server

After all components on the SAN are logged in and configured, the system is ready for installation of NetBackup Enterprise Server. Refer to the Symantec NetBackup Installation

Guide or contact Symantec customer support for detailed installation procedures and requirements. Symantec provides several wizards to help you install and configure the master server and media servers.

Installing NetBackup Server Software

Symantec recommends installing in the following order: 1. For NetBackup 6.0 and later, install Infrastructure Core Services/Private Branch Exchange (ICS/PBX) on all servers (for older versions, proceed to step 2) 2. Master server 3. Media servers 4. NetBackup Remote Administration Console (if any) 5. NetBackup clients 6. NetBackup add-on products (such as NetBackup for Oracle) NOTE: HP recommends backup software currently configured on your system be removed before installing NetBackup. The following items can negatively affect how NetBackup installs and functions: Other backup software Tape device applications that are part of the operating system or test utilities SAN or system management software

Device Configuration Wizard

After installing NetBackup software, storage devices must be defined before any backups can be run.NetBackup provides the Device Configuration Wizard to make configuring shared drives fast and easy.Using this wizard helps eliminate common mistakes that are made when SSO configuration is donemanually. HP strongly recommends using the Device Configuration Wizard. NOTE: Be sure that all media servers have the latest Symantec NetBackup maintenance pack or feature pack installed. For additional information visit the Symantec support website: http://support.veritas.com. Use the Device Configuration Wizard to: Specify device hosts in NetBackup 5.x or earlier (in NetBackup 6.0, device hosts are automatically added to the Enterprise Media Manager (EMM) database and do not need to be specified) Scan hosts for back-up devices Verify the devices that were automatically detected Verify and correct the drive configuration Update the drive configuration
Enterprise Backup Solution with Symantec NetBackup Enterprise Server implementation guide 14

Configure storage units NOTE: Be sure to stop and restart NetBackup services on the master server after adding a storage unit, otherwise the master server will return a message that says the storage unit is not available.

Device Serialization
The Device Configuration Wizard uses device serialization, a library feature that allows device identification and configuration. Each robot and drive found in the configuration returns a unique serial number. For any robots in the configuration, an additional command is issued to the robot. The robot

returns the number of drives and the serial number for each of the drives contained in the library. Thisinformation is used by the wizard to determine the correct drive number for each drive in the library. NOTE: If the Device Configuration Wizard is unable to detect serial numbers of the robot or tape drives,(which can happen when the drive or library firmware is upgraded) check via the library front panel to ensure the library reports a serial number for each device.

Creating Policies
A policy must be created before performing a backup. A schedule must be created. A policy can contain multiple clients, but all clients must be the same type, such as Windows or Standard. After creating a policy, run a manual backup to test the policy.

Performance and Tuning

To analyze speed and performance, it is necessary to examine the entire backup process as a system.Although many factors contribute to the overall performance of the system, there are five main factors that must be thoroughly understood to determine the maximum performance in any specific situation. These factors are: Storage ConnectionFor EBS, this is the Fibre Channel connection. Buffer AllocationEBS with Symantec NetBackup Enterprise Server supports configurable buffer sizes. See Buffer Allocation for specified details. File (Data) Compression RatioThe amount of compression has a direct impact on the rate at which a tape drive can read/write data. Source Disk and File SystemsData source, local disk, RAID array storage, file system type, andvolume type. Tape DriveIn the EBS, these are the various types of tape drives in HP StorageWorks Libraries.

Buffer Allocation
Buffer sizes can be set to maximize the performance of tape drives. Two text files, SIZE_DATA_BUFFERS and NUMBER_DATA_BUFFERS, created in <install_path>/netbackup/db/config/, are used to optimize the tape drive buffers. For documentation on modifying buffer sizes, refer to http://support.veritas.com. NOTE: If either of these files are changed, be sure that the new specifications are appropriate for all media on that media server.
Enterprise Backup Solution with Symantec NetBackup Enterprise Server implementation guide 15

File (Data) Compression Ratio

HP tests show that not all data can be compressed equally. The compression ratio affects the amount of data that can be stored on each tape cartridge, as well as the speed at which the tape drives can read or write the data. Table 2 shows typical compression ratios of various applications.

Source Disk and File Systems

In the past, tape performance was typically identified as a bottleneck. However, tape performance has now surpassed many of the source systems available today. Items to consider when calculating desired throughput and performance metrics include: Source hardware (disk subsystems) Source filesystem status Server configuration The following factors critically affect the speed of backup from disk to tape: Data file size

The larger the number of smaller files, the larger the overhead associated with backing them up. The worst-case scenario for backup is large numbers of small files due to system overhead of file accession. Data compressibility Incompressible data will back up slower than higher compressible data. For example, JPEG files are not very compressible, but database files can be highly compressible. The accepted standard for quoting tape backup specifications revolves around an arbitrary figure of 2:1 compressible data. Disk array performance It is often overlooked that data cannot be put onto tape any faster than it can be read from disk. Backup is more sequential in nature than random (from a disk array access perspective). Disk array performance depends on the number of disks, RAID configuration, the number of Fibre Channel ports accessing the array, and queue depth available, for example. Fragmentation The more fragmented the files are on disk, the more random will be the disk access method, hence the backup will take longer. If the system has a defragmentation utility, it is advisable to run it before full backups or on a regular scheduled basis to ensure that files are contiguously arranged on the disk. For more information on factors that can affect tape performance see the Getting the most performance from your HP StorageWorks Ultrium 960 tape drive white paper: http://h18006.www1.hp.com/storage/tapewhitepapers.html.

Tape Drive
The tape drive is the fifth factor in determining backup and restore performance. HP tape drives have varying levels of performance. Factors such as file size (larger is better), directory depth, and datacompressibility all affect system performance. Data interleaving during backup also affects restore

1.bpmedialist bpmedialist queries one or more NetBackup media catalogs and produces a report on the status of the NetBackup media. Authorized users can run this command. For more information about NetBackup authorization, refer to the NetBackup Security and Encryption Guide. bpmedialist produces one of four reports: Media List Report, Media Summary Report, Media Contents Report, Media Count Report.

2.bpimmedia
bpimmedia queries the NetBackup image catalog and reports on the NetBackup images. bpimmedia produces two types of reports: An Images-on-Media report A Spanpools report The first form of bpimmedia in the SYNOPSIS displays a set of NetBackup images in the Images-on-Media report. This report lists the contents of media as recorded in the NetBackup image catalog. You can generate this report for any medium (including disk. Filter the report contents according to client, media ID, path, and so on. Refer to the section on NetBackup Reports in the NetBackup Administrators Guide for more information, including details about

the fields in the Images-on-Media report. The report does not show information for the media that is used in backups of the NetBackup catalogs. Several new options (-dt, -dp, -dv, -stype) report images present on SAN disk storage only, not on any other disk-resident images. Other options and output format continue to function as before. The second SYNOPSIS form of bpimmedia uses -spanpools to list the disk ID pools that are related because images span from one volume to another. The output lists, for each media server in the cluster, the media IDs that have

3.bpimagelist Uses a specified format to report on catalog images or the removable media that match the attributes that are sent from the command options. It writes its debug log information to the following directory: /usr/openv/netbackup/logs/admin You can use the information in this directory for troubleshooting. The output of bpimagelist goes to standard output. When running the bpmedialist -L command, a hex value is returned for the status of the tape.
Code: 0x0 0x01 0x02 0x04 0x08 0x10 0x20 0x40 0x80 0x100 0x200 0x400 Status: ACTIVE FROZEN SUSPENDED Description: Indicates the tape is in use for backups Indicates tape is frozen and to not use tape for writing Indicates tape is suspended and to not use for writing until tape is expired REC_FREE Indicates the record is no longer in use MEDIA_FULL Indicates the media id is FULL NEW_SCR Indicates the tape is newly allocated scratch media and needs a header NOMEDIA_EOM Indicates that after End of Media(EOM) is encountered there is no more media MULT_RETLEV Indicates there are multiple retention levels on the media IMPORTED WAS_FULL MPX_MEDIA FAKE_ENTRY Indicates the media was created via import process Indicates if FULL status was cleared on last image delete Indicates if media contains some mpx images Used for alternate server restores

Note: The status 0x1 FROZEN and 0x2 SUSPENDED can be combined with other status codes. Example:
0x81 0x82 This indicates the tape is This indicates the tape is

IMPORTED and FROZEN. IMPORTED and SUPSENDED.

Determine tape drive serial number / library drive number / rmt number matches: o /usr/openv/volmgr/bin/goodies/scan (list tape drives/serial numbers in library drive order) o lscfg v | grep p 3580 (list tape drives/serial numbers and rmtx device names) o optionally, you can run /usr/local/netbackup/tape_scan to retrieve data

: Define library and drives o Start Netbackup processes via bp.start_all o tpconfig -add -robot 0 -robtype tld -robpath /dev/ovpass0 o tpconfig -add -drive -type hcart2 -path /dev/rmt1.1 -asciiname ltof2d1 -index 1 -shared no -robot 0 -robtype tld -robdrnum 1 (for each drive; use the serial number/drive matching from previous step to ensure drives are defined in the proper order) o bp.kill_all o bp.start_all o tpconfig d (verify library and drive definitions) o /usr/local/netbackup/tape_scan (verify drive order) Update tape inventory from library in Netbackup o Edit /usr/openv/volmgr/vm.conf placing entries to use correct barcode string o MEDIA_ID_BARCODE_CHARS 0 8 1:2:3:4:5:6 o /usr/openv/volmgr/bin/vmupdate -rn 0 -rt tld -rh apaha058 -h apaha058 -use_barcode_rules o Ensure all tapes are showing in the library including the catalog tape

Netbackup Master Server Install & Configure Procedure

The following is specific master installation procedure steps under AIX enviornment which as same as currently working environment. NBU installation step overview: 1. Mounting a NetBackup CD-ROM 2. Installing NetBackup Server Software 3. Configuring Automatic Startup and Shutdown of NetBackup 4. Configuring Storage Devices for the Operating System 5. Configuring NetBackup Server Software AIX Tape Drive Request: Atape.driver 8.2.5.0 COMMITTED IBM AIX Enhanced Tape and devices.fcp.tape.rte 5.1.0.51 COMMITTED FC SCSI Tape Device Software devices.scsi.tape.diag 5.1.0.50 COMMITTED SCSI Tape Device Diagnostics devices.scsi.tape.rspc 5.1.0.0 COMMITTED RISC PC SCSI Tape Device devices.scsi.tape.rte 5.1.0.51 COMMITTED SCSI Tape Device Software devices.fcp.tape.rte 5.1.0.25 COMMITTED FC SCSI Tape Device Software Mounting a Netbackup CD-ROM 1. Login as root. 2. Mount the CD-ROM using either of the following methods:

 You can use the smitty cdrfs and smitty mountfs commands to mount the CD-ROM. Enter: smitty cdrfs OR Enter: smitty mountfs Follow the instructions to mount the CD-ROM file system. You can also mount the CD-ROM manually. Create the mount point (for example, mkdir /cdrom). Enter: mount -v cdrfs -r device_path mount_point For example, to mount the CD-ROM manually using /cdrom as the mount point, you would enter: mount -v cdrfs -r /dev/cd0 /cdrom Installing NetBackup Server Software 1. log on as the root user on the server. 2. Change your working directory to the CD-ROM directory: cd cd_rom_directory 3. Execute the install script: ./install Configuring Automatic Startup and Shutdown of NetBackup AIX /etc/rc.veritas.aix Note You will need to edit /etc/inittab to add the following entry so this script is called during a level two boot: veritas:2:wait:/etc/rc.veritas.aix. Note To shut down, add the following line to /etc/rc.shutdown: /etc/rc.veritas.aix stop. Configuring Storage Devices for the Operating System Before start the configuration of Netbackup storage devices. It must be make sure all the device tapes have been already recognized on the operating system level. The following commands to verify devices reorganization status on OS level. lsdev Cc tape smitty devices After confirm devices could be found on the OS. Then, we can start the devices configuration for Netbackup. In the Veritas Netbackup, it has used a driver called ovpass to control the library robotic arm. So, we will need to configure the ovpass driver at the beginning. Following steps is ovpass configuration procedure. /etc/rc.veritas.aix/etc/inittab veritas:2:wait:/etc/rc.veritas.aix/etc/rc.shutdown/etc/rc.veritas.aix stop/etc/rc.veritas.aix/etc/inittab veritas:2:wait:/etc/rc.veritas.aix/etc/rc.shutdown/etc/rc.veritas.aix stop1. /usr/openv/volmgr/bin/driver/install_ovpass 2. /usr/sbin/lsdev -C | grep I/O Check which fcscsi interface is connected with tape library (Note: it will be same as rmt driver) 3. lsdev |grep smc

smc0 Available 14-08-01 IBM 3584 Library Medium Changer (FCP) 4. /usr/bin/odmget -q name=smc0 CuAt CuAt: name = smc0 attribute = scsi_id value = 0x111ca type = R generic = DU rep = s nls_index = 25 CuAt: name = smc0 attribute = lun_id value = 01000000000000 type = R generic = DU rep = s nls_index = 26 In the above example output, the SCSI ID is 0x111ca and the lun is 1. The lun is derived from the lun ID, by right shifting it 48 bits. 5. mkdev -c media_changer -s fcp -t ovpass -p > -w >,> > mkdev -c media_changer -s fcp -t ovpass -p fsp0 -w 0x111ca,1 (Note: The controller may be called fscsi0 or fscsi1, it need to verify by smitty) 6. Restart the Netbackup service to take effect of the ovpass driver /usr/openv/netbackup/bin/goodies/netbackup start Configuring NetBackup Server Software After completed the ovpass configuration, we can starting to configure the device robotic & tape devices configuration. Afterward is the volume pool, storage unit, backup policy. /etc/rc.veritas.aix/etc/inittab veritas:2:wait:/etc/rc.veritas.aix/etc/rc.shutdown/etc/rc.veritas.aix stop/etc/rc.veritas.aix/etc/inittab veritas:2:wait:/etc/rc.veritas.aix/etc/rc.shutdown/etc/rc.veritas.aix stop
netbackup configuration Example 1. NetBackup software

Master Server root@hkbkpp01:/netbackup # cd /cdrom root@hkbkpp01:/cdrom # ls Acrobat Alpha NetBackup_BS_GetStarted_UnixServer.pdf NetBackup_DC_Install_UnixServer.pdf

AutoRun AutoRun.inf Common Doc JavaInstallFiles Macintosh NB-Java NBClients

Os2 PC_Clnt Readme_NT.txt X86 hp700 hp800 install solaris

root@hkbkpp01:/cdrom # cd s* root@hkbkpp01:/cdrom/solaris # ls SUNWmmgr SUNWnetbp

root@hkbkpp01:/cdrom/solaris # pkgadd -d . * Processing package instance from VERITAS Media Manager (sparc) 3.4,REV=2000.06.23.16.09 Copyright 1993 2000 VERITAS Software Corporation, All Rights Reserved Media Manager binaries will be installed in /opt/openv/volmgr

is this okay? (y) [y,n,?,q] n Where do you want the ./openv/volmgr directory? /netbackup Media Manager binaries will be installed in /netbackup/openv/volmgr is this okay? (y) [y,n,?,q] Using as the package base directory. ## Processing package information. ## Processing system information. ## Verifying disk space requirements. ## Checking for conflicts with packages already installed. ## Checking for setuid/setgid programs.

This package contains scripts which will be executed with super-userpermission during the process of installing this package. Do you want to continue with the installation of [y,n,?] yInstalling VERITAS Media Manager as ## Executing preinstall script. create /netbackup/openv ## Installing part 1 of 1. /netbackup/openv/man/share/man/man1/tpreq.1 /netbackup/openv/man/share/man/man1m/tlhcd.1m ## Executing postinstall script. Copied files to /kernel/drv. Doing add_drv of the sg driver Leaving existing sg configuration. If you wish to update the configuration you need to rm -f /kernel/drv/sg.confand rerun /usr/openv/volmgr/bin/driver/sg.install.Media Manager configuration was successful. Installation of was successful.Processing package instance from VERITAS NetBackup(sparc) 3.4,REV=2000.06.23.16.03 Copyright 1993 2000 VERITAS Software Corporation, All Rights Reserved NetBackup 3.4GA will be installed. There is an existing link from /usr/openv to /netbackup/openv. NetBackup will be installed in /netbackup/openv/netbackup is this okay? (y) [y,n,?,q] y The Solaris clients will be loaded. to load any other NetBackup clients onto the server? (y) [y,n,?] y Choose the Platform Client types you wish to install by selecting the platform type one at a time or select ALL client platforms. Platform Client Options 1. DEC Alpha 2. Auspex Do you want

3. CRAY/J90 4. DataGeneral 5. HP9000 6. INTEL (FreeBSD) 7. Linux (RedHat) 8. MACINTOSH (MacOSXS) 9. NCR 10. Pyramid 11. IBM RS6000 12. SCO 13. Sequent 14. SGI 15. Solaris 16. ALL client platforms q Quit client selection Enter Choice (Default is 16) [1-16,?,q] 11 16,?,q] q You have chosen to install: RS6000 Solaris Enter Choice (Default is 16) [1-

Is this the list you wish to use? (y) [y,n,?] yUsing as the package base directory. ## Processing package information. ## Processing system information. 6 package pathnames are already properly installed. ## Verifying package dependencies. ## Verifying disk space requirements. ## Checking for conflicts with packages already installed.

## Checking for setuid/setgid programs. This package contains scripts which will be executed with super-userpermission during the process of installing this package. Do you want to continue with the installation of [y,n,?] yInstalling VERITAS NetBackup as ## Executing preinstall script.## Installing part 1 of 1. /netbackup/openv/NBJava.install/netbackup/openv/netbackup/client/Solaris/Solaris_x86_2.6/xbp [ verifying class ] ## Executing postinstall script. The NetBackup binaries are installed. Read the release notes carefully.

If you ran pkgadd instead of ./install, you must run /usr/openv/netbackup/bin/install_bp to initiate NetBackup. Installation of was successful.root@hkbkpp01:/cdrom/solaris # root@hkbkpp01:/netbackup # cd openv/netbackup/bin root@hkbkpp01:/netbackup/openv/netbackup/bin # ls XKeysymDB XNB XNB.dt add_slave bpdm bpdynamicclient bpgp bphdb goodies index_clients initbpdbm initbprd install_bp install_client install_client_files merge_auth_templates nonroot_admin restore_notify session_notify

add_slave_on_clients bpinst admincmd backup_exit_notify backup_notify bp bpadm bparchive bpjava-msvc bpjava-usvc bplist bpmount bpps bprd

bpbackup bpbkar bpbrm bpcd bpclimagelist bpclntcmd bpdbm bpdbm.lock bpdbm_child bpdbm_parent

bprd_parent bprestore bpsched bptm client_config cp_to_client dbbackup_notify diskfull_notify fsanalyze ftp_to_client

session_start_notify tar update_clients update_dbclients userreq_notify version xbp xbpadm.cat xbpmon.cat

root@hkbkpp01:/netbackup/openv/netbackup/bin # ./install_bp A NetBackup BusinesServer or DataCenter license key is needed for installation to continue. Enter license key: BJN6-CPII-6XVR-6PPP-PPPP-POPP-PPPO-P Evaluation NetBackup DataCenter with Oct 19, 2000 expiration date will be registered. Is this OK? (y/n) [y] yBJN6-CPII-6XVR-6PPP-PPPP-POPP-PPPO-P: Evaluation NetBackup DataCenter Base product with all the features enabled has been registered. Installing NetBackup DataCenter version: 3.4GAIs hkbkpp01 the master server? (y/n) [y]Do you have any media (slave) servers? (y/n) [n] Checking for a bpcd entry in /etc/inetd.conf: Adding bpcd entry.Original /etc/inetd.conf saved as /etc/inetd.conf.NB_MM.3.4GA. Checking for a vopied entry in /etc/inetd.conf: Adding vopied entry. Checking for a bpjava-msvc entry in /etc/inetd.conf: Adding bpjava-msvc entry. Checking /etc/services for the needed NetBackup and Media Manager services.Copying original /etc/services file to /etc/services.NBU_081900.13:39:15Editing /etc/services to update NetBackup and Media Manager services. /etc/services will be updated to add the following entries for NetBackup/Media Manager.bprd 13720/tcp bprdbpcd 13782/tcp bpcd

bpdbm

13721/tcp

bpdbm vopied bpjava-msvc

vopied 13783/tcp bpjava-msvc vmd acsd tl8cd tldcd ts8d odld vtlcd tl4d tsdd tshd tlmd tlhcd lmfcd rsmd

13722/tcp vmd acsd tl8cd tldcd ts8d odld vtlcd tl4d tsdd tshd tlmd tlhcd lmfcd rsmd

13701/tcp 13702/tcp 13705/tcp 13711/tcp 13709/tcp 13706/tcp 13708/tcp 13713/tcp 13714/tcp 13715/tcp 13716/tcp 13717/tcp 13718/tcp 13719/tcp

To change these entries modify the file /tmp/services.ov_edited.3075and enter when ready to continue: /etc/services has been updated to contain NetBackup and Media Manager services.WARNING: ypwhich: the domainname hasnt been set on this machine.WARNING: ypcat: the domainname hasnt been set on this machine. Sending SIGHUP to inetd process.NetBackup startup command found in /etc/rc2.d.NetBackup shutdown command found in /etc/rc0.d. Extracting NetBackup-Java product files Installing NetBackup-Java, and the Java runtime environment for SunOS 5.6. Configuring NetBackup-Java runtime environment.

The installation of the NetBackup-Java product on hkbkpp01 is complete. In order for device discovery and auto-configuration to work properly in a DataCenter environment, particularly where peripherals are connected to multiple servers, one host must serve as the repository for global device configuration information. Enter which host will store global device information.(default: hkbkpp01):To be able to install the client software the NetBackupprocesses need to be started. Do you want to start the NetBackup processes so client software can be installed? (y/n) [y] Starting the NetBackup database manager process (bpdbm).Do you want to create class and schedule examples that you can view or usewhen you are configuring your own classes and schedules? (y/n) [y] Deleting NetBackup classes template_normal template_weekend enter ^C within 5 seconds to terminate creating class template_normal creating schedules for class template_normal creating class template_weekend creating schedules for class template_weekend Done creating example classes and schedules.Do you want to start the NetBackup bprd process sobackups and restores can be initiated? (y/n) [y] Starting the NetBackup request daemon process (bprd).Client database indexing reduces the search time when restoringclient files, but it takes about 2% more disk space. Do you want to index the client database files? (y/n) [y] The default index level is 9 levels. Use the default? (y/n) [y]Running index_clients process in background mode. Output from the process will be written to /tmp/index_clients.output. Do you want to add additional license keys now? (y/n) [y]nUse /usr/openv/netbackup/bin/admincmd/get_license_keyto add, delete or list license keys at a later time. root@hkbkpp01:/netbackup/openv/netbackup/bin # ls /dev/sgc0t0l0 c0t3l1 c1t0l0 c1t3l1 c2t0l0 c2t3l1 c3t0l0 c3t3l1 c4t0l0c0t0l1 c0t4l0 c1t0l1 c1t4l0 c2t0l1 c2t4l0 c3t0l1 c3t4l0 c4t0l1

c0t1l0 c0t4l1 c1t1l0 c1t4l1 c2t1l0 c2t4l1 c3t1l0 c3t4l1 c4t1l0 c0t1l1 c0t5l0 c1t1l1 c1t5l0 c2t1l1 c2t5l0 c3t1l1 c3t5l0 c4t1l1 c0t2l0 c0t5l1 c1t2l0 c1t5l1 c2t2l0 c2t5l1 c3t2l0 c3t5l1 c4t2l0 c0t2l1 c0t6l0 c1t2l1 c1t6l0 c2t2l1 c2t6l0 c3t2l1 c3t6l0 c4t3l0 c0t3l0 c0t6l1 c1t3l0 c1t6l1 c2t3l0 c2t6l1 c3t3l0 c3t6l1 root@hkbkpp01:/netbackup/openv/netbackup/bin # sgscan/dev/sg/c0t0l0: Disk (/dev/rdsk/c0t0d0): SEAGATE ST39102LCSUN9.0G/dev/sg/c0t6l0: Cdrom: TOSHIBA XM6201TASUN32XCD /dev/sg/c2t0l0: Tape (/dev/rmt/0): QUANTUM DLT7000 /dev/sg/c2t0l1: Tape (/dev/rmt/4): QUANTUM DLT7000 /dev/sg/c2t1l0: Tape (/dev/rmt/1): QUANTUM DLT7000 /dev/sg/c2t1l1: Tape (/dev/rmt/5): QUANTUM DLT7000 /dev/sg/c2t2l0: Tape (/dev/rmt/2): QUANTUM DLT7000 /dev/sg/c2t3l0: Tape (/dev/rmt/3): QUANTUM DLT7000 /dev/sg/c2t6l0: Changer: STK L180 Peripheral Types

root@hkbkpp01:/netbackup/openv/netbackup/bin # vmconf 1. NONE Not Robotic 2. TLD Tape Library DLT 3. TSD Tape Stacker DLT 4. TS8 Tape Stacker 8MM 5. TL8 Tape Library 8MM 6. TL4 Tape Library 4MM 7. ODL Optical Disk Library 8. TSH Tape Stacker Half-inch 9. Tutorial/Help

10. Exit Enter Choice [1-10] 2Do you want this script to check for the necessary devicefiles for the TLD? (if you answer no, this script will not perform any additional device or media configuration) (y/n) [y] Scanning for media changers connected to this system (This could take a few minutes.) Please select the media changer to be controlled using TLD robotics. SCSI-attached Media Changers: Vendor Model SCSI Control (SG) Path - 1. STK L180 /dev/sg/c2t6l0

2. None of the above Enter Choice [1-2] 1Enter the number of drives in the TLD [1-10] 6Please select the tape device to be configured as TLD robot drive number 1.SCSI-attached Tape Devices: Vendor Model SCSI Tape Path SCSI Control (SG) Path - - 1. QUANTUM DLT7000 DLT7000 /dev/rmt/4 3. QUANTUM DLT7000 4. QUANTUM DLT7000 5. QUANTUM DLT7000 6. QUANTUM DLT7000 /dev/rmt/0 (/dev/sg/c2t0l0)2. QUANTUM (/dev/sg/c2t0l1) /dev/rmt/1 /dev/rmt/5 /dev/rmt/2 /dev/rmt/3 (/dev/sg/c2t1l0) (/dev/sg/c2t1l1) (/dev/sg/c2t2l0) (/dev/sg/c2t3l0) Enter Media Manager Drive Type for

7. None of the above Enter Choice [1-7] 1 TLD drive 1 1. DLT Cartridge (dlt) 2. DLT Cartridge 2 (dlt2) 3. DLT Cartridge 3 (dlt3)

Enter Choice [1-3] 1Please select the tape device to be configured as TLD robot drive number 2.SCSI-attached Tape Devices: Vendor Model SCSI Tape Path SCSI Control (SG) Path - - 1. QUANTUM DLT7000 2. QUANTUM DLT7000 /dev/rmt/0 /dev/rmt/4 (/dev/sg/c2t0l0) (/dev/sg/c2t0l1)

3. QUANTUM DLT7000 4. QUANTUM DLT7000 5. QUANTUM DLT7000 6. QUANTUM DLT7000

/dev/rmt/1 /dev/rmt/5 /dev/rmt/2 /dev/rmt/3

(/dev/sg/c2t1l0) (/dev/sg/c2t1l1) (/dev/sg/c2t2l0) (/dev/sg/c2t3l0) Enter Media Manager Drive Type for

7. None of the above Enter Choice [1-7] 3 TLD drive 2 1. DLT Cartridge (dlt) 2. DLT Cartridge 2 (dlt2) 3. DLT Cartridge 3 (dlt3)

Enter Choice [1-3] 1and so on until drive 6, following /dev/rmt/# sequence You will be using /dev/sg/c2t6l0 for the robotics control. You will be using /dev/rmt/0cbn for the drive 1 non-rewind device name. You will be using /dev/rmt/1cbn for the drive 2 non-rewind device name. You will be using /dev/rmt/2cbn for the drive 3 non-rewind device name. You will be using /dev/rmt/3cbn for the drive 4 non-rewind device name. You will be using /dev/rmt/4cbn for the drive 5 non-rewind device name. You will be using /dev/rmt/5cbn for the drive 6 non-rewind device name. Do you want this script to add the robot and/or drive(s) to the Drive and Robot databases, instead of using xdevadm or tpconfig interactively? (if you answer no, this script will not perform any additional device or media configuration) (y/n) [y] Adding robots & drives to the Drive and Robot databases added robot number 0 of type TLD to configuration Adding drive to the configuration added drive index 0 of type dlt to configurationAdding drive to the configuration added drive index 1 of type dlt to configurationAdding drive to the configuration

added drive index 2 of type dlt to configurationAdding drive to the configuration added drive index 3 of type dlt to configurationAdding drive to the configuration added drive index 4 of type dlt to configurationAdding drive to the configuration added drive index 5 of type dlt to configuration(re)initiating the Media Manager device daemon (ltid) Use /usr/openv/volmgr/bin/tpconfig or xdevadm to alter the drive and robotconfiguration, if necessary, at a later time. Use /usr/openv/volmgr/bin/xvmadm or vmadm to addmedia to the volume configuration. root@hkbkpp01:/netbackup/openv/volmgr # echo SCRATCH_POOL = scratch > vm.confroot@hkbkpp01:/netbackup/openv/volmgr # stopltid root@hkbkpp01:/netbackup/openv/volmgr # ltid NOTE: ADDED tapes with 1 CLN tapesNOTE: CONFIGURED BARCODE RULES NOTE: CONFIGURED MULTIHOST DRIVES NOTE: ADDED MH_HOST_NAME TO VM.CONF root@hkbkpp01:/netbackup # exitroot@hkbkpp01:/usr/openv/netbackup # cd /var/tmp root@hkbkpp01:/var/tmp # ls2.6_Recommended _vmsa_cmd_ hrm7_Recommended blap.26363 manpagesAAA0KFj4S blap.27671 scriptsAAA0_cFd_ bpvault-dist_tar_Z.y vaultCMBiChase bpvault.solarisroot@hkbkpp01:/var/tmp # cat *y |crypt| uncompress|(cd /usr/openv/netbackup;tar xvf -)Enter key:x vault, 0 bytes, 0 tape blocks x vault/production/bpvault.tlm, 949 bytes, 2 tape blocks x vault/regform.txt, 1468 bytes, 3 tape blocks root@hkbkpp01:/var/tmp cd /usr/openv/netbackup/vault/productionroot@hkbkpp01:/usr/openv/netbackup/vault/prod uction # ls bpinject bpinject-tlm bpvault.acs bpvault.all bpvault.all.new bpvault.opsmenu bpvault.rs6000 bpvault.sequent bpvault.sgi bpvault.solaris bpvault.tlm bpvault.tlm.eject changecopy.sh dup_param.acs_example dup_param.tl8_example

bpvault.change bpvault.dec bpvault.env bpvault.hp800 bpvault.menu bpvault.ncr

bpvault.tl8 bpvault.tl8.eject bpvault.tld bpvault.tld.eject bpvault.tlh bpvault.tlh.eject

dup_param.tld_example dup_param.tlh_example dup_param.tlm_example haltdups.now version

root@hkbkpp01:/usr/openv/netbackup/vault/production # mv bpvault.solaris bpvault.solaris.oldroot@hkbkpp01:/usr/openv/netbackup/vault/production # cp /var/tmp/bpvault.solaris .root@hkbkpp01:/usr/openv/netbackup/vault/production # ln -s bpvault.solaris bpvaultNOTE: edit bpinject, dup_param, robot_inventory, bpvault.opsmenu, bpvault.env, create bpinject.sh Media Server The installation of a media server is more or less like a master server. By pkgadd-ing the packages SUNWmmgr and SUNWnetbp, the configuration is more or less done. The procedure is summarized to the following steps: 1. 2. 3. pkgadd SUNWmmgr as usual, do not need to install any client. pkgadd SUNWnetbp as usual. Run install_bp specifying the hkbkpp01 as the master server.

4. Use the master server to dump the client to the slave, therefore do not use the original client install (if installed). 5. Use vmconf to create the tape device, in xdevadm, create a robot with control host as the master server, and add the drives as multihost drives under the robot. 6. Add MH_HOSTNAME entry in the vm.conf.

7. Add SERVER entries in clients that will use it as the backup host, for trival reasons, it includes the slave itself. For the slave itself, the entry for itself must be on the 2nd line. 8. Create storage units in master server.

9. Create client for the slave. Since the client will be using itself as the backup server, using the nodename will be fine. 10. Create the corresponding classes for the slave to include the clients which will use it as the backup server

Here is an example for hkccsd01 Configure Fibre Switch 1) configure fibre switch for zoning configuration for new slave 2) enable new configuration 3) re-enable netbackup tape devices in server hkbkpp01 Add Hardware to hkccsd01 1) shutdown server with init 5 2) install ethernet card, and connect it to backup network 167.84.127.0 for qfe0 and 167.84.127.64 for qfe1 3) install fibre card and connect it to fibre switch 4) boot up server and login as root 5) from JNI CDROM, install package JNIfcaPCI with pkgadd -d /cdrom/cdrom0/SOLARIS/PCI/JNIFCA-PCIEMC.PKG 6) configure /kernel/drv/fca-pci.conf, set fca-nport=1 and dev_hba_binding=non-jni; 7) in /kernel/drv/st.conf, change entries From name=st class=scsi target=0 lun=0; name=st class=scsi target=1 lun=0; name=st class=scsi target=2 lun=0; name=st class=scsi target=3 lun=0; To name=st class=scsi target=0 lun=0 hba=fca-pci0 wwn=100000e00201a5cf; name=st class=scsi target=1 lun=0 hba=fca-pci0 wwn=100000e00201a5d1; name=st class=scsi target=2 lun=0 hba=fca-pci0 wwn=100000e00201a588; name=st class=scsi target=3 lun=0 hba=fca-pci0 wwn=100000e00201a5a7; Add name=st class=scsi target=0 lun=1 hba=fca-pci0 wwn=100000e00201a5cf; name=st class=scsi target=1 lun=1 hba=fca-pci0 wwn=100000e00201a5d1;