It is up to you how to set-up the TSM server policies. If you prefer to
save space on off-site tapes you have to pay a price and it is many tape
mounts. If you want speedy restores as from primary tapes you can
collocate off-site pool as well. An example:
business critical servers - primary collocated by filespace, copy
collocated by node
important servers - primary collocated by node, copy not collocated
other servers (or notebook of financial manager saving on tapes :-) -
not collocated both primary and copy

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
Sent by:        "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To:     ADSM-L AT VM.MARIST DOT EDU
cc:

Subject:        Re: DISASTER  Client Restores Slow

I am sure TSM will wait. And while we're on this subject, we are looking
at
Disaster Recovery plans and the path we must take using TSM to recover a
couple hundred servers.  It looks bleak.

We are finding that, due to incremental forever backups, recovery times
are
extremely long because of tape mount after tape mount after tape mount. In
a
real disaster, we expect to take an entire day or more to recover a single
server. With a limited number of tape drives the recovery time required
for
100 servers could take weeks.

Has anyone else run into this dilemma? What is TSM's direction? How can I
speed up the recovery process?

John G. Talafous              IS Technical Principal
The Timken Company            Global Software Support
P.O. Box 6927                 Data Management
1835 Dueber Ave. S.W.         Phone: (330)-471-3390
Canton, Ohio USA  44706-0927  Fax  : (330)-471-4034
talafous AT timken DOT com           http://www.timken.com