Backup

Jake Forster Updated by Jake Forster

Backup Client Database and Data Files

This utility allows the user to make a backup copy of the client database containing the client names and addresses, and a copy of the client data files that are stored in each client's data subdirectory.

The source of the backup is always the current data path as set on the Configuration Options screen.

The user must first select the destination drive and directory for the backup copy. It can be the root directory or subdirectory of a floppy disk, local hard disk, or network drive. The destination directory can contain a previous backup or it must be empty. No other files are allowed. The backup can span multiple floppy disks (do not use a subdirectory on the floppy in this case). After changing the destination by clicking the drive and directory lists, the NEXT button will become enabled and the color of the destination path will change from red to blue when a valid selection has been made.

When a valid destination is selected, click the NEXT button. A list of clients will appear. Select the clients to backup (including <Quick Access>) from the list by clicking on the client name. To select a group of clients that are next to each other, select the first client; then, while holding down the SHIFT key, select the last client. To select multiple clients that are not next to each other, hold the CTRL key down while selecting clients.

When finished click FINISH. The count of files and bytes in the data files will be presented. Select OK to start the backup.

FILES BACKED-UP: The selected clients are backed up to a database file in the destination directory. The client data files are backed up to client subdirectories off of the destination directory. This is the same file structure used by the program during operation. If desired the backup could be used as the data set during program operation (providing it does not span multiple floppies).

Auxiliary data files residing in the \INIS subdirectory off of the program directory are also backed-up to a \INIS subdirectory off of the destination directory. These files include saved data from certain modules that is common to all users, such as preparer database and custom labels.

How did we do?

Backup Considerations

Contact