File_System_Migration

CDMS Overview
◆ For small migrations, the level of planning required to migrate
data from source file servers to a VNX is likely modest, but still a
necessary part of the process. At a minimum, the following tasks
are performed:
Analyzing CIFS shares and NFS exports
Calculating the amount of data to be migrated
Configuring VNX storage
Estimating migration times
Optionally, excluding certain files/directories from migration
Optionally, identifying large/highly used files
Mapping source and destination shares and exports
Reviewing the basic network for the migration process
Scheduling the migration
Understanding the source file server’s data structure
However, migrations of more than 10 servers require a significant
effort in planning and designing the migration. For large
migrations, a detailed project plan might be required as a
roadmap.
NFS specific The following environmental assumptions are unique to NFS data
migrations:
◆ The UNIX environment, including the source file server and Data
Mover, is configured correctly for appropriate access, including
Domain Name System (DNS) and Network Information Service
(NIS) access, if required.
◆ For Perl migration planning scripts only, CDMS has a UNIX
workstation capable of supporting an NFS connection. In
addition, ensure that the Perl package is 64-bit compatible.
CIFS specific The following environmental assumptions are unique to CIFS data
migrations:
◆ The CIFS environment, including the Windows source file server
and Data Mover, is configured within the same domain.
Usermapper is strongly recommended for CDMS migrations that
use the CIFS protocol. Usermapper should be configured for all
domains that have access to files and shares on the source file
server.
24 VNX File System Migration Version 2.0 for NFS and CIFS User Guide 7.1