ATT DEFINITY Communications System Generic 1, Generic 3, System Management Instructions Manual

							CHAPTER 8. SYSTEM BACKUP FOR DEFINITY G3r
If a good copy of the announcement file is not available, then the restore announcements opera-
tion cannot be executed until the 
save announcements command is successfully completed.
The announcements on the board are still accessible and usable.
Restore Announcements Command
The restore announcements command copies announcement data from the specified MSS dev-
ice to the announcement board (TN750).
Command Syntax
restore announoements [disk | tape]
The announcement file is always restored from the active device.
The 
[disk | tape] options specify the device from which to restore the announcement board data.
This set of options only applies in a system with a disk.
Invoking the 
restore announcements command with the disk option forces the system to copy
the announcement board data from the disk to the announcement board.
Invoking the 
restore announcements command with the tape option forces the system to copy
the announcement board data from the tape to the announcement board.
Command Operation
There is only one announcement board allowed m the system. The announcement file is always
restored from the active processor’s device.
The 
restore announcements command will not be allowed if there is no integrated announce-
ment board in the system (E28); or if any port on the ANN board is active (E31).
The 
restore announcements command will be denied if:
l No announcement data module has been administered (E29).
l No system port data module has been administered (E35).
l The announcement data module is out of service (E34).
l A user is in an integrated announcements session (E31).
A user cannot enter an integrated announcement session after the restore announce-
ments command has started.
l The MSS is in use.
The MSS maybe in use by either another user or by maintenance (E3).
l The announcement file is not formatted on the MSS (E40).
8-5 
						

							CHAPTER 8. SYSTEM BACKUP FOR DEFINITY G3r
If restoring from tape, the restore announcements command will abort if no tape is in the tape
drive (E37).
The restore announcements command will also abort if:
l No system access port is available (E39).
l The MSS is in use by the SPE duplication memory refresh activity (E41).
Announcements on the ANN board will not be available until the restore operation is complete.
Treatment to calling users will vary according to the feature. Otherwise, normal call processing
service continues during the restore announoements operation.
The command completion status is displayed on the system administration terminal. The
displayed information includes a success or error message.
In case of a failure, it is the users responsibility to make sure the announcement file is com-
pletely copied to the announcement board, although the system will continually attempt to down-
load the board in 10 minute intervals until a download issuccessful, announcements are
recorded, or a download is initiated from the system administrative terminal. The user should
take appropriate action based on the error message returned. If the error is the result of a
hardware or firmware failure, the MSS software will log a hardware error with maintenance.
Maintenance software will invoke tests to diagnose and attempt to correct the problem. If mainte-
nance software fails to correct the problem, an alarm would be raised and the system technician
should take appropriate action.
In the case where the system crashes and/or there is aprocessor interchange, the restore opera-
tion will fail. In this case, there will not be a valid announcement file on the announcement board.
The command should be restarted on the newly active processor to copy the announcements
from the active processors MSS device to the announcement board. Until the announcements
are successfully and completely copied to the announcementboard, calls will not be connected to
any announcements on the ANN board.
When the ANN board is plugged in or reset, maintenance
will perform a series of tests, including
a DRAM Checksum test. The teat will fail due to the power loss to the board, resulting in
automatic downloading of the announcement file.
8-6 
						

							CHAPTER 8. SYSTEM BACKUP FOR DEFINITY G3r
Error Conditions
The following is a list of all error messages displayed to the user. If any of these error conditions
can be attributed to hardware failures or disk/tape configuration problems, they will be logged
with the maintenance subsystem. Error messages that are caused by a user entering improper
command operations will not be logged with the maintenance subsystem; the user is notified of
the error.
For each error message listed, an identifier is provided which indicates where on the screen the
message will occur. If (M) is shown next to the error code, the error message will appear on the
message line. If (W) is shown next to the error code, the error message will appear as command
output.
A failure can occur on either processor in a duplicated system. When the error is displayed, it is
associated with the processor on which the error was encountered.
E3 (M)
E11 (M)
E12 (M)
E13 (W)
E14 (W)
E16 (W)
E28 (W)
E29 (W)
MSS is currently in use
This message means some other administration or maintenance user is currently
making use of the MSS device and, therefore, it is not available for the MSS operation
requested.
Standby option invalid on a simplex system
This message means a duplex option to a command was specified on a simplex sys-
tem.
The disk option is invalid in a tape-only system
This message means that a disk option was entered on an MSS command for a
tape-only system.
Disk device is out of service
This message means that the disk device has been taken out of service by mainte-
nance.
Tape device is out of service
This message means that the tape device has been taken out of service by mainte-
nance.
Standby processor (PE_A) is not available or
Standby processor (PB_B) is not available
This message means that the standby processor has been taken out of service by
maintenance, that the PE-SELECT switches are not in their normal position, or that
some other hardware problem exists. When the standby processor is out of service,
memory shadowing from the active processor to the standby processor is disabled.
Integrated announcement board not present
This message indicates that the announcement board is not present in the system.
Required data module not administered or unavailable.
The required data module is either not administered or is currently in use.
8-7 
						

							CHAPTER 8. SYSTEM BACKUP FOR DEFINITY G3r
E31 (W)
E32 (W)
E33 (W)
E34 (W)
E35 (W)
E36 (W)
E37 (W)
E38 (W)
E39 (W)
E40 (W)
E41 (W)
E42 (W)
Announcement port in use; please try later.
One or more of the announcement ports are in use. The port could be in use for an
integrated announcements sessionor for integrated announcement playback.
Bad announcement file on tape (disk).
This message indicates that the announcement file stored on disk or tape is corrupt.
A valid file must be stored on the MSS before it can be accessed. This helps to
prevent overwriting valid announcements on the ANN board.
No announcements on board.
Announcements must be stored on the ANN board in order to proceed with com-
mand. This helps to prevent overwriting or corrupting a good annoucement file on
the MSS.
Announcement data module out of service.
This message indicates that the announcementdata module has been taken out of
service by maintenance. The data module could have been taken out of service
because of errors on the data module detected by maintenance.
Required system access port not administered or out of service.
A systemaccess port is either not available or is out of service.
Announcement data module not available.
Cannot access the announcement data module because the upload/download port is
active.
Tape access failure; no tape cartridge or tape drive failure.
No tape is in the tape drive.
Tape write failure; no tape cartridge or tape drive failure.
The tape is write protected.
Required system access port unavailable.
The required system accessport is unavailable.
Tape (disk) not formatted with announcement file.
Device must be formatted with the announcement file in order to read or write it.
Refresh currently in progress, please try again later.
MSS is in use by SPE duplication memory refresh. This is an indication to try the
command again later.
MSS device is maintenance busy.
8-8 
						

							CHAPTER 8. SYSTEM BACKUP FOR DEFINITY G3r
Save Translation Command
The save translation command copies translation data from memory to the MSS. By default,
translation data is written to the primary MSS device in a simplex processor system, or to both
primary MSS devices in a duplicated processor system. In addition, the save translation com-
mand can be directed to write to devices on either of the processors and/or the secondary
device(s). The translation data can be automatically backed up as part of regularly scheduled
maintenance. It is recommended that automatic backup be performed on a daily basis.
Command Syntax
save translation [active | standby | SPE_A | SPE_B | both | either] [disk | tape]
The bracketed options specify which mass storage system the translation data is to be saved to.
This set of options only applies in a duplicated system. The options, 
SPE_A and SPE_B, refer to
processors 
A and B respectively in a duplicated system.
Invoking the command with the 
active option instructs the system to write to the specified device
in the active processor.
Invoking the command with the 
standby option instructs the system to write to the specified dev-
ice in the standby processor.
Invoking the command with the 
either option causes the system to write the translation data to
the specified device on both processors. If the standby processor is inaccessible, the command
will still execute on the active processor and data will be copied to the specified device.
Invoking the 
save translation command with the SPE_A option forces the system to write the
translation data to the specified device in processor A. 
SPE_A is the default in a simplex system.
Invoking the 
save translation command with the SPE_B option forces the system to write the
translation data to the specified device in processor B.
In duplicated systems, 
both is the default option.
The 
[disk | tape] option specifies the device on which to save the translation data. This option
set only applies in a system with a disk.
Invoking the 
save translation command with the disk option forces the system to write the
translation data to the disk. In a system configured with both a disk and a tape, disk is the
default.
Invoking the 
save translation command with the tape option forces the system to write the
translation data to the tape. In a system configured with only a tape unit, tape is the default.
In a duplex system, the capability to save translation to only one of the MSS devices is provided.
This capability should be exercised with extreme caution since it is Iikely to lead to translation
data inconsistencies between the different devices on the two processors.
8-9 
						

							CHAPTER 8. SYSTEM BACKUP FOR DEFINITY G3r
Command Operation
The save translation command writes two time-stamped identical copies of translation data to
the selected device(s). The time stamp for both copies will be the same (it will be the time of writ-
ing to the first copy). Each copy is written as consecutive 2K blocks. Each block contains a
checksum for error detection purposes. Each copy contains a time stamp and the state of the
copy (either “good” or “bad”).
The save operation writes one complete copy first; then writes the second copy in a different area
of the device. The save operation updates only one copy at a time. The save operation will
always choose to overwrite the “least good” copy first. The following selection criteria should be
applied on both the active and standby devices:
l If a copy has a bad status, always overwrite that copy first.
l If both copies have good status, overwrite the one with the older time stamp. If both time
stamps are the same, it does not matter which copy is overwritten first since the copies
are identical.
Each copy of the translation data is marked “bad” prior to a translation save operation, and it will
only be marked “good’ after the save operation to that file completes successfully. Any failure
during the save operation, including a system crash, will usually affect only one copy of transit-
ion data. If this occurs, the affected copy will be marked with a “bad” status indicator and should
not be used to bad translation into the system. Thus an intact copy of translation can be used as
a backup. Normally at least one of the two copies will be in a good state. If save translation is
performed automatically as part of daily scheduled maintenance, there is a high degree of prob-
ability that identical copies of translation exist on the tape.
When MSS devices on bothprocessors in a duplicated system are specified, the save operation
will save translation data from the active processor to the active and standby MSS devices in
parallel. The status of each save operation is reported to the user separately. If one of the save
operations fail, the save operation to the other device continues.
If invoked during regularly scheduled maintenance, the 
save translation command in a dupli-
cated processor system will save the translation to one of the MSS devices even if the other dev -
ice is out of service.
8-10 
						

							CHAPTER 8. SYSTEM BACKUP FOR DEFINITY G3r
The command completion status is displayed on the screen, as shown below.
Save Translation
ProcessorCommand Completion StatusError Code
SPE_A*
success/specific error messagenl
SPE_B*success/specific error messagen2
* In a simplex system, only the active (default) SPE status is given. ln a duplex system if a qualifier is
used to select save translation for only one SPE, only that SPE’s status is given.
FIGURE 8-1. Save Translation Completion Status
The displayed information includes either a success message or an error message and error
code for each processor (see Table 8-A). A success message means both copies of translation
data were updated successfully on a particular device from the in-memory translation data. The
error code for each processor provides further information as to whether only one or two copies
of translation data were updated successfully. If only one copy was updated or neither copy was
updated, an alarm would be raised on that device so that the system technician can take
appropriate repair actions.
TABLE 8-A. Save Translation Command Error Codes
CODE interpretation
0
The save operation was a complete success;
both copies of translation data were updated.
1The save operation was a partial success;only
one of the two copies of translation data was updated.
2The save operation failed completely; no translation
was saved to eithercopy of translation data.
8-11 
						

							CHAPTER 8. SYSTEM BACKUP FOR DEFINITY G3r
The following operational rules apply to the save translation command:
1.
2.
3.
4.
5.
6.The 
save translation command will only be allowed if there are no translation updates
being made. All requests to update translation, after the command starts, will be denied
(E1).
If Terminal Translation Initialization (TTI) activation or deactivation is in progress, the
save translation command will be denied (E2).
The 
save translation command will not be allowed if the MSS is engaged by another
user or is being used for background maintenance (E3).
The options entered by the user are validated against the system configuration and the
target devices for the 
save translation command are determined (E11, E12).
If the user requests that translation be saved to a disk, the disk must be in service (E13).
If the user requests that translation be saved to a tape, the tape must be in service
(E14). If the user requests that translation be saved to the standby processor, the
standby processor must be in service, shadowing must be enabled, and refresh must be
completed (E16).
If the file system of the target device is a core-dump file system, the command will be
denied (E17).
If the target device is a tape, and the file system type of the tape is an installation file
system, and the vintage of the boot image running in the active processor
matches the
vintage of the boot image on the tape, then the system will first configure the tape with
the same configuration as is currently running. If the in-memory vintage does not match
the vintage on the tape, the save translation command will be denied (E18). In this situa-
tion, the user must manually configure the tape by using the configure command and
then reissue the 
save translation command.
If errors are encountered in the operations described above, the save operation should
not be attempted.
8-12 
						

							CHAPTER 8. SYSTEM BACKUP FOR DEFINITY G3r
Backup Command
Additional data integrity is achievable through disk to tape backups. These backups may be
done on demand or run daily as part of scheduled maintenance. This command is only valid in a
system which has both disk and tape as part of its MSS. The 
backup command will work in
either a simplex SPE or a duplex SPE system. When the command is run as part of scheduled
maintenance, the default for a simplex system is an incremental backup of SPE A. In a duplex
system, the default is an 
incremental backup on both SPE A and SPE B.
When the 
backup command is executed on demand the defaults remain the same.
Command Syntax
backup disk [active | standby | SPE_A | SPE_B | both | either] [incremental | full]
The bracketed options, [active | standby | SPE_A | SPE_B | both | either], specify which mass
storage system the user wishes to backup. Invoking the backup command with the SPE_A
option causes files from the disk associated with processor A to be copied to the tape cartridge
on the same processor. SPE_A is the default in a simplex system. Invoking the backup com-
mand with the SPE_B option causes the files on the disk on
processor B to be copied to the tape
on the same processor.
Invoking the command with the 
active option causes the files on the disk on the active processor
to be copied to the tape on that processor.
Invoking the command with the 
standby option causes the files on the disk on the standby pro-
cessor to be copied to the tape on that processor.
Invoking the 
backup command with the both option causes files on the disk associated with
both of the processors to be backed up to their respective tapes concurrently. If the standby pro-
cessor is inaccessible the command will fail on both processors. No files will be copied from disk
to tape on either processor. The default value in a duplex system is 
both.
Invoking the backup disk command with the either option causes the files on the disks associ-
ated with both of the processors to be backed up to their respective tapes concurrently. If the
standby processor is inaccessible, the command will still execute on the active processor and the
disk files will be copied to tape.
Invoking the command with the 
incremental option causes a selective backup to be performed.
In this case, all files on the disk that are marked as “good files” and which have a newer last file
update time than the corresponding tape files, are copied to the tape. Not copying files marked
as “bad” ensures that corrupted files do not overwrite good (but possibly older) files. The default
value is incremental.
If a full disk backup is specified, the entire disk is copied to tape. All files, “good” and “bad,”
regardless of the last file update times, will be copied to the tape.
8-13 
						

							CHAPTER 8. SYSTEM BACKUP FOR DEFINITY G3r
Command Operation
When an incremental backup is performed, the following procedure governs this operation.
Before each file is copied from the disk to the tape, the file on the tape is marked as “bad.”
When the file has been completely copied over to the tape, the file is then marked as “good” on
the tape. This process ensures that if the system were to reboot in the middle of this operation,
files in the process of being copied will not be usable (on the tape) because they will still be
marked as “bad.”
When a full backup is performed, the following procedures are used. When the process begins,
all files on the tape are marked as “bad.” When the entire disk has been copied, the files on the
tape will be marked as “good.” The only exception to this is that a file which is marked as “bad”
on the disk will retain this marking on the tape also.
When the backup is performed on both processors, the operation is performed in parallel. If the
backup operation fails on one processor the backup operation will proceed on the other proces-
sor.
The success or failure of the backup operation for each processor wili be displayed on the
screen, as shown below.
Processor
SPE_A*
SPE_B*
Backup Disk
Command Completion Status
success/specific error message
success/specific error message
* In a simplex system, only the active (default) SPE status is given. In a duplex system, if a qualifier is
used to select backup disk for only one SPE, only that SPE’s status is given.
FIGURE 8-2. Backup Completion Station
The following operational rules apply to the backup command:
1.
2.
3.The 
backup command will only be allowed if there are no other applications currently
using the MSS devices (E3).
The options entered by the user are validated against the system configuration and the
target devices for the backup command are determined (E11).
The disk must be in service (E13). The tape must be in service (E14).
8-14