Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Overriding Global Include / Exclude list

Status
Not open for further replies.

jcolon1

Programmer
May 30, 2001
2
US
I'm an inexperienced TSM user, and have what might be a simple question. We're using TSM version 5 on AIX. Our server-level include / exclude file has the following directory excluded:

Code:
*** FILE INCLUDE/EXCLUDE ***
Mode Function  Pattern (match from top down)  Source File
---- --------- ------------------------------ --------------
Excl Directory /dbload*                       Server

This is all fine and dandy, because when I do the full server backup, I don't want to backup any files in this directory.

However, I do want to run a separate selective backup to copy the directory structure of this using the -dirsonly option. When I try to do the selective backup, I get the message:

Code:
ANS1115W File '/dbload01/*' excluded by Include/Exclude list

Is there a way to override the server-level include / exclude list for one particular command?

Thanks!
 
When you say server-level, do you mean TSM server level, or NODE level? I believe TSM Client overrides the server unless the clopt on the TSM server has FORCE=YES.
 
Thanks for your reply, ProbablyDown.

My exclude is on the node (client) level. Guess that wasn't very clear.

On the node level, I need to have that directory excluded, so that when the backup of the data files executes, the files in that directory are not copied.

But, I want to have another backup job that runs a command like this:

dsmc selective -dirsonly "/dbload01/*"

and backs up the directory structure of the the /dbload01 directory, without the files, in spite of the fact that the directory is excluded on the node level. Does that make sense? Can I even do it?

 
Hmm not sure... you *could* just create a second TSM node and back that stuff up there.. don't exclude anything there and just run the dirsonly backup there..

Just a thought, All you would need is another stanza in your dsm.sys and another dsm.opt file maybe call it dsm_dirs.opt and point it to the other node?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top