Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: replace Caringo Connect refences with DataCore Downloads

To update any CSN implementation, download and use the CSN 8.3 bundle from the Downloads section on the DataCore Support Portal.

Info
titleNote

Any components running separately from the CSN host, such as Content Gateway and Elasticsearch, are not updated by the CSN install script and must be upgraded separately, using the RPMs in the CSN bundle.

...

To update the version of Swarm Storage software being used in the storage cluster, do the following:

  1. Download the latest CSN bundle from the Downloads section on the DataCore Support Portal.

  2. Expand the bundle on your CSN server.
    Image RemovedImage Added
  3. Install the new Storage (castor) RPM using the following command from a standard RHEL/CentOS terminal window:

    Code Block
    languagebash
    yum install [new Swarm version RPM]
    


  4. After the install, open the CSN Console. A new Swarm software version will appear on the Cluster Services > Netboot Management page.
    See Console - Cluster Services.

  5. To switch to an alternate Swarm software version, select the desired version and click Update. This will change the software image used to network boot all Swarm nodes. 

    Info
    titleNote
    Suspending volume recoveries from the Swarm Admin Console is not necessary. Swarm will automatically enter into maintenance mode after an admin initiated reboot. Administrators may wish to delete older versions of Swarm software that are no longer needed to reduce the size of configuration backups.


  6. Reboot the Swarm cluster so that it can pick up the new version. You may reboot the Swarm cluster all at once or rebooting one node at a time from the Admin Console to pick up the new version.

...

  1. To identify configuration issues for the upgrade, download and run the latest Storage Settings Checker, which is bundled with the Swarm Support tools. With help from Support, address any setting issues (such as deprecations and new requirements) that the report surfaces.
  2. If you have ever customized the /etc/caringo/netboot/netboot.cfg file (such as for "gateway" or "kernelOptions"), make a record of your non-default parameters.
  3. Download the latest CSN bundle from the Downloads section on the DataCore Support Portal.
  4. Expand the bundle on your CSN server.
    Image RemovedImage Added
  5. Remove the yum lock before running the script:

    Code Block
    languagebash
    yum remove yum-plugin-versionlock


  6. Run the CSN's install script from a terminal console, or run using SSH by adding the --viassh flag:

    Code Block
    languagebash
    ./caringo-csn-bundle-install.sh --viassh


  7. The install script ensures that the Swarm cluster.cfg is current with Swarm 9, but the script may reverse some changes required for Swarm 11. Be sure to verify the following before rebooting the nodes:
    In the cluster.cfg, modify the security and SNMP users to make them Swarm 10+ compatible. See Swarm Passwords.
    • Remove the “snmp” user from the administrators line
    • Remove security.operators
    • Add snmp.rwCommunity and snmp.roCommunity
  8. Verify that any customizations you needed for /etc/caringo/netboot/netboot.cfg (such as for "gateway" or "kernelOptions") are present.
  9. The install script restores the defaults in /etc/rsyslog.conf for where log files are stored. If you had changed the log location, reapply your changes after running the script.
  10. From the Netboot page of the CSN Console, select the new Swarm version.

    Info
    titleImportant
    This step is essential because the Swarm configuration values in the CSN may only be compatible with the newer Swarm software included in the CSN ZIP installation. Older Swarm versions may not boot with newer configuration parameters that are not recognized.


  11. From the Swarm UI or legacy Admin Console, reboot the whole cluster at once or do a rolling reboot. As directed by Support, you can use the Support Tools bundle script swarmrestart to perform a rolling reboot.

...

Info
titleBackups
During upgrade, the backup process will not be able to complete and so may log errors. After upgrade, previous backup sets may be marked on the Backup and Restore page of the CSN Admin Console as being only compatible with a previous software version. These backups cannot be restored with the current version but will remain available if the software is reverted to a previous version. See CSN Reset for instructions on how to install different versions of the CSN using the csn-reset functionality.

...