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

Cristie Software Ltd. 

New Mill 

Chestnut Lane 

Stroud GL5 3EH 

United Kingdom 

Tel:+44(0)1453 847000 

Fax:+44(0)1453 847001 

cbmr@cristie.com 

CBMR for HP-UX PA-RISC 

Quick Start Guide 

Version 1.4 

Cristie Data Products GmbH 

Nordring 53-5 

63843 Niedernberg 

Germany 

Tel: +49 (0) 60 28/97 95-0 

Fax: +49 (0) 60 28/97 95 7-99 

cbmr@cristie.de 

Cristie Nordic AB 

Gamla Värmdövägen 4 

SE-131 37 Nacka 

Sweden 

Tel:+46(0)8 718 43 30 

Fax:+46(0)8 718 53 40 

cbmr@cristie.se


Copyright © 2003-2008 Cristie Software Ltd. 

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, UBax, Cristie Storage Manager (CSM), SDB and CBMR (Cristie Bare Machine Recovery) are trademarks of 

Cristie Software Ltd. 

HP-UX and HP Ignite-UX are trademarks of the Hewlett-Packard Corporation. 

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

Contents 


Contents 

1 Introduction 4 

1.1 Why ................................................................................................................................... should I read this document? 

4 

1.2 Overview ................................................................................................................................... 4 

2 How to use CBMR 5 

2.1 Requirements 

................................................................................................................................... 5 

2.2 Licensing ................................................................................................................................... 5 

2.3 Setup ................................................................................................................................... 5 

2.3.1 Check TSM ......................................................................................................................................................... Client 

6 

2.3.2 Installation ......................................................................................................................................................... 6 

2.3.3 Creating a TSM ......................................................................................................................................................... Client Node 

8 

Creating a dedicated .................................................................................................................................................. node via the TSM Admin client 

8 

Additional Configuration .................................................................................................................................................. to Maintain Multiple Backup Versions 

9 

2.4 Configuring ................................................................................................................................... CBMR 

10 

2.4.1 Create default ......................................................................................................................................................... Backup Location 

10 

2.4.2 Store machine ......................................................................................................................................................... configuration data 

12 

2.4.3 Create DR ......................................................................................................................................................... bootable media 

16 

2.4.4 Do regular ......................................................................................................................................................... system backups 

16 

2.4.5 Testing the ......................................................................................................................................................... Disaster Recovery media 

19 

2.5 Performing ................................................................................................................................... a Disaster Recovery 

31 

2.5.1 Recovering ......................................................................................................................................................... the system 

32 

3 CBMR Examples 38 

3.1 CBMR ................................................................................................................................... Standalone System Example 

38 

3.1.1 Setting up ......................................................................................................................................................... the Disaster Recovery 

38 

3.2 CBMR ................................................................................................................................... Network Example 

39 

3.2.1 Setting up ......................................................................................................................................................... the Disaster Recovery for the Workstations 

39 

3.2.2 Setting up ......................................................................................................................................................... the Disaster Recovery for the Server 

39 

3.3 CBMR ................................................................................................................................... TSM Network Example 

39 

3.3.1 Setting up ......................................................................................................................................................... Disaster Recovery for a TSM system 

40 

3.3.2 Restoring ......................................................................................................................................................... from a Disaster for a TSM system 

40 

Index 41 

3

4 CBMR for HP-UX PA-RISC 

1 Introduction 

1.1 Why should I read this document? 

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

Recovery) version 1.2.00 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 following figures). 

· 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. 

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

recovery purposes. 

Copyright © 2003-2008 Cristie Software Ltd.

Introduction 

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 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.00 PA-RISC machine (32 or 64-bit). 

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

Note recovery requires at least 64MB RAM. 

2.2 Licensing 

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. 

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. 


5


2.3.1 Check 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.00 - client versions 5.1.x through to 5.4.x 

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 

The installation depot can be downloaded from the Cristie website at http://www.cbmr.info/ 

download/HP 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.2.00.depot \* (for HP-UX 11.00) 


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 

disrec System/DR Command line recovery program 

gdisrec User/Prep Curses version of mkdisrec 

getini System/DR Read configuration information 

during DR 

How to use CBMR 

ggetini System/DR Curses version of getini used during 

DR. 

mkdisrec User/Prep Write configuration prior to DR 

make_cbmr 

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 

7


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. 

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 



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). 

9


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. 

2.4.1 Create default Backup Location 

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 menu 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 

dsm.sys is normally found in "/opt/tivoli/tsm/client/api/bin" 

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

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


11


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

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, re-create 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. 

To store the machine configuration data follow these steps: 

Launch gdisrec (creating the CBMR configuration can also be performed on the command line using 

the mkdisrec program). 

Select the Save Configuration menu option 1. 

The above menu will then be displayed. Configuration data may be stored with the backup itself 

(usually the most convenient), or to a network share. Select Save config with backup. The 

configuration will be built and saved to a local directory called CBMRCFG/ in the root. 

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


13


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, from the main menu select Manage NFS Shares: 

Use the NFS options provided to create the remote mount. For example: 



If saving the configuration to a network share select the Save config on NFS share menu option. 

This could take a few minutes to complete, but a successful save is signified by the following: 

If you prefer to use the command line equivalent of this menu, use the mkdisrec command thus: 

This example creates the configuration on the system in the folder /CBMRCFG/: 

mkdisrec -s /CBMRCFG 

CBMRCFG is the default root folder if the folder name is omitted as in 

mkdisrec -s 


15


This example creates the configuration on a remote share in the folder /cristie_nfs/: 

mkdisrec -s /cristie_nfs 

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.: 

This example creates and saves the bootable CBMR image to a network share. Other options 

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

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. 


On the Executive menu select option 1 Backup: 



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

17


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: 



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 

NOTE:- 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 (network boot is another option if your CBMR boot image was placed 

on a network share). 

19


The figure below shows a typical boot sequence from CD: 

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. 



21


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

on CD/DVD or tape. 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 discussion 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 tape, 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: 


23


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 backup location. 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: 

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: 


25


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: 

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. 


27


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 2 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: 



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: 


29


3. You will then be offered a choice of NFS shares in case 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: 

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

system: 



4. At this point 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. 

Note:- 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 

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. 


31


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'). 




33


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 

setup the network, configuration location and the Backup Location. 

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. 



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 some time) the following message is displayed: 


35


4. Press to display: 



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: 


37


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. 

Note: 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 

3 CBMR Examples 

The following simple examples are provided: 

§ CBMR for an isolated standalone system 

§ CBMR for a simple network 

§ CBMR for an IBM Tivoli Storage Manager client 

3.1 CBMR Standalone System Example 

This simple system consists of a workstation connected to a local SCSI tape drive. 

3.1.1 Setting up the Disaster Recovery 

In this scenario you would need to: 

1 Configure gubax to create a tape drive device for the SCSI drive. 

2 Create and store DR configuration parameters. 


3 Create bootable DR media. 

4 Backup the workstation's system to the tape drive (via gubax/ubax). 

3.2 CBMR Network Example 


CBMR Examples 

This simple network has four workstations and a server connected to a SCSI tape drive. The workstations 

are backed up to the server, and the server is backed up to the tape. 

3.2.1 Setting up the Disaster Recovery for the Workstations 

For each workstation you would need to: 

1 Configure gubax to set up a file (virtual tape) device on the server to store workstation backups. 

2 Create and store DR configuration parameters for each workstation on the server (via a network 

share). 

3 Create a bootable DR media for each workstation. If the workstations are similar (i.e. same 

version of HP-UX etc.) it will be possible to create a single boot image media to cover all 

workstations. 

4 Backup the workstation's system to the virtual tape device (via gubax/ubax). 

5 Backup the server's data to tape under normal backup procedures. 

3.2.2 Setting up the Disaster Recovery for the Server 

The server can be treated in exactly the same way as the workstation in the standalone system 

(see CBMR Standalone System Example). 

3.3 CBMR TSM Network Example 

This simple network shows an IBM Tivoli Storage Management (TSM) system. The TSM server is 

resident on the highly reliable TSM server. All other machines have TSM clients and are running 

Cristie BMR. This procedure provides Disaster Recovery for the TSM client machines. It is assumed 

that the TSM server is totally reliable and it is a safe residence for TSM client backups. 

39


3.3.1 Setting up Disaster Recovery for a TSM system 

For each workstation or server you would need to: 

1. Set up a dedicated client node in TSM for ubax (see Creating a TSM Client Node). 

2. Create an TSM Storage Device in ubax corresponding to the node. 

3. Create and store DR configuration parameters on a server network share. 

4. Create a bootable DR media for the workstations only. If the workstations are similar (i.e. same 

version of HP-UX etc.) it will be possible to create a single boot image media to cover all 

workstations. 

5. Backup the workstation/server's system (via ubax) to the TSM server via the dedicated node. 

3.3.2 Restoring from a Disaster for a TSM system 

Boot the failed workstation from the Disaster Recovery media. 

1 Provide the location of the DR configuration media. 

2 Choose Automatic Recovery which will restore the system files from the TSM server. 

3 Reboot the restored system. This should start HP-UX. 

4 Restore additional data using the normal backup/restore procedures. (Normally from the TSM 

Server using a Backup/Admin Client). 


Index 

- B - 

backup recovery 5 

boot 19 

bootable media 5 

boots 19 

- C - 

Configuration 5, 12, 16, 19 

cron 16 

- D - 

depot 6 

dsm.sys 10 

- E - 

examples 38 

- G - 

gdisrec 12 

ggetini 19 

gubax 4, 10, 16 

- H - 

HP Ignite-UX 4 

- I - 

installation 6 

- K - 

keyboard 19 


- L - 

license 5, 8 

- M - 

make_cbmr 16 

mkdisrec 12 

- N - 

network share 19 

NFS 19 

- P - 

password 19 

password generation 8 

- R - 

reboot 19 

Recovering the system 32 

Recovery CD 19 

Recovery Console 19 

Requirements 5 

- S - 

showdevs 12 

swinstall 6 

swremove 6 

- T - 

Test access 32 

Test access to backup device 19 

TSM 19 

TSM Client 4, 6, 8 

- U - 

ubax 4, 10, 16, 32 

uninstall 6 

Index 41

42 

- V - 

version 9, 19 


Virtual Tape Device 4 

Virtual Tape Device (VTD) 4 

vt100 19 

VTD 19

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

Create successful ePaper yourself

Delete template?

Save as template?