Audit Mirroring Properties Dialog Box

Getting there

In the right pane of the Databridge Enterprise window, right-click a base source and click Properties.
In the Base Source Properties dialog box, click [Audit Mirror].

The options are as follows:

Mirroring parent directory (enables audit file mirroring)	Target directory for mirrored Audit Files An audit file is created by DMSII and contains the raw format of changes made to the DMSII database by update programs. Audit file records contain the deletes, adds, and modifies that were made to the various structures. It can contain, for example, hours', days', or weeks' worth of information. An audit file is created by the DMSII Accessroutines and contains the raw format of changes made to the DMSII database by update programs. Audit file records contain the deletes, creates, and modifies that were made to the various structures. Depending on the frequency of changes made to a database, the information in an audit file can span a few hours or several weeks. If you set the DBEngine Read Active Audit option, Databridge can access the current audit file. If you do not set Read Active Audit = true in the DBEngine parameter file, Databridge can access audit information up to and including the current audit file minus one. The audit file contains the update level at the time the audit file was created. The update level in the audit file and the update level in the DESCRIPTION file used by Databridge must match before Databridge will update a replicated database. When an audit file is closed, DMSII creates the next one in the series. Audit files are closed for several reasons, including the following: An operator closes the audit file with the mixnumber SM AUDIT CLOSE command. The audit file reaches the file size set in its DASDL. There is an I/O error on the audit file. There is not enough disk space for this audit file. The database update level changes due to database definition changes A Databridge accessory closed the file in preparation for the fixup phase after extracting records from a DMSII database. The current audit file could not be found. A file reorganization was executed to modify the DMSII structure. . This can be a local path, or a network path described in UNC format. (For example: \\server\share\directory.) The mirrored audit files will be stored in the sourcename subdirectory of the parent directory specified here. For example, if the source is named BANKDB and the parent directory is D:\Databridge\Mirror, then the mirrored audit files will be stored in the D:\Databridge\Mirror\BANKDB subdirectory. Placing the mirrored audit files near the secondary system rather than on a local drive of the Enterprise Server computer is strongly recommended. That way, if the network connection fails between the Enterprise Server computer and the DBAuditMirror computer, DBAuditMirror can continue mirroring all available audit files.
Read mirrored files as user	Enter the Windows account and password that Enterprise Server will use when running the batch file, reading mirrored audit files, and so on.
Password	Enter the password for the Windows account specified in the previous box.
After mirroring an audit file to the secondary host, run	Optionally, you may specify a batch file or application to run after mirroring each audit file to the secondary MCP system. This batch file might remove the mirrored file from the audit mirroring directory. Enterprise Server includes a sample file FinishMirrored.cmd in the Enterprise Server directory that removes the mirrored file after it is mirrored to the secondary system (using DBAuditMirror). This file contains information about parameters available to any batch file specified in this option.
Wait for audit to mirror	From the menu, specify the wait and retry rules that Enterprise Server follows when mirroring. If you select Wait forever, set a value for Seconds between retries. If you select Wait max seconds, set values for Max seconds and Seconds between retries.