...
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. |
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 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:
...