Ongoing Migration of a File System

The following example describes how to migrate a file system between on an ongoing basis. Some of the following steps require a backup of the file system to be created. To simplify the process, you can create one backup before performing any of the steps instead of creating multiple backups as you go.

  To perform an ongoing migration

1. Ensure that there are no files in the file system that will be inaccessible after migrating the data due to large file size or user/group id platform differences:
      # fscdstask validate OS mount_point

   If such files exist, move the files to another file system or reduce the files' sizes.

   ---

     Note    There is no output if no limits are exceeded.

   ---

2. Add to the OS_list file:
3. Enforce the limits:
      # fscdstask limit enforce mount_point

   This is the last of the preparation steps. When the file system is to be migrated, it must be unmounted, and then the storage moved and mounted on the target system:

4. Unmount the file system:
      # umount mount_point
5. Use the fscdsconv command to convert the file system to the opposite endian, if required. See Converting a File System.
6. Make the physical storage and Volume Manager logical storage accessible on the system by exporting the disk group from the source system and importing the disk group on the target system after resolving any other physical storage attachment issues. See Maintaining Your System for more information.
7. Mount the file system on the target system.

Ceasing Ongoing Migration

To stop performing ongoing migrations and leave the file system on the current system, the enter the following commands to stop the usage of CDS mechanisms: