Veritas Storage Foundation Portable Data Containers: Cross-Platform Data Sharing 5.0.1 Administrators Guide, HP-UX 11i v3, First Edition, November 2009

To perform a one-time migration
1
If the underlying Volume Manager storage is not contained in a CDS disk
group, it must first be upgraded to be a CDS disk group, and all other physical
considerations related to migrating the storage physically between systems
must first be addressed.
See “Converting a non-CDS disk group to a CDS disk group” on page 25.
2
If the file system is using a disk layout version prior to 7, upgrade the file
system to Version 7.
See the Veritas Storage Foundation Installation Guide.
3
Use the following command to ensure that there are no files in the file system
that will be inaccessible after migrating the data due to large file size or to
differences in user or group ID between platforms:
# fscdsadm -v -t target mount_point
If such files exist, move the files to another file system or reduce the size of
the files.
4
Unmount the file system:
# umount mount_point
5
Use the fscdsconv command to convert the file system to the opposite endian.
See “Converting the byte order of a file system” on page 53.
6
Make the physical storage and Volume Manager logical storage accessible on
the Linux 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 “Disk tasks” on page 31.
7
Mount the file system on the target system.
Migrating a file system on an ongoing basis
This example describes how to migrate a file system between platforms 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.
51File system considerations
Migrating a file system on an ongoing basis