TSM can collocate (i.e, keep on the same tape) all files for one node, or
not. If you tell it NOT to, then a FULL restore can be slow - but full
restores are the exception rather than the rule. A single-file restore will
still be fast.
Not collocating files is good because it lets several nodes share one tape
volume - better use of your storage than havin a bunch of tapes all 10% full
(because the client only uses 7GB and the tape holds 70GB).
Collocating files is good because restores are fast - only one (or few)
volume mounts.
I usually advise collocation on business-critical servers, non-collocation
on desktops and such.
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Bernard Ruelas
Sent: Tuesday, May 08, 2001 12:18 PM
To: [EMAIL PROTECTED]
Subject: Newbie Concern on Restore Times
My company is looking at replacing Legato's NetWorker with
Tivoli's TSM, and I've been told by another competitor's
marketing rep that TSM restore time takes forever.
The problem occurs with the backup of a volume of 30GB+
over a week, then trying to restore it many changes later.
We plan to test this case, but does anyone have any horror
stories/previous experience or docs that would refute this?
I'm a little nervous about trusing what the competitor says....
Thanks in advance,
-Bern
_
Bern Ruelas | <[EMAIL PROTECTED]> () |_>
Sr Systems Engineer | /\ ___|__
Wk: (408) 428-5246 | \ \ ___/ | \__
Pgr: (888) 500-4043 | Are you excited?.... /_ \o) ____/ \______/ \____
