Different Copy Groups for one Client? 1

[EGR]

Hi,

we have got a TSM 5.3 Running.
Following question:

One of our Windows 2000 file servers has a directory that should be handled different from other directories on the server.

Is that possible?

For example the directory test1 should have following settings:
frequecy=1 verexists=nolimit verdeleted=nolimit retextra=30 retonly=10

Directory test2 should have this:
frequecy=1 verexists=1 verdeleted=10 retextra=1 retonly=30

Thanks in advance
/egr

 

[Yrrk]

Easy.. just create another management class in that domain that node is assigned to and ensure it's copygroup settings are as you desire. Then in the dsm.sys/opt file specify what you'd like to backup under that new management class.

e.g.

/somepath/* <newmgmtclassname>

Normally everything is backed up under the "default" management class and therefore assumes the default retention settings. When you want to have different settings for other file types or directory paths, you simply specify them explicitely in the options file.

Note you can also do this for many nodes by using TSM's client option set feature (help define cloptset) without having to go through and modify all the node's config files (dsm.opt/sys).

Note #2 - once you define the cloptset or do the above change in your options file, you'll notice the next time a backup is run that it will "rebind" all the files that are applicable to the new assignments. This "rebinding" in the backup log tells you it's changing the management class those files are assigned to in TSM's database. It doesn't back up those files again (unless they need to be). It simply tells TSM "hey this file is now under a new management class and you need to update the metadata to indicate this".

This could have a negative effect if your new management class has more aggressive retention settings. if your default management class specifies that you retain 10 copys of something and your new one says you retain only 5, the next time your TSM backup runs it'll do the following..

1. rebind all the files to the new management class which specifies only to retain 5 copies instead of 10
2. when "expire inventory" runs, it will expire 5 of your 10 copies (the copies that are no longer applicable to the new settings).

so be careful

 

[EGR]

Hi,

thank you very much for that clear answer?

Regards
/egr