Print Page - moving TSM server content to another existing TSM Server

Title: moving TSM server content to another existing TSM Server
Post by: Michel de Kraker on April 04, 2013, 05:47:18 AM

Hi All,

At the moment i am using a dedicated TSM server voor CMOD archiving. TSM Server version is 5.4
Plan is to move all content of this TSM server to an existing TSM server which we are using for normal backup/restore.
This existing TSM server is al TSM server level 6.2.5.0

I am looking for best practices or experiences in doing this. Is it wise? Or should i leave the TSM server for CMOD a dedicated one?

Thanks for your replies.

Kind regards,

Michel.

Title: Re: moving TSM server content to another existing TSM Server
Post by: Justin Derrick on April 04, 2013, 10:08:19 AM

I normally recommend that folks upgrade their TSM system (changing hardware if they must) and keep it separate from their enterprise backup system.

Rationale is:

Load and retrieval patterns are very different, and the backup team won't like the random load/retrieval cycles that CMOD normally sees.
It complicates the addition of new storage nodes -- especially when you follow my recommendation for each Application Group having it's own storage node.
Expiration processing (a database intensive job on TSM) normally occurs on CMOD at the same time the backup servers are the most busy creating enterprise backups

-JD.

Title: Re: moving TSM server content to another existing TSM Server
Post by: Michel de Kraker on April 04, 2013, 12:32:23 PM

Thank you JD.

Makes perfectly sense.

Michel.

OnDemand Users Group

Support Forums => CMOD for Multiplatforms => Topic started by: Michel de Kraker on April 04, 2013, 05:47:18 AM