Backup Requirements
Selecting and applying an appropriate backup strategy (software, number of backups, frequency, etc) is outside of the scope of this guide.
However, the chosen strategy must be able to preserve the SGC’s critical files. Provided that a version of these files are available from before any event causing catastrophic failure it should be possible to restore the failed SGC node or nodes.
Possible options include:
|
Backing up of an entire VM from the VM host is not recommended due to the likelihood of significant whole VM pauses. Such a pause can cause Hazelcast to detect cluster failure which may result in node restarts. |
Backup Critical Files Only
This option involves taking a backup of the critical files and, where file locations have been customized, noting which have changed and where they should be located.
Restoration of the SGC component requires:
-
Installing the SGC from the original
ocss7-${version}.zippackage -
Copying the configuration files from the backup to the new installation, honouring any original custom locations
|
|
Restoration following a whole-OS failure also requires reinstatement of any SCTP tuning parameters, user process tuning and network interfaces as originally described in Installing the SGC. |
Backup Whole SGC Installation
This option involves taking a backup of the entire SGC installation directory. Note that if any file locations have been customized to live outside of the SGC installation directory these will also need including.
Restoration of the SGC component requires:
-
Extracting the entire SGC installation from the backup
|
|
Restoration following a whole-OS failure also requires reinstatement of any SCTP tuning parameters, user process tuning and network interfaces as originally described in Installing the SGC. |
Critical Files
The following files contain installation-specific configuration and must be included in any backup regimen. The following are the default paths of these files, specified relative to the OCSS7 installation root:
-
config/sgcenv -
config/SGC.properties -
config/log4j.xml -
config/hazelcast.xml— if it exists -
var/sgc.dat
In addition, the files in the following locations must be preserved for at least 30 days, preferably longer:
-
logs/ -
cli/log/
This is to ensure that logging remains available in the event that a support request is required for an event that occurred just prior to catastrophic failure of an SGC host.
