Chapter 5. Automate the system backup using the ITSM scheduler
A.2 Windows 2000 (Professional, Server, Advanced Server standard installation or with
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 diskettes
Here 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.
Figure 5-27 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.
.
Figure 5-30 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 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 files
To 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 definitions
The 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
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
MLS Media Library Services
SSS Scheduler Services
SMS Storage Management Services
Category Description
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
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
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)
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
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.
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.
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.
® from around the world create timely technical information based on realistic scenarios.
Specific recommendations are provided to help you implement IT solutions more
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.