Automatically Back Up Laptop Files to Windows Hosting Using FTP or FTPS
Quick Answer Yes. You can automatically back up a folder on your Windows laptop to your Windows hosting account using software that supports scheduled transf...
Quick Answer
Yes. You can automatically back up a folder on your Windows laptop to your Windows hosting account using software that supports scheduled transfers and incremental backups. Your hosting account provides the remote storage, while the software on your laptop manages the backup process.
Suitable options include Duplicati for encrypted, incremental backups and SyncBack for synchronizing files to a remote folder. Cobian Reflector is another option to evaluate. The right choice depends on whether you need directly accessible files in Plesk or a structured backup that you restore through the backup application.
Understanding the Backup Requirement
The objective is to create a dedicated folder on your Windows hosting account, managed through Plesk, and automatically back up a selected folder from your laptop to that remote location.
The initial backup transfers the existing files. Subsequent incremental backups transfer changes since the previous backup, where supported by the selected software and backup configuration. This can reduce transfer time and bandwidth compared with repeatedly uploading all files.
Before choosing a solution, distinguish between these two approaches:
- File synchronization: Copies new and changed files to the remote folder. Depending on the configuration, deletions and overwrites on the laptop may also affect the remote copy.
- Versioned backup: Preserves earlier versions of files so that accidentally deleted, overwritten, or corrupted data may be recoverable.
Synchronization alone is not a substitute for a versioned backup. If the laptop is infected by ransomware or a file is accidentally deleted, a simple synchronized copy may also be affected.
Recommended Backup Software
| Software | Suitable use | Important considerations |
|---|---|---|
| Duplicati | Encrypted, compressed, incremental backups with retention options. | Uses its own backup structure. Files generally need to be restored through Duplicati rather than browsed as ordinary documents in Plesk. Verify support for your hosting server's available transfer protocol before deployment. |
| SyncBack | Copying or synchronizing ordinary files to remote storage on a schedule. | FTP, FTPS, and SFTP support depends on the edition. Confirm version-history and deletion-handling options for the selected edition. |
| Cobian Reflector | Scheduled file backups with full, incremental, or differential backup options where supported by the selected configuration. | Check the current release's supported destination protocols and features before selecting it for a Plesk-hosted FTP destination. |
Product features and supported protocols can change between releases and editions. Consult the software's current official documentation before installation. Do not assume that every edition supports FTPS or SFTP.
Which Backup Method Should You Choose?
Option 1: Use Duplicati for Recoverable, Versioned Backups
Choose Duplicati if your priority is recovering previous versions of files rather than opening every backed-up document directly in Plesk. It is designed to create managed backup sets and supports encryption, compression, scheduling, and retention settings.
Use Duplicati to perform the initial backup. Do not manually upload the source folder and expect Duplicati to recognize that ordinary folder as an existing Duplicati backup. Configure the application to create and manage its own backup destination.
Before proceeding, verify that your hosting provider supports a destination protocol compatible with your chosen Duplicati version. If your provider offers only FTP or FTPS, check the current Duplicati documentation for the exact supported backend and configuration.
Option 2: Use SyncBack for Files Visible in Plesk
Choose a suitable SyncBack edition if you want backed-up files to remain accessible as ordinary files through your hosting account or Plesk File Manager.
Configure a one-way backup from the laptop to the remote folder. Review the profile's overwrite, deletion, and versioning settings carefully. If the goal is to retain deleted files, do not enable an option that automatically deletes destination files merely because they no longer exist at the source.
A one-way copy is usually more appropriate than two-way synchronization for a backup destination. Test the profile with a small sample folder before including important business documents.
Prepare Your Windows Hosting Account in Plesk
Step 1: Create a Dedicated Backup Folder
Sign in to Plesk and determine where your hosting provider permits non-website data to be stored. Create a dedicated folder for backups outside the website's public document root, if your hosting plan and permissions allow it.
Do not assume that every folder displayed in Plesk is private. Confirm the folder's location and access permissions with your hosting provider. If a folder must be created under a particular account directory, follow the provider's documented configuration.
Step 2: Create a Separate FTP Account
If Plesk and your hosting plan support additional FTP accounts, create a dedicated account restricted to the backup folder. This limits the potential impact if the credentials are compromised.
Record the connection details locally:
- FTP server hostname.
- Username for the dedicated backup account.
- Port and connection protocol specified by the provider.
- Remote backup directory.
- Whether explicit or implicit FTPS is required, if applicable.
Never publish the hostname, username, or password in a public article, screenshot, support forum, or shared configuration file.
Step 3: Confirm the Available Protocol
FTP transfers credentials and data without encryption unless an additional protected protocol is used. Prefer FTPS or SFTP when supported by both the hosting provider and the selected backup application.
FTPS protects FTP using TLS. SFTP is a different protocol that transfers files over SSH; it is not simply another name for FTPS. Standard Windows hosting may offer FTP or FTPS without SFTP, so confirm actual availability instead of assuming that all three protocols are supported.
Use the hostname and certificate validation settings provided by the hosting company. Do not disable certificate validation merely to make a connection succeed.
Configure the Laptop Backup
Step 1: Select the Source Folder
Identify the exact folder on your laptop that needs protection, such as a business documents folder or a dedicated project directory. Avoid selecting the entire system drive unless the software is specifically configured for that purpose.
Check whether the folder contains files that require special handling, such as active databases, Outlook data files, virtual machines, or application data. A normal file copy may capture an inconsistent version of a file that is currently being modified. Use an application-supported backup method or a consistent export for such data.
Step 2: Configure the Remote Destination
In the backup application, add a remote destination using the exact protocol supported by your host. Enter the hostname, port, account credentials, and remote directory according to the software's documentation.
For Duplicati, configure the destination as a new managed backup. For SyncBack, create a profile that copies the selected local folder to the remote directory. The precise screens and options depend on the product version.
Step 3: Perform the Initial Backup
Run the first backup manually and allow it to complete. This initial run normally transfers the existing files and may take considerable time depending on the data size, connection speed, and hosting limits.
Check the application's logs for failed transfers, skipped files, permission errors, or storage-limit problems. Confirm that the remote destination contains the expected backup data.
Step 4: Schedule Incremental Backups
Configure a schedule appropriate for how often the files change. For example, daily backups may suit documents that change throughout the working day, while a more frequent schedule may be needed for critical files.
Make sure the laptop is powered on, connected to the internet, and able to run the backup application at the scheduled time. A scheduled task cannot complete a transfer if the laptop is unavailable or the network connection fails.
Configure retry behavior and notifications where available. Review the application's logs periodically instead of assuming that a configured schedule means every backup has succeeded.
Configure Retention and Previous Versions
Retention defines how long older backup versions are kept before they are removed. If you need to recover a file deleted or overwritten on the laptop, configure retention or versioning that supports that recovery goal.
For a versioned backup, choose a retention period that fits your available hosting storage and recovery requirements. For a synchronization profile, check whether the software provides a separate versioning or recycle-bin feature.
Do not enable automatic deletion of old backup data until you understand its effect. Retention policies can permanently remove recovery points once they expire.
Verify That the Backup Can Be Restored
A successful upload does not prove that a backup is recoverable. Perform a test restoration before relying on the system for important data.
- Select a small, non-critical test file in the source folder.
- Run the configured backup and confirm that it completes without errors.
- Change the test file and run another backup.
- Verify that the latest version is backed up and, where configured, that an earlier version remains recoverable.
- Restore a copy to a separate test folder rather than overwriting the original file.
- Open the restored file and confirm that its contents are correct.
Repeat restore tests periodically and after significant changes to the backup software, credentials, or hosting configuration.
Common Problems and Troubleshooting
| Problem | What to check |
|---|---|
| Connection fails | Verify the hostname, port, selected protocol, hosting firewall rules, and whether the provider permits the connection from your network. |
| Authentication fails | Check the dedicated account's username, password, status, and permissions. Re-enter credentials securely without posting them in a support request. |
| Permission denied | Confirm that the account has write access to the configured remote folder and that the path is correct for the hosting environment. |
| Backup is incomplete | Review logs for skipped files, locked files, network interruptions, file-size restrictions, or hosting storage limits. |
| Every run transfers many files | Check whether the profile is configured for incremental backup or ordinary synchronization, and whether the software detects changes as expected. |
| Deleted files disappear from the destination | Review deletion propagation, mirroring, and retention settings. Restore from a retained version if one exists. |
| Hosting storage is full | Review the size of stored backups and the retention policy. Do not delete recovery data until you have confirmed what can safely be removed. |
Security and Hosting Limitations
- Check hosting terms: Some shared hosting plans restrict backup storage or use of hosting space for general-purpose file storage. Obtain confirmation from your provider.
- Protect credentials: Use a dedicated account with minimum required permissions and store its password in a reputable password manager or the application's protected credential store.
- Encrypt sensitive backups: If the backup application supports client-side encryption, enable it when appropriate and securely preserve the encryption passphrase or recovery key. Losing the key may make the backup unrecoverable.
- Monitor storage limits: Incremental backups and retained versions can accumulate over time. Account for both the initial backup and future changes.
- Keep another recovery copy: Hosting is useful as an offsite destination, but it should not be the only copy of important business data. Maintain an additional independent backup where practical.
- Protect the destination: Keep backup data outside public website access and restrict permissions. A difficult-to-guess folder name is not a substitute for access controls.
Frequently Asked Questions
Can I upload the folder manually once and then upload only changes?
Yes, if you use a file-synchronization tool configured to compare the source and destination. However, a managed backup application such as Duplicati generally needs to create its own backup structure. Do not assume that an ordinary manually uploaded folder can be adopted as an existing managed backup.
Can I use Plesk to schedule backups of my laptop?
Plesk manages the hosting environment, but it does not automatically back up arbitrary laptop folders just because they are accessible through an FTP account. A backup or synchronization application running on the laptop is generally needed to transfer the files on a schedule.
Will incremental backups retain deleted files?
Not automatically in every configuration. A versioned backup with an appropriate retention policy can preserve earlier copies. A synchronization profile may delete remote files when they are deleted locally, depending on its settings.
Can I browse all backup files directly in Plesk?
This depends on the backup method. With a normal file-copy profile, the destination may contain directly accessible files. With Duplicati, the destination uses a managed backup structure, and restoration is normally performed through the application.
Can the backup run when my laptop is switched off?
No. A backup application running on the laptop cannot upload files while the laptop is switched off. The laptop must be running and have network access when the scheduled job executes.
Should I use FTP, FTPS, or SFTP?
Prefer FTPS or SFTP when supported by the hosting provider and backup software. FTPS and SFTP are different protocols, and compatibility must be confirmed for the specific hosting plan and software edition.
Conclusion
For automatic laptop-to-hosting backups, choose a solution based on your recovery requirements. Use Duplicati when managed, encrypted, incremental backups and version retention are the priority. Consider an appropriate SyncBack edition when ordinary files need to remain accessible through Plesk. Before deploying either option, confirm protocol compatibility, hosting storage permissions, and retention behavior, then perform a successful restoration test.
Sources
Was this guide useful?
Your answer helps us keep BISONKB accurate and practical.