The dependable Duplicacy workflow for a Linux VPS is: place the Linux executable on the server, select storage that survives a VPS failure, initialize an encrypted repository, schedule separate backup, integrity-check, copy and prune jobs, and regularly restore a test file. Duplicacy can write to cloud storage, a local disk or an SFTP server, so your design should normally keep the primary backup off the VPS itself.
Antihost offers Linux VPS plans with full root access, unlimited traffic on a 1 Gbps port and a 14-day free trial.
The original Backup ID, storage location, storage credentials and encryption password are recovery-critical. Record them securely before the first production backup; without the ID or credentials, moving the repository to a replacement server can become an avoidable emergency.
As an Amazon Associate I earn from qualifying purchases.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
What Duplicacy is doing on a Linux VPS
Duplicacy stores versioned snapshots of a directory rather than replacing one large archive on every run. The command-line program is the engine used by the graphical editions, and Linux Web Edition is distributed as an executable; there is no traditional package installer to run. You can put the executable on PATH and call it from an interactive shell, a script or a scheduler.
A typical VPS protection plan has four independent operations:
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
- Backup creates a new snapshot from the directories you selected.
- Check verifies that stored data and metadata can still be read and that the repository is internally consistent.
- Copy duplicates snapshots to another configured storage location, which is useful when one provider or server is unavailable.
- Prune applies retention rules and eventually removes data that no longer belongs to a retained snapshot.
Keeping these jobs separate makes failures visible. A successful backup does not prove that every chunk is readable, and a successful check does not create a new recovery point. Schedule each operation deliberately.
Choose Web Edition or the command line
Both interfaces use the same underlying backup engine. Choose the interface that matches how you operate the VPS rather than assuming that a web interface is automatically safer.
| Concern | Web Edition | CLI-driven operation |
|---|---|---|
| Scheduling | Job definitions for backup, check, copy and prune can be managed in the Web Edition interface. | Use cron, a system service timer or another scheduler around the executable. |
| Scripting flexibility | Good for repeatable settings, but changes are made through the application. | High: shell scripts can add pre-flight checks, logging, alerts and maintenance steps. |
| Unattended credentials | Credentials are stored and used by the Web Edition service; protect its data directory and administration account. | Credentials must be supplied through the CLI’s supported configuration or a protected automation mechanism; never put secrets in world-readable scripts. |
| Observability | Use the job history and status displayed by the Web Edition interface. | Capture standard output and errors, exit codes and scheduler logs, then alert on failures. |
| Licensing | Check the current Web Edition licensing terms before deploying it as a permanent service. | The command-line version is the operation engine and is suitable for direct, scripted use; confirm the applicable license for your installation. |
For a single VPS managed by a small team, Web Edition is convenient when you need a visible schedule and job history. CLI automation is often a better fit for infrastructure-as-code, immutable servers or environments where a web service would be another exposed component. You can also initialize and test a repository with the CLI and use Web Edition later, provided both use the same repository settings.
Decide where the backups should live
A backup on the same VPS is useful for a quick rollback but does not protect against deletion of the VPS, filesystem corruption, an account suspension or a regional outage. At least one destination should be outside the failure domain of the machine being protected.
| Destination | Geographic separation | Security and credentials | Durability, cost and bandwidth | Restore speed | Operational complexity |
|---|---|---|---|---|---|
| Cloud object storage | Usually easy to place in another region or provider; verify the selected region. | Client-side encryption is available and strongly recommended for cloud storage. Protect both the storage credentials and the Duplicacy encryption password. | Designed for durable remote storage, but recurring storage, request and possible egress charges depend on the service and retention policy. | Constrained by available download bandwidth and egress limits. | Low after credentials and a bucket or container are prepared; monitor quotas and lifecycle settings. |
| Another server or NAS over SFTP | Can be genuinely off-site if the machine is in another facility or region; a second disk in the same rack is not geographic separation. | Use a dedicated SFTP account with access limited to the backup directory and a key protected on the VPS. Ensure the remote folder exists when using the SFTP layout from the quick-start. | Uses the remote system’s disks and network; costs are predictable, but you must manage its capacity, updates and redundancy. | Often fast on a private or nearby network, subject to the link between sites. | Higher than managed object storage because you own the remote host, accounts and monitoring. |
| Local disk or mounted volume | None if it is attached to the same VPS host or facility; treat it as a convenience copy, not your only disaster-recovery copy. | Filesystem permissions and encryption of the volume become your responsibility. | Usually the lowest latency and simplest capacity model, but the disk can fail with the VPS or be deleted with it. | Fastest when the volume is local and available. | Simple to configure, weak as the sole recovery location. |
Before committing to a destination, estimate how much data changes between snapshots, how long you can tolerate a restore taking, and whether your network or provider charges for downloads. A second destination configured for a copy job can reduce dependence on one storage system.
Prepare the VPS and the backup identity
Use a dedicated backup identity
Run backups with a service account that can read the application and data directories but does not grant unnecessary administrative access. If the service must read protected files, grant only the required group membership or narrowly scoped permissions. Keep the repository’s configuration and logs out of public web roots.
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 matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
Define what is in scope
List the directories that make the service recoverable: application code, uploads, user data, configuration, TLS material, scheduled-job definitions and database dumps. A filesystem snapshot alone may not be a consistent database backup. Schedule a database’s native dump or quiesce step before Duplicacy reads the dump directory, and test restoring that dump separately.
Check practical prerequisites
- Leave enough free disk space for temporary files and normal VPS operation; a backup should not fill the root filesystem.
- Confirm outbound connectivity to the selected cloud or SFTP endpoint and that firewall rules permit it.
- Use stable time settings so logs and retention decisions are easy to interpret.
- Decide where scheduler logs and failure alerts will go before enabling unattended jobs.
- Document the Backup ID, storage URL, destination path and the person or system that holds the encryption password.
Install the Linux executable
Download the Linux build appropriate for your architecture from the vendor’s distribution channel, place the executable in a protected directory and give it execute permission. Web Edition on Linux is executable-based, so no package-manager installation is required. If you want to invoke the CLI from any directory, place it on PATH; otherwise use its absolute path in every script.
- Create a directory owned by the account that will run backups, or use a system-wide binary directory with administrator-controlled ownership.
- Copy the Duplicacy executable into that directory and restrict write access so an unprivileged web process cannot replace it.
- Run the executable from a shell and verify that it starts. Record the displayed version in your operations notes.
- If using Web Edition, start it under a dedicated service account and restrict access to its administration interface to a management network or secure tunnel.
Do not place a password directly in a command that will be saved in shell history. Use the credential mechanism supported by your chosen interface and protect its configuration files with filesystem permissions.
Initialize a repository and storage
Change to the directory whose contents you want to protect, then initialize the repository with a stable Backup ID and the storage URL:
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →duplicacy init <backup-id> <storage-url>
The Backup ID is the name under which that repository’s snapshots are recorded in the storage. Choose a descriptive, durable value such as a service or server role rather than an ephemeral hostname. You will need the original ID when restoring to another computer.
Cloud or local storage
Supply the storage URL format required by the selected backend and complete the credential prompts or configuration steps. Confirm that the account can create and read objects in the target location but cannot alter unrelated data.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
SFTP storage
Prepare the remote account, key authentication and destination directory first. The remote folder must exist when following the SFTP pattern in the quick-start. Verify that the VPS can establish an SFTP session and list the directory before starting the first large backup.
Protect the repository
Enable client-side encryption during setup. The encryption password is separate from the storage login and is required to decrypt snapshots. Store it in an access-controlled password manager or an offline escrow process that your recovery operators can use. Losing the encryption password can make otherwise intact data undecryptable; losing storage credentials can prevent access to the repository at all.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Schedule backups, checks, copies and pruning
Web Edition jobs
Create distinct jobs using the Web Edition’s job types rather than one opaque command. Set a backup job at the interval that matches how much data you can afford to lose. Add a check job often enough to detect repository damage before an incident, a copy job if you maintain a second destination, and a prune job after your retention policy is defined.
Give each job a useful name, select the intended repository and storage, and review the run history after the first execution. Ensure the Web Edition service remains running after a reboot and that its data directory is included in your server-management backup plan.
CLI scheduling
Wrap the CLI in a script and call that script from cron or another service scheduler. A robust wrapper should:
Recommended Free Tools
- Exit immediately when a prerequisite command fails.
- Acquire a lock so two backups cannot run against the same repository at once.
- Write timestamped output and preserve the executable’s exit status.
- Send an alert when backup, check, copy or prune fails.
- Run with the same account and environment used during manual testing.
Schedule the operations so they do not compete for CPU, disk or network. For example, run backups during the application’s quiet period, checks after a recent backup has completed, and pruning only after you have confirmed that the desired snapshots exist. The exact cron expression is an operational choice; document it with the retention policy and recovery objective.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
Set retention without deleting the wrong recovery points
Retention is a business decision expressed as commands. The CLI quick-start shows policies such as:
duplicacy prune -keep 1:7duplicacy prune -keep 7:30duplicacy prune -keep 0:180
Use these documented forms only after mapping them to your required hourly, daily, weekly and long-term recovery points. Review the snapshot list and test the policy on a non-production repository before applying it to valuable data. Keep enough history to cover delayed discovery of corruption, not merely the time needed to notice that a backup job failed.
Understand fossil collection
Pruning is a two-step process. The first prune marks unreferenced chunks as fossils. A later prune can remove fossils that are eligible under the retention rules. Consequently, free space may not increase after the first run, and a job report that shows fossils is not evidence that deletion has completed. Schedule a second run according to the documented behavior and monitor storage usage after both runs.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteVerify that backups are usable
A green scheduler status is not a recovery test. After the first backup:
- Run a check job and review its completion status and logs.
- Identify a small, known file and restore it to a temporary directory.
- Compare its contents, permissions and expected metadata with the source.
- Confirm that the destination has enough space and that the restored file is not being served publicly.
- Record the recovery steps, credentials location and time required.
Repeat a small restore on a fixed cadence and perform a larger exercise whenever the application, storage endpoint or VPS architecture changes. Include database dumps and configuration secrets in the exercise; a backup that restores only static files is not a complete service recovery.
Restore on the existing VPS
Use Web Edition to select the required repository and revision, then choose a safe destination. Restore into a temporary directory first when you are unsure whether files should overwrite live data. Compare the result, stop or place the application in maintenance mode, and move files into production only after checking ownership, permissions and configuration paths.
With the CLI, invoke the restore operation for the selected revision and destination using the options displayed by your installed version’s restore help. Do not guess a revision number: select it from the snapshot history and preserve the original data until the restored copy has been validated.
Restore to a replacement server
A replacement-server restore requires the original Backup ID and access to the same storage. The recovery sequence is:
- Provision a clean Linux server with sufficient disk space and network access to the storage endpoint.
- Install or place the same Duplicacy executable family used to create the repository.
- Recreate the service account and destination directory, or choose a temporary recovery directory.
- Provide the original storage credentials and encryption password through protected channels.
- Initialize or open the repository using the original Backup ID and the same storage location; do not invent a new ID if you need the existing snapshots.
- Select the required revision in Web Edition, or run the CLI restore workflow with that revision and destination.
- Validate files, ownership, application configuration and database recovery before switching traffic.
- After the service is operating, create a new backup from the replacement server and confirm that its job schedule and alerts are active.
Keep the old VPS untouched until the replacement has passed this validation. That preserves a second source of logs and data if a path, permission or credential was entered incorrectly.
Troubleshoot common failures
| Symptom | Likely cause | Corrective action |
|---|---|---|
| Initialization cannot create the storage location | Incorrect storage URL, missing remote SFTP folder or insufficient permissions. | Test the endpoint independently, create the required folder, and grant the account access only to the intended repository path. |
| Backup reads fewer files than expected | The scheduler runs as a different user, or directory permissions and exclusions differ from the manual test. | Run the job as its service account, audit read permissions and inspect the job configuration and logs. |
| Web job works manually but not overnight | The Web Edition service stopped, the environment differs, or the destination network is unavailable. | Enable service restart handling, check boot persistence, capture logs and test connectivity from the service context. |
| Prune does not immediately reclaim space | Chunks were marked as fossils on the first pass and are waiting for a later eligible prune. | Run the second prune after verifying the retention policy and monitor the storage report. |
| Restore cannot find snapshots on a new server | The Backup ID or storage location differs from the original, or credentials point to another account. | Use the original ID and storage, then verify access before attempting a restore. |
| Files are present but cannot be decrypted | The encryption password is missing or incorrect. | Use the protected escrow copy; there is no safe substitute for the original encryption password. |
| Restore completes but the service fails | Ownership, permissions, secrets, sockets or database state were not restored consistently. | Restore into a staging path, recreate runtime dependencies, import the database dump and validate the application before cutover. |
Security and operational safeguards
- Use client-side encryption, especially for cloud destinations, and keep the encryption password separate from storage credentials.
- Limit SFTP keys and cloud tokens to the backup path and required operations.
- Protect Web Edition administration and never expose it directly to the public internet without an appropriate access control layer.
- Keep at least one copy outside the VPS’s failure domain and consider a second destination through a copy job.
- Alert on missed backups, failed checks, failed copies and failed prunes; do not rely on storage growth alone as a health signal.
- Document the Backup ID, storage URL, executable version, scheduler definition, retention rules and restore destination.
- Rehearse recovery before you need it. A short, repeatable restore drill is more valuable than an untested assumption that the repository is usable.
A practical operating cadence
Use the following cadence as a starting framework and adjust it to your recovery-point and recovery-time requirements:
- Each backup window: create a snapshot, record its result and alert on failure.
- Regularly after backups: run a check against the repository and inspect errors rather than only the final status.
- When using two destinations: copy snapshots after the primary backup and verify that the second endpoint is reachable.
- According to retention: prune only after confirming that required snapshots exist; allow for the later fossil-removal run.
- On a fixed recovery schedule: restore a known file, then perform a full service recovery when architecture or credentials change.
This separation gives you clear answers to four different questions: did a new snapshot complete, can stored data be read, is there an independent copy, and does the retention policy leave the recovery points you expect?
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.
