martynweber Absent Member.
Absent Member.
1375 views

Windows migration to OES2SP1 failing

Trying to migrate from a Windows 2000/2003 server to OES2SP1. Have managed to migrate the USER's home directory share although I had to modify one of the script to take a list of usernames and groups we wanted to transfer as the script was failing as the AD contains too many grps and users for the script to hold.

However trying on a larger share now and the ntfsmap script is failing. It taking forever to run and is eventually getting killed by the system.

Looking at the script it is stuck in the line...

ntfs_tree.build_from_ntfs_collection (YAML.load_windows_yaml (input ) )

The input file containing all the Windows acls is 168MB in size so I apprieciate this might take a while. However the script never gets passed this point.

Any suggestions or alternative migration strategies apprieciated as senior management are questioning if a migration back to Novell from Windows is the right way forward.

regards
Martyn
Labels (1)
Tags (3)
0 Likes
3 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Windows migration to OES2SP1 failing

martynweber wrote:
> Trying to migrate from a Windows 2000/2003 server to OES2SP1. Have
> managed to migrate the USER's home directory share although I had to
> modify one of the script to take a list of usernames and groups we
> wanted to transfer as the script was failing as the AD contains too many
> grps and users for the script to hold.
>
> However trying on a larger share now and the ntfsmap script is failing.
> It taking forever to run and is eventually getting killed by the
> system.
>
> Looking at the script it is stuck in the line...
>
> ntfs_tree.build_from_ntfs_collection (YAML.load_windows_yaml (input )
> )
>
> The input file containing all the Windows acls is 168MB in size so I
> apprieciate this might take a while. However the script never gets
> passed this point.
>
> Any suggestions or alternative migration strategies apprieciated as
> senior management are questioning if a migration back to Novell from
> Windows is the right way forward.
>
> regards
> Martyn
>
>


Hi Martyn

YAML.load_windows_yaml reads set of objects from the specified yaml file
and return to the caller, in this case it is ntfsmap. Definitely for
168MB of input file takes more time to load and read, however it should
not be killed by system.

Can you send us /var/log/messages file to check why ntfsmap is being
killed by system. You need to get this file whenever you hit this issue.

Can you also send us the project.log file created in your project directory.

Thanks,
Ramesh
0 Likes
martynweber Absent Member.
Absent Member.

Re: Windows migration to OES2SP1 failing

Cant find any reference to the ntfsmap program in the messages file and there is no project.log file as Im running the command line tools rather than the windows share migration which failed completely.
I apprieciate that it takes a long time, but this was left for 3 days before it failed. If i do need to send the messges file, where should I send it?
Am i better raising a helpdesk call?
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Windows migration to OES2SP1 failing

martynweber wrote:
> Cant find any reference to the ntfsmap program in the messages file and
> there is no project.log file as Im running the command line tools rather
> than the windows share migration which failed completely.
> I apprieciate that it takes a long time, but this was left for 3 days
> before it failed. If i do need to send the messges file, where should I
> send it?
> Am i better raising a helpdesk call?
>
>


Looks like an issue with ntfsmap in loading huge volume file as input
file. I suggest you to please raise a SR through Novell support, so that
they will file a defect and we can fix the same.
In this way you will be getting the fixed rpm too.

We appreciate your commitment towards Novell!!

Thanks,
Ramesh
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.