Procedure 6.21: MAKE FULL OFFICE BACKUP DISK
5E10 and LATER
OVERVIEW
CAUTION:
During normal operations, work within a couple of file systems can trigger
UNIX*
file system alarms.
These alarms normally warn the switch owner of situations where a file system is likely to run out of file
space unless actions are taken to prevent the space exhaustion. Though, in the cases of /updtmp (or
/update 5E9 or later) and /nododd/imdataX, these file systems can become and (in the case of
/no5odd/imdataX,), stay full legally because of software update application or NRODD growth,
respectively.
NOTE:
The backout Last Overwrite feature can not be used if the office backup tapes/disks are used to recover the
switch.
This procedure allows the technician to Make Full Office Backup of the AM Text and AM office dependent data
(ODD) to software backup disk and corresponding DAT (digital audio tape) or tapes.
The full office backup disk procedure is the process used to save a copy of the office software [text, ODD, and
equipment configuration data (ECD) data bases]. The full office backup is done in order to provide a reliable vehicle
for system recovery in the event that data in both system disk drives becomes mutilated.
A software backup disk (MHD14 or MHD15) is created from the files on the system disk, and backup tapes are
created from the SM text and SM ODD on the outboard disks. Also, two (or more) tape sequences are required, one
for SM Text, and one tape for each disk pair that is allocated for SM ODD. The tapes made on KS23113, LIST 14
(
KEYSTONE
III) tape drives must be writable at 6250 bits-per-inch (bpi) and should be certified tapes. Certified
tapes are tapes that have been verified to be writable at 6250 bpi. The tapes should also be usable across the
expected temperature range of the particular office.
Office backup is performed by either the automated GENBKUP process which requires approximately 2 to 4 hours
to complete or by a manual office backup which requires from 8 to 12 hours to complete. The time required to do an
ODD back-up must also be considered.
The automated GENBKUP executes all audits, populates the software backup disk(s) with AM text and AM ODD,
and creates the SM Text, SM ODD tapes. If any commands identify errors during the execution of GENBKUP,
GENBKUP will quit gracefully with a message indicating the command which found the errors.
GENBKUP should be entered from the recent change terminal or a supplemental trunk line work station. It may also
be entered from the SCC during nonprime hours and exited (entering ``q'') before the backup media is changed.
After invoking GENBKUP, it will query you for the type of backup that is wanted and tell you when tapes should be
mounted and unmounted.
When using GENBKUP, the portion of the backup process that runs the
BKUP:ODD
, simplexes disks, clears
partitions, and restores partitions may be created separately from the tape (and software backup disk) generation.
When the main menu is displayed, tape request should be made instead of software disk backup to execute the
memory checking logic of GENBKUP. When GENBKUP prompts for the tape to be mounted, exit (entering ``q'') and
return to the tape menu. The tapes and software backup disk may be generated during normal shift hours by
reentering GENBKUP when the technician is in the office and able to manipulate the backup tapes. Software
backup disk and matching backup tapes (text and ODD) should always be made in the same GENBKUP session.
Disk backup of the entire office should be done at least once a month or more often if many software updates and/or
ECD changes are being added to the office. An office should keep two different versions of office backup disks (one
on each copy), with the oldest copy being discarded when a new copy is made.
235-105-210
October 1999
Copyright © 1999
Page 1
Summary of Contents for 5ESS-2000
Page 96: ...235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 184: ...235 105 210 October 1999 Copyright 1999 Page 3 ...
Page 300: ...13 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 55 ...
Page 339: ...7 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 13 ...
Page 342: ...235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 359: ...235 105 210 October 1999 Copyright 1999 Page 5 ...
Page 609: ...2 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 12 ...
Page 676: ...235 105 210 October 1999 Copyright 1999 Page 9 ...
Page 792: ...3 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 9 ...
Page 799: ...Figure 11 36 3 1 Cleaning Points 235 105 210 October 1999 Copyright 1999 Page 7 ...
Page 801: ...235 105 210 October 1999 Copyright 1999 Page 9 ...
Page 839: ...2 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 16 ...
Page 999: ...2 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 13 ...
Page 1008: ...Figure 11 55 1 CTSNS DIP Switch Settings 235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 1011: ...235 105 210 October 1999 Copyright 1999 Page 5 ...
Page 1053: ...235 105 210 October 1999 Copyright 1999 Page 15 ...
Page 1289: ...Figure 15 17 2 AMATPS Data Link 235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 1292: ...235 105 210 October 1999 Copyright 1999 Page 5 ...
Page 1303: ...9 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 1360: ...Figure 15 47 2 Typical SCANS III Link Diagram 235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 1372: ...235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 1374: ...235 105 210 October 1999 Copyright 1999 Page 4 ...
Page 1421: ...Table 1 1 O M Checklist 235 105 210 October 1999 Copyright 1999 Page 3 ...