Installation and User's Guide

To perform an incremental-by-date backup using the GUI, select the incremental(date only) option from the type of backup pull-down menu or use the incrbydateoption with the incremental command.The client backs up only those files whose modification date and time is later thanthe date and time of the last incremental backup of the file system on which thefile resides. Files added by the client after the last incremental backup, but with amodification date earlier than the last incremental backup, are not backed up.Files that were renamed after the last incremental backup, but otherwise remainunchanged, will not be backed up. Renaming a file does not change themodification date and time of the file. However, renaming a file does change themodification date of the directory in which it is located. In this case, the directoryis backed up, but not the files it contains.If you run an incremental-by-date backup of the whole file system, the serverupdates the date and time of the last incremental backup. If you perform anincremental-by-date backup on only part of a file system, the server does notupdate the date of the last full incremental backup. In this case, the nextincremental-by-date backup backs up these files again.Note: Unlike incremental backups, incremental-by-date backups do not expiredeleted files or rebind backup versions to a new management class if you changethe management class.Comparing incremental-by-date, journal-based, and NetAppsnapshot difference to full incremental and partial incrementalbackupsIncremental-by-date, journal-based, and NetApp snapshot difference arealternatives to full incremental and partial incremental back methods.Incremental-by-date backupAn incremental-by-date backup takes less time to process than a fullincremental backup and requires less memory.An incremental-by-date backup might not place exactly the same backupfiles into server storage because the incremental-by-date backup:vvvDoes not expire backup versions of files that you delete from theworkstation.Does not rebind backup versions to a new management class if youchange the management class.Does not back up files with attributes that change, unless themodification dates and times also change.v Ignores the copy group frequency attribute of management classes(Journal-based backups also ignore this attribute).Journal-based backupThe memory requirements for an initial journaling environment are thesame as the memory requirements for a full file space incremental, becausejournal-based backups must complete the full file space incremental inorder to set the journal database as valid, and to establish the baseline forjournaling.Journal-based backup has the following limitations:116 IBM Tivoli Storage Manager for Windows Backup-Archive Clients: Installation and User's Guide