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.