• This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.

Migrating a Server

#1
Hi all,

We need to migrate a server to another box. The current server is a 6U
ML570 windows 2003 ent edition. We want to migrate it to a 2U DL380 windows
2003 std edition. We have 2 licenses of Double Take but they are both
standard editions so we cannot use the license on the windows 2003 ent
edition. We cannot afford to upgrade the license.

What are other solutions to migrate the server? Does a simple restore of
the ML570 to the DL380 work?

Thanks.
 

My Computer

#2
BTW, this is a stand alone server running SQL 2005.


"ME" <ME@newsgroup> wrote in message
news:e9YLvxlVKHA.4780@newsgroup

> Hi all,
>
> We need to migrate a server to another box. The current server is a 6U
> ML570 windows 2003 ent edition. We want to migrate it to a 2U DL380
> windows 2003 std edition. We have 2 licenses of Double Take but they are
> both standard editions so we cannot use the license on the windows 2003
> ent edition. We cannot afford to upgrade the license.
>
> What are other solutions to migrate the server? Does a simple restore of
> the ML570 to the DL380 work?
>
> Thanks.
>
 

My Computer

A

Ace Fekay [MCT]

#3
"ME" <ME@newsgroup> wrote in message
news:e9YLvxlVKHA.4780@newsgroup

> Hi all,
>
> We need to migrate a server to another box. The current server is a 6U
> ML570 windows 2003 ent edition. We want to migrate it to a 2U DL380
> windows 2003 std edition. We have 2 licenses of Double Take but they are
> both standard editions so we cannot use the license on the windows 2003
> ent edition. We cannot afford to upgrade the license.
>
> What are other solutions to migrate the server? Does a simple restore of
> the ML570 to the DL380 work?
>
> Thanks.
>

Is this a DC or a member server?

If it's just a member server (such as a file/print or app server), is there
any reason not to simply install 2003 Std on the new box, and move the data
over to it?

If a DC, you would be better off installing it fresh, promoting it to a DC
into the domain, then demote the old one. Keep in mind, DCs do not support
imaging restore methods. If you try it, they will wind up getting into a USN
Rollback error, which is complicated to repair.

Is Exchange involved?

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.

Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA
2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer

For urgent issues, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.
 

My Computer

#4
Oops, this is a member server in a 2003 AD.

This box is SQL 2005 running SQL reporting service along with an intranet
site, no Exchange invloved. We don't want a fresh install of 2003 Std and
move the data over because the intranet site needs to be rebuilt while our
new dev guys are still caching up with the environment so we cannot rely on
them for the IIS part.

I read this post
http://serverfault.com/questions/22118/how-to-best-migrate-a-server-to-new-hardware.
What do you think? Thx.


a.. do a system state backup using the built in software, to disk
a.. backup the whole server to tape
a.. do a clean install of windows on the new hardware giving the server the
same name
a.. install backup software (probably to a different location than normal so
restore doesn't overwrite it)
a.. restore the server, don't reboot
a.. restore the system state backup from the disk copy
a.. put in windows cd/dvd and reboot. when it comes up, boot from cd
a.. (hit F6 to add raid drivers if required)
a.. go into Repair mode and do a Repair install. This blows away hardware
settings and reinstalls drivers for the hardware



"Ace Fekay [MCT]" <aceman@newsgroup> wrote in message
news:eDo6d1lVKHA.3420@newsgroup

> "ME" <ME@newsgroup> wrote in message
> news:e9YLvxlVKHA.4780@newsgroup

>> Hi all,
>>
>> We need to migrate a server to another box. The current server is a 6U
>> ML570 windows 2003 ent edition. We want to migrate it to a 2U DL380
>> windows 2003 std edition. We have 2 licenses of Double Take but they are
>> both standard editions so we cannot use the license on the windows 2003
>> ent edition. We cannot afford to upgrade the license.
>>
>> What are other solutions to migrate the server? Does a simple restore of
>> the ML570 to the DL380 work?
>>
>> Thanks.
>>
>
>
> Is this a DC or a member server?
>
> If it's just a member server (such as a file/print or app server), is
> there any reason not to simply install 2003 Std on the new box, and move
> the data over to it?
>
> If a DC, you would be better off installing it fresh, promoting it to a DC
> into the domain, then demote the old one. Keep in mind, DCs do not support
> imaging restore methods. If you try it, they will wind up getting into a
> USN Rollback error, which is complicated to repair.
>
> Is Exchange involved?
>
> --
> Ace
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> Please reply back to the newsgroup or forum for collaboration benefit
> among responding engineers, and to help others benefit from your
> resolution.
>
> Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA
> 2003/2000, MCSA Messaging 2003
> Microsoft Certified Trainer
>
> For urgent issues, please contact Microsoft PSS directly. Please check
> http://support.microsoft.com for regional support phone numbers.
>
>
 

My Computer

A

Ace Fekay [MCT]

#5
Inline...

"ME" <ME@newsgroup> wrote in message
news:ejs333mVKHA.1232@newsgroup

> Oops, this is a member server in a 2003 AD.
>
> This box is SQL 2005 running SQL reporting service along with an intranet
> site, no Exchange invloved. We don't want a fresh install of 2003 Std and
> move the data over because the intranet site needs to be rebuilt while our
> new dev guys are still caching up with the environment so we cannot rely
> on them for the IIS part.
>
> I read this post
> http://serverfault.com/questions/22118/how-to-best-migrate-a-server-to-new-hardware.
> What do you think? Thx.
>
>
> a.. do a system state backup using the built in software, to disk
> a.. backup the whole server to tape
> a.. do a clean install of windows on the new hardware giving the server
> the same name
It has to be the same version - 2003 Ent. Ent to Std in this method will NOT
work.

> a.. install backup software (probably to a different location than normal
> so restore doesn't overwrite it)
> a.. restore the server, don't reboot
> a.. restore the system state backup from the disk copy
> a.. put in windows cd/dvd and reboot. when it comes up, boot from cd
> a.. (hit F6 to add raid drivers if required)
> a.. go into Repair mode and do a Repair install. This blows away hardware
> settings and reinstalls drivers for the hardware
With a repair/update you still need to supply drivers using F6.

If you want this server to be 2003 Std, you have to install it from scratch,
then export/import SQL data. There is no "upgrade" method based on the link
you read. Those steps are fine if using the same exact version of the OS.

Ace
 

My Computer

#6
Thanks.

I forgot to say that I will install windows server Ent edition on the DL380
server then use the ML570 server to run VMware.



"Ace Fekay [MCT]" <aceman@newsgroup> wrote in message
news:eo%23EvqnVKHA.3696@newsgroup

> Inline...
>
> "ME" <ME@newsgroup> wrote in message
> news:ejs333mVKHA.1232@newsgroup

>> Oops, this is a member server in a 2003 AD.
>>
>> This box is SQL 2005 running SQL reporting service along with an intranet
>> site, no Exchange invloved. We don't want a fresh install of 2003 Std
>> and move the data over because the intranet site needs to be rebuilt
>> while our new dev guys are still caching up with the environment so we
>> cannot rely on them for the IIS part.
>>
>> I read this post
>> http://serverfault.com/questions/22118/how-to-best-migrate-a-server-to-new-hardware.
>> What do you think? Thx.
>>
>>
>> a.. do a system state backup using the built in software, to disk
>> a.. backup the whole server to tape
>> a.. do a clean install of windows on the new hardware giving the server
>> the same name
>
> It has to be the same version - 2003 Ent. Ent to Std in this method will
> NOT work.
>

>> a.. install backup software (probably to a different location than normal
>> so restore doesn't overwrite it)
>> a.. restore the server, don't reboot
>> a.. restore the system state backup from the disk copy
>> a.. put in windows cd/dvd and reboot. when it comes up, boot from cd
>> a.. (hit F6 to add raid drivers if required)
>> a.. go into Repair mode and do a Repair install. This blows away hardware
>> settings and reinstalls drivers for the hardware
>
> With a repair/update you still need to supply drivers using F6.
>
> If you want this server to be 2003 Std, you have to install it from
> scratch, then export/import SQL data. There is no "upgrade" method based
> on the link you read. Those steps are fine if using the same exact version
> of the OS.
>
> Ace
>
>
>
>
>
 

My Computer

A

Ace Fekay [MCT]

#7
"ME" <ME@newsgroup> wrote in message
news:eRlvlNoVKHA.4484@newsgroup

> Thanks.
>
> I forgot to say that I will install windows server Ent edition on the
> DL380 server then use the ML570 server to run VMware.
>

Other than the VMWare part, you did mention you are going from Std to Ent in
your first post. That's the part I was addressing answering your questions.

I hope I was able to point out what's involved in the current plan and may
not work exactly as desired.

Ace
 

My Computer

#8
my apology for not being clear in the post.

I hope it will work when I try it this weekend.


"Ace Fekay [MCT]" <aceman@newsgroup> wrote in message
news:u$5B72rVKHA.3720@newsgroup

> "ME" <ME@newsgroup> wrote in message
> news:eRlvlNoVKHA.4484@newsgroup

>> Thanks.
>>
>> I forgot to say that I will install windows server Ent edition on the
>> DL380 server then use the ML570 server to run VMware.
>>
>
>
> Other than the VMWare part, you did mention you are going from Std to Ent
> in your first post. That's the part I was addressing answering your
> questions.
>
> I hope I was able to point out what's involved in the current plan and may
> not work exactly as desired.
>
> Ace
>
 

My Computer

A

Ace Fekay [MCT]

#9
"ME" <ME@newsgroup> wrote in message
news:uC7Fmf0VKHA.5208@newsgroup

> my apology for not being clear in the post.
>
> I hope it will work when I try it this weekend.
>
Good luck! Let us know how you make out.

Ace
 

My Computer

#10
I backed up the ML570 server (source server) using ntbackup and restored it
to the DL380 server (destination server). Before I ran the backup I stopped
all unnecessary services: sql and all sql related services; IIS Admin; DTC;
HP management services; I did the same thing on the DL380 server before I
restored.

First at all I disconnected the dest. server from the network, renamed the
dest. server with the name of the source server then started the restore.
By default the restore option is "Do not replace files on disk ...", I
changed it to "Always replace ...". When the restore completed I booted the
server with a windows server CD and did a repair. After another reboot the
server found new hw, installed drivers itself and asked me to reboot again.
The server functions fine except some minor errors in event log because it
is not connected to the domain such as SNMP, SMTP, etc. However IIS, SQL
are working fine.

So far it is a successful restore but the last thing is to shut down the
source server and connect the dest server to the network. I am not sure how
the new server is recognized by the domain controllers. If the trust
somehow broken I am not sure if it will be corrected by using netdom reset
per http://support.microsoft.com/kb/249694

netdom reset Destination computer /domain:domain_name usero:admin_user
/passwordo:admin_user_password

That is the last thing I worry about.

Thanks,


"Ace Fekay [MCT]" <aceman@newsgroup> wrote in message
news:OWlFoE5VKHA.4004@newsgroup

> "ME" <ME@newsgroup> wrote in message
> news:uC7Fmf0VKHA.5208@newsgroup

>> my apology for not being clear in the post.
>>
>> I hope it will work when I try it this weekend.
>>
>
> Good luck! Let us know how you make out.
>
> Ace
>
 

My Computer

A

Ace Fekay [MCT]

#11
"ME" <ME@newsgroup> wrote in message
news:eRXXjbXXKHA.1280@newsgroup

>I backed up the ML570 server (source server) using ntbackup and restored it
>to the DL380 server (destination server). Before I ran the backup I
>stopped all unnecessary services: sql and all sql related services; IIS
>Admin; DTC; HP management services; I did the same thing on the DL380
>server before I restored.
>
> First at all I disconnected the dest. server from the network, renamed the
> dest. server with the name of the source server then started the restore.
> By default the restore option is "Do not replace files on disk ...", I
> changed it to "Always replace ...". When the restore completed I booted
> the server with a windows server CD and did a repair. After another
> reboot the server found new hw, installed drivers itself and asked me to
> reboot again. The server functions fine except some minor errors in event
> log because it is not connected to the domain such as SNMP, SMTP, etc.
> However IIS, SQL are working fine.
>
> So far it is a successful restore but the last thing is to shut down the
> source server and connect the dest server to the network. I am not sure
> how the new server is recognized by the domain controllers. If the trust
> somehow broken I am not sure if it will be corrected by using netdom reset
> per http://support.microsoft.com/kb/249694
>
> netdom reset Destination computer /domain:domain_name usero:admin_user
> /passwordo:admin_user_password
>
> That is the last thing I worry about.
>
> Thanks,
>
Interesting. So you didn't restore based on a System State restore, rather
just a flat file restore?

If it was a flat file restore, I can see why the domain trust may be bonked.

Ace
 

My Computer

#12
Yes, I did restore system state along with the files.

I have not retired the old server and the new server is not online yes. Next week I will:
a.. do a backup of system state and SQL databases (assuming IIS and SQl reports are not updated during the code freeze priod) then turn off the old server
b.. restore the SQL databases and system state on new server then turn off, plug the server into the network then turn on.
Does it sound right?

Thanks.


"Ace Fekay [MCT]" <aceman@newsgroup> wrote in message news:Ofi4A$aXKHA.3676@newsgroup

> "ME" <ME@newsgroup> wrote in message
> news:eRXXjbXXKHA.1280@newsgroup

>>I backed up the ML570 server (source server) using ntbackup and restored it
>>to the DL380 server (destination server). Before I ran the backup I
>>stopped all unnecessary services: sql and all sql related services; IIS
>>Admin; DTC; HP management services; I did the same thing on the DL380
>>server before I restored.
>>
>> First at all I disconnected the dest. server from the network, renamed the
>> dest. server with the name of the source server then started the restore.
>> By default the restore option is "Do not replace files on disk ...", I
>> changed it to "Always replace ...". When the restore completed I booted
>> the server with a windows server CD and did a repair. After another
>> reboot the server found new hw, installed drivers itself and asked me to
>> reboot again. The server functions fine except some minor errors in event
>> log because it is not connected to the domain such as SNMP, SMTP, etc.
>> However IIS, SQL are working fine.
>>
>> So far it is a successful restore but the last thing is to shut down the
>> source server and connect the dest server to the network. I am not sure
>> how the new server is recognized by the domain controllers. If the trust
>> somehow broken I am not sure if it will be corrected by using netdom reset
>> per http://support.microsoft.com/kb/249694
>>
>> netdom reset Destination computer /domain:domain_name usero:admin_user
>> /passwordo:admin_user_password
>>
>> That is the last thing I worry about.
>>
>> Thanks,
>>
>
> Interesting. So you didn't restore based on a System State restore, rather
> just a flat file restore?
>
> If it was a flat file restore, I can see why the domain trust may be bonked.
>
> Ace
>
>
>
 

My Computer

A

Ace Fekay [MCT]

#13
> Yes, I did restore system state along with the files.

>
> I have not retired the old server and the new server is not online yes. Next
> week I will: a.. do a backup of system state and SQL databases (assuming
> IIS and SQl reports are not updated during the code freeze priod) then turn
> off the old server b.. restore the SQL databases and system state on new
> server then turn off, plug the server into the network then turn on. Does it
> sound right?
>
> Thanks.
>
Oh, ok. Then a little suprised that you are getting a secure channel
issue. I haven't really tried a netdom to reset the trust channel on a
DC. Is there any way possibly you can demote it and then re-promote it?

I've done that successfully on a couple of customer machines with
Exchange on it. Of course Exchange yelled at me, but as soon as I
re-promoted it (not changing the name, of course), everything was
smooth sailing.

Ace
 

My Computer

#14
No, I have not plugged it into the network so I was just thinking of worst
case scenario and got prepared for it.

This is a member server, not a domain controller. What do you mean by
"demote"?

Thanks.


"Ace Fekay [MCT]" <aceman@newsgroup> wrote in message
news:mn.30af7d9b7ead8e73.105663@newsgroup

>> Yes, I did restore system state along with the files.
>> I have not retired the old server and the new server is not online yes.
>> Next week I will: a.. do a backup of system state and SQL databases
>> (assuming IIS and SQl reports are not updated during the code freeze
>> priod) then turn off the old server b.. restore the SQL databases and
>> system state on new server then turn off, plug the server into the
>> network then turn on. Does it sound right?
>>
>> Thanks.
>>
>
> Oh, ok. Then a little suprised that you are getting a secure channel
> issue. I haven't really tried a netdom to reset the trust channel on a DC.
> Is there any way possibly you can demote it and then re-promote it?
>
> I've done that successfully on a couple of customer machines with Exchange
> on it. Of course Exchange yelled at me, but as soon as I re-promoted it
> (not changing the name, of course), everything was smooth sailing.
>
> Ace
>
>
 

My Computer

A

Ace Fekay [MCT]

#15
"ME" <ME@newsgroup> wrote in message
news:O5wnLpwXKHA.504@newsgroup

> No, I have not plugged it into the network so I was just thinking of worst
> case scenario and got prepared for it.
>
> This is a member server, not a domain controller. What do you mean by
> "demote"?
>
> Thanks.
Oh... I thought it was a DC. Sorry. Then the netdom should work. If not, you
can safely disjoin and rejoin it.

Ace
 

My Computer

#16
Thx.
Tomorrow we will plug the new server into the network. Will update you
here.

"Ace Fekay [MCT]" <aceman@newsgroup> wrote in message
news:%23gJNNN1XKHA.872@newsgroup

> "ME" <ME@newsgroup> wrote in message
> news:O5wnLpwXKHA.504@newsgroup

>> No, I have not plugged it into the network so I was just thinking of
>> worst case scenario and got prepared for it.
>>
>> This is a member server, not a domain controller. What do you mean by
>> "demote"?
>>
>> Thanks.
>
> Oh... I thought it was a DC. Sorry. Then the netdom should work. If not,
> you can safely disjoin and rejoin it.
>
> Ace
>
>
>
 

My Computer

#18
The migration went well as we planned, mission accomplished.

Thanks for helping me out.

Reagrds,



"Ace Fekay [MCT]" <aceman@newsgroup> wrote in message
news:e3L5o0mYKHA.5620@newsgroup

> "ME" <ME@newsgroup> wrote in message
> news:OJx5wDXYKHA.4688@newsgroup

>> Thx.
>> Tomorrow we will plug the new server into the network. Will update you
>> here.
>>
>
> Sounds good!
>
>
>
 

My Computer

A

Ace Fekay [MCT]

#19
"ME" <ME@newsgroup> wrote in message
news:O$mNWPvYKHA.4312@newsgroup

> The migration went well as we planned, mission accomplished.
>
> Thanks for helping me out.
>
> Reagrds,
You are welcome! I'm glad things worked out successfully. And thank you for
posting back your results.

Ace
 

My Computer

Users Who Are Viewing This Thread (Users: 1, Guests: 0)