| Table of Contents | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| 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. |
Prerequisites
Before proceeding with the recovery, have the following items on hand:
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 required, 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, administrator password, and cluster name of your storage cluster.
The DHCP initialization parameters used for the storage cluster (reserved IP address pool ranges).
...
...
VERY IMPORTANT
Make 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
| Info |
|---|
The installed SCS software must be the same version used to create the backup. |
...
| Code Block |
|---|
# scsctl backup restore [{backup file name]} |
Step 5
Check the version of the Swarm storage component.
...
| Code Block |
|---|
scsctl storage software activate ["{software version]}" |
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.
...
| Code Block |
|---|
scsctl repo component add -f [{storage component bundle file name]} |
During this process, you will be asked whether to use encryption-at-rest with disk volumes and a name to use for the storage cluster.
| Info |
|---|
ImportantIt is important to use the same encryption settings and cluster name that are being used in the current storage cluster. |
...
| Info |
|---|
RequiredTo ensure SCS and cluster settings are consistent, always use the “--allow-notification-failures” flag when changing administrator-related settings. |
Step
...
7
| 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
|
...
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 although IP addresses will come from the same range of the address pool as long as DHCP is initialized with the same parameters.).
...