What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The safest way to protect self-hosted services on a Raspberry Pi is to combine a whole-device image for disaster recovery with regular, service-aware copies of deployment files and persistent data. An image can return a replacement card or disk to the exact state captured; file-level and database backups let you recover one service without overwriting everything else.
Do not assume that copying a Docker container is enough. Containers are disposable; Compose files, environment files, bind-mounted directories, named volumes and database exports contain the state you actually need. The right backup set depends on where each service stores data and whether that data can be copied safely while the service is running.
As an Amazon Associate I earn from qualifying purchases.
Decide what “recovery” must accomplish
Start by defining the failure you are preparing for. A dead SD card, a failed SSD, an accidental configuration change and a corrupted database require different recovery material.
- Whole-device recovery: Rebuild the operating system, boot settings, installed packages, containers and files as they existed at one point in time.
- Service recovery: Recreate one application on a repaired host without replacing unrelated services.
- File recovery: Retrieve a document, media file, certificate or configuration file while leaving services online.
- Data-consistent recovery: Restore a database or other stateful store without relying on a potentially inconsistent copy made during writes.
Write down the recovery target for every service. A media server may need only its library database and configuration, while a password manager or database-backed application also needs an application-consistent export. Keep a copy of the service’s documented restore procedure with the backup rather than relying on memory.
#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.
Backup methods compared
| Method | What it captures | Typical downtime | Best use | Main limitation |
|---|---|---|---|---|
SD-card or disk image with dd or an imaging app |
Every readable block on the selected device, including the operating system and current service state | Requires shutdown and removal of the card for the documented workflow | Rapid replacement after total storage failure | Large files are awkward for frequent backups and individual-file recovery |
tar archive |
Selected directories and their contents, such as /home/pi |
Can run while the system is up, but changing files may not be consistent | Portable, browsable file-level recovery | Only the paths you select are included; it is not automatically a complete system backup |
rsync |
Changed files in selected paths, preserving a mirror or history when configured | Usually low; pause services when consistency requires it | Frequent scheduled copies to another disk or mounted share | Does not by itself create an application-consistent database dump |
| raspiBackup | dd, tar or rsync-based Raspberry Pi backups, with retention and multiple destinations |
Depends on mode and whether containers are stopped | Repeatable full-system or incremental protection | Restore requirements vary by backup type, boot mode and current release |
A single image protects against a catastrophic storage failure but does not provide convenient history. A scheduled file backup is easier to run often but cannot recreate an entire bootable device unless you deliberately include all required state. Using both addresses those different failure modes.
Inventory every service before copying anything
Make an inventory on the Pi and store it in the backup destination. For each service, record its name, deployment directory, image tag or version, exposed ports, dependencies, persistent paths, database type and restore notes.
Recommended Free Tools
Deployment and configuration files
- Compose files or other container-deployment definitions.
.envfiles and separate environment files containing non-secret settings.- Reverse-proxy, TLS and DNS configuration.
- Systemd unit files, cron entries and scripts that start, stop or update services.
- Package lists, mount definitions and any custom kernel or boot configuration.
Protect secrets separately when appropriate. An encrypted archive is useful, but restoration also requires the encryption key or password. Store recovery instructions where an operator can reach them if the Pi itself is unavailable.
Bind mounts and named volumes
A bind mount stores data in an ordinary host directory; a named volume is managed by the container engine. Neither is recreated merely by pulling the container image. Locate both kinds of storage from your deployment files and from the running containers. A useful inspection command is docker inspect <container-name>; review its Mounts section and write down each source path and destination.
Back up the host directories used as bind mounts. For named volumes, use the service’s documented export method or mount the volume into a temporary helper container and copy its contents while the application is stopped. Do not delete or prune a volume until you have verified an independent copy.
Databases and changing state
Databases need special handling. A raw directory copy taken while pages are being written may be unusable even if every file appears in the archive. Consult the application’s own documentation for a logical dump, snapshot or quiescing procedure. If no safe online method exists, stop the service, perform the dump or copy, then start it again.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →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.
Keep the database export alongside the deployment files and persistent directories, and record the export date and database version. A system image can preserve a point-in-time database directory, but it should not replace an application-specific dump when the service documents one.
Create a whole-card image for disaster recovery
The Raspberry Pi Official Magazine describes a complete SD-card image as the simplest whole-device method. The documented process is offline: shut the Pi down, remove the card, connect it to another computer with a card reader and read the correct block device into an image file.
- Stop services cleanly and run
sudo shutdown -h now. Wait until activity LEDs stop before disconnecting power. - Remove the SD card and connect it to a Linux, macOS or Windows computer with a suitable reader.
- Identify the card by capacity and model. On Linux, inspect
lsblkbefore and after inserting it; never assume a name such as/dev/sdbis correct. - Unmount any partitions the desktop has opened automatically.
- Read the card into an image. On a Linux workstation, the pattern is
sudo dd if=/dev/sdX of=raspberry-pi-YYYY-MM-DD.img bs=4M status=progress conv=fsync, replacing/dev/sdXonly after checking the device listing. - Safely eject the card, then copy the image to a separate disk or network destination. Keep a checksum if your workflow supports one.
The image is a snapshot of the card, including unused space, so its file can be large. It is not a substitute for frequent database exports or small file-level restores. Keep the source and destination roles unmistakable: reversing them can overwrite the wrong disk.
Writing an image to replacement media
- Choose a replacement card or disk at least as large as the original image’s required capacity and compatible with the Pi’s boot method.
- Connect it to the recovery computer and identify it again by capacity and current device listing.
- Unmount its partitions.
- Write the image with an imaging application or the reverse
ddoperation, for examplesudo dd if=raspberry-pi-YYYY-MM-DD.img of=/dev/sdY bs=4M status=progress conv=fsync. - Wait for the write and flush to finish, safely eject the media and install it in the Pi.
- Boot with network access disabled if you need to prevent old services from immediately sending notifications or changing remote data. Confirm local access first, then reconnect and check each service.
Always verify /dev/sdY immediately before writing. A wrong destination can destroy another partition or an unrelated disk.
Use archives and scheduled copies for selective recovery
A compressed archive
The Raspberry Pi guide demonstrates archiving /home/pi with tar and copying the result to removable storage. That is convenient for files kept in the home directory, but it does not include every system path, Docker volume or database unless those locations are explicitly included.
A representative command is tar -czpf /mnt/backup/pi-home-YYYY-MM-DD.tar.gz /home/pi, where /mnt/backup is a mounted backup destination. Exclude cache directories and transient files when appropriate, and check that the archive lists the paths you expect with tar -tzf. Do not archive a live database directory unless the database documentation says that is safe.
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.
Incremental copies with rsync
rsync copies changed files instead of recopying an entire tree. A basic pattern is rsync -aH --delete /srv/self-hosted/ /mnt/backup/self-hosted/. The trailing slashes matter, and --delete removes files at the destination that no longer exist at the source, so test without that option first and keep versioned destinations if accidental deletion is a concern.
Run scheduled copies from cron or a system timer after deciding which services can remain online. For databases and rapidly changing application stores, stop the service or create its logical dump before the copy. Keep logs and alert on failures; a job that silently stops running is not a backup plan.
Graphical scheduling
Déjà Dup is described as a graphical option that can schedule backups and restore to the original or a selected location. The guide lists local flash storage, SSH, FTP and Amazon S3 among possible destinations and recommends setting an encryption password in its example. Availability and settings can change between Raspberry Pi OS releases, so confirm the installed version’s destination support before relying on a particular workflow.
Protect Docker deployments correctly
A container image contains application software, not the mutable data written after the container starts. Docker’s documentation uses Docker Desktop, not Raspberry Pi Docker Engine, but the underlying distinction is useful: persistent volumes and bind mounts must be protected separately, and the Compose definition is needed to recreate containers with their configuration.
What to include
- The complete Compose project directory, including Compose files and environment files.
- Every bind-mounted host directory.
- Every named volume that contains configuration, uploads, indexes, keys or databases.
- Images or exact image tags when reproducibility matters; otherwise record the tag and registry location.
- Custom networks, reverse-proxy configuration and certificates.
- Service-specific dumps made with the application’s supported tool.
Keep a plain-text inventory mapping each container to its persistent paths. If a Compose file uses relative paths, preserve the project directory structure so those paths resolve identically during restoration.
Coordinate running containers
Stopping containers briefly reduces the chance of copying half-written files. raspiBackup documents an extension that can stop Docker containers before a backup and start them afterward. Treat that as orchestration, not as proof that every database is consistent: follow the application’s own dump or shutdown procedure as well.
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
Before scheduling a stop-and-copy window, test that dependencies restart in the correct order and that clients reconnect. A backup that leaves a database stopped or a reverse proxy misconfigured needs immediate alerting and a rollback plan.
Use raspiBackup for repeatable Raspberry Pi backups
raspiBackup documents three backup types: dd and tar create full backups, while its rsync mode makes a complete initial copy and later incrementals using hard links. It supports configurable history, including a grandfather-father-son rotation, and can operate in regular full-system or partition-oriented modes.
Destinations documented by the project include local USB media, external disks and SSDs, SMB and NFS shares, SSHFS, WebDAV and other Linux-mountable locations. The project also documents restoring to an SD card, USB disk, SSD or NVMe SSD. Exact options and restore steps depend on the current release, device, boot mode and selected backup type, so use the live raspiBackup documentation for command syntax.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsPlan retention and destinations
- Keep at least one recent full-system recovery point.
- Retain older points when configuration changes or updates may need rollback.
- Use a destination that is not permanently attached if ransomware or accidental deletion is part of your threat model.
- Keep enough capacity for the history you configure; the documentation does not prescribe a universal size.
- Record which backups are
dd,tarorrsync, because their restore environments differ.
Restore to a replacement device
Image restore
For an image, the recovery computer writes the saved image to replacement media as described earlier. The Pi should be powered off while you exchange storage. After booting, check filesystem expansion, mounts, network identity and scheduled jobs before starting every container. If the replacement device is larger, expand partitions only after confirming the image boots normally.
raspiBackup tar or rsync restore
The raspiBackup restore guide requires the target device to be separate from the operating system that is currently running. Its tar and rsync restores require Linux; the documentation recommends using a Raspberry Pi OS system as the recovery environment.
- Boot a separate, compatible Raspberry Pi OS recovery system or use another Linux computer.
- Attach the backup destination and the blank target SD card, USB disk, SSD or NVMe SSD.
- List devices and partitions, then identify the target by model and capacity. Device names can change between boots.
- Unmount target partitions and confirm that the running recovery system is not located on the target.
- Follow the current raspiBackup restore procedure for the selected backup type.
- After the restore completes, shut down the recovery system, move the target device to the service Pi and boot it.
- Validate mounts, container startup, database integrity and external access before declaring recovery complete.
Never restore over the running recovery operating system. A mistaken target assignment can overwrite the recovery disk or another attached partition.
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.
Restore one service without rebuilding the Pi
- Stop only the affected service and its dependents.
- Preserve the failed data directory by renaming it rather than deleting it.
- Restore the Compose project, environment files and bind-mounted directories to their original paths.
- Recreate the named volume if necessary, then import the service’s database dump or supported backup.
- Start the service and inspect logs, health checks, permissions, ownership and network connectivity.
- Test authentication, recent records, uploads and background jobs before allowing normal traffic.
Keep the old directory until users confirm that the restored service is complete. This gives you a fallback if the wrong backup version was selected.
Free tools Windows power users keep installed
One-click scans. No signup required.
Test that backups are usable
A successful backup job proves only that files were copied. Schedule a recovery rehearsal on spare media or a separate target. Use a small service first, then a full-system image when practical.
- Confirm the backup destination is readable from a different machine.
- List archives and check that expected Compose files, mounts and exports are present.
- Verify that encrypted backups can be decrypted with the recorded key.
- Boot an image or restore a file-level backup to separate media.
- Measure whether the restored services meet your acceptable downtime and data-loss window.
- Update the inventory when paths, containers, databases or boot devices change.
No reviewed source publishes a universal restore-success rate, backup duration or storage-failure statistic. Your own rehearsal is therefore the meaningful evidence that a particular backup set works for your Pi and services.
Troubleshoot common failures
The restored Pi does not boot
- Recheck that the image was written to the whole device, not a partition such as
/dev/sdY1. - Confirm the replacement media is compatible with the Pi model and boot firmware.
- Compare the image’s partition table with the target and repeat the write if the source or destination was misidentified.
Containers start but show empty settings
- Inspect the Compose file’s bind-mount paths and named-volume declarations.
- Check that the restored files are owned by the user expected by the container.
- Verify that the Compose project was launched from the directory assumed by relative paths.
A database reports corruption
- Stop the application before attempting another file copy.
- Use the application’s supported dump or restore utility instead of replacing live database files blindly.
- Restore the newest known-good export and record which later transactions cannot be recovered.
The backup job is too slow or fills the destination
- Use
rsyncincrementals or retention limits rather than keeping unlimited full images. - Exclude caches and reproducible downloads while retaining user data and configuration.
- Move older recovery points to a larger external disk or a mounted network destination.
A practical operating schedule
After every major configuration change, capture the Compose files, environment files and affected service data. On a regular schedule, create database exports and run an incremental rsync or raspiBackup job. At a less frequent interval, make an offline whole-card image so that the operating system and boot configuration have a known recovery point.
Use an external USB SSD, USB flash drive or external disk sized for the history you intend to retain; raspiBackup documents these as local destination categories and as possible restore targets. A USB microSD card reader is useful for the offline imaging workflow. No particular model or performance level is established here, so verify compatibility, capacity and availability for your Pi.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Label each backup with the date, method, source device and encryption status. Keep the recovery notes, credentials needed to unlock encrypted archives and a current device map in a location separate from the Pi. The result is a layered plan: an image for total replacement, file and configuration copies for selective repair, and application-aware exports for data that must remain consistent.
Quick Recap
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.
