Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

Server recovery storage

Storage for server recovery copies

Keep the data and configuration needed to rebuild your server. Check backup access and restore steps before an outage.

Hosting options

Compare the services for your project.

Your requirements

What does your project need?

01

What the service needs to cover

Check storing server recovery data away from the live VPS or dedicated server, including configuration, application data, databases, secrets handling, and enough documentation to rebuild the service.

02

Ownership and access

Record the account owner, administrator and recovery contact. Keep passwords and keys in an appropriate secret store, not in this worksheet.

03

Recovery and retention

For backups, define the data-loss window and retention period. Check physical and account separation from the source, then restore a sample before relying on the copy.

04

Changes and renewals

Keep current configuration and renewal details. Review the plan when the data, software or people responsible for the service change.

Field guide

Store what a rebuild actually needs

Server recovery storage holds the pieces required to rebuild a service on a fresh machine. That means application files, database dumps, configuration files, scheduled task definitions, and a list of installed packages and versions. An image of data alone leaves the rebuild guessing at the environment.

Keep secrets out of plain text inside the recovery copy. Store configuration with secret values replaced by placeholders, and keep the real values in a password manager. Write the rebuild order down: system packages first, then services, then data, then traffic. Test that order once a year.

01

Package inventory

Export the installed package list and runtime versions after every major change. Rebuilding with different versions is a common cause of subtle failures.

02

Cron and services

Save scheduled tasks and service unit settings with the data. Backups that miss a nightly job or a queue worker restore an incomplete system.

03

Rebuild drill

Once a year, rebuild the service on a spare machine from the recovery copy alone. Time it, and fix every gap the drill exposes.

Planning

Access, backups and handover

Confirm the current product specifications and service responsibilities. Record who can approve a change and how to recover the service if it goes wrong.

Free guide

Storage for server recovery copies: planning checklist

Use the detailed checklist to plan setup, access, migration and recovery with your team.

Download PDF →
Help choosing

Tell us about your project.

Send us the software you use, your storage needs and your launch or moving date.

Ask about hosting

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move