--> Is Restore Time(RTO) less while coping data directly from copy storage
pool.

No one answered this so I will give it a shot.
Actual speed depends mainly on collocation settings of copy pool(s). If
copy pools are set with "lower" collocation that primaries you can expect
small or significant performance drop. Evaluate it yourself - restoration
from collocated vs. non-collocated or filespace-collocated
vs.node-collocated pool - it does not matter is it primary or copy but
collocation really matters.

The only chance to have restore time from copy pool less than from primary
pool would be for non-collocated primary and collocated copy pool (I guess
no one implements TSM that way).

Zlatko Krastev
IT Consultant






Srinivas Polu <SrinivasP AT HCLCOMNET.CO DOT IN>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
11.04.2003 06:46
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        RTO while restoring client data


Dear all,

        I had one doubt on Restoring client data when my TSM server
crashes.
Suppose, if my tsm crashes after installing the new server and restoring
conf files, tsm database. Can i Directly access Copy storage pool and
retrive data, instead of first restoring the data to primary storage pool
and then restore.

        If it can restore from copy storage pool, what is the procedure on
what commands shall i use. Is Restore Time(RTO) less while coping data
directly from copy storage pool.


        Pl. clarify.


Regards,
Srini