Anonymous_User Absent Member.
Absent Member.
960 views

OES11 migration hardware to esxi

Hello
Is there a good doc on Migrating a currently running hardware OES11sp2 to an
ESXi guest? I presume using the migration tool will work. I am looking for
some guidance on pre setting up the target in the VM. I currently have a
blade center that we are upgrading and need to move this particular server
into our VM environment. I want to keep the identity. This server currently
completely boots and runs from san and also has a very large NSS volume.
Thanks.

Labels (1)
0 Likes
6 Replies
Knowledge Partner
Knowledge Partner

Re: OES11 migration hardware to esxi

If there is no local disk associated with your current server, the migration should be fairly easy.

I would begin by making a backup copy of the LUN containing the OES volume.

When you say:
This server currently completely boots and runs from san and also has a very large NSS volume.

Am I correct in assuming that the NSS volume also resides on the SAN?

Do you have an iSCSI interface to your SAN?

Here's an article that seems to describe what you want to do.
Creating/Adding a Raw Device Mapping (RDM) to a Virtual Machine

You would create a new VM and assign memory, processors, and an iSCSI adapter. Since you are booting from the same OES volume, you are going to retain the same configuration. Once OES boots up, you may have to update some drivers to access your NSS volume.

Please let us know how this works for you.
_____
Kevin Boyle - Knowledge Partner - Calgary, Alberta, Canada
Who are the Knowledge Partners?
If you appreciate my comments, please click the Like button.
If I have resolved your issue, please click the Accept as Solution button.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: OES11 migration hardware to esxi

Thanks for the reply.
There are no local disks at all. Yes the NSS volume is also on the SAN. The
SAN is connected via Fiber Channel to the blade center via the SAN
controllers (Compellent). Thanks for the info. I'll look into the article.

"KBOYLE" wrote in message news:KBOYLE.80yutz@no-mx.forums.microfocus.com...


If there is no local disk associated with your current server, the
migration should be fairly easy.

I would begin by making a backup copy of the LUN containing the OES
volume.

When you say:
> This server currently completely boots and runs from san and also has a
> very large NSS volume.

Am I correct in assuming that the NSS volume also resides on the SAN?

Do you have an iSCSI interface to your SAN?

Here's an article that seems to describe what you want to do.
'Creating/Adding a Raw Device Mapping (RDM) to a Virtual Machine'
(https://www.vmadmin.co.uk/resources/35-esxserver/58-rdmvm)

You would create a new VM and assign memory, processors, and an iSCSI
adapter. Since you are booting from the same OES volume, you are going
to retain the same configuration. Once OES boots up, you may have to
update some drivers to access your NSS volume.

Please let us know how this works for you.


--
Kevin Boyle - Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below this post.
Thanks.
------------------------------------------------------------------------
KBOYLE's Profile: https://forums.novell.com/member.php?userid=19359
View this thread: https://forums.novell.com/showthread.php?t=504309

0 Likes
Knowledge Partner
Knowledge Partner

Re: OES11 migration hardware to esxi

The SAN is connected via Fiber Channel to the blade center via the SAN controllers (Compellent).


Do you have a SAN controller on your ESXi host or were you thinking of moving your OES and NSS volumes into a vSphere datastore?
_____
Kevin Boyle - Knowledge Partner - Calgary, Alberta, Canada
Who are the Knowledge Partners?
If you appreciate my comments, please click the Like button.
If I have resolved your issue, please click the Accept as Solution button.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: OES11 migration hardware to esxi

Yes we are going to move it into our datastore that happens to also reside
on the same SAN:). We have two HP blade chassis. Six of the blades are our
VM hosts running vSphere 6.0 off of the same SAN that a bunch of blades also
boot from. Two of them are OES boxes. The HP blade centers are end of life
so we are installing a Hyper converge system to replace it and migrating
everything over to it. the current VM will be easy. we are getting all of
our current blades that are booting from the SAN (mostly windows and sql)
either PtoV over, retiring or in this case migrating to VM and then
migrating it over to the new system. Summer is so much fun in a school
system. So this the move to migrate the HW OES box to a VM. Seems to be that
the easiest way would be to to a migrate / identity procedure using the
miggui tool. And with your suggestions looks to be pretty straight forward.

"KBOYLE" wrote in message news:KBOYLE.810hmo@no-mx.forums.microfocus.com...


> The SAN is connected via Fiber Channel to the blade center via the SAN
> controllers (Compellent).


Do you have a SAN controller on your ESXi host or were you thinking of
moving your OES and NSS volumes into a vSphere datastore?


--
Kevin Boyle - Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below this post.
Thanks.
------------------------------------------------------------------------
KBOYLE's Profile: https://forums.novell.com/member.php?userid=19359
View this thread: https://forums.novell.com/showthread.php?t=504309

0 Likes
Knowledge Partner
Knowledge Partner

Re: OES11 migration hardware to esxi

CCPS;2460778 wrote:
Yes we are going to move it into our datastore that happens to also reside on the same SAN:).

Thank you for that explanation.

The article to which I referred in an earlier post provides a method to boot your VM from your SAN and have OES access your NSS volume directly on the SAN. If your objective is to just virtualize OES and continue to access the data on the SAN in the same way the physical server does, then the procedure described in that article appears to be the simplest way to accomplish that.

If I understand your explanation correctly, the above procedure would be a temporary solution with the final objective being to move both your OES and NSS volumes into a VMware datastore. If that is the case, there may be a better way to accomplish this that does not need to use the procedure described in the article.

The best way to accomplish such a migration depends on several factors including

  • Your specific configuration.
  • The length of time an server outage can be tolerated.

Some of the ideas presented in these Cool Solution articles may be helpful. While the focus is NetWare, the procedures can also be used with OES.

Your approach to create a new OES virtual machine and migrate using "transfer id" and miggui will definitely work but it could take a very long time depending upon the size of your NSS volume and the number of files that need to be transferred. The Cool Solution articles explore this topic in greater detail.
_____
Kevin Boyle - Knowledge Partner - Calgary, Alberta, Canada
Who are the Knowledge Partners?
If you appreciate my comments, please click the Like button.
If I have resolved your issue, please click the Accept as Solution button.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: OES11 migration hardware to esxi

Yes the migrate / transfer ID is the goal and looks to be the most logical
option. I need to get the OES off of the hardware and into the VM esxi
environment. Again thanks for all of the info.

"KBOYLE" wrote in message news:KBOYLE.810u80@no-mx.forums.microfocus.com...


CCPS;2460778 Wrote:
> Yes we are going to move it into our datastore that happens to also
> reside on the same SAN:).

Thank you for that explanation.

The article to which I referred in an earlier post provides a method to
boot your VM from your SAN and have OES access your NSS volume directly
on the SAN. If your objective is to just virtualize OES and continue to
access the data on the SAN in the same way the physical server does,
then the procedure described in that article appears to be the simplest
way to accomplish that.

If I understand your explanation correctly, the above procedure would be
a temporary solution with the final objective being to move both your
OES and NSS volumes into a VMware datastore. If that is the case, there
may be a better way to accomplish this that does not need to use the
procedure described in the article.

The best way to accomplish such a migration depends on several factors
including

- Your specific configuration.
- The length of time an server outage can be tolerated.

Some of the ideas presented in these Cool Solution articles may be
helpful. While the focus is NetWare, the procedures can also be used
with OES.

- 'Quickly Virtualize your NetWare server'
(https://www.novell.com/communities/coolsolutions/quickly-virtualize-netware-server/)
- 'Migrating Files from NetWare to Linux or OES in 2017'
(https://www.novell.com/communities/coolsolutions/migrating-files-netware-linux-oes-2017/)

Your approach to create a new OES virtual machine and migrate using
"transfer id" and miggui will definitely work but it could take a very
long time depending upon the size of your NSS volume and the number of
files that need to be transferred. The Cool Solution articles explore
this topic in greater detail.


--
Kevin Boyle - Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below this post.
Thanks.
------------------------------------------------------------------------
KBOYLE's Profile: https://forums.novell.com/member.php?userid=19359
View this thread: https://forums.novell.com/showthread.php?t=504309

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.