No, As I said in the first email, it was a vm'ed lab scenario. I blew it out and built another, same topology, different server names though. One dc, one exchange server. Probably a Beta anomaly...
I'll make note of that event id the next time as I am will likely blow this one out soon again:) jlc From: Alex Fontana [mailto:afontana...@gmail.com] Sent: Tuesday, May 05, 2009 11:32 AM To: MS-Exchange Admin Issues Subject: Re: Exchange DB Portability Well...there used to be another server right? And AD knows about it...if it's the same AD setup that is. If it is then a move-mailbox -configurationonly is necessary to update AD. If this is a different AD/Exchange Org then you may need to run a clean-mailboxdatabase to expose the disconnected mailboxes. As for the event ID that is generated after mounting a pre-existing mdb on a new box, the only one I can find is Event ID 7043, Source: MSExchangeIS Mailbox, Category: IS/AD Interactions. The text refers to the GUID of the SystemMailbox. Hope this helps. On Tue, May 5, 2009 at 7:56 AM, Joseph L. Casale <jcas...@activenetwerx.com<mailto:jcas...@activenetwerx.com>> wrote: That's in essence what I did, except for the renaming. I made the new one the same name but since it's a single exchange server setup, there was no move-mailbox possible? Oh well... I'll just assume broken in Beta :) jlc From: Sobey, Richard A [mailto:r.so...@imperial.ac.uk<mailto:r.so...@imperial.ac.uk>] Sent: Tuesday, May 05, 2009 4:26 AM To: MS-Exchange Admin Issues Subject: RE: Exchange DB Portability Assuming DB portability in 2010 works the same as 2007, these are the high level steps I used to move all databases from one server to another. It works lovely. I've taken some of my own notes out that relate specifically to my organization. 1) Shut down Exchange on <old server>. Run ESEUTIL /MH <Path to DB file> and ensure it's in a clean shutdown state. 2) Mailbox databases should be set NOT to mount at startup. 3) Disable Exchange services and turn <old server> off. 4) Repoint the SAN presentations to <new server>. 5) Rescan the server so it sees the SAN disks and point them at the correct mount points or drive letters. 6) Create the new mailbox databases called NewDatabaseName.edb. 7) Set the AllowFileRestore flag on all new databases. 8) Rename the databases on disk from OldDataBaseName.edb to NewDataBaseName.edb. 9) Mount the databases on the new server. 10) Move the mailboxes from the old server to the new one with the -ConfigurationOnly switch. From: bounce-8515732-8066...@lyris.sunbelt-software.com<mailto:bounce-8515732-8066...@lyris.sunbelt-software.com> [mailto:bounce-8515732-8066...@lyris.sunbelt-software.com<mailto:bounce-8515732-8066...@lyris.sunbelt-software.com>] On Behalf Of Joseph L. Casale Sent: 04 May 2009 23:23 To: MS-Exchange Admin Issues Subject: Exchange DB Portability I had a lab setup with an E2k10 DB that had some data in it. I setup a new lab, same topology, different server names, used a cmdlet to create the Mailbox Database with the recovery switch specifying the pre-existing paths to the copied db (everything was copied over). It warned me that it needed to be in a clean shutdown state before mounting, so I checked it with eseutil /mh and it was. I mounted it without error but I couldn't enumerate the disconnected MB's in it? How does one accomplish this? Thanks! jlc ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~
