A plugin update leaves a white screen, someone deletes the wrong folder, or the site gets hacked. The fastest fix is often returning to the last working state, and if your ISPmanager account has a backups section you can do it yourself. Restoring in a hurry is risky, though: the wrong date, or rolling back everything at once, can erase the last few days of orders and email.
Where backups live and what they contain
The Backups section lists server-made copies by date. Whether it is visible and how long copies are kept depends on your hosting setup, so contact sayt.uz support if it is missing or the date you need is not there. A backup usually holds site files, databases and mailboxes, and the key feature is restoring them separately. Files and database belong together, though: old WordPress files with today's database can mismatch plugin versions and settings, so restoring both from the same date is usually safest.
Save the current state first
Even a broken site deserves a snapshot before you restore, so you can go back if you pick the wrong date. Archive the folder in the file manager and export the database in phpMyAdmin, or over SSH:
tar -czf $HOME/misol-before.tar.gz -C $HOME/www misol.uz
mysqldump -u shop_user -p shop_db > $HOME/shop_db-before.sql
Keep these files in your home directory, not inside the public www folder, and remove them afterwards to save quota.
Restoring step by step
- Choose a date before the problem began; when unsure, go one day earlier.
- Open the backup and select only what you need, for example the
misol.uzfiles and its database. - Start the restore and wait for it to finish.
- Open the site with a fresh cache, log into the admin area and test key functions.
If only one file is damaged, download the backup, extract that file and upload it through the file manager without touching anything else.
Example: a restaurant that must not lose orders
A Tashkent restaurant takes online orders on misol.uz. A theme update on Thursday broke the order page, but nobody noticed until Saturday. Rolling the database back to Wednesday would delete every order from Thursday and Friday. Since the bug is in theme code, restore only the files to Wednesday and keep today's database. If the database must be rolled back too, restore the old copy into a separate empty database and move over only the tables you need.
Restoring a hacked site
A restore alone does not close the hole the attacker used, such as an outdated plugin or weak password, and the chosen backup may already contain a hidden backdoor. Right after restoring, update the CMS, theme and plugins, change admin, FTP, database and panel passwords, and look for unknown administrator accounts.
Restoring a mailbox
Sometimes the problem is email, not the website: someone deleted a folder of important correspondence, or a badly configured phone app pulled messages off the server. Restore just that mailbox from the backup rather than the whole account. Depending on how the restore works, messages received after the backup date may be overwritten, so first save any important recent mail from that mailbox through an email client, then ask the owner to confirm everything is back.
What to check afterwards
A page that loads is not proof that everything works. Open the site in a private window and clear any caching plugin, then submit the contact form, place a test order and check that images load. A sudden SSL warning or redirect loop often means an older .htaccess came back with the files, so compare it with your current setup. Finally, note the date and reason for the restore; it saves time next time.
Keep your own copies too
Server backups are kept for a limited time and are outside your control. For an important site, regularly store your own file archive and database export on your computer or in cloud storage, especially before redesigns, CMS upgrades or migrations.