HP NetServer AA 4000 HP AA HP Netserver 4000 Reference Guide - Page 113

update your NT Emergency Repair Disk.

Page 113 highlights

Ch 6: Backp and Restore is a significant change to the CE, a new backup copy needs to be made using the MTCCPYNT.EXE. Otherwise, the backup directory created by the utility becomes out of date. A recovery from the saved data should be upgraded with the latest back up (of the system disk). The steps to implement this scheme are included below: a. PERIODICALLY CREATE AN EMERGENCY RECOVERY COPY of your CE OS b. Determine the pathname where mtccpynt.exe can be located (Marathon CD-ROM Z:\support for purposes of the following discussion.) c. Determine the drive letter where the CE OS resides.- from the perspective of the CE. (C: for purposes of the following discussion) d. Determine the drive letter where the EMERGENCY RECOVERY COPY will be created (X: for purposes of the following discussion.) e. 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: (1) On a CE mirror set, OR (2) On both IOP disks access the partitions from the CE using the virtual network. NOTE Remember that the virtual network is slow, so plan the time when this is done to have minimal impact to users. f. After each successful update to the CE OS, use Marathon's MTCCPYNT utility to "clone" the current (running) CE root as the "emergency recovery copy". (Browse the marathon CD ROM and run z:\support\mtccpynt c:\winnt x:. If using the IOP disk alternative, one mtccpynt (of two) must be targeted at each IOP. NOTE When performing updates to the emergency recovery copy, you will be prompted to overwrite existing directories. Answer yes in all cases. g. Repeat the above procedure each time your would otherwise update your NT Emergency Repair Disk. Network Server Division 6-13

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142

Ch 6: Backp and Restore
Network Server Division
6-13
is a significant change to the CE, a new backup copy needs to be
made using the MTCCPYNT.EXE.
Otherwise, the backup
directory created by the utility becomes out of date.
A recovery
from the saved data should be upgraded with the latest back up
(of the system disk).
The steps to implement this scheme are included below:
a.
PERIODICALLY CREATE AN EMERGENCY
RECOVERY COPY of your CE OS
b.
Determine the pathname where mtccpynt.exe can be located
(Marathon CD-ROM Z:\support for purposes of the
following discussion.)
c.
Determine the drive letter where the CE OS resides.- from
the perspective of the CE.
(C: for purposes of the following
discussion)
d.
Determine the drive letter where the EMERGENCY
RECOVERY COPY will be created (X: for purposes of the
following discussion.)
e.
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:
(1)
On a CE mirror set, OR
(2)
On both IOP disks access the partitions from the CE
using the virtual network.
NOTE
Remember that the virtual network is slow, so plan the time
when this is done to have minimal impact to users.
f.
After each successful update to the CE OS, use Marathon’s
MTCCPYNT utility to “clone” the current (running) CE root
as the “emergency recovery copy”.
(Browse the marathon
CD ROM and run z:\support\mtccpynt c:\winnt x:.
If using
the IOP disk alternative, one mtccpynt (of two) must be
targeted at each IOP.
NOTE
When performing updates to the emergency recovery copy, you
will be prompted to overwrite existing directories.
Answer yes
in all cases.
g.
Repeat the above procedure each time your would otherwise
update your NT Emergency Repair Disk.