IBM Tivoli Storage Manager for UNIX and Linux Backup-Archive ...

Journal-based backupJournal-based backup is supported on the AIX Backup-Archive client, on JFS, JFS2,and VxFs file systems. A backup for a particular file system is journal-based whenthe Tivoli Storage Manager journal daemon is installed and configured to journalthe file system, and a valid journal has been established.If the journal daemon is installed and running, then by default the incrementalcommand will perform a journal-based backup on file systems which are beingmonitored by the journal engine daemon. The following conditions must be met inorder to successfully perform a journal-based backup:vvvvThe journal daemon must be set up to monitor the file system that contains thefiles and directories being backed up.A full incremental backup must have been run successfully at least once on thefile system being backed up.The file space image of the file system at the server cannot have been modifiedby an administrative command since the last full incremental backup.The storage management policy for the files being backed up cannot have beenupdated since the last full incremental backup.The journal daemon records changes to an object or its attributes in a journaldatabase. During a journal-based backup, the client obtains a list of files that areeligible for backup from the journal database. Journal-based backup can increasebackup performance because the client does not scan the local file system orcontact the server to determine which files to process. Journal-based backup alsoreduces network traffic between the client and serverTivoli Storage Manager filters the list based on the current include-exclude list andprocesses, expires, and updates the resulting files according to policy constraints,such as serialization. However, the client ignores the server frequency attributeduring a journal-based backup. The reason for this is because a journal-basedbackup eliminates the backup version query to the server; therefore, the client doesnot know how many days have transpired since the last backup of the file.The journal daemon does not record changes in UNIX special files.The journal daemon excludes specific system files from having changes recorded inthe journal. Because changes to these files are not journaled, Tivoli StorageManager does not back up these files. See the journal daemon configuration filetsmjbbd.ini located in the Tivoli Storage Manager installation directory for specificsystem files that are excluded.Note:1. When using antivirus software, there are limitations to journal-based backup.Some antivirus software can incorrectly generate change notifications to theTSM journal service, causing files that have not changed to be incorrectlybacked up during journal based backup. To avoid these problems, use NortonAnti-Virus Corporate Edition 8.0 and higher.2. A journal-based backup might not fall back to the traditional incrementalbackup if the policy domain of your node is changed on the server. Thisdepends on when the policy set within the domain was last updated and thedate of the last incremental backup. In this case, you must force a fulltraditional incremental backup to rebind the files to the new domain. Use thenojournal option with the incremental command to specify that you want toperform a traditional full incremental backup, instead of the defaultChapter 11. Using commands 471