Audit Mirroring Properties Dialog Box

Getting there

The options are as follows:

Mirroring parent directory (enables audit file mirroring)

Target directory for mirrored audit files. 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.


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.