Exporting a file system and a recovery groups on an old ECE cluster
Use the mmexportfs command to export both file system and recovery group configurations.
For more information about the mmexportfs command, see the mmexportfs in the IBM Storage Scale: Command and Programming Reference Guide in the IBM Storage Scale documentation.
-
Check the recovery group and file system state.
- Check the file system state.
A sample output is as follows:mmvdisk fs list --fs test_fs1vdisk with list of holds holds storage vdisk set recovery group count trim failure groups metadata data pool -------------- -------------- ----- ---- -------------- -------- ----- ------- VS1 rg1 8 0 1, 2 yes yes system - Check the recovery
state.
A sample output is as follows:mmvdisk rg list --rg rg1 --da --server --vdisk-set --pdisknode number server active remarks ------ -------------------------------- ------- ------- 3 c72f3u25-eth0 yes serving rg1: LG002, LG006 1 c72f3u27-eth0 yes serving rg1: root, LG004, LG008 2 c72f3u29-eth0 yes serving rg1: LG001, LG005 4 c72f3u31-eth0 yes serving rg1: LG003, LG007 declustered needs vdisks pdisks capacity array service type BER trim user log total spare rt total raw free raw background task ----------- ------- ---- ------- ---- ---- --- ----- ----- -- --------- -------- --------------- DA1 no HDD enable no 8 9 16 2 2 24 TiB 12 TiB scrub 14d (61%) mmvdisk: Total capacity is the raw space before any vdisk set definitions. mmvdisk: Free capacity is what remains for additional vdisk set definitions. declustered paths AU pdisk array active total capacity free space log size state ------------ ----------- ------ ----- -------- ---------- -------- ----- n001p001 DA1 1 1 1863 GiB 1017 GiB 3072 MiB ok n001p002 DA1 1 1 1863 GiB 1017 GiB 3072 MiB ok n001p003 DA1 1 1 1863 GiB 1017 GiB 3072 MiB ok n001p004 DA1 1 1 1863 GiB 1017 GiB 3072 MiB ok n002p001 DA1 1 1 1863 GiB 1024 GiB 3072 MiB ok n002p002 DA1 1 1 1863 GiB 1016 GiB 3072 MiB ok n002p003 DA1 1 1 1863 GiB 1017 GiB 3072 MiB ok n002p004 DA1 1 1 1863 GiB 1017 GiB 3072 MiB ok n003p001 DA1 1 1 1863 GiB 1018 GiB 3072 MiB ok n003p002 DA1 1 1 1863 GiB 1017 GiB 3072 MiB ok n003p003 DA1 1 1 1863 GiB 1017 GiB 3072 MiB ok n003p004 DA1 1 1 1863 GiB 1017 GiB 3072 MiB ok n004p001 DA1 1 1 1863 GiB 1017 GiB 3072 MiB ok n004p002 DA1 1 1 1863 GiB 1018 GiB 3072 MiB ok n004p003 DA1 1 1 1863 GiB 1017 GiB 3072 MiB ok n004p004 DA1 1 1 1863 GiB 1017 GiB 3072 MiB ok declustered capacity all vdisk sets defined recovery group array type total raw free raw free% in the declustered array -------------- ----------- ---- --------- -------- ----- ------------------------ rg1 DA1 HDD 24 TiB 12 TiB 50% VS1 vdisk set map memory per server node class available required required per vdisk set ---------- --------- -------- ---------------------- nc1 10 GiB 3633 MiB VS1 (48 MiB)
- Check the file system state.
- Unmount the file system.
A sample output is as follows:# mmumount test_fs1 -ammumount: Unmounting file systems ... - Export the file
system.
A sample output is as follows:# mmexportfs test_fs1 -o exportmmexportfs: Processing file system test_fs1 ... mmexportfs: Propagating the cluster configuration data to all affected nodes. This is an asynchronous process. mmcommon pushSdr_async: mmsdrfs propagation started mmcommon pushSdr_async: mmsdrfs propagation completed; mmdsh rc=0 - Save the export generated configuration file for later use in the new cluster. It is important to save the export file even after importing file system for later reference.
- Move all drives to the destination servers of the new cluster.
- Remove drives from each server on the old cluster.
- Label each drive with a corresponding server ID to maintain clarity.
- Insert the drives into the new server, ensure that the drive to server relation is identical.
- Ensure that drives of different servers within a single server in the new cluster are not mixed.
- Ensure that all the drives were migrated. The mmimportfs command might fail if missing drives are found during the process.