The question that causes disputes.
THE COMMON AMBIGUITY
The business assumes the developer handles it. The developer assumes the host handles it. The host's backups are a net with finite retention.
Nobody is actually responsible, and this is discovered on the worst day.
WHAT WE PROVIDE
Server-level backups with retention according to your plan. A safety net for infrastructure events, not your archive.
WHAT YOU ARE RESPONSIBLE FOR
Your own backups, their retention, and knowing how to restore them.
IF A DEVELOPER MAINTAINS YOUR SITE
Agree explicitly, in writing: who takes backups, how often, where they are stored, how long they are kept, and who restores.
If it is not written down, it is not agreed.
IF YOU MAINTAIN CLIENT SITES
The same, from the other side. State what you provide and what you do not.
WHAT TO ESTABLISH
One named person or party responsible A documented arrangement A verification routine somebody actually performs
THE TEST
Ask everyone involved who takes the backups. If the answers differ, that is the problem.
