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

							CHAPTER 7. SYSTEM BACKUP FOR DEFINITY G1 AND G3i
Tape Backup for a System Without the Duplication Option
Two cassette tapes are provided with the system. It is recommended that backup copies of
the translation data be made weekly, or after many changes have been made to the translation
data. This will minimize the loss of recent translation data changes if the cassette tapes in the
system become damaged.
The following procedure can be used to make a backup tape:
1. Remove the cassette tape from the tape drive.
2. Insert the backup cassette tape into the tape drive.
3. Login to the terminal.
4. Verify that the screen displays:
enter command:
5. Enter save translation and press [RETURN]. This command instructs the system to
take all translation information in memory and write it onto the cassette tape.
6. The screen displays:
save translationSPE A
SAVE TRANSLATION
ProcessorCommand Completion StatusError Code
SPE_A
Success0
Command successfully completely
enter command:
FIGURE 7-1. Save Translation—SPEA
7. Verify that a 
0 is displayed in the Error Code column. A 0 indicates that the save
translation was successfully completed for the tape drive. If a 
0 did not appear, the
save translation did not complete. Record the “error code number” and the “error mes-
sage” and notify maintenance support.
8. if the system is equipped with a TN750 Announcement circuit pack, the recorded
announcements can be saved using the save announcement commands. Enter save
announcements and press [RETURN].
7-2 
						

							CHAPTER 7. SYSTEM BACKUP FOR DEFINITY G1 AND G3i
9. The screen displays:
save announcement
SPE A
SAVE ANNOUNCEMENT
Processor
Command Completion StatusError Code
SPE_ASuccess
0
Command successfully completely
enter command:
FIGURE 7-2. Save Announcements Screen—SPEA
10. Verify that a 0 is displayed for SPE_A in the Error Code column. A 0 indicates that
the save announcement was a success for the tape drive. If a 0 did not appear, the
save announcement did not complete. Record the “error code number” and the “error
message” and notify maintenance support.
11. Remove the backup cassette tape from the tape drive and insert the original cassette
tape into the tape drive.
12. Label the backup cassette tape with the date and time it was updated. A special notation
may be put on the tape to clearly distinguish it from other cassette tapes.
13. Store the backup tape in a secure place.
7-3 
						

							CHAPTER 7. SYSTEM BACKUP FOR DEFINITY G1 AND G3i
Tape Backup for a System With the Duplication Option
Four cassette tapes are provided with the system. It is recommended that backup copies of
the translation data be made weekly, or after many changes have been made to the translation
data. This will minimize the loss of recent translation data changes if the cassette tapes in the
system become damaged.
The following procedure can be used to make backup tapes:
1. Remove the two original cassette tapes from the tape drives.
2. Insert the two backup cassette tapes into the tape drives.
3. Login to the terminal.
4. Verify that the screen displays:
enter command:
5. Enter save translations and press [RETURN]. This command instructs the system to
take all translation information in memory and write it onto the two cassette tapes.
6. The screen displays:
save translation
SAVE
Processor
Command
SPE_B
SPE_A
Command successfully completely
enter command:SPE B
TRANSLATION
Completion Status
Error Code
Success
0
Success0
7.
8.
FIGURE 7-4. Save Translation—SPE_B
Administration Nets:
The active SPEs completion status is always displayed first.During the save trans-
lation, as illustrated in the above screen, SPE_B is displayed as the active SPE in
the upper right corner of the screen.
Verify that a 0 is displayed for SPE_B and SPE_A in the Error Code column. A 0
indicates that the save translation was a success for each tape drive. If a 0 did not
appear for SPE_B and SPE_A, the save translation did not complete. Record the “error
code number” and the “error message” for the SPE that did not have a 0 and notify
maintenance support.
If the system is equipped with a TN750 Announcement circuit pack the recorded
announcements can be saved using the save announcement commands. Enter save
announcements and press [RETURN].
7-4 
						

							CHAPTER 7. SYSTEM BACKUP FOR DEFINITY G1 AND G3i
9. The screen displays:
save announcementsSPE B
SAVE ANNOUNCEMENT
Processor
Command Completion StatusError Code
SPE_B
Success
0
SPE_A
Success0
Command successfully completely
enter command:
10.
11.
12.
13.
FIGURE 7-4. Save Announcements—SPE_B
Administration Note:
The active SPE’s completion status is always displayed first. During the save
announcement, as illustrated in the above screen, SPE_B is displayed as the active
SPE in the upper right corner of the screen.
Verify that a 0 is displayed for SPE_B and SPE_A in the Error Code column. A 0
indicates that the save announcement was a successfor each tape drive. If a 0 did not
appear for SPE_B and SPE_A, the save announcementdid not complete. Record the
“error code number” and the “error message” for the SPE that did not have a 0 and
notify maintenance support.
Remove the two backup cassette tapes from the tape drives and insert the original two
cassette tapes into the tape drives.
Label the two backup cassette tapes with the date and time they were updated. A special
notation may be put on the tapes to clearly distinguish them from other cassette tapes.
Store the two backup tapes in a secure place.
7-5 
						

							CHAPTER 7. SYSTEM BACKUP FOR DEFINITY G1 AND G3i
Tape Errors
Since the tape drive is a mechanical device, tape-related failures may occur. When these
failures occur, the system responds with “tape error messages”. The following is a list of the
tape error messages and recommended responses to each. Check for proper operation after
each response is done.
1.
2.
3.
4.
5.
Tape access error: no tape cartridge or device problem
Indicates that the cassette tape is missing or improperly seated. This error can also occur
if the tape drive has a hardware problem.
Response: Check tape drive for missing or improperly seated cassette tape.
Check cassette tape to determine if write-protect indicator points to SAFE. If so, turn
pointer away from SAFE to allow “write” capability.
Check for alarm at attendant console. If alarm is present, notify maintenance support to
repair tape drive.
WARNING: Cheek for damaged or worn cassette tape. If the cassette tape is
damaged, do not insert the backup tape. If the backup tape is
inserted it may also be destroyed. Notify maintenance support to
repair the tape drive.
Tape currently in use
Indicates that the system is currently
accessing the tape for administration or mainte-
nance purposes.
Response: Wait a few minutes and repeat the command that generated the tape error
message.
Cannot write to tape:cartridgeor device problemor Tape write
failure: cartridge or device failure
Indicates that there was a failure in writing to the tape.
Response: Refer to the procedures in message 1.
Cannot read from tape:cartridge or device problem or Tape write
failure: cartridge or device failure
Indicates that there was a failure reading from the tape.
Response: Refer to the procedures in message 1.
System 1 error or Internal system error
Indicates that the system software requires reset procedures.
Response: Notify maintenancesupport.
7-6 
						

							CHAPTER 7. SYSTEM BACKUP FOR DEFINITY G1 AND G3i
6. Internal translation data is corrupted
Indicates that the translation data is inconsistent and the translation was not saved on
tape.
Response: Replace cassette tape with system backup tape.
Enter the command reset system 3. After the command completes, remove the backup
tape, install the original tape, and then repeat the command that generated the error
message. Notify maintenance support if the same error message is displayed again.
7. 
Translation file is too large to fit on tape
Indicates that the system software has malfunctioned.
Response: Notify maintenance support.
7-7 
						

							CHAPTER 8. SYSTEM BACKUP FOR DEFINITY G3r
CHAPTER 8. SYSTEM BACKUP FOR DEFINITY G3r
Overview
The DEFINITY G3r Mass Storage System (MSS) utilizes tape and disk to provide stable storage
of switch data. MSS configurations include single Switch Processing Element (SPE) and dupli-
cated systems. There are four basic MSS configurations:
Simplex Tape-Only
In a simplex tape-only system, the tape drive 
is the primary MSS device.
In this configuration, there is no alternate means to boot the system or
save system data if the tape drive fails.
Simplex Disk/TapeIn a simplex disk-tape system, the disk drive is the primary MSS device
and the tape is the secondary MSS device. If the disk is not available,
the tape is available to boot from or to save system data. The tape unit
is normally a backup of the disk In addition, a tape provides a remov-
able backup of the system data.
Duplex Tape-OnlyIn a duplicated processor system, MSS is provided for each processor.
Each processor boots from its local tape unit only. Translation data and
the integrated announcement board data can be backed up from
memory to the local tape unit, the standby tape unit, or both tape units.
Normally, when data is written, both the active and standby tape units
are updated simultaneously.
In addition, scheduled maintenance is provided to verify that the file sys-
tems on each storage device are consistent and that the files are con-
sistent between the different storage devices.
Duplex Disk/TapeIn a duplicated processor system, each processor normally boots from
its local disk unit only. Data is backed up from memory to the local disk,
the local tape unit, the standby disk unit, the standby tape unit, both disk
units, or both tape units. Normally, when data is written, both the active
and standby disk units are updated simultaneously.
Backup from disk to tape can occur on the active system, the standby
system, or on both simultaneously. Restore from tape to disk can occur
on the active system, the standby system, or on both simultaneously.
The primary backup operations are:
lSave translation: All translation data is kept in memory during system operation. This
means that all data would be lost if the switch went down. The save translation operation
allows the System Manager to save the in-memory translation data on disk/tape. This
operation maybe done as part of scheduled maintenance and/or as required.
lBackup/Restore: In a disk/tape configuration, additional data integrity is achievable
through the disk-to-tape backup process. The backup operation can be done as part of
scheduled maintenance and/or as required. The contents of the disk will be copied onto
a tape. This tape backup contains enough formatting/structure to allow the system to
boot from it.
8-1 
						

							CHAPTER 8. SYSTEM BACKUP FOR DEFINITY G3r
Command Interface Conventions
In the following sections, the commands used to interface with the MSS are described. The con-
ventions used to describe the commands are:
Optional Command ArgumentsA set of brackets [ ] is used to designate optional groups of
arguments to a command. One item listed within each set of
brackets can be specified on the command line.
Error Conditions
Following the descriptions of the command operations is a list
of error conditions which may occur before or during command
execution. Within the command descriptions, error condition
notations may appear (E#, where # corresponds to the error
condition number). Refer to the “Error Conditions” section of
this chapter for explanations of the specific error conditions.
Save Announcement Command
The save announcements operation copies announcement data from the announcement board
(TN750) to the MSS. By default, announcement 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 announcements command can be directed to write to devices on either of the
processors and/or to the secondary device(s).
Command Syntax
save announcements [active | standby | PE-A | PE-B | both | either] [disk | tape]
The bracketed options specify to which mass storage system the announcements are saved.
This set of options only applies in a duplicated system. The options, 
active and standby, refer to
the currently active and standby proccessors,
respectively, in a duplicated system. The options,
PE-A and PE-B, refer to the processors in carriers
A and B, respectively, in a duplicated system.
Invoking the 
save accouncements command with the active option forces the system to write
the announcements data to the specified device in the currently active processor. In a simplex
system, active is the same as PE-A and is the default.
Invoking the 
save announcements command with the standby option forces the system to write
the announcements data to the specified device in the standby processor.
Invoking the 
save announcements command with the PE-A option forces the system to write
the announcements data to the specified device in processor A. PE-A is the default in a simplex
system.
Invoking the 
save announcements command with the PE-B option forces the system to write
the announcements data to the specified device in processor B.
8-2Invoking the 
save announcements command with the both option forces the system to write the
announcements data to the specific device in both mass storage systems concurrently. If either
access fails, the entire operation fails. In a duplex system, both is the default. 
						

							CHAPTER 8. SYSTEM BACKUP FOR DEFINITY G3r
Invoking the save announcements command with the either option forces the system to write
the announcements data to the specified device in both mass storage systems concurrently. If
there is a failure in accessing one of the devices, the announcements data will still be written to
the device that has not failed.
The 
[disk | tape] options specify the device on which to save the announcements data. These
options only apply in a system with a disk.
Invoking the 
save announcements command with the disk option forces the system to write the
announcements data to the disk. In a system configured with both a disk and a tape, 
disk is the
default.
Invoking the 
save announcements command with the tape option forces the system to write the
announcements data to the tape. In a system configured with only a tape unit, 
tape is the
default.
Command Operation
The save announcement command will only be allowed if there is an integrated announcement
board in the system (E28).
The save announcement 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 port is out of service (E34).
l The announcement data module port is active (e.g., performing an announcement play-
back) (E36).
l No announcements are on the ANN board (E33).
l A user is in an integrated announcements session
(E31).
l The board is currently being uploaded or downloaded (E29).
A user cannot enter an integrated announcement session after the 
save announ-
ments command has started, although 15 channels are still available for announcement
playback (one is reserved for uploading and downloading).
If saving to tape, the 
save announcements command will abort if:
l The tape is not in the tape drive (E37) or the tape is write-protected (E38).
l No system access port is available (E39).
l The MSS is in use by the SPE duplication memory refresh activity (E41).
In addition, the save announcements command will not be allowed if the MSS is in use. The
MSS maybe in use by either another user (E3) or by maintenance (E42).
Options entered by the user are validated against the system configuration and the target devices
for the save announcement command are determined (E11, E12).
If the user requests that announcements be saved to a disk the disk must be in service (E13).
8-3 
						

							CHAPTER 8. SYSTEM BACKUP FOR DEFINITY G3r
If the user requests that announcements be saved to a tape, the tape must be in service (E14).
If the user requests that announcements be saved to the standby processor, the standby proces-
sor must be in service and shadowing must be enabled (E16).
If an error is encountered in the above steps, the save operation is not attempted.
When MSS devices on both processors in a duplicated system are specified, the save announce-
ments operation will save announcement data from the announcement board 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.
The goal is to save the new announcement data on some MSS device so that it is not totally lost;
this will cause the announcement data to be inconsistent between these MSS devices.
The command completion status is displayed on the system administration terminal. The screen
will be identical to that shown in Figure 5-1, except it will be entitled “Save Announcement.” The
displayed information includes a success or error message for each processor.
In case of a failure, it is the users responsibility to make the announcement
files on the two MSS
devices consistent. The files may become inconsistent due to hardwarefailures or if “save” to
one device fails while the other continues; for example, while using the 
either option.
If announcement files are inconsistent due to failure on the hardware used during the 
save
announcements 
command, the user should take appropriate action based on the error message
returned. Maintenance software monitoring this hardwarewill log a hardware error with mainte-
nance. Maintenance software will invoke tests to diagnose and attempt to correct the problem. If
maintenance software fails to correct the problem, an alarm would be raised and the system
technician should take appropriate action.
The save announcements command writes two time-stamped identical copies of announcement
data to the selected device(s). The time stamp for both copies will be the same (it will be the
time of writing to the first copy). Each copy is written as consecutive 2K Blocks. Each block con-
tains a checksum for error detection purpose. Each copy contains the following status informa-
tion: time stamp, and the state of the copy (i.e., “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 only updates one of the copies at a time. The save operation
will always choose to overwrite the “least good” copy first. The following selection criteria is
applied separately on the active and standby devices:
l If a copy has a bad status, then always overwrite that copy first.
l If both copies have good status, then overwrite the one with the older time stamp. If both
time stamps are the same, then it doesn’t matter which copy is overwritten first since
both copies are identical.
Each copy of the announcement data is marked “bad” prior to an announcement 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, should only affect one copy of
announcement data. In that case, the affected copy will be marked with a “bad” status indicator
and will not be used to restore announcements into the system. Thus, an intact copy of
announcement data can be used as a backup. Normally at least one of the two copies should be
in a good state.
8-4