To fully back up the mvBase system, use the FILE-SAVE Proc to save all the data files on the system. All users should be logged off during the execution of this Proc in order to prevent the database from being updated during the filesave.
All backups are governed by sets of Group Update Flags. A Group Update Flag is automatically set for a group whenever data in that group is added to or modified in any way.
Each time a full backup is done, all groups are saved regardless of the state of the Group Update Flags, and all Group Update Flags are cleared. Clearing the Group Update Flags starts a new incremental cycle.
Incremental backups, on the other hand, save only those groups whose Group Update Flags are set, ensuring that only updated groups are saved.
Incremental backups do not clear any Group Update Flags; thus, subsequent incremental backups save the same updated groups again, as well as any other groups whose flags have been newly set.
Backing Up the Data Area (Full Filesave)
The following procedure describes how to use the FILE-SAVE Proc, which is the usual and recommended method for backing up all the data files on the system.
FILE-SAVE stores a formatted copy of the entire data area. Data files are stored one after another on the backup medium, allowing the operator to locate any particular account, file, or items within a file. Thus, it is possible to selectively restore an account, a file, or selected items from a filesave tape.
Never skip a FILE-SAVE due to lack of time. It is true that formatted FILE-SAVEs, especially with larger- capacity disks, can take a significant amount of time, but having recent backup data is essential for recovering from any event that corrupts the database. mvBase has the ability to start a FILE-SAVE at a user-specified time of the day or night (i.e., during nonpeak-usage hours). In fact, most installations start a FILE-SAVE at the end of the work day.
If performing a backup to physical tape, load a backup medium in the tape drive. Be sure it is write-enabled.
T-SELECT the appropriate logical tape unit and press ENTER.
If performing a backup to a virtual tape file, perform a SET-TAPEFILE if the virtual tape file is not already mapped to the selected logical tape unit.
Type T-ONLINE and press ENTER again.
Ensure that all users are logged off, then use the MAXUSERS command to set the number of users who can log on to 1. This prevents users from logging on while the filesave is in process.
On the system console, log on to the FILE-SAVE account by typing the following at the TCL prompt:
LOGTO FILE-SAVE |
If the PASSWORD prompt appears, enter the password. It will not appear on the screen. Messages similar to the following display:
Connect Time= n mins.; CPU= nn UNITS; LPTR pages= n BLOCK SIZE: nnnnn [6070] VIRTUAL TAPE UNIT SET TO: C:\FSAVE.VTF BLOCK SIZE: nnnnn [6004] TAPE ON LINE BLOCK SIZE: nnnnn
FILE SAVE BEGINNING AT hh:mm:ss dd mmm yyyy CONSOLE LISTING TO PRINTER? |
Type N for a list of account names and file names to be displayed on the system console as they are saved. Type Y for a printed list. This prompt then displays:
DO YOU WANT A FILE STATISTICS REPORT? |
Type Y to send the File Statistics Report to the printer. For more information, see The File Statistics Report.
Type N if you don’t want to print the report. File statistics are recorded in the STAT-FILE file, which you can list using the LIST-FILE-STATS command. This prompt then displays:
DO YOU WANT TO DO A FILE-SAVE VERIFICATION? |
Type Y to verify the tape or diskette (to ensure it is valid, having no parity or data errors). A list of what was saved displays after the filesave is finished.
Type N if you do not want to verify the filesave tape or diskette.
NOTE |
Rocket highly recommends performing a FILE-SAVE verification. |
The system now checks the backup medium and the disk drive to make sure the recording process is functioning correctly. Messages similar to the following are displayed while the test is run:
FILE SAVE DEVICE AND MEDIA CHECK WRITE 20 RECORDS AND EOF REWIND AND READ 20 RECORDS |
If messages similar to the following appear, either the backup medium is damaged or the disk drive is not working properly:
RECORD nn DOES NOT EQUAL WRITTEN RECORD nnn BYTES OUT OF nnn DO NOT MATCH FIRST BAD BYTE IS AT POSITION nnnn BAD BYTE = xx; WRITTEN BYTE = xx |
Unload the backup medium, reload it, and start the FILE-SAVE Proc over again, beginning at Step 3. If this doesn’t work, try again with a different tape. If it doesn’t work with any tape, call your system supplier. If the filesave works with the second tape, it means the first tape is bad and should be discarded.
If, on the other hand, the test is successful, the following message displays and the filesave begins:
NO ERRORS |
Accounts and files are listed on the screen as they are saved.
If the system reaches the end of the tape before the filesave is finished, a prompt similar to the following displays:
LOAD REEL # 02 ON LTU# 01 LABEL 01 DD mmm yyyy filename # |
Load the next tape, then type C to continue. The filesave continues.
If you requested a filesave verification in Step 10, these messages display:
* FILE-SAVE VERIFICATION * MOUNT REEL #1 THEN PRESS <ENTER>> |
Reload the first reel of the filesave tapes and press ENTER. All accounts and files present on the filesave tape are listed on the screen.
Repeat this step for the remaining tapes in the filesave, unload the previous tape and load the next tape until all of the remaining tapes have been loaded.
When the FILE-SAVE Proc has finished, it logs itself off and the logon prompt displays:
Logon Please: |
Unload the tape from the tape drive, logon and reset the maximum number of users who may log on (MAXUSERS). The system is now ready for use.
See Also