Hub Site DC in USN ROllback!

Hello Experts!

I have a question. I have a Hub and Spoke topology with say 20 spokes. Each site has only one DC (including Hub site).
Now my Hub site DC goes in USN rollback state and I have no system state backup with me...
Please let me know what should I do to make my environment work.
I have no connectivity between spoke sites.

Regards,

Arun.
LVL 7
ARK-DSAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Mike KlineCommented:
With a USN rollback you will need to do a /forceremoval and metadata cleanup.    The DS team has a great blog about USN rollbacks here:

http://blogs.technet.com/askds/archive/2009/06/05/dc-s-and-vm-s-avoiding-the-do-over.aspx

start with the section

"...To correct this situation we need to do the following on the DC that has the roll back issue..."

You will have that box back up as a DC after you go through the steps.

Thanks

Mike
0
pubeheedCommented:
Hi Arun,

Mike is spot on, bascially what you will need to do is complete a removal or AD from the server and them perfom a clean up of that DC to remove all entries of it from AD. Once it is fully removed repl will start working again (although you might need to play about with your repl topology if this is the main hub and everything is spoked from it)

Once it has been fully removed and repl is happy you can safely add it back in again using the standard dcpromo method.

I would suggest reading through the article above a few times and then stepping through it.

The one thing that would be good to understand is how this happend - is this DC a VM and it was rolled back to a previous state? If so it would be a good time to point out that will always cause this to happen VM rollbacks and DC do not go well together.

Good luck

GM
0
ARK-DSAuthor Commented:
Thanks Mike,

Thats what I thought. But then If the DC replicates with the DC in site A, ofcourse Site A will start replicating to the Hub site. But, what about the other 19 spoke sites? How would they start replicating with the HUB site?

Regards,

Arun.
0
The Ultimate Tool Kit for Technolgy Solution Provi

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more!

Mike KlineCommented:
All the spokes have site links to the hub, so when the new hub DC comes back up it will still be the hub and spoke so they will replicate based on the schedule defined in your site links.

One other thing, in this sort of design I'd have several DCs in the hub site.

Thanks

Mike
0
ARK-DSAuthor Commented:
OK,

Please see the file attached. Its a smaller model of the domain I am talking about (with four spokes).

Wont I have to clean Meta Data of DC-H  from all sites? I dont think I would be able to promote the DC without cleaning meta data...

And once I do this from all sites, all sites will know that there is no DC in the HUB site. Right? So no connection objects on sites...

I understand that we should have multiple DCs in a site and especially HUB site. But this is what the situation is...

Regards,

Arun.
USN-ROLLBACK-IN-HUB-SITE.JPG
0
pubeheedCommented:
Hi Arun,

Yes you are correct replication is not going to happen if you have a pure hub and spoke replication.

Two things I would suggest you do.

1) until this is fixed move one of the Domain controllers within sites and services to the hub site and make sure that replication is happening once it is run the metadata cleanup on that box for your failed DC

2) Build a temp DC in your HUB site and let it replicate with other servers then do a metadata cleanup - might be a good idea to down the corrupt DC until replication is happy with new DC

GM.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ARK-DSAuthor Commented:
Thats what I was looking for... I think this is the perfect solution for this situation...

If we would have gone ahead without putting a DC in the HUB site, we would have been in trouble and then we would have had to take dumps of the configuration partition of HUB site and put that in rest 19 sites... to tell those sites that there is a DC in the HUB site and then KCC would have been able to create connections...

Thanks Pubheed and Mike.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Active Directory

From novice to tech pro — start learning today.