Lucent Technologies 5ESS-2000, Инструкции по эксплуатации и техническому обслуживанию

Страница: 147 / 1421

exist. You must seek appropriate technical assistance to correct the situation.
Input Message Time-Out
If GENBKUP aborts due to the expiration of the waiting period (``time-out''), GENBKUP prints the expired
input message on the ROP. Check the ROP and investigate if the message ever completed.
If the message never completes or completion message never arrives, investigate the cause and correct the
situation.
If the message completes shortly after the time-out, then retry GENBKUP when the system load is lighter.
The message probably took longer than usual due to system load. However, if this happens consistently on
the same message OR if the message completes a long time (for example, 10 or 15 minutes) after the
time-out, the problem needs further investigation. Seek next level of technical assistance.
If the message completed before GENBKUP timed out, it is due to either GENBKUP was waiting for a wrong
output message or the output message was not sent to MTCLOG. Check MTCLOG0 or MTCLOG1,
whichever was current at the time, and see if the output message reporting the completion/failure is in it.
If the output message is found in the MTCLOG and the time stamp agrees (that is, the time stamp is between
the times when the input message was issued and when GENBKUP timed out), GENBKUP was waiting for a
wrong message. Check the output string pattern listed in this document. If there is a mismatch between what
was printed and what GENBKUP expected, this must be reported to the next level technical support.
If the output message was not found in the MTCLOG and the message is printed on the ROP, check the
ECD classdef form for the output message class to see if MTCLOG is listed as one of the devices. If not,
modify the ECD form to add MTCLOG and retry GENBKUP.
Others
If GENBKUP aborts due to other reasons than those mentioned earlier, consult 235-600-750, Output
Message Manual , ``RCV MENU GENBKUP'' page and find the error message matching the one printed on
the ROP/screen by GENBKUP. Take corrective actions suggested in the manual.
5.11 BACKUP SCHEDULES AND GUIDELINES
5.11.1 GENERAL
The scheduling of various backup levels is determined by local practices based on the following guidelines.
5.11.2 MEMORY TO PRIMARY DISK (MHD 0/1)
Memory to primary disk backup should be scheduled based on recent change and software update activity.
Scheduled intervals for disk backup may vary; they can be performed as often as daily or as infrequently as monthly.
5.11.3 DMERT ROOT PARTITIONS TO BACKUP PARTITIONS
The DMERT root partitions backup should be based on root partition changes associated with the ECD and
software update activity. The primary partitions should be copied to the backup partitions before ECD and/or
software updates are made permanent. This backup activity is not required for individual changes but should be
done for sets of changes. If there is a number of software updates which affect the root partitions, the root partitions
should be copied to backup root and the software updates should be applied. However, if all software update
changes were made to files with pathnames beginning with /no5text, then this type of backup is not needed. The
no5text partition does not have a backup partition on the disk.
235-105-210 October 1999
Copyright © 1999 Page 39