You said is a W2003 server. What are the details of it?
CPU, memory, etc. Maybe that is problem? Or is their
restore time including not just the DB restore, but
all the "prep" work, etc. involved in the restore?
DL
>>> Neil Sharp <tsmrocks AT GOOGLEMAIL DOT COM> 2/4/2008 12:32 PM >>>
Thanks Charles for responding
The majority of the restore time is spent in formatting the DB and logs.
They are actually restoring from a fileclass backup of the TSM DB. I know
when they told me these times I found them hard to believe as well.
On 04/02/2008, Hart, Charles A <charles_hart AT uhc DOT com> wrote:
>
> I think the first question id 45GB restored in 5Hours, that's 5 GB hour
> / 1.3MBS Second... What kind of Tape Drive are you using, is it on its
> own HBA (Don't Mix Disk / Tape I/O down same path)
>
> Sounds like you have an I/O challenge. As far as the Idea below, never
> tried, but take in consideration that if the TSM DR box is in a
> different geographical location you'll have to use FCIP or Disk Frame
> replication to gain access to those volumes.
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of
> Neil Sharp
> Sent: Monday, February 04, 2008 10:28 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: [ADSM-L] TSM DR restore query
>
> Hello I was wondering if anybody could help or advise with the following
> question.
>
> I need to devise a solution to speed up DR for one of my customers.
> Currently their DR solution is the classic restore from TSM DB tape and
> then load all of the off site tapes into the DR library and then perform
> the client restores. The problem is that the TSM DB restore can take in
> the region of 5 hours. The TSM DB is 45GB.
>
> I was thinking of using the following method. Can any one see any issues
> with this?
>
> *On the primary TSM server:*
>
> They have a Windows 2003 Standard Edition TSM server. I am proposing
> that we set up TSM DB and log mirroring, one copy on local disk and the
> second copy on SAN attached disk.
>
> *On the DR site:*
>
> They also have a TSM 2003 Standard Edition TSM server. When DR is to be
> tested / invoked, I would propose that they re-zone the DR TSM server to
> access the LUN that contains the DB and logs. Ensure that the DR TSM
> server's dsmserv.dsk points to the mapped drives.
>
> Note the the TSM tape library is also SAN attached.
>
> Any comments / experiences would be appreciated.
>
>
> This e-mail, including attachments, may include confidential and/or
> proprietary information, and may be used only by the person or entity to
> which it is addressed. If the reader of this e-mail is not the intended
> recipient or his or her authorized agent, the reader is hereby notified
> that any dissemination, distribution or copying of this e-mail is
> prohibited. If you have received this e-mail in error, please notify the
> sender by replying to this message and delete this e-mail immediately.
>
#####################################
This message is for the named person's use only. It may
contain confidential, proprietary, or legally privileged
information. No confidentiality or privilege is waived or
lost by any mistransmission. If you receive this message
in error, please immediately delete it and all copies of it
from your system, destroy any hard copies of it, and notify
the sender. You must not, directly or indirectly, use,
disclose, distribute, print, or copy any part of this message
if you are not the intended recipient. Health First reserves
the right to monitor all e-mail communications through its
networks. Any views or opinions expressed in this message
are solely those of the individual sender, except (1) where
the message states such views or opinions are on behalf of
a particular entity; and (2) the sender is authorized by
the entity to give such views or opinions.
#####################################
|
