The backup services we provide, unless there is a special agreement include are as follows.
If content has been deleted, or pretty much any configuration or data in a web server needs to be recovered it is likely to be covered by the database backup. The exception being uploaded files.
30 days of database backups are kept, with the backup script being run nightly. As with any recovery, please contact us as soon as you find out that a restore is needed.
There are a couple of scenarios:
- Restore specific pages/configuration. We will typically take the backup offline and run-up a development server and copy in the changes.
- A complete restore is required. Not performed often, any content that has been changed that is not on the copy will be lost.
Both options can be time consuming and depending on the website subscription there may be a charge involved.
The host backup will also keep the database backups for a further 2 weeks.
RiumHosting provide an on-host backup that is typically run weekly (say Tuesday at 3am). 2 copies are kept. This backup is used if files are lost from the server.
MountainRiver CMS stores as much of the server building as possible in code and this is version managed (git). This means that we have copies of the webserver code at every point in time and maintain this on a master server, in development and test copies and on production servers.
This will be used as the first point for:
- Determining if unauthorised changes have been made to the web server.
- In setting up development or test environments.
The source code can be used to reset to a prior version although a copy of the same version of the database will be required for an accurate recreation.