IT Employment

Ask something
Discussion Locked

replaicing server

0 helpful
10 replies

by kurtasha

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
what si the best rout to take when replaicing an old windows nt server with a new one,reason for this is old server is running out of storage space i was thinking of ghosting it? please anyone need help asap.

10 replies

by kurtasha

it is the pdc of the network i also syncronized the bdc with the pdc and once i ghost the pdc to the bdc i was going to promote it to be the new pdc

by beecee

Why ghost the server? Plus, you will probably have major issues because of the hardware differences. Best thing to do is just rebuild it from scratch, place the user data back onto the drives and whalla, brand spanking new clean server with latestpatches etc. This will give you lots more control. Also, NT is funny with a lot of its 'stuff'. If you do ghost it you are also probably going to find issues with Disk Admin, registry, shares ETC. I would not do it in a million years.
Other questions you need to ask yourself is what is running on the server that could possibly make you even consider ghost.
Write down a list of items, evaluate the ways to export the data and how to put it back.

Good Luck!
Adriana

by pandadude

I am getting a W2K stand-alone home PC which I plan to install a lot of stuff...Oracle, DB2, M$ etc. And I want to start ghosting this new machine:
Need some education:
1) Is ghosting really the best practice & insurance for system recovery & stability ?
2) (Cheap) Software utility recommendation please
3) I need > 1 HDs ?

Thanks

by mckaytech

I have seen very few NT Servers that I would want to ghost to new hardware. Over time, NT Servers invariably build up detritus in the registry and elsewhere on the hard drive because of poorly designed un-install programs, driver changes, software upgrades, configuration changes, etc.

Over the years, I've become a big fan of doing a clean install and restoring only the user data. In your case, I would promote your BDC to a PDC and then rebuild your new server as a BDC on the network and then promote it afterwards.

I used that procedure this past weekend on a server and even in restoring to the same hardware ended up with a significant improvement in performance over the old box.

paul

by radiic

Computers are like poker, did you know that. I personally belive in the royal flush theory when it comes to my workstations and servers. Better to start with a brand spanking new install. At least you know that everything is fresh on the server (registry, patches, fragmentation)...I guess the only downfall is that when it crashes down the road you cant blame anything else ;)

by admin

Why don't you just install a bigger disk?

Unless you need a new PDC, it seems that this would be the most cost-effective efficient route.

If you really need a new one, I'd start from scratch rather than ghost. disk imaging onto completely different hardware in something like a PDC may get running faster (may) but will likely take more time down the road.

by ebob

...was anticipating pretty similar, if not identical H/W platforms, from A to B. But since in this case, "A" is not the platform of choice, what's the point?

Definitely, build from scratch. While you're at it, you'll not only build the HDDs differently, but you'll have a faster CPU, more RAM, all the goods.

by kurtasha

the server was successfully replaced i want to thank all of you that replayed to my posting on your helpfull ideas.And special thanks goes to .... well the person knows who i am talking about thanks again.

by kima

Why don't you get a bigger HD instead..eventually it will run out of space again and again and you'll have to keep ghosting it...

This discussion is closed to new replies.