Dear BE2010 users and technical support,
after discovering that some files did not archive at all onto our tape robot, I learned with fear the following within this forum:
full (with reset Archive bit) = Backup all files in the selection and unset the archive bit
Full (Copy) = Backup all the files in the selection and don't change the status of the archive bit
Incremental (with reset archive bit) = Backup only files in the selection that have the archive bit set and then unset the archive bit on those files
-------
My boss in the past set all backup jobs to incremental only (never full backup) in the past due to tape consumtion. We do have HUGE files to archive FOREVER (10+ years). Files normally never change after archiving once. Users may demand files after years, our task is then to locate them and restore them manually to the server for the user (much like your local university's book library would do it).
Could our incremental ONLY jobs be the reason that files have not been targetted by the jobs, because the archive bit was not set (According to Mr. Weaver, having the archive bit not set is no problem with setting "full - with reset archive bit", since ALL files get archived, but a problem with setting "incremental - with reset archive bit" since ONLY files with set archive bit will be archived here...is that so?
If so, how can we incrementally archive in our environment without many redundant copies of the same files on tapes? NTFS journal? We cannot rely on users setting their archive bits....
Did we buy the right product for our demand?
