No, journaling has nothing to do with the archive bit. When you configure the TSM journal engine, it installs an additional Windows service. That service is a file-system monitor that watches for changes in the filesystem. The journal data base retains a list of all the files that change.
When a regular non-journal incremental backup runs, the TSM client has to scan the entire filesystem and examine the properties of each file (change date, archive bit, file size, etc.) to see if there has been any change since the last backup. When an incremental backup runs with the journal engine configured, all the client has to do is read the list of changed files from the journal data base, and back up those files. HOpe that helps. Regards, Wanda On Sat, Dec 5, 2009 at 10:04 AM, Mehdi Salehi <[email protected] > wrote: > Hi, > Archive bit helps incremental backup at file level. This be can be set to 0 > if file has been already backed up and if not changed, so the next > incremental backup ignores it. If the file changes (more specifically the > the inode changes), archive bit will be set to 1 again for the next > incremental backup. > I wonder how journaling helps incremental backups in TSM as it can create a > so-called journal database for each filesystem. Is it the same as archive > bit mechanism or something different? > > Thanks in advance. >
