CBMR 6.1 for HP-UX PA-RISC Systems - Cristie Data Products GmbH

www.cristie.com 

CBMR 6.1 for HP-UX 

PA-RISC Systems 

Software Version: 6.1 

Date Published: November 2009

Contents 

Page 2 

CBMR for HP-UX PA-RISC Version: 6.1 

Section No. Section Title Page 

1.0 Introduction 3 

1.1 Why should I read this document? 3 

1.2 Overview 3 

2.0 How to use CBMR 3 

2.1 Requirements 3 

2.2 Licensing 4 

2.3 Setup 4 

2.3.1 Check TSM Client 4 

2.3.2 Installation 5 

2.3.3 Creating a TSM Client Node 6 

2.3.3.1 Creating a dedicated node via the TSM client 6 

2.3.3.2 Additional configuration to maintain multiple backup versions 7 

2.4 Configuring CBMR 7 

2.4.1 Create default backup location 8 

2.4.2 Store machine configuration data 10 

2.4.3 Create DR bootable media 11 

2.4.4 Do regular system backups 11 

2.4.5 Testing the disaster recovery media 13 

2.5 Performing a Disaster Recovery 22 

2.5.1 Recovering the system 22 

Copyright © 2003-2009 Cristie Software Ltd. All rights reserved. 

The software contains proprietary information of Cristie Software Ltd.; it is provided under a license agreement containing restrictions on use and 

disclosure and is also protected by copyright law. Reverse engineering of the software is prohibited. 

Due to continued product development this information may change without notice. The information and intellectual property contained herein is 

confidential between Cristie Software Ltd. and the client and remains the exclusive property of Cristie Software Ltd. If you find any problems in the 

documentation, please report them to us in writing. Cristie Software Ltd. does not warrant that this document is error-free. 

No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, 

photocopying, recording or otherwise without the prior written permission of Cristie Software Ltd. 

IBM Tivoli Storage Manager (TSM) and TIVOLI are trademarks of the IBM Corporation. 

PC-BaX, Cristie Storage Manager (CSM), SDB, TBMR (Bare Machine Recovery for TSM) and CBMR (Cristie Bare Machine Recovery) are trade- 

marks of Cristie Software Ltd. 

Cristie Software Ltd 

New Mill, Chestnut Lane 

Stroud GL5 3EH UK 

+44 (0) 1453 847000 Internet E-Mail: cbmr@cristie.com 

Website: http://www.cristie.com

1.0 Introduction 

1.1 Why should I read this document? 

Page 3 


Please take a moment to review this Quick Start Guide before using CBMR (Cristie Bare Machine 

Recovery) version 6.1 in your HP-UX PA-RISC environment for the first time. It will save you time and 

will reduce installation problems. CBMR is not an off-the-shelf program that you can install on your system 

and run straight away! 

This is a Quick Start Guide so only typical examples of the use of CBMR are provided. Refer to the 

individual man pages for detailed help on the CBMR component programs. 

Before installation, you must check the availability of certain services and protocols which CBMR will 

require during the setup of servers and clients and during the restore of a downed machine. Some system 

administration experience is required to perform these one time tasks. 

1.2 Overview 

CBMR allows a crashed system to be recovered providing you have made sensible provision in advance. 

CBMR consists of the following components or modules: 

• A backup and restore module (ubax) which allows you to backup system files. ubax is provided 

with 2 forms of user interface: command line or ‘curses’ based (gubax). The User may choose whichever 

form is convenient. This guide shows examples using the curses based interface (refer to the 

screen-shots shown). 

• A disaster recovery (DR) module which stores machine configuration data and recovers a crashed 

system using a custom built minimal HP-UX PA-RISC operating system. 

• An IBM Tivoli Storage Manager (TSM) support module (if required) that allows you to back up TSM 

client systems to TSM servers. 

Please note that this version of CBMR does NOT require the use of an HP Ignite-UX server for disaster 

recovery purposes. 

You may backup to and restore from any suitable device available on your system. This might be for 

example: 

• A tape (on its own or in a library) 

• A Cristie Virtual Tape Device (VTD) file (on a network server) 

• A TSM Node/Filespace. 

2.0 How to use CBMR 

CBMR can protect a system all the time, if setup and configured correctly. The following sections explain 

the basic procedure. 

2.1 Requirements 

CBMR for HP-UX on PA-RISC can be installed on any HP-UX 11.23 or 11.31 PA-RISC machine (32 or 64bit). 

If TSM is to be used, your system should have an appropriate 64-bit TSM API client already installed. 

To create bootable D.R ISOs the third party product CDRecord is required to be installed. 

Note recovery requires at least 64MB RAM.

2.2 Licensing 

Page 4 


Production use of CBMR requires a license to be purchased from Cristie. The fully working product is 

however provided for free evaluation for a period up to 30 days. Use beyond that period requires that a 

CBMR for HP-UX license be purchased from Cristie or its partners. 

2.3 Setup 

You must follow the procedure in the order listed below. CBMR can be used with or without a TSM server. 

You may omit the steps involving TSM configuration if you use CBMR with a directly attached storage 

device or a VTD on a remote share. 

1. Check TSM Client Version. 

2. Install CBMR. 

3. Create an TSM Client node. 

4. Create a default TSM or VTD Backup Location. 

5. Configure CBMR. 

6. Store machine configuration data. 

7. Create DR bootable media. 

8. Perform regular system backups. 

9. If encryption is used, copy the key repository file somewhere safe. 

To perform a Bare Machine Recovery you must: 

1. Boot up the machine to be restored from the previously prepared DR bootable media. 

2. Specify the location of the machine configuration data. 

3. Perform a backup recovery from CBMR. 

2.3.1 Check the TSM Client 

If you are not using TSM, skip this step. 

It is important to check the version of the TSM Client installed on your machine. TSM Client compatibility 

is: 

HP-UX version 11.23 & 11.31 - client versions 5.1.x through to 6.1.0 

Only clients with a compatible TSM Server are supported by CBMR. To check use the HP-UX command: 

swlist TIVsm 

This will produce output like the example shown below.

2.3.2 Installation 

Page 5 


The installation depot can be downloaded from the Cristie website at http://www.cristie.com or can be 

found in the install directory on the CBMR for HP-UX PA-RISC CD-ROM. 

CBMR installation requires the standard HP-UX installation utility swinstall. This is required in order to 

install the CBMR depot. Use the following command to install CBMR: 

swinstall -s/tmp/cbmr-1.3.11_HP-UX_11.23.depot \* (for HP-UX 11.23) 

To uninstall CBMR, use: 

swremove CBMR 

The installation process will install the following programs/utilities: 

Program/Utility User/System Component Description 

dr System/DR Curses CBMR DR program 

cbmrcfg User/Prep Write configuration prior to DR 

make_cbmr User/Prep Create CBMR recovery media 

format_floppy User/Prep Create formatted floppy disk 

showdevs User/Prep/DR List currently installed CD/DVD/Tape/ 

Floppy devices 

ubax User/System Prep/DR Cristie backup/restore program 

gubax User/Prep Curses version of Ubax 

show_routes System/DR Show network routes in DR environment. 

(Note: format_floppy is present but not used). 

In addition, a detailed discussion of each component is provided by installed man pages. Finally, a 

readme.txt file containing late breaking news and User Guides (including this guide) can be found in the 

directory: /etc/cristie.

2.3.3 Creating a TSM Client Node 

If you are not using TSM, skip this step. 

Page 6 


CBMR will connect to an TSM server as a client node and the machine’s operating system files and other 

important files should be stored under a Filespace under the client Node. If you need to create a Client 

Node using the TSM Admin Client, refer to the TSM Administrator Guide for further information. 

Note that a valid license must be installed for the TSM component of CBMR. A 30-day trial license is 

provided. 

2.3.3.1 Creating a dedicated node via the TSM Admin client 

To use the TSM module, you must enable ubax to backup to the IBM Tivoli Storage Manager by creating a 

dedicated node via the TSM Admin client. 

The settings required for the node are: 

Archive Delete Allowed Yes 

Backup Delete Allowed Yes 

Client Compression Setting Client 

Force Password Reset No 

Node Type Client 

In addition, you must consider your password policy. If you specify a Password Expiration period, you will 

have to set the password in ubax every time the password expires. 

The automatic password generation for the client nodes is supported (contact Cristie for details on how to 

do this).

2.3.3.2 Additional configuration to maintain multiple backup versions 

Page 7 


If it is required to hold more than 1 version of the DR backup in the same filespace then the node must be 

setup correctly to support this. You must have a Management Class (MC), which contains a Backup Copy 

Group (BCG) and an Archive Copy Group (ACG).Your node needs to be registered to use the MC. 

The parameters of the BCG of interest are: 

Versions Data Exists = 2 

Versions Data Deleted = 1 

Retain Extra Versions = 30 

Retain Only Version = 60 

In this example, there can be 2 versions of an object, the Versions Data Deleted attribute specifies the 

maximum number of different backup versions (1 in this case) retained for files and directories that you 

erased from your file system. This parameter is ignored as long as the file or directory remains in your file 

system. 

The expiration date for the remaining versions is based on the retain extra versions and retain only 

version parameters. In the example, if there is more than one version and one is deleted, the deleted one 

will be kept for 30 days. The only remaining copy of the object will be retained for 60 days (that is AFTER 

you make it inactive). 

2.4 Configuring CBMR 

The heart of CBMR is the Cristie UBax Backup and Recovery software (ubax). You need to create a 

Backup Location using the ubax New Backup Location option. If you are familiar with the ubax 

command line use that. If you are new to ubax, launch the curses based version gubax. Refer to the 

ubax and gubax man pages for more information regarding device creation. 

There is also extensive online man page help for ubax and gubax. 

It is important that the basic steps in setting up the DR components are carried out in the correct order. 

That is: 

1. Create Backup Location(s) - use the ubax/gubax utility 

2. Create the DR configuration - use the cbmrcfg utility 

3. Create DR backups - use the ubax/gubax utility 

4. Create bootable media. 

If, for example, you create the DR configuration before the Backup Locations the DR process will 

fail. In this case the configuration will not contain the Backup Location details.

2.4.1 Create default Backup Location 

Page 8 


Use the gubax program option 4 to create the location of the default backup location. In this example 

we are using TSM to hold the disaster recovery backup. 

Then select option 6 of the Backup Locations menu to setup the TSM server details. 

This results in the following screen where you can enter the TSM server details. Note that the 

ServerName field corresponds to the name of the corresponding entry in the TSM dsm.sys file. Note 

also, dsm.sys is normally found in: /opt/tivoli/tsm/client/api/bin64

The contents of a sample TSM dsm.sys is shown below: 

Page 9 


Return to the Backup Locations menu and select option 2: ‘Create New Backup Location’. 

Complete the TSM node and filespace details as in the following example:

Page 10 


The ServerName field must much that defined in the TSM server setup (see above). Note the last Backup 

Location added will always become the CBMR default. The TSM Backup Location is now fully defined. 

2.4.2 Store machine configuration data 

CBMR relies heavily on the machine configuration data to be able to restore the network configuration, 

recreate the volume groups, logical volumes and file systems and to restore other operating system related 

data. The configuration data can be either stored in the backup itself or on a network share. You only 

need to do it once, but you must do it again every time you change your hardware configuration. 

Storing the system configuration information on a network share could be useful if a large number of servers 

are running CBMR. You can create a new share or use an existing share. If using an existing share, 

create a directory for CBMR so that CBMR stores its information in this directory. 

All CBMR utilities discussed in this section are provided with ‘man’ page help. 

Use the cbmrcfg utility to store the machine configuration data. For example to save the configuration 

with the backup enter this command: 

cbmrcfg 

This will by default place the configuration data into a folder named CBMRCFG/ in the root. 

This effectively stores the configuration data with the backup itself (usually the most convenient). It may 

optionally also be saved to a network share. 

This may take a few moments, but successful completion is signified by: 

The contents of the /CBMRCFG/ folder contains the following files: 

When a subsequent backup is made this folder will get backed up. During a DR sequence this folder and 

its contents will be extracted before the main backup is restored to configure disks/partitions etc. first. 

If saving the configuration to an NFS share, mount it first and then run the cbmrcfg tool. For example: 

mount -F nfs 10.2.1.21:/mnt/hdc1 /cristie_nfs 

cbmrcfg -s /cristie_nfs 

where /cristie_nfs is the mount point of the share. 

Other locations for the configuration are potentially CD, DVD or tape, but are rarely used in practice.

2.4.3 Create DR bootable media 

This is performed using the command line utility make_cbmr, e.g.: 

Page 11 


This example creates and saves the bootable CBMR image to a network share. The final DR ISO can be 

found on the share called cbmr..iso e.g. cbmr.buffy.iso in this example. 

Other options include CD, DVD and tape but are rarely used. This ISO should be burnt to a suitable CD 

perhaps on a PC if CD burning software is not available on the HP-UX server. 

2.4.4 Do regular system backups 

In order to perform a DR full backup (to TSM) straight away, enter this on the command line: 

ubax -b -d myTSM /etc/cristie/scripts/cbmr.scp 

This presupposes a CBMR TSM device myTSM has already been created and CBMR has been installed 

to the standard directories. The backup script used is the default provided for a DR backup. However this 

may be edited to include or exclude other directories as required. The default is used in this example. 

If it is preferred gubax can be used to perform the DR backup instead. Always use the provided CBMR 

script (cbmr.scp) to perform the DR backup. 

Select Executive(option 1) from the gubax main menu.

Then, on the Executive menu select option 1; Backup: 

Page 12 


You are then prompted for the backup script. Select the default cbmr.scp script for a DR backup. 

Finally, enter the media volume header details as required and press OK. The backup can be password 

protected if required.

The backup begins by creating the list of files to backup: 

At the end of the backup a summary display is shown: 

Page 13 


Ensure that the DR backup is created regularly. It is suggested that a cron job be setup that periodically 

performs the DR backup (via the ubax command line tool). The system configuration could also be 

updated in the same job. 

2.4.5 Testing the Disaster Recovery media 

Before finally storing your Disaster Recovery Boot Media and the DR Configuration it is important to check 

that the Disaster Recovery process works and that the Disaster Recovery configuration and Backup device 

are accessible from the booted image. The tests described here follow the standard DR sequence, but 

will not attempt to actually perform a full Disaster Recovery - only up to the point of testing access to the 

backup device. 

Insert the prepared Disaster Recovery CD, DVD or tape in the appropriate boot device and reboot your 

computer from this media.

The screen-shot below shows a typical boot sequence from CD: 

Page 14 


When the DR system boots, follow the on-screen instructions to first select the appropriate keyboard layout 

for your system (see example below). By default the terminal type configured is ‘hp’. If this is not suitable 

for your terminal type this may be changed to ‘vt100’ if required. Do this by editing the ‘TERM = hp’ line 

manually before proceeding with the keyboard selection and pressing .

At this point the main CBMR Recovery Console menu will be displayed. 

Page 15 


Before testing access to the backup ensure that the media containing the configuration is loaded if on 

CD. If the configuration is on a network share or contained within the backup itself this step can be ignored. 

CBMR requires access to the system configuration before it tests access to the backup. In this way it tests 

both the integrity of the backup and the configuration. 

This document describes 2 common scenarios - firstly the configuration held within a TSM backup itself 

and secondly the configuration held on a network share with the backup in TSM. Other examples include 

a configuration held within a VTD, or a configuration held on a CD, but these are not described here. 

Configuration data stored in a TSM backup 

In this example we show how to test access to a configuration held in a TSM backup. 

1. If the backup is held in TSM or on a remote VTD, or the configuration is held on a remote share, the 

network will need to be started. To do this select option 3 (Tools) on the Recovery Console main menu. 

On the Tools menu itself select option 1 (Configure the network). Then select option 1 (Start the 

network) on the Configure Network menu.

You will then be prompted for the network details as follows: 

If the network starts successfully the following message will be displayed: 

Page 16 


2. With the network now operational, select option 4 on the Tools menu, (Test access to backup device). 

You will then be provided with the following Access Configuration menu: 

3. From this menu selection option 1: From a CBMR backup. You will now need to setup a Backup 

Location to represent the TSM backup. Before this is done however the TSM server details must be 

setup.

The next menu displayed is the Backup Locations menu: 

Use option 6 (Set TSM Server) on the Backup Locations menu to do this: 

Page 17 


Now create a TSM Backup Location. Select Create New Backup Location, then TSM Backup 

Location. Specify the TSM node and filespace details as in the following example:

Page 18 


Note that the ServerName field (Server_a in the above example) should match the name given to the 

TSM server setup above. successful definition of the Backup Location is signified with this message: 

4. Press to display a prompt for the backup media volume password: 

Enter the correct password for the backup. 

5. At this stage CBMR is just retrieving the configuration files from the backup - in this example the 

configuration files are contained within the TSM backup itself. The program will then check that a 

connection can be made with the backup device and that a valid volume header can be accessed. 

If the TSM backup contains several versions, an additional prompt containing the date/time of each 

version is displayed. Select the correct version as required. 

Successful retrieval of the configuration files is signified by: 

6. Press to continue and you will be re-prompted for both the media password and the version 

Select the same version date/time selected for the configuration before.

7. Successful access to the backup is signified by the message: 

Page 19 


8. If this process is successful, you can select Exit and Reboot from the main menu and boot the machine 

back to the normal HP-UX operating system. 

Configuration data stored on a network share 

If the configuration data is held on a network share rather than external media or TSM, follow these steps. 

1. Select option 4 on the Tools menu - Test access to backup device. You will then be provided with the 

following Access Configuration menu: 

In this case select option 3 - From an NFS share. You will then be prompted with the server network 

details so that the network can be started: 

Successful start of the network is indicated by:

Page 20 


2. You will then be required to setup details of the NFS network share as shown in the following example: 

Successful setup of the NFS share is indicated by: 

3. You will then be offered a choice of NFS shares (in cases where more than 1 have been defined): 

Select the appropriate share. If more than 1 server configurations are found on the network share, select 

the appropriate host:

Page 21 


The selected server configuration files will then be copied from the network share to the local system: 

4. At this point CBMR will examine the configuration files to determine where the backup is held and 

proceed to access the backup. Now press and you will then be prompted for the backup 

media volume password (if any - leave blank if none). 

5. Our backup is held in TSM and several versions are available: 

Select the same version date/time selected for the configuration before. 

6. Successful access to the backup is signified by the message: 

7. If this process is successful, you can select Exit and Reboot from the main menu to boot the machine 

back to the normal HP-UX operating system. 

Store the DR System CD and the DR backup tape (if used) in a safe location. It is a good idea to keep 

more than one copy and store them in different locations. This does not apply to TSM backups.

2.5 Performing a Disaster Recovery 

Page 22 


In the event of a disaster, having taken a backup of the system, CBMR enables you to restore your 

system back to its original state. You will need both your CBMR Disaster Recovery boot media and your 

DR Configuration media (if not held within the backup itself). These were created earlier. 

Ensure that your backup device is connected, switched on and that the device (tape/CD/DVD/TSM) is 

switched on and accessible. Boot the machine (or replacement machine) using the prepared CBMR boot 

media to display the CBMR Recovery Console main menu. 

2.5.1 Recovering the system 

The CBMR Disaster Recovery system will be booted. 

At the end of the boot process select the appropriate keyboard layout for your system and then choose 

the location of your DR configuration media. You may modify the ‘TERM = hp’ setting as the CBMR 

Recovery Console boots to something more appropriate (e.g.’TERM = vt100’).

Page 23 


After initialising the NICs (this may take a few moments), the CBMR Recovery Console main menu will 

then be displayed. 

1. Test access to the backup device first from option 4 on the Tools menu. This procedure will also 

require you to setup the network, specify the configuration location and the backup location. 

Select option 1, access configuration From a CBMR backup. 

2. If you are confident that the configuration data and backup device are correct and accessible, select 

option 1 Automatic Recovery from the main menu. You will be prompted with a caution before 

proceeding with the recovery because the next process will write to the hard drive and overwrite all the 

current data.

Page 24 


3. Select “Yes” to proceed with the disaster recovery. The recovery actions are summarised below: 

• Any bootable hard disks identified in the configuration data will be made bootable. 

• Any physical volumes will be created. 

• Any volume groups will be created. 

• Any logical volumes will be created. 

• Any file systems will be created and mounted as necessary. 

• Any mount points will be recreated 

• Swap and dump will be configured. 

• Networks and routes will be configured. 

The example shows 2 TSM backup versions. Select the appropriate date/time of the backup required; 

ubax will then be used to restore the files. At the end of the file restore step (this could take sometime) the 

following message is displayed: 

4. Press to display:

Page 25 


5. Press to return to the Recovery Console main menu. At this point, you should be able to select 

option 6 Exit and Reboot. However, Cristie advises that you save the recovery log files before doing 

this in case there are any boot problems. These log files will be required by Cristie Support. Select 

option 5: Copy log files to do this. 

You will be required to set up the NFS share if not already setup. 

Enter the share details and the log files will be copied to the share:

Page 26 


6. Return to the main menu and selection Option 6 Exit and Reboot. The machine will boot and run from 

the hard disk. 

7. When the computer is operational, you will be in a state prior to the disaster, to the state when the DR 

backup was taken. 

If you have taken any other regular backups after taking the Disaster Recovery Backup, you may restore 

them using ubax or the respective backup software to get the most up to date information back on your 

computer.

Cristie Software Ltd, New Mill, Chestnut Lane, Stroud GL5 3EH, U.K 

Tel: +44 (0)1453 847 000 Fax: +44 (0)1453 847 001 email: sales@cristie.com

CBMR 6.1 for HP-UX PA-RISC Systems - Cristie Data Products GmbH

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?