...
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 is stored and maintained by the customer. See below. |
...
The jtel CI Process uploads new files and data here automatically from the build process.
| Info |
|---|
jtel Container On Premise Backup
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 All On Premise system backups are kept locally in a location of the customers choosing. For On Premise installations, the customer will provide provides jtel with a fileshare accessible to the container system on the network (SMB or NFS). The jtel will mount Container System mounts this fileshare on in the Container stack.
The backup is Automatic backups are 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 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
...