Backup Central

Have you thought about ghosting the system?


Jim Proctor
Virtual Team Lead
USGS/NGTOC III
Rolla, Missouri
jproctor < at > usgs.gov
(573)308-3521





From: Michael Leone <Michael.Leone < at > PHA.PHILA.GOV>
To: NETWORKER < at > LISTSERV.TEMPLE.EDU
Date: 11/15/2011 09:48 AM
Subject: [Networker] OT - migrating a VM to a physical machine
Sent by: EMC NetWorker discussion <NETWORKER < at > LISTSERV.TEMPLE.EDU>



I realize this is a bit (OK, maybe a bit more than a bit ..) OT. But I
will be using Networker in the process, so I thought I'd ask here.

VMware Environment: 6 host EX 4.1 U1 cluster. VM in question - Win2003
Enterprise, 32 bit

My boss tells me that I need to convert this from a VM back onto a
physical machine - for licensing reasons, this needs to be a physical box,

apparently. And there's no budget for software designed for this purpose
(of course ).

So here's the big rub ... this VM is one of those mission critical VMs.
Ordinarily, what I might have done is do a sysprep of the VM, and - before

shutting it down - do a full backup using Networker. Then, I would do a
BMR (Bare Metal Recovery) of Windows on the new physical hardware. That
way, after the reboot at the end of the BMR, sysprep would run, find the
new disk controller drivers, etc, and not blue screen with inaccessible
boot device errors.

However, my boss has vetoed that idea, since we can't take any chances
with the VM perhaps not working after the sysprep. If that BMR doesn't
work, then I would need to turn the VM back on. and we have no guarantees
that it would continue to work the same after the sysprep, etc.

So my hands are tied that way.

Then I thought - well, we could still do a BMR, but without the sysprep
first. I could install the drivers for the new disk controller, etc, into
the running VM. Do a regular full backup, shutdown the VM, and then do the

BMR to the physical box. It should recognize that the hardware has
changed, see the new hardware, see it has a driver for it, reboot
accordingly. Repeat until it's happy and boots normally. If absolutely
necessary, do a Windows Repair installation.

That way, either the physical box would work, and I'd leave the VM powered

off, or the physical box would fail, and I would power the VM back up.
Since the domain SID never changes, all should be happy.

I think that should work. Anyone ever done anything similar? The BMR
should just be: install same version of Windows onto physical hardware (no

need for updates) with same name and IP address, not as member of domain.
Install NW client (same version as what's in the VM). Do a full restore of

everything except the NW client program files folder. Reboot when
prompted. That should work as a BMR for a 32bit Win2003 box, yes?


"signoff networker" in the body of the email. Please write to
networker-request < at > listserv.temple.edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER



via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

I realize this is a bit (OK, maybe a bit more than a bit ..) OT. But I
will be using Networker in the process, so I thought I'd ask here.

VMware Environment: 6 host EX 4.1 U1 cluster. VM in question - Win2003
Enterprise, 32 bit

My boss tells me that I need to convert this from a VM back onto a
physical machine - for licensing reasons, this needs to be a physical box,
apparently. And there's no budget for software designed for this purpose
(of course ).

So here's the big rub ... this VM is one of those mission critical VMs.
Ordinarily, what I might have done is do a sysprep of the VM, and - before
shutting it down - do a full backup using Networker. Then, I would do a
BMR (Bare Metal Recovery) of Windows on the new physical hardware. That
way, after the reboot at the end of the BMR, sysprep would run, find the
new disk controller drivers, etc, and not blue screen with inaccessible
boot device errors.

However, my boss has vetoed that idea, since we can't take any chances
with the VM perhaps not working after the sysprep. If that BMR doesn't
work, then I would need to turn the VM back on. and we have no guarantees
that it would continue to work the same after the sysprep, etc.

So my hands are tied that way.

Then I thought - well, we could still do a BMR, but without the sysprep
first. I could install the drivers for the new disk controller, etc, into
the running VM. Do a regular full backup, shutdown the VM, and then do the
BMR to the physical box. It should recognize that the hardware has
changed, see the new hardware, see it has a driver for it, reboot
accordingly. Repeat until it's happy and boots normally. If absolutely
necessary, do a Windows Repair installation.

That way, either the physical box would work, and I'd leave the VM powered
off, or the physical box would fail, and I would power the VM back up.
Since the domain SID never changes, all should be happy.

I think that should work. Anyone ever done anything similar? The BMR
should just be: install same version of Windows onto physical hardware (no
need for updates) with same name and IP address, not as member of domain.
Install NW client (same version as what's in the VM). Do a full restore of
everything except the NW client program files folder. Reboot when
prompted. That should work as a BMR for a 32bit Win2003 box, yes?


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

Have you thought about ghosting the system?

I would need a Ghost server to do that, and I don't have one. And even
finding a work around way to do it - storing the ghost image somewhere a
ghost boot could get at it - wouldn't solve the problem of the hardware
changing. Hopefully, pre-installing the drivers into the running VM before
the full backup (or Ghosting, if I could go that route) would help resolve
that, as I don't want to/ can't? do that.

Effectively speaking this is (I think) a Disaster Recovery Bare Metal
Recovery to dissimilar hardware ...




Jim Proctor
Virtual Team Lead
USGS/NGTOC III
Rolla, Missouri
jproctor < at > usgs.gov
(573)308-3521





From: Michael Leone <Michael.Leone < at > PHA.PHILA.GOV>
To: NETWORKER < at > LISTSERV.TEMPLE.EDU
Date: 11/15/2011 09:48 AM
Subject: [Networker] OT - migrating a VM to a physical machine
Sent by: EMC NetWorker discussion <NETWORKER < at > LISTSERV.TEMPLE.EDU>




I realize this is a bit (OK, maybe a bit more than a bit ..) OT. But I
will be using Networker in the process, so I thought I'd ask here.

VMware Environment: 6 host EX 4.1 U1 cluster. VM in question - Win2003
Enterprise, 32 bit

My boss tells me that I need to convert this from a VM back onto a
physical machine - for licensing reasons, this needs to be a physical
box,
apparently. And there's no budget for software designed for this purpose

(of course ).

So here's the big rub ... this VM is one of those mission critical VMs.
Ordinarily, what I might have done is do a sysprep of the VM, and -
before
shutting it down - do a full backup using Networker. Then, I would do a
BMR (Bare Metal Recovery) of Windows on the new physical hardware. That
way, after the reboot at the end of the BMR, sysprep would run, find the

new disk controller drivers, etc, and not blue screen with inaccessible
boot device errors.

However, my boss has vetoed that idea, since we can't take any chances
with the VM perhaps not working after the sysprep. If that BMR doesn't
work, then I would need to turn the VM back on. and we have no
guarantees
that it would continue to work the same after the sysprep, etc.

So my hands are tied that way.

Then I thought - well, we could still do a BMR, but without the sysprep
first. I could install the drivers for the new disk controller, etc,
into
the running VM. Do a regular full backup, shutdown the VM, and then do
the
BMR to the physical box. It should recognize that the hardware has
changed, see the new hardware, see it has a driver for it, reboot
accordingly. Repeat until it's happy and boots normally. If absolutely
necessary, do a Windows Repair installation.

That way, either the physical box would work, and I'd leave the VM
powered
off, or the physical box would fail, and I would power the VM back up.
Since the domain SID never changes, all should be happy.

I think that should work. Anyone ever done anything similar? The BMR
should just be: install same version of Windows onto physical hardware
(no
need for updates) with same name and IP address, not as member of
domain.
Install NW client (same version as what's in the VM). Do a full restore
of
everything except the NW client program files folder. Reboot when
prompted. That should work as a BMR for a 32bit Win2003 box, yes?


and type "signoff networker" in the body of the email. Please write
to networker-request < at > listserv.temple.edu if you have any problems
with this list. You can access the archives at http://
listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

Another option would be to look at http://clonezilla.org/ The price is
right and might do what you want.


Jim Proctor
Virtual Team Lead
USGS/NGTOC III
Rolla, Missouri
jproctor < at > usgs.gov
(573)308-3521





From: Michael Leone <Michael.Leone < at > PHA.PHILA.GOV>
To: NETWORKER < at > LISTSERV.TEMPLE.EDU
Date: 11/15/2011 10:21 AM
Subject: Re: [Networker] OT - migrating a VM to a physical machine
Sent by: EMC NetWorker discussion <NETWORKER < at > LISTSERV.TEMPLE.EDU>



Have you thought about ghosting the system?

I would need a Ghost server to do that, and I don't have one. And even
finding a work around way to do it - storing the ghost image somewhere a
ghost boot could get at it - wouldn't solve the problem of the hardware
changing. Hopefully, pre-installing the drivers into the running VM before

the full backup (or Ghosting, if I could go that route) would help resolve

that, as I don't want to/ can't? do that.

Effectively speaking this is (I think) a Disaster Recovery Bare Metal
Recovery to dissimilar hardware ...




Jim Proctor
Virtual Team Lead
USGS/NGTOC III
Rolla, Missouri
jproctor < at > usgs.gov
(573)308-3521





From: Michael Leone <Michael.Leone < at > PHA.PHILA.GOV>
To: NETWORKER < at > LISTSERV.TEMPLE.EDU
Date: 11/15/2011 09:48 AM
Subject: [Networker] OT - migrating a VM to a physical machine
Sent by: EMC NetWorker discussion <NETWORKER < at > LISTSERV.TEMPLE.EDU>





I realize this is a bit (OK, maybe a bit more than a bit ..) OT. But I
will be using Networker in the process, so I thought I'd ask here.

VMware Environment: 6 host EX 4.1 U1 cluster. VM in question - Win2003
Enterprise, 32 bit

My boss tells me that I need to convert this from a VM back onto a
physical machine - for licensing reasons, this needs to be a physical
box,
apparently. And there's no budget for software designed for this purpose


(of course ).

So here's the big rub ... this VM is one of those mission critical VMs.
Ordinarily, what I might have done is do a sysprep of the VM, and -
before
shutting it down - do a full backup using Networker. Then, I would do a
BMR (Bare Metal Recovery) of Windows on the new physical hardware. That
way, after the reboot at the end of the BMR, sysprep would run, find the


new disk controller drivers, etc, and not blue screen with inaccessible
boot device errors.

However, my boss has vetoed that idea, since we can't take any chances
with the VM perhaps not working after the sysprep. If that BMR doesn't
work, then I would need to turn the VM back on. and we have no
guarantees
that it would continue to work the same after the sysprep, etc.

So my hands are tied that way.

Then I thought - well, we could still do a BMR, but without the sysprep
first. I could install the drivers for the new disk controller, etc,
into
the running VM. Do a regular full backup, shutdown the VM, and then do
the
BMR to the physical box. It should recognize that the hardware has
changed, see the new hardware, see it has a driver for it, reboot
accordingly. Repeat until it's happy and boots normally. If absolutely
necessary, do a Windows Repair installation.

That way, either the physical box would work, and I'd leave the VM
powered
off, or the physical box would fail, and I would power the VM back up.
Since the domain SID never changes, all should be happy.

I think that should work. Anyone ever done anything similar? The BMR
should just be: install same version of Windows onto physical hardware
(no
need for updates) with same name and IP address, not as member of
domain.
Install NW client (same version as what's in the VM). Do a full restore
of
everything except the NW client program files folder. Reboot when
prompted. That should work as a BMR for a 32bit Win2003 box, yes?


and type "signoff networker" in the body of the email. Please write
to networker-request < at > listserv.temple.edu if you have any problems
with this list. You can access the archives at http://
listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER


"signoff networker" in the body of the email. Please write to
networker-request < at > listserv.temple.edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER



via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

Hey Michael,

I'm just wondering what the licensing reason for moving back to a physical, is it because the vendor wants to license all of the sockets in the ESX cluster rather than the virtual CPU's that are assigned to the guest?

If that's the case, I'm just wondering if it might be easier to run the boxes as standalone ESX servers, it kinda sucks from a virtualization point of view, but might get you round your issue with as little pain as possible.

If that's not the case, you could get the machine(s) cloned as an initial step, and then run the sysprep over the clone - at least then you fall back would be just to power up the original VM.


Mat
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER < at > LISTSERV.TEMPLE.EDU] On Behalf Of Michael Leone
Sent: Wednesday, 16 November 2011 1:47 AM
To: NETWORKER < at > LISTSERV.TEMPLE.EDU
Subject: [Networker] OT - migrating a VM to a physical machine

I realize this is a bit (OK, maybe a bit more than a bit ..) OT. But I will be using Networker in the process, so I thought I'd ask here.

VMware Environment: 6 host EX 4.1 U1 cluster. VM in question - Win2003 Enterprise, 32 bit

My boss tells me that I need to convert this from a VM back onto a physical machine - for licensing reasons, this needs to be a physical box, apparently. And there's no budget for software designed for this purpose (of course ).

So here's the big rub ... this VM is one of those mission critical VMs.
Ordinarily, what I might have done is do a sysprep of the VM, and - before shutting it down - do a full backup using Networker. Then, I would do a BMR (Bare Metal Recovery) of Windows on the new physical hardware. That way, after the reboot at the end of the BMR, sysprep would run, find the new disk controller drivers, etc, and not blue screen with inaccessible boot device errors.

However, my boss has vetoed that idea, since we can't take any chances with the VM perhaps not working after the sysprep. If that BMR doesn't work, then I would need to turn the VM back on. and we have no guarantees that it would continue to work the same after the sysprep, etc.

So my hands are tied that way.

Then I thought - well, we could still do a BMR, but without the sysprep first. I could install the drivers for the new disk controller, etc, into the running VM. Do a regular full backup, shutdown the VM, and then do the BMR to the physical box. It should recognize that the hardware has changed, see the new hardware, see it has a driver for it, reboot accordingly. Repeat until it's happy and boots normally. If absolutely necessary, do a Windows Repair installation.

That way, either the physical box would work, and I'd leave the VM powered off, or the physical box would fail, and I would power the VM back up.
Since the domain SID never changes, all should be happy.

I think that should work. Anyone ever done anything similar? The BMR should just be: install same version of Windows onto physical hardware (no need for updates) with same name and IP address, not as member of domain.
Install NW client (same version as what's in the VM). Do a full restore of everything except the NW client program files folder. Reboot when prompted. That should work as a BMR for a 32bit Win2003 box, yes?



We're behind the Bid!
GOLD COAST 2018 - XXI COMMONWEALTH GAMES CANDIDATE CITY
www.goldcoast2018bid.com

*********************************DISCLAIMER*********************************


The information contained in the above e-mail message or messages
(which includes any attachments) is confidential and may be legally
privileged. It is intended only for the use of the person or entity
to which it is addressed. If you are not the addressee any form of
disclosure, copying, modification, distribution or any action taken
or omitted in reliance on the information is unauthorised. Opinions
contained in the message(s) do not necessarily reflect the opinions
of the Queensland Government and its authorities. If you received
this communication in error, please notify the sender immediately
and delete it from your computer system network.


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

On Tue, Nov 15, 2011 at 9:46 AM, Michael Leone
<Michael.Leone < at > pha.phila.gov> wrote:

I think that should work. Anyone ever done anything similar? The BMR
should just be: install same version of Windows onto physical hardware (no
need for updates) with same name and IP address, not as member of domain.
Install NW client (same version as what's in the VM). Do a full restore of
everything except the NW client program files folder. Reboot when
prompted. That should work as a BMR for a 32bit Win2003 box, yes?


Michael,
Reading the NW Admin guide as well as some of the Microsoft
documentation, my understanding is the only supported BMR option for
Windows without using 3rd party tools is ASR:
http://technet.microsoft.com/en-us/library/cc758365(WS.10).aspx

Curious which way you have decided.

Cheers,
Eugene


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

Eugene Vilensky wrote:
On Tue, Nov 15, 2011 at 9:46 AM, Michael Leone
<Michael.Leone < at > pha.phila.gov> wrote:


I think that should work. Anyone ever done anything similar? The BMR
should just be: install same version of Windows onto physical hardware (no
need for updates) with same name and IP address, not as member of domain.
Install NW client (same version as what's in the VM). Do a full restore of
everything except the NW client program files folder. Reboot when
prompted. That should work as a BMR for a 32bit Win2003 box, yes?



Michael,
Reading the NW Admin guide as well as some of the Microsoft
documentation, my understanding is the only supported BMR option for
Windows without using 3rd party tools is ASR:
http://technet.microsoft.com/en-us/library/cc758365(WS.10).aspx

Yes this is true for Windows below 2008R2 and 7.6.2. 7.6.2 offer for Win
2008R2 true BMR options. Read more ID:esg121662.
This is "free" for Win 2008R2 and 7. Disaster recovery you need
NetWorkerWindowsDisasterRecovery_7.6.2-638_x86.iso

You can also bought this BMR functions for earlier versions of Windows
and other OS. http://www.emchomebase.com/pg/product/productset.html or
use ASR save set for earlier versions than 2008R2 of Windows.

Regards, Riku
Curious which way you have decided.

Cheers,
Eugene


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER



via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

I'm just wondering what the licensing reason for moving back to a
physical, is it because the vendor wants to license all of the
sockets in the ESX cluster rather than the virtual CPU's that are
assigned to the guest?

Pretty much.

If that's the case, I'm just wondering if it might be easier to run
the boxes as standalone ESX servers, it kinda sucks from a
virtualization point of view, but might get you round your issue
with as little pain as possible.

Hmmm ... I will mention it. But I think my boss has his heart set on a
stand-alone physical machine, not running as a VM ... there may be
licensing details that I am not aware (i.e., different pricing for
virtualization vs physical, regardless of pricing for number of CPUs, etc)

If that's not the case, you could get the machine(s) cloned as an
initial step, and then run the sysprep over the clone - at least
then you fall back would be just to power up the original VM.

But I couldn't fall back. The sysprep would change the SID, so the VM
would not be able to authenticate to the domain again. I would need to
sysprep the clone, and then re-join the domain. That would stop me from
using the VM again.



Mat
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER < at > LISTSERV.TEMPLE.EDU
] On Behalf Of Michael Leone
Sent: Wednesday, 16 November 2011 1:47 AM
To: NETWORKER < at > LISTSERV.TEMPLE.EDU
Subject: [Networker] OT - migrating a VM to a physical machine

I realize this is a bit (OK, maybe a bit more than a bit ..) OT. But
I will be using Networker in the process, so I thought I'd ask here.

VMware Environment: 6 host EX 4.1 U1 cluster. VM in question -
Win2003 Enterprise, 32 bit

My boss tells me that I need to convert this from a VM back onto a
physical machine - for licensing reasons, this needs to be a
physical box, apparently. And there's no budget for software
designed for this purpose (of course ).

So here's the big rub ... this VM is one of those mission critical VMs.
Ordinarily, what I might have done is do a sysprep of the VM, and -
before shutting it down - do a full backup using Networker. Then, I
would do a BMR (Bare Metal Recovery) of Windows on the new physical
hardware. That way, after the reboot at the end of the BMR, sysprep
would run, find the new disk controller drivers, etc, and not blue
screen with inaccessible boot device errors.

However, my boss has vetoed that idea, since we can't take any
chances with the VM perhaps not working after the sysprep. If that
BMR doesn't work, then I would need to turn the VM back on. and we
have no guarantees that it would continue to work the same after the
sysprep, etc.

So my hands are tied that way.

Then I thought - well, we could still do a BMR, but without the
sysprep first. I could install the drivers for the new disk
controller, etc, into the running VM. Do a regular full backup,
shutdown the VM, and then do the BMR to the physical box. It should
recognize that the hardware has changed, see the new hardware, see
it has a driver for it, reboot accordingly. Repeat until it's happy
and boots normally. If absolutely necessary, do a Windows Repair
installation.

That way, either the physical box would work, and I'd leave the VM
powered off, or the physical box would fail, and I would power the
VM back up.
Since the domain SID never changes, all should be happy.

I think that should work. Anyone ever done anything similar? The BMR
should just be: install same version of Windows onto physical
hardware (no need for updates) with same name and IP address, not as
member of domain.
Install NW client (same version as what's in the VM). Do a full
restore of everything except the NW client program files folder.
Reboot when prompted. That should work as a BMR for a 32bit Win2003 box,
yes?


and type "signoff networker" in the body of the email. Please write
to networker-request < at > listserv.temple.edu if you have any problems
with this list. You can access the archives at http://
listserv.temple.edu/archives/networker.html or via RSS at http://
listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

We're behind the Bid!
GOLD COAST 2018 - XXI COMMONWEALTH GAMES CANDIDATE CITY
www.goldcoast2018bid.com


*********************************DISCLAIMER*********************************


The information contained in the above e-mail message or messages
(which includes any attachments) is confidential and may be legally
privileged. It is intended only for the use of the person or entity
to which it is addressed. If you are not the addressee any form of
disclosure, copying, modification, distribution or any action taken
or omitted in reliance on the information is unauthorised. Opinions
contained in the message(s) do not necessarily reflect the opinions
of the Queensland Government and its authorities. If you received
this communication in error, please notify the sender immediately
and delete it from your computer system network.


and type "signoff networker" in the body of the email. Please write
to networker-request < at > listserv.temple.edu if you have any problems
with this list. You can access the archives at http://
listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

I think that should work. Anyone ever done anything similar? The BMR
should just be: install same version of Windows onto physical
hardware (no
need for updates) with same name and IP address, not as member of
domain.
Install NW client (same version as what's in the VM). Do a full
restore of
everything except the NW client program files folder. Reboot when
prompted. That should work as a BMR for a 32bit Win2003 box, yes?



Michael,
Reading the NW Admin guide as well as some of the Microsoft
documentation, my understanding is the only supported BMR option for
Windows without using 3rd party tools is ASR:
http://technet.microsoft.com/en-us/library/cc758365(WS.10).aspx

"Before performing an ASR restore, ensure that the target system to which
the restore will be made meets the following requirements:
The target system hardware (except for hard disks, video cards, and
network adapters) is identical to that of the original system."

Since this will not be the case (the hardware will not be identical,
obviously), not all of this will apply. This also (mostly) presupposes
the use of Windows Backup, which we obviously don't use either.


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER