What the service needs to cover
Check keeping a remote backup copy away from the production account so deletion, compromise, storage failure, or a provider-side incident does not remove every recovery point at once.
Remote backup Canada
Send backup copies to Canadian SFTP storage. Check that the destination is separate from the system and location you need to protect.
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 keeping a remote backup copy away from the production account so deletion, compromise, storage failure, or a provider-side incident does not remove every recovery point at once.
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
A remote copy protects against failures that take the whole account with them. Account deletion, a compromised admin password, or a storage failure on the production server can remove local backups in the same event. A copy held in a separate service survives those cases.
Distance matters less than independence. The remote copy needs separate credentials, a separate login, and retention that runs longer than the local copy. If ransomware or a bad deploy corrupts live data, an older remote restore point may be the only clean version left to restore from.
Use a login for backup storage that differs from the hosting login. Shared credentials mean one stolen password exposes both copies.
Keep remote restore points for at least twice as long as local ones. Slow corruption and quiet deletions are often found weeks after they happen.
Confirm you can reach the remote storage from a different network and device. A recovery copy you cannot reach during an outage helps nobody.
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.