Migrating Appliances from Internal to External Disk

This section describes how to migrate a standalone Guaranteed Messaging appliance from using the internal disk for spooling to using an external disk. The new external disk LUN must be present in the system before migrating the internal disk spool files to the new LUN.

Migrating from internal to external disk is service affecting. For example, the shutdown Service CONFIG commands used in this procedure will cause a disruption in customer service when run. You should do this during a maintenance window to reduce service interruption for clients.

If you require assistance, or if you have questions about any steps in this procedure, contact Solace.

The procedure discussed in this section is only applicable to Solace PubSub+ appliances.
This procedure does not apply to appliance releases older than 7.2.2.
Operations below that state they can only be performed by root can now also be performed by a Sysadmin User. For information on configuring Sysadmin Users, refer to Configuring Multiple Linux Shell Users.

Steps

To migrate from internal to external disk for Guaranteed Messaging spooling, do the following:

Enter the following command to ensure that message-spool defragmentation is not active:
```
solace1> show message-spool

. . .

Defragmentation Status:                   Idle

. . .
```
If the message spool defragmentation status is not Idle, wait for the defragmentation process to complete before proceeding.
Register the appliance HBA with the external array. For details, refer to Configuring an External Disk Array for Guaranteed Messaging.
After registering the appliance HBA with the external array, you must restart the appliance to ensure all changes are detected correctly. Enter the following commands to restart the appliance and update it with the new LUN configuration:
```
solace1> enable
solace1# reload
This command causes a reload of the system.
Do you want to continue (y/n)? y

solace1#
```
After restarting the appliance, do not make any further changes to the external array until you have completed this procedure.

Enter the show hardware details command to confirm that the new external disk LUN is available according to the new WWN.

Obtain the WWN of the new LUN from your storage administrator.

The examples in this procedure use 60:06:01:60:e8:60:1c:00:4e:32:ab:65:55:df:e2:11 as the WWN of the new LUN.

Don't proceed further until the new LUN is visible.

Partition and create the file system on the new LUN. For details on how to do this, see Configuring an External Disk Array for Guaranteed Messaging.

Shut down the message spool on the event broker to stop Guaranteed Messaging:

solace1(configure)# hardware message-spool
solace1(configure/hardware/message-spool)# shutdown

Using root access to the event broker, mount the p1 partition of the new external disk LUN to /usr/sw/externalSpool/p1.
This partition is located in /dev/mapper/ and is named <wwn><p#>.
```
mount /dev/mapper/360060160e8601c004e32ab6555dfe211p1  /usr/sw/externalSpool/p1
```
Copy all directories and files from the internal spool directory to the external spool p1 directory.
```
cp -a /usr/sw/internalSpool/* /usr/sw/externalSpool/p1
```
Unmount the p1 partition of the new external LUN.
```
umount /usr/sw/externalSpool/p1
```

Enter the following commands on the event broker to configure the message spool to use the new external disk LUN, using the WWN of the new LUN as displayed in step 4.

solace1# configure
solace1(configure)# hardware message-spool
solace1(configure/hardware/message-spool)# no internal-disk
solace1(configure/hardware/message-spool)# disk-array wwn 60:06:01:60:e8:60:1c:00:4e:32:ab:65:55:df:e2:11

Enter the following CONFIG commands to start Guaranteed Messaging and message spooling:
```
solace1# configure
solace1(configure)# no hardware message-spool shutdown primary
```

Provide feedback