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
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
Great analysis. Thanks!
I have a hard time imagining how file-based restores could be faster
than image-based restores. File restores have to create each of the
300,000 files, right? and file-create, during restore, is a lot slower
than file-open, during backup.
But I guess if you have a lot
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
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
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: Re:
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
You can also modify dynamic memory to help with the memory issue.
It does require a reboot to implement, but it has worked great for a bunch of
our larger 32bit servers.
Here is the Microsoft article.
http://support.microsoft.com/kb/304101
-Original Message-
From: ADSM: Dist Stor
Del and/or Andy can probably answer this, hopefully in a way that a
non-hardware/OS person, like me, can understand.
Our hardware guy upgraded a driver on my 6 AIX boxen. As a result, my thruput
went to hell, with backups running, not at Kb/s, but bits/s. But not on
clients with the MSSQL or
- Fred Johanson f...@uchicago.edu wrote:
Del and/or Andy can probably answer this, hopefully in a way that a
non-hardware/OS person, like me, can understand.
Our hardware guy upgraded a driver on my 6 AIX boxen. As a result, my
thruput went to hell, with backups running, not at Kb/s,
Hello Everybody,
I would like to share next information. I think it can be interesting for those
who put fingers into TSM Client 6.1.2 already.
If upgrade TSM Client 5.5.X/6.1.0.X to 6.1.2.0 is required on server with TDP
for SQL 5.5.2.1 only next sequence of actions leads to working
11 matches
Mail list logo
