12.07.2015 Views

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

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

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

SHOW MORE
SHOW LESS
  • No tags were found...

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Note: Include.fs.nas does not apply to incremental snapdiff.A NAS file system specification uses the following conventions:v NAS nodes represent a new node type. The NAS node name uniquely identifiesa NAS file server <strong>and</strong> its data to <strong>Tivoli</strong> <strong>Storage</strong> <strong>Manager</strong>. You can prefix the NASnode name to the file specification to specify the file server to which the includestatement applies. If you do not specify a NAS node name, the file system youspecify applies to all NAS file servers.v Regardless of the client plat<strong>for</strong>m, NAS file system specifications use the <strong>for</strong>wardslash (/) separator, as in this example: /vol/vol0.Use the following syntax:►► pattern mgmtclassname toc=value ►◄ParameterspatternSpecifies the objects to include <strong>for</strong> backup services, to assign a specificmanagement class, or to control TOC creation. You can use wildcards in thepattern.mgmtclassnameSpecifies the name of the management class to assign to the objects. If amanagement class is not specified, the default management class is used.toc=valueSee “Toc” on page 423 <strong>for</strong> more in<strong>for</strong>mation.For example, to assign a management class to the /vol/vol1 file system of a NASnode called netappsj, specify the following include statement:include.fs.nas netappsj/vol/vol1 nasMgmtClass toc=yesIncrbydateUse the incrbydate option with the incremental comm<strong>and</strong> to back up new <strong>and</strong>changed files with a modification date later than the last incremental backupstored at the server, unless you exclude the file from backup. Files added at theclient after the last incremental backup, but with a modification date earlier thanthe last incremental, are not backed up.Recommendation: Files that are modified or created after their respective directorywas processed by the <strong>Tivoli</strong> <strong>Storage</strong> <strong>Manager</strong> client, but be<strong>for</strong>e theincremental-by-date backup completes, are not backed up <strong>and</strong> will not be backedup in future incremental-by-date backups, unless the files are modified again. Forthis reason, a regular incremental backup should be run periodically, withoutspecifying the incrbydate option.An incremental-by-date updates the date <strong>and</strong> time of the last incremental at theserver. If you per<strong>for</strong>m an incremental-by-date on only part of a file system, thedate of the last full incremental is not updated <strong>and</strong> the next incremental-by-datewill back up these files again.Important:Chapter 10. Using processing options 337

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!