5.12.2 ORIGINATION
Origination for ODD backup is under local control. Local control is required for the following reasons:
(a)
The ODD backup is run ``on demand.''
(b)
After the first initialization of the office, the dynamic head blocks stored in the ODD must be backed up.
5.12.3 FREQUENCY
The frequency of ODD backup depends on the disk space allocated to log regular RCs and CORCs and the number
of these changes in the system. In addition to showing the percentage, the output message will also indicate the
number of regular RCs and CORCs in the disk log. The
OP:RCSTAT,SM=x&&x,AM;
,
OP:CORC
STAT,SM=x&&y,AM,CMP=a&&b;
message will give the amount of CORCs in each processor.
The
OP:ODD,SM=x&&y,CMP=a&&b,AM;
message will give the percent of memory used and also the percent of
available memory for each processor.
It is recommended that the ODD be backed up whenever the disk log reaches 80 percent of the log space usage.
To avoid recent change performance degradation, the backup should be run in off-peak hours when system load
and RC input are minimal.
5.12.4 SAFEGUARDS
When the disk log files reach 80 percent of the log file space usage, an alarmed output message notifies local
maintenance personnel.
When an ODD backup is in progress, CORCs are blocked and the subscriber receives reorder tone. Similarly, when
the
EXC:ODDRCVY:ALL;
message is required, the backup request is denied. Also, if an attempt to perform an
ODD backup is initiated while a processor is in the RC BKOUT state, the backup request is denied for this
processor.
5.12.5 DISK SPACE REQUIREMENTS
The ODD backup requires disk space for two copies of the entire ODD. The first copy is used as a working copy for
the file update during backup, while the other copy is considered a ``save'' copy.
5.12.6 RELIABILITY AND RECOVERY
Errors may be introduced during an ODD backup operation. These errors may be due to bad or lost messages,
buffer overwrites, etc.
All processes used during an ODD backup are automatically released if a failure occurs. If the backup fails, a
manual restart of the ODD backup operation should correct the problem. If not, a more serious system malfunction
may be indicated. Seek technical assistance.
The ODD backup does not interface directly with any of the levels of software recovery. If a processor or the system
has an initialization during an ODD backup, the ODD backup is normally aborted with no damage done to the official
ODD files. The ODD backup can be restarted at another time. After the initialization, an RC recovery must be
performed to reinstate the lost RCs and CORCs.
5.13 OFFICE DEPENDENT DATA RECOVERY
235-105-210
October 1999
Copyright © 1999
Page 41
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 ...