Direkt zum Inhalt

Cyber Protect cloud backup and cleanup logic

Thread solved

I just upgraded my TI2020 to Cyber Protect to get the latest cloud support. After a few partition "test" backups to the cloud it appears to be doing a "full" backup followed by only "incremental" backups. I later found this documented. This is fine and to be expected. 

My real question is what happens when I limit the number of versions. I could not find a good discussion of this. After a full backup, I set the version limit to 2 and did another backup (2nd). Looking at the cleanup option for the backup it showed a full and inc backup with the timestamps for each. After doing a 3rd backup (incremental), cleanup still showed a full and inc backup, but the "full" backup now had the timestamp of the 2nd incremental backup and a new incremental backup had been created. It appears that cleanup after the 3rd backup "merged" the 2nd backup (incremental) into the original "full" backup to create a new "full" backup and then deleted the original "full" backup to satisfy my 2 version cleanup limit. If I understand this correctly, it makes a lot of sense to me, but I would have liked to see it documented somewhere.

Can anyone confirm the cleanup logic that I think I'm seeing AND point me to somewhere where it's documented?? I don't want to have unlimited versions taking up space, but I also want to know what happens when the version limit is reached.

Thanks

Bob

0 Users found this helpful

Bob, welcome to these public User Forums.

I wrote the following description for another user recently which may be of help to you:

A version means the data captured each time that a backup is performed as defined by the data selected for the Source of the backup task, and the changes to that backup source data.

If you change one or more files in the Source data, then those changes are captured when the backup task next runs, and if using the default settings, up to 20 such changes to data / files can be captured and stored.

In the same way, if you delete or remove one or more files, then that is also reflected in the subsequent versions of the backup, and eventually those deleted / removed file(s) will be purged as new backup versions are created.

Any files which remain unchanged from when the initial backup to the Cloud was made are not captured in subsequent backup versions as only changes are captured, so take no additional space in storage.

The net effect of the above is that the user can choose any restore point for recovering either the whole backup, i.e. a disk backup of the OS, or specific files held at the available points in time as reflected by the available versions in storage.

Note: for backup to the Cloud, only one initial Full backup is created & uploaded.  If you reach the limit set for the number of versions to keep, then changed data from versions that will be removed is automatically consolidated into the Full backup unless it was deleted where that action would be mirrored to the Full backup.  Such actions would cause the timestamp for the Full backup to be updated.

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Beiträge: 2
Kommentare: 1727

Hello everybody!

Thanks Steve for providing accurate answers as always.

 

Thanks Steve for the good description of what's happening. It works pretty much as I expected. I'm still going to do a little more testing before I set up my scheduled backups to the cloud. 

I've been using the product since TI2009 and have had good success with it. I have lots of local backups, but wanted to go one step further with offsite backups as well. If I have any questions in the future, I'll be sure to post them here.

Thanks again.