About Database Operations
The following list outlines the general capabilities and operating parameters of the ICE Database backup system.
Important: ICE Server blocks upgrades while a backup or restore operation is in progress.
Only one backup or restore process may run at a time. Attempts to initiate a backup or restore while another is already in progress will be rejected.
About Backup Mode
Only the most recent 1-10 copies of backups may be kept online.
Daily backup is available as an option.
Storage location supported:
► Remote Storage
UNIX scp
UNIX sftp
S3 compatible storage such as Minio and Amazon S3
Microsoft Azure Blob Storage through a storage container service
► Local Storage
Backups are stored on local cluster
Backups are replicated in Georedundant configuration
Backups are replicated in multi-node setup
Downloading backup tarball possible thru pre-signed URL in backupTable (validity: 1 day)
Archived Recordings are included by default but may be omitted to reduce size.
About Restore Mode
Restore by previous Backup ID
► Pick and choose the backup to be restored through the ICE OS Wizard > Backups table.
► If the backup location is remote, the authentication trust information must be provided
Restore by manual entry
Good for restoring backups that no longer appear in the backup table due to age, or the access information such as Login ID, host, etc. have changed since the backup was made.
Good for restoring backups that no longer appear in the backup table due to age, or the access information such as Login ID, host, etc. have changed since the backup was made.
► When backing up from the command line, you will be prompted for all access information.
Restore by manual upload
► Upload a backup tarball thru pre-signed upload URL (validity: 1 day)
All restores are all-or-nothing. You must restore Cassandra, Minio files, and - if specified during backup - all Archived Recording files.
Arcus does not need to be up and running. However, Cassandra must be in healthy running state.