12.07.2015 Views

Installation and User's Guide

Installation and User's Guide

Installation and User's Guide

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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Note: The include.fs.nas option does not apply to incremental snapshot differenceincremental backup.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 Tivoli Storage Manager. 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 platform, NAS file system specifications use the forwardslash (/) separator, as in this example: /vol/vol0.v NAS file system designations on the comm<strong>and</strong> line require brace delimiters {}around the file system names, such as: {/vol/vol0}. Do not use brace delimitersin the option file.Use the following syntax:►► pattern mgmtclassname toc=value ►◄ParameterspatternSpecifies the objects to include for 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 496 for more information.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.Important: Files that are modified or created after their respective directory wasprocessed by the Tivoli Storage Manager client, but before the incremental-by-datebackup completes, are not backed up <strong>and</strong> will not be backed up in futureincremental-by-date backups, unless the files are modified again. For this reason, aregular incremental backup should be run periodically, without specifying theincrbydate option.An incremental-by-date updates the date <strong>and</strong> time of the last incremental at theserver. If you perform 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-datebacks up these files again.Chapter 12. Processing options 401

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

Saved successfully!

Ooh no, something went wrong!