Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Code Block
scsctl storage instance list -d
Info

This listing will also include instances that SCS knows about that are currently offline. If any of these instances will remain offline (decommissioned hardware, etc), then consider removing them from SCS.

Assuming an Old Instance Identity

...

Code Block
curl -X PATCH --data-binary '{"name": "{former instance ID}"}' "http://{SCS IP address}:8095/platform/components/{component name}/groups/{group name}/instances/{new instance ID}/?force=yes"

Defining the Storage Cluster

The storage component within SCS only allows a single group/cluster to be defined for that site. The name of that cluster is governed by the name assigned to its group within SCS.

Create the Cluster

To create a group for Swarm Storage:

Code Block
scsctl storage group add "{cluster name}"

Assigning a Storage Node to a Subcluster

Each node forms a de-facto subcluster if no explicit subcluster assignments are made in Swarm Storage configuration. The Swarm Storage component (storage) provides the node.subcluster setting as a free-form name that may be assigned to one or more nodes.

...

Removing an Instance

If SCS ever needs to “forget” about an instance, use the following command to fully remove it from SCS. The example below uses the default group, but use the -g {group name} form of the command as needed.

Note

Removing an instance removes all custom configuration (settings), configuration file templates, and static files associated with that instance. Use this with caution!

Code Block
scsctl {component} instance remove -d {instance ID}

Defining the Storage Cluster

The storage component within SCS only allows a single group/cluster to be defined for that site. The name of that cluster is governed by the name assigned to its group within SCS.

Create the Cluster

To create a group for Swarm Storage:

Code Block
scsctl storage group add "{cluster name}"

Assigning a Storage Node to a Subcluster

Each node forms a de-facto subcluster if no explicit subcluster assignments are made in Swarm Storage configuration. The Swarm Storage component (storage) provides the node.subcluster setting as a free-form name that may be assigned to one or more nodes.

The storage process looks at all names assigned to the different nodes and forms them into groups, which can then be used to determine how object replica distribution and protection are handled. The nodes may be grouped using subclusters in any way needed to achieve the desired replica/fail-over paradigm.

...

Update the list of NTP servers (specified as comma- or space-delimited list):

Code Block
scsctl platform config set -d "network.ntpServers={new NTP servers}"

...

platform config set -d "network.ntpServers={new NTP servers}"

This also requires that the DHCP server be updated so the setting can be made available to booting Storage nodes.

Code Block
scsctl init dhcp {reserved ranges}

Swarm (Internal) Network MTU

Network MTU for the entire Swarm storage cluster is governed by the MTU set on the internal network interface of SCS. This value is put into DHCP configuration during the init dhcp process, and served to all storage nodes on boot.

Note

Caution

It is important that this is done after the init wizard has been run. The wizard may modify the internal network interface definition and overwrite any MTU updates. If the wizard is run again, then MTU updates will need to be re-applied.

  1. Update the MTU on the internal network interface.

  2. List the interface details on the SCS to ensure that the change is correct.

  3. Re-initialize DHCP to apply to changes to any future booting storage nodes:

    Code Block
    scsctl init dhcp {reserved ranges}

Swarm (Internal) Network

...

Gateway

The network gateway for the entire Swarm storage cluster is governed by a setting available in SCS as of version 1.5. The setting is provided by the MTU set on the network_boot component, and is called network.gateway. By default, this setting points to the IP address of the internal network interface of SCS, but may be overridden by normal means using the CLI. This value is put into DHCP configuration during the init dhcp process, and served to all storage nodes on boot.

Note

Caution

It is important that this is done after AFTER the init wizard has been run. The wizard may modify the internal network interface definition and overwrite any MTU updatesthe internal interface IP address. If the wizard is run again, then MTU updates will any custom gateway definition may need to be re-applied.

  1. Update the MTU on the internal network interface.gateway setting.List the interface details on the SCS to ensure that the change is correct.

    Code Block
    scsctl network_boot config set -d "network.gateway={gateway_ip_address}"
  2. Re-initialize DHCP to apply to changes to any future booting storage nodes:

    Code Block
    scsctl init dhcp {reserved ranges}

Swarm (Internal) Network Gateway

The network gateway for the entire Swarm storage cluster is governed by a setting available in SCS as of version 1.5. The setting is provided by the network_boot component, and is called network.gateway. By default, this setting points to the IP address of the internal network interface of SCS, but may be overridden by normal means using the CLI. This value is put into DHCP configuration during the init dhcp process, and served to all storage nodes on boot.

Note

Caution

It is important that this is done AFTER the init wizard has been run. The wizard may modify the internal network interface definition and overwrite the internal interface IP address. If the wizard is run again, then any custom gateway definition may need to be re-applied.

...

Updating Network Bonding in Swarm Storage

Swarm Storage supports customizing network bonding for NICs and bonding mode. Additionally, a sysctl file may be specified for storage nodes. Refer to the following sections for bonding NICs and/or mode. In either case, the setting(s) must be applied to the PXE boot system before the new values are available to booting storage nodes.

Relevant bonding information can be found at Network Devices and Priority.

Info

Required

The “Apply the Setting to the PXE Boot System” step is required. If the setting is not properly applied to the PXE boot system, then storage nodes will not receive the updated bonding mode during the boot process.

Bonding NICs

Update the bonding NICs setting in SCS:

Code Block
scsctl network_boot config

...

Re-initialize DHCP to apply to changes to any future booting storage nodes:

Code Block
scsctl init dhcp {reserved ranges}

Updating Network Bonding Mode in Swarm Storage

This list of supported network bonding modes can be found at Network Devices and Priority.

Info

Required

Both of the below steps are required. If the setting is not properly applied to the PXE boot system, then storage nodes will not receive the updated bonding mode during the boot process.

...

 set -d "kernel.bondingNics={comma-delimited list of NICs}"

The list of NICs should look like: eth0,eth1, with whatever values are appropriate.

Confirm the new setting value:

Code Block
scsctl network_boot config show -d "kernel.bondingNics"

Bonding Mode

Update the bonding mode setting in SCS:

...

Note

Warning

SCS may need to be upgraded before Swarm Storage. Verify the Swarm Storage version and SCS version are compatible before upgrading Swarm Storage. See Upgrading to the Latest SCS Version for more details.

Obtain the component bundle for the desired version from DataCore Downloads to upgrade the Swarm Storage software of a running cluster. Transfer the bundle to the SCS server and run the following commands to register it with SCS.

...

Navigate to the Storage directory and run tun the following:

Code Block
cd Swarm-new-version/Storage/
scsctl repo component add -f swarm-scs-storage-new-version.tgz

...

This backup allows for SCS settings to be restored in the event that the SCS needs to be rebuilt. A full backup allows for this kind of restoration; a lightweight backup is useful for support purposes only.

...

nameBackup warning

...

Warning

...

.

Full Backup

Obtain a full backup of all data:

...