Backup and restore

Add redundancy when you need another copy

A backup target is optional. Use it when you want extra redundancy outside the SyncVisor server, then prove recovery with one small file.

Goal

Prove one recovery check

Finish with a connected optional backup target, a WebUI backup verification result, and one recovered test file.

Before

Before you start

  • Server Manager shows the server is running.
  • You can sign in to the WebUI as an admin.
  • You have an object-storage bucket or container you control.
  • You know where backup credentials are stored.

1. Choose a target

Use storage that is separate from the SyncVisor server disk. Supported target types include S3-compatible storage, Google Cloud Storage, and Azure Blob Storage.

2. Keep credentials narrow

Use credentials limited to the bucket or container used for SyncVisor backup. Record the account owner and where recovery credentials live.

3. Enable backup from the WebUI

Open the WebUI admin area and add the backup target. Start with a small folder so status and restore are easy to verify.

4. Check status

  • The target is connected.
  • New chunks are queued and uploaded.
  • Failures are visible and retryable.
  • The object store shows new backup objects.

5. Prove recovery

  • Upload a small test file.
  • Wait for backup status to show it has been handled.
  • In the WebUI admin area, run backup verify for the target and confirm the sampled chunks pass.
  • Use the native app's version history to restore an older version, or use WebUI version history to download a version.
  • Open the restored or downloaded file and confirm its contents.

Success check

You can point to the server, the backup target, the recovery credentials, a successful WebUI backup verification result, and a file recovered through native version restore or WebUI version download.

Continue

Use backup with confidence