Dell VNX5600 Using VNX File Migration Technical Notes
Dell VNX5600 Manual
 |
View all Dell VNX5600 manuals
Add to My Manuals
Save this manual to your list of manuals |
Dell VNX5600 manual content summary:
- Dell VNX5600 | Using VNX File Migration Technical Notes - Page 1
Using VNX® File Migration Technical Notes P/N 300-014-344 REV 05 February, 2016 This technical notes document contains information on these topics: VNX file migration overview 3 Migration of system configurations 13 VDM level migration 17 FS level migration 21 VNX file migration - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 2
migration 88 View summary information of migration 90 View detailed information of migration 92 Create a FS level migration 97 Appendix A: Troubleshooting 101 Appendix B: Migration roll back 105 Appendix C: Moving a CIFS server to a VDM from a physical Data Mover ...121 2 Using VNX - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 3
Migration Tool, refer to the VNX File Migration Tool User Guide provided with the tool. Types of VNX file migrations VNX file will not be migrated. The source and destination system software versions that are supported for VDM level migrations are listed in Table 1. File system level migration - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 4
on the actual size of the checkpoint data being migrated from the source and not the size of the SavVol on the source. Table 1. Supported source to destination system configuration, VDM and FS migrations Source System Legacy Celerra system running DART software version 6.0.41 or later VNX system - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 5
overview Control Station network ports, see the Security Configuration Guide for VNX. Enforced file system ID preservation and NFS system can be migrated over to the new source system. This feature is only supported when migrating off of the source system. For example, if you had replication from - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 6
be used to preserve the DR sessions. Only remote DR solutions that are created using replication sessions are supported. Loopback and local replications are not supported. The source system maintains the existing DR solutions after the migration complete operation (running the Complete command - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 7
VNX file migration overview Note: For more information about one-to-many replication configurations, see the Using VNX Replicator guide. The following sections provide descriptions and graphical depictions of an example migration of a one-to-many configuration. Existing replication configuration - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 8
VNX file migration overview 3. Session 3: A remote replication session, the destination of this RepV2 session is fs1_replica3 on the server_4 in another remote system, DR System. This replication session will be migrated. After migration create Figure 2 shows the processes of migration create - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 9
VNX file migration overview 3. Synchronizes the destination FS (fs1/server_5) with the source FS through replication Session 5. Note: Loopback replication (Session 1) and local replication (Session 2) are not migrated. After migration complete phase 1: reverse PFS Figure 3 shows phase 1 of the - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 10
VNX file migration overview Migration rollback: reverse PFS Note: If you need to roll back the migration, you must do so before migrating the DR solution (before complete phase 2), when you are maintaining the original DR configuration, or before you initiate a Delete process when you are not - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 11
VNX file migration overview After migration complete phase 2: take over DRs Figure 5 shows phase 2 of the processes of the migration complete command: take over DRs. New Destination System (original Source System) New Source System (original Destination System) server_2 fs1 Session 5 ( - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 12
VNX file migration overview 7. Create new replication Session 6 (incremental attach). 8. Synchronizes the replica fs1_replica3 with the destination FS fs1/server_5 through replication Session 6. 12 Using VNX® File Migration Technical Notes - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 13
service Note: The virus checking rights on the local group of the source DM are not migrated to the destination. You must manually reconfigure the virus checking rights by using the MMC Snap-in on the destination system after the migration has completed. If the source system configurations - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 14
you can choose the overwrite_destination option to enforce a migration of all DNS (and other service) settings from the source to the destination. You can choose to configure DNS on the destination DM manually, in this case the configuration tool will not migrate them. NTP migrate_system_conf will - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 15
actual parameter values have been changed. The Migrate_system_conf script does not support the migration of server parameters if a file system is mounted the usermapper service in the destination cabinet manually. Migrate_system_conf will not help to disable the usermapper service in the destination - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 16
is retired. Plan carefully before using this tool. The database of the usermapper service in the destination will be backed up to /tmp/nasadmin/migrate_system_conf/usermapper_backu p/ before erasing it. Manually configure the destination usermapper as secondary and point to the source if the - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 17
. The system does not track file system mount/unmount or checkpoint create/delete/refresh operations triggered by an administrator or data services after the migration plan is created. VDM level migration occurs in the following sequence without DR preservation: 1. Create migration plan (nas_migrate - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 18
VDM level migration 6. Delete migration plan (nas_migrate -plan -delete) VDM level migration occurs in the following sequence with DR preservation: 1. Create migration plan (nas_migrate -plan -create -dr) 2. Create migration (nas_migrate -create) 3. Complete migration (nas_migrate -complete) 4. ( - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 19
one physical DM to another. Migrations must be initiated from the destination of the migration. Each VDM level migration can only support migration of one VDM. It does not support multiple VDMs in a migration. File systems that are exported for NFS and Windows hosts are not excluded from a VDM - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 20
VDM level migration is 256 per DM. If the number of file systems exceeds the restrictions, they cannot be migrated concurrently. The VDM ID may change; if using NDMP backups on the VDM, you should ensure that the backup software has the correct path. The replication sessions to be migrated must - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 21
on the destination DM, which will allow you to specify a smaller SavVol in order to reduce space usage. If you are creating the destination FS manually, this destination FS must be empty, mounted to a DM or a VDM as read-only, and have an identical size as the source FS and keep - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 22
FS level migration If the destination is a VDM, the system will try to create and use the same mount point name on the destination side. If the same mount point name is already used by another file system, the migration will fail. If -enforce_fsid is not specified, the system cannot guarantee that - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 23
be initiated from the destination of the migration. Each FS level migration can only support one FS (including its read- only checkpoints). The source FS must be DM to a physical destination DM, some additional manual steps are required in the process: 23 Using VNX® File Migration Technical - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 24
. FS level migration from a physical source DM to a destination VDM During a FS level migration from a physical source DM to a destination VDM, some additional manual steps are required in the process: 1. Create an interface (in the DOWN state) on the destination DM with the same interface name and - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 25
FS level migration 4. Export the FS and ensure that it is being exported from the destination VDM. For example, /fs1 on the source (physical DM) should be exported as /fs1 on the destination (VDM). 5. Create the FS level Migration and wait for the READY_TO_COMPLETE status. 6. Any time after the FS - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 26
for a subsequent VDM level migration on the same DM. Using the migrate_system_conf CLI command is optional. You can also migrate the system configurations manually. (VDM level migration only) Creating the migration plan (When creating a migration plan for VDM and the goal is to also migrate the - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 27
whether the source system configurations and services should be migrated to the destination DM migrate_system_conf, provided by VDM migration or manually. a. Because there are many necessary. If disaster recovery (DR) preservation support is required, specify this using the -dr option - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 28
VNX file migration process b. You can modify an existing migration plan based on your requirements. You can also view summary and detailed information about a specific migration plan or all migration plans in a destination system and delete an existing migration plan. 3. Create a migration Note: The - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 29
VNX file migration process replication sessions created by the migration are set to synchronize automatically by leveraging VNX Replicator. 4. Stop (Used to suspend the migration operation in order to delay it to another time or to fix an issue with the migration. The migration must be in a - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 30
VNX file migration process d. Once the VDM Migration is successfully completed: - The state of the source VDM changes from loaded to mounted, and any file systems associated with the migration are remounted on the source as read-only - The destination VDM is put into a loaded state and the - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 31
VNX file migration process to that migration because it is no longer available. Also, you cannot rollback the migration to have the source be active again after the Delete operation. a. Delete all VDM/FS replication sessions created by the migration, which also includes the deletion of internal - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 32
VNX file migration process Figure 6. VNX file migration process 32 Using VNX® File Migration Technical Notes - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 33
, see the Using VNX Replicator technical module. The complete set of EMC VNX customer publications is available on the EMC Online Support Website at http://support.emc.com. Figure 7 shows the architecture of a VDM level migration, which includes the migration of the vdm root_fs. The architecture of - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 34
VDM and FS replication sessions During the migration, the NAS clients can still access data from the source VDM. However, once the migration complete command has been issued, the network interfaces associated to the source VDM will be turned down. After the migration is completed successfully, the - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 35
because the interfaces must be deleted from the source before you initiate the Complete process of the migration, and then the interfaces must be manually created on the destination afterward. The estimated time for the Complete cutover step of a single FS on a VDM is approximately 60 seconds. Add - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 36
Planning for online and offline migration FS. In addition, the higher the rate of change per FS increases the cut over time. Table 2 lists the application environments under which VDM file migrations have been successfully tested and whether the migration is considered online or offline. Also, the - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 37
Planning for online and offline migration Hyper-V with SMB3 Checkpoints/FS: 5 to 10 Hyper-V servers: 2 FS: 2 Size of each FS: 1 TB Users/FS: 5 to 10 Checkpoints/FS: 5 to 10 NFS for Linux clients NFS clients: 2 FS: 2 Size of each FS: 1 TB Linux clients/FS: 5 to 10 Checkpoints/FS: 5 to 10 VNX 7.1 - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 38
Preparatory actions required for a VNX file migration Preparatory actions required for a VNX file migration The following preparatory actions must be completed before creating a VDM level migration plan, VDM level migration, or FS level migration: Ensure that VNX Replicator and Snapsure licenses - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 39
Preparatory actions required for a VNX file migration IP aliasing with Dual Control Stations If your VNX is configured with dual Control Stations, you must use the IP aliasing feature. If you do not, replications will not work if the primary Control Station fails over to the secondary Control - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 40
Preparatory actions required for a VNX file migration Note: For detailed information about the nas_cel and nas_config CLI commands, see the VNX Command Line Interface Reference for File. Bi-directional Control Station-to-Control Station communication You must establish the bi-directional trust - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 41
list of source and destination network interfaces available to a migration. You define the interface list by using IP addresses (IPv4) or name service interface names or a combination of both. How you specify an interface determines whether a migration later specifies the interface by interface name - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 42
interface names are not the same as VNX network device names (for example, cge0). Name service interface names are names that are resolved through a naming service (local host file, DNS, NIS, or LDAP). Bandwidth schedule - Allocates the interconnect bandwidth used on specific days, or specific - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 43
VNX offers flexibility in managing network storage based on the support environment and interface preferences. You can use the separate about using the VNX File Migration Tool, refer to the VNX File Migration Tool User Guide provided with the tool. You also can use the VNX OE for file CLI to - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 44
complete set of EMC VNX customer publications is available on the EMC Online Support Website at http://support.emc.com. EMC VNX Command Line Interface Reference for File Sets on VNX for File Security Configuration Guide for VNX System Operations 44 Using VNX® File Migration Technical Notes - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 45
, use the nas_license -list | -create [=] CLI command. For example, to install a license for the snapsure software package, type: $ nas_license -create snapsure Note: The key_code is supplied by EMC valid package_names: replicator and snapsure. After the licenses are enabled - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 46
Complete the preparatory actions for a VNX file migration single IP address regardless of whether the primary Control Station is running in slot 0 or slot 1. Note: For information about configuring IP aliasing using Unisphere, refer to the Unisphere online help. Create IP alias 1. Log in to the - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 47
Complete the preparatory actions for a VNX file migration # /nas/sbin/nas_config -IPalias -list For an IPv6 IP alias, use: # /nas/sbin/nas_config -IPalias -list6 Delete IP aliasing 1. To delete an IP alias using the script, type: For an IPv4 IP alias, use: # /nas/sbin/nas_config -IPalias -delete - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 48
Complete the preparatory actions for a VNX file migration The same 6-15 characters passphrase must be used for both source and destination systems. Set up bidirectional CS-to-CS trust relationship communication This section describes the process of establishing communication between source and - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 49
Complete the preparatory actions for a VNX file migration device = channel = net_path = 192.168.168.10 celerra_id = APM000420008170000 passphrase = nasadmin Example: To add an entry for the Control Station of the source legacy Celerra or VNX system, cs100, to the destination VNX system cs110, - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 50
Complete the preparatory actions for a VNX file migration 0 cs100 0 1 eng168123 201 3 eng16853 501 5 cs110 503 192.168.168.12 APM000340000680000 192.168.168.123 APM000437048940000 192.168.168.53 APM000183501737000 192.168.168.10 APM000446038450000 Note: The sample output shows that the - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 51
Complete the preparatory actions for a VNX file migration after you set it up from both sides. You configure only one interconnect between the same Data Mover pair. These tasks are required for VDM or File System migration. The interconnect between Data Movers is HTTPS in anonymous mode. This HTTPS - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 52
Complete the preparatory actions for a VNX file migration = name of the interconnect, use only alpha-numeric characters, spaces and special characters are not allowed = name of the Data Mover, first for the source side of the interconnect and then for the destination (peer) side - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 53
Complete the preparatory actions for a VNX file migration $ nas_cel -interconnect -create cs100_s2s3 -source_server server_2 destination_system cs110 -destination_server server_3 source_interfaces ip=192.168.52.136,ip=192.168.53.137,ip=192.168.168.138 destination_interfaces ip=192.168.52.146,ip=192. - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 54
destination interface list must also include an IPv6 address. 3. If no communication is established and you have verified that no other networking problems exist, add a routing entry to the source Data Mover's routing table to the specified destination and gateway address, using this command syntax - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 55
Once you have verified that communication between the Data Movers on the source and destination systems is in effect, you can migrate the global service configurations from a source legacy Celerra system or VNX system to a destination VNX system to facilitate a VDM migration. See Migrate the system - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 56
Table 1 for a list of the source and destination systems that are supported. Prerequisites Before you migrate a system configuration, you must complete the -source_user -source_mover -destination_mover -service {-all | {ldap|ftp|sftp|http|nis|dns|ntp|passwd| - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 57
source SSH user, and a hidden option -p can be specified, or by default you will be prompted for the password. -service: migrate different service types. For mover level configuration, specify "-all" to migrate all mover configurations, or list the configuration names separated by commas - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 58
system configurations Example of CLI output of the system configuration migration command for LDAP, DNS, and NIS services: # /nas/bin/migrate_system_conf ... -service ldap,dns,nis Check network connection started Check network connection...........succeeded Check DNS conflict started Check DNS - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 59
1 for a list of the source and destination systems that are supported. Note: The system does not track file system mount/unmount or interface attach/detach operations triggered by an administrator or data services after the migration plan is created. Only the file systems/interfaces - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 60
Create a VDM level migration plan Action The destination network devices are connected to the correct network. You have read and abide by the restrictions described in the section VDM level migration restrictions. To create a migration plan for a VDM level migration, use this command syntax: $ - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 61
interfaces on the destination DM with the identical names as those of the source interfaces before creating a migration. Also, configure the DNS server manually with the new VDM IP addresses on the destination. Note: Windows Server 2000 with dynamic DNS masks this change from your clients. When - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 62
: mapping of all source network devices associated to the source VDM onto network devices on the destination Data Mover. This mapping guides the migration to choose the correct network devices to be used when creating destination network interfaces when the -take_over_ips switch is specified - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 63
Result Create a VDM level migration plan -enforce_fsid: (optional) If specified, the IDs of the source file systems will be preserved on the destination system. If the IDs to be preserved have a conflict with those of the destination system (IDs already exist on the destination system), the - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 64
... succeeded Validate interconnect ... succeeded Validate source system licenses ... succeeded Validate system versions ... succeeded Validate I18N and CIFS service ... succeeded Validate source VDM ... succeeded Make migration plan for VDM ... succeeded Validate source file system(s) ... succeeded - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 65
View summary information of migration plan View summary information of migration plan You can view summary information of a specific migration plan or all migration plans in the destination system. Prerequisites None. Action To view summary information of a specific migration plan or all - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 66
View detailed information of migration plan View detailed information of migration plan You can view detailed information of a specific migration plan or all migration plans in the destination system. Prerequisites None. Action To view detailed information of a specific migration plan or all - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 67
View detailed information of migration plan Peer Data Mover Interconnect Data Mover Interconnect Source VDM Destination VDM Destination Pool (for VDM) File Systems Source Mover Destination Mover Read-Only User Checkpoints Excluded Takeover IP Addresses Interfaces - Devices Migrate DR Solutions Old - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 68
View detailed information of migration plan Destination VDM Replication ID Replication Type Replication Role Destination VDM Non-migrated DR Solutions fs1_rep_loopback, fs1_rep_local = vdm2_replica = 1384_BB0050562DDCB4_0000_364_BB0050562C7D9C_0000 = filesystem = source = vdm2_fs1 = N/A 68 Using - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 69
Modify a VDM level migration plan Modify a VDM level migration plan If required, you can modify an existing VDM level migration plan. Prerequisites The following conditions must exist before you modify a VDM level migration plan: The migration plan exists. The migration plan is not used by an - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 70
... succeeded Validate interconenct ... succeeded Validate source system licenses ... succeeded Validate system versions ... succeeded Validate I18N and CIFS service ... succeeded Validate source VDM ... succeeded Make migration plan for VDM ... succeeded Validate source file system(s) ... succeeded - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 71
Modify a VDM level migration plan Verify plan ... succeeded Save plan ... succeeded OK 71 Using VNX® File Migration Technical Notes - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 72
Delete a VDM level migration plan Delete a VDM level migration plan You can delete an existing VDM level migration plan. Prerequisites The following conditions must exist before you delete a VDM level migration plan: The migration plan exists. The migration plan is not used by an existing - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 73
See Table 1 for a list of the source and destination systems that are supported. The migration will include the VDM configuration and file systems mounted to the you intend to migrate the physical DM configuration (for example, global service configurations such as NTP, DNS, FTP, LDAP, and CAVA) to - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 74
migration Action Note: The system does not track file system mount/unmount or interface attach/detach operations triggered by an administrator or data services after the migration plan is created. Only the file systems/interfaces included in the migration plan are migrated. When there are new file - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 75
Result Create a VDM level migration -background: (optional) run the task in background. If specified, output related to the command operations will not appear at the console except for the task ID information, which will appear in the following format: Info 26843676673: In Progress: Operation is - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 76
Create a VDM level migration Create VDM Replication ... succeeded Initial Copy of VDM root file system [vdm1] ... succeeded Create destination file systems ... Create destination file systems: 1/2(updated per 2 minutes) Create destination file systems ... succeeded Create checkpoints ... Create - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 77
of time to complete. Note: After the Complete process ends and before a Delete process is initiated, manual roll back of a VDM or FS level migration is supported through a Service engagement (see Appendix B: Migration roll back). Prerequisites The following conditions must exist before you complete - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 78
Complete a migration Action Result Other migrations are not using the bandwidth for large data transfer (for example, during initial_copying, a refresh of a large delta during READY_TO_COMPLETE, or in the refresh stage of migration completion) To complete a migration, use this command syntax: $ - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 79
Complete a migration 1. Checks the migration state. 2. Changes the migration state to COMPLETING. 3. Checks for mismatched user checkpoints. 4. (VDM level migration only ) Checks the interfaces available on the destination mover. 5. Checks the VDM and FS status of a VDM level migration or the FS - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 80
Complete a migration $ nas_migrate -complete VdmMig_XYZ Info 26843676673: In Progress: Operation is still running. Check task id 2059 on the Background Tasks screen for results. Check migration state ... passed Change migration state to COMPLETING ... succeeded Check mismatched user checkpoints ... - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 81
Complete a migration - Duration: 1 mins 31 secs Restore checkpoint schedules on the destination ... succeeded Change migration state to COMPLETED ... succeeded OK Example CLI output of the complete command for a VDM level migration with -dr option: $ nas_migrate -complete VdmMig_XYZ -dr Info - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 82
Complete a migration Change migration state to COMPLETING ... succeeded Check mismatched user checkpoints ... passed Check file system status ... passed Cut over the migration Cut-over start time: 2014-02-26 03:28:21 - Reverse file system replications ... - Reverse file system succeeded Cut over - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 83
switch. Also, if there is an issue with the Complete process, do not use the -delete switch. In this case a manual roll back can be performed by an EMC support representative, but only when a delete has not been performed. Also, once you delete a migration, you cannot view the status information - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 84
Delete a migration Action Result To delete a migration, use this command syntax: $ nas_migrate -delete {|id=} [-background] Where: : name of migration session. : ID of migration session. -background: (optional) run the task in background. If specified, output - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 85
Delete a migration Check remote replication state ... succeeded Delete replication in parallel ... Delete replication task state: Total=2 Succeeded=0 Failed=0 Delete replication task state: Total=2 Succeeded=1 Failed=0 Delete replication task state: Total=2 Succeeded=1 Failed=0 Delete replication - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 86
Stop a migration Stop a migration During a migration, you may need to suspend its operation in order to delay it to a more convenient time or to fix an issue with the migration, or to save bandwidth in the event there are network issues. You can stop a migration whose state satisfies the following - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 87
Result Stop a migration Use the nas_task -i command to see the result of the task: succeeded, failed, or running. If not specified, the CLI will return the task progress until the task is complete. 1. System stops all the associated replication sessions. 2. The CLI will return the task - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 88
Start a migration Start a migration You may have stopped a migration to suspend its operation to a later time or to fix an issue with the migration, or to save network bandwidth. You can resume a migration that has been stopped providing that its state satisfies the following prerequisites. - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 89
Result Start a migration If not specified, the CLI will return the task progress until the task is complete. 1. System starts all the associated replication sessions. 2. The CLI will return the task progress until the task is complete (if no background flag is specified). The migration is now in - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 90
View summary information of migration View summary information of migration You can view summary information of all migrations in the destination system, or in the destination mover. Note: Once you delete a migration, you cannot view the status information related to that migration because it is - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 91
View summary information of migration STOP_FAILED | STARTING | STOPPED | START_FAILED | DELETING | DELETE_FAILED $ nas_migrate -list -id ID Name Type State Source Celerra/VNX Source VDM/FS Dest VDM/FS Network Status 20000010804 vdmMigEx1 VDM READY_TO_COMPLETE spring vdmEx1 vdmEx1 OK - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 92
View detailed information of migration View detailed information of migration You can view detailed information of a specific migration or all migrations in the destination system. Note: Once you delete a migration, you cannot view the status information related to that migration because it is no - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 93
View detailed information of migration Note: The migration states that can appear in the output are: CREATING | INITIAL_COPYING | INITIAL_COPY_FAILED | READY_TO_COMPLETE | COMPLETING | COMPLETE_FAILED | COMPLETED | STOPPING | STOP_FAILED | STARTING | STOPPED | START_FAILED | DELETING | - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 94
View detailed information of migration Migrate DR Solutions DR Solution State DR Solutions Replication ID Replication Type Replication Role Source FS Common Base Checkpoint Peer Common Base Checkpoint New DR #1: Replication ID Source FS Common Base Checkpoint FNM00124700250_2007 : Filesystem = Yes - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 95
View detailed information of migration Peer Data Mover Interconnect Data Mover Interconnect File Systems Source Mover Destination Mover Read-Only User Checkpoints Excluded Replications Migrate DR Solutions DR Solution State DR Solutions Replication ID Replication Type Replication Role Source FS - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 96
View detailed information of migration New DR #2: Replication ID Source FS Common Base Checkpoint Old DR #3: Replication ID Replication Type Replication Role Source FS Common Base Checkpoint Peer Common Base Checkpoint New DR #3: Replication ID Source FS Common Base Checkpoint = - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 97
. See Table 1 for a list of the source and destination systems that are supported for a FS level migration. A FS level migration is a non-transparent/offline a FS level migration: You have read and follow the instructions described in the section FS level migration. The preparatory actions - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 98
Create a FS level migration [-sav { id=|}] [-vdm ] -interconnect {|id=} [-checkpoint_excluded] [-dr] [-enforce_fsid] [-background] Where: : name of the migration session, unique per mover on - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 99
Result Create a FS level migration id=: specify the fsid of the existing FS as the destination. -pool: specify a storage pool to create the destination file system. -sav: (optional) use this option to specify the destination Sav Vol that will be used for all FS checkpoints (including - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 100
Create a FS level migration 2. The system prepares the destination product file systems and/or checkpoint file systems. 3. The system creates a FS level migration. 4. The CLI will return the task progress until the task is complete (if no background flag is specified). 5. To complete the migration, - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 101
's ID to search the Knowledgebase on EMC Online Support. After logging in to EMC Online Support, locate the applicable Support by Product page, and search for the error message. Log files The following log files are available to help troubleshoot VNX file migration. Additionally, you can use the - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 102
Appendix A: Troubleshooting sys_log webui/webui.log and webui/cli.log VNX file migration logs: migrate_server_conf.log mig_plan.log nas_log.al.mig nas_migrate.cli.log migration_utility.log (rollback - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 103
Appendix A: Troubleshooting cli.log messages The cli.log file contains start and end time log entries for a particular CLI replication operation. To view the cli.log messages - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 104
Movers that were down or experiencing errors during the -create, and restores them to service using the configuration required for Data Mover authentication. Network performance troubleshooting When you experience a performance issue during the transferring of data, check the following: Duplex - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 105
of the VDM or FS level migration, this function is supported through an EMC Professional Services engagement. Manual roll back of a VDM or FS migration Manual roll back consists of the following sequence: 1. Enable a migration to support roll back. 2. Roll back the migration. 3. Delete the migration - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 106
Appendix B: Migration roll back Note: When a migration is enabled to support roll back immediately after the Complete process is finished, the time it will take to rollback will be immediate; otherwise, the roll back time will - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 107
id 5046 on the Background Tasks screen for results. # nas_task -info 5046 Task Id = 5046 Celerra Network Server = vnx5400 Task State = Succeeded # nas_replicate -start id=199_FNM00130702660_2007_108_FNM00130702685_2007 -reverse -background Info 26843676673: In Progress: Operation is still - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 108
back a migration The amount of time it takes to roll back a migration depends on when the migration is enabled to support a roll back. If a migration is enabled to support roll back immediately after the Complete process is finished, the time it will take to rollback will be immediate. Otherwise, if - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 109
will need to be synchronized to the old source system. Preconditions The migration MUST have been enabled to support roll back (see Enable a VDM or FS level migration to support roll back). The migration MUST be in COMPLETED state. The replication sessions are in the following status on - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 110
Appendix B: Migration roll back vdm1 : fs1 on /fs1 uxfs,perm,rw fs2 on /fs2 uxfs,perm,rw On source CS: # server_mount vdm1 vdm1 : fs1 on /fs1 uxfs,perm,ro fs2 on /fs2 uxfs,perm,ro 2. Identify the interfaces in use by the destination VDM (VDM1 in this example): On destination CS: $ server_cifs - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 111
Appendix B: Migration roll back OK # nas_replicate -refresh id=196_FNM00130702660_2007_102_FNM00130702685_2007 OK 5. Place the interfaces on the destination VDM down: On destination CS: # server_ifconfig server_2 10-241-166-118 down server_2 : done 6. Perform a reverse for each Replication - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 112
following migration commands are workable: migration stop migration start migration complete migration delete Delete a Migration that is enabled to Support Roll back Preconditions The migration MUST be in COMPLETED state The replication sessions are in the following status on destination - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 113
{ | id= } [-background] Other considerations related to manual roll back Usermapper You do NOT need to re-configure Usermapper when you If you want to roll back all migrations on a destination DM and power off the destination DM, and the destination DM is the primary Usermapper, - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 114
or roll back. See Planning for online and offline migration for more information. Why do we run nas_migrate delete after we delete the replication sessions manually? To remove the migration entry from the migration DB in DART or VNX OE for file. How do you get the migrationId ? $ nas_migrate - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 115
Appendix B: Migration roll back If interfaces are taken over by the migration, you can get the interface list directly from the migration information. You do not need to consider interfaces for FS level migration. .reset_mig_state wrapper This tool should be deployed to the following path: /nas/ - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 116
Appendix B: Migration roll back command(s) succeeded Warning: Must check migration information to ensure the state was reset to READY_TO_COMPLETE successfully. [nasadmin@localhost lclhost]$ nas_migrate -l -id (Verify the migration state.) ID Name Type State Source Celerra/VNX Source VDM/FS Dest VDM - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 117
a usermapper roll back and runs the commands to roll back the usermapper service to the source system given the name or ID of the source system related password. Roll back script limitations The roll back script does not support background mode. You cannot set it to background using the -background - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 118
Appendix B: Migration roll back $ /nas/tools/migration_utility -migration vdmMig3001 -rollback Query information of migration (vdmMig3001) ... succeeded Rollback migration (vdmMig3001) ... Check pre-conditions ... Check migration state ... Check migration dr solution and state ... Check migration dr - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 119
Appendix B: Migration roll back Get read-only file systems ... - 2 Source File Systems to become read-only:fs3002, fs3003 Get read-only file systems ... succeeded Refresh replications ... - 4 Replication(s):MIGVDM_vdm3001_3001, MIGVDM_vdm3001_3002, MIGVDM_vdm3001_3003, MIGVDM_vdm3001_3004 Refresh - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 120
Appendix B: Migration roll back - Duration: 52 secs Set migration state(READY_TO_COMPLETE) ... Check migration state ... Check migration dr solution and state ... Check migration dr solution and state ... succeeded Check migration state ... succeeded Set migration state ... succeeded Check post- - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 121
Appendix C: Moving a CIFS server to a VDM from a physical Data Mover Appendix C: Moving a CIFS server to a VDM from a physical Data Mover The Virtual Data Mover (VDM) feature allows administrating CIFS servers inside a container including its own configuration and user file systems. The container, - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 122
. Active connections on the moved CIFS server will be stopped. EMC recommends that clients close the files before moving the CIFS server. The CIFS service must be started. Command description The move option of the server_cifs command allows moving a CIFS server from a data mover setup to a VDM - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 123
Appendix C: Moving a CIFS server to a VDM from a physical Data Mover server_cifs Unjoin compname=,domain=, admin= Step 2: The move operation. server_cifs move compname"netbios= Step 3: the server must - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 124
Appendix C: Moving a CIFS server to a VDM from a physical Data Mover Step 2: The move back operation. server_cifs move compname/netbios= Step 3: the server must be joined if the server is a compname, else go to step 4. server_cifs Join - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 125
Appendix D: FSID conflict after cycling through the FSID range Appendix D: FSID conflict after cycling through the FSID range Although the allocation of FSIDs in different ranges between source and destination systems is allowed while enforcing FSID preservation of a specific VDM or file system, a - Dell VNX5600 | Using VNX File Migration Technical Notes - Page 126
Appendix D: FSID conflict after cycling through the FSID range Copyright © 2013-2015 EMC Corporation. All Rights Reserved. EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. THE INFORMATION IN THIS PUBLICATION
-
1 -
2 -
3 -
4 -
5 -
6 -
7 -
8
-
9
-
10
-
11
-
12
-
13
-
14
-
15
-
16
-
17
-
18
-
19
-
20
-
21
-
22
-
23
-
24
-
25
-
26
-
27
-
28
-
29
-
30
-
31
-
32
-
33
-
34
-
35
-
36
-
37
-
38
-
39
-
40
-
41
-
42
-
43
-
44
-
45
-
46
-
47
-
48
-
49
-
50
-
51
-
52
-
53
-
54
-
55
-
56
-
57
-
58
-
59
-
60
-
61
-
62
-
63
-
64
-
65
-
66
-
67
-
68
-
69
-
70
-
71
-
72
-
73
-
74
-
75
-
76
-
77
-
78
-
79
-
80
-
81
-
82
-
83
-
84
-
85
-
86
-
87
-
88
-
89
-
90
-
91
-
92
-
93
-
94
-
95
-
96
-
97
-
98
-
99
-
100
-
101
-
102
-
103
-
104
-
105
-
106
-
107
-
108
-
109
-
110
-
111
-
112
-
113
-
114
-
115
-
116
-
117
-
118
-
119
-
120
-
121
-
122
-
123
-
124
-
125
-
126
 |
 |
1
Using VNX
®
File Migration
Technical Notes
P/N 300-014-344
REV 05
February, 2016
This technical notes document contains information on these topics:
VNX file migration overview
...................................................................
3
Migration of system configurations
......................................................
13
VDM level migration
...............................................................................
17
FS level migration
....................................................................................
21
VNX file migration process
....................................................................
26
VDM and FS replication sessions
..........................................................
33
Planning for online and offline migration
............................................
35
Preparatory actions required for a VNX file migration
......................
38
User interfaces
..........................................................................................
43
Related features and functionality information
...................................
44
Complete the preparatory actions for a VNX file migration
..............
45
Migrate the system configurations
........................................................
56
Create a VDM level migration plan
.......................................................
59
View summary information of migration plan
....................................
65
View detailed information of migration plan
......................................
66
Modify a VDM level migration plan
.....................................................
69
Delete a VDM level migration plan
.......................................................
72
Create a VDM level migration
...............................................................
73