Backup placement is the part of a residency decision that a production-only review leaves unanswered. A production-only review approves one dataset in one place. Unless it explicitly includes the repository, copy-job target, replica and archive tier, it does not establish that those destinations meet the same residency boundary. Each of those destinations holds a placed copy of the same data, placed by whoever configured it, at the time they configured it.
This post makes a narrow argument. It does not claim that a regulation requires backups to sit beside production, and it does not claim that any vendor fails to control where copies go. It argues that backup placement is its own architecture decision, and that it needs its own inventory, a named owner and a verification routine, evaluated apart from the production dataset.
The residency review covered one dataset.…