5.11.4 ODD BACKUP TO TAPE
The frequency of the ODD backup to tape will depend on how often an ODD backup (from main store to disk) is
performed in the particular office. The ODD backups should be performed on a regular basis. The appropriate time
to schedule an ODD disk image backup to tape is before an ODD backup. This will allow the maximum soak period
for the ODD disk image before it is written to tape. Also, whenever the ECD has been altered, the ODD backup to
tape should not be used. The full office-to-tape backup should be used instead. This is because the ODD backup to
tape does not cover the ECD. All ODD disk image backup tapes made between two full office-to-tape backups
should be saved. When a new ODD backup tape is made after a full office backup, the oldest ODD disk image
backup tape made since the previous office backup should be discarded first. The following schedule for ODD
backup to tape is recommended:
(a)
If an ODD backup is performed daily, the ODD disk image backup should be done once a week.
(b)
If an ODD backup is performed twice a week, the ODD disk image backup should be done once every 2
weeks.
(c)
If an ODD backup is performed weekly, the ODD disk image backup should be done once a month.
In any event, an ODD disk image backup should be done at least once a month and no more than once a week. In
addition to the ODD backup to tape, an ODD recovery from tape procedure is provided in the Memory Alteration
Procedures (Section 6 ).
5.11.5 FULL OFFICE BACKUP TO TAPE
The full office backup tapes should be made based on the following considerations:
(1)
Office backup tapes should be made when the number of permanent software updates in the office reaches
a point that makes it desirable to back up the software changes to tape. The number of software updates is
office dependent but should not be more than 5.
(2)
Office backup tapes should be made when there is text/data base coupling that results from a recent change
or software update change. The coupling and the need to make an office backup should be specified in the
software update documentation.
(3)
Office backup tapes should be made whenever the office experiences a DMERT level 3 or higher
initialization. The backup should be done after the system stabilizes and the disks are duplexed.
(4)
After a software release retrofit, a set of office backup tapes should be made of the new software release.
Once the office is committed to the new software release, the old software release backup tapes should be
purged from the office in approximately 2 weeks. Also, the new software release tapes used to boot the office
during the software release retrofit should be kept as certified tapes until they are no longer usable as backup
tapes.
5.12 OFFICE DEPENDENT DATA BACKUP
5.12.1 PURPOSE
The purpose of ODD backup is to provide a sound basis for recovery by allowing the system to recover quickly from
a boot or pump. The changes to the ODD may be introduced by regular recent change (RC), customer-originated
recent change (CORC), maintenance, and ODBE.
Backup of the ODD makes the current memory image (that is, in-core contents) of the ODD permanent on disk. The
ODD in the AM, CMP, and all of the SMs will be backed up during this operation.
235-105-210
October 1999
Copyright © 1999
Page 40
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 ...