ATI 2010: Full backup to one location, incremental backup to another?
When creating an incremental set, is it possible to save the first backup (ie. the full backup) to one location (eg. one particular hard drive), but then save all subsequent backups (ie. the incremental backups) for that set to a different location (eg. a different hard drive)?
Why do you want to separate them?
When the increments are created they are based on the full backup and any previous increments, you also cannot carry out a restore if the full isn't present in the same folder as the increments, so the simple answer is no.
I assume that the same applies to differential backups as well.
Hi,
sorry for my English skills - I try to explain it:
I delete my backups after 90days - BUT I want to keep some of the Full Backups. Therefore it would be easier to have all Full Backups in one folder.
Christian
I assume you mean that you delete only the increments? This would not be a problem as you can move/copy a full backup to wherever you wish with Windows Explorer or from within TI, depending on the version, just like any other file.
I would recommend that you validate the moved file afterwards using the rescue CD however to make sure you are able to restore it, should you need to.
By the way your English skills are excellent
Hi como,
thanks for your reply.
I wold love to delete only the increments. My main problem is: How can I identify a Full Backup ? In TIH it's easy to find a Full Backup. But how can I identify it in a normal Explorer Window? That's why I thought about a separate folder with Full Backups only.
Thanks,
Christian
The increments will have the same file name as the full but with a numeric addition, in any case the increments should be much smaller than the full
Yes, they are normally smaller, but as the increments are not always smaller, you can't identify them by a batch. You have to do it automatically.
Until TIH2010 I did it with a unique filename and TIH always added a number in brackets "xyz_(2).tib". Increments got a additional number "xyz_(2)3.tib". After a failure you were able to point the backup task back to the correct full backup. My batch-file searchs for ").tib" and gets always a full backup.
Since TIH2011 you are not able to open a task and point it to the correct chain. After a failure (e.g. network problems) the file name looks like "xyz_(2)31", "xyz_(2)32", "xyz_(2)33", "xyz_(2)3(1)", "xyz_(2)3(1)2" and so on. That means it disturbs the naming completely and I have problems to identify a full backup by a batch file.
That's why I am really interested in identifying a full backup in a different way.
Christian