moving information strore to seperate server (Full Version)

All Forums >> [Microsoft Exchange 2000] >> Information Stores



Message

smueller -> moving information strore to seperate server (17.Jan.2007 4:47:33 PM)

Hi all - I've seen similiar but not quite the same questions - my apologies in advance if this has been asked before. 

Specifically - is is possible/safe to move the information store to a server that is seperate from the actual Exchange install?  I know it's easy enough to move the location of the stores/logs on the same server but was curious if they could be moved to a share on another server.  I'm simply running out of room on the existing server and I want to be able to buy some time while we plan for our transistion to 2007 Server.  Any insight would be greatly appreciated. 



Taelo -> RE: moving information strore to seperate server (19.Jan.2007 8:18:15 AM)

I would imagine so.  Can you not copy the database to your other server, share it, and link to it from the Exchange console?



smueller -> RE: moving information strore to seperate server (19.Jan.2007 9:33:32 AM)

Thanks for the reply.  I would also imagine it could be done but, before doing so, I was looking for some feedback from anyone that had done something similar - including a brief how-to.  If I get brave enough, maybe I'll try it later today and report back my results - good, bad and ugly.



Taelo -> RE: moving information strore to seperate server (19.Jan.2007 11:52:11 AM)

If I recal correctly, I think you just view the properties of the particular mail store, and there is an option to change the path.  You must move the DB prior to doing this however.  It won't move the DB automatically.



smueller -> RE: moving information strore to seperate server (23.Jan.2007 6:39:10 PM)

well, things have gone from bad to worse.  the IS was dismounted and when i try to remount it I get messages about the database is not consistent.  I've run the eseutil utility to try to do a repair and it get through about 30 percent of the repair and then throws an error about there not being and space left on the drive.  However, I have used the /t switch to have the temporary database built on another drive - with plenty of space.  I've watched the temp db build as the process chugs along.  I am currently very low on space on the drive of the IS so I assume this message is related to something the repair process is trying to write to that drive.  Can anyone confirm that you need space on the drive where the IS is housed even if you designate a different temp db location?  More importantly, is there any way to run this process if there isn't sufficient space on the drive where the IS is housed?  Any help would be greatly appreciated.



Page: [1]