Skip to main content

Backups, recovery and support

A private system needs a documented recovery plan. Owning the device does not by itself establish that information can be recovered after loss or damage.

Confirm the backup scope​

  • Which databases, files, application settings and credentials are covered.
  • Where copies are stored and whether one copy is independent of the main device.
  • The schedule, retention period, access permissions and encryption arrangements.
  • Who checks failed jobs and when recovery tests are agreed.
  • Who can request restoration and how the request is confirmed.

RAID, a second nearby device and a snapshot can have useful roles, but each has limits. They should not be described as an independent off-site backup without checking the actual configuration.

What proves recovery​

Ask for the latest available recovery-test result and its scope. A completed copy job is not the same as a successful restore. Record the result, any missing data and the next agreed check.

Remote support​

Agree the access method, authorised staff, maintenance window and how access can be revoked. Support hours, response targets, updates and additional work follow your agreement; local installation does not imply continuous monitoring or a 24/7 SLA.

If there is an incident, avoid unplanned resets or deletion. Follow the incident checklist and contact the team.