RE: Repairing / modyfing Exchange

Thank you Nathan Liu for your qiuck answer,
I haven't tried your solution yet. I'll setup a new server today to try it.

Also, because I have messed something up with the First Storage Group, if I
delete it and recreate it will I destroy everything? Is there a way to create
a new one without destroying everything?

""Nathan Liu [MSFT]"" wrote:

> Hello Georgek,
>
> Thank you for posting in the SBS newsgroup.
>
> Also, many thanks for Axel's great input.
>
> According to your description, I understand that you would like to move the
> Exchange Database to another disk, and restore the mailbox store. If I have
> misunderstood your concern, please don't hesitate to let me know.
>
> Question: Is there a way to move it to the D: partition which is about 40GB
> without destroying everething (including outlook web access)?
>
> Answer: Axel is right, please refer to the KB article 821915 to move the
> Exchange Database. For detailed information, you may refer to the below
> document:
>
> 821915 How to move Exchange databases and logs in Exchange Server 2003
> http://support.microsoft.com/?id=821915
>
> Moving Data Folders for Windows Small Business Server 2003
> http://go.microsoft.com/fwlink/?LinkId=49931
>
> Additionally, if you have a good backup of the original Exchange
> information store in case the original server is totally damaged, to
> restore the data back or mount the edb file on a newly installed Exchange
> server, the following essential naming scheme elements in your original
> organization must be the same as your new one.
>
> * The Exchange organization name.
>
> * The name of the administrative group to which the database belongs.
>
> * The name of the storage group to which the database belongs.
>
> * The logical database name itself.
>
> * The legacyExchangeDN value for the administrative group object that the
> database currently belongs to.
>
> For more information, please refer to the following link:
> http://www.microsoft.com/technet/prodtechnol/exchange/2000/support/dbrecovr.
> mspx
>
> However, in case there is some differentiation, Legacydn.exe could help you
> some.
>
> Legacydn.exe is a tool that you can use to perform the following tasks:
>
> - Change the Microsoft Exchange 2000 Server or Microsoft Exchange Server
> 2003 organization name.
>
> - Change the administrative group names.
>
> - View the legacyExchangeDN values.
>
> - Change the legacyExchangeDN values.
>
> Note We only support the use of the Legacydn tool in a lab environment. The
> tool works only in a single domain controller environment.
>
> For more information, please refer to:
>
> 324606 XADM: How to Use Legacydn.exe to Correct Exchange Organization or
> Administrative Group Names
> http://support.microsoft.com/?kbid=324606
>
> 293324 XADM: "C104173A" Error Message Occurs After You Restore the Database
> http://support.microsoft.com/?id=293324
>
> Furthermore, in case you have a good backup and meet the above
> requirements, when you recover the database in the RSG, you could still not
> recover the mailbox since the Exmerge file may not find the original user
> referenced in the original mail store. Following error will occur:
>
> Error! Cannot identify the user with the msExchMailboxGuid
> \3C\C8\7D\D7\99\C3\FCL\B5\E3\FEUWa\D6F. The legacyExchangeDN is
> /O=DOMAIN/OU=FIRST ADMINISTRATIVE GROUP/CN=RECIPIENTS/CN=USER.
>
> This is because the exmerge utility cannot find referenced user in the AD.
>
> In normal mail store, we could create a non-mail enabled user and connect
> the orphan mailbox in storage via Mailbox Wizard. However, in the RSG, it
> is not possible. We need to manually create new user and replace the
> msExchMailboxGuid via ADSI.
>
> In the Exmerge log, we may find filtered msExchMailboxGuid as
> \3C\C8\7D\D7\99\C3\FCL\B5\E3\FEUWa\D6F
>
> We may need to manually translate it to valid form via following rule
>
> \3C\C8\7D\D7\99\C3\FCL\B5\E3\FEUWa\D6F -> will become separated with spaces
> like this:
>
> 3C C8 7D D7 99 C3 FC L B5 E3 FE U W a D6 F -> we have to convert letters
> L,U,W,a and F back to Hex using ASCII table (attached as below)
>
> 3C C8 7D D7 99 C3 FC 4C B5 E3 FE 55 57 61 D6 46 -> this is our recovered
> msExchMailboxGuid
>
> Then, the whole steps on the SBS server will be:
>
> 1. Logon SBS server as built-in administrator
>
> 2. Restore the exchange database file (*.edb, *.stm) to the SBS server
>
> 3. Run Exchange utility and make sure it is in the Clean state
>
> 4. Create a new Recover Storage Group
>
> 5. Add database to Recover and select the only database you find
>
> 6. Delete all files created in the new Recover storage Group folder. Copy
> the backup edb and stm file to this folder and rename it as mentioned in
> the recovery storage group database settings.
>
> 7. On the Database tab of the Mailbox Store Properties dialog box, verify
> that the "This database can be overwritten by a restore" check box is
> selected.
>
> 8. Mount the store.
>
> 9. Create new users
>
> 10. Modify the msExchMailboxGuid properties mentioned above via ADSI.
>
> 11. Run the Exmerge program and export it to a PST file
>
> To get additional information, you may refer to the following document:
>
> Exchange 2000 Server Database Recovery
> http://www.microsoft.com/technet/prodtechnol/exchange/2000/support/dbrecovr.
> mspx#XSLTsection128121120120
>
> I am appreciated your time and cooperation. If anything is unclear, please
> feel free to let me know. I am looking forward to hearing from you.
>
> Best regards,
>
> Nathan Liu (MSFT)
> Microsoft CSS Online Newsgroup Support
>
> Get Secure! - www.microsoft.com/security
> ======================================================
> This newsgroup only focuses on SBS technical issues. If you have issues
> regarding other Microsoft products, you'd better post in the corresponding
> newsgroups so that they can be resolved in an efficient and timely manner.
> You can locate the newsgroup here:
> http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
>
> When opening a new thread via the web interface, we recommend you check the
> "Notify me of replies" box to receive e-mail notifications when there are
> any updates in your thread. When responding to posts via your newsreader,
> please "Reply to Group" so that others may learn and benefit from your
> issue.
>
> Microsoft engineers can only focus on one issue per thread. Although we
> provide other information for your reference, we recommend you post
> different incidents in different threads to keep the thread clean. In doing
> so, it will ensure your issues are resolved in a timely manner.
>
> For urgent issues, you may want to contact Microsoft CSS directly. Please
> check http://support.microsoft.com for regional support phone numbers.
>
> Any input or comments in this thread are highly appreciated.
> ======================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> --------------------
> >Thread-Topic: Repairing / modyfing Exchange
> >thread-index: AcWZO60uqBvsilGfRqK1aRaVFfNJEg==
> >X-WBNR-Posting-Host: 62.38.216.83
> >From: "=?Utf-8?B?R2VvcmdlSw==?=" <GeorgeK@xxxxxxxxxxxxxxxxxxxxxxxxx>
> >Subject: Repairing / modyfing Exchange
> >Date: Thu, 4 Aug 2005 14:30:03 -0700
> >Lines: 14
> >Message-ID: <E6068E70-842A-4C4E-9216-DDB46D66A00E@xxxxxxxxxxxxx>
> >MIME-Version: 1.0
> >Content-Type: text/plain;
> > charset="Utf-8"
> >Content-Transfer-Encoding: 7bit
> >X-Newsreader: Microsoft CDO for Windows 2000
> >Content-Class: urn:content-classes:message
> >Importance: normal
> >Priority: normal
> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> >Newsgroups: microsoft.public.windows.server.sbs
> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> >Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
> >Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:141646
> >X-Tomcat-NG: microsoft.public.windows.server.sbs
> >
> >Hi, we have a SBS2003 server and we used exchange. A few days ago our
> raid
> >crushed and we almost lost all our files. We managed to rescue most of
> them
> >but we had to reinstall the OS. By error I selected to keep the exchange
> >databases in c:\program files\exchsrvr which is only 20Gb (about 6GB free)
> .
> >Is there a way to move it to the D: partition which is about 40GB without
> >destroying everething (including outlook web access)?
> >Also due to the failure we want to restore the mailbox store from the
> >previous installation in order to get back the older messages, but I don't
> >know how. I only have all the directories with the databases. Is there a
> way
> >to save them and import them to the new one? We have only 12 mailboxes.
> >
> >Please Help!
> >
> >Thanks in advance
> >
>
>
.

Relevant Pages

  • RE: Exchange restore on SBS2003 from SBS2000 backup
    ... I agree with you that using ExMerge is a good ... How to recover or restore a single mailbox in Exchange 2000 Server ... >> the Exchange database from the SBS 2000 backup to the SBS 2003 Server. ...
    (microsoft.public.windows.server.sbs)
  • RE: Windows server 2003 SP1
    ... I agree with Marina that you must keep the same server name to restore Exchange database. ... please also refer to the following KB articles for restore Exchange database. ... >Do the same for the public folder store ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS2k Exchange recovery - HELP!
    ... as it pulls mail out into a SQL database. ... I discovered something else I didn't know about Exchange.. ... If I could have got OWA working from the RDP into the Server (so only ...
    (microsoft.public.backoffice.smallbiz2000)
  • RE: Repairing / modyfing Exchange
    ... Thank you for posting in the SBS newsgroup. ... Exchange Database to another disk, ... Moving Data Folders for Windows Small Business Server 2003 ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange is really messed up... (long)
    ... If you still have that PST with the data not merged into Exchange, ... Information Store First Storage Group: ... Information Store First Storage Group: The database engine has ...
    (microsoft.public.windows.server.sbs)