Back up your server
VPSTitan servers are not backed up unless you add Automatic backups. Whether or not you add them, keep your own copy of anything you cannot afford to lose.
Automatic backups
Section titled “Automatic backups”Automatic backups are scheduled backups of the whole server: the operating system, your files, databases and settings. They are an optional add-on with a monthly price for each plan, shown on the configure step of the order.
- Add them when you order, on the configure step. See Order a VPSTitan server.
- Check whether they are on on the service overview in the client portal, where the Server card shows Backups as on or off.
- Add or remove them later by opening a support ticket that names the server’s hostname.
Restore a backup
Section titled “Restore a backup”Open a support ticket with:
- the server’s hostname
- roughly when the server was last in a good state
- whether anything on the server now must be kept
Restoring returns the whole server to the state it was in when the backup was taken, so anything written after that point is replaced. Copy off any newer files you need before you ask for a restore.
Keep your own copies
Section titled “Keep your own copies”Automatic backups protect you against mistakes and failed updates, but they are stored with the service. When a server is cancelled, its backups are deleted with it. The Terms of Service set out your responsibility to keep independent copies of your data.
Good practice for a self-managed server:
- Dump databases on a schedule (for example with
mysqldumporpg_dump) instead of copying their data files while they run. - Copy backups to another location with a tool such as
restic,borgorrsync. Remember that outbound traffic counts toward your bandwidth allowance. - Test a restore now and then. A backup you have never restored is a guess.