Storage
Databases and backups
Plan database setup, user access, backup schedules, recovery checks, and plan-aware backup visibility before client traffic arrives.
What databases and backups do
Database tools cover server database services, site database attachment, database creation, user creation, credentials, local backups, scheduled backups, and plan-aware backup access. Backup planning should be part of launch, not an afterthought.
Before production traffic
- Decide which database engine the application needs.
- Confirm whether the database is created during site setup or separately.
- Choose backup frequency based on how often data changes.
- Decide who can view, download, or delete backup files.
Typical workflow
- Install or confirm the database service on the server.
- Create the required database and user.
- Attach the database details to the site or application environment.
- Run an on-demand backup before risky changes.
- Configure scheduled backups where the plan allows it.
- Review backup history and restoration expectations.
Checks before relying on backups
- The latest backup is visible.
- The database and file coverage are understood.
- A restore path has been tested or planned.
- Access to downloaded backup files is limited.
- Retired projects do not keep unnecessary backup schedules.
Common issues
- A team assumes files are backed up when only the database is scheduled.
- Backups exist but nobody has tested a restore.
- Production credentials are copied into unrelated notes.
- Backup schedules keep running after a client project ends.