Re: Problems after cloning SBS2003
- From: "kj" <kj@xxxxxxxxxxx>
- Date: Fri, 18 May 2007 22:18:19 -0700
nick wrote:
I have 1 domain with a SBS 2003, a windows 2003 fileserver and a
windows 2003 terminal server. All three are DCs and AD is replicated
across them all.
The SBS had a 72GB hard disk (well - 2 x 72GB in a RAID 1
configuration) and was nearing full capacity. So I added 2 x 145GB in
a RAID 1 and used Norton Ghost to dupliacte the partitions across.
BIG mistake!
On reboot I got all sorts of errors most of which I resolved. The only
problem I am left with is that replication is no longer happening on
the SBS. I have researched and discovered that windows servers don't
take well to ghosting and the like.
Domain Controllers especially. Some Servers can be safely imaged, but not
these (DC's)
There are lots of events logged indicating that replication isn't
working. My main worry is that the SBS will eventually fall into a
tombstone situation and therefore time is not on my side.
It's really worse than that. DC's are accumulating changes that won't ever
be replicated to all three.
There is an article about USN rollback. It would appear to be quite
complicated. Is this my only option?
If the restored image of the SBS was *very* current you might choose to take
the AD version that is in force now.
Demote the remaining Domain Controllers and then repromote. You may need to
do a forced demotion and you may need to do a metadata cleanup or your AD
before repromoting these other DC's.
If your not comfortable doing this, spend the money and get Microsoft PSS
help in resolving this ASAP!!!
All help appreciated.
Thanks.
--
/kj
.
- Prev by Date: Re: POP connection not working
- Next by Date: Re: Fax (re)install fails
- Previous by thread: Re: Problems after cloning SBS2003
- Next by thread: Re: Problems after cloning SBS2003
- Index(es):
Relevant Pages
|
