Procedure 6.12: SCHEDULE AUTOMATIC ODD BACKUP
OVERVIEW
This procedure requests to schedule the ODD backup to run periodically at specific intervals.
NOTE:
During heavy recent change activity, an ODD backup has a slight chance of aborting because of a lack of
resources for the backup to execute. Requesting ODD backup during heavy recent change activity is not
recommended because this will affect the ODD backup and recent change performance and response
time. If a backup aborts, re-request the ODD backup during a period of light recent change activity. Failure
of ODD backup will cause a minor alarm.
PROCEDURE
1.
At master control center (MCC), type and enter:
BKUP:ODD[,FULL][,AM][,CMP=0][,NRODD=a&&b][,RODD=a],EVERY=c,AT=d;
Where:
FULL
= Back up the entire ODD unconditionally. If FULL is not specified, only those ODD
blocks that have been altered since the last ODD backup will be backed up (a differential
backup). The AM ODD backup is always a full backup (that is, a differential backup of the
AM ODD in not available).
CMP
= Back up the CMP ODD.
CMP
= Back up the CMP ODD.
NRODD
= Back up the SM nonredundant ODD.
RODD
= Back up the redundant ODD. (The default is the entire system [the AM, the CMP,
NRODDs of all SMs and RODD] if none is specified).
a
= SM number or the lower limit of a range of SM numbers.
b
= Upper limit of a range of SM numbers.
c
= Interval in days (0-90) between successive ODD backup runs.
d
= Time of day in in hours and minutes when ODD is to be backed up.
Response:
NG
= No good. Valid values are as follows:
INVALID CMP RANGE = the input request is not valid.
INVALID SM RANGE = the input request is not valid.
PF
= Printout follows: Request accepted and the corresponding
BKUP:ODD
output message
will follow:
RL
= Retry later. The request cannot be executed now due to unavailable system resources.
Results:
Automatic ODD backup scheduled.
2.
STOP. YOU HAVE COMPLETED THIS PROCEDURE.
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 ...