Skip to main content

Storage compliance and status

Storage status (system administrators)​

Admin > Backups > Storage status shows on one page:

  • Status: Everything is in order, Needs attention (backups late or off, a copy or a destination test failed) or Failing (the newest backup or verification failed); the last backup, the last success, the next run, failed runs in the last 24 hours and the last verification. MonoPhone's admin section shows the same card.
  • Backup copies: copies of every backup on other install storage destinations, each with its own schedule and retention. Add a copy, Copy now, edit or remove. A copy keeps at least what the backup target keeps. Nothing is decrypted to copy (backups are encrypted with your passphrase).
  • Install-wide destinations: region, write-once (WORM), last test and what uses them. A destination backups use cannot be deleted.
  • Manifest signing keys: every backup and delivery leaves a manifest with the SHA-256 of each file, signed with this key. Give the public key to an auditor; Rotate the key starts a new one (the old one still verifies).
  • Prove a backup is unchanged: type the backup id and press Check.

The backup target itself can be an install storage destination: in the backup settings choose the destination instead of a directory or bucket.

Alerts​

You are told by e-mail, by push in MonoPhone (admin alert Backups), by web push and on the alert webhook when:

AlertWhen
The newest backup failedthe last backup run did not complete
No successful backup for N hoursscheduled backups are on but none succeeded for more than two intervals
A backup copy failedthe last run of a copy did not complete (retried within the hour)
Verification failed or is staleas before

The same conditions are Prometheus rules (BackupFailed, BackupLate, BackupCopiesFailed) for installs that run Prometheus; see Alerts.

Storage compliance (company administrators)​

Admin > Settings > Storage > Storage compliance:

  • Data residency: the regions the company's data may be stored in, for example eu-* or eu-central-1, eu-west-3. A destination elsewhere (or one without a region) is refused; saving lists the destinations that are already outside.
  • Prove a delivered file is unchanged: choose the destination, type the run id and the file's key as the run's manifest lists them, and press Check. MonoPbx reads the file again, hashes it and compares it with the signed manifest. Unchanged needs a valid signature and the same SHA-256.
  • Legal hold: put a legal hold on one object or take it off (Amazon S3 and S3-compatible services whose bucket was created with Object Lock, Google Cloud Storage, and Azure Blob containers with version-level immutability). While it holds, neither MonoPbx nor anyone else can delete the object. See Write-once destinations for what each provider needs.

Checking a manifest yourself​

Next to each manifest is <manifest>.sig. With the public key from the console:

  1. sha256(manifest) must equal manifest_sha256 in the signature file;
  2. the Ed25519 signature must verify over the text mpbx-manifest-signature-v1\n<manifest_key>\n<manifest_sha256>\n<signed_unix>\n<key_id>\n;
  3. each file's SHA-256 must equal the one the manifest lists.

Always use the public key the console shows, not the one inside the signature file.

See also Storage destinations for the permissions each provider needs.