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

Developer backup storage

Backup storage for developers

Keep recovery copies of application data, configuration and other irreplaceable work. Check encryption keys and restore access as part of deployment.

Hosting options

Compare the services for your project.

Your requirements

What does your project need?

01

What the service needs to cover

Check developer backup storage for application data, database dumps, configuration exports, build artifacts that truly need preservation, and restore tests that prove the copy is more than successful upload logs.

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

Prove the copy restores cleanly

Developer backups usually cover database dumps, application data, configuration exports, and uploaded files. Build artifacts and dependency folders rarely belong in long term storage, because they can be rebuilt from source and a lock file. Keep what cannot be regenerated, and document how the rest is rebuilt.

A green upload log proves only that bytes moved. Proof comes from loading a dump into a scratch database and running the application against the restored copy. Automate that check where you can, and keep at least one restore point from before each major release.

01

Dump before deploy

Take a database dump before every schema migration. A failed migration with a fresh dump is an inconvenience; without one it can be data loss.

02

Exclude rebuildable data

Skip dependency folders, caches, and compiled output in backups. Smaller backups run faster and restore with fewer stale files.

03

Version the dumps

Name dumps with the application version and date. Matching a data copy to a code release removes guesswork during a rollback.

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

Backup storage for developers: 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