// Backups under control
Website backups and restoration without panic
Setting up backup copies of a website, database, files, hosting or VPS/VDS, checking recovery and assistance with rollback after an error, hack, update or unsuccessful transfer.
Copies
Site files, database, downloads, configs and critical settings.
Base
Database backups and data integrity check.
Rollback
Recovering from a bug, hack, update or failed transfer.
Control
Checking scheduling, storage and recovery capabilities.
// Backup should work
A backup is only useful if it can be restored
Many websites consider themselves protected until it turns out that the backup is old, incomplete, stored on the same server, or has never been checked. Therefore, not only copies are important, but also restoration control.
Site files
Template, plugins, downloads, configs, media files and important system files.
Database
Copy of the database, checking the size, integrity and compatibility of the recovery.
Hosting/VPS
Backup storage, access, disk space, automation and server limitations.
Schedule
Daily, weekly or manual copies depending on website activity.
Recovery
Site rollback after hacking, update error, file deletion or unsuccessful transfer.
Check
Control that a backup is actually created and can be used.
// Protection against website loss
Backup is not an archive “just in case”, but part of the service
Before updates, transfers, virus cleaning and major edits, you always need the ability to rollback. This reduces risk and allows you to work calmly.
// How the work goes
Backup must be verifiable
If a copy cannot be restored, it does not solve the problem of protecting the website.
Audit
What is being copied now, where is it stored and is it enough?
Setting
Files, database, schedule, storage and notifications.
Check
Control of copy creation and restoration capabilities.
Rollback
Recovery from an error, hack, update or transfer.
Regulations
Clear procedure: when to make copies and how to check them.
// When needed
When backups are especially important
- Before updates
- Before moving the website
- After hacking
- For online store
- If the website changes frequently
- If there is no developer
- Before changing PHP
- Before topic edits
- If the hosting is unstable
- If the website is important for enquiries
// Application
You can start by checking your backups
Send a link to the website and indicate where the copies are currently stored: hosting, plugin, VPS, cloud, or nothing configured.
// FAQ
Frequently asked questions: Website backups and restoration
What should be included in the backup?
Site files, database, downloads, configs and important settings. For a CMS, the database and uploads are often critical.
How often should I make backups?
Depends on website activity. For a regular website, weekly copies may be enough; for a store, more frequent copies are needed.
Is it possible to restore a website after being hacked?
Yes, if there is a clean backup. But after the rollback, you need to close the cause of the infection, otherwise the hack may happen again.
Is backup on hosting sufficient?
Not always. It is better to understand how often it is created, where it is stored and whether it can be restored independently.
Can I check existing backups?
Yes, you can check availability, size, date, composition and refurbishment.
What to do before updating the website?
Make a fresh copy of the files and database, and then perform an update with the ability to rollback.
Is it possible to set up backups for VPS?
Yes, for VPS you need to separately think about files, database, schedule, storage location and recovery check.
What if there is no backup?
First you need to create a current copy, then set up regular backups.
Is it possible to restore only part of the website?
Sometimes yes: a file, folder, database or individual data. It depends on the structure of the copy.
Are backups included in the service?
Yes, monitoring backups is one of the basic elements of regular website maintenance.