Backing Up Your Database

To make a backup copy of your database, use the COPYAUDIT and DMUTILITY programs. The COPYAUDIT program copies Audit files that are named as database/ AUDITnnnn where database is the name of your database, and nnnn is a 1-, 2-, 3-, or 4-digit number.

If you select an option other than None in the Copy Audit to Tape segment configuration property for your application, COPYAUDIT is automatically run when an Audit file is released.

If not, you might still run COPYAUDIT as follows:

From the MARC Home menu, choose TOOLS.
From the TOOLS menu, select OCM (Database Operations Control Manager).
From the OCM menu, select CVAUDIT (Copy/Verify Audit Files).
Enter your parameters and selections, and transmit.
Enter QUIT in the Action line when finished.

The SYSTEM/DMUTILITY program copies the Database data files; that is, all files prefixed with database/ (except the Audit files mentioned above). Enter:

RUN *SYSTEM/DMUTILITY ("DB = database OFFLINE DUMP = TO tape ")

You must use the WFL COPY statement to copy the following database files to tape:

DMSUPPORT/database
DESCRIPTION/database
RECONSTRUCT/database
<system name>/=
	*<usercode>/<system name>/COMS/CONFIG/=

<system name>/= includes all the runtime and deployment information, including the <system name>/SOURCE/DMS file. For example, memdb files for BLD and Appl_Bld.

It is recommended that users manually load the <system name>/COMS/CONFIG/FULL file after a restoration to ensure that COMS entities for the system are correctly configured.

Refer to the Enterprise Database Server for ClearPath MCP Utilities Operations Guide for more information on how to use these programs. The following files, for which a backup copy is also necessary, should be copied (using WFL COPY) from the Object and Dictionary packs each time they are built:

All programs, after each generation:
```
system/= 
DESCRIPTION/database
```
Note: If the system value is the same as database, then any database files resident on the designated Object pack is also copied (even if the database is open). The database should always be closed for this type of copy.
The COMS Configuration file, on a regular basis.

To copy DMS II database files, use the SYSTEM/COPYAUDIT and SYSTEM/DMUTILITY programs. Refer to COPYAUDIT for more information. Refer to the Enterprise Database Server for ClearPath MCP Utilities Operations Guide for more information on DMUTILITY operation.

Caution
Do NOT use the WFL COPY statement to copy DMS II database files, because this does not check the integrity of the files.

When Logging is set, you might also copy the log files, which are named as follows.

        system/LINCLOG/nnn

The nnn value is the number of the current log (001 through 998).

A WFL job named system/LOGBACKUP is started when each log file is closed, if such a job exists on the Object pack for that application. It is your responsibility to create a job for each application. However, a sample job is supplied in the file NGEN28SYS/ LOGBACKUP, which is used by your Agile Business Suite Software itself.

This job allows you to control what happens to each log file as it is closed. For example, it might be written directly to tape.

Your LOGBACKUP job should be on the Object pack for the application it applies to.