...
Before proceeding with the recovery, have the following items on hand:
The SCS 1.5.1 RPM and the RPM for the desired SCS version and any related files required for SCS installation, as described here.
A copy of your most recent SCS backup. A full backup is idealrequired, and must be made with the same version of SCS being installed: https://perifery.atlassian.net/wiki/spaces/public/pages/1223491667/SCS+Administration#Full-Backup
A copy of the Swarm storage bundle that matches the version of the Swarm storage software running on your storage cluster. This is not necessary if a full backup is used.
The administrator user name and , administrator password, and cluster name of your storage cluster.
The DHCP initialization parameters used for the storage cluster (reserved IP address pool ranges).
| Note |
|---|
VERY IMPORTANTMake sure the newly configured SCS has the same private side SCS network address. There are parameters stored in the Persistent Settings Stream that point to this address. If you are restoring to a new SCS while the old SCS is still online, you may shut down the private side network interface on the old SCS so that there are no duplicate IP addresses. |
Steps for Recovery
| Insert excerpt | ||||||||
|---|---|---|---|---|---|---|---|---|
|
| Info |
|---|
The backup and the version of the installed SCS software installed must be the same version as was used to create the backup. |
Step 1
Install SCS by following the instructions in https://perifery.atlassian.net/wiki/spaces/public/pages/3042345098/Online+SCS+Installation.
...
| Code Block |
|---|
scsctl platform software activate |
This will present a list of all available versions of the platform component. Verify that the correct version is marked as active (choose it from the list).
Step 4
Restore the SCS backup.
...
Note
The software version provided as a parameter to the command shown above must match the listed version exactly, character by character. (Include the parentheses and string inside them in the parameter.). It is helpful to wrap this version string in quotation marks.
Case 3
If no components are listed or the software version running on the storage cluster is not shown in the list, add the version of the Swarm storage component to SCS that matches the version currently running on the storage cluster.
...
| Info |
|---|
RequiredTo ensure SCS and cluster settings are consistent, always use the “--allow-notification-failures” flag when changing administrator-related settings. |
Step 6
| Note |
|---|
If static IP addresses are used (whether automatically- or manually-assigned), then all assigned addresses need to be within the storage pool range. |
| Code Block |
|---|
Subnet Layout: | | | | | reserve | | reserve | | <-- lower --> | <--- storage pool range ----> | <-- upper --> | | range | | range | | | | | subnet | <------ DHCP and Static ------> | broadcast address address |
...
After restoring a current backup of an SCS 1.5.1 instance, storage node IP addresses should retain the same IP addresses when they are rebooted, as long as the SCS backup file was created after all storage nodes were booted from the SCS instance (and those nodes were up and running). This includes the case where static IP addresses were manually set for the nodes in the storage cluster.
The IP addresses of storage nodes added to the storage cluster subsequent to the creation of the backup file will not have been recorded in the backup, and those nodes may acquire a different IP address when they are rebooted. (Although IP addresses will come from the same range of the address pool as long as DHCP is initialized with the same parameters.).
Ensure that nodes that had their IP addresses recorded in the backup are booted first. All other nodes may only be safely booted after these are online.