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 Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Zoltan Forray/AC/VCU
Sent: Wednesday, December 09, 2009 10:06 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Restoring LARGE server

I don't know about the original server but since it is handling sooooo
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 situation/configuration. I just need a way
to manage restoring soooo many objects.

If I am correct that MEMORYEFFICIENT is only for backups, I question why
there wouldn't be a similar option for restoring?  It goes without says
that if you have to use this option for backup because of the sheer number
of objects, there should be something to handle the restore.  After all,
isn't restoring a critical part of the backup process?



From:
Richard Sims <rbs AT BU DOT EDU>
To:
ADSM-L AT VM.MARIST DOT EDU
Date:
12/09/2009 09:46 AM
Subject:
Re: [ADSM-L] Restoring LARGE server
Sent by:
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>



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.)

    Richard Sims