What is the best way to migrate to new hardware. A few physical and a few VMs. In the past I used Novell’s migration Transfer ID for Netware to OES. Is there something equivalent for SUSE. Any documentation available.
Current config:
SLES 12 sp3 (Will stay the same)
eDirectory and eDirectory LDAP
Any ideas appreciated.
Thanks!
ka12312 wrote:
[color=blue]
What is the best way to migrate to new hardware. A few physical and a
few VMs. In the past I used Novell’s migration Transfer ID for
Netware to OES. Is there something equivalent for SUSE. Any
documentation available.Current config:
SLES 12 sp3 (Will stay the same)
eDirectory and eDirectory LDAPAny ideas appreciated.
Thanks![/color]
Hi ka12312 and welcome to the SUSE forums.
Before we can answer your question, it would help if we had some
additional information…
You have installed eDirectory on SLES 12 sp3, is that correct? This is
not an system created by an OES install, correct?
How many physical servers are we talking about?
What hypervisor are you using to host your VMs?
Do your VMs reside on some kind of shared storage?
What other services are you running that need to be migrated?
–
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.
Thank you.
Hi Kevin,
The VMs are esxi VMware. I’m not certain what the physical standalone servers will be (raid 10 I know). I’m in a new job and simply getting a head start on what needs to be done. A few of these servers are OES and a few plain SLES 12 sp3. The SLES 12 servers are not an upgrade from OES, I think.
eDirectory and LDAP, certs etc are all that I know will need to be migrated. Plus several config files for third party apps I’m certain. It will take me awhile to figure out what all needs to migrate. eDir has some custom cache configs that will need to be saved. Have not found the config file yet. Only been here 9 days!
I will need to keep the same server name and IP etc as several apps link to the LDAP servers.
The transfer ID process from Netware to OES was so simple. Just wondering if SUSE has something like this. Or how to exactly do it. Any documents. I’m a bit rusty!! Forced to the other side for a few years. So happy to be back here!!
ka12312 wrote:
[color=blue]
Hi Kevin,
The VMs are esxi VMware. I’m not certain what the physical standalone
servers will be (raid 10 I know). I’m in a new job and simply
getting a head start on what needs to be done. A few of these
servers are OES and a few plain SLES 12 sp3. The SLES 12 servers are
not an upgrade from OES, I think.[/color]
That makes your migration much easier: you do not need to migrate the
services running on one server to a new server; you only need to move
your whole virtual machine(s) to a new host!
This forum, as you probably know, is for SLES install/boot issues. Do
you have any physical SLES boxes that you need to migrate?
As for VMware, what version of vSphere are you running and what version
of ESXi?
Are you upgrading any of the VMware stuff or simply installing ESXi on
a new box(es) and migrating the VMs?
Can you describe a bit about what you are trying to accomplish and I’ll
offer some suggestions how you might proceed.
[color=blue]
The transfer ID process from Netware to OES was so simple. Just
wondering if SUSE has something like this. Or how to exactly do it.
Any documents. I’m a bit rusty!! Forced to the other side for a few
years. So happy to be back here!![/color]
Transfer ID is a Novell process that allows you to transfer NetWare/OES
services from one server to a new server and make the new server appear
to be the old server. It greatly simplifies certain types of
migrations. It may still be useful.
If you are upgrading a VM’s OS from one major version to a new one, be
aware of this:
VMware support for guest operating system upgrade (2018695)
https://kb.vmware.com/s/article/2018695
–
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.
Thank you.
I will be migrating six sles servers currently on a physical server to new servers.
As far as VMWare, I have not yet talked to the VM folks to get access. Only my ninth day here. It’s the physical ones I’ll need to investigate. Basically the new server taking on the complete identity of the old server, server config, eDirectory and I think that is all at this point. It has been awhile since I have done this. Why I am planning ahead! That would be great if transfer ID worked.
I’ll acquire additional info over the next several weeks. I’ll get back.
Thank you again! I appreciate it!
ka12312 wrote:
[color=blue]
Basically the new server taking on the complete identity of the old
server, server config, eDirectory and I think that is all at this
point.[/color]
If you need new or additional VMware ESXi hosts you just add them to
the mix: New host names, IP addresses, whatever. eDirectory doesn’t
enter into the picture.
If you need your existing SLES or OES VMs to run on the new VMware
hosts, you just migrate the VMs using the vSphere Web client and it’s
done. You don’t have to do anything to the actual SLES/OES server and
you don’t have to worry about migrating to a new server because your
virtual server is not changed in any way. The VM migration takes only a
couple of minutes, especially if the VMs reside on shared storage that
is accessible by both hosts.
–
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.
Thank you.
I have migrated VMs for certain. I’m thinking they may want me to migrate some physical servers to VMs. As well as migrate a few standalone servers to new hardware. I’m working on a plan. One of the servers is our main LDAP servers. If that goes wonky I’m in trouble! I will be spending a lot of time testing and planning. I have done this before. Just need to remeber how I did it. ANy tips appreciated. Thank you Kevin!!
ka12312 wrote:
[color=blue]
ANy tips appreciated.[/color]
Once you have a better understanding of just what you need to
accomplish and have some specific examples, come back and let us know.
In the mean time, good luck!
–
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.
Thank you.
Thank you Kevin! I will stay in touch!!