• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1740
  • Last Modified:

Moving large exchange 2003 database files - Insufficient resources - server 2003

Okay, I'm hoping one of you Exchange geniuses I've already learned so much from can help me with this one.  I'm in the process of moving my Exchange03 databases from one SAN volume to another, so as far as windows (server2003 32bit) is concerned, it is disk to disk.  

In testing, we tried to copy a moderately large (30gb), dismounted database file to the new volume.  EVERY time we try it, it fails with "insufficient resources."

Now I know that this is not how you are supposed to move exchange databases and that I am supposed to do it through ESM.  I plan to.  However, I want to make absolutely sure that it is going to succeed because this server cannot suffer any more outages.  It's already had several, and issues with the underlying disk have caused issues with backups, log truncation, etc....   Suffice to say it absolutely has to work the first time.

So, with that in mind, what are your thoughts on relocating a DB via ESM even if a 30+gb file cannot be moved via explorer?  Does ESM employ another method or does it just move the file the same as if you did it via explorer?  What will happen if I attempt to move a database using ESM and it fails due to insufficient resources?

Any guidance on this issue will be greatly appreciated.
0
Jon Brelie
Asked:
Jon Brelie
  • 4
  • 3
  • 3
  • +1
2 Solutions
 
mcv22Commented:
Try using robocopy to transfer the file. It allows you to resume transfers in case it is interrupted and can retry on failure.

http://technet.microsoft.com/en-us/library/cc733145(WS.10).aspx
0
 
MegaNuk3Commented:
Use
Eseutil /y

Or esefile to do the copy as they are made for copying Exchange Database files. Ensure any file level AV excludes EDBs from scanning.
0
 
AmitIT ArchitectCommented:
Never ever use robocopy for Exchange db move. Use need to do it from ESM

Check this article

http://www.petri.co.il/move_exchange_stores_to_a_different_disk.htm
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell┬« is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
AmitIT ArchitectCommented:
0
 
AmitIT ArchitectCommented:
And Stop the OS level AV, or exclude the folders from scanning where you are moving.
0
 
Jon BrelieSystem ArchitectAuthor Commented:
Thanks all.  My concern using ESM to move the database is that it will fail like Explorer copies do.  I'm planning on doing an Eseutil copy over the weekend on one of our larger EDB/STM pairs to see how it goes.

What would be the steps for bringing the copied database back up in Exchange?  Changing DB properties in ESM complains that the file already exists.  Is there a standard way of doing this, or do I just change the values in ADSIEdit?  Also, do I need to restart any services, or should it just mount after the attributes are changed?

Thanks!
0
 
AmitIT ArchitectCommented:
First it never fails. I last 8 years, i have done this 1000 times. It is safest method and Exchange manages everything. Rest is you need to decide. I still prefer ESM.
0
 
MegaNuk3Commented:
Just change the values in ADSIedit, wait a little while for AD replication and then when ESM on that server shows you the correct paths to the files mount the DB.
0
 
Jon BrelieSystem ArchitectAuthor Commented:
Eseutil /y and updating AD attributes was the best choice in this situation.  Not only was it faster in my testing, but it copies vs. moving so that there is easy fall back if something doesn't work right.  I successfully transferred a live 120gb EDB/STM last night and have more queued up for the weekend.

Everything I read about ESM moves indicated that it utilizes the underlying win32 copy, which in my case has not been working for large files.

Thanks all, for your comments
0
 
Jon BrelieSystem ArchitectAuthor Commented:
Oh, and for anyone wondering about the ADSI attributes, you can find them here:

Configuration, <domain>, Services, Microsoft Exchange, <exchange org>, Admin Groups, <your admin group>, Servers, <Server Name>, Information Store, <storage group>

select your database properties.  Paths to EDB/STM are stored in:

MsExchEDBFile & MsExchSLVFile
0
 
MegaNuk3Commented:
Thanks for the points, glad it worked.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

  • 4
  • 3
  • 3
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now