IT Audit Factory · Evidence-first audit operationsFree · Professional · MSP

Documentation

Back up and maintain an MSP Server

MSP Server administrator · Updated 9 October 2026

Follow the numbered steps, then check the result before continuing. Choose only the procedure that matches your task.

Before you begin

  • Schedule maintenance and notify connected users. Know the intended database and a backup destination with sufficient space.
  • Do not test restore against production just to verify a backup. Use an administrator-controlled recovery environment and a documented recovery plan.

1. Create and inspect a backup

  1. Open MSP Server Administration → Backups. Review Backup folder and enter the approved location if needed.
  2. Click Save Settings after changing the backup destination. Confirm that the service account can write to it.
  3. Click Run Backup Now and wait for the result. Do not assume that clicking the button means the backup completed.
  4. Click Open Backups. Confirm that a new backup artifact exists with the expected time and nonzero size. Retain it with the corresponding recovery/configuration information under your access controls.
  5. Before an upgrade or destructive maintenance, verify the backup according to your recovery process. Restore Backup... is a separate recovery action; review its target and implications before invoking it.
Check before continuingThe backup operation reports success and its output is present. File existence alone is not a restore test.

2. Preview and run safe cleanup

  1. Open Maintenance & Cleanup. Set Retention days according to your approved retention policy.
  2. Keep Dry-run mode selected initially. Choose only the intended operations, such as Invalid-run cleanup, Find orphaned files/records, Vacuum and Analyze or Reindex database. Review the implications before selecting Remove orphaned files.
  3. Click Preview Cleanup. Read the eligible records, protected records, missing files and orphaned storage summary. Legal holds and unexpired evidence retention block deletion.
  4. If the preview matches your authorized maintenance scope, keep Backup before cleanup enabled, clear Dry-run mode only when ready to make changes, and select I confirm this maintenance operation.
  5. Click Run Safe Cleanup. Wait for completion. Use Open Maintenance History or Refresh History to inspect operation status, retention and affected run/file counts.
Check before continuingThe operation’s history records its outcome and scope. Any failure is investigated before scheduling another cleanup.

If something goes wrong

Backup fails

Check destination permissions, free space and the reported database/service error. Retain the diagnostic details and resolve them before an upgrade.

Preview shows protected records

Do not lower retention or remove holds just to force cleanup. Have the authorized record owner review the retention/legal-hold decision.

You need to restore

Use the approved recovery plan, confirm the target environment and keep current-state recovery material. Contact Support with the backup/error details if the restore prerequisites are unclear.