Incremental Backup Strategy Using BEWS 12.0 - 'Using archive bit' or 'Using modified time'

[chris_lee1]

Hi,

Our grandfather, father, son strategy has been in place for some years, it uses tapes and is tried and tested.  We are now considering changing our strategy to incremental to disc (this will then be mirrored to an off site location).

I would like to hear peoples thoughts/experiences with the two types of incremental job offered in BEWS 12.0, these are:

-Using archive bit (reset archive bit)
-Using modified time

Email support for this product has ended.  Any comments would be appreciated.  Our strategy would include approx 12 physical servers and approx 5 virtual images (we currently use pre and post commands as part of our weekly full job and daily differential job).

Thanks,
Chris

[Deepak_W]

Kindly go through below mentioned details for your question.

Incremental backups include only the files that have changed since the last full or incremental backup.  Backup Exec provides two incremental backup methods, one that uses archive bit and one that uses modified time to determine if the file was backed up. If you select to use the Full - Back up files - Using archive bit (reset archive bit) and want to run incremental backups, you must use the Incremental - Back up changed files since last full or incremental- Using archive bit (reset archive
bit) method. If you select to use the Full - Back up files - Using modified time, you must use the Incremental - Back up changed files since last full or incremental - Using modified time method. The advantages and disadvantages described in this section pertain to either type of differential backup.

Note:  If you use modified time to determine if files have been backed up, the full and incremental backups must use the same backup selection list.

For more information refer to BE Admin Guide