Adding Local Disks to the Audit Vault Server ASM Disk Groups

To increase storage, you can add local disks to the Oracle Automatic Storage Management (ASM) disk groups for the Audit Vault Server.

This procedure discusses how to add storage to all three ASM disk groups. However, it may not be necessary to increase the storage for all three. Use your discretion to add storage where it’s needed.

Note: For Oracle DBSecCentral installations that are hosted on VMware, don’t extend the current virtual disk. Instead, add a new virtual disk device.

Prerequisite

Ensure that any disks that you added to the Oracle DBSecCentral appliance have no preexisting Local Volume Manager (LVM), partition, or other device mapper metadata. If the disks have been used previously, then restore them to a clean state before completing this procedure.

Procedure

  1. Log in to the Audit Vault Server through SSH and switch to the root user.

    See Logging In to Oracle DBSecCentral Appliances Through SSH.

  2. Run fdisk -l to view a list of all the available hard disks. For example:

    /sbin/fdisk -l 2> /dev/null | more
Disk /dev/sda: 322.1 GB, 322122547200 bytes
255 heads, 63 sectors/track, 39162 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
   Device Boot Start   End    Blocks  Id  System
/dev/sda1    *     1    19    152586  83  Linux
/dev/sda2         20 10727  86012010  8e  Linux LVM
/dev/sda3      10728 22914  97892077+ 83  Linux
/dev/sda4      22915 39162 130512060   5  Extended
/dev/sda5      22915 31037  65247966  83  Linux
/dev/sda6      31038 39162  65264031  83  Linux

Disk /dev/sdb: 107.3 GB, 107374182400 bytes
255 heads, 63 sectors/track, 13054 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

  3. From the list, locate a disk with no partitions defined and with the same size that you need. Ignore any entries referring to /dev/dm-0, and so on.

    In the example in step 2, a SATA disk of 100 GB was added, so the target in that example would be /dev/sdb.

    Note:

    • Fiber Channel-based storage with multipath is supported.

      Here's an example of the multipath device: /dev/mpatha

      To get a list of existing multipath devices, run the multipath -ll command.

    • Fiber Channel over Ethernet (FCoE) is currently not supported by Oracle Oracle Database Security Central.

  4. Use the parted command to create the partitions.

    1. Run parted /<path of the disk> using the path of the disk that you identified in step 3. For example:

      /sbin/parted /dev/sdb

GNU Parted 1.8.1
Using /dev/sdb
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted)

      Oracle recommends that all ASM disks in a disk group should be the same size. For example, if the SYSTEMDATA disk group has a 5 GB disk and you want to add another disk, it should also be 5 GB. This is because Oracle ASM stripes the files in the disk group across each disk. If the disks are mismatched in size, the smallest disk limits the size of the whole disk group. After the smallest disk is 100 percent full, you can’t rebalance until space on that disk is freed.

    2. Run mklabel gpt to set the disk label to GPT. For example:

      (parted) mklabel gpt
(parted) print

Model: ATA VBOX HARDDISK (scsi)
Disk /dev/sdb: 107GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number Start End Size File system Name Flags

(parted)

    3. Run the mkpart primary ext3 command to create the partition.

      When prompted, enter 0GB as the start point and specify another size of the first partition as the end point.

      For example, to create three partitions and to use 35GB as the end of partition 1, use the following command:

      (parted) mkpart primary ext3
Start? 0GB
End? 35GB
(parted)

    4. Run the mkpart command to create the second partition. For example:

      (parted) mkpart primary ext3
Start? 35GB
End? 70GB
(parted)

    5. Run the mkpart command to create the third partition. For example:

      (parted) mkpart primary ext3
Start? 70GB
End? 107GB
(parted) print

      The end point GB should match the total GB for the disk that appears in the output of step 4b.

    6. Run quit to exit parted. The changes are automatically saved.

  5. Run oracleasm createdisk to create the ASM disks. For example:

    /usr/sbin/oracleasm createdisk -v EVENTDATA2 /dev/sdb1
Disk "EVENTDATA2" does not exist or is not instantiated
Writing disk header: done
Instantiating disk: done

    Note: If this command fails, then remove all the data and partitions from the new disk and repeat all the preceding steps.

  6. Add the new disks to the existing ASM disk groups.

    1. Run the following commands to change to the grid user and connect to the grid instance as sysasm to manage the existing ASM disk groups:

      su - grid
      id
      sqlplus /nolog
      sqlplus / as sysasm

    2. Check the current status of the existing ASM disks and disk groups.

      select GROUP_NUMBER,NAME,TOTAL_MB,FREE_MB from V$ASM_DISKGROUP;

      For example:

      GROUP_NUMBER NAME        TOTAL_MB FREE_MB

------------ ----        -------- -------
1            EVENTDATA   63718    62557
2            RECOVERY    95597    91924
3            SYSTEMDATA  63734    60577
      column MOUNT_STATUS format a12
column HEADER_STATUS format a12
column MODE_STATUS format a10
column STATE format a10
column TOTAL_MB format 999999
column FREE_MB format 999999
column NAME format a20
column PATH format a40
column LABEL format a10
column LABEL format a1
set linesize 250

SELECT MOUNT_STATUS,HEADER_STATUS,MODE_STATUS,STATE,TOTAL_MB,FREE_MB,NAME,PATH,LABEL FROM V$ASM_DISK;

      For example:

      MOUNT_STAT HEADER_STATUS  MODE_STATUS   STATE   TOTAL_MB FREE_MB  NAME             PATH                             LABEL

---------- -------------  -----------   -----   -------- -------  ----             ----                             -----
CLOSED     PROVISIONED    ONLINE        NORMAL  0        0                         /dev/oracleasm/disks/RECOVERY2
CLOSED     PROVISIONED    ONLINE        NORMAL  0        0                         /dev/oracleasm/disks/SYSTEMDATA2
CLOSED     PROVISIONED    ONLINE        NORMAL  0        0                         /dev/oracleasm/disks/EVENTDATA2
CACHED     MEMBER         ONLINE        NORMAL  63734    60577    SYSTEMDATA_0000  /dev/oracleasm/disks/SYSTEMDATA1
CACHED     MEMBER         ONLINE        NORMAL  63718    62557    EVENTDATA_0000   /dev/oracleasm/disks/EVENTDATA1
CACHED     MEMBER         ONLINE        NORMAL  95597    91924    RECOVERY_0000    /dev/oracleasm/disks/RECOVERY1
6 rows selected.

    3. Use ALTER DISKGROUP to add the new disks to the disk groups. For example:

      SQL> ALTER DISKGROUP EVENTDATA add disk 'ORCL:EVENTDATA2';
Diskgroup altered.

    4. Verify the increase in storage space. For example:

      SQL> select GROUP_NUMBER,NAME,TOTAL_MB,FREE_MB from V$ASM_DISKGROUP;

GROUP_NUMBER NAME       TOTAL_MB FREE_MB

------------ ----       -------- -------
1            EVENTDATA  97096    95933
2            RECOVERY   131239   127564
3            SYSTEMDATA 97112    93953

Related Topics