Highlighted
Contributor.
Contributor.
747 views

NSS32 to NSS64 for Filr - HowTo?

Hello everyone,
we do have user files located at OES2015SP1 server. It is also a home file server for our users. Lets call this volume HOME. This HOME volume is connected to Filr. This HOME volume is also clustered - so it have own IP address, it hawe own virtual server name etc. Users are using the Filr Desktop client also.

HOME volume is NSS32. We need to convert this volume to NSS64. How to do that? Is there any way?

I found no way to convert NSS32 to NSS64. I found a way of migration only:
https://www.novell.com/documentation/oes2015/stor_nss_lx/data/t42v5hiqjnzn.html

I hope I do not need to use this way of migration. I cant imagine how to manage this. How to prevent Filr Desktop clients to be desynchronized? Did anybody try this task?

Is already a way of conversion NSS32 to NSS64 instead of migration to new volume?
I just found there are a lot of another unhappy admins with the same idea, but I do not know if there is any result or fix:
https://ideas.microfocus.com/MFI/novell-oes/Idea/Detail/2049
0 Likes
5 Replies
Absent Member.
Absent Member.

Am 13.06.19 um 11:04 schrieb jsimek:
>
> Hello everyone,
> we do have user files located at OES2015SP1 server. It is also a home
> file server for our users. Lets call this volume HOME. This HOME volume
> is connected to Filr. This HOME volume is also clustered - so it have
> own IP address, it hawe own virtual server name etc. Users are using the
> Filr Desktop client also.
>
> HOME volume is NSS32. We need to convert this volume to NSS64. How to do
> that? Is there any way?
>
> I found no way to convert NSS32 to NSS64. I found a way of migration
> only:
> https://www.novell.com/documentation/oes2015/stor_nss_lx/data/t42v5hiqjnzn.html
>
> I hope I do not need to use this way of migration. I cant imagine how to
> manage this. How to prevent Filr Desktop clients to be desynchronized?
> Did anybody try this task?
>
> Is already a way of conversion NSS32 to NSS64 instead of migration to
> new volume?
> I just found there are a lot of another unhappy admins with the same
> idea, but I do not know if there is any result or fix:
> https://ideas.microfocus.com/MFI/novell-oes/Idea/Detail/2049
>
>


Check:
<https://www.novell.com/documentation/open-enterprise-server-2018/stor_nss_lx/data/mediaupgr.html>

Bernd
0 Likes
Highlighted
Contributor.
Contributor.

nntp-user;2500882 wrote:
Am 13.06.19 um 11:04 schrieb jsimek:
>
> Hello everyone,
> we do have user files located at OES2015SP1 server. It is also a home
> file server for our users. Lets call this volume HOME. This HOME volume
> is connected to Filr. This HOME volume is also clustered - so it have
> own IP address, it hawe own virtual server name etc. Users are using the
> Filr Desktop client also.
>
> HOME volume is NSS32. We need to convert this volume to NSS64. How to do
> that? Is there any way?
>
> I found no way to convert NSS32 to NSS64. I found a way of migration
> only:
> https://www.novell.com/documentation/oes2015/stor_nss_lx/data/t42v5hiqjnzn.html
>
> I hope I do not need to use this way of migration. I cant imagine how to
> manage this. How to prevent Filr Desktop clients to be desynchronized?
> Did anybody try this task?
>
> Is already a way of conversion NSS32 to NSS64 instead of migration to
> new volume?
> I just found there are a lot of another unhappy admins with the same
> idea, but I do not know if there is any result or fix:
> https://ideas.microfocus.com/MFI/novell-oes/Idea/Detail/2049
>
>


Check:
<https://www.novell.com/documentation/open-enterprise-server-2018/stor_nss_lx/data/mediaupgr.html>

Bernd


Thank you for a reply, Bend, but I thing this do not solve the task we need. We need to upgrade NSS32 to NSS64, because we need to improve size of disk. Maximum capacity of NSS32 formatted disk can be 8TB. We need more than 8TB disk.
JS
0 Likes
Highlighted
Outstanding Contributor.
Outstanding Contributor.

Legacy NSS32 cannot currently be in-place upgraded to NSS64, migration is required
OES development team MAY have an unreleased tool, but I haven't heard of anything.
0 Likes
Highlighted
Contributor.
Contributor.

Hello,

I am sorry for long time of no answer. I have saved a time now to look for a solution for this task. But no success yet. Anone can help me? Our NSS32 pool is used for CIFS access. The same pool is used for Filr, Filr desktop client etc. It is also indexed by filr all the time for file changes. So WE NEED TO HAVE THE SAME NAME OF CLUSTER AND VOLUME after creation. Name change is rally not acceptable. Anyone use also clustered environment with Filr? Can anyone help me how to migrate to NSS64?

0 Likes
Highlighted
Honored Contributor.
Honored Contributor.

Are you sure, this is really a problem? Did you try what happens, if the home directory of a user is moved from one Netfolder server to another Netfolder server?
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.