The data area can be restored in two ways. Normally you use the :FILELOAD command in the SYSPROG account to restore the entire data area from a filesave tape. But there are times, particularly after a system failure, when it is not possible to access the SYSPROG account.
In such cases you can restore the data area as part of a system restart process. From the mvBase Administration Utility:
Select the correct Boot Tape.
Turn the Fileload checkbox ON.
The :FILELOAD Procedure
Use the following procedure from TCL to restore the data area using a filesave backup medium.
Log on to the SYSPROG account.
If you are at the TCL prompt, type:
LOGTO SYSPROG |
If you are at the Logon Please prompt, type:
SYSPROG |
At the PASSWORD prompt, enter the password to the SYSPROG account.
Ensure that all users have logged off the system, then use the MAXUSERS command to set to 1 the number of users who can log on. This prevents users from logging on while the restoration is in process.
T-SELECT the appropriate drive and press ENTER.
To access a virtual tape file, perform a SET-TAPEFILE if the correct file is not already assigned to the selected LTU.
To restore the data area from a virtual tape file, use SET-TAPEFILE to map the virtual tape file containing the filesave to the selected logical tape unit, if the correct file is not already assigned.
To use a physical tape, insert the filesave tape.
Type T-ONLINE and press ENTER again.
At the TCL prompt, type:
:FILELOAD |
This message displays:
SPOOLER STARTED |
The name of each file displays as it is restored. If the filesave comprises multiple tapes, you are prompted to load the next tape when all files on the previous one have been restored. When all files on all tapes have been restored, this message displays:
Restore updates (Y/N)? |
Type N. (You would only type Y if you had an incremental save tape to restore.)
The COLD-START Proc is automatically run. Messages such as the following appear:
THIS IS THE COLD-START PROCEDURE COUNT SYSTEM ERRORS [401] NO ITEMS PRESENT |
The system then verifies itself. If no frame mismatches are detected, the following message displays:
[341] OPERATING SYSTEM SOFTWARE VERIFIED |
If any frame mismatches are detected, a message such as the following appears:
214 92AD 9CDE 489 C317 3746 [342] *** THE SYSTEM SOFTWARE DOES NOT VERIFY! *** THERE ARE 2 FRAMES WITH MISMATCHES |
Write down all the numbers, then inform your system supplier.
When the COLD-START Proc has finished running, it logs itself off, and the logon prompt appears. The system is now up and running.
Unload the tape from the drive. Be sure to reset the maximum number of users who may log on (MAXUSERS).
Full File-restore When Starting the mvBase Server
To perform a full file-restore when starting the mvBase Server, follow these instructions:
Switch to the mvBase Administration Utility.
Turn the Fileload checkbox ON.
If the filesave was made to a physical disk or a virtual tape file added through the mvBASE Administration Utility, select it as the Boot Tape device now.
If the filesave was made to a virtual tape file created at TCL, add this tape file now.
Select the Server tab; select Configure, Tapes, Add Tape File.
Enter the full path of the virtual tape file containing the filesave and select OK. Return to the Server tab.
Select this tape as the Boot Tape device.
Turn the AUTOBOOT flag off.
Start the Server as an application. The following messages appear when mvTerm opens:
SPOOLER STARTED Insert FILESAVE Media and press RETURN (or R to inhibit reallocation) |
Press ENTER. The names of the files appear as each is loaded.
At the Restore updates (Y/N)? prompt, type N.
See Also