What is a backup copy job?
A backup copy job is a task in backup software that reads restore points from one repository and writes them to another. It creates a second, independent copy of backups, usually on different storage or at a different site, without reading the production systems again.
How does a backup copy job differ from a backup job?
A backup job reads data from the source, such as a virtual machine or a file server, and writes a restore point to the primary repository. A backup copy job starts from that restore point. It puts no load on production, it can run on its own schedule, and it can apply its own retention, which is often longer than the primary job's.
| Aspect | Backup job | Backup copy job |
|---|---|---|
| Reads from | Production systems | An existing repository |
| Load on production | Yes, during the backup window | None |
| Typical target | Primary repository | Second repository or site |
| Retention | Short to medium | Often longer, with GFS tiers |
When does a backup copy job run?
Two modes are common. In immediate mode the job copies each new restore point as soon as the backup job that created it finishes. In periodic mode it runs at set times and copies the latest state. Immediate copying keeps the second copy closest to the first. Periodic copying is easier to fit around a limited network link.
What is copy lag, and why does it matter?
Copy lag is the age difference between the newest restore point on the primary repository and the newest on the second. If the first site is lost, everything created during that gap is lost with it. Lag grows when the link is too slow for the daily change, when the copy window is short or when the target is busy. Backup copy job lag explains how to measure it, and sizing the link for cross-site copies covers the network side.
Where does a backup copy job fit in the 3-2-1 rule?
The 3-2-1-1-0 rule asks for several copies on different media with at least one offsite and one immutable. A backup copy job is the usual way to produce the offsite copy. Pointed at object storage with S3 Object Lock, the same job also provides the immutable one.
Frequently asked questions
Does a backup copy job back up the source again?
No. It reads restore points that already exist in a repository, so production systems are not touched.
Can a backup copy job have different retention from the backup job?
Yes. Copy jobs keep their own retention settings, which lets the second copy hold restore points for longer than the first.
Is a backup copy job the same as replication?
No. Replication keeps a ready-to-start copy of a system. A backup copy job copies restore points in backup format, which must be restored before use.