On customer-owned hosting, maintenance belongs to the named operator unless your agreement assigns it to DigLab. Record the update, backup, capacity and incident responsibilities before the installation becomes a business dependency.
Preserve a recoverable backup#
A useful recovery set includes application-version information, configuration, the database, required storage and the encryption material needed to read stored credentials. Protect that material in the approved encrypted backup plane with restricted access.
An exported server definition is not a complete backup. The transfer intentionally omits stored credentials, and an installation's encrypted data may be unusable without its matching encryption key. Do not rotate or replace that key as an ordinary troubleshooting step.
Before an update#
Read the release requirements and note the running version. Capture the current settings and a restorable backup. Check available disk space, PHP ZIP and ZipArchive availability before using the native updater, and choose a change window appropriate to the workload. Preserve a rollback release and any approved local compatibility changes.
Use the supported package/update mechanism. Do not overwrite the live installation with another customer's database, configuration or credentials.
Verify after the update#
Check the administrator page, HTTPS, scheduler, software activation and branding. Then repeat discovery and a harmless read-only call through the actual client connection. Recheck authorised writes only with an appropriate test and authorisation.
If local compatibility changes were required in your delivery, check whether the update preserved or superseded them. Report stages separately: files updated, migrations completed, application healthy and client workflow accepted.
Test recovery#
Restore to an isolated recovery environment using the matching protected secrets. Verify that the backup can be read and the intended test workflow runs. Avoid enabling production sends, schedules or webhooks in a recovery environment merely because they were enabled in the original.
Monitor capacity and scheduled maintenance#
Track storage, database growth, logs and dependency health. Confirm that scheduled maintenance actually runs. Review limits before a large import or traffic increase; software activation capacity is not a guarantee of unlimited server resources.