Free tools Windows power users keep installed
One-click scans. No signup required.
Portainer’s built-in backup is not a complete Docker backup. It downloads a password-protectable tar.gz archive of Portainer’s /data volume. That archive preserves Portainer configuration, its database, and stack files deployed through Portainer, but it does not contain running containers, services, named-volume contents, bind-mounted application data, or Docker and Kubernetes configuration stored outside Portainer’s database.
Antihost offers VPS plans with one-click Docker, NVMe storage and a 14-day free trial.
A dependable recovery plan therefore has three parts: download Portainer’s configuration archive, preserve every stack definition and its deployment inputs, and back up application data separately with database-consistent procedures. The steps below show what belongs in each part and how to restore Portainer on a new host.
As an Amazon Associate I earn from qualifying purchases.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →What Portainer’s built-in backup contains
An administrator starts the backup from Settings > Back up Portainer. Portainer creates a tar.gz archive of its /data volume. You can enable password protection before downloading it, which is appropriate whenever the file could leave the host or be handled by someone outside the administrator group.
According to Portainer’s documentation, the archive is intended only for Portainer configuration. Its versioned FAQ clarifies that the archive includes the Portainer database and stack files deployed using Portainer. Those records can include access-control information, environment metadata and the definitions Portainer manages.
#1 Best Overall
- Easily store and access 2TB to content on the go with the Seagate Portable Drive, a USB external hard drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
| Item | Included in the Portainer archive? | What to do |
|---|---|---|
| Portainer database and configuration | Yes | Download the archive after material changes and retain dated copies. |
| Stack files deployed through Portainer | Yes | Keep the archive, but also maintain an independently recoverable copy of each definition. |
| Running containers and services | No | Redeploy them from preserved stack definitions after restoring Portainer. |
| Named-volume contents | No | Back up the contents of every volume that holds application state. |
| Bind-mounted files and directories | No | Back up each mounted path separately, including databases, uploads and certificates. |
| Docker or Kubernetes configuration outside Portainer’s database | No | Include that platform configuration in your host or cluster backup plan. |
The practical boundary is configuration recovery versus workload-data recovery. Restoring the archive gives you Portainer’s records and definitions; it does not recreate the workloads or repopulate their storage.
Build an inventory before choosing a backup schedule
Start with an inventory that another administrator could use during an outage. Record each environment connected to Portainer, every stack, all named volumes, every bind-mounted path, secrets and external networks. Note which stacks were entered in the Web Editor, uploaded as Compose files or deployed from Git.
- Environments: identify standalone Docker hosts, Swarm environments and Kubernetes environments, along with the address or connection method Portainer uses.
- Stacks: record the stack name, deployment type, source location and the branch or tag used when Git supplied the files.
- Storage: map each service to its named volumes and bind mounts. Mark which locations contain a database, user uploads, certificates or other irreplaceable state.
- Secrets and variables: document where non-secret variables are stored and how secret values are supplied. A stack file that refers to an unavailable secret is not sufficient for recovery.
- Networks: list external networks that a stack expects. These may need to be recreated before a deployment can start.
- Placement: document the host and persistent-storage location of the
portainer_datavolume.
This inventory turns a Portainer archive into a usable recovery plan instead of an unexplained file that may be impossible to apply under pressure.
Back up Portainer configuration
Download a protected archive
- Sign in to Portainer with an administrator account.
- Open Settings.
- Choose Back up Portainer.
- Enable password protection if the archive may be copied to removable, shared or off-site storage.
- Download the generated
tar.gzfile. - Give it a dated, unambiguous name and record the password in an approved secrets system rather than beside the archive.
Keep several dated copies so an unnoticed configuration change does not overwrite the last known-good state. Create a new archive after material changes such as adding an environment, changing access control, modifying a Portainer-managed stack or migrating a deployment.
Store more than one copy
A local download protects you from a Portainer configuration mistake but not from loss of the host itself. Copy the archive to separate storage, such as a USB external hard drive, and maintain an off-site or S3-compatible copy when your recovery plan requires geographic separation. Business Edition administrators can configure S3 or an S3-compatible host for off-site Portainer backups.
Password protection addresses unauthorized access to the archive; it does not replace isolation, retention or restore testing. Restrict who can read both the archive and the password, and make sure the password can still be obtained if the original administrator is unavailable.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteRank #2
- Easily store and access 5TB of content on the go with the Seagate portable drive, a USB external hard Drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
Preserve stack definitions as an independent source of truth
The archive can preserve stack records and files deployed through Portainer, but a repository or separately retained Compose file gives you a recovery path that does not depend on successfully reading Portainer’s database. Preserve every stack definition in the form in which it can be redeployed.
Web Editor and uploaded Compose stacks
For a stack entered in Portainer’s Web Editor or uploaded as a Compose file, export or copy the complete definition into a controlled repository. Include the service definitions, image references, volume declarations, networks, health checks and restart policies that the stack requires. Keep the non-secret environment values with the definition, while storing secret values in your approved secret-management process.
Git-deployed stacks
For a Git-managed stack, the repository is the authoritative copy of the Compose files. Protect the repository itself, the deploy key or other authentication material, the branch or tag Portainer deploys, and the environment-variable material required by that revision. Git-managed Compose files are edited in the repository, so a Portainer archive should not be treated as a substitute for repository retention.
Record the exact branch or tag used for each deployment. Without that reference, a later checkout may produce a different stack even though the repository still exists. Preserve access to the repository independently of the Portainer host so a destroyed host does not also remove the deployment source.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Why the archive and repository should coexist
The archive is valuable because it captures Portainer’s database and its managed stack records in one operation. The repository is valuable because it is inspectable, versioned and recoverable without first bringing Portainer’s database back. Keeping both covers configuration corruption, accidental edits and a complete host loss without forcing one artifact to perform both jobs.
Back up named volumes and bind mounts separately
Docker defines named volumes as persistent data stores. Portainer’s configuration archive does not contain their contents. A volume may be shared by several services through Compose declarations, so the backup plan must include the volume itself and the ownership and permissions expected by every service that uses it.
Rank #3
- Easily store and access 1TB to content on the go with the Seagate Portable Drive, a USB external hard drive.Specific uses: Personal
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop. Reformatting may be required for Mac
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
Identify state that cannot be recreated
For each stack, inspect its volume declarations and bind mounts. Prioritize locations containing:
- Databases and their transaction or journal files
- User uploads and generated media
- TLS certificates and private keys
- Application configuration created at runtime
- Any other state that is not present in the image or source repository
Do not assume that a volume is disposable because its name looks generic. Confirm which service writes it and whether another service reads it.
Use an application-consistent method
Copying files from a live database directory can produce an unusable backup. Stop or quiesce each database when the database vendor requires it, or use the vendor’s supported dump or snapshot procedure. Apply the same discipline to other applications whose files can change while an archive is being made.
After creating an archive, verify that it can be read and that its expected files are present. A successful copy operation proves only that bytes were copied; it does not prove that a database can open the restored files or that a certificate and its permissions survived.
Record ownership and mount expectations
Alongside each data archive, record the source path or volume name, the service that consumes it, required ownership and permissions, and whether it is mounted read-only or read-write. These details prevent a technically complete restore from failing because the application cannot read or write its data.
Protect Portainer’s own persistent placement
The Portainer archive is stored separately from the running service, but the service still needs persistent storage for its /data volume. Document where the portainer_data volume lives and how it is attached to the Portainer deployment.
Rank #4
- 【Versatile Storage Expansion – For Gaming, Work & Everyday Use】 Running out of space on your PS5 or Xbox Series X/S? This external hard drive lets you store and play PS4 / Xbox One games directly, instantly freeing up your console’s internal storage for next‑gen titles. At the same time, it handles work file backups, media libraries, and cross‑device data transfers with ease. One drive, all your needs. *（Note: PS5 / Xbox Series X|S games cannot be run or stored directly from the external hard drive. However, by offloading your PS4 / Xbox One games, you can free up valuable space for newer titles.）*
- 【Patented Silicone Sleeve – Data Protection You Can Count On】 Worried about drops? We’ve got you covered. The patented built‑in silicone sleeve acts like a shock‑absorbing armor, cushioning your drive against bumps and falls. Whether it’s important work documents, precious family photos, or hard‑earned game saves, your data deserves this level of protection.
- 【Plug & Play, Compatible with Computers & Consoles】 No complicated setup—just plug in and go. Works seamlessly with Windows, Mac, and Linux computers, as well as PS4, PS5, Xbox One, and Xbox Series X/S. Process files at the office, back up data at home, or enjoy gaming in your downtime—one drive handles all your devices, simply and hassle‑free.
- 【USB 3.0 Ultra‑Fast Transfer – No More Waiting】 Tired of watching progress bars crawl? With USB 3.0 speeds up to 5Gbps, large files transfer in seconds. Whether you’re moving work documents, transferring hundreds of gigs of games, or backing up a year’s worth of photos, you get more done in less time.
- 【Sleek, Lightweight, and Ready to Go】 Weighing just 0.16 kg—lighter than a can of soda—this compact drive features a stylish mirror‑and‑frosted finish. Toss it in your bag and go, whether you’re heading to the office, visiting a friend for a gaming session, or giving a presentation on the road.
Swarm placement matters
In Swarm, constrain Portainer to a node that has the persistent data, or use storage available to the service wherever it is scheduled. If Portainer is rescheduled onto a node without the original persistent volume, it can appear to be a fresh installation. That behavior can look like data loss even though the old volume still exists on another node.
Include the placement rule or storage dependency in the deployment documentation. A restore plan that recovers the archive but starts Portainer against a new, empty volume will not show the expected configuration until the correct persistent storage is attached.
Restore Portainer on a new server
Portainer documents restoration to a fresh instance with an empty data volume. Treat the restore as a staged operation: recover Portainer’s configuration first, reconnect environments, then recover stacks and application data.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →- Prepare an isolated host. Install a fresh Portainer instance and provide an empty data volume for it. Do not point the new instance at an unrelated, pre-populated data directory.
- Keep the required artifacts together. Obtain the selected Portainer
tar.gzarchive and its password, the environment inventory, stack definitions or repository access, secret and variable material, network notes, and the separate volume and bind-mount backups. - Restore during initialization. Use Portainer’s documented initialization restore flow to import the archive into the fresh instance. The archive restores Portainer’s database and managed stack records; it does not start the old workloads or restore application files.
- Reconnect environments. Re-establish access to each Docker, Swarm or Kubernetes environment using the connection details recorded in the inventory. Confirm that Portainer can communicate with each one before deploying stacks.
- Validate the recovered records. Check users and access control, environment metadata and the list of stacks. If a stack was Git-managed, verify the repository, deploy key and branch or tag before attempting deployment.
- Redeploy stacks. Deploy from the preserved Web Editor or Compose definition, or from the recorded Git revision. Recreate required external networks and confirm that image and secret prerequisites are available.
- Restore application data separately. Put named-volume contents and bind-mounted files back in their intended locations, preserving ownership and permissions. Restore databases using the consistency method selected for that database.
- Run functional checks. Confirm that services start, databases open, uploads are visible, certificates are accepted and inter-service networks work. Check logs for permission, missing-secret and connectivity errors.
Performing these stages in an isolated host lets you discover a bad archive, missing variable or incomplete volume backup without disrupting the production environment.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Compare backup designs by recovery capability
A useful comparison is not “which file is easiest to download?” but “which failure can this design actually recover from?” Evaluate every design on four axes.
| Axis | Questions to answer |
|---|---|
| Declarative, versioned definitions | Are stack files retained outside Portainer, and can you identify the exact revision, branch or tag used? |
| Application consistency | Were database and volume backups made with the application quiesced or with its supported export or snapshot procedure? |
| Isolation and off-site copies | Do copies survive loss of the Portainer host, and is an off-site or S3-compatible copy required by your recovery plan? |
| Restore rehearsal | Have you started a fresh Portainer instance, imported an archive, reconnected environments, redeployed stacks and restored data successfully? |
A configuration-only plan scores well for recovering Portainer settings but poorly for recovering application state. A data-only plan may preserve databases while leaving you without the stack definitions and environment metadata needed to redeploy them. The complete design deliberately covers both.
Best Value
- High capacity in a small enclosure – The small, lightweight design offers up to 6TB* capacity, making WD Elements portable hard drives the ideal companion for consumers on the go.
- Plug-and-play expandability
- Vast capacities up to 6TB[1] to store your photos, videos, music, important documents and more
- SuperSpeed USB 3.2 Gen 1 (5Gbps)
Test and maintain the plan
Run a periodic restore rehearsal
On an isolated host, deploy a fresh Portainer instance with an empty data volume and use a selected archive. Reconnect a non-production environment, redeploy representative stacks and restore representative volume data. Confirm that the result is usable rather than merely present.
Recommended Free Tools
Check every artifact, not just the download
- Open each downloaded archive and verify that it is readable.
- Confirm that the password is available through the approved secrets system.
- Check that repository credentials, deploy keys and selected revisions still work.
- Verify that volume archives contain the expected directories and files.
- Confirm that database backups pass the database’s own validation or restore check.
- Review whether external networks, certificates and environment variables are still documented.
Update after operational changes
Refresh the inventory and take a new Portainer archive after adding or removing environments, changing stack definitions, rotating certificates, altering access control or moving persistent storage. Recheck Swarm placement whenever the node or storage topology changes.
Common failure modes and the corrective action
“The Portainer restore succeeded, but my containers are missing.”
This is expected when only the configuration archive was restored. Reconnect the environments, then redeploy the stacks from their preserved definitions. The archive does not recreate running containers or services.
“The stack appears, but the application starts empty.”
The stack record is not the application’s data. Restore the named volumes and bind-mounted paths separately, then verify that the mounts, ownership and permissions match the stack’s expectations.
“A Git stack cannot be redeployed.”
Check repository access, the deploy key, the recorded branch or tag and the required environment-variable or secret material. The Compose files may be intact while one of those deployment inputs is unavailable.
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 errors“Portainer looks like a new installation after a Swarm reschedule.”
Portainer likely started on a node without the persistent portainer_data volume. Apply the documented placement constraint or make the storage available to the service, then start Portainer against the original persistent data.
“The volume archive exists, but the database will not open.”
Revisit the backup method. The database may have been copied while active and inconsistent. Use the database vendor’s supported dump, snapshot or quiesced-file procedure and validate the result in an isolated restore.
Quick Recap
A concise operational checklist
- Inventory environments, stacks, volumes, bind mounts, secrets and external networks.
- Download a password-protected Portainer archive from Settings > Back up Portainer after material changes.
- Retain several dated copies and place copies on separate and, where required, off-site storage.
- Keep Web Editor and uploaded Compose definitions in a controlled repository.
- Protect Git repositories, deploy keys, selected revisions and variable or secret material.
- Back up every stateful named volume and bind-mounted path independently.
- Use database-consistent procedures and verify that archives can be read and restored.
- Document the location and placement requirements of
portainer_data. - Rehearse a fresh-instance restore, environment reconnection, stack deployment and data recovery.
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.
