A weekly hosting backup can put your website back as it was when the last backup ran: its files and its databases. It cannot bring back anything that changed after that, so up to a week of orders, posts, form entries and uploads may be missing from a restore. On Noiz shared hosting, the weekly backup is taken by the control panel and kept off site, as a safety net for your website. For anything that changes daily, add your own backups as well, with Plesk, Softaculous or a WordPress plugin, and keep at least one copy away from the server.
The US National Institute of Standards and Technology (NIST) calls the point in time you can recover to the recovery point. With one backup every seven days, your recovery point can be up to a week old.
Two examples show what that means:
How often you need a backup depends on how much change you can afford to lose.
Every Noiz shared hosting plan includes a weekly backup, taken by the Plesk panel and stored off site, so it survives a problem with the server itself.
| What the weekly plan backup is for | Keep your own copy of |
|---|---|
| Website files: code, themes, plugins, images and uploads | Anything you cannot afford to lose, including your mail and other important data |
| Databases | Changes made since the last weekly backup: your own more frequent backups |
The weekly backup is a safety net for the site, so keep your own copy of your mail and other important data. The Email Security add-on includes email backup for a domain hosted with Noiz, which plan backups do not cover.
If you need a restore from the weekly backup, open a ticket.
The weekly backup is a safety net. For a site that changes often, add backups on your own schedule. There are three common ways, and you can combine them.
Plesk, the control panel on every Noiz shared plan, can back up your subscription's websites, databases and mail on a schedule you set, as full backups or as incremental backups that store only what changed. You can restore a single site, file or database from a backup without overwriting everything else.
Plesk can store backups on a remote server over FTP or FTPS, or over SFTP, and with extensions in cloud storage. A backup can be protected with a password. Plesk warns that an incremental backup is useless if the full backup it depends on is deleted or damaged, so keep the full backups too.
Our help centre covers each step:
Backups stored inside your hosting account count against your disk, and they sit on the same server as the site. A remote location is safer.
If you installed an application with Softaculous, the one-click installer in Plesk, it can back up that installation and restore it from its Backups and Restore screen. Softaculous supports automatic backups once a day, once a week or once a month, with a rotation setting that decides how many to keep, and backup locations away from the server. By default its backups are stored in your own account, on the same server. Our guide explains what Softaculous is.
Several well-known WordPress plugins back up your site from inside WordPress:
| Plugin | Free version backs up | Free version stores to |
|---|---|---|
| UpdraftPlus | Files and database, on a schedule from every two hours to monthly, with restore | Dropbox, Google Drive, Amazon S3 and compatible storage, FTP, email and others |
| BackWPup | The full database and all files, hourly to monthly | The web server, Dropbox, FTP, Amazon S3 and compatible storage, and others |
| Duplicator | Files and database as one package, for moving or restoring a site | A download you keep; scheduled backups and cloud storage are in its paid version |
Each plugin's free version differs in what it restores. BackWPup's free version, for example, restores only backups you upload by hand. Check before you rely on one.
Tell us what your site does and how often it changes, and we will suggest a backup schedule that fits. Open a ticket.
Checked 19 October 2026.
Definitions and guidance
Tools
Noiz
Note: while some of this content was produced with the help of AI, the final editing has been done by a real human being.