Ibm tivoli storage manager bare machine recovery for windows with cristie bmr redp3704

ibm.com/redbooks Redpaper

Front cover

IBM Tivoli Storage Manager:Bare Machine Recovery for Windows with Cristie BMRdows with Cristie BMR

Barry KadleckDavid McFarlane

Pracha PechsuksanWah Han Tan

Use Cristie BMR with ITSM, to protect your Windows environment

Learn how to configure your system for recovery

Secure your server environment

http://www.redbooks.ibm.com/


International Technical Support Organization

IBM Tivoli Storage Manager: Bare Machine Recovery for Windows with Cristie BMR

October 2003

© Copyright International Business Machines Corporation 2003. All rights reserved.Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP ScheduleContract with IBM Corp.

First Edition (October 2003)

This edition applies to Version IBM Tivoli Storage Manager Version 5.2 and above.

Note: Before using this information and the product it supports, read the information in “Notices” on page 7.

Contents

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9The team that wrote this Redpaper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Become a published author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Comments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Chapter 1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1 Cristie Bare Machine Recovery overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.2 IBM Tivoli Storage Manager overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.3 CBMR with ITSM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.4 An overview on how Bare Machine Recovery is done . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Chapter 2. CBMR/ITSM installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52.1 System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62.2 CBMR/ITSM setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62.3 ITSM Client installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2.3.1 ITSM Client configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.4 CBMR installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.5 CBMR storage device configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232.6 CBMR Disaster Recovery system configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

2.6.1 Creating the CBMR DR floppy diskette configuration . . . . . . . . . . . . . . . . . . . . . . 272.6.2 Creating the CBMR network share configuration . . . . . . . . . . . . . . . . . . . . . . . . . 32

Chapter 3. CBMR/ITSM backup operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393.1 Performing Windows OS backup using CBMR DR module . . . . . . . . . . . . . . . . . . . . . 403.2 Performing system data backup using ITSM client . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Chapter 4. Restoration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474.1 Restoration using three CBMR DR floppy diskettes (boot, system, configuration) . . . . 484.2 Restoration using CBMR CD-ROM and DR configuration floppy diskette . . . . . . . . . . 514.3 Restoration using CBMR CD-ROM with network share configuration . . . . . . . . . . . . . 554.4 Restoration of system data using TSM backup/archive client. . . . . . . . . . . . . . . . . . . . 614.5 Post BMR processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Chapter 5. Automate the system backup using the ITSM scheduler . . . . . . . . . . . . . . 655.1 Configure ITSM client scheduler service in the ITSM client . . . . . . . . . . . . . . . . . . . . . 665.2 Configure ITSM client scheduler in the TSM Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 705.3 CBMR/TSM backup script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

5.3.1 Creating CBMR backup and restore scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Appendix A. List of files backed up by CBMR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77A.1 Windows NT4 (Workstation, Server, Enterprise with service pack 4-6a) . . . . . . . . . . . 78A.2 Windows 2000 (Professional, Server, Advanced Server standard installation or with

service pack 1-3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Appendix B. CBMR DR Boot and System diskettes creation . . . . . . . . . . . . . . . . . . . . 79B.1 Creating CBMR DR Boot and System diskettes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

© Copyright IBM Corp. 2003. All rights reserved. 5

Appendix C. CBMR log and error description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83C.1 Description of CBMR log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84C.2 CBMR error definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

6 IBM Tivoli Storage Manager: Bare Metal Restore for Windows with Cristie BMR

Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing, IBM Corporation, North Castle Drive Armonk, NY 10504-1785 U.S.A.

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrates programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to IBM's application programming interfaces.


TrademarksThe following terms are trademarks of the International Business Machines Corporation in the United States, other countries, or both:

pSeries®AIX®GDPS®HACMP/6000™

IBM®Redbooks™SP2®Tivoli®

Redbooks(logo) ™IBM ™

The following terms are trademarks of other companies:

ActionMedia, LANDesk, MMX, Pentium and ProShare are trademarks of Intel Corporation in the United States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

C-bus is a trademark of Corollary, Inc. in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

SET, SET Secure Electronic Transaction, and the SET Logo are trademarks owned by SET Secure Electronic Transaction LLC.

Other company, product, and service names may be trademarks or service marks of others.


Preface

This Redpaper will help you install, tailor and configure Cristie BMR with IBM® Tivoli® Storage Manager (ITSM) to protect your systems from catastrophic failures.

The team that wrote this RedpaperThis Redpaper was produced by a team of specialists from around the world working at the International Technical Support Organization, San Jose Center.

Barry Kadleck is responsible for tape and Tivoli Storage projects at the International Technical Support Organization, San Jose. He has a degree in Electronic Engineering and joined IBM U.K. in 1985. He has been working with storage software and hardware for the last 10 years. Before joining the ITSO in 2001, Barry worked at the Product Introduction Consultancy, Hursley, U.K. as a Program Manager, introducing new Tivoli Storage products into Europe.

David McFarlane is a Technical Solutions Architect in Australia. He has 19 years of experience in the I/T industry. His areas of expertise include storage management, VTS, and z/series solutions. He has participated in two other ITSO residencies: IBM TotalStorage Virtual Tape server: Planning, Implementing and Monitoring, SG24-2229-04, and produced course materials for “GDPS®, XRC, PPRC,VTS Peer to Peer.”

Pracha Pechsuksan is a I/T Specialist in Thailand. He has six years of experience in AIX® field and two years of experience in TSM field. He has worked at IBM for 12 years. His areas of expertise include AIX, TSM, SP2®, and HACMP/6000™.

Wah Han Tan is a IT Specialist with the pSeries® services team in Singapore. He has worked at IBM Singapore for seven years. His areas of expertise include AIX, TSM, SP2, and HACMP/6000.

Become a published authorJoin us for a two- to six-week residency program! Help write an IBM Redbook dealing with specific products or solutions, while getting hands-on experience with leading-edge technologies. You'll team with IBM technical professionals, Business Partners and/or customers.

Your efforts will help increase product acceptance and customer satisfaction. As a bonus, you'll develop a network of contacts in IBM development labs, and increase your productivity and marketability.

Find out more about the residency program, browse the residency index, and apply online at:

ibm.com/redbooks/residencies.html

Comments welcomeYour comments are important to us!


http://www.redbooks.ibm.com/residencies.html

http://www.redbooks.ibm.com/residencies.html

We want our papers to be as helpful as possible. Send us your comments about this Redpaper or other Redbooks™ in one of the following ways:

� Use the online Contact us review redbook form found at:

ibm.com/redbooks

� Send your comments in an Internet note to:

[email protected]

� Mail your comments to:

IBM Corporation, International Technical Support OrganizationDept. QXXE Building 80-E2650 Harry RoadSan Jose, California 95120-6099



http://www.ibm.com/redbooks/

http://www.ibm.com/redbooks/

http://www.redbooks.ibm.com/contacts.html

Chapter 1. Introduction

The objective of this redbook is to provide materials describing how to perform a Bare Machine Recovery using Cristie Bare Machine Recovery (CBMR) version 4.0.2 and IBM Tivoli Storage Manager (ITSM) version 5.2.

In this chapter, we discuss the following sections:

� Cristie Bare Machine Recovery Overview� IBM Tivoli Storage Manager Overview� CBMR with ITSM� An overview on how Bare Machine Recovery is done

We assume readers will have a basic knowledge of the Microsoft Windows operating system, Cristie Bare Machine Recovery, and IBM Tivoli Storage Manager. Readers can access the following Web sites for further information:

http://www.cristie.comhttp://www.microsoft.comhttp://www.tivoli.com


http://www.cristie.com

http://www.microsoft.com

http://www.tivoli.com

1.1 Cristie Bare Machine Recovery overviewCristie Bare Machine Recovery (CBMR) is a powerful and flexible backup and disaster recovery software suite. This, integrated with IBM Tivoli Storage Manager (ITSM), provides a Bare Machine Recovery (BMR) solution for all users of Windows 9X, ME, NT, 2000, and XP.

The components of CBMR are:

� PC-BaX - A backup and recovery module to backup system files

� DRM - Disaster Recovery Module that stores machine configuration data and recovers a crashed system using a minimal Linux operating system

� OFM - Open File Module that allows open files to be backed up

� Tivoli Storage Manager (TSM) support module - Allows back up of TSM client to TSM servers.

CBMR is a comprehensive Microsoft Windows operating system (OS) backup, restore, and reinstallation tool. It is a file by file backup of the operating system (not a system image backup). It back ups and automatically restores the operating system structures necessary to rebuild the operating system, as well as data files if required.

Figure 1-1 PC-BaX Backup and Recovery Software

1.2 IBM Tivoli Storage Manager overviewIBM Tivoli Storage Manager and its complementary products provide a comprehensive solution focused on the key data protection activities of backup, archive, recovery, space management, and disaster planning. Tivoli Storage Manager enables high availability of business applications by providing superior data protection and unique technology to significantly improve performance and resource utilization. Additionally, optional application modules for mail, databases, application servers, Enterprise Resource Planning (ERP), and


hardware provide higher levels of application and hardware integration with the data protection process.

The base functions provided by IBM Tivoli Storage Manager include:

� Backup and Restore: The backup process creates a copy of the file or application data that can be recovered if the original data is lost or destroyed. Unlike other backup applications, Tivoli Storage Manager implements a progressive backup methodology to move data quickly and reliably. Using progressive backup, the number of file versions maintained by Tivoli Storage Manager and the length of time they are retained can be specified by the storage administrator. Backups can be scheduled, performed manually from the Tivoli Storage Manager client interface, or performed remotely using a Web-based interface. The restore process transfers a backup data copy from the Tivoli Storage Manager server-managed storage onto a designated machine.

� Archive and Retrieval: The archive process creates a copy of a file or a set of files, and stores it as a unique object for a specified period of time. This function is useful for maintaining copies of vital records for historical purposes. Like the backup process, the archive process can be scheduled, performed manually from the Tivoli Storage Manager client interface, or performed remotely using a Web-based interface. The retrieval process transfers the archival data copy onto a designated machine.

� Instant Archive and Rapid Recovery: IBM Tivoli Storage Manager allows for the creation of a complete set of client files, called a backup set, on the Tivoli Storage Manager server system using the most recent backup versions stored by the server. In a process called Instant Archive, a backup set is used to retain a snapshot of a client file system for a designated period of time. The Rapid Recovery process allows you to copy backup sets onto portable media for LAN-free recovery of a client system.

1.3 CBMR with ITSMThe functionality of both products will enable customers to recover the core Windows operating system to a new disk drive using floppy diskette and a disaster recovery backup stored in the ITSM Server.

The backup of the operating system comprises the files contained in the Windows operating system folder together with the TSM client files and the CBMR files. These are backed up as a few files within the ITSM filespace, and kept up to date either on an ad hoc basis, or by using the scheduler incorporated within CBMR.

The configuration files contain key static information about the hard disk drive, boot sectors, and partitions, and this is stored either on a network share or on a floppy diskette (one for each computer).

The boot files are contained on the supplied bootable CD-ROM, or can be created on floppies by running a utility in CBMR.

A Bare Machine Recovery is performed by booting from the supplied CD-ROM or created floppy diskette, and running the CBMR recovery program. This program loads a shell operating system, the drivers required to access the network, and the ITSM Application Program Interface (API) client. The Windows operating system is then recovered to the most recent point in time backup and the system rebooted in Windows mode. The system data is then restored by ITSM backup/archive client.

Chapter 1. Introduction 3

Figure 1-2 CBMR and ITSM combined architecture

1.4 An overview on how Bare Machine Recovery is doneHere are the steps:

1. Boot the system either from CBMR installation CD-ROM or CBMR Disaster Recovery (DR) floppy diskette into Linux operating system.

2. Load the drivers required to access the network and the ITSM API client with either the CBMR DR floppy configuration diskette or network share configuration.

3. Perform an Automatic Recovery, which does the following:

– Partitions whole system (does not respect partitions)– Format – boot and system partition– Restore – CBMR, Windows and ITSM folders– Make system bootable – restores 1st sector of master boot record

4. Reboot into Windows mode, with which the DR wizard does the following:

– Formats the data partition to fat16 or fat32– Converts fat16 and fat32 to NTFS then reboots

5. Restore the system to most recent state using ITSM backup/archive client.


Chapter 2. CBMR/ITSM installation

In this chapter, we show the following sections:

� System requirements� CBMR/ITSM setup� ITSM client installation� ITSM client configuration� CBMR installation� CBMR storage device configuration� CBMR Disaster Recovery system

We assume readers have a ITSM server configured and running. We will not show the installation and configuration of the ITSM server. The Bare Machine Recovery of the ITSM Server itself, and the recovery of the ITSM database are not discussed in this book.

2


2.1 System requirementsSupported Windows platforms

� Windows NT4 SP6 or higher � Windows 2000 Professional, Server, Advanced Server, and Cluster Server � Windows Terminal Server � Windows XP Home and Professional

ITSM requirements

� ITSM 4.2, ITSM 5.1, 5.2� Must have the ITSM client API runtime files installed

Hardware support

� Supports all Intel based processors and most motherboards

� There is a wide and ever increasing range of network adapters, Fibre Channel HBAs, and RAID controllers, which are supported and available on the Cristie Web site: http://www.cristie.co.uk/uk/uk_html/disrec/index.html

Firewall requirement

� If there is a firewall between the file server and the client node where CBMR is running, port 139 must be open.

CBMR limitations

There are some limitations that we need to take note of. Some or all of these limitations may be removed in future CBMR releases:

� CMBR does not support systems installed on Windows Dynamic Disk volumes.� CBMR and ITSM client both should be installed on the Windows partition.� Automatic ITSM node password reset by ITSM server is not supported.� ITSM API Client version 4.2.1.32 or above is required.

2.2 CBMR/ITSM setupIn our CBMR/ITSM setup, we configure the ITSM Server to use the disk storage pool to store the CBMR/ITSM client system OS backup. We will back up the client system OS and data to the ITSM Server using both the ITSM API and ITSM backup/archive client. In the CBMR network share configuration example, the ITSM Server will export a network share directory, DR_DIR to the client systems. All CBMR/ITSM client systems will back up the system information to the network share directory.

The client systems in this example were installed with the following software versions:

ITSM Server

� Windows 2000 SP3� ITSM Server version 5.2

Workstation

� Windows 2000 SP3� ITSM Client version 5.2� CBMR version 4.0.2


http://www.cristie.co.uk/uk/uk_html/disrec/index.html

Figure 2-1 CBMR /TSM setup example

2.3 ITSM Client installationHere are the steps:

1. Install the ITSM client by using the ITSM client Installation CD-ROM. If AutoPlay is enabled in your system, the CBMR menu will display. If it does not display, double click TSMCLI.exe in the CD-ROM to launch it manually.

2. Select the location for the installation directory, and click Next to continue.

Chapter 2. CBMR/ITSM installation 7

Figure 2-2 Select the location to save files

3. Select the Setup language for the installation and click OK.

Figure 2-3 Select the Setup language

4. Click Next to continue.

Figure 2-4 Click Next to continue

5. Select the destination folder and click Next to continue.


Figure 2-5 Select the Destination Folder

6. In this Setup Type screen, select Custom to install some of the ITSM Client additional program features:

– Administrative Client Command Line Files to connect to the ITSM Server to perform administrative ITSM commands

– Open File Support - allow Open File backup

7. Click Next to continue:

Figure 2-6 Select Custom to install ITSM Client additional program features

Note: In the typical setup, both ITSM backup/archive and API programs install automatically. To install only the ITSM API, choose Custom setup from the Setup Type selection screen, and deselect the Backup-Archive Client files.


Figure 2-7 Select additional ITSM Client features

8. Click Install to start the ITSM Client installation.

Figure 2-8 Click Install to begin the ITSM Client installation

9. Once the ITSM Client installation is complete, we have to configure the environment variables in the Windows to make it more convenient to use the command line.

10.We need to set the following environment variables in the Windows:

– PATH: This is the default search path the operating system uses to locate executable files. Set this to include the fully qualified paths of the client installation directories, for example, SET PATH=%PATH%;C:\Program Files \Tivoli \TSM \baclient.

– DSM_CONFIG: Set this environment variable to the fully qualified path and filename of the client options file, for example, DSM_CONFIG=C:\Program Files \Tivoli \TSM \baclient \dsm.opt.

– DSM_DIR: Set this environment variable to the directory where the client message file dsc*.txt is located, for example, DSM_DIR=C:\Program Files \Tivoli \TSM \baclient.

– DSM_LOG: Set this environment variable to the fully qualified path where you want the error log files to reside, for example, DSM_LOG=C:\Program Files \Tivoli \TSM \baclient\log.


11.Reboot the system. We have completed the ITSM Client installation, we will proceed to the next section to configure the ITSM Client.

2.3.1 ITSM Client configurationCBMR backup the Windows operating system (OS) to the ITSM Server through the ITSM API client. If we are going to use the ITSM backup/archive client to backup the system data, we need to register two different ITSM clients within the same system, namely the ITSM API client for the CBMR OS backup, and the ITSM backup/archive client for the system data backup. CBMR will not work with ITSM using the same ITSM client.

1. Register two new nodes from the ITSM Server Web administration console. The first node will be the ITSM API client. Ensure the following settings are set for this ITSM API client:

– Archive Delete Allowed YES– Backup Delete Allowed YES– Client Compression setting CLIENT– Force password reset NO– Node Type CLIENT

Note: At the current CBMR version release, CBMR does not support multiple versions of backups. In the ITSM policy setting, it is recommended to create one backup version and a nil deleted version (verexists=1 verdeleted=0) for the ITSM API clients. To maintain multiple versions of the CBMR backup, create different CBMR devices targeted with different filespaces.


Figure 2-9 Register a new node

3. Next, register the ITSM backup/archive client from the ITSM Server Web administration console. Now, we have both the ITSM backup/archive client and ITSM API client registered in the ITSM Server.

Note: In regards to passwords, consider the following:

1. Automatic password generation for the ITSM API client to be use with CBMR is not supported.

2. If a password expiration period for a CBMR/TSM API client node is used, the password has to be set in PC_BaX every time it expires.


Figure 2-10 TSM nodes information

4. We have to configure the ITSM backup/archive client. Click Backup-Archive GUI from the Window Programs. A ITSM Client Configuration Wizard will appear on the screen for first time activation. Select the necessary client components and click Next to continue.

Figure 2-11 TSM Client Configuration Wizard

5. Select Create a new option file and click Next to continue.


Figure 2-12 Create a new option file

6. Enter the ITSM backup/archive Client name and click Next to continue.

Figure 2-13 Enter the ITSM Backup/Archive client name

7. Select TCP/IP as the communication method and click Next to continue.


Figure 2-14 Select TCP/IP as the communication method

8. Enter the ITSM Server IP address and click Next to continue.

Figure 2-15 Enter ITSM Server IP address



Figure 2-16 Domain and include/exclude lists

10.Click Finish to begin the ITSM backup/archive client configuration.

Figure 2-17 Click Finish to complete the ITSM client configuration

11.Enter the ITSM backup/archive client password.

Figure 2-18 Enter ITSM backup/archive password

12.If we successfully log in, we will be able to access the ITSM backup/archive client GUI menu. Now, the ITSM backup/archive client configuration is complete.


Figure 2-19 ITSM backup/archive client GUI menu

2.4 CBMR installationHere are the steps:

1. Install CBMR by using the CBMR installation CD-ROM. If AutoPlay in your system is enabled, the CBMR menu will display. If it does not display, double click SetupBmr.exe in the CD-ROM to launch it manually. In our testing we were limited to the CBMR trial version.

Note: Automatic password generation for the ITSM backup/archive client is allowed.


Figure 2-20 CBMR Installation Menu

2. Click INSTALL CBMR, select English and click Next to continue.

.

Figure 2-21 Select English



Figure 2-22 Click Next to continue

4. Select I accept the term of the license agreement and click Next to continue.

Figure 2-23 License Agreement

5. Enter the customer information and click Next to continue.


Figure 2-24 Enter the customer Information

6. Select Complete and click Next to continue.

Figure 2-25 Select Complete

7. Leave both entries blank to run in Local System account and click Next to continue.

Note: Tivoli Storage Manager (TSM) Support Module will select automatically if the ITSM API client is already installed. If the ITSM API client is not install, install the ITSM API client, and select TSM Support Module under the Custom option. Both ITSM backup/archive and API client are installed together by ITSM default mode.


Figure 2-26 Leave both entries blank for Local System account

8. Click Yes to start CBMR Scheduler services automatically and click Next to continue.

Figure 2-27 Click Yes to start CBMR Scheduler services automatically

9. Accept the default Program Folder name and click Next to continue.


Figure 2-28 Accept the default Program Folder name

10.Click Install to complete the CBMR installation.

Figure 2-29 Click Install to complete CBMR installation

11.Click Finish to reboot the system to complete the CBMR installation.


Figure 2-30 Reboot the system after the CBMR installation is complete

2.5 CBMR storage device configurationHere are the steps:

1. When CBMR PC-BaX program is opened for the first time, PC-BaX will ask to scan for new devices. Click No to scan for new devices.

Figure 2-31 Click No to configure ITSM device

2. To configure a ITSM device, click Storage Device.

Figure 2-32 Click Storage Device to configure a ITSM device


3. Click NEW to create an ITSM device.

Figure 2-33 Click NEW to create an ITSM device

4. Select ITSM Device and click Next to continue.

Figure 2-34 PC-BaX New Storage Device Wizard

5. Enter the client information for the PC-BaX to access to the ITSM Server. Click Create to create the ITSM device. See Table 2-1 for the description of the fields.

Note: Use different filespaces under the same node to maintain different active backup sets. It is also possible to use one node for all the system’s backups and each of the system’s data can be stored under a different filespace. However, if the node is deleted, all system’s backup data will be lost.


Figure 2-35 Enter the required informations

Table 2-1 Description for the Field entry

6. Click OK to return to the Storage Device wizard screen.

Figure 2-36 Click OK

7. Click Finish to end the creation of the Storage Device.

Field Description

Name The friendly name of the device. Any valid character sequence up to 79 characters is acceptable.The name should be unique and you cannot specify the name of an existing device.

Communication method The method of communication to use. The possible selections are:TCPIP - to use TCP/IPIPXSPX - to use IPX/SPXNETBIOS - to use NetBIOSNAMEDPIPE - to use Named Pipes

Server address The host name of the ITSM server or the IP address in dotted decimal form.If DNS address are use, please make sure the DNS is working and have enter the correct DNS settings under the network protocol

Port The TCP port at which the ITSM server is listening for client requests.

Nodename Enter the node name which must have been created earlier

Node Password Enter the node password, if any. Leave it blank for no password

Filespace Name Enter the name of the filespace which should start with /. If this doesn't exist before, it will be registered.


Figure 2-37 Click Finish to end the creation of the Storage Device

8. Now, the new ITSM device information will be stored in an “ini” file named Devices\Devices.ini in the CBMR Program folder

Figure 2-38 Device.ini file


2.6 CBMR Disaster Recovery system configurationCBMR stores the unique system configuration in a file named DISREC.INI. This is an important file which contains system configuration information such as the number of hard disks, partitions, Windows system directory, CBMR and ITSM installation directory, etc. There is another important file named modules.lst which holds SCSI, RAID and network adapter information. If the system has more than 2 RAID, 2 SCSI or 2 network devices, the information must be manually updated in this file.

The disaster recovery configuration can be stored either on a Disaster Recovery Configuration floppy diskette or on a network share. Network share option will be very useful, if there is a large number of systems running CBMR in your environment.

The disaster recovery configuration needs to be updated after a hardware and/or software change:

� Add or remove disks to the system

� Change partition sizes or create new or delete one

� Format a partition to a different file system

� Reinstall CBMR or ITSM or change the ITSM client/password/filespace information

� Change network/SCSI/RAID adapters

We will show how to create the floppy diskette configuration and network share configuration.

2.6.1 Creating the CBMR DR floppy diskette configurationHere are the steps:

1. Prepared a blank formatted 1.44 MB floppy diskette. Insert the CBMR Installation CD-ROM. If AutoPlay is enabled in your system, the CBMR menu will display. If it does not display, double click SetupBmr.exe in the CD-ROM to launch it manually. Select CREATE FLOPPIES.

Figure 2-39 Click CREATE FLOPPIES


2. In the drop down list, select DR Configuration Disk/Share, and click Create.

Figure 2-40 Select DR Configuration Disk/Share

3. Select Copy Configuration information to floppy, and click OK to continue.

Figure 2-41 Select Copy Configuration information to floppy

4. Insert a blank 1.44 MB floppy diskette into the Drive A and click OK.

Figure 2-42 Insert a blank floppy diskette into Drive A and click OK

5. Once this is completed, labelled the floppy diskette as DR Configuration. Click OK.


Now, the newly created floppy diskette contains the basic CBMR information. We will need to update this floppy diskette with system specific information.

6. Select Disaster Recovery from the PC-BaX main program


Figure 2-44 Click disaster recovery

7. Select Create/Update configuration disk, and choose the correct storage device to use, and click Next to continue.

Figure 2-45 Select the correct storage device

8. Select for the correct floppy drive and click Next to continue.

Figure 2-46 Select the correct Floppy Drive and click Next to continue


9. Select Tivoli Storage Manager (TSM) and click Next to continue.

Figure 2-47 Select Tivoli Storage Manager as the correct device type

10.Enter the TSM Server information:

– communication protocol (normally TCP)– Either the TSM Server hostname or TSM Server IP address– TCP port (normally 1500)

Click Next to continue.

Figure 2-48 Enter the ITSM Server information

11.Select the correct RAID/SCSI and Network adapters.The drivers are the Linux drivers that will be used by CBMR. If the required adapter driver is not on the list, click Download latest Drivers to connect to the Cristie Web site for latest drivers. Click Next to continue.


Figure 2-49 Select the correct adapter drivers

12.Specify the IP settings of the local server. Click Use DHCP if DHCP is used in the network environment. Click Next to continue.

Figure 2-50 Enter the IP informations

13.Click Finish to update the configuration information to the floppy diskette.


Figure 2-51 Click Finish to update he configuration information to the floppy diskette

The following files is create in the floppy diskette:

� Disrec.ini - contain the hard disk information along with the Windows, CBMR and ITSM installation folders.

� Modules.lst - contain the drivers that need to be loaded.

� Device.ini - contain the logical device information stored by CBMR.

The system’s configuration information is stored into the floppy diskette.We are ready to proceed to the next chapter to do the backup.

2.6.2 Creating the CBMR network share configurationHere are the steps:

1. Insert the CBMR Installation CD-ROM. If AutoPlay is enabled in your system, the CBMR menu will display. If it does not display, double click SetupBmr.exe in the CD-ROM to launch it manually. Select CREATE FLOPPIES.


Figure 2-52 Click CREATE FLOPPIES

2. In the drop down list, select DR Configuration Disk/Share, and click Create.

Figure 2-53 Select DR Configuration Disk/Share

3. Select Copy Configuration information to network, enter the path of the share directory. Click OK to copy the configuration information to the share directory.

Figure 2-54 Enter the path of the share directory

4. The configuration information is copied to the share directory. This contains the basic CBMR information. Click OK to exit. We will update this information with system specific information.


Figure 2-55 CBMR configuration information is successfully copied to the share directory

5. Select Disaster Recovery from the PC-BaX main program

Figure 2-56 Click Disaster Recovery

6. Select Create/Update configuration disk, and choose the correct storage device to use, and click Next to continue.


7. Select Network and specify the share directory information. Click Next to continue.


Figure 2-58 Specify the share directory information

8. Select Tivoli Storage Manager (TSM) and click Next to continue.

Figure 2-59 Select Tivoli Storage Manager as the correct device type

9. Enter the ITSM Server information:

– Communication protocol (normally TCP)– Either the ITSM Server hostname or ITSM Server IP address– TCP port (normally 1500)

Click Next to continue.

Note: If a floppy configuration diskette is created, select Update Floppy Disk to update the system information to the floppy configuration diskette. This will ensure system latest information is copy to the network share and floppy diskette.


Figure 2-60 Enter the ITSM Server information

10.Select the correct RAID/SCSI and Network adapters. The drivers are the Linux drivers that will be used by CBMR. If the required adapter driver is not on the list, click Download latest Drivers to connect to the Cristie Web site for latest drivers. Click Next to continue.

Figure 2-61 Select the correct adapter drivers

11.Specify the IP settings of the local server. Click Use DHCP if DHCP is used in the network environment. Click Next to continue.


Figure 2-62 Enter the IP informations

12.Click Finish to update the configuration information to the network share directory.

Figure 2-63 Click Finish to update he configuration information to the share directory

13.A directory folder is created with the backup system hostname. Inside the folder are the following files:

� Disrec.ini - contain the hard disk information along with the Windows, CBMR and ITSM installation folders.

� Modules.lst - contain the drivers that need to be loaded.

� Device.ini - contain the logical device information stored by CBMR.

We are ready to proceed to the next chapter to do the backup.


Figure 2-64 A folder is create with the backup system hostname


Chapter 3. CBMR/ITSM backup operations

This chapter will show the following sections:

� Performing an Windows OS backup using CBMR DR module� Performing system data backup using ITSM client

3


3.1 Performing Windows OS backup using CBMR DR module

Here are the steps:

1. Open the main PC-Bax main program, and select Disaster Recovery.

Figure 3-1 Select Disaster Recovery to perform a DR backup

2. Select Do a DR backup and the correct Storage device to use. Click Next to continue.


3. By selecting the default mode, CBMR DR will back up necessary files needed to restore the system Windows OS. CBMR DR will not restore all other information even if all drives are selected and backed up. We will back up the system data using ITSM backup/archive client. Please refer to Appendix A, “List of files backed up by CBMR” on page 77 for a list of files backed up by CBMR.


.

Figure 3-3 Select the default backup mode

4. Now, the CBMR DR will back up the Windows OS files to the ITSM Server through the ITSM API function.

Figure 3-4 Backup Status

5. A ITSM API client session will connect to the ITSM Server.

Figure 3-5 CBMR access the ITSM Server through the TSM API client

Chapter 3. CBMR/ITSM backup operations 41

6. CBMR DR will perform an automatic verify after the backup process is complete.

Figure 3-6 Automatic verify for backup

7. After the automatic verify of the backup is complete, click OK to exit.

Figure 3-7 Automatic verify is complete

8. If there are any backup errors, go to the PC-BaX main window and select Log Files. View the log files for any detailed messages.

Figure 3-8 View the log files for error messages


We have finished the Windows OS backup. Proceed to the next section for data backup.

3.2 Performing system data backup using ITSM clientHere are the steps:

1. Open the ITSM backup/archive GUI program. Select BACKUP or ARCHIVE to perform the data backup. In this demonstration, we use the ITSM backup/archive client backup function to back up the system data.

Figure 3-9 TSM backup/archive client GUI menu

2. We back up those files/directories that are not backed up by CBMR. Please refer to Appendix A, “List of files backed up by CBMR” on page 77 for list of files backed up by CBMR.

Figure 3-10 Click those folder to backup by TSM backup/archive client


3. Once you have selected the folders, click Backup to perform the backup operation.

Figure 3-11 Perform a backup operation

4. For detail backup report status, click Report.

Figure 3-12 Click Report for detail backup status

5. Once backup operation is complete, click OK to exit. If there is an error, click View for more details on the error messages.


Figure 3-13 Backup complete



Chapter 4. Restoration

In this chapter, we show the restoration of the system Window operating system using the following methods:

� Restoration using three CBMR DR floppy diskettes (boot, system, configuration)� Restoration using CBMR CD-ROM and CBMR DR configuration floppy diskette� Restoration using CBMR CD-ROM and network share configuration

After the restoration of the Windows core operating system, we use the ITSM backup/archive client to restore the system data to the most recent system state.

We show how to edit the CBM.INI to perform a complete restoration with the TSM script after the recovery of the Windows core operating system.

4


4.1 Restoration using three CBMR DR floppy diskettes (boot, system, configuration)

Before we begin the restoration using three CBMR DR floppy diskettes, we need to create the CBMR DR boot and system diskettes. Please see Appendix B.1, “Creating CBMR DR Boot and System diskettes” on page 80 for the creation of both the CBMR DR Boot and system diskettes.

The device drivers are not copied onto the CBMR floppy configuration diskette during the creation of the floppy configuration diskette. In order to perform a restoration of the Windows core (or “boot-up”) OS from the three CBMR DR floppy diskettes, we need to copy all the necessary drivers from the CBMR CD-ROM to the CBMR floppy configuration diskette.

In this example, we need to copy the Ethernet card driver from the CBMR CD-ROM folder, E:\dr\config\modules\e100.o (assuming E is the CD-ROM drive), to the floppy configuration diskette folder A:\modules.

Once the driver is copied onto the CBMR DR floppy configuration diskette, we can perform the recovery of the client system as follows:

1. Insert the CBMR DR boot floppy diskette. Wait until the prompt appears on the monitor screen to insert CBMR DR system disk.

2. Insert the CBMR DR system diskette and press Enter. Wait until the prompt appears on the monitor screen to insert CBMR DR configuration disk.

3. Insert CBMR DR configuration diskette and press Enter. This will load the configuration information from the configuration diskette, and it will load the PC-BaX Disaster Recovery Console.

Figure 4-1 PC-BaX Disaster Recovery Console

4. Select option 4. Hardware Drivers and press Enter.

5. Select option 5. List Loaded Modules and press Enter.


Figure 4-2 List loaded Modules

6. If the correct driver is loaded successfully, it will display loaded module. Press any key to continue. If the module is empty, select option 3. Load Network Modules to load the correct driver.

Figure 4-3 Display the module if loaded successfully

7. Select option 7. Exit from the Hardware Drivers and press Enter.

8. Select option 1. Test Backup Device and press Enter. Do not press any other key at this point to enter into the automatic configuration mode. CBMR will do a connection to the ITSM Server. If the connection is successfully, it will show Backup Device accessed successfully on the monitor screen. Press any key to continue.

Note: If the Test Backup Device result is not successfully, please do not perform any system recovery. The Test Backup Device result must be successful as it performs a test connection to the ITSM Server. Check for any errors on the TSM Server, ensure that the system clients’ information is correct, and ensure the network is working.

Chapter 4. Restoration 49

Figure 4-4 Automatic configuration mode

9. Select option 2. Automatic Recovery and press Enter.

10.Select option 1. Yes and press Enter to begin the automatic recovery of the client system. This will rebuild the partition table and reformat the hard disk before it begins the connection of the ITSM API client to the ITSM server in order to perform a restoration of the Windows core OS.

Figure 4-5 Enter Yes for automatic recovery

11.On the completion of the restoration of the client system OS, remove the CBMR media, and reboot the client system.


12.After you log on to the system, the PC-BaX/DR wizard will prompt you to convert the partition and format information from Linux to Windows. Click Next to continue.

Figure 4-6 Welcome screen

13.Accept default setting, and click Yes to continue.

Figure 4-7 Accept default setting

14.Click OK to reboot.The conversion of the partition and format information will take place.

15.The client system will boot up in the Windows OS. We then use the ITSM backup/archive client to restore the system data.

4.2 Restoration using CBMR CD-ROM and DR configuration floppy diskette

Here are the steps:

1. Insert the CBMR CD-ROM. Reboot the client system and wait until the prompt appears on the monitor console.


Figure 4-8 LiRest Restore Utility

2. Press f and insert the floppy configuration diskette into the floppy drive. Press Enter.

3. This will load the PC-BaX Disaster Recovery Console.


4. Select option 1. Test Backup Device and press Enter. Do not press any other key at this point to enter into the automatic configuration mode. CBMR will do a connection to the ITSM Server. If the connection is successful, it will show Backup Device accessed successfully on the monitor screen. Press any key to continue.



5. Select option 2. Automatic Recovery and press Enter.

6. Select option 1. Yes and press Enter to begin the automatic recovery of the client system. This will rebuild the partition table and reformat the hard disk before it begins the connection of the ITSM API client to the ITSM server, to perform a restoration of the Windows core OS.

Note: If the Test Backup Device result is not successfully, please do not perform any system recovery. The Test Backup Device result must be successful as it performs a test connection to the ITSM Server. Check for any errors on the TSM Server, ensure that the system clients’ information is correct and ensure the network is working.



7. On the completion of the restoration of the client system OS, the client system will reboot.

8. After you logon to the system, PC-BaX/DR wizard will prompt you to convert the partition and format information from Linux to Windows. Click Next to continue.


9. Accept default setting, and click Yes to continue.



10.Click OK to reboot.The conversion of the partition and format information will take place.

11.The client system will boot up in the Windows core OS. We will use the ITSM backup/archive client to restore the system data.

4.3 Restoration using CBMR CD-ROM with network share configuration

Here are the steps:

1. Insert the CBMR CD-ROM. Reboot the client system. Wait until the prompt appears on the monitor console as seen in Figure 4-14.

Figure 4-14 LiRest restore utility

2. Press Enter for CD-ROM.

3. This will load the PC-BaX Disaster Recovery Console.



4. Select option 4. Hardware Drivers and press Enter.

5. Select option 3. Load Network Modules and press Enter.

Figure 4-16 Load network modules

6. From the list of the network modules, select the correct network driver and press Enter.

Figure 4-17 Select the correct network driver

7. If the network driver loaded successfully, the following message will appear on the monitor screen, press any key to exit:

insmod /usr/modules/e100.oPress any key to continue


8. Select option 5. Remote Configuration and press Enter.

9. Select option 1. Setup and press Enter.

Figure 4-18 Remote Configuration

10.Enter the required information. See Table 4-1 for the description of the fields. Click OK when done.

Figure 4-19 Enter the information for Remote Configuration

Field Description

LocalIPAddress Local IP address to be used for the local network interface setup for connecting to the share containing the system configuration. The value can be DHCP if a DHCP server is to be used, or the IP address of the client system.

SubnetMask Subnet mask for the network interface. The value can be DHCP if a DHCP server is to be used or the subnet mask of the client system.

GatewayIP The gateway to be used to connect to the remote share. The value can be DHCP or IP address of the gateway. If no gateway is required, leave it blank.

ServerIPAddress IP address of the server, which holds the network share configuration information

Workgroup Workgroup or domain name for the server containing the network configuration


Table 4-1 Description of the fields

11.Select option 2. Select Configuration and press Enter.

Figure 4-20 Select Configuration

12.A list of configurations will be displayed. Select the correct configuration belonging to the client system and press Enter.

13.Select option 3. Exit to exit.

14.Select option 1. Test Backup Device and press Enter. Do not press any other key at this point to enter into the automatic configuration mode. CBMR will do a connection to the ITSM Server. If the backup device test is successful, the monitor screen will have the following messages in Figure 4-21.

ServerShare The server share name which holds the system configuration information. The share name should be of the form: \\<hostname>\<share_name>

Username A username which has read access to the share containing configuration information

Password Password used by the user

ConfigPath The path under the share where the configuration information is stored. The patch should begin with a \

Field Description



15.Press any key to continue.

16.Select option 2. Automatic Recovery and press Enter.

17.Select option 1. Yes and press Enter to begin the automatic recovery of the client system. This will rebuild the partition table and reformat the hard disk before it begins the


connection of the ITSM API client to the ITSM server to perform a restoration of the Windows core OS.


18.On the completion of the restoration of the client system OS, the client system will reboot.

19.When you log on to the system, the PC-BaX/DR wizard will prompt to convert the partition and format information from Linux to Windows. Click Next to continue.


20.Accept default setting, and click Yes to continue.

Note: If the Test Backup Device result is not successfully, please do not perform any system recovery. The Test Backup Device result must be successful as it performs a test connection to the ITSM Server. Check for any errors on the TSM Server, ensure that the system clients’ information is correct, and ensure the network is working.



21.Click OK to reboot.The conversion of the partition and format will take place.

22.The client system will boot up in Windows’ core OS. We will use the ITSM backup/archive client to restore the system data.

4.4 Restoration of system data using TSM backup/archive client

Here are the steps:

1. Open the ITSM backup/archive GUI program. Select Restore if the BACKUP command was used to copy the client system data. Select Retrieve if the Archive command was used to copy the client system data.

Figure 4-25 TSM backup/archive client GUI menu

2. Select the client system files and directories to be restored. Click Restore.


Figure 4-26 Select the client system files/directories to restore

3. Click Original location to restore the backup files and directories to original path.

Figure 4-27 Click Original location

4. The restoration will proceed.

Figure 4-28 Restoration in progress


5. Click Report for more details on the restoration process.

Figure 4-29 Detailed Restore Status Report

6. Once the restoration process is complete, click OK to exit.

Figure 4-30 Restoration process is complete

7. Exit the TSM backup/archive client, and reboot the client system.

8. Once the Windows OS is started, the system is restored to the point of the latest backup.


4.5 Post BMR processingIt is possible to start a script to perform a full restore process once the recovery of the Windows’ core operating system is complete. Edit the CBMR configuration file, CBM.INI, found under the CBMR program directory C:\Program Files\Cristie\Cristie BMR. Open the file with notepad.exe, search under the section [DR Options] for the following line:

;PostDRCommand = "C:\dbg\postdr.cmd"

Uncomment the line, and replace it with the location of the TSM restore script:

PostDRCommand = “C:\Program Files\Cristie\Cristie BMR\Scripts\tsmrestore.cmd”

Important: After changing the file, it must be backed up by CBMR DR, so that the script can run for a complete system recovery on the next CBMR DR operation.


Chapter 5. Automate the system backup using the ITSM scheduler

In this chapter, we will show you how to use the ITSM client scheduler to perform the system backup.

For the ITSM client schedules, there are four key pieces of information:

� The command that needs to be executed� When the command executes� How long the command takes to complete� How often the command needs to be repeated

The command to be run can be an incremental backup or a backup script, which should be run every day at a particular time. In order to synchronize all schedules and have load balancing on the ITSM server, an estimation of the duration of the schedules is required.

In the next few sections of this chapter, we show how to configure a backup job using the ITSM client scheduler. We will also show the content of the backup scripts run by the TSM scheduler:

� Configure ITSM client scheduler services in the ITSM client� Configure ITSM client scheduler in the ITSM Server� CBMR/ITSM backup script

5


5.1 Configure ITSM client scheduler service in the ITSM client1. Activate the ITSM GUI client by clicking the Windows Start button and selecting

Programs --> Tivoli Storage Manager --> Backup Archive GUI.

2. From the main GUI window, select Utilities --> Setup Wizard.

Figure 5-1 Select Setup Wizard

3. Click Help me configure the TSM Client Scheduler

Figure 5-2 TSM Client Configuration Wizard

4. Select Install a new or additional scheduler and click Next to continue.


Figure 5-3 TSM Scheduler Wizard

5. Enter the name for the TSM scheduler and click Next to continue.

Figure 5-4 TSM Scheduler name and location

6. Specify the client option file that TSM should use, and click Next to continue.

Figure 5-5 Specify the option file name and location

7. Enter the TSM client node name and password.

Chapter 5. Automate the system backup using the ITSM scheduler 67

Figure 5-6 TSM authentication

8. Select Automatically when Windows boots to have the scheduler service to start during the Windows reboot.

Figure 5-7 Service login options

9. Specify the locations for the scheduler log and TSM client error log.

Figure 5-8 Log file names and locations

10.Select Yes to start the scheduler services upon the completion of the wizard.


Figure 5-9 Immediate start option

11.Click Finish to complete the ITSM client configuration wizard.

Figure 5-10 Click Finish to complete the TSM client configuration wizard

12.Click OK to exit if the scheduler service is successfully installed.

Figure 5-11 Click OK to exit

1. To check that the scheduler service is installed in the system, click the Windows Start button and select Programs --> Settings --> Control Panel --> Administrative Tools.

2. Click the Services. Locate the newly defined TSM scheduler service. It should be started.


Figure 5-12 Windows services

5.2 Configure ITSM client scheduler in the TSM ServerIn this example, we will use TSM administrator command line to configure the ITSM client scheduler:

1. In the TSM Server, click the Windows Start button and select Programs --> Tivoli Storage Manager --> Admin Command Line.

2. Issue the following command to create a client schedule:

define scheduler standard System_backup description="Backup OS and data using script" action=command onjects="C:\Progra~1\Cristie\Cristi~1\Scripts\systembackup.cmd" priority=5 startdate=07/03/2003 starttime="11:00:00

3. Define the client association with the schedule with the command:

define association standard system_backup cbres1

4. To display the defined client scheduler, run the command:

query sched

Note: If the directory folder name consists of two words, then replace the seventh character (exclude blank space) and all following with the special ~ (tilde) character. As in the example above, for example: C:\Program files\Cristie\Cristie BMR\Scripts becomes C:\Progra~1\Cristie\Cristi~1\Scripts


Figure 5-13 To display client scheduler

5. To display the information about which client nodes are associated with one or more schedules, run the command:

query association

Figure 5-14 To display client nodes association

6. To check that the ITSM client scheduler is working, open a DOS command prompt at the client system and run the following command:

dsmc sched

Figure 5-15 dsmc sched command

To display the status of the scheduled events, run the TSM query event command.


Figure 5-16 Query event command

5.3 CBMR/TSM backup scriptThe backup script used in the ITSM scheduler is placed under C:\Program files\Cristie\Cristie BMR\Scripts. It is one of the directories being backed up by CBMR DR backup. The backup script name called by the ITSM scheduler is systembackup.cmd which performs the CBMR DR backup and backs up the system data using the ITSM backup command.

Figure 5-17 C:\Program files\Cristie\Cristie BMR\Scripts\tsmbackup.cmd

We also make use of the ITSM client option file, dsm.opt to exclude some directories from being backed up by CBMR DR.

Figure 5-18 TSM client option file dsm.opt

5.3.1 Creating CBMR backup and restore scriptsThe CBMR backup script DisRec.scp is generated by the CBMR DR module. This script backs up the core Windows files along with CBMR files and ITSM files. It can be generated using the following steps:

1. Open the main PC-Bax main program, and select Disaster Recovery.


Figure 5-19 Select Disaster Recovery to perform a DR backup

2. Select Do a DR backup and the correct Storage device to use. Click Next to continue.


3. Click Generate Backup and Restore scripts alone and click Next.

Figure 5-21 Click Generate Backup and Restore scripts alone

4. Both the scripts DisRec.scp and DisRest.scp are created under the directory C:\Program Files\Cristie\Cristie BMR. Click OK to exit.


Figure 5-22 Both DisRec.scp and DisRest.scp are created

Figure 5-23 Content of CBMR Backup script


Figure 5-24 Content of CBMR Restore script



Appendix A. List of files backed up by CBMR

In this appendix, we show a list of the files backed up by CBMR for the Windows NT and Windows 2000 environments.


A.1 Windows NT4 (Workstation, Server, Enterprise with service pack 4-6a)

C:\NTLDR

C:\NTDETECT.COM

C:\BOOT.INI

C:\NTBOOTDD.SYS (If present)

C:\BOOTSECT.DOS (If present)

C:\PROGRAM FILES\CRISTIE\Cristie BMR 04.01\*.* (CBMR Installation folder with subdirectories)

C:\PROGRAM FILES\TIVOLI\TSM\*.* (TSM Client installation folder with subdirectories)

C:\WINNT\*.* (Windows installation folder with subdirectories.)

A.2 Windows 2000 (Professional, Server, Advanced Server standard installation or with service pack 1-3)

C:\NTLDR

C:\NTDETECT.COM

C:\BOOT.INI

C:\NTBOOTDD.SYS (If present)

C:\BOOTSECT.DOS (If present)

C:\DOCUMENT AND SETTINGS\*.* (Include All Users and Default User and the subdirectories)

C:\DOKUMENTE UND EINSTELLUNGEN\*.* (Present in a German 2000 installation)

C:\PROGRAM FILES\CRISTIE\Cristie BMR 04.01\*.* (CBMR Installation folder with subdirectories)

C:\PROGRAM FILES\TIVOLI\TSM\*.* (TSM Client installation folder with subdirectories)


Appendix B. CBMR DR Boot and System diskettes creation

In this appendix, we show you how to create the CBMR DR Boot and System diskettes. These two floppy diskettes together with the CBMR DR Configuration diskette are used to boot up the system into CBMR DR recovery console.


B.1 Creating CBMR DR Boot and System diskettesHere are the steps:

1. Load in the CBMR installation CD-ROM. If AutoPlay is enabled in your system, the CBMR menu will display. If it does not display, double click SetupBmr.exe in the CD-ROM to launch it manually. Select CREATE FLOPPIES.

Figure 5-25 CBMR Installation Menu

2. To create CBMR DR Boot Diskette, select DR Boot Disk and click Create.

Figure 5-26 Select DR Boot Disk

3. Insert a blank floppy diskette into the floppy drive and click OK.


4. Once this is completed, label the floppy diskette DR Boot. Click OK to exit.


Figure 5-28 DR boot diskette is successfully created

5. To create CBMR DR System Disk, select DR System Disk and click Create.

Figure 5-29 Select DR system Disk

6. Insert a blank floppy diskette into the floppy drive and click OK.

.


7. Once this is completed, label the floppy diskette as DR System. Click OK to exit.

Figure 5-31 DR system diskette is successfully created

Appendix B. CBMR DR Boot and System diskettes creation 81


Appendix C. CBMR log and error description

In this appendix, we explain the description of some log files in CBMR. We also list the CBMR errors description.


C.1 Description of CBMR log filesTo check the error logs on CBMR, access from PC-BaX main menu’s the Log Files.

The error will be in the file with the format of XXX.Err. TSM errors also propagated to the error logs.

Backup logs in the CBMR are located in the following directory:

C:\Program Files\Cristie\Cristie BMR\Logfiles

The log files are in the format XXXXX.log:

� backup.log: Information related to backups� disrec.log: Information related to disaster recovery backup� Ofm.log: Information related to status of the open file module� restore.log: Information related to restore� verify.log: Information related to comparison of files on OS and TSM� compare.log: Information related to byte by byte comparisons of OS and TSM files

Restore logs can be written to the floppy diskettes /logs directory:

� disrec.log: Information related to Linux partitioning (before and after)� lirst.log: Information about Linux restore of files� lspci.log: lists the local PCI devices� messages.log: Information about Linux error messages� dsierror.log: TSM errors� scsi.log: Information about SCSI devices, network card, kernel IP routing table

C.2 CBMR error definitionsThe CBMR errors are grouped into several categories that identify the module that the error originated from. The following categories are currently defined:

Table 5-1 Category of CBMR errors

Category Description

BUS Backup Software - Non-module specific

BMS Backup Manager Services

MFS Media Format Services

FSS File System Services


1. Category --- BUS (Backup Software - Non-module specific)

BUS0001 -- General Error

BUS0002 -- Unable to open file

BUS0003 --- Unable to read file

BUS0004 --- Unable to write file

BUS0005 --- Memory allocation failure

BUS0006 --- Invalid service module

BUS0007 --- Service module not loaded

BUS0008 --- Unable to load Backup Manager

BUS0009 --- Unable to create Backup Folder

BUS0010 --- Unable to create program object in backup folder

BUS0011 --- Illegal request to remove NULL item from list

BUS0012 --- File specifications must start from the root

BUS0013 --- Invalid file specification in script

BUS0014 --- DLL has already been loaded

BUS0015 --- Cannot free a DLL that has not been loaded

BUS0016 --- Operation has been aborted by the user

BUS0017 --- Invalid Storage Device structure

BUS0018 --- Invalid Storage Device name

BUS0019 --- Invalid List Handle

BUS0020 --- List is Read-Only

BUS0021 --- List is empty

BUS0022 --- Invalid Syntax specified on command line

BUS0023 --- The maximum data size has been reached

BUS0024 --- No script mode has been specified

BUS0025 --- The Backup Manager has not been loaded

BUS0026 --- Duplicate storage device name

BUS0027 --- The requested operation is only allowed on a Robotics device

BUS0028 --- The requested operation is only allowed on a Cascaded device

BUS0029 --- Parameter error

BUS0030 --- The requested operation is only allowed on a Library device

BUS0031 --- There is at least one missing media in the library slots

BUS0032 --- There are no elements/slots configured for this library device

BUS0033 --- There are no drives configured for this robotics device

MLS Media Library Services

SSS Scheduler Services

SMS Storage Management Services

Category Description

Appendix C. CBMR log and error description 85

BUS0034 --- The end of media reached on the last element/slot in the library

BUS0035 --- The name contains one or more reserved characters

2. Category --- BMS (Backup Manager Services)

BMS0001 --- General failure

BMS0002 --- Unable to read script file

BMS0003 --- Script file contains an invalid entry

BMS0004 --- Script file - missing = character

BMS0005 --- No files were found to process

BMS0006 --- No (valid) storage device has been specified

BMS0007 --- Application error - invalid INI file operation requested

BMS0008 --- No name was specified for the script

BMS0009 --- Unable to create script file

BMS0010 --- Device is not an autochanger

BMS0011 --- Autochanger does not have a cartridge fitted

BMS0012 --- Invalid SDS category in device specification

BMS0013 --- Missing option in storage device specification

BMS0014 --- Incorrect Volume in storage device

BMS0015 --- Unable to write log file

BMS0016 --- Cleaning cycle failed

BMS0017 --- Cleaning cycle has been run

BMS0018 --- Invalid File specification in script

BMS0019 --- Missing date delimiter

BMS0020 --- Invalid date in script

BMS0021 --- Invalid month in date

BMS0022 --- Invalid Day in script

BMS0023 --- Device is not available

BMS0024 --- Invalid Volume Handle

BMS0025 --- Memory Allocation failure

BMS0026 --- Unable to open log file

BMS0027 --- Unable to access drive

BMS0028 --- Invalid Media Library Operation

BMS0029 --- The Media Library Services module is not available

BMS0030 --- The Backup Manager is already open

BMS0031 --- The Backup Manager has not been opened

BMS0032 --- Invalid Object Type

BMS0033 --- Invalid List Handle

BMS0034 --- Request to free list not allocated by the Backup Manager

BMS0035 --- Request to free list not allocated by the Backup Manager


BMS0036 --- Unable to delete specified object

BMS0037 --- The specified scheduler job is invalid

BMS0038 --- The specified scheduler job is not running

BMS0039 --- Unable to attach to specified scheduler job

BMS0040 --- The specified scheduler job has terminated

BMS0041 --- The specified scheduler job is already attached

BMS0042 --- The specified scheduler job has not been attached

BMS0043 --- The specified scheduler job has been detached

BMS0044 --- Script name is invalid

BMS0045 --- Unable to open user info file

BMS0046 --- User info file has incomplete entry

BMS0047 --- Unable to add network connection

BMS0048 --- Invalid object type

BMS0049 --- Logon failure

BMS0050 --- Invalid use of NULL as parameter

BMS0051 --- Incorrect Operating system for this version

BMS0052 --- Unknown property specified

BMS0053 --- This function is not available in this version

BMS0054 --- Operation aborted by user

BMS0055 --- The trial period for this product has expired

BMS0056 --- This product is not installed correctly or it has been tampered with. Please reinstall

3. Category --- MFS (Media Format Services)

MFS0001 --- General Error

MFS0002 --- Invalid structure on media

MFS0003 --- Dataset not found

MFS0004 --- Invalid media position requested

MFS0005 --- File mark reached

MFS0006 --- Memory allocation failure

MFS0007 --- Missing storage device option

MFS0008 --- Data compression failure

MFS0009 --- Invalid/missing Dataset password

MFS0010 --- Invalid/missing Media Header password

MFS0011 --- No more datasets exist

MFS0012 --- Invalid Media Header

MFS0013 --- Invalid Dataset Header

MFS0014 --- Operation aborted by user

MFS0015 --- Incorrect media name


MFS0016 --- Missing Filemark

MFS0017 --- Invalid Backup Manager Request

MFS0018 --- Unable to access application Queue

MFS0019 --- Unable to access I/O Queue

MFS0020 --- Unable to read application Queue

MFS0021 --- Unable to write Application Queue

MFS0022 --- Unable to write I/O Queue

MFS0023 --- Unable to read I/O Queue

MFS0024 --- I/O operation has stopped

MFS0025 --- Media Info Buffer is too small for Library Info

MFS0026 --- Dataset Info Buffer is too small for Library Info

MFS0027 --- This volume does not contain a valid media header

MFS0028 --- Media is write protected

MFS0029 --- The block size is too large - maximum is 64k

MFS0030 --- There is no storage device selected

MFS0031 --- Bad File Header

MFS0032 --- This media contains an older format backup.

MFS0033 --- This media contains a newer format backup.

4. Category --- FSS (File System Services)

FSS0001 --- Unable to open file

FSS0002 --- Unable to get file/directory Info

FSS0003 --- Unable to get Extended Attribute Info

FSS0004 --- Unable to get Access Control List Info

FSS0005 --- File Read Error

FSS0006 --- File Write Error

FSS0007 --- Unable to select directory

FSS0008 --- Unable to create directory

FSS0009 --- Compare failed

FSS0010 --- File skipped

FSS0011 --- File sizes are different

FSS0012 --- File not found

FSS0013 --- Operation aborted by user

FSS0014 --- Unknown support module

FSS0015 --- Path not found

FSS0016 --- Unable to set file/directory Info

FSS0017 --- Unable to set Extended Attribute Data

FSS0018 --- Unable to set Access Control List (ACL)

FSS0019 --- System File - File ignored


FSS0020 --- Unable to replace registry file

FSS0021 --- Unable to backup registry file

FSS0022 --- Error backing up file data

FSS0023 --- Unable to create temporary filename

FSS0024 --- Unable to create file

FSS0025 --- The file size has increased during the backup

FSS0026 --- The file size has decreased during the backup

FSS0027 --- Unable to open directory handle

FSS0028 --- Error writing NT file/directory stream header

FSS0029 --- Error writing NT file/directory stream data

FSS0030 --- Unable to set file/directory compression state

FSS0031 --- Unable to set file/directory access times

FSS0032 --- File too big

5. Category --- MLS (Media Library Services)

MLS0001 --- General failure

MLS0002 --- Unable to create new media library entry

MLS0003 --- Unable to initialize new media library entry

MLS0004 --- Unable to append to media library entry

MLS0005 --- Unable to open media library entry

MLS0006 --- Unable to close media library entry

MLS0007 --- Invalid Media Library volume handle

MLS0008 --- Invalid/missing volume password

MLS0009 --- Invalid/missing dataset password

MLS0010 --- Attempt to access a volume that has not been opened

MLS0011 --- Access Denied - no password has been specified

MLS0012 --- Unable to read media library volume info

MLS0013 --- Unable to write media library volume info

MLS0014 --- Unable to read media library dataset entry

MLS0015 --- Unable to write media library dataset entry

MLS0016 --- Unable to read media library directory info

MLS0017 --- Unable to write media library directory info

MLS0018 --- Unable to read Media Format Specific volume information

MLS0019 --- Unable to write Media Format Specific volume information

MLS0020 --- Invalid Volume List

MLS0021 --- Invalid callback address passed

MLS0022 --- No more datasets exist for this volume

MLS0023 --- Unable to find the specified dataset entry

MLS0024 --- Attempt to access an unspecified dataset


MLS0025 --- Unable to find specified directory path

MLS0026 --- The currently open volume does not contain any information

MLS0027 --- The currently selected dataset does not contain any information

MLS0028 --- No file information available

MLS0029 --- Unable to rename media library entry

MLS0030 --- Unable to delete media library entry

MLS0031 --- Invalid file query specification

Category --- SSS(Scheduler Services)

SSS0001 --- Unable to start the scheduler session

SSS0002 --- The scheduler has not been started

SSS0003 --- This job is running and cannot be removed

SSS0004 --- Invalid job number

SSS0005 --- This job already exists

SSS0006 --- The scheduler is not responding

SSS0007 --- Job has been held

SSS0008 --- Invalid command has been sent to the scheduler

SSS0009 --- Unable to update this job

SSS0010 --- Non specific error reported by the scheduler

SSS0011 --- Unable to find requested program

SSS0012 --- Invalid option

SSS0013 --- Unable to open the scheduler log file

SSS0014 --- Scheduler has not been initialized

Category --- SMS (Storage Management Services)

SMS0001 --- There has been a failure with the Linked List Mechanism.

SMS0002 --- Unable to read list.

SMS0003 --- Unable to allocate memory.

SMS0004 --- The specified device does not exist.

SMS0005 --- Unable to resolve which device is being specified.

SMS0006 --- The device is in use.

SMS0007 --- A parameter passed to the SMS was invalid.

SMS0008 --- The selected device is not ready.

SMS0009 --- The device is reporting a media error.

SMS0010 --- The device is reporting a hardware failure.

SMS0011 --- The specified operation is not permitted by the device.

SMS0012 --- There has been a reset, power loss or media change.

SMS0013 --- The media in the device is write protected.

SMS0014 --- The media in the device is blank and cannot be read.


SMS0015 --- The device is reporting a vendor specific error.

SMS0016 --- The device has aborted a copy operation.

SMS0017 --- The device has aborted the current command.

SMS0018 --- The device is reporting an error where two things are the same.

SMS0019 --- The device is reporting an overflow error.

SMS0020 --- The device is reporting a compare failure.

SMS0021 --- The device is reporting an unknown error.

SMS0022 --- The device has detected a filemark (tape mark).

SMS0023 --- The device has reached the end of the media.

SMS0024 --- The blocksize on the media does not match the selected size.

SMS0025 --- The device has reached the physical end of the media.

SMS0026 --- The data buffer has been partially written.

SMS0027 --- The specified media is in use.

SMS0028 --- The source location does not contain media.

SMS0029 --- The destination location already has media in it.

SMS0030 --- The media cannot be found.

SMS0031 --- The specified device is a library.

SMS0032 --- Unable to open the selected device at SDS level.

SMS0033 --- Unable to select the interface at SDS level.

SMS0034 --- Unable to select the adapter at SDS level.

SMS0035 --- Unable to select the device at SDS level.

SMS0036 --- Unable to check device because it is busy.

SMS0037 --- The SDS is reporting an error accessing the SDI.

SMS0038 --- The SDI is reporting a general error.

SMS0039 --- The SDI is reporting a data transfer error.

SMS0040 --- The SDI is reporting an error from the device.

SMS0041 --- The SDS is reporting a Sense error.

SMS0042 --- The SDS is reporting an API error.

SMS0043 --- The selected SDS function is not supported.

SMS0044 --- The Storage Manager is unable to refresh the list of devices.

SMS0045 --- Media is not loaded in the selected device.

SMS0046 --- Unable to deallocate drives.

SMS0047 --- The SM has encountered an error with a Mutex Object.

SMS0048 --- The requested media has not been found.

SMS0049 --- The error is unknown.

SMS0050 --- The barcode is not available.

SMS0051 --- Unable to set TSM Protocol.

SMS0052 --- Unable to set TSM Option 1.

SMS0053 --- Unable to set TSM Option 2.


SMS0054 --- Unable to set TSM Port.

SMS0055 --- Unable to set TSM Node Name.

SMS0056 --- Unable to set TSM Password.

SMS0057 --- Unable to set TSM File System Name.

SMS0058 --- Unable to set TSM Server Name.

SMS0059 --- This error is SDS Specific.


®

INTERNATIONAL TECHNICALSUPPORTORGANIZATION

BUILDING TECHNICAL INFORMATION BASED ON PRACTICAL EXPERIENCE

IBM Redbooks are developed by the IBM International Technical Support Organization. Experts from IBM, Customers and Partners from around the world create timely technical information based on realistic scenarios. Specific recommendations are provided to help you implement IT solutions more effectively in your environment.

For more information:ibm.com/redbooks

Redpaper

IBM Tivoli Storage Manager:Bare Machine Recovery for Windows with Cristie BMR

Use Cristie BMR with ITSM, to protect your Windows environment

Learn how to configure your system for recovery

Secure your server environment

This Redpaper describes the use of IBM Tivoli Storage Manager (ITSM) with Cristie BMR Bare Machine Recovery product, to perform the Bare Metal Restoration of Microsoft Windows environments.

Cristie BMR provides a methodology to perform Bare Machine Recovery of Microsoft Windows environments. Cristie BMR is closely coupled to IBM Tivoli Storage Manager to provide a straight-forward methodology to recover from catastrophic server failures.

In this paper, we describe the steps to set up your systems to prepare for system recovery, and show examples of actual recovery scenarios using ITSM with Cristie BMR.

Back cover




Technology

Ibm tivoli storage manager bare machine recovery for windows with cristie bmr redp3704