Installation and User's Guide

processes directories and wildcarded file specifications in the same way. TivoliStorage Manager uses the domain list if you do not specify a file specification.Note: Journal-based backup might not fall back to the traditional incrementalbackup if the policy domain of your node is changed on the server, depending onwhen the policy set within the domain was last updated and the date of the lastincremental. In this case, you must force a full traditional incremental backup torebind the files to the new domain. Use the nojournal option with the incrementalcommand to specify that you want to perform a traditional full incrementalbackup, instead of the default journal-based backup.When a user deletes a file with a long name, the Windows operating system mightsupply a short, or compressed, name to the journal engine service. After the objectis deleted, the compressed name can be reused and the deletion notice might nolonger identify a unique object. During a journaled incremental backup, theattempt to expire the file fails because the compressed name is not known to theserver. When this occurs, a record is placed in the journal indicating that thecurrent directory is not exactly represented at the server. Use the incrthresholdoption to specify what action is taken when this occurs.Under the following conditions, the journal database is considered invalid and theclient reverts to the traditional full incremental backup:v A journaled file space name has changed.v The client node name has changed.v The client contacts a different server to do the backup.v Policy changes have occurred (new policy set activation).v The journal is corrupt (out of space conditions, disk error).v The journal service is not running.v The journal service is stopped or started for any reason, including system reboot.Journal-based backup differs from the traditional full incremental backup in thefollowing ways:v Tivoli Storage Manager does not enforce non-default copy frequencies (otherthan 0).v Attribute changes to an object require a back up of the entire object.You can use the nojournal option with the incremental command to perform atraditional full incremental backup instead of the default journal-based backup.Multiple journal-based backup sessions are possible.Virtual volume and virtual mount point (Windows NTFS)If you perform an incremental backup of a file space on which a volume ismounted, Tivoli Storage Manager does not traverse the mount junction to back upall mounted data.For example, if you have a mounted volume named c:\mount on file space c:,Tivoli Storage Manager backs up only the junction point, not the data underc:\mount.To back up all data for a file system, including virtual volumes and virtual mountpoints, run an incremental backup on each virtual volume. You must also performan incremental backup on the file system.Chapter 13. Using commands 573