How SaBackup Protects Your Data — Features & Setup

How SaBackup Protects Your Data — Features & Setup

Key protection features

• Incremental backups: Only changed files are saved after the initial backup, reducing bandwidth and storage use.
• End-to-end encryption: Data is encrypted on the client before transfer and remains encrypted at rest on the backup server.
• Versioning & retention: Multiple file versions are stored so you can restore from past points in time; retention policies automatically prune old versions.
• Integrity checks: Regular checksums and verification routines detect and repair corrupted backup data.
• Access controls: Role-based permissions and API keys restrict who can create, modify, or restore backups.
• Network throttling & scheduling: Limits bandwidth use and schedules backups during off-peak hours to avoid disruption.

Typical setup (assumes SaBackup server + client)

1. Install client: Download and install the SaBackup client on systems to protect (Windows, macOS, Linux).
2. Create account & register client: Generate API key or pair client with the SaBackup server using a registration token.
3. Select data to back up: Choose files, folders, or mount points; set exclusion rules for temp files or large media.
4. Configure encryption: Set a passphrase or use managed keys. If using a user passphrase, ensure it’s stored securely—losing it may prevent restores.
5. Set schedule & retention: Define backup frequency (e.g., hourly incremental, daily full), retention windows, and version limits.
6. Bandwidth & throttling: Configure limits and set maintenance windows for full backups or large restores.
7. Enable alerts & monitoring: Configure email/SMS alerts for failures, verify daily reports, and enable integrity checks.
8. Test restores: Perform periodic test restores (file-level and full system) to validate backup integrity and recovery time.

Best practices

• Use strong, unique encryption keys and store recovery keys separately (e.g., hardware token or secure vault).
• Follow 3-2-1 rule: Keep 3 copies of data, on 2 different media, with 1 copy offsite.
• Automate and monitor: Automate backups and alerting; review logs and failure reports weekly.
• Encrypt backups in transit and at rest.
• Limit access: Use least-privilege roles and rotate API keys regularly.
• Regular restore drills: Schedule quarterly full-restore tests to ensure recovery procedures work.

Recovery workflow

1. Authenticate to SaBackup console or client with proper credentials.
2. Locate dataset and choose restore point (timestamp or version).
3. Select restore target (original location or alternate path).
4. Start restore; monitor progress and verify checksums after completion.
5. If full system restore, follow boot/media instructions provided by SaBackup for bare-metal recovery.

If you want, I can provide a sample client config file and a cron/scheduler example for a typical Linux server.