...
It is possible to go back to a previous incarnation of the stack / installation as needed.
All Backup Scenarios
| Warning |
|---|
None of the backup scenarios described provide:
If you require retention of call recording audio files or voice recordings, then you must provide an FTP storage to which call recordings and voice recordings will be uploaded. Detailled call and process logs are not be backed up in any scenario. |
jtel Cloud SaaS Customer WORM Storage backup
| Info |
|---|
This applies only for jtel Cloud SaaS systems. For On Premise installations, the backups are stored and maintained by the customer. See below. |
The system makes a backup to WORM storage (Write Once Read Many times) which is hosted by jtel in Azure (Geo Location: Germany West). The backup is created once a day at 02:00.
The backup is a content based backup which allows for re-creation of the same container stack on any suitable host.
...
- The storage account cannot be deleted, even by global jtel admins for 180 days
- The backups are immutable and therefore cannot be encrypted
For initial stack setup, a vanilla backup provided from the jtel WORM Storage is used.
The backups from a running system are made nightly, automatically, by the acd-task-runner container.
| Info |
|---|
Each WORM storage is a specific storage instance housed in a customer specific storage account and is used for one customer only. It has it's own unique access credentials and endpoint providing a very high level of security. The upload is done via rclone command Networking related information here Cloud jtel Container Stack - Networking Cloud OnPrem |
jtel WORM Storage
This immutable storage contains version specific files and data stored for specific releases. These files are required and copied to the customer specific storage when an initial (empty) installation is made or when an update to a new release is performed.
The jtel CI Process uploads new files and data here automatically from the build process.
| Info |
|---|
This applies only for jtel Cloud SaaS systems. For On Premise installations, the backups are stored and maintained by the customer. See below. |
jtel Container On Premise Backup
For On Premise installations, the customer provides jtel with a fileshare accessible to the container system on the network (SMB or NFS). The jtel Container System mounts this fileshare in the Container stack.
Automatic backups are created once a day at 02:00.
The backup is a content based backup which allows for re-creation of the container stack on a suitable host.
For initial stack setup, a vanilla backup provided from jtel is used.
| Warning |
|---|
The customer is responsible for implementing suitable backup retention periods. |
Creating a new Installation
...
- The version to update to is configured in the customer repository
- The customer repository is updated on the target host (one liner)
- The following steps are the same as above from "Start Containers"
- When the containers are started, the required versions will automatically be pulled and any updates necessary will be applied to the database and file system.
Updating a System / Disaster Recovery / Moving a System - Out of Place (Migrations)
The same procedure is used for all of the following use cases:
...