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

Moving an Exchange 2003 Database

For an unknown reason, an Information Store's .EDB and .STM files are in two different folder locations; E:\Exchsrvr\MDBDATA\inv.edb and E:\Eschsrvr\MDBDATA\inv.stm

II've tried moving the INV.STM file from it's current location, to the same location as the INV.EDB file, however I receive an error that there are not enough system resources to make the move.

The (E:) in which both files are located on has 92GB of free space. The files are 42GB and 7GB in size. So there is enough space free on this drive to move the files.

I'm not positive, but I have a feeling that it's copying a TEMP file to the (C:) drive, which only has 7GB free.

If this is the case, is there a command-line that enables me to move the database file, while specifying the location of the TEMP file, during the IS move process?
0
Dieck783
Asked:
Dieck783
  • 4
  • 3
1 Solution
 
Neil RussellTechnical Development LeadCommented:
E:\Exchsrvr\MDBDATA\inv.edb
E:\Eschsrvr\MDBDATA\inv.stm

Thats the SAME location.......
0
 
jbvernejCommented:
I don't recall that the ESM database file move operation need the TEMP directory. After unmonting database, files are directly moved to the new location on file system and registry and AD are updated. I can't see why a need of a TEMP dir will be needed...

- could you reboot the server (to recover a max of ressource) and retry the move ?
- do you have a realtime antivirus on the server that could lock the file during the move ?
try disabling it temporary

You can also do things manually; to do that follow the kb822676 - How to manually move the database file location in Exchange 2000 Server and Exchange Server 2003
http://support.microsoft.com/kb/822676/en-us
0
 
jbvernejCommented:
Neilsr:E:\Exchsrvr\MDBDATA\inv.edb
E:\Eschsrvr\MDBDATA\inv.stm

Thats the SAME location.......

are you sure ?  ;-)
yes if you read   X and S as the same letter !   LOL
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.

 
Dieck783Author Commented:
Thanks for the response JB. I'll look over that KB Article. I already have a reboot scheduled for the server this evening. I wasn't going to try moving it again after the reboot, but now I'll give it another try.

Also, thanks for pointing out the location, I couldn't think of a tactful way of correcting NeilSr.
0
 
Dieck783Author Commented:
The reboot did not resolve the issue. I still can't move the file's location. Currently researching the issue more.
0
 
jbvernejCommented:
Strange.


Could you post here the exact error message ?
0
 
Dieck783Author Commented:
Issue is still outstanding. Opened web ticket with Microsoft. Closing EE ticket.
0
 
Dieck783Author Commented:
n/a
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

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.

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