Scaling Up Oracle DBSecCentral Instances

Learn to scale up Oracle DBSecCentral instances on OCI.

CPU, memory, network bandwidth, and repository storage of Oracle DBSecCentral instance can be scaled up without recreating the instance. This allows for increased performance to meet growing workload needs.

Changing the Shape of Oracle DBSecCentral Instance

CPU, memory, and network bandwidth can be scaled up by changing the shape of the instance to one of the supported VM standard shapes.

Use the OCI console to edit the shape of the instance. Refer to Using the Console for more details.

Note: Changing a shape to a smaller one than the current shape is not supported. For example, changing the shape from VM.Standard2.4 to VM.Standard2.2 is not supported.

Expanding Repository Storage for Audit Vault Server

Each Audit Vault Server instance has a repository that stores the collected audit and network event data. The storage requirements increase as the collection workload grows. To meet the storage needs, expand the Audit Vault Server repository storage in the following ways:

• During Instance creation: When specifying the boot volume larger than the default for Audit Vault Server instance, the underlying repository storage is automatically expanded. Refer to section Creating an Oracle DBSecCentral instance with Oracle Cloud Marketplace Image on how to specify custom boot volume size.

• Post instance creation: Follow these steps:

  1. Attach additional OCI Block storage to the instance. Follow the steps listed in Attaching the Volume to an Instance.

  2. Ensure the disks are visible at the OS level, by running the following command:

     lsblk

  3. Expand the repository storage. See Adding Local Disks to the Audit Vault Server ASM Disk Groups.

Note:

• Ensure the attached OCI Block storage is not shared with any other instance as it may lead to data loss.

• SAN storage is not supported.