• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 227
  • Last Modified:

Restoring server for dev purposes

Hi,

I'm suppose to restore a server from a backup, change its name, give it a different domain and plug it in back to live network however I think there will be an issue with it. If I change the restored computer name, eventually it'll contact the domain and change its name there hence affecting the production server, right?

I obviously don't want to test it because it might screw everything up so I'd rather ask if this is the case or how can I do it, to have dev server cloned from production on the same network?

Thanks.
0
JurajUQU
Asked:
JurajUQU
  • 5
  • 2
2 Solutions
 
Tony GiangrecoCommented:
Your best bet would be a clear install... run it from the Windows CD, delete the Windows partition ald others found, recreate the Windows partition the same size or larger and perform a full install. If you don't do a clean install, it will be more work in the long run and a few headaches on the way.

Before doing all that, I suggest downloading a the latest Bios and drivers so when you install, you will be bettter prepared.

If it's a Dell, you can go to www.dell.com/support and enter the service tag. It will bring up all the drivers and bios updates.

Hope this helps!
0
 
JurajUQUAuthor Commented:
I think you misunderstood me. I have the production server and it's working fine, I just want to restore it into virtual environment and have a clone of it for testing purposes.
0
 
Tony GiangrecoCommented:
Oh, that's much different. You will need to change the name, IP and other items before it will run properly.
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
JurajUQUAuthor Commented:
Could you be more specific what items? Would it mess up with my current setup?
0
 
Leon FesterIT Project Change ManagerCommented:
The main thing that can go wrong when cloning a physical to virtual (P2V) is the SID of the new computer.

Granted you will change the name and IP's, but the SID will be copied from the old server.
You don't mention how you'll be restoring, but if you've got virtual systems available then rather look at the native tools available to complete this task.
VMware and Hyper-V both have instructions and tools on how to do this.

Some links that may help to answer this and other questions:
http://www.vmware.com/products/converter/overview.html
http://communities.vmware.com/message/1129526
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1000528
http://searchservervirtualization.techtarget.com/tip/Top-5-tips-for-P2V-conversion-success
http://technet.microsoft.com/en-us/library/bb740912.aspx
0
 
JurajUQUAuthor Commented:
I'll be using Shadow Protect to accomplish this and yes, I'm going virtual with the dev/test system.

But even if I'll change SID, won't it affect connectivity to the domain of an existing production machine? That is my biggest fear as it would obviously create lot of problems for me and our operation.
0
 
JurajUQUAuthor Commented:
OK so I've done following:

Restored the server into virtual environment with networking
Removed from the AD
Change its name
Ran sysprep to change SID
Changed SN for Windows to get activated and not create conflict with the prod server
Delete any mentions of the AD in registry (though I think this wasn't necessary)
Deleted all the old profiles (ditto)
Made sure that all the services running there are pointing to the dev server
Joined back to the domain

And it works fine!
0
 
JurajUQUAuthor Commented:
dvt_localboy reminded me to change the SID from which I've developed a step-by-step solution that worked
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 5
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now