03.10.2012 Views

File_System_Migration

File_System_Migration

File_System_Migration

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Planning and Design<br />

Evaluate migration<br />

issues<br />

Step Action<br />

To outline areas to consider with regard to migration issues, perform<br />

the following:<br />

1 Document future plans for the VNXstorage configuration.<br />

The migration analyst must understand growth potential regarding VNX requirements. At a minimum, obtain<br />

growth patterns over the last several months on each of the identified file systems. Take that information and<br />

increase the value by a minimum of 20%.<br />

2 If appropriate, review and document the Windows domain model for trust relationships from the CIFS source<br />

file server's domain to other domains in the environment.<br />

For every domain with a trust to the source file server, ensure that there is a domain entry in Usermapper.<br />

3 Identify any additional hardware required to achieve the migration.<br />

Additional hardware could be limited to a UNIX workstation or Windows client that acts as an NFS or domain<br />

client in the network, or might include adding NICs to each server for the purposes of providing a private<br />

network.<br />

Additional switches and other network hardware might be necessary to accomplish the migration in a timely<br />

manner.<br />

4 Consider that CDMS requires that a Data Mover mount an NFS or CIFS source file server to permit the<br />

copying of files to the MGFS.<br />

Although the source file servers must be shared or exported to permit this, they might be shared with<br />

permissions limited to allow only the destination Data Mover to access the source, and deny any other<br />

means of access which could modify the source during the migration.<br />

5 Determine whether any of the NFS source file servers are NetApp servers.<br />

If NetApp servers are present, migration from the server requires additional migration steps. Appendix E,<br />

“Network Appliance Considerations,” provides further information about the steps required for this particular<br />

environment.<br />

This release of CDMS does not support migration of CIFS data from NetApp servers.<br />

6 Identify any additional software or software upgrades required to achieve the migration.<br />

If the target VNX is not running version 5.6 or later, you must install a software upgrade.<br />

7 Define any other constraints pertinent to the migration effort.<br />

Note: Even if the Data Mover is configured for Virus Checker, the data<br />

migration of CDMS with the server_cdms command script does not trigger<br />

Virus Scan as long as scan on read is turned off on the Data Mover. If scan on<br />

read is turned on, the CDMS data migration does trigger Virus Scan. In this<br />

case, the performance impact on the Virus Checker software and the Data<br />

Mover must be considered.<br />

80 VNX <strong>File</strong> <strong>System</strong> <strong>Migration</strong> Version 2.0 for NFS and CIFS User Guide 7.1

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!