I would say the advice was incomplete and your "feelings" are quite
correct.
Restore of a TSM server DB is the first step inoperational recovery
process. Next (though not so lengthy) step is to configure the libraries,
drives, paths, and ... storage agents + polled clients.

Imagine the mess when the restored "SAPPROD" contacts a node in polling
mode and convinces it to perform a backup. Execution of
preschedule&postschedule scripts in the middle of the day might become a
big headache.

The problem wouldn't be resolved by simply renaming restored server to
SAPQAS as the library manager knows that SAPPROD is the onwer of those
libvolumes. The mess can get deeper and deeper.


What actually are you trying to accomplish?

Zlatko Krastev
IT Consultant






Willem Roos <wroos AT SHOPRITE.CO DOT ZA>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
11.12.2003 13:23
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Multiple TSM Servers/Informix restore


Hi list,

May i pick your collective brain?

We have multiple TSM Servers (called TSM_SERVER, SAPPROD and SAPQAS).
TSM_SERVER owns the 3584, SAPPROD and SAPQAS are library clients.

When we wish to restore an Informix database backed up on SAPPROD to
SAPQAS, our local friendly TSM support company has advised us to

1) backup tsm db on SAPPROD,
2) restore SAPPROD's tsm db to SAPQAS
3) copy ixbar file
4) and restore

However, i have this strange feeling that TSM_SERVER is now getting
terribly confused between SAPPROD (on sapprod) and SAPPROD (on sapqas)
and starts messing up tape [dis]mount requests etc.

What do you think?

Many thanks in advance,

-------------------------------------------
  Willem Roos - (+27) 21 980 4941
  Per sercas vi malkovri