Tivoli Header

Tivoli Storage Manager for Windows Backup-Archive Clients Installation and User's Guide

Processing Rules when Using UNC Names

When processing files with UNC names, Tivoli Storage Manager uses the rules described above. In addition, the following rules apply.

Explicit Use of UNC names for Remote Drives

Tivoli Storage Manager will recognize explicit use of UNC names for remote drives. For example, in the list below the UNC name pattern can be substituted for the DOS pattern. Assume local drive letter r: is mapped to remote share point \\remote\c$, s: is mapped to \\remote\share4, and t: is mapped to \\remote\share2.

Table 9. Using UNC Names with Include and Exclude Patterns

UNC Name Pattern DOS Pattern
\\remote\c$\include\file.out 
r:\include\file.out
\\remote\c$\...\file.out 
r:\...\file.out
\\remote\share4\exclude\*
s:\exclude\*  
\\remote\share2\...\?.out 
t:\...\?.out

Conversion of DOS Pathnames for Fixed and Remote Drives

Tivoli Storage Manager converts DOS pathnames that are mapped to remote share points. For example, a remote share point that is mapped from

r:\test\...\exclude.out

to

\\remote\share\test\...\exclude.out

is converted. Remote share points that are not mapped are not converted. Files on removable media are not converted.

File Space Name Matching

File space names that are specified with a wildcard must be UNC names. For example, the specification ?:\...\test.txt only matches files named test.txt which are specified in one or more of the following ways:

\\server\d$\test.txt
\\server\share\directory\test.txt
a:\diskette\test.txt

Character Class Matching

The following examples show valid matches using character class:

\\remote[a-z]\share\file.txt
matches    \\remotea\share\file.txt
 \\remote\share[a-z]\file.txt
matches     \\remote\sharex\file.txt
 \\remote\share\file[a-z].txt
matches     \\remote\share\fileg.txt 


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]