4.3 Secondary Storage Configuration

Perform the following steps to configure the secondary storage so that Change Guardian can migrate event partitions to a less-expensive storage:

NOTE:This process is optional and the secondary storage does not need to be high-availability in the same way that you configured the rest of the system. You can use any directory, mounted from a SAN or not, NFS, or CIFS volume.

  1. Log in to the Change Guardian web console.

  2. Navigate to Administration > Storage > Events.

  3. Under Secondary storage not configured, select one of the secondary storage location.

Use a simple iSCSI Target as a network shared storage location, with the same configuration as the primary storage. In your production environment, the storage technologies might differ.

Use the following procedure to configure the secondary storage for use by Change Guardian:

  1. Review the steps above to determine which partition was created for use as secondary storage (/dev/<NETWORK1>, or something like /dev/sdc1). If necessary create an empty directory on which the partition can be mounted (such as /var/opt/netdata).

  2. Set up the network filesystem as a cluster resource: use the Sentinel interface or run the command:

    crm configure primitive sentinelnetfs ocf:heartbeat:Filesystem params device="/dev/<NETWORK1>" directory="<PATH>" fstype="ext3" op monitor interval=60s

    where /dev/<NETWORK1> is the partition that was created in the Shared Storage Setup section above, and <PATH> is any local directory on which it can be mounted.

  3. Add the new resource to the group of managed resources, using the following commands:

    crm resource stop sentinelgrpcrm configure delete sentinelgrpcrm configure group sentinelgrp sentinelip sentinelfs sentinelnetfs sentineldb sentinelservercrm resource start sentinelgrp

  4. You can connect to the node currently hosting the resources (use crm statusor Hawk) and make sure that the secondary storage is properly mounted (use the mount command).

  5. Log in to the Change Guardian web console.

  6. Navigate to Administration > Storage > Events and then select the SAN (locally mounted) under Secondary storage not configured.

  7. Type in the path where the secondary storage is mounted, for example /var/opt/netdata.

    Use simple versions of the required resources, such as the simple Filesystem Resource Agent. If required, you can choose to use sophisticated cluster resources like cLVM (a logical-volume version of the Filesystem).