Aller au contenu principal

Backup Saved In The Wrong Place

Thread needs solution

I have ATI 2018 Build 12510.

I run several backup jobs on different schedules and saved to different external drives.

One job, which is called "System" saves disc C: and partition D: (partition D: is on a different physical drive than C:)

The "System" backup job is configured to do a full backup, then 5 incrementals, and save 3 chains before deleting the oldest chain to free up space.

A second job, which is run less often, is called "CDE" and saves C: D: and E:

The "CDE" backup job is configured to do a full backup, then 8 incrementals, and save 3 chains before deleting the oldest chain to free up space.

I noticed a few days ago that drive on which job "CDE" is saved suddenly had all of the old backup chains deleted and a new one started.  I was a bit concerned, but not too much, because the "CDE" job is mostly duplicated by the "System" job (the contents of partition E doesn't change much).

This morning, when I checked the "System" job, I discovered that it stalled unless the external drive on which "CDE" was saved was connected.  There should be nothing on that drive that needs to be backed up by the "System" job, so I started investigating.

When I checked the location where the "System" backups are saved I found that one of the incremental backups was missing. The incremental backup immediately after the full backup was missing.  See the first screenshot attached.

Then I checked the location where the "CDE" backup job is saved.  I noticed that although there was only one file in this location, it was named as if it was an incremental backup rather than a full backup.  When I looked inside this file, I found that it has two backups, one of which seems to be the missing "System" backup -- although it's labeled as a "full" rather than "incremental" backup.  See the second screenshot.

How do I get out of this situation?

Presumably, the next time "System" is run, it will create the 5th incremental and the time after that, a new full "System" backup will be created.  The new chain after that will (I hope) no longer be looking for the piece that's on the other drive.

For the "CDE" backup, should I delete what's there now and restart with a new full backup or will the extraneous backup file that belongs to the "System" job just be ignored going forward?  And if I delete what's there now, will it make a difference if I create the new full backup by clicking "Backup Now" rather than waiting until the next time "CDE" is scheduled to run?

 

Fichier attaché Taille
Capture.JPG 40.81 Ko
Capture1.JPG 22.33 Ko
0 Users found this helpful

Pete,

I think I follow here and understand what you are trying to accomplish with redundant backups.  However, in my opinion, I think you've attempted a simplified solution by combining multiple locations into single backups, but have actually made it a bit tougher.  As you've noticed, by having a missing drive, you're seeing a paused or stalled backup waiting for the external when it's not attached, because that entire backup says to backup all of those drives.

So, if it were me...

1) I would do an individual backup for each physical drive.  Do one backup task just for the disk that has C.  Do one task just for the disk that has partition D and do one backup task for the partition that just has E.  That way, your jobs can run independently of each other, regardless of which drive is attached or not and can still be recovered as needed too.  It will just be more simple in the long run.

2) As for the missing INC, no idea what happened there.  Yeah, I think you're missing the inc_b9_S2_v1.tib unless it was somewhere not in the screenshot.  With that being the case, if it is missing, none of the incrementals after that full will work.  You could force the next full, simply by manually kicking off that task to complete the chain and waiting for the next full to complete.  In that case, then you should be good to go after that, from that new full standpoint.

However, if you take my advice on separating the drives and additional partitions into their own backup tasks, you'll essentially be starting FRESH with 3 new backups (one for the OS entire disk, one for partition D and one for partition E).  Once those are all done, then you could remove the old backup tasks and either hold onto the old backup for posterity (just in case), or blow them away to free up some space.

3) As for the backup going away - that is likely your retention scheme.  Under the backup scheme, if automatic cleanup is enabled, your settings determine what to keep.  Forget the days... If you want to keep 1 full version chain, then say 1 vesion chain (or 2 or 3 or whatever).  When the next Full backup completes, if it is more than the quota you set, then the oldest chain will get deleted, but you'll retain the other ones.