setting up collocation-management class question 1

[gsavy]

Hello,

I'd like to set up collocation for one server. This server was originaly in a Storage pool (LTOSAN) with other servers. So I need to create a new storage pool for this server because I don't want the others servers to collocate

My problem is the following. The management class is associated with a storage pool. In my TSM implementation, the same management class is used for all the server using the pool LTOSAN.

So if I create a new stg pool, to use it I need to create a new mgmt class, and use this mgmt class with my server.

What will be the impact for a client to change all its management class ???

will it lose all the history version of backup files? what about archiving ?



Thanks for you help

 

[comtec17]

First you will need to move the backup files to the new Storage Pool.

Not sure why you need to create a new storage pool to do this. Multiple copy groups and management classes can use the same pool.

 

[gsavy]

Not sure why you need to create a new storage pool to do this."

--> because (my understanding) it's in the definition of the storage pool that you choose to collocate. This means that all clients using this stg pool will collocate. In my case I have 4 clients using the same stg pool, and now I want one of them to collocate. So I must create a storage pool for itself, because I don't want the 3 remaining clients to collocate.

 

[Yrrk]

You're correct you need to define it at the stgpool level. You're also correct you can do this by creating a new mgmt class. The impact will be that all previously backed up files which you are assigning to a new mgmtclass will now rebind to the new mgmtclass. In other words if you mistakenly set your copygroup to a different (shorter?) retention then you previously had, the next time you run a backup the files will rebind to the new mgmtclass thus giving them their new retention settings. If you happened to mistakenly make shorter retention settings then before, the next time expire inventory runs the files will be expired.

 

[gsavy]

Thanks for your answer

when you wrote "you can do this by creating a new mgmt class"

is there another way to do that ?

 

[Yrrk]

not really since as you pointed out, the management class is associated with the storagepool and collocation is specifically set at the stgpool level. You are on the right track..

The one neat thing with management classes is if you're backing up a single server, you can have all kinds of file-level granularity retention settings thanks to them. e.g. maybe you only want to keep 1 version of .txt files, no mp3's, 5 versions of .doc files, and store your .nsf (lotus notes) files in a different storagepool with collocation and different retention settings. Pretty simple with TSM. Just create new mgmt classes for each and then either in your options file or on the tsm server itself define their associations. e.g.:

include /.../*.txt txtmgtclass
include /.../*.doc docmgtclass
include /.../*.nsf nsfmgtclass
exclude /.../*.mp3

Everyting else goes to the "default" mgmtclass..

Lets see other software packages show that level of granularity for retention and storage management configurability.