Configuring a SAN Repository

Learn how to configure, discover targets, and add and drop disks for an OOracle Database Security Central storage area network.

About Configuring a SAN Repository

You can configure an Oracle Audit Vault storage area network (SAN) for event data, system data, recovery data, and for high availability.

You can use storage area networks (SANs) to expand your data storage, and manage high availability.

Types of Data Supported for SANs

You have the option to configure a SAN storage repository for these data types:

• Event Data - Data that is kept online in the Oracle Audit Vault Server for a specified duration according to archiving policies. After the online duration expires, this data is then archived.

• System Data - Data specific to the Oracle Database Security Central system

• Recovery - Recovery data for the Oracle Audit Vault Server repository

During the Oracle Audit Vault Server installation process, your server is partitioned to store Event, System, and Recovery data in a way that works with the number of disk partitions you have set up on the server. Optionally, you can register SAN servers and configure your storage repository to use additional disks to store this data.

About Configuring a SAN Repository When Federal Information Processing Standards (FIPS) is Enabled on the Audit Vault Server

Challenge-Handshake Authentication Protocol (CHAP) should be disabled on the SAN server when FIPS is enabled.

About Configuring a SAN Repository in High Availability Environments

In a high availability environment, you can configure the storage repository on the secondary Oracle Audit Vault Server from the primary Oracle Audit Vault Server, using either the console UI or AVCLI commands. The primary and secondary Oracle Audit Vault Servers must not share (read or write to) the same SAN disks, and you must ensure that the secondary server has at least the same amount of space in each disk group as the primary server.