Anonymous_User

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2013-11-07
16:29
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
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
1 Reply


Knowledge Partner
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2013-11-08
12:45
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
> 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
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de