Use Proton Drive CLI as a scheduled, one-shot backup job rather than a continuously watching sync process. For most off-site backups, start with a daily or weekly run, select create-new-revision for changed files, and verify exclusion behavior in the help for the exact binary you installed. Proton does not publish a universal numeric revision-retention period: older versions consume account storage and are limited by your plan.
Your schedule should match the amount of data you can afford to lose between successful runs. Keep credentials in an operating-system secret store (or the documented pass store for headless jobs), emit --json output for monitoring, and rehearse a filesystem download restore. A backup that has never produced a verified restore is only an assumption.
As an Amazon Associate I earn from qualifying purchases.
What Proton Drive CLI does—and what it does not do
Proton describes the CLI as an atomic command-line tool: it starts one operation, performs it, and exits. It does not watch a local folder continuously. Recurrence therefore comes from your operating system or an external job runner, not from a resident Proton process. The product launch announcement explains this distinction between the CLI and continuously running sync clients: Proton Drive CLI: Use Drive from your terminal.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
That design separates three decisions that are often confused:
#1 Best Overall
- Get NVMe solid state performance with up to 1050MB/s read and 1000MB/s write speeds in a portable, high-capacity drive(1) (Based on internal testing; performance may be lower depending on host device & other factors. 1MB=1,000,000 bytes.)
- Up to 3-meter drop protection and IP65 water and dust resistance mean this tough drive can take a beating(3) (Previously rated for 2-meter drop protection and IP55 rating. Now qualified for the higher, stated specs.)
- Use the handy carabiner loop to secure it to your belt loop or backpack for extra peace of mind.
- Help keep private content private with the included password protection featuring 256‐bit AES hardware encryption.(3)
- Easily manage files and automatically free up space with the SanDisk Memory Zone app.(5). Non-Operating Temperature -20°C to 85°C
- Schedule: how often a successful upload should create a new recovery point.
- Scope: which local files are allowed into the upload, including any exclusions supported by your installed version.
- History: what the CLI does when a remote file already exists and the local copy changed.
Michal Hořejšek, lead of Proton’s Drive Foundation team, summarizes the responsibility in Proton’s backup guide: “The CLI is not a complete backup solution on its own. You still decide what to back up, how often, how many versions to keep, and how to test your restores.” Read the full guidance at How to automate offsite encrypted backups with Proton Drive CLI.
Choose a schedule from your recovery-point requirement
Think in terms of the maximum interval of local changes you could lose after a disaster. If losing a week of work is acceptable, a weekly run may be sufficient. If losing one business day is unacceptable, use a daily run and make sure the job has enough time and bandwidth to finish before the next one. Also account for how quickly the source data changes, the volume of each upload, available upload bandwidth, and whether previous jobs reliably complete.
Proton’s current guidance says daily or weekly off-site backups are generally enough and warns against needlessly high-frequency schedules such as every 60 seconds. A very short interval can create overlapping jobs, excessive traffic, and unnecessary revisions without improving recoverability if the previous run has not completed.
| Cadence | Appropriate when | Advantages | Risks and checks |
|---|---|---|---|
| Weekly | Your data changes slowly or a several-day recovery-point gap is acceptable. | Low traffic and simple operations. | Changes made after the last run remain unprotected for several days; confirm that the job completes before the chosen day ends. |
| Daily | Typical personal, project, and small-business files where one day of possible loss is the target. | Matches Proton’s stated off-site-backup guidance while limiting upload volume. | Confirm enough time for the full scan and upload, and alert on failures rather than assuming a scheduled task ran successfully. |
| More often than daily | A documented workload requirement justifies a smaller recovery-point gap. | Less time between successful snapshots. | Higher traffic and more revisions; measure completion time and avoid launching a new run while another is active. Proton specifically cautions against extreme frequency such as every minute. |
Do not equate a frequent start time with a frequent successful backup. A job that starts every hour but fails authentication, times out, or is terminated by the next invocation may protect less data than a daily job that completes and is monitored.
Schedule the one-shot command on Linux or macOS
Proton documents cron as the normal scheduler on Unix-like systems. First, run the upload manually as the same account that cron will use. Confirm that the remote destination is correct, unchanged files are skipped, and the command exits successfully. Use the installed binary’s help to confirm argument order and available flags before putting it into cron:
Rank #2
- 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.
proton-drive filesystem upload --helpThe following illustrates a nightly run. The local and remote paths are examples; substitute paths that exist in your environment and keep the conflict strategy appropriate for backups:
proton-drive filesystem upload "/srv/project-data" "/Backups/project-data" --file-conflict-strategy create-new-revision --jsonAfter you have validated the command interactively, create a wrapper script. A wrapper gives you one place to set the working directory, capture logs, prevent overlapping runs, and return the CLI’s exit status. Keep the script readable and protect it with normal filesystem permissions.
#!/bin/sh
set -eu
exec /usr/local/bin/proton-drive filesystem upload "/srv/project-data" "/Backups/project-data" --file-conflict-strategy create-new-revision --jsonAdd a cron entry with an explicit, stable path to the wrapper. This example starts at 02:00 every day and appends standard output and errors to a log:
0 2 * * * /usr/local/sbin/proton-drive-backup.sh >> /var/log/proton-drive-backup.log 2>&1Check the cron service’s own logs and the wrapper log after the first run. If the command works in an interactive shell but fails under cron, compare the user account, PATH, home directory, network availability, and credential-store access. A desktop keyring may depend on an active graphical session; headless jobs should use the credential method Proton documents for that environment.
Schedule it with Windows Task Scheduler
On Windows, Proton’s guide points to Task Scheduler. Open Task Scheduler, choose Create Task… rather than a disposable basic task, and configure the task deliberately:
Rank #3
- Solid state performance with up to 800MB/s read speeds in a portable drive. (Based on internal testing; performance may be lower depending on host device, interface, usage conditions and other factors. 1MB=1,000,000 bytes.)
- Back up your content and memories on a storage solution that fits seamlessly into your mobile lifestyle.
- Take it with you on your adventures—up to two-meter drop protection means this durable drive can take a beating. (Based on internal testing.)
- Secure it to your belt loop or backpack for extra peace of mind thanks to the tough rubber hook.
- From SanDisk, a brand professional photographers trust to take on assignments.
- On General, give the task a descriptive name such as “Proton Drive off-site backup.” Select the account that owns the Proton credentials and choose Run whether user is logged on or not when the machine must back up unattended.
- On Triggers, create a daily or weekly trigger at a time when the computer is powered, connected, and unlikely to be under heavy load.
- On Actions, choose Start a program. Point Program/script to the full path of
proton-drive.exe. Put the verified upload command and its flags in Add arguments; do not rely on an interactive shell profile. - On Conditions, decide whether the task may run on battery and whether it should wait for a network connection. A laptop-only backup that is blocked whenever it is unplugged may silently miss its recovery point.
- On Settings, enable a useful failure response, set a reasonable execution time limit, and prevent overlapping instances. Save the task, enter credentials if Windows requests them, then use Run to test it immediately.
Review Last Run Result, the task history, and the JSON log produced by the CLI. A green scheduler status only proves that Windows launched the process; it does not prove that every file reached the remote destination.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows 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 reinstallHandle exclusions conservatively
The official support page and CLI README reviewed for this guide do not establish a universal exclusion flag or pattern syntax. Do not copy an --exclude option, glob format, or rclone configuration from another tool and assume Proton Drive CLI accepts it. Start with the help for the installed binary:
proton-drive filesystem upload --helpCompare that output with the version you deploy and record the exact flags in your wrapper or operations notes. Proton’s support instructions are available at Using Proton Drive CLI. The command surface can change, so an exclusion recipe found in an older post may be wrong for your installation.
Test an exclusion before trusting it
- Create a small test tree containing files that must be uploaded, files you intend to omit, nested directories, hidden files, and names with spaces.
- Run the upload to a temporary remote folder, using only the exclusion syntax shown by your installed help.
- List or inspect the resulting remote tree and compare it with your expected inclusion list.
- Modify one included file and one excluded file, run the command again, and verify that only the intended change appears remotely.
- Save the test result with the backup configuration so a future CLI upgrade can be checked against the same cases.
Exclusions reduce transfer volume and can keep caches, build artifacts, or disposable data out of an archive. The failure mode is more serious than extra bandwidth: an overly broad rule can silently prevent an important document from ever being uploaded. If a dataset matters during recovery, include it unless you can demonstrate that it is recreated elsewhere and document that decision.
Choose conflict behavior and understand revision retention
The CLI skips unchanged identical files, reducing needless bandwidth. When a local file differs from the remote copy, the --file-conflict-strategy setting determines whether the old cloud content remains available.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Rank #4
- MADE FOR THE MAKERS: Create; Explore; Store; The T7 Portable SSD delivers fast speeds and durable features to back up any endeavor; Build your video editing empire, file your photographs or back up your blogs all in an instant
- SHARE IDEAS IN A FLASH: Don’t waste a second waiting and spend more time doing; The T7 is embedded with PCIe NVMe technology that brings fast read and write speeds up to 1,050/1,000 MB/s¹, making it almost twice as fast as the T5
- ALWAYS MAKE THE SAVE: Compact design with massive capacity; With capacities up to 4TB, save exactly what you need to your drive – from large working files to game data and everything in between
- ADAPTS TO EVERY NEED: Whether using a PC or mobile phone, count on the T7 for extensive compatibility²; It’s a true team player when it comes to heavy-duty application usage or file-saving
- HI RESOLUTION VIDEO RECORDING: Record Ultra High Resolution (4K 60fs) videos directly onto the T7 Portable SSD with your favorite camera or mobile devices; Supports iPhone 15 Pro Res 4K at 60fps video and more³
| Strategy | What happens to changed content | Recovery and storage effect | Backup suitability |
|---|---|---|---|
create-new-revision |
The changed file is stored as a new revision of the existing remote file. | Prior content remains available subject to account limits; each revision consumes storage. | Proton recommends this strategy for backups because it preserves file history. |
rename |
A second copy is retained under a suffixed filename. | Both copies use storage, and the folder can accumulate names that are harder to interpret. | Useful when independent, separately named copies are preferred, but plan the naming and cleanup process. |
replace |
The remote file is overwritten. | The previous content is lost as a recoverable file version through this operation. | Not appropriate when historical recovery matters. |
skip |
An existing remote file is left untouched, even when the local file changed. | New local changes may never reach the backup. | Proton says this is not recommended for backups. |
Folder merge and file-level create-new-revision are used together in Proton’s backup example: the folder structure is merged while modified files gain revisions. Keep those concepts separate from a calendar-based retention policy. A revision is a stored historical state; it is not proof that the service offers a user-configurable “keep 30 days” or “keep 12 versions” rule.
Proton does not state a universal numeric revision window in the cited guidance. The number of versions available depends on your account plan and storage allowance, and revisions consume that storage. Check your current plan details and the behavior of the installed CLI before promising a retention period to yourself or an organization. If storage is tight, increasing schedule frequency or preserving every revision can fill the account faster than expected.
Store credentials safely for unattended jobs
Proton Drive CLI supports Windows, macOS, and Linux. The official SDK README documents operating-system secret stores by default and a pass credential-store option. Proton’s backup guide recommends pass for headless cron environments because desktop keyrings may require an active GUI session. Read the current implementation notes in the official repository: ProtonDriveApps SDK CLI README.
- Run the scheduler under a dedicated account with only the filesystem access required for the source data.
- Use the documented secret-store mechanism and verify that the scheduled account can unlock it without an interactive prompt.
- Do not put passwords or recovery secrets in the command line, cron file, Task Scheduler arguments, or captured logs.
- Avoid the
unsafe_filecredential store for routine backups; the SDK documentation describes it as intended for testing. - After rotating credentials, run the scheduled task manually and confirm that the monitoring path reports success.
Credential success is not upload success. Keep authentication checks, file-scope checks, and restore checks as separate tests.
Recommended Free Tools
Monitor every run with structured output
Add --json to produce structured output that another script can parse for status, counts, or failure alerts. Store the JSON with a timestamp and retain enough history to identify intermittent failures. At minimum, alert when the process exits nonzero, produces an authentication error, cannot reach the service, or reports that files were skipped unexpectedly.
Best Value
- 9.5X faster than hard disk drives with up to 1050MB/s read and 1000MB/s write, for significantly faster transfers
- Super-fast backups and instant storage expansion
- Built-in, double layer graphite sheets quickly conduct heat, enchancing heat dissipation to keep the drive cool, even during blazing fast transfers
- The drive is drop-resistant up to 2 meters for protection, ensuring durability for everyday and office use.
- Plug-and-play compatibility with a 2-in-1 USB-C/USB-A cable to easily use with your PC, Mac, tablet, smartphone, and more
Do not treat an empty change set as a failure by itself: an unchanged source tree may legitimately produce no new uploads. Conversely, a successful process exit does not prove that your exclusion rules selected the right files. Periodically compare a known manifest or sample of critical files with the remote tree.
Prevent overlapping jobs. If a large upload can run longer than the interval, configure cron, Task Scheduler, or your wrapper so a second instance waits or exits with a visible alert. Overlap can create confusing logs and unnecessary conflict operations.
Build and test a restore procedure
Proton recommends preparing a restore script based on proton-drive filesystem download and testing recovery regularly. Write the destination to a separate directory or spare system first; do not experiment by overwriting the only local copy of your data.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitches- Choose a representative restore set: several ordinary files, a deeply nested folder, a large file, a filename with spaces, and at least one file that has multiple revisions.
- Run
proton-drive filesystem download --helpand confirm the installed syntax, destination behavior, and JSON option. - Download the test set to an empty directory using the same credential context as the recovery account.
- Open files, compare sizes or hashes where appropriate, and verify permissions and names that matter to your application.
- Record the elapsed time, errors, and any manual steps. Update the script when the CLI or account configuration changes.
Schedule restore drills at a cadence that matches the importance of the data. A daily green upload is not useful if a damaged archive, inaccessible credential store, or misunderstood revision strategy makes recovery impossible.
Place Proton Drive in a 3-2-1 backup plan
Proton presents the 3-2-1 rule as at least three copies of your data, on at least two different media, with at least one copy off-site. Proton Drive can serve as the off-site copy, but it should not be the only copy. A separate local disk is one possible second medium; choose its capacity from the size of the dataset, expected revision growth, and budget rather than from a universal product recommendation.
For important data, combine the scheduled Proton upload with a local backup and test restores from both. Keep the local and off-site jobs independent enough that one credential problem, filesystem mistake, or accidental deletion does not remove every copy.
Quick Recap
Troubleshoot the common failure modes
| Symptom | Likely cause | Action |
|---|---|---|
| The command works in a terminal but not in cron. | Different user, PATH, home directory, network state, or unavailable desktop keyring. |
Use absolute paths, run as the scheduler’s account, inspect logs, and use the documented pass store for a headless setup when appropriate. |
| Changed files are missing remotely. | skip was selected, or an exclusion matched more broadly than intended. |
Review the conflict strategy, inspect upload help, and repeat the representative-tree test. |
| Storage grows faster than expected. | create-new-revision preserves changed content and revisions consume plan storage. |
Check account capacity and revision behavior; reduce unnecessary source data, not critical files, and choose a schedule that matches actual change rates. |
| Two jobs run at once. | The interval is shorter than the upload duration or the scheduler allows parallel instances. | Add a lock or scheduler setting that prevents overlap, then choose a cadence with enough completion margin. |
| The task reports success but recovery fails. | Restore has never been tested, the wrong remote folder was selected, or credentials differ during recovery. | Run a controlled filesystem download drill, inspect JSON and logs, and document the working restore command. |
A practical configuration checklist
- Define the maximum data-loss interval you can accept, then choose daily or weekly unless a documented workload requires otherwise.
- Verify the upload and download syntax with the installed binary’s
--helpoutput. - Use
create-new-revisionwhen preserving older file contents is part of the backup objective. - Record your account plan and available storage; do not promise a numeric revision-retention period that Proton has not documented.
- Test exclusions against a representative tree and re-test after CLI upgrades.
- Use an OS secret store or the documented
passmethod for headless operation, never routine plaintext test storage. - Emit
--json, retain logs, alert on nonzero exits, and prevent overlapping runs. - Perform and document a real restore before declaring the backup operational.
- Keep another copy on a different medium so the Proton account is one part of a 3-2-1 design, not the entire design.
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.
