Simple definition
A Backup Copy is a secondary copy of data or restore points stored in another repository, site, or medium so that recovery does not depend on a single backup location.
Technical definition
Unlike a primary backup that reads production data directly, a Backup Copy mechanism can reuse existing restore points and build an independent chain on the target. Retention, scheduling, and protection of the copy can differ from the primary job.
How it works / role
After a primary restore point is created, the backup software identifies the data required for the copy, transfers it to the target, and maintains the configured chain and retention. Depending on the product, copying can be continuous, periodic, or limited to a defined window.
What is it used for?
Keep a second copy away from the primary repository, implement a 3-2-1 strategy, extend retention, or maintain restore points at another site.
Practical example
Daily backups are stored at the primary site and a Backup Copy job automatically transfers the required restore points to a remote repository with a longer retention policy.
Common issues
- The destination repository is unavailable or full
- Bandwidth is insufficient to complete copying within the required window
- Retention is oversized and consumes excessive capacity
- The secondary copy uses the same credentials and is not sufficiently isolated
Key takeaway: A Backup Copy provides real protection only when the second copy is independent, monitored, and regularly tested for recovery.