Moving NCS cluster from old to new storage

  • 7024590
  • 29-Apr-2020
  • 29-Apr-2020


Open Enterprise Server 2018 (OES 2018) Linux
Open Enterprise Server 2015 (OES 2015) Linux


Migrating OES NCS cluster from old to new SAN.
OES2018SP1/SLES12SP3 cluster (failover) with NSS32 Pools and the SDB RAID1 (512 MB) with 2 segments.


1. Migrate SDB to new storage on master node: nssmu -> Raid 1 -> Segments -> delete 1 segment -> expand with a partition on new storage; wait for sync; redo with the other partition;

2. Create an Local NSS64 Pool and volume on the new SAN LUN, which is presented on the OES Cluster servers. 3. Migrate the NSS32 cluster volume data to NSS64 volume . For migrating NSS data from NSS32 to NSS64 , refer link : 4. Make a note of NSS32 resource name, virtual server name , cifs server name , ip address , scripts ? load/unload/monitor and protocols selected and Offline cluster resource . It will be useful while you cluster enable NSS64 pool. 5. Rename the NSS32 pool to some name , because later we wanted to rename the NSS64 POOL with same name of NSS32 pool name. 6. Delete the NSS32 cluster resource , you can try this , steps ( 1 to 3 only) 7. Rename the NSS64 - step(1) pool to match the NSS32 resource POOL name and also rename the volume . 8. Cluster enable the step(1) NSS 64 pool - refer this link - with the same resource name , ip etc.. noted in step (3) 9. Modify the load/unload/monitor scripts if any additional changes to be done on NSS64 resource noted in step (3)
10.Online the NSS64 resource and verify login scripts , user access and applications working fine.

Additional Information

Note:  Don't remove/delete the existing NSS32 for few weeks until you made sure everything is working fine with new NSS64 pool resource. It is kept as an backup.

Note: The pool move cannot move the Pool data from NSS32 to NSS64. By default, pool creations tools/utilities(NSSMU or iManager from OES2018 release onward) doesn't show creation of new NSS32 pools. If your still OK with going ahead with NSS32 Pool on the new LUNs, then use nlvm utility to create NSS32 pool.