Creating regular backups in Plesk is one of the most reliable ways to protect websites, databases, email accounts, and configuration data. Whether you manage a single domain or multiple hosting subscriptions, a well-planned backup strategy helps you recover quickly after accidental deletion, plugin conflicts, update failures, malware incidents, or server-side issues. In a managed hosting environment, backups are especially important because they reduce downtime and make restoration more predictable.
Plesk provides built-in backup tools that let you create full or partial backups, store them locally on the server, or send them to an external FTP storage location. You can also decide whether to include mail data, databases, configuration settings, and logs. If you host websites for clients or run a business-critical project, knowing how to create and manage backups in Plesk should be part of your everyday administration workflow.
What a Plesk backup includes
A backup in Plesk can contain different parts of your hosting account depending on the backup scope you choose. Before you start, it is useful to understand what is typically included:
- Website files — HTML, PHP, CMS files, media uploads, themes, plugins, and other content stored in the web root.
- Databases — MySQL or MariaDB databases used by your website applications.
- Email data — mailbox messages, folders, and email account settings, if selected.
- Domain and subscription settings — DNS, hosting configuration, PHP settings, and related Plesk parameters.
- SSL and security-related configuration — depending on the backup type and permissions.
For most websites, a full backup is the safest option before major changes. For example, if you are upgrading a CMS like WordPress or changing DNS settings, a complete backup gives you a restore point that is easier to roll back to.
When you should create a backup
It is a good idea to create a manual backup in Plesk before:
- Updating a CMS, theme, or plugin
- Making changes to PHP versions or server settings
- Importing a new database
- Changing DNS records or mail configuration
- Moving files or cleaning up the website structure
- Testing custom code or third-party integrations
- Performing maintenance on a production site
Even if automatic backups are enabled by your hosting provider, a manual backup before important changes is still recommended. It gives you a recent restore point and can save time in case a backup schedule has not yet run.
How to create a backup in Plesk
The exact menu labels can vary slightly depending on the Plesk version and your permissions, but the general process is straightforward.
Step 1: Log in to Plesk
Sign in to your Plesk control panel using your administrator, reseller, or subscription-level credentials. If you manage multiple sites, make sure you are working in the correct subscription or domain before starting the backup.
Step 2: Open the backup manager
From the main dashboard, go to the section for your domain or subscription and locate Backup Manager. In some layouts, it may appear under Tools & Settings for server-level tasks or under the subscription management area for site-specific backups.
Step 3: Start a new backup
Click Back Up or Back Up Now. Plesk will open a backup creation dialog where you can choose the backup type and storage location.
Step 4: Choose what to include
Select whether you want a full or partial backup. A full backup is usually the best choice if you want complete recovery protection. A partial backup may be enough if you only need files, only databases, or only mail data.
Depending on your access level, you may see options such as:
- Website files and directories
- Databases
- Mail configuration and mail content
- Domain configuration
- SSL certificates
If your website relies heavily on email, always confirm whether mailboxes are included. In many cases, email data is the part users forget to back up until they need it.
Step 5: Select the backup storage
Plesk usually allows you to store the backup in one of the following places:
- Server storage — saved locally on the hosting server
- FTP storage — transferred to an external FTP server or backup location
Local storage is convenient and fast, but it is still stored on the same infrastructure as your website. For better resilience, an external FTP destination is often the more reliable choice because it keeps a copy away from the main hosting environment.
Step 6: Configure backup options
Before running the backup, review options such as:
- Backup description — useful for identifying the purpose of the backup later
- Compression — helps reduce storage usage
- Password protection — adds an extra security layer when supported
- Backup content — full or selected items only
- Destination path — especially important for FTP backups
If available, use a clear description like “Before WordPress update” or “Monthly full backup August” so you can quickly identify the correct restore point later.
Step 7: Run the backup
Click the confirmation button to begin the backup process. Depending on the size of the website, number of mailboxes, and database volume, the process may take a few minutes or much longer. Large hosting accounts can require significant time, especially if they contain media-heavy websites or multiple mail domains.
While the backup is running, avoid making major changes to the site if possible. For best results, schedule backups during low-traffic periods.
How to create a backup for a single domain or subscription
If you manage multiple websites in one Plesk account, you may not need to back up everything at once. Plesk allows you to create backups at the subscription or domain level so you can protect one site independently from the others.
This is useful when:
- You are updating only one client site
- One website has a separate release cycle
- You want to store backups in smaller, easier-to-manage sets
- You need faster restoration for a single project
To back up one domain, open that domain’s management page in Plesk, go to the backup section, and choose the content relevant to that subscription. If your hosting plan allows it, you can also include mailboxes connected to that domain.
How to create an FTP backup in Plesk
Storing backups on an external FTP server is a practical way to keep backup copies separate from your hosting account. This is especially useful for business websites that require a stronger recovery strategy.
Set up FTP storage first
Before you create the backup, make sure you have valid FTP credentials, a destination folder, and enough free space on the remote server. In Plesk, open the FTP backup settings and enter:
- FTP server hostname or IP address
- Username and password
- Port number if different from the default
- Destination folder or path
Test the connection
Always verify that Plesk can connect to the FTP location before relying on it for production backups. A failed connection can interrupt scheduled backups or prevent manual backup completion. After the connection is saved, run a test or create a small backup to confirm that the destination is reachable.
Why external storage is useful
Using external FTP storage gives you another layer of protection in case the main hosting server becomes unavailable or the local backup repository gets corrupted. For many hosting setups, this is a better practice than relying only on on-server backups.
How to choose between full and partial backups
Picking the correct backup type depends on what you need to restore later.
Use a full backup when
- You are making major changes to the site
- You want a complete restore point
- You are migrating content, mail, or settings
- You are not sure which component may be affected
Use a partial backup when
- You only need website files
- You only want to protect one database
- You need a mail-only backup
- You are saving storage space for a specific task
In most day-to-day hosting scenarios, full backups are the safest default. Partial backups are better when you know the exact component you need.
How to verify that the backup was created successfully
After the backup finishes, open the backup list in Plesk and confirm that the new backup appears with the correct date, size, and description. A successful backup should show as completed without errors.
Check the following:
- The backup file is listed in Backup Manager
- The size looks reasonable for the selected content
- The backup description matches your expected task
- No warnings or errors appear in the log
- If using FTP, the file is present on the remote storage location
For important environments, it is also a good idea to test a restore occasionally. A backup is only useful if it can be restored when needed.
Best practices for backups in Plesk
To keep your backup strategy effective, follow these operational practices:
- Create backups before every major change — not only after something goes wrong.
- Keep more than one backup copy — a single restore point may not be enough.
- Store backups off-server when possible — external storage adds resilience.
- Name backups clearly — use dates and maintenance notes.
- Monitor storage usage — backups can fill disk space quickly.
- Check backup logs — failures should be investigated immediately.
- Test restores periodically — confirm that the recovery process works.
For managed hosting customers, a backup policy often works best when it combines automatic scheduled backups with manual backups before maintenance tasks.
Common issues when creating a backup
Not enough disk space
If the server storage is nearly full, Plesk may fail to create a backup. Delete old or unnecessary backups, clear temporary files, or use external FTP storage. Large media websites and mailbox-heavy subscriptions often need more space than expected.
Backup takes too long
Long backup times usually mean the account contains a lot of data or the server is under load. Consider running the backup during quieter hours, excluding unnecessary content, or moving the backup to external storage.
FTP backup fails
Verify the FTP host, credentials, folder path, and network access. Some providers also require passive mode or specific port settings. If the remote location is on another provider’s server, check that firewalls are not blocking the connection.
Backup appears but cannot be restored
This may happen if the backup is incomplete, corrupted, or created with an incompatible scope. Review the backup log and make sure the relevant files, databases, or mail data were included.
How often should you back up a website in Plesk?
The right frequency depends on how often your content changes:
- Daily — for active stores, membership sites, and frequently updated business websites
- Weekly — for standard company websites with moderate updates
- Before every change — for maintenance, updates, or development work
- More often — if you manage important email or high-value data
For many hosting environments, daily automated backups plus manual backups before changes provide a strong balance between protection and storage efficiency.
How backups support email and log recovery
This category also covers mail, backups, and logs, which means backups are not only about website files. If your hosting account includes important mailbox data, a Plesk backup can help preserve message history and account settings. That is particularly important for business users who rely on domain email for customer communication, billing, or internal operations.
Logs are not usually the primary reason to create a backup, but they can be relevant for troubleshooting and diagnostics. If you are investigating a site issue and need a clean rollback point, a recent backup can help you compare changes made before and after the problem started.
FAQ
Can I create a backup in Plesk without stopping my website?
Yes, in most cases you can create a backup while the website remains online. However, for the most consistent result, it is better to avoid major content changes during the backup window.
Does Plesk back up email accounts automatically?
It can, if you select mail data in the backup options or if your hosting plan uses a full backup that includes email. Always check the selected backup scope before starting.
Where are Plesk backups stored?
They can be stored locally on the server or on an external FTP destination, depending on the options available in your Plesk setup.
How do I know whether my backup is complete?
Review the backup status in Backup Manager and confirm there are no errors. For important sites, test the restore process occasionally to make sure the backup is usable.
Can I download a Plesk backup to my computer?
In many setups, yes. Plesk often allows you to download backup files locally, depending on file size and permissions. If the backup is very large, external storage is usually more practical.
Is a backup the same as a website migration copy?
Not exactly. A backup can be used for restoration and sometimes for migration, but a migration may also involve moving DNS, mail settings, and server-specific configuration. A full backup is often a useful starting point.
Conclusion
Creating a backup in Plesk is a practical and essential part of managing a hosting account. It protects your website, database, and email data from accidental loss and gives you a reliable recovery option before updates or maintenance. By using full backups for major changes, storing copies on external FTP when possible, and checking that backups complete successfully, you reduce risk and keep your hosting environment easier to manage.
If you regularly maintain websites in Plesk, make backups part of your standard workflow rather than something you do only after a problem appears. A few minutes spent creating the right backup can save hours of recovery work later.