What the service needs to cover
Check protecting a website with copies of files and changing database state while documenting how DNS, certificates, configuration, uploads, and external dependencies are recreated during recovery.
Website backup Canada
Store copies of your website files and databases. Include email or other data where needed, and test that a restore works.
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 protecting a website with copies of files and changing database state while documenting how DNS, certificates, configuration, uploads, and external dependencies are recreated during recovery.
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 website backup needs two parts that belong together: the files and the database. Files hold themes, plugins, and uploads. The database holds posts, orders, users, and settings. Restoring files from Tuesday with a database from Friday creates a site that errors in ways that are hard to trace.
Recovery also needs the small pieces around the site. Keep notes on the DNS records, the certificate source, the configuration file values, and any external services the site calls. A restored site that cannot send mail or reach its payment service is only partly recovered.
Take the file archive and database dump in the same job run. Label both with one timestamp so a matched pair is always easy to find.
Media uploads usually drive backup size, not code. Check the uploads folder size monthly and adjust storage before the job starts failing on space.
Store a copy of DNS records and configuration values beside the backup. Rebuilding a site goes faster when nobody has to guess the settings.
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.