ADSM-L

Re: [ADSM-L] Restoring LARGE server

2009-12-09 11:14:29
Subject: Re: [ADSM-L] Restoring LARGE server
From: "Laughlin, Lisa" <Lisa.Laughlin AT OA.MO DOT GOV>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 9 Dec 2009 10:13:58 -0600
How about using just the CLI and the no-query restore option?

thanks!
lisa                    


> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of Ochs, Duane
> Sent: Wednesday, December 09, 2009 9:57 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] Restoring LARGE server
> 
> Zoltan,
> Have you attempted a Point in Time restore from command line?
> That might help with the number of inactive files you are
experiencing.
> If that is not an option, you may have to go a couple directories at a
> time.
> 
> I have only had experience restoring up to 9M files and the one time I
> did it used PIT and worked fine, turned maxmp up to 4. It certainly
> took a while. But it did complete.
> 
> What OS are you using on the client ?
> 
> 
> Duane
> 
> 
> 
> 
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of Zoltan Forray/AC/VCU
> Sent: Wednesday, December 09, 2009 7:51 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Restoring LARGE server
> 
> Trying to restore a LARGE Windows server.  Over 40M objects.  Client
is
> 6.1
> 
> As you can imagine, we have had to use the journal as well as
> MEMORYEFFICIENT to perform backups.
> 
> If I read correctly, MEMORYEFFICIENT is ONLY for backups.  Obviously
> the
> journal is of no value since the restore is to a new machine/location.
> 
> The other issue gumming up the works is that the backups have been
> failing
> (drive array problems/corruption) and thus TSM has marked almost
> everything
> as "inactive".  A first, NQR restore (just selected the drive) attempt
> only
> restored 90GB (of 600G+) before "finishing successfully".  But when I
> choose to pick inactive as well as active, the NQR is disabled.
> 
> The server transfers down 1GB of metadata before the client chokes on
> "insufficient memory".
> 
> So, how am I supposed to restore this many objects, besides picking
one
> directory at a time, which is not to say that some directories are
> large
> enough to also cause a "not enough memory" situation?
> 
> Suggestions on how to handle this?