Merv Porter [SBS-MVP]
Guest
|
 Posted:
Tue Jan 18, 2005 8:45 am Post subject:
Re: Exchange > system mailbox problems |
|
|
I think you should take this to Jeff M. (Mr. Swing IT) directly so he can
guide you and document any anomalies that might be found.
--
Merv Porter [SBS MVP]
===================================
"Fisheye" <support@fisheye.co.nz> wrote in message
news:OkR9HWQ$EHA.4004@tk2msftngp13.phx.gbl...
| Quote: | Hi guys
We are currently migrating a client from SBS2000 onto SBS2003 with new
server hardware.
We have decided to use the SBSmigration.com swing IT kit > props to you
guys
and I recommend it.
We are on our first SWING and everything worked well until now (Phase 4-5)
We have done a forklift upgrade of exchange (just like an offline restore
only onto a new server that has a copy of the AD from the existing DC) and
it restarted and mounted fine.;)
As a precaution we then tried an online backup using Veritas Backup Exec.
I have isolated the problem to the 2 instances of the SMTP and
SystemMailbox
I have searched registry for the 2 GUID's listed and one of the GUID's is
found but the other is not.
I backed up all actual user mailboxes and this verified fine. (Actual real
human mailboxes)
Also I backed up the SMTP and SystemMailbox with the correct GUID and this
verified fine.
When backing up the other instances the job backs up 0 bytes and fails to
verify > surprise, surprise !
So I believe the SMTP and SystemMailbox with the unrecognised GUID are
references that are out of date or not required and have somehow remained
in
our directory. How do we get rid of them.
Also there are 2 System Attendant mailboxes > is this OK ?
Also will we have any problems with the new mail when it comes in ? (ie
after we install new upgraded server and start up the SMTP service)
At least with the SWING method I dont have to worry about client downtime.
They are still working fine on their old server for the mean time. ;)
tia
Fisheye
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in