A manual backup is worth creating whenever you are about to make a change that could affect your site’s content, files, database, or server configuration. In managed hosting environments and control panels such as Plesk, a backup gives you a restore point before updates, migrations, theme changes, plugin installations, or any maintenance task that might break the website. For websites hosted in Europe and serving EU users, this is especially important because downtime, broken forms, or lost data can affect customer trust, compliance workflows, and day-to-day business operations.
Even if your hosting platform already runs automated backups, a manual backup is the safer choice before high-risk actions. Automatic backups are usually scheduled at fixed intervals, which means they may not capture your latest changes. A manual backup lets you preserve the exact state of your website right before you modify it.
When a manual backup is recommended
Create a manual backup before any change that may be difficult to reverse. The general rule is simple: if a task can modify content, database records, application files, permissions, or DNS-related settings, back up first.
Before updating the website or CMS
One of the most common reasons to create a manual backup is before updating your content management system, plugins, themes, or extensions. This applies to WordPress, Joomla, Drupal, Magento, PrestaShop, and similar platforms.
- Core CMS updates can change how the site behaves.
- Plugin or extension updates can introduce conflicts.
- Theme updates can affect layout, checkout flows, or custom code.
- Security patches may require database changes that cannot be easily rolled back.
If you manage your site through Plesk or another control panel, back up both the website files and the database before starting the update. That way, if the update causes an error, you can restore a known-good version quickly.
Before changing website design or code
Any time you edit templates, CSS, JavaScript, PHP files, or server-side scripts, a manual backup is strongly recommended. A small syntax mistake or incompatible code change can bring down the entire site.
- Theme customization
- Child theme changes
- Custom plugin development
- Editing configuration files such as .htaccess or web.config
- Deploying code from staging to production
For Apache-based hosting, changes to .htaccess can affect redirects, access rules, caching, and security behavior. Always save a backup copy before editing.
Before installing or removing extensions
Installing a new module, plugin, or app can alter database tables, create background jobs, or add new dependencies. Removing an extension can also delete data or leave broken references behind.
Manual backups are useful in these cases because they let you return to the exact previous state if the extension causes performance issues, errors, or compatibility problems.
Before major content changes
Not all backup triggers are technical. Content-heavy websites should also back up before large editorial changes, such as:
- Bulk editing product catalogues
- Importing posts, pages, or media files
- Updating pricing or multilingual content
- Replacing homepage content or call-to-action sections
- Changing forms, banners, or landing pages
If an import overwrites existing content or creates duplicate records, restoring from a manual backup can save time and prevent data loss.
Before database maintenance
Database operations can have serious consequences. You should create a manual backup before:
- Running database migrations
- Optimizing or repairing tables
- Changing collation or character set
- Importing or exporting large SQL files
- Cleaning old records or logs
Database issues often affect the entire site, especially e-commerce stores, member areas, booking systems, and customer portals. A restore point is essential before making structural changes.
Before server or hosting configuration changes
On a hosting platform, not every important backup is about website content. Configuration changes can also create problems, especially when they involve the web server, PHP version, mail settings, or security rules.
- Switching PHP versions
- Changing memory limits or execution limits
- Updating Apache or nginx directives
- Editing mail routing or DNS settings
- Changing cron jobs or scheduled tasks
In managed hosting, these tasks may be handled by an admin or support team, but it is still wise to create a manual backup first when the change affects your application behavior.
Situations where a manual backup is especially important
Some situations carry higher risk than others. In these cases, a manual backup should be treated as mandatory rather than optional.
Before a site migration
Whether you are moving to a new hosting platform, switching domains, or changing the document root, migration is a common point of failure. Files may be missed, database credentials may change, or redirects may break.
Back up the full website, database, and any custom configuration before the move. If you are using Plesk, make sure the backup includes the subscription, mail settings, and related domain data if needed.
Before launching a redesign
A redesign can involve changes to templates, navigation, page structure, forms, and scripts. Because many elements are updated at once, diagnosing problems after the launch can be difficult.
A manual backup gives you a clean fallback if the new design causes performance issues, broken links, or conversion problems.
Before sales campaigns or seasonal traffic peaks
When your website is about to receive more visitors, you do not want to make risky changes at the same time. Before Black Friday, holiday campaigns, new product launches, or major marketing pushes, create a backup so you can recover quickly if something fails.
This is especially important for EU businesses that rely on their websites for multilingual content, online orders, service bookings, or support requests.
Before security-related changes
Changing security rules can accidentally block access to the site, the admin area, or APIs. Create a manual backup before:
- Installing a firewall plugin
- Changing access rules
- Updating SSL/TLS settings
- Modifying authentication or two-factor login options
- Restricting IP access to the admin area
Security hardening is important, but it should not be done without a recovery path.
How to decide if you need a manual backup
A quick decision framework can help. Ask these questions before making a change:
- Will this change files, database content, or server settings?
- Could it break the website, forms, checkout, or login flow?
- Would recovery be time-consuming if something goes wrong?
- Do I have a recent automatic backup that includes the latest changes?
- Is this a production site with real users or live transactions?
If the answer to any of these is yes, create a manual backup first. A few minutes of preparation can prevent hours of troubleshooting and data recovery.
What a good manual backup should include
A proper manual backup is more than just copying files. For most websites, you should include all components needed to restore the site to a working state.
Website files
This usually includes application files, themes, plugins, media uploads, scripts, and configuration files. Make sure hidden files are included when relevant, such as .htaccess.
Database
The database contains pages, posts, user accounts, orders, settings, and many dynamic site elements. For CMS-based websites, the database is often just as important as the files.
Email and DNS-related data
If your change could affect email routing or domain configuration, consider backing up the relevant settings or documenting them carefully. In hosted environments, restore needs may include mailboxes, aliases, and DNS records depending on the scope of the change.
Custom configuration
Save any custom server or application configuration, including cron definitions, environment variables, and manual overrides. These are easy to overlook but can be critical during restore.
Practical examples
Here are a few realistic examples of when a manual backup should be created.
Example 1: Updating a WordPress plugin
You are about to update a plugin that powers your contact form and spam protection. Because the plugin interacts with form submission and database records, a conflict could stop lead generation. Create a manual backup first, then update and test the form immediately.
Example 2: Changing PHP version in Plesk
You want to switch from one PHP version to another to improve compatibility or performance. Some applications work better on newer versions, while others need older ones. Back up before switching so you can restore the previous environment if the site shows errors.
Example 3: Editing Apache rules
You are adding redirects and access restrictions in .htaccess. A syntax error can create a 500 Internal Server Error. Save a manual backup of the file and ideally a full site backup before making the change.
Example 4: Importing product data
An online store is about to import a new product catalogue with updated SKUs, prices, and descriptions. A mistaken CSV mapping can overwrite existing data. Back up the database and media files before the import begins.
Best practices for manual backups
To make manual backups effective, use a consistent process rather than creating ad hoc copies.
- Create the backup immediately before the change.
- Use a clear name with date, time, and purpose.
- Verify that the archive is complete and readable.
- Store it in a separate location from the live site.
- Keep at least one recent restore point for critical websites.
- Test the restore process on staging when possible.
If your hosting control panel supports backup snapshots, use them in addition to file-level or database backups. A combination of backup types gives you better recovery options.
Version your backups
When you create several backups during a maintenance window, label them clearly. For example:
- before-plugin-update-2026-04-21
- before-php-switch-2026-04-21
- before-migration-production
This makes it much easier to identify the correct restore point later.
Do not rely only on one copy
A backup stored only on the same server can be lost if the server itself has a problem. Keep a copy in a separate location, such as secure cloud storage or another system under your control, depending on your hosting policy and operational needs.
Manual backups vs automatic backups
Automatic backups are essential, but they serve a different purpose. They protect you against general incidents and provide a rolling history of recoverable states. Manual backups are for deliberate changes that you are about to make right now.
- Automatic backup: scheduled, continuous protection
- Manual backup: a custom restore point before a specific action
The safest approach is to use both. Automatic backups reduce overall risk, while manual backups protect critical maintenance windows and deployment changes.
FAQ
Should I create a manual backup even if my hosting platform already has daily backups?
Yes, if you are about to make a risky change. Daily backups may not reflect the current state of your site, and they may not capture the exact version you want to restore.
Do I need a manual backup for small content edits?
For a single text change, probably not. But if the edit is part of a larger content update, affects a live campaign, or involves multiple pages, a backup is still a good idea.
Is a file backup enough?
Usually not. For CMS-based websites and online stores, the database is often just as important as the files. Back up both whenever possible.
Can I make a manual backup from Plesk?
Yes. In a Plesk environment, backup and restore tools usually let you create a backup of the subscription, domain, files, databases, and selected settings. The exact options depend on your hosting plan and permissions.
When should I test a backup restore?
Test restores on staging whenever possible, especially before major updates, migrations, or platform changes. A backup is only useful if it can be restored successfully.
Conclusion
Create a manual backup before any change that could affect your live website, database, or hosting configuration. The most important moments are before updates, plugin installs, code edits, migrations, database operations, and server changes. In a managed hosting or Plesk environment, a manual backup is your safest way to protect production data and reduce downtime risk.
If you follow one simple rule, use this: when the change is important enough to worry about, it is important enough to back up first. That habit will save time, prevent data loss, and make every website maintenance task safer.