HP NetServer AA 6200 Backup/Recovery Guide for HP AA Solutions - Page 11

policy for a system recovery.

Page 11 highlights

• Perform a Marathon software installation for the CE ONLY while operating on the IOP (in offline mode). 1. Select Endurance Software Installation 2. Check CE and explicitly un-check IOP 3. When prompted for the location of the CE root browse or enter d:\winnt (or an alternative pathname that defines your CE OS). 4. If prompted to overwrite files that are newer on disk - choose NO for all files that begin with "mtc". Such files are Marathon components that have been upgraded via a hotfix installation. By choosing NO it will not be necessary to reapply the Marathon hotfixes. • Reboot the IOP(s) in Operational Mode • Boot the repaired CE OS. The CE WILL NOW BOOT (if the proper repair was made)!! 3. Restore A Saved Copy Of Windows NT Prepare and maintain an EMERGENCY RECOVERY COPY of the CE OS. Use an IOP in offline mode to invoke a recovery - then force a mirror copy in the proper direction as you recover2. Reapply your tape backups to bring the system to a fully consistent state. Marathon provides a tool (normally used during installations) that supports this procedure. Mtccpynt.exe is located on the Marathon CDROM and can be used to "clone" the running NT installation to another disk partition for safe storage. (See Marathon Endurance 4000 User's Guide, Chapter 6-Marathon tools and utility -- for Mtccpynt usage.) If necessary it can be used to reverse the copy direction - and therefore restore a disk to the state that was most recently saved. There are limitations to this approach - just as there are when depending on Emergency Repair Disks (ERDs). You need to update the information each time a significant change to the CE OS is made or it becomes out of date. A recovery from the saved data should be upgraded with the latest back up (of the system disk). Several files can out of date (particularly the registry and user profiles) after making the (safe) copy - and before executing a recovery that uses it. The steps to implement this scheme are included below: PERIODICALLY CREATE AN EMERGENCY RECOVERY COPY of your CE OS In the following discussion: • Determine the pathname where mtccpynt.exe can be located (Marathon CD-ROM Z:\support for purposes of the following discussion.) • Determine the drive letter where the CE OS resides.- from the perspective of the CE. (C: for purposes of the following discussion) • Determine the drive letter where the EMERGENCY RECOVERY COPY will be created (X: for purposes of the following discussion.) • Create a small partition for this purpose - and label it conspicuously (i.e. CE_RECOVER). A minimum of 200MB should be enough (compressed NTFS is recommended). A nominal NT Server install consumes about 80MB but over time this can grow. Locate this storage area in accord with one of the following two alternatives: • On a CE mirror set. -OR- 2 In the normal HPAA system, it is recommended that the System Administrator keep a spare good copy of the CE boot drives on a 200MB or larger partition. This can be an insurance policy for a system recovery. 12/08/99 Hewlett-Packard Co. 11

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16

12/08/99
Hewlett-Packard Co.
11
Perform a Marathon software installation for the CE ONLY while operating on the IOP (in offline
mode).
1.
Select Endurance Software Installation
2.
Check CE and explicitly un-check IOP
3.
When prompted for the location of the CE root browse or enter d:\winnt (or an alternative
pathname that defines your CE OS).
4.
If prompted to overwrite files that are newer on disk - choose NO for all files that begin with
“mtc”.
Such files are Marathon components that have been upgraded via a hotfix installation.
By choosing NO it will not be necessary to reapply the Marathon hotfixes.
Reboot the IOP(s) in Operational Mode
Boot the repaired CE OS.
The CE WILL NOW BOOT (if the proper repair was made)!!
3.
Restore A Saved Copy Of Windows NT
Prepare and maintain an EMERGENCY RECOVERY COPY of the CE OS. Use an IOP in offline
mode to invoke a recovery - then force a mirror copy in the proper direction as you recover
2
.
Re-
apply your tape backups to bring the system to a fully consistent state.
Marathon provides a tool (normally used during installations) that supports this procedure.
Mtccpynt.exe is located on the Marathon CDROM and can be used to “clone” the running NT
installation to another disk partition for safe storage. (See Marathon Endurance 4000 User's Guide,
Chapter 6-Marathon tools and utility -- for Mtccpynt usage.)
If necessary it can be used to reverse the
copy direction - and therefore restore a disk to the state that was most recently saved.
There are limitations to this approach - just as there are when depending on Emergency Repair Disks
(ERDs).
You need to update the information each time a significant change to the CE OS is made or
it becomes out of date.
A recovery from the saved data should be upgraded with the latest back up
(of the system disk).
Several files can out of date (particularly the registry and user profiles) after
making the (safe) copy – and before executing a recovery that uses it.
The steps to implement this scheme are included below:
PERIODICALLY CREATE AN EMERGENCY RECOVERY COPY of your CE OS
In the following discussion:
Determine the pathname where mtccpynt.exe can be located (Marathon CD-ROM Z:\support for
purposes of the following discussion.)
Determine the drive letter where the CE OS resides.- from the perspective of the CE.
(C: for
purposes of the following discussion)
Determine the drive letter where the EMERGENCY RECOVERY COPY will be created (X: for
purposes of the following discussion.)
Create a small partition for this purpose - and label it conspicuously (i.e. CE_RECOVER).
A
minimum of 200MB should be enough (compressed NTFS is recommended).
A nominal NT
Server install consumes about 80MB but over time this can grow.
Locate this storage area in
accord with one of the following two alternatives:
On a CE mirror set.
–OR-
2
In the normal HPAA system, it is recommended that the System Administrator keep a spare
good copy of the CE boot drives on a 200MB or larger partition. This can be an insurance
policy for a system recovery.