MHGlenn Absent Member.
Absent Member.
1928 views

iFolder 3.8 to 3.9 via MIGGUI Consolidate: No-go?

Hello; it's me again.

I'm having a spot of trouble here: I need to consolidate from an OES2-SP3 server to a new OES-11 box, but for some reason I can't get the MIGGUI application to recognize iFolder on the source and target servers. I've run it several times, and now I'm re-building the target server from scratch just in case I missed something in the instructions.

In the meantime, any input on this? I don't suppose I could just copy the entire /var/simias tree over to the new server and be done with it?

Thanks.
Labels (1)
Tags (3)
0 Likes
4 Replies
hpfeil Absent Member.
Absent Member.

Re: iFolder 3.8 to 3.9 via MIGGUI Consolidate: No-go?

Check out below. Make sure you don't patch until after the migration. Hope this helps.
-Hans




Markus,
Almost correct. The rebooting and patching parts are correct.
However, if we avoid patching until migration has been completed then
the miggui file transfer problem (where the system hangs and volumes may
not show) will not occur. Patching induces the trouble.
The reboot step is to ensure the machine is internally consistent
before we make further changes, particularly after adding OES11.
Id transfers will require console access without the machine's network.
Thus we can progress without waiting for Novell to issue an OES11
patch, by simply not patching. I recommend avoiding NCC registration
until the machine is completely built and checked out, migrations done,
polishing completed, and we have had another cup of coffee to mentally
review matters.
Novell is aware of all these awkward aspects; hopefully many can be
overcome in the near term.
Joe D.

On 29/12/2011 07:48, Markus Borst (HRZ) wrote:

> If I understand you correctly, your suggested sequence would be scenario
> dependent:
>
> Identity transfer:
> - Install SLES11 SP1
> - Install OES11
> - reboot
> - start miggui from the physical console (or iLO for HP machines or
> vmware console for virtual ESX machines etc., etc.)
> - Register machine for patch channels, install patches
>
> Filemigration (and others):
> - WAIT for Novell to release Patches to miggui
> - Install SLES11 SP1
> - Install OES11
> - Register for patch channels, patch everything (including the then
> released miggui patch)
> - Do the migration
>
> If I got your suggestions wrong, please correct me.
>
> Greetings
> Markus Borst
>
>
> Am 28.12.2011 10:58, schrieb Joe Doupnik:

>> Before the holidays I wrote a heads up note about potential
>> problems with the migration utilities in OES11. Today I know more and
>> offer more specific guidance. There is an easy way around the problems I
>> encountered.
>>
>> First, how I dug a hole. I built SLES 11 SP1, polished it, patched
>> it. Then OES11 was added (add-on product), and patching was done again.
>> Afterward the migration material was employed. Two bad things happened
>> to me. The first was miggui would hang when trying to migrate files. The
>> cause was an ldapsearch call was prompting for a password, but the
>> miggui code had shunted aside the prompt and still waited for it. After
>> considerable debugging I identified the problem and created a
>> workaround. Then the same operation failed to show volumes on the source
>> server. More debugging, I identified that problem and created a
>> workaround. File migration then worked as expected. I climbed out of the
>> holes. Novell has my reports and solutions and we are discussing the
>> matters.
>> The problems I encountered were in Ruby code which yielded
>> different behaviours depending upon the way I patched things.
>>
>> Second, I went back and ran a battery of test cases, building
>> destination machines differently and performing an entire identity
>> transfer migration. From this emerged confirmation of a platitude: Delay
>> all patching until the machine has been completely built. Just ignore
>> the many prompts to register with NCC.
>> The tests showed me that identity transfer migration (including the
>> file movement part) works with the unpatched media. That should be
>> reassuring news for readers. Tests showed me that patching SLES before
>> installing OES11 could lead to problems, and that patching again after
>> OES11
>> installation could/did make matters worse for migration. Novell said
>> they test with patching SLES and then adding OES11, but not with
>> patching twice. My experience is patching once or twice is inviting
>> trouble in this particular code.
>>
>> The safe path forward is avoid patching until migration has been
>> completed and you are happy with the results.
>>
>> Then there is another problem waiting to pounce. Between the steps
>> of adding OES11 and starting migration you must reboot the machine.
>> Failure to reboot will cause failure of the identity transfer process.
>> What is going on is adding OES11 creates additions to a user's PATH to
>> access eDirectory utilities. That PATH becomes usable after a reboot. If
>> we don't reboot then the migration code cannot find needed eDir
>> utilities and fails.
>>
>> There is a potential problem waiting for those of us who upgrade
>> remotely. The identity transfer process changes the IP address of the
>> destination machine, and miggui is run on that machine. The IP change
>> step occurs partway through the sequence and thus our connection
>> vanishes at that point, leaving migration in an unknown state. There is
>> a pop up window which clearly states if migrating remotely then one must
>> go to the console of the machine to perform the IP address change and
>> all which follow it. If that console is not within reach then sorry, you
>> are now wedged. Trying to reconnect and rerun the migration utility may,
>> might, we don't really know, produce a good completion. The guidance is
>> perform identity transfer only if you can lay hands upon the destination
>> machine; do not do it remotely.
>>
>> All of the above and more is being discussed in the background. A
>> fix for the miggui code on the first problems will hopefully be issued
>> through the patch channels, but I don't know when. You have information
>> on how to avoid those problems. The remaining issues are for future
>> editions of the software.
>>
>> This story has a happy ending. Just do less to accomplish more.
>> Joe D.
>> P.S. If we think back to that uncomfortable thread about where is the
>> OES11 patch channel, we now see that avoiding patches is our goal, not
>> adding them to satisfy habits.
>> _______________________________________________
>> novttp mailing list
>> novttp@lists.novttp.org
>> http://www.novttp.org/mailman/listinfo/novttp

>


_______________________________________________
novttp mailing list
novttp@lists.novttp.org
http://www.novttp.org/mailman/listinfo/novttp








>>> On 3/15/2012 at 1:16 PM, in message <MHGlenn.59hd4n@no-mx.forums.novell.com>, MHGlenn<MHGlenn@no-mx.forums.novell.com> wrote:



Hello; it's me again.

I'm having a spot of trouble here: I need to consolidate from an
OES2-SP3 server to a new OES-11 box, but for some reason I can't get the
MIGGUI application to recognize iFolder on the source and target
servers. I've run it several times, and now I'm re-building the target
server from scratch just in case I missed something in the instructions.


In the meantime, any input on this? I don't suppose I could just copy
the entire /var/simias tree over to the new server and be done with it?


Thanks.


--
MHGlenn
------------------------------------------------------------------------
MHGlenn's Profile: http://forums.novell.com/member.php?userid=6822
View this thread: http://forums.novell.com/showthread.php?t=453494
0 Likes
MHGlenn Absent Member.
Absent Member.

Re: iFolder 3.8 to 3.9 via MIGGUI Consolidate: No-go?

Well, I certainly got further; The File System configuration doesn't hang anymore.

But I still do not see any option to migrate the iFolder service; just the file system.

Am I still missing something?
0 Likes
hegdegg Absent Member.
Absent Member.

Re: iFolder 3.8 to 3.9 via MIGGUI Consolidate: No-go?

You may want to check the doc that has list of supported migration scenarios. http://www.novell.com/documentation/oes11/mig_tools_lx/data/bg4flrr.html. Migration from OES2 SP3 to OES11 is not a supported scenario.

You could just copy the simias data path, in case of transfer ID.

>>> MHGlenn<MHGlenn@no-mx.forums.novell.com> 3/15/2012 11:46 PM >>>


Hello; it's me again.

I'm having a spot of trouble here: I need to consolidate from an
OES2-SP3 server to a new OES-11 box, but for some reason I can't get the
MIGGUI application to recognize iFolder on the source and target
servers. I've run it several times, and now I'm re-building the target
server from scratch just in case I missed something in the instructions.


In the meantime, any input on this? I don't suppose I could just copy
the entire /var/simias tree over to the new server and be done with it?


Thanks.


--
MHGlenn
------------------------------------------------------------------------
MHGlenn's Profile: http://forums.novell.com/member.php?userid=6822
View this thread: http://forums.novell.com/showthread.php?t=453494
0 Likes
hegdegg Absent Member.
Absent Member.

Re: iFolder 3.8 to 3.9 via MIGGUI Consolidate: No-go?

Migration support is present only from iFolder2.x and iFolder 3.2 to latest version. However, if you use Transfer ID migration, and move the /var/simias tree over to new server you will be able to get iFolder working fine on the new servers. Please note, you will have to use transfer id migration and then configure iFolder server and retain the datastore path as is, if the datastore was on /var/simias/ even on the new server you should have it on /var/simias/ and move all data.

Let me know if you need more info.

regards,
gg

>>> MHGlenn<MHGlenn@no-mx.forums.novell.com> 3/15/2012 11:46 PM >>>


Hello; it's me again.

I'm having a spot of trouble here: I need to consolidate from an
OES2-SP3 server to a new OES-11 box, but for some reason I can't get the
MIGGUI application to recognize iFolder on the source and target
servers. I've run it several times, and now I'm re-building the target
server from scratch just in case I missed something in the instructions.


In the meantime, any input on this? I don't suppose I could just copy
the entire /var/simias tree over to the new server and be done with it?


Thanks.


--
MHGlenn
------------------------------------------------------------------------
MHGlenn's Profile: http://forums.novell.com/member.php?userid=6822
View this thread: http://forums.novell.com/showthread.php?t=453494
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.