iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
For most Linux VPSs, the safest design in 2026 is a layered 3-2-1 plan: use provider snapshots for quick rollback, an encrypted and deduplicated Restic or Borg repository outside the provider’s failure domain for disaster recovery, and a separately controlled or offline copy for irreplaceable data. Snapshots alone are not a complete backup because they can share the same account, region, provider controls and deletion risks as the server.
The recommended Linux VPS backup architecture
A VPS backup plan should serve two different jobs. The first is rapid rollback after a bad package update, configuration edit or deployment. The second is recovery when the virtual machine, account, region or provider is unavailable. One mechanism rarely does both well, so separate them into layers.
| Layer | Purpose | Implementation | Important checks |
|---|---|---|---|
| 1. Provider snapshot | Fast rollback to a recent server state | Enable the VPS provider’s scheduled snapshots at a cadence that matches your change rate | Retention period, geographic placement, export capability, restore process and account-recovery terms |
| 2. Off-site encrypted repository | Recovery if the VPS, account or provider fails | Run Restic or Borg from the VPS to storage outside the provider’s failure domain | Encryption key escrow, repository integrity checks, deletion protection and successful restores |
| 3. Independent or offline copy | Protection from provider-wide incidents, credential theft and destructive deletion | Replicate selected data to a second provider, removable drive or other separately controlled medium | Different credentials and ideally a different provider or region; disconnect or write-protect the medium when practical |
The 3-2-1 formulation means three copies of the data, on two different media types, with at least one copy off-site. Treat it as a planning rule rather than a guarantee of a particular recovery time or cost.
Why VPS snapshots are not enough
A snapshot is usually tied to the same provider account that runs the VPS. If an attacker obtains that account, a billing or policy problem suspends it, the provider suffers a regional outage, or the provider’s snapshot service fails, the snapshot may be inaccessible at the moment you need it. Retention can also be shorter than your corruption-detection window, and export or cross-provider restore may not be supported.
#1 Best Overall
- Read Before You Buy — No Video Output: These adapters support charging and USB 2.0 data transfer, but cannot transmit video signals. Except for standard USB webcams (which use USB data only), they are not compatible with HDMI/DisplayPort cables, video-capable USB-C hubs, or docking stations with video output.
- Convert USB-A Ports to USB-C: Designed to connect USB-C earphones, cables, flash drives, card readers, and other USB-C accessories to standard USB-A ports. Plug-and-play with no drivers or software required.
- Aluminum Alloy Housing: Built with a sturdy aluminum alloy shell that aids in heat dissipation and protects against daily wear and scratches. Designed to maintain a stable and secure connection.
- Compact & Travel-Friendly: The ultra-compact design allows the adapter to stay plugged into your device without blocking adjacent ports or adding bulk, reducing wear and tear on your original USB ports.
- 12-Month Warranty: Backed by a 12-month manufacturer warranty for peace of mind. Designed to meet strict quality control standards for reliable everyday performance.
Use snapshots when you need to undo a change in minutes. Do not use them as the only copy of application data, database dumps, secrets or deployment configuration. Before relying on them, confirm the provider’s documented retention, storage location, export format, restore procedure and account-recovery process. Perform an actual restore or export test rather than assuming that a snapshot can be booted elsewhere.
Set recovery objectives before choosing a schedule
Your recovery-point objective (RPO) is the maximum acceptable amount of data you can lose. A daily backup gives an RPO of up to roughly 24 hours; it is not sufficient for a workload that changes every few minutes. Your recovery-time objective (RTO) is how quickly the service must be operating again. Snapshots can reduce RTO for a straightforward rollback, while an off-site repository and a clean VPS rebuild address a provider or account failure.
- Ordinary websites and internal tools: run an off-site backup at least daily, with provider snapshots before major changes.
- Frequently changing customer or transactional data: run more often than daily, and create database dumps or logical backups on a cadence that meets the RPO.
- High-value or regulated data: add an independently controlled or offline copy and document who can retrieve the encryption key.
Backups should run on a schedule, but neither Restic nor Borg is a built-in scheduler. Use a systemd timer, cron, or a wrapper, and make sure a second run cannot overlap the first.
Restic versus Borg
Both tools create versioned, deduplicated repositories and can be automated from a Linux VPS. The better choice depends mainly on the destination and the VPS’s resource limits.
| Axis | Restic | Borg |
|---|---|---|
| Encryption | Repository encryption and authentication are part of its design and are always enabled. | Client-side authenticated encryption is supported; the encryption mode is selected when the repository is initialized. |
| Storage targets | Official backends include SFTP, REST, S3-compatible storage, Backblaze B2, Azure Blob Storage and Google Cloud Storage. | Commonly writes to a remote backup host over SSH. |
| Scheduling | Requires an external scheduler such as systemd or cron. | Also requires an external scheduler or wrapper. |
| Resource profile | A practical general-purpose choice when object storage, multiple cloud backends or portable binaries matter. | A mature, memory-efficient choice for small VPSs and an SSH-accessible backup host. |
| Main operational risk | Someone with write access can still delete or manipulate repository data; the tool does not promise protection against that threat. | The repository and encryption key need protection, and SSH and deletion permissions should be separated where possible. |
Choose Restic when object storage is the priority
Restic is usually the simpler default for a VPS that should send backups directly to S3-compatible or other cloud object storage. It encrypts and deduplicates data before upload, so the storage service does not need access to plaintext files. Its repository can also be hosted through SFTP or a REST server when object storage is not suitable.
Rank #2
- 5-in-1 USB-C Hub: Experience comprehensive connectivity featuring a Power Delivery input, two USB-A 2.0 ports, a USB-A 3.0 port, and an HDMI port. (Note: The USB-C power delivery input port is only for connecting an external wall charger to power your laptop and cannot power peripheral devices.)
- 90W Pass-Through Charging: Achieve optimal charging with 90W pass-through power to your laptop, supported by a total input of 100W, with the hub reserving 10W for operational efficiency. (Note: Wall charger not included.)
- Quick Data Transfers: Accelerate your productivity with rapid data transfers using a high-speed 5Gbps USB 3.0 port and two 480Mbps USB 2.0 ports.
- 4K HDMI Display: Enhance your visual experience with a hub capable of delivering 4K resolution at 30Hz in both mirror and extend modes. Please note that this hub is compatible with MacBook (macOS 12 and newer), Windows 10 and 11, ChromeOS, and laptops equipped with DP Alt Mode and Power Delivery. Note: This device is not compatible with Linux.
- What You Get: Anker USB-C Hub (5-in-1, 4K HDMI), welcome guide, 18-month warranty, and our friendly customer service.
Choose Borg when an SSH backup host and low memory use fit better
Borg is well suited to a VPS that can reach a separately administered Linux backup host over SSH. It provides content-defined deduplication, optional compression, client-side encryption and integrity verification. Keep the Borg key safe and design the remote account so that a compromised VPS cannot freely erase the entire repository.
Free tools Windows power users keep installed
One-click scans. No signup required.
What to include in the backup
A successful archive is more than a copy of /var/www. Inventory what is required to rebuild the service on a fresh VPS.
- Application source, uploaded assets and generated files that cannot be recreated.
/etcconfiguration, service units, reverse-proxy settings, firewall rules and scheduled jobs.- Deployment manifests, container definitions, package lists and infrastructure configuration.
- TLS certificates and private keys, SSH configuration and other host-specific credentials, protected with appropriate permissions.
- Database exports produced by a consistency-aware method.
- Scripts, licenses and environment documentation needed to start the application.
Do not assume that copying a live database directory produces a recoverable point-in-time backup. Use the database’s dump or backup facility, or briefly quiesce writes when an application-consistent filesystem copy is required. Store the resulting dump in the encrypted repository and test importing it.
Build a Restic backup to object storage
1. Prepare a destination outside the VPS provider
Create a bucket or repository in a different failure domain from the VPS whenever possible. Use a dedicated identity that can write new objects but cannot casually delete historical data. If the storage service supports object lock, append-only retention or a separate administrator role, use those controls for the backup path.
2. Install Restic and keep credentials separate from the server image
Install a current Restic package or binary using your distribution’s trusted method. Keep the repository password in a password manager and in a separately stored offline escrow. Losing the password can make encrypted data unrecoverable. Do not put it in a world-readable shell script or commit it to a deployment repository.
Recommended Free Tools
Rank #3
- Sleek 7-in-1 USB-C Hub: Features an HDMI port, two USB-A 3.0 ports, and a USB-C data port, each providing 5Gbps transfer speeds. It also includes a USB-C PD input port for charging up to 100W and dual SD and TF card slots, all in a compact design.
- Flawless 4K@60Hz Video with HDMI: Delivers exceptional clarity and smoothness with its 4K@60Hz HDMI port, making it ideal for high-definition presentations and entertainment. (Note: Only the HDMI port supports video projection; the USB-C port is for data transfer only.)
- Double Up on Efficiency: The two USB-A 3.0 ports and a USB-C port support a fast 5Gbps data rate, significantly boosting your transfer speeds and improving productivity.
- Fast and Reliable 85W Charging: Offers high-capacity, speedy charging for laptops up to 85W, so you spend less time tethered to an outlet and more time being productive.
- What You Get: Anker USB-C Hub (7-in-1), welcome guide, 18-month warranty, and our friendly customer service.
3. Initialize the repository
export RESTIC_REPOSITORY='s3:https://S3_ENDPOINT/BUCKET/PREFIX'
export AWS_ACCESS_KEY_ID='BACKUP_ACCESS_KEY'
export AWS_SECRET_ACCESS_KEY='BACKUP_SECRET_KEY'
export RESTIC_PASSWORD_FILE='/root/.config/restic/password'
restic initFor SFTP, REST, Backblaze B2, Azure Blob Storage or Google Cloud Storage, set the repository and provider-specific credentials according to that backend’s documented format. Keep those credentials distinct from the VPS provider login.
4. Back up application files and database exports
restic backup /etc /home /var/www /var/lib/application /var/backups/databaseExclude caches, temporary files and reproducible build artifacts after confirming they are not needed for recovery. Tag runs by role or environment so that you can identify them during retention and restore operations.
restic backup --tag production-vps /etc /var/www /var/backups/database
restic snapshots5. Schedule the job and prevent overlap
Create a root-owned wrapper that loads the repository credentials, creates a fresh database dump, runs Restic and writes a nonzero exit status to the service log on failure. Use flock or an equivalent lock so a slow upload cannot overlap the next run.
flock -n /run/lock/restic-vps.lock restic backup --tag production-vps /etc /var/www /var/backups/databaseA systemd timer is preferable when you want journal logging and failure status. A daily 02:30 timer is only an example; choose a time and interval that satisfy the RPO and avoid the busiest database period.
[Unit]
Description=Linux VPS Restic backup
[Service]
Type=oneshot
ExecStart=/usr/local/sbin/run-restic-backup
[Unit]
Description=Run the VPS backup daily
[Timer]
OnCalendar=*-*-* 02:30:00
Persistent=true
[Install]
WantedBy=timers.targetAfter enabling the timer, confirm it appears in systemctl list-timers and inspect the service journal after the first run. Alert on failed units, missing runs and unexpectedly small backup sizes.
Rank #4
- Dual Converters, Infinite Potential：Includes 2× USB C male to USB A female adapters and 2× USB A male to USB C female adapters. Perfect for a wide range of uses—tablets with Bluetooth keyboards, expand USB ports on macbook, and more. Two different converters for all your daily needs
- Next-Level 10Gbps & 3A Charging: No more slow 480Mbps, this usb to usb c adapter has a transfer speed of up to 10Gbps, allowing you to do more transferring in less time. This usb adapter fits both USB A and USB C charger, supporting up to 3A fast charging
- Upgraded Exquisite Craftsmanship: With an aluminum alloy housing and metal connector, the usbc to usb adapter is extremely durable and sturdy. Rigorously tested to withstand more than 10,000 times of plugging and unplugging, ensuring long-lasting performance
- Broad Compatible: The usb c to usb adapter widely supports all USB C/ USB A devices like laptops, tablets, cellphones, car chargers, and phone chargers. Such as compatible with MacBook Pro/Air 2023/2022, Thunderbolt 4/3 Devices,Apple MagSafe Watch 9/8/7/SE/Ultra, iPad Pro 2022/2021, Samsung Galaxy S23/S20/S10, and iPhone 17/16/15 Pro. Plug and play
- Please Note: To reach 10Gbps speed, keep the cable under 3.3 ft. For USB A Male to USB C adapters, try flipping the USB C connector. USB C Male to USB A adapters support bidirectional 10Gbps transfer within 3.3 ft
6. Apply retention and check the repository
Retention should preserve enough daily, weekly and monthly points to cover delayed detection of corruption or compromise. The exact counts are a policy decision, not a universal default.
restic forget --keep-daily 7 --keep-weekly 4 --keep-monthly 12 --prune
restic checkRun pruning when the storage and CPU impact is acceptable, and monitor the result. A retention command that deletes the only copy of a needed historical state is an operational failure, so document the policy and review it before changing it.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Build a Borg backup over SSH
1. Provision a dedicated backup account
On the remote host, create a repository owned by a dedicated account. Restrict the SSH key to that account and limit shell capabilities where practical. Keep administrative deletion rights separate from the key used by the VPS.
2. Initialize an encrypted repository
export BORG_REPO='backup-user@BACKUP_HOST:/srv/borg/production-vps'
export BORG_PASSPHRASE_FILE='/root/.config/borg/passphrase'
borg init --encryption=repokey-blake2Choose the encryption mode deliberately and escrow the key or passphrase offline. Without it, the encrypted archives may be impossible to read.
3. Create archives and prune old points
borg create --compression lz4 --stats "$BORG_REPO::{now}" /etc /var/www /var/backups/database
borg prune --list --keep-daily=7 --keep-weekly=4 --keep-monthly=12
borg checkSchedule these commands with systemd or cron, use a lock, and alert on nonzero exit codes. Test that the remote account can create archives but cannot destroy more history than your recovery policy allows.
Best Value
- 5-in-1 Connectivity: Equipped with a 4K HDMI port, a 5 Gbps USB-C data port, two 5 Gbps USB-A ports, and a USB C 100W PD-IN port. Note: The USB C 100W PD-IN port supports only charging and does not support data transfer devices such as headphones or speakers.
- Powerful Pass-Through Charging: Supports up to 85W pass-through charging so you can power up your laptop while you use the hub. Note: Pass-through charging requires a charger (not included). Note: To achieve full power for iPad, we recommend using a 45W wall charger.
- Transfer Files in Seconds: Move files to and from your laptop at speeds of up to 5 Gbps via the USB-C and USB-A data ports. Note: The USB C 5Gbps Data port does not support video output.
- HD Display: Connect to the HDMI port to stream or mirror content to an external monitor in resolutions of up to 4K@30Hz. Note: The USB-C ports do not support video output.
- What You Get: Anker 332 USB-C Hub (5-in-1), welcome guide, our worry-free 18-month warranty, and friendly customer service.
Retention, frequency and monitoring
| Control | Recommended practice | Why it matters |
|---|---|---|
| Frequency | At least daily for ordinary workloads; increase the interval when the RPO is tighter | Limits the maximum unprotected change window |
| Snapshot timing | Take a provider snapshot before upgrades, migrations and high-risk configuration changes | Provides a quick rollback point without replacing off-site backups |
| Retention | Keep documented daily, weekly and monthly points appropriate to how long corruption may remain undetected | Prevents a rolling window from deleting every clean copy |
| Overlap control | Use a lock and fail the second invocation | Prevents concurrent scans, inconsistent logs and unnecessary load |
| Monitoring | Alert on failed jobs, missed schedules, authentication errors, repository-check failures and abnormal size changes | A backup that silently stopped is not a recovery control |
Restore testing: prove that the backup works
A repository that has never been restored is an assumption. Restic emphasizes verifiable restoration, and a sound VPS plan tests both individual files and a complete rebuild.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problems- Test a single file after setup. Restore a known configuration file or uploaded asset into a temporary directory and compare it with the expected content.
- Test a database import. Retrieve the latest dump into an isolated database instance and run application-level checks.
- Perform a fresh-host drill periodically. Provision a clean VPS or isolated machine, install the operating system and backup client, retrieve credentials, and restore the repository.
- Re-create services. Apply firewall rules, install packages, restore service units and TLS material, then start the application in the documented order.
- Record the result. Measure the time to obtain credentials, provision the host, download data, restore the database and validate key user journeys. Note every manual step that should become automation.
Run file-level checks after initial setup and repeat full rebuild drills on a schedule that reflects the value of the service. Also test the provider snapshot’s export or restore path; a snapshot that cannot leave a disabled account does not solve that failure scenario.
Protect against deletion, credential loss and provider failure
Repository deletion or manipulation
Restic’s threat model explicitly does not protect against an attacker who can delete or modify files at the storage location. A compromised VPS key or storage account can therefore destroy history even though the data is encrypted. Use append-only or write-protected storage where available, separate upload and deletion identities, and retain an independent copy that the VPS cannot erase.
Lost encryption credentials
Store the Restic password or Borg key in a password manager and a separate offline escrow controlled by the people responsible for recovery. Verify that an authorized operator can retrieve it without logging in to the failed VPS. Never rely on a key stored only in the machine being backed up.
VPS provider account disappears
With an off-site repository, recovery begins on a new provider or physical host: obtain the independently stored credentials, install Restic or Borg, connect to the repository, restore configuration and database data, and re-create DNS, firewall and service settings. Document this runbook while the original VPS is healthy, because account recovery is hardest during an incident.
Same-machine storage
A second directory or attached volume on the same VPS is not an independent backup. Disk failure, ransomware, an incorrect deletion command or account suspension can affect both copies. Keep at least one repository outside the VPS account and, for high-value data, outside the provider or region as well.
Add the third, independently controlled copy
Choose the medium according to how much data must be protected and how quickly it must be recovered.
| Option | Use case | Controls to add |
|---|---|---|
| Second object-storage provider or region | Automated, remotely accessible disaster recovery | Separate account, credentials and deletion policy; verify egress and restore access |
| Removable external drive | Low-cost archive for selected repositories or database exports | Encrypt it, disconnect or write-protect it when practical, rotate drives and store one off-site |
| Independent backup host | SSH-based Borg repository with administrative separation | Dedicated account, restricted key, monitored capacity and a separate administrator for deletion |
Replicate the data that would be most expensive or impossible to recreate first: database exports, user uploads, secrets required to rebuild services and the backup repository metadata itself. Periodically verify that the third copy can actually be read.
Quick Recap
Operational checklist
- Provider snapshots are enabled and their retention, location, export and account-recovery behavior are documented.
- An encrypted Restic or Borg repository exists outside the VPS provider’s failure domain.
- Database dumps are generated consistently before the file-level backup runs.
- Credentials and encryption keys are stored in a password manager plus offline escrow.
- The backup job is scheduled, overlap-protected and monitored for failures and missed runs.
- Retention preserves daily, weekly and monthly points appropriate to delayed detection.
- Deletion rights are restricted, and at least one copy is independently controlled or offline.
- Individual-file restores and full fresh-host rebuilds have been completed and timed.
- A written recovery runbook explains how to obtain credentials, provision a host, restore data and validate the application.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
