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

How to keep ip and domain name after moving the harddrive to another machine

I have 2 databases running on one sql server 2000, this server is old and need to be changed. I want to move the harddrive to a similiar newer server. I am wondering if the new machine has same ip and domain name after moving the harddrive to new machine. Since there are some appliations in the networking are calling two databases on this machine via ip and domain name like d1.test.abcd.com? how to approach?  is there any risk I lose applications?
0
blue_wireless
Asked:
blue_wireless
  • 3
  • 3
  • 2
  • +1
2 Solutions
 
AncientFribCommented:
if this new server has nearly identical hardware then possibly yes.  If the boot process encounters difficulties while identifying new hardware than you may run in to a number of problems.

But bottom line is if the hardware is identical then technically you can swap hard drives and the machine will be as if it was never affected.
0
 
MikealclCommented:
Just move the databases and bind the ip to the new server.  Why physically move the hard drive??


0
 
blue_wirelessAuthor Commented:
moving database only will result in different domain name, and there are may be some other unknown settings, files and applications on old server. I don't have all documents about old server. So I think physically  moving hard drive is the simplest way.
0
Prepare for your VMware VCP6-DCV exam.

Josh Coen and Jason Langer have prepared the latest edition of VCP study guide. Both authors have been working in the IT field for more than a decade, and both hold VMware certifications. This 163-page guide covers all 10 of the exam blueprint sections.

 
MikealclCommented:
Its sql.  The client machines won't know the difference if you move the data, and bind the ip.
All you will have to check is your stored procedures etc.

0
 
easyDKCommented:
Try cloning that harddrive...
0
 
blue_wirelessAuthor Commented:
If all application query via IP in connection string / hard codes, that works. but some applications running on other machine query from this machine via domain name like "server=t1.old.machine.com". so I have to keep both domain name and IP.

why do I need to check store procedure? I am confused. As long as domain name and IP are same, other appliations on other machine query the same store procedure.
0
 
blue_wirelessAuthor Commented:
is cloning, say ghost keep the harddrive same ip and domain name?
0
 
MikealclCommented:
What do you think the computer name is?  It's nothing but a DNS record, or netbios name.

Just move the database, bind the IP, and make sure the DNS record still exists.
If your really paranoid use the hosts file in c:\windows\system32\drivers\etc to make the netbios name resolve to the right ip address.

I have never had to physically move a hard drive to migrate an SQL server.  That's really overkill.
0
 
AncientFribCommented:
Blue,

To answer your question - Yes cloning with Ghost will keep the same IP etc.  Mikealcl makes some good points though, this approach can be more painstaking than anything.  As I said, if the hardware is not identical, you are likely to have issues.

Although when I have ghosted a harddrive in the past for a backup machine with identical hardware it was a breeze overall.  So when it works, it works well, when it doesn't it is a real headache.
0

Featured Post

Important Lessons on Recovering from Petya

In their most recent webinar, Skyport Systems explores ways to isolate and protect critical databases to keep the core of your company safe from harm.

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