Session: HP Data Protector Best Practice Deployment (ID: I338)

Presenter:

Eamonn Fitzmaurice, Technology Consultant, Technology Services, HP.

 Topics
Architecture Installation and configuration Features of backups and restore operations Patching Common problems and resolutions Troubleshooting Performance Miscellaneous Q&A

Components of cell

Session flow

 Architecture
Disk agent and Media agent
Volume Backup Disk Agent (VBDA Raw Disk Backup Disk Agent (RBDA) Volume Restore Disk Agent (VRDA) Raw Disk Restore Disk Agent (RRDA) Filesystem Browse Disk Agent (FSBRDA)

Robotic Media Agent (UMA) Backup Media Agent (BMA) Restore Media Agent (RMA)

Processes
SH SYS /PROC=*OMNI*
00000482 OMNI$INET_BG679 HIB 00000483 OMNI$INET_BG691 HIB 00000484 OMNIADMIN_24924 LEF 00000485 OMNIADMIN_9580 LEF 5 5 5 5 568 569 603 607 0 00:00:00.13 0 00:00:00.09 0 00:00:00.09 0 00:00:00.08 614 614 493 493 608 608 615 615 N N S S

A OMNI$INET_BGXXX process is created for each disk agent and runs INET.EXE A OMNIADMIN_XXXX process is created for each disk agent also and runs VBDA.EXE Where the destination device runs on OpenVMS a further OMNIADMIN_xxxx process is created for every media agent and runs BMA.EXE So in Data Protector if we create a backup job with many disks we can have several hundred processes running!!!

DA and MA flow
If Media Agent and Disk agent are on same system then shared memory is used Otherwise data flow is via TCP/IP (Lan backup) System services used SYS$CRMPSC() SSP issue SSPUX611_027 replaced by SSPNT611_045 For performance recommend VBDA and BMA running on the same server i.e. SAN backup

Installation
Prerequisites
Mandatory HP TCP/IP (aka UCX) only Fibre_scsi OpenVMS patches Both ODS-2 and ODS-5 supported Installation Server (IS) is not supported Local install only using Polycenter software Installation Utility (PCSI) Note for Data Protector 6.20 that it requires minimum Integrity 8.3 and Alpha 7.3-2 onwards
Oracle 10g or 10gR2 (64 bit)

Oracle Support
No Oracle RDB support or API for RMU Oracle is supported via RMAN integration

http://tinyurl.com/65bu4v4 Filenames for 6.20 installation and sizes

1)ESD_HP_DP_6.2_for_Netware_OVMS_HP_Software_Integration_TD586_15000_02 2)ESD_HP_DP_6.2_for_HP_UX_TD586_15001_01.tar.gz 642.35 1654.83

3)ESD_HP_DP_6.2_for_Linux_TD586_15002_01.tar.gz
4)ESD_HP_DP_6.2_for_Solaris_TD586_15002_02.tar.gz 5)ESD_HP_DP_6.2_for_Windows_and_Media_Operation_TD586_15000_01.zip

1459.74
1469.06 1924.09

Available download from HP - 60 day trial Not part of layered products 6.20 on DVDs

Installation contd
Locations of installation files .
/Alpha/HP-AXPVMS-DP-A0620-351-1.PCSI /IA64/HP-I64VMS-DP-A0620-351-1.PCSI 6.20 supports Alpha 7.3-2, IA64 8.3 min 6.11 supports Alpha 7.3-2, IA64 8.2-1 min

See Installation and Licensing PDF doc in /DOCS directory

Installation contd
Before installing note . For all Data Protector versions On OpenVMS 8.3 and above, the installation displays the following message: %PCSI-I-CANNOTVAL, cannot validate [PATH]HP-AXPVMS-DP-A0611 -XXX-1.PCSI;1 -PCSI-I-NOTSIGNED. product kit is not signed & thus no manifest file To avoid this -I- run the install with /OPTION=NOVALIDATE_KIT. Cluster environment Installation

Common system disk perform install once. However, the OMNI$STARTUP.COM procedure needs to be executed for each node If you use a cluster TCP/IP alias name, you can define a client for the alias name as well if you are using a cluster common system disk.

Sample 6.20 PCSI Install

$ product install dp 1 - HP AXPVMS DP A6.20-370 E - Exit Layered Product

Choose one or more items from the menu: 1 Performing product kit validation of signed kits ... %PCSI-I-CANNOTVAL, cannot validate $2$DKA200:[EAMONN]HP-AXPVMS-DP-A0620-370-1.PC SI;1-PCSI-I-NOTSIGNED, product kit is not signed and therefore has no manifest file The following product has been selected: HP AXPVMS DP A6.20-370 Layered Product Do you want to continue? [YES] Configuration phase starting ... You will be asked to choose options, if any, for each selected product and for any products that may be installed to satisfy software dependency requirements. Configuring HP AXPVMS DP A6.20-370: HP AXPVMS DATA PROTECTOR V6.20 Do you want the defaults for all options? [YES] no Do you wish to install Disk Agent for this client node? [YES] y Do you wish to install Media Agent for this client node? [YES] y

Do you wish to install Command Language Interface for this client node? [YES] y
Do you wish to install Oracle Integration Agent for this client node? [NO] y

Sample 6.20 PCSI install contd

Do you want to review the options? [NO] Execution phase starting ... The following product will be installed to destination HP AXPVMS DP A6.20-370 DISK$ALPHASYS:[VMS$COMMON.] The following product will be removed from destination: HP AXPVMS DP A6.0-331 DISK$ALPHASYS:[VMS$COMMON.]

Portion done: 0%...10%...20%...30%...40%...80%...90%...100% The following product has been installed: HP AXPVMS DP A6.20-370 Layered Product The following product has been removed: HP AXPVMS DP A6.0-331 Layered Product HP AXPVMS DP A6.20-370: HP AXPVMS DATA PROTECTOR V6.20 Insert the following lines in SYS$MANAGER:SYSTARTUP_VMS.COM: @SYS$STARTUP:OMNI$STARTUP.COM Insert the following lines in SYS$MANAGER:SYSHUTDWN.COM: @SYS$STARTUP:OMNI$SHUTDOWN.COM

 The default location for the installation is

SYS$SYSDEVICE:[VMS$COMMON.OMNI]

An account is created during the installation, under which the OMNI service runs: - Account name: OMNIADMIN with UIC[1,500] - Login directory for this account: OMNI$ROOT:[LOG]

$ tcpip show service omni

Service OMNI Port Proto Process 5555 TCP OMNI$INET Address 0.0.0.0 State Enabled

14

 omni$root is defined as logical in the system table Product directory tree contents
$ dir omni$root:[000000] Directory OMNI$ROOT:[000000] BIN.DIR;1 CONFIG.DIR;1 SCSITAB.;1 TMP.DIR;1 LOG.DIR;1 NLS.DIR;1 OMNIRC.TMPL;1

"OMNI$ROOT" = "VMS$DKA0:[VMS$COMMON.OMNI.]" (LNM$SYSTEM_TABLE)

SYS$STARTUP:OMNI$STARTUP.COM - Starts the Data Protector service. SYS$STARTUP:OMNI$SHUTDOWN.COM - Shuts down the Data Protector service. OMNI$ROOT:[BIN]OMNI$STARTUP_INET.COM - Starts up a new TCP/IP INET process, which then executes the commands sent by the Cell Manager. OMNI$ROOT:[BIN]OMNI$CLI_SETUP.COM - Defines symbols for commands. SYS$COMMON:[SYSHLP]DPA0620.RELEASE_NOTES;1 - Release notes location.

 Post installation
$ edit SYSTARTUP_VMS.COM add @SYS$STARTUP:OMNI$STARTUP.COM $ edit SYSHUTDWN.COM add @SYS$STARTUP:OMNI$SHUTDOWN.COM FQDN and host name resolution between cell manager and clients

Omniadmin a/c change password from datapro123 SmWaitForDevice, MaxBSessions on cell manager GLOBAL file 64k block size default. Increase for other O/S

Post Installation
Importing client on DP Cell Manager
SYS$SYSDEVICE:[VMS$COMMON.OMNI.CONFIG.CLIENT]CELL_SERVER.;

Copy OMNIRC.TMPL;1 to OMNIRC.; otherwise not usable!

Media Agent
SAN discovery of Tape Library and devices
$ mcr sysman io find_wwid

%SYSMAN-I-OUTPUT, command execution on node AVALON On port _MYVMS$PGA0:, the following tape WWIDs and their proposed device names have been found but not yet configured: [Device $1$GGA0] WWID=0B000007:0080-1121-119E-123A
[Device $1$MGA0] WWID=01000008:5006-0B01-1111-B77B

 SYSMAN> IO LIST_WWID %SYSMAN-I-OUTPUT, command execution on node MYVMS On port _PGA0:, the following tape WWIDs are not yet configured:

Target 7, LUN 0, HP Ultrium 3-SCSI WWID=02000008:5001-1010-007A-1211

Target 7, LUN 1, HP MSL G3 Series WWID=02000008:5001-1010-007A-1212 Target 8, LUN 0, HP Ultrium 3-SCSI WWID=02000008:5001-1010-007A-1213 Target 9, LUN 0, HP Ultrium 3-SCSI WWID=02000008:5001-1010-007A-1214

Devbra support
DEVBRA on node MYVMS:
Exch HP:EML E-Series Path: "_$2$GGA0:" SN: "GR123414VX" Description: Control device Revision: 1070 Flags: 0x0002 Slots: 98 Drives: 2 Drive(s) SN: "HP Ultrium 3-SCSI HU12342SSA" "HP Ultrium 3-SCSI HU12342SSB" Tape HP:Ultrium 3-SCSI Path: "_$3$MGA0:" SN: "HU12342SSA" Description: HP LTO drive Revision: L58W Device type: lto [13] Flags: 0x0001 Tape HP:Ultrium 3-SCSI Path: "_$3$MGA1:" SN: "HU12342SSB" Description: HP LTO drive Revision: L58W Device type: lto [13] Flags: 0x0001

 Media Agent configuration Best practice is let Cell Manager control the library and present tape drives to each SAN based client Use the Data Protector GUI to manually configure or auto-configure these devices. When configuring in Manager GUI ensure entry for individual nodes and cluster.

If you restore to a location other that the original location, only the disk device and starting directory are changed. The original directory path is added to the destination path to form the new restore location.

If the Restore Time Attributes (-notouch) option is disabled during a restore, the last accessed date will be updated with the current date and time on ODS-5 disks. On ODS-2 disks, the original dates will be set on the files. Restoring to a different OS you may lose attributes, including ACLs.

ODS-5 disk backups that have extended filesystem names (upper and lower case letters, Unicode characters, etc) may not be restored to an ODS-2 structured disk. During restore files are always locked whether the Lock Files during Restore (-lock) option is set or not

The default device and directory for pre- and post-exec command procedures is omni$root:[bin]. For alternative location you must specify Unix/dos style notation: /SYS$MANAGER/SHUT_APP.COM
If the Restore Protection Attributes (-no_protection) option is disabled, the files are created with the default owner, protection, and ACL. When specifying wildcard characters for Skip (-skip) or Only (-only) filters use '*' for multiple characters and '?' for single characters. Disk quotas are not supported. OMNIADMIN may be used or disable diskquota

OpenVMS Restore
The directory structure and the files are restored, together with the following filesystem information:
File and directory attributes ACL (Access Control List) Secondary file entries During an OpenVMS filesystem backup, files with multiple directory entries are backed up once using the primary path name. Secondary path entries are saved as soft links. For example, system specific roots on an OpenVMS system disk will have the SYSCOMMON.DIR;1 path stored as a soft link. The data for this path will be saved under [VMS$COMMON...]. During a filesystem restore, these extra path entries are restored.

 Full system disaster restore

OpenVMS system with Disk Agent required OpenVMS WRITEBOOT utility can be used to make the system disk bootable

Backup/ignore=interlock and nobackup setting supported

ZDB functionality
Zero Downtime Backup eg. EVA leverages business copy to snap and backup volume Not supported on OpenVMS however
DIY
Pre exec - Com file to stop application or quiesce Use SSSU to snap volume and present Com file to change volume label and mount Data Protector backup snapped volume via backup server. Post exec - Com file to start up app , delete snap etc

Patching

Need Software Support contract for entitlement to patches

Patch is a self extracting DPWIN_XXXX.exe for Windows. Asks which directory? After extraction .PCSI and .text files residing in specified directory. Next action is transferring .PCSI packet to OpenVMS client. Package file name should be in PCSI predefined format, for example: HP-AXPVMS-DP-A0510-2-1.PCSI for DP build A.05.10(2) Package file attributes should be the following: Record format: Fixed length 8192 byte records Record attributes: None $ set file/attribute=(rfm:fix,lrl:8192,rat:none) *.PCSI Patching always in Data Protector is full file replacement!.

Common Problems
Cell Manager cannot backup OpenVMS client.
FQDN and shortname resolution from server to client and viceversa - Ping Telnet thevmshostname 5555 Telnet cellmanagerhostname 5555 Tcpip show service omni

Problems contd
If using a file library in 6.20 there is a format problem where it cannot be used.
Solution is upgrade TCP/IP 5.6 to ECO 5

Problems contd
"Cannot append to medium (Invalid device block size 63KB, should be 256KB or
"Cannot append to medium (Invalid device block size 256KB, should be 63KB

The first happens when trying to append a VMS backup to a tape with windows data on it. The second case when happens when appending a windows backup to a tape with VMS data.

Problems contd
A Data Protector Client cannot be a member of two different cells.
Import will fail with: [12:1625] Import Host Failed OMNI$ROOT:[CONFIG.CLIENT]CELL_SERVER.;1 . Type this file to confirm that it contains a reference to the old cell manager: $ TYPE OMNI$ROOT:[CONFIG.CLIENT]CELL_SERVER.;1 olddpserver.hp.com Delete this file. Login to the new cell manager and perform the client import by opening up a command prompt and issuing the command: omnicc -import_host myvmsserver

Problems contd
Restoring from a Data Protector backup from Alpha to an Integrity Server CANNOT SET MODE error message
Advisory available but not realistic in some scenarios. Case still open

 Troubleshooting
HP Library and Tape Tools to test devices
Also this tool is multi platform (HP L&TT)

Are other clients having a problem? Media Robot Utility [ABSxxx] OpenVMS Backup to test SAN or LAN?

 Performance
SAN preferred than LAN. Examine session log to determine LANCP check speed of NIC, duplex if LAN based SAN polling (Windows RSM, Mgt agents, HPLTO driver) Split disks over multiple jobs SYSUAF Omniadmin Increase concurrency from default of 4 Defrag volumes Raw disk backups Avoid Enhanced Incremental feature on OpenVMS
Used for detecting renamed files/moved files , ACL change

Performance
Use OpenVMS Null device for testing VMS Null device is NLA0 Consider Raw Disk Backup (supported in 6.11)

 Miscellaneous
Call jobs from OpenVMS: Omnib datalist my ad-hoc backup mode full no_monitor omnib gives [31:20] You have no permission to start a backup Add OpenVMS user to the userlist in Data Protector Manager GUI Users Context.

Thank you!

Questions and Answers

Email:

Eamonn.Fitzmaurice@hp.com