ADSM-L

[ADSM-L] AW: Looking for suggestions to speed up restore for a Windows server

2007-08-28 08:45:48
Subject: [ADSM-L] AW: Looking for suggestions to speed up restore for a Windows server
From: Salak Juraj <J.Salak AT ASAMER DOT AT>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 28 Aug 2007 14:43:43 +0200
GREAT bird-view of approaching a problem! 

I *do* know that prior to solving a problem the problem per se has to be 
checked, but I oten forget to do that. You did not. Juraj

-----Ursprüngliche Nachricht-----
Von: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] Im Auftrag 
von Schaub, Steve
Gesendet: Dienstag, 28. August 2007 13:20
An: ADSM-L AT VM.MARIST DOT EDU
Betreff: Re: Looking for suggestions to speed up restore for a Windows server

Tom,

Having just gone through a similar scenario 2 weeks ago, here was my very 
non-technical fix:

(me) "Hello, end-user?  I'm not going to be able to get your 800GB of data 
restored in 2 hours like you want.  Care to narrow down the restore to what you 
really need?"
(end-user)  "Oh.  Well, we really only need the 10GB of data in the xxxx and 
yyyy directories to run the important stuff."
(me)  "Ok, done."

Maybe this wont apply to you, in which case the monthly image backup seems like 
a good suggestion.

Good luck,

Steve Schaub
Systems Engineer, WNI
BlueCross BlueShield of Tennessee
423-535-6574 (desk)
423-785-7347 (cell)
***public***


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Kauffman, Tom
Sent: Monday, August 27, 2007 2:40 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Looking for suggestions to speed up restore for a Windows 
server

We had our fall D/R hotsite test last week and all went well -- except for the 
recovery of our primary Windows 2003 file sharing system. It just takes WAY too 
long.

Part of the problem is the sheer number of files/directories per drive
-- I'm working with the Intel/Windows admin group to try some changes when we 
swap this system out in November.

Part of the problem is that the directory structure is scattered over a mass of 
other backups. I'm looking for suggestions on this.

The system is co-located by drive, but only for five of the nine logical drives 
on the system. I may have to bite the bullet and run all nine logical drives 
through co-location.

Is there any way to force the directory structure for a given drive to the same 
management class/storage pool as the data? I'm thinking I may have finally come 
up with a use for a second domain, with the default management class being the 
one that does co-location by drive. If I go this route -- how do I migrate all 
of the current data? Export/Import?
How do I clean up the off-site copies? Delete volume/backup storage pool?

I'm on TSM Server 5.3.2.0, with a 5.3 (not sure of exact level) client.

TIA

Tom Kauffman
NIBCO, Inc
CONFIDENTIALITY NOTICE:  This email and any attachments are for the exclusive 
and confidential use of the intended recipient.  If you are not the intended 
recipient, please do not read, distribute or take action in

reliance upon this message. If you have received this in error, please notify 
us immediately by return email and promptly delete this message and its 
attachments from your computer system. We do not waive attorney-client or work 
product privilege by the transmission of this message.

Please see the following link for the BlueCross BlueShield of Tennessee E-mail
disclaimer:  http://www.bcbst.com/email_disclaimer.shtm
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten 
haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. 
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht 
gestattet.

This e-mail may contain confidential and/or privileged information. If you are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorised 
copying, disclosure or distribution of the material in this e-mail is strictly 
forbidden.

<Prev in Thread] Current Thread [Next in Thread>