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.
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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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
Check this article
http://www.petri.co.il/move_exchange_stores_to_a_different_disk.htm
And Stop the OS level AV, or exclude the folders from scanning where you are moving.
ASKER
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!
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!
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.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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
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
ASKER
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
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
Thanks for the points, glad it worked.
http://technet.microsoft.com/en-us/library/cc733145(WS.10).aspx