UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21. Read more.
UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21.Read more.
Absent Member.
Absent Member.
636 views

OES2.3 to OES11.1 on VMware

Greetings,

We are about to start our journey on migrating our OES2.3 servers to
OES11.1 using the Transfer ID. We have used this process before many
times for migrations and my question is not really about that process,
but more on the planning for roll back in case something goes wrong
during the Transfer ID.

According to the documentation, it is advised to perform an eDir backup
prior to start. Since both our source and target servers are on VMware,
we were discussing shutting down both source and target to get a cold VM
snapshot prior to the Transfer ID process.

Since I have never rolled back a server from a VM snapshot before with
eDirectory, could this introduce issues into our eDirectory environment?

Any insight would be appreciated.

Thanks!
~Don


Labels (1)
0 Likes
1 Reply
Knowledge Partner Knowledge Partner
Knowledge Partner

On 07.11.2013 17:29, Don wrote:
> Greetings,
>
> We are about to start our journey on migrating our OES2.3 servers to
> OES11.1 using the Transfer ID. We have used this process before many
> times for migrations and my question is not really about that process,
> but more on the planning for roll back in case something goes wrong
> during the Transfer ID.
>
> According to the documentation, it is advised to perform an eDir backup
> prior to start. Since both our source and target servers are on VMware,
> we were discussing shutting down both source and target to get a cold VM
> snapshot prior to the Transfer ID process.
>
> Since I have never rolled back a server from a VM snapshot before with
> eDirectory, could this introduce issues into our eDirectory environment?


Yes, absolutely. The transfer ID activity at all stages makes extensive
eDirectory changes that cannot be simply undone by going back in time on
just one server. You introduce a new (temporary) server into the tree,
remove it again, and make quite a few changes to eDir when the OES2 gets
updated to OES11, e.g around the proxy users for the server.

Nothing here is a full showstopper, but it takes a lot of planning and
extensive in-depth knowledge to backout of a transfer ID either way.

CU,
--
Massimo Rosen
Novell Knowledge Partner
No emails please!
http://www.cfc-it.de
CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
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.