Skip to main content

Keeping a second copy

Each backup copied, as it is stored, to a second drive or your NAS after it passes its check. Either copy restores on its own.

Updated
On this page

A backup on one drive is lost with that drive. Keep a second copy somewhere else copies each backup to a second place: another drive, a USB disk you keep in a drawer, your NAS (Home and Pro), an S3 bucket off-site, or a file server or another cloud: SFTP, FTP, WebDAV, Azure or Google Cloud (Pro). A backup in the cloud keeps one too, on a drive at home or with another provider.

Turning it on#

  1. Open the job (Edit) and go to the Where step.
  2. Under Keep a second copy somewhere else, switch it on.
  3. Choose Another drive or USB, Network share / NAS, Cloud (S3) or File server or cloud, and the folder (for S3: the saved S3 profile, the bucket and the folder in it; for a file server or another cloud: the saved account, the folder on its server, and for Azure or Google Cloud the container or bucket). A drive other than the backup's is best.
  4. Choose what the copy keeps (below), then Test second copy.
  5. Save the job.

Wizard step 2 - a second copy on another driveWizard step 2 - a second copy on another drive

The job page then shows two cards: Backup and Second copy.

Job page - a backup and its second copyJob page - a backup and its second copy

What it copies#

  • Each backup that completes and passes its check is copied as it is stored: compressed and encrypted, nothing read from your PC again.
  • On a drive or a share, every file is read back from the copy and compared. In a bucket, every upload carries a checksum the bucket checks before it keeps a byte, and the backup's files are then listed there with their sizes. A file that does not match is sent once more; if it still does not match, that backup is not kept on the copy (E-COPY-002).
  • A backup that failed, or failed its check, stays on the backup only.
  • A copy is never half there: a backup appears on the copy only when all of it has been copied and checked.

What the copy keeps#

ChoiceThe copy keeps
The same as the backupWhat the job's own retention keeps. A mirror's copy keeps the newest.
The last 30 days / the last yearBackups from that period, whole chains only.
The last 10 backupsThat many, whole chains only.
Every backupEverything, until you change it.

A mirror job can keep several backups on its copy: a single up-to-date copy on the drive, and some history on the NAS.

When it is made#

  • Right after each backup that completes and passes its check. It runs on its own line in Activity, and the backup's report says Second copy: copied to ….
  • When the place comes back. If the drive is unplugged or the NAS is off, the copy waits. GBM AI looks again every few minutes and catches up by itself. A drive is recognised by its volume serial, whatever letter it gets.
  • Copy now, on the job page, copies whatever the copy does not have yet.

Pausing scheduled backups pauses catching up too. A copy that is running can be paused or stopped like a backup; a stopped copy keeps the backups it finished.

Restoring from the copy#

Restore lists each backup once, with a Held on column: H: J: for a backup on both; for one the copy does not have yet, copy at 14:38 (or copied soon) when the next copy will take it, and copy waiting while the copy's drive is away.

Restore - Held on columnRestore - Held on column

  • If the backup's drive is not there, the point restores from the copy. Nothing to choose.
  • Backups the backup's own retention removed, but the copy still keeps, are listed too.
  • An encrypted backup needs the same password from either copy.
  • On another PC, Restore ▸ Open backups… ▸ A folder opens the copy's folder like any backup.

What the job page says#

The copyMeans
Up to dateThe copy has every backup it should.
3 points to copyBackups are waiting to be copied; the next backup or Copy now copies them.
Waiting for J: (Travel SSD)The drive or share is not there. Plug it in or switch the NAS on.
Copy failedThe last copy did not finish. Open its report to see why.

A copy in an S3 bucket#

  • Each backup goes up as it is stored, under the folder you chose in the bucket, so Restore ▸ Open backups… ▸ S3 bucket opens the copy like any cloud backup: on this PC, or on a new one with nothing but the S3 account.
  • Restore names the bucket on the points it holds (S3). When the backup's drive is gone, open the copy from the bucket as above.
  • What the copy keeps works as on a drive, whole chains only.

A copy on a file server or another cloud#

  • The same as a bucket, through the account saved under Settings ▸ Network & credentials: each backup goes up under the folder you chose, with the job's marker, so Restore ▸ Open backups… ▸ A file server or cloud… opens the copy on this PC or on a new one with nothing but an account for the server.
  • Every file is listed after it goes up and its size compared; one that does not match is sent once more.
  • No object lock: that is S3's.

A copy of a cloud backup#

A backup that goes to S3, a file server or another cloud keeps a second copy too: on a drive, a share, or another cloud.

  • Each backup is read back from the cloud and copied as it is stored, every file checked as on a drive.
  • Your cloud may charge for what is read back (its download or egress price). A drive at home costs nothing to fill.
  • Keep the copy somewhere else: the backup's own folder, a folder inside it or around it is refused. Another provider, or a drive, is best.
  • If the cloud account is lost, the copy restores alone: Restore ▸ Open backups… opens its folder, bucket or server.

Was this article helpful?