ADSM-L

Re: DISASTER Client Restores Slow

2002-05-17 13:52:40
Subject: Re: DISASTER Client Restores Slow
From: Nikolai Sonin <nfsonin AT ESIGROUP DOT ORG>
Date: Fri, 17 May 2002 10:53:40 -0700
Nikolai Sonin
System Architect
ESI Group
28381 Encina Drive Suite 100
Winters CA, 95694-9007
530-795-0200 ext. 235




"Talafous, John G." <Talafous AT TIMKEN DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
05/17/2002 07:33 AM
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: DISASTER  Client Restores Slow


You can use backup sets to create point in time restores of machines. Also
with that few tape drives have you considered collocation.  That way
especially with LTO a small server and several incrementals will fit on
one tape.
Our CEO's PC is backed up using TSM with Collocation to an LTO drive and
after a month of incrementals all his data sits on one tape.  A test
restore of his workstation took less than 3 hours.  Also if you have over
100 servers you need to get more tape drives.




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
<Prev in Thread] Current Thread [Next in Thread>