inactive. That way you can leverage NQR to
get these big boys.
-Ken
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Zoltan Forray/AC/VCU
Sent: Thursday, December 10, 2009 2:10 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Restoring LARGE serve
[mailto:ads...@vm.marist.edu] On Behalf Of
Zoltan Forray/AC/VCU
Sent: Thursday, December 10, 2009 2:10 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Restoring LARGE server
AFAIK, NQR isn't something you can "pick and choose" - if it was, I
would.
>From the book:
When you ent
Of course yes. Fro command line or from GUI.
From: ADSM: Dist Stor Manager [ads...@vm.marist.edu] On Behalf Of Zoltan
Forray/AC/VCU [zfor...@vcu.edu]
Sent: Thursday, December 10, 2009 6:14 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Restoring LARGE s
Zoltan
is there another 64bit server you could use? maybe mount the disks to
this other 64 bit server, do the restore there and then unmount/remount
on the 32 bit server.
The borrowed 64 bit server could perhaps continue to serve its usual
function as well as do the restore, depending of course
Zoltan:
Have you looked at the server-side of this situation? You can optimize
for backup or restore but not usually both. While you may slam TBs to
the server in a short window of time, you usually are increasing the
window on the restore-- unless you've thought about it when
architecting.
Do
AFAIK, NQR isn't something you can "pick and choose" - if it was, I would.
>From the book:
When you enter an unrestricted wildcard source file specification on the
restore command and do not specify any of the options: inactive, latest,
pick, fromdate, todate, or |volinformation, the client uses
Can I do a PIT of 1-specific volume to a different location?
From:
"Ochs, Duane"
To:
ADSM-L@VM.MARIST.EDU
Date:
12/09/2009 10:58 AM
Subject:
Re: [ADSM-L] Restoring LARGE server
Sent by:
"ADSM: Dist Stor Manager"
Zoltan,
Have you attempted a Point in Time restore from command line?
That migh
Manager [mailto:ads...@vm.marist.edu] On Behalf Of Zoltan
Forray/AC/VCU
Sent: Wednesday, December 09, 2009 10:06 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Restoring LARGE server
I don't know about the original server but since it is handling so
many files and terabytes of storage, I
I am restoring 2-drives (F: and G:) with 27M and 22M objects and 900G and
700G, respectively. Since the F: was going to be so problematic, I
decided to start the G: last night at 11:30pm since I can run
NQR/unattended. So far as of this writing, it has restored 15M/250GB.
Not sure if the PIT wi
How about using just the CLI and the no-query restore option?
thanks!
lisa
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf
> Of Ochs, Duane
> Sent: Wednesday, December 09, 2009 9:57 AM
> To: ADSM-L@VM.MARIST.EDU
> Subject:
I don't know about the original server but since it is handling so
many files and terabytes of storage, I would assume 64-bit.
As for the server I am restoring to, it is a W2K3SP2 Enterprise Edition
quad-core but am assuming 32-bit since it doesn't say 64-bit.
Either way, I can't change this
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
Zoltan -
Your posting provides no information about the Windows system. A
large server should be 64-bit, where one would expect the 64-bit
client to easily handle the task. (If it's a 32-bit Windows, that's a
bad choice on the part of the Windows administrators - one of those
plan-ahead things.
13 matches
Mail list logo
