Managing Storage Volumes

The solacectl command-line utility is used to manage the storage volumes used by machine and cloud images of the Solace PubSub+ software event broker. The utility can assign storage volumes to external block devices or move them back to the Linux host.

Prior to using the solacectl storage command discussed below, it's recommended that you review the Storage Configuration section on planning considerations related to storage volumes.

Setting Up Volumes as New Block Devices

To set up a storage volume that the Solace PubSub+ application uses as a new block device, enter the following commands from the Linux Host shell as root:

solacectl service stop
solacectl storage configure [-n] [-p] <device> <volumes>

Where:

-p (or --partition) the partition to setup if there are more than one. Normally, this option is not needed.

-n or --new specifies to setup a volume as a new block device. This is the default option and is used unless another option is specifically provided.

device is the destination device on which to store the volumes.

volumes is a space-separated list of volume names.

By default, the solacectl storage configure command preserves the files on the storage volume when migrating to a new block device.

:  To review the list of available block devices and volumes, run the solacectl storage ls command, then check the block devices and storage volumes columns in the output.

Setting Up Volumes as Existing Block Devices

To set up a storage volume that the Solace PubSub+ application uses as an existing block device, enter the following commands from the Linux Host shell as root:

solacectl service stop
solacectl storage configure [-p] -e <device> <volumes>

Where:

-p (or --partition) the partition to setup if there are more than one. Normally this option is not needed.

-e (or --existing) specifies to setup a volume as an existing software event broker block device.

device is the destination device on which to store the volumes.

volumes is a space-separated list of volume names.

:  To review the list of available block devices and volumes, run the solacectl storage ls command, then check the block devices and storage volumes columns in the output.

Formatting Block Devices

To format a block device by erasing partition tables and data, enter the following commands from the Linux Host shell as root:

solacectl service stop
solacectl storage configure [-p] -f <device> <volumes>

Where:

-p (or --partition) the partition to setup if there are more than one. Normally this option is not needed.

-f (or --format) specifies to format a block device by erasing partition tables and data.

device is the destination device on which volumes are stored.

volumes is a space separated list of volume names.

:  To review the list of available block devices and volumes, run the solacectl storage ls command, then check the block devices and storage volumes columns in the output.

Migrating Storage-Elements to External Storage

The procedures shown in this section provide instructions for how to migrate storage-elements to external storage for these configurations:

Before you begin

  • The procedures make use of the solacectl storage command discussed in the previous sections. If you aren't familiar with the command, it's recommended to review those sections shown above.
  • It's recommended that you review the Storage Configuration section on planning considerations related to storage volumes.

Stand Alone Event Brokers

Prerequisites

  • You have planned your storage strategy. Consult the Storage Configuration section if you need more information.

Steps

  1. Log into the event broker's host shell as sysadmin.
  2. Ensure the persistent storage is sized correctly to support the volumes being moved.
  3. Switch to the root user.
  4. Stop the solace service using solacectl service.
  5. Migrate the storage-elements to external storage using solacectl storage.
  6. Verify the storage-elements have been moved to external storage.
  7. Re-start the solace service using solacectl service.
  8. Log out of the event broker.

Event Brokers in an HA Group

Prerequisites

  • You have planned your storage strategy. Consult the Storage Configuration section if you need more information.
  • Before beginning the migration you need to ensure the event brokers in the HA group are in the correct state:
    1. Log into each event broker as an admin user.
    2. On the primary event broker, you should verify that:
      • Configuration Status is Enabled.
      • Redundancy Status is Up.
      • Message Spool Status is AD-Active.

      You can use the show redundancy CLI command to make the verification.

    3. On the backup event broker, you should verify that:
      • Configuration Status is Enabled.
      • Redundancy Status is Up.
      • Message Spool Status is AD-Standby.

      You can use the show redundancy CLI command to make the verification.

    4. Log out of all event brokers.

Steps

  1. On the backup event broker migrate the storage-elements to external storage.
    1. Log into the backup event broker's host shell as sysadmin.
    2. Ensure the persistent storage is sized correctly to support the volumes being migrated.
    3. Switch to the root user.
    4. Stop the solace service using solacectl service.
    5. Migrate the storage-elements to external storage using solacectl storage.
    6. Verify the storage-elements have been moved to external storage.
    7. Re-start the solace service using solacectl service.
    8. Log out of the backup event broker's host shell.
  2. Release activity on the primary event broker.
    1. Log into each event broker as an admin user
    2. Verify that Redundancy Status is Up on both the primary and backup event brokers. You can use the show redundancy command to do this as was illustrated in Prerequisites.
    3. Release activity on the primary event broker.
    4. Verify that the Message Spool Status on the backup event broker is AD-Active.
    5. Log out of all event brokers.
  3. On the primary event broker migrate the storage-elements to external storage.
    1. Log into the primary event broker's host shell as sysadmin.
    2. Ensure the persistent storage is sized correctly to support the volumes being migrated.
    3. Switch to the root user.
    4. Stop the solace service using solacectl service.
    5. Migrate the storage-elements to external storage using solacectl storage.
    6. Verify the storage-elements have been moved to external storage.
    7. Re-start the solace service using solacectl service.
    8. Log out of the primary event broker's host shell.
  4. Revert activity on the backup event broker.
    1. Log into the primary event broker as admin.
    2. No release activity on the primary event broker.
    3. Log out of the primary event broker.
    4. Log into the backup event broker as admin.
    5. Revert activity on the backup event broker.
    6. Verify Redundancy Status is Up on each event broker.
    7. On the primary event broker the Message Spool Status should be AD-Active.

      On the backup event broker the Message Spool Status should be AD-Standby.

    8. Log out of the backup event broker
  5. On the monitoring event broker migrate the storage-elements to external storage.
    1. Log into the monitoring event broker's host shell as sysadmin.
    2. Ensure the persistent storage is sized correctly to support the volumes being migrated.
    3. Switch to the root user.
    4. Stop the solace service using solacectl service.
    5. Migrate the storage-elements to external storage using solacectl storage.
    6. Verify the storage-elements have been moved to external storage.
    7. Re-start the solace service using solacectl service.
    8. Log out of the monitoring event broker's host shell.
  6. Verify the Redundancy Status is Up on all three event brokers in the HA group.