N
Neil Maxwell
So setting the backup type to "Full" will overwrite the target file if
it already exists?
Yes.
And if the existing incremental backups are referencing a full backup
that doesn't exist, they will be overwritten when the scheduled
incremental backup runs? In my experience, a scheduled incremental
backup will never overwrite an existing file, but maybe the conditions
just weren't right?
This is just my experience with TI7; my earlier experiences were with
tape-based backup and didn't have the same level of filename control.
Other programs may work differently.
When TI7 runs an incremental backup, it appends to the most recent
backup (full or incremental) and increments the file name. For
instance, if you don't do a full for 2 weeks and do incrementals, it
will get up to C-Full14.tib. If you then restart the full/weekly
series, it will replace C-Full.tib on the first full backup, then
replace C-Full2.tib thru C-Full7.tib on the following incrementals,
and start over again. It will leave the 8-14 files in place as
orphans, where they will get increasingly stale, and need to be
deleted to free up the space.
If, on the 3rd day, you ran another C-Full.tib full backup, the next
day's incremental would be named C-Full2.tib, and so on. All the
older files would still be there, but would be orphaned, and
eventually overwritten as the schedules got re-synced.
I see this when my full backups get missed for various reasons.
Deleting the orphaned incrementals depends on their creation date;
anything created before the full can be deleted, anything created
after the full is part of the current backup set, regardless of name.
Neil Maxwell - I don't speak for my employer