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.
Server recovery storage
Keep the data and configuration needed to rebuild your server. Check backup access and restore steps before an outage.
Hosting options
Canadian SFTP storage for your backup software. Check physical separation from your source server before treating a copy as off-site.
See Backup storage →02Tell us what you need to host and when it needs to be ready.
See Ask about your project →03Register or transfer a domain and manage DNS. Registration and renewal prices depend on the extension.
See Domains →Your requirements
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.
Record the account owner, administrator and recovery contact. Keep passwords and keys in an appropriate secret store, not in this worksheet.
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.
Keep current configuration and renewal details. Review the plan when the data, software or people responsible for the service change.
Field guide
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.
Export the installed package list and runtime versions after every major change. Rebuilding with different versions is a common cause of subtle failures.
Save scheduled tasks and service unit settings with the data. Backups that miss a nightly job or a queue worker restore an incomplete system.
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
Confirm the current product specifications and service responsibilities. Record who can approve a change and how to recover the service if it goes wrong.
Use the detailed checklist to plan setup, access, migration and recovery with your team.
Download PDF →Send us the software you use, your storage needs and your launch or moving date.
Ask about hostingYour 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.