Re: Swing Migration ROCKS!
- From: "Jeff Middleton [SBS-MVP]" <jeff@xxxxxxxxxxxxxxxx>
- Date: Tue, 19 Jul 2005 14:00:08 -0500
Armand,
Just to clarify on this one point, it shouldn't be too surprising that among
the SBS MVPs are some of my closest friends, people I know beyond the
discussions here. Like anyone's friends, occasionally the have the means to
contact me that I simply can't extend to the public much less even to my
customers world wide. In this case, I was at a conference which was attended
as well by other SBS MVPs, and getting a message passed along via friend to
friend occasionally works,l even though I was working each day. :)
I think the important point is that Frank was trying to ensure that I was
aware that you were stuck and needed some more help.
For anyone interested, the diagnosis and resolution of Armand's issue was as
follows:
== Problem:
Store won't mount when attempting to transfer the Information Store intact
from a previous SBS 2003 Server being replaced via Swing Migration with a
new SBS 2003 Server (as a hardware upgrade with clean install of SBS in the
process, but retaining the original domain).
Attempts to mount the store returned errors.
== Diagnosis and Resolution
Part A
----------
The initial diagnosis was that there were corrupted pages in the Information
Store that needed repair.
That was repaired via:
http://support.microsoft.com/default.aspx?scid=kb;en-us;810190
The "hard repair" section was done, not the Exmerge. Errors were found and
resolved, Fixes = 0 after 3 passes completed.
Part B
----------
After the repairs were completed, the Store would still load on the original
server normally, and the database size was reduced substantially, by more
than half. However, the store would not mount on the new server running SBS
2003 with the same domain and server name configuration.
Further analysis revealed that the error messages were now different. At
this point, it became clear that the two servers were not on the same SP
level. The target server was brought up to Exchange SP1 and Windows 2003 SP1
to match what was on the original server. (This had been overlooked.)
Following the SP updates, the store mounted as normally expected.
- Jeff Middleton
YCST@xxxxxxxxxxxxxxxx
"Armand Salmon" <ArmandSalmon@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D1C3DA21-1D88-4EC3-928B-8D7D14AF1366@xxxxxxxxxxxxxxxx
> I find that you knowing Jeff was working with me directcly suprsising
since I
> read your post before Jeff helped me. How did you know that?
>
> Just Curious
>
> Armand
>
> "Frank McCallister SBS MVP" wrote:
>
> > Matt I believe Jeff is working directly with Armond on this issue.
> >
> > --
> > Frank McCallister SBS MVP
> > COMPUMAC
> > "Matt Gibson" <mattg@xxxxxxxxxxxxxxx> wrote in message
> > news:%236SCeIriFHA.3656@xxxxxxxxxxxxxxxxxxxxxxx
> > > You'll have to give us more information...what are you swinging to and
> > > from? Service pack levels?
> > >
> > > Matt Gibson - GSEC
> > >
> > > "Armand Salmon" <ArmandSalmon@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
> > > news:95B9E618-FD43-4F4D-A5CC-01E6887180A0@xxxxxxxxxxxxxxxx
> > >> Glad your swing was successful David, Wish I could say the same
myself.
> > >> Maybe you can help me with this issue? :
> > >>
> > >> I am having trouble Mounting the Information Store from my
> > >> source server to the target server. The swing method aside, this
would
> > >> be
> > >> considered doing an Offline restore of the MDBDATA directory located
at
> > >> C:\Program Files\Exchsvr\MDBDATA. The exchange services are stopped
both
> > >> on
> > >> the source and target server allowing for the data to be copied off
to
> > >> say an
> > >> external drive, and then the empty store on the target server is
renamed,
> > >> and
> > >> a new MDBDATA folder is created where the source MDBDATA files are
then
> > >> dropped. (prior to this on the target server the option in the
exchange
> > >> server manager is selected to allow "This database can be overwritten
by
> > >> a
> > >> restore".
> > >> This method is referred to as the "forklift method".
> > >>
> > >> My question:
> > >>
> > >> After doing this, I cannot mount the store, error id: 9518 which
> > >> according
> > >> to the KB article explains is a permissions error and resolution is
to
> > >> restore default permissions on that directory (which of course is
done
> > >> alreadY)
> > >>
> > >> Has anyone run into this issue when restoring an offline exchange
> > >> database?
> > >> I have checked permissions, numerous Knowledge Base articles, the
> > >> troubleshooting guide for info on the forklift method and used the
> > >> LegacyDN
> > >> to check for consistencey, which pans out.
> > >>
> > >> Thanks for reading
> > >> Armand Salmon
> > >>
> > >> armandsalmon @ yahoo dot com
> > >>
> > >>
> > >>
> > >
> > >
> >
> >
> >
.
- Follow-Ups:
- Re: Swing Migration ROCKS!
- From: Jeff Middleton [SBS-MVP]
- Re: Swing Migration ROCKS!
- References:
- Swing Migration ROCKS!
- From: David Elders
- RE: Swing Migration ROCKS!
- From: Armand Salmon
- Re: Swing Migration ROCKS!
- From: Matt Gibson
- Re: Swing Migration ROCKS!
- From: Frank McCallister SBS MVP
- Re: Swing Migration ROCKS!
- From: Armand Salmon
- Swing Migration ROCKS!
- Prev by Date: Re: 1 NIC v. 2 NICS & remote access questions from beginner
- Next by Date: Re: Remote Web Workplace not working after installing ISA server 2
- Previous by thread: Re: Swing Migration ROCKS!
- Next by thread: Re: Swing Migration ROCKS!
- Index(es):
Relevant Pages
|
Loading