Dell EMC Unity™ Family
Version 4.2
VNX® Series Data Import to Dell EMC Unity™ All Flash
or Hybrid, or UnityVSA™ System User Guide
302-003-062 REV 03
Copyright © 2016-2017 Dell Inc. or its subsidiaries. All rights reserved.
Published July 2017
Dell 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 IS PROVIDED “AS-IS.“ DELL MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND
WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. USE, COPYING, AND DISTRIBUTION OF ANY DELL SOFTWARE DESCRIBED
IN THIS PUBLICATION REQUIRES AN APPLICABLE SOFTWARE LICENSE.
Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be the property of their respective owners.
Published in the USA.
Dell EMC
Hopkinton, Massachusetts 01748-9103
1-508-435-1000 In North America 1-866-464-7381
www.DellEMC.com
2
Unity Family 4.2 VNX Series Data Import to Unity All Flash or Hybrid, or UnityVSA System User Guide
CONTENTS
Chapter 1
Introduction
5
About this document.................................................................................... 6
Additional resources..................................................................................... 6
About import................................................................................................ 7
Chapter 2
Import workflow
9
Configure import.........................................................................................10
NFS-only VDM import.................................................................... 10
CIFS-only VDM import................................................................... 12
Block import...................................................................................16
Configure a VDM or block import................................................... 17
Related concepts........................................................................... 18
Chapter 3
Considerations for import
21
Restrictions and limitations for NFS-only VDM file import .........................22
Restrictions and limitations for CIFS-only VDM file import ........................ 24
Block import restrictions and limitations.....................................................26
Chapter 4
Configure import using Unisphere
29
Configure protection and mobility interfaces..............................................30
Configure import connection.......................................................................31
Create an import session for file................................................................. 32
Manage import sessions for file.................................................................. 34
Create an import session for block............................................................. 35
Manage import sessions for block.............................................................. 36
Chapter 5
Configure import using the CLI
39
Create mobility interfaces.......................................................................... 40
Create remote system configurations......................................................... 41
View import sessions.................................................................................. 42
Create a NAS import session...................................................................... 43
View import sessions for file....................................................................... 49
Change import session settings for file.......................................................50
Cutover import session for file................................................................... 52
Commit import session for file....................................................................53
Cancel a NAS import session...................................................................... 54
Create a block import session.....................................................................55
View import sessions for block................................................................... 57
Change import session settings for block................................................... 58
Cut over import session for block............................................................... 59
Cancel a block import session.....................................................................59
View import session elements.....................................................................60
Chapter 6
Troubleshooting
63
Information related to import operation problems...................................... 64
VNX system with two Control Stations...................................................... 65
Unity Family 4.2 VNX Series Data Import to Unity All Flash or Hybrid, or UnityVSA System User Guide
3
CONTENTS
Appendix A
NFS-only VDM import details
67
NFS-only VDM import work flow................................................................68
Prerequisites for an NFS-only VDM import session....................... 68
Change settings of an NFS-only VDM import................................ 69
Start an NFS-only VDM import session......................................... 70
NFS-only VDM import initial copy..................................................70
NFS-only VDM import cutover....................................................... 71
NFS-only VDM import incremental copy........................................72
NFS-only VDM import commit.......................................................72
NFS-only VDM import pause......................................................... 72
NFS-only VDM import resume....................................................... 72
NFS-only VDM import cancel........................................................ 73
View NFS-only VDM import information..................................................... 73
File system mount options mapping............................................................ 74
NFS export options mapping...................................................................... 74
Appendix B
CIFS-only VDM import details
77
CIFS-only VDM import work flow............................................................... 78
Prerequisites for a CIFS-only VDM import session.........................78
Change settings of a CIFS-only VDM import................................. 80
Start a CIFS-only VDM import session.......................................... 80
CIFS-only VDM import initial copy................................................. 81
CIFS-only VDM import cutover......................................................83
CFS-only VDM import incremental copy........................................84
CIFS-only VDM import commit...................................................... 84
CIFS-only VDM import pause........................................................ 85
CIFS-only VDM import resume...................................................... 85
CIFS-only VDM import cancel....................................................... 85
View CIFS-only VDM import information.................................................... 86
Appendix C
LUN or Consistency Group of LUNs import details
87
LUN or Consistency Group of LUNs import work flow................................88
Prerequisites for a LUN or CG import session................................88
Start a LUN or CG import session..................................................89
LUN or CG import initial copy........................................................ 89
LUN or CG import cutover.............................................................90
4
Unity Family 4.2 VNX Series Data Import to Unity All Flash or Hybrid, or UnityVSA System User Guide
CHAPTER 1
Introduction
This chapter addresses the following topics:
l
l
l
About this document............................................................................................6
Additional resources.............................................................................................6
About import........................................................................................................ 7
Introduction
5
Introduction
About this document
This document provides information that you can use to configure and manage VNX
imports (migrations) on the Unity system. Along with relevant concepts and
instructions to configure VNX imports using the Unisphere GUI, this document also
includes information about the CLI commands that are associated with configuring
VNX imports.
Note
For more information about other Unisphere features or CLI commands, refer to the
Unisphere online help and Unisphere Command Line Interface User Guide.
Additional resources
As part of an improvement effort, revisions of the software and hardware are
periodically released. Therefore, some functions described in this document might not
be supported by all versions of the software or hardware currently in use. The product
release notes provide the most up-to-date information on product features. Contact
your technical support professional if a product does not function properly or does not
function as described in this document.
Where to get help
Support, product, and licensing information can be obtained as follows:
Product information
For product and feature documentation or release notes, go to Unity Technical
Documentation at: www.emc.com/en-us/documentation/unity-family.htm.
Troubleshooting
For information about products, software updates, licensing, and service, go to Online
Support (registration required) at: https://Support.EMC.com. After logging in, locate
the appropriate Support by Product page.
Technical support
For technical support and service requests, go to Online Support at: https://
Support.EMC.com. After logging in, locate Create a service request. To open a
service request, you must have a valid support agreement. Contact your Sales
Representative for details about obtaining a valid support agreement or to answer any
questions about your account.
Special notice conventions used in this document
DANGER
Indicates a hazardous situation which, if not avoided, will result in death or
serious injury.
WARNING
Indicates a hazardous situation which, if not avoided, could result in death or
serious injury.
6
Unity Family 4.2 VNX Series Data Import to Unity All Flash or Hybrid, or UnityVSA System User Guide
Introduction
CAUTION
Indicates a hazardous situation which, if not avoided, could result in minor or
moderate injury.
NOTICE
Addresses practices not related to personal injury.
Note
Presents information that is important, but not hazard-related.
About import
The Import feature allows you to migrate a VDM, or a LUN or a consistency group
(CG) of LUNs, with its configuration and data from an existing source VNX storage
system to a target Unity storage system. This feature provides a built-in capability for
NFS-only VDM imports with minimal or no disruption to clients. It also provides a builtin capability for CIFS-only VDM and block-based imports. However, cutting over of a
CIFS-only VDM or a block import session can be a disruptive process.
For a block-based import, after the cutover completes, host I/O operations are
switched to the target system and the import process completes automatically. For a
file-based virtual data mover (VDM) import, after cutover completes, the import
process does an incremental copy automatically but you must complete the import
manually.
An import is always conducted from the Unity storage system. The target system
makes a remote call to the VNX storage system and instigates a pull (for file-based
import) or push (for block-based import) of the source storage resources to the
target system.
About import
7
Introduction
8
Unity Family 4.2 VNX Series Data Import to Unity All Flash or Hybrid, or UnityVSA System User Guide
CHAPTER 2
Import workflow
This chapter addresses the following topics:
l
Configure import................................................................................................ 10
Import workflow
9
Import workflow
Configure import
You can manually import a VDM (including all its associated file-based storage,
network, and configuration information and file systems) from a VNX storage system
to a Unity storage system.
VDM import operations support only:
l
Import of VDM with only NFSV3 protocol enabled (VDMs with NFSV4 protocol
enabled are not supported)
l
Import of VDM with only CIFS protocol enabled
NOTICE
Import of a VDM with multiprotocol file systems, or with both NFS and CIFS file
systems exported/shared, is not supported.
You can also import multiple concurrent block import sessions for LUNs, or
Consistency Group (CG) of LUNs, from the VNX system to the Unity system.
NFS-only VDM import
The configuration and identity information that can be imported along with the data as
part of a NFS-only VDM import include:
l
l
l
Networking:
n
IP address configuration
n
Routing configuration
n
VLAN configuration
Name Services:
n
DNS
n
LDAP
n
Local files
n
NIS
NFS server identity:
n
l
10
NFS exports
Data:
n
File systems (including quota configuration)
n
Security or permissions for NFSv3
Unity Family 4.2 VNX Series Data Import to Unity All Flash or Hybrid, or UnityVSA System User Guide
Import workflow
Note
When the domain configuration is disabled for the source VDM, only the first DNS
domain that is configured on the physical Data Mover which is hosting the VDM is
imported. If the intended DNS domain for the source VDM is not the first one on the
physical Data Mover, the wrong DNS configuration is imported. To avoid importing the
wrong DNS domain, enable the Name Service configuration on the source VDM by
using the server_nsdomains CLI command on the source VNX. Use this command
to enable and set the DNS, LDAP, or NIS configuration on the source VDM to ensure
proper import to the Unity system.
Source VNX VDM Servers, along with their respective file systems (UFS32-based file
systems), are migrated to the new UFS64-based file systems format on the target
Unity system. In addition, all file systems are migrated as Thin. File systems cannot be
migrated individually, only as part of the VDM server migration.
For a file system that is used by VMware as an NFS data store, you must specify the
file systems to be imported as a VMware NFS data store. Only one NFS export at file
system root directory should exist on the VNX for those source file systems.
Otherwise, both create session and resume session operations fail because VMware
NFS data store in Unity only supports this export configuration.
The target file system is a normal file system by default. If you specify one file system
to be imported as a VMware NFS data store, the target file system is VMware NFS
data store, which enables virtualization specific optimization such as asyncmtime. A
source file system that is specified as file level retention (FLR) enabled cannot be
imported as a VMware data store file system.
Prerequisites for NFS-only VDM import
Import of a VDM and its related file systems from a VNX storage system to a Unity
storage system requires the following prerequisites:
l
Time is synchronized between the VNX and Unity storage systems. The time
difference must be within five seconds. Use the same NTP server on the VNX
Data Mover that hosts the source VDM, as well as the target Unity SPs. Refer to
Configuring Time Services on VNX for information about NTP.
l
One or more pools must be created and available on the target Unity system to
perform a VDM import operation. The pools that are selected should be large
enough to hold the source VDM and all its file systems that are migrated.
Note
Compressed data is uncompressed and deduped data is undeduped for migration.
Therefore, ensure that the target pool has enough capacity to handle these
changes in data size. Check on the source VNX for the amount of space savings
compression and deduplication provide for the data, then determine how much
space would be required for the uncompressed and undeduped data.
l
Before creating an import connection, you must configure mobility interface IP
address for each SP (A and B) of the target system. (When creating an import
session, you select the mobility interface IP address of either SPA or SPB to use
as the target import interface. This interface is used to migrate the VNX CIFS
server and file systems.)
l
Before creating the VDM import session, you must do the following:
n
Create a migration interface on the source Data Mover (for IPv4, use
server_ifconfig <server_name> -create -Device <device> name <nas_migration_interface_name> -protocol IP <ipv4>
NFS-only VDM import
11
Import workflow
<ipnetmask> <ipgateway> ; for IPv6, use server_ifconfig
<server_name> -create -Device <device> -name
<nas_migration_interface_name> -protocol IP6 <ipv6/
PrefixLength>) and attach the interface to the source VDM to be migrated
(using nas_server -vdm <vdm_name> -attach
<nas_migration_interface_name>). The interface added on the source
VDM to perform migration must be named with the prefix "nas_migraiton_" so
that the interface can be clearly identified by the migration process. This
interface is used only for the VDM import operation and must not be used as a
production interface. After each VDM import session is committed, this
interface can be re-used by attaching it to the next VDM, and so on.
n
Verify that the physical Data Mover on which the source VDM is located has at
least one IP interface configured that is not attached to the VDM being
migrated. This IP interface ensures that the source Data Mover can provide
uninterrupted Name Services for the remaining file servers. If this additional
interface is not present, the VDM import session fails.
l
For a source VNX system with two Control Stations, the home directory of a user
with the Administrator role, which is used in configuring the import connection,
must exist on the primary Control Station of the VNX. A system administrator user
has. For more information, see VNX system with two Control Stations on page
65.
l
Before conducting a VDM import, an import connection must be created between
the source VNX system and the target Unity system.
Note
If the naming services server (DNS, NIS, or LDAP) configured on the Data Mover of
the source VNX cannot be connected using the network interface that is attached to
the VDM to be migrated, attach another interface to the VDM. This additional
interface ensures that the VDM can connect to the naming services server.
Otherwise, the target NAS server cannot connect to the naming services server. If the
naming services server configured on the Data Mover of the source VNX can only be
connected using the network interface that is attached to the VDM to be migrated,
create another network interface on the Data Mover. This additional network interface
ensures that the Data Mover can connect to the naming services server. Otherwise,
other clients of the Data Mover cannot connect to the naming services server.
CIFS-only VDM import
The configuration and identity information that can be imported along with the data as
part of a CIFS-only VDM import include:
l
l
Networking:
n
IP address configuration
n
Routing configuration
n
VLAN configuration
Name Services:
n
l
CIFS server identity:
n
12
DNS
Name
Unity Family 4.2 VNX Series Data Import to Unity All Flash or Hybrid, or UnityVSA System User Guide
Import workflow
l
l
n
Active Directory (AD) account
n
CIFS shares
n
Local group
n
Local users
VDM settings:
n
parameters
n
quota
Data:
n
File systems
n
File security (Access Control List (ACL) preservation)
n
Timestamps (create date and last modification date are not modified during
import)
Note
When the domain configuration is disabled for the source VDM, the domain name of
the SMB server is used to search the corresponding DNS configuration. If the
configuration cannot be found, the migration cannot start. Enable the domain
configuration for the VDM by using the server_nsdomains CLI command. Use this
command to enable and set the DNS, LDAP, or NIS configuration on the source VDM
to ensure proper import to the Unity system.
Source VNX VDM Servers, along with their respective file systems (UFS32-based file
systems), are migrated to the new UFS64-based file systems format on the target
Unity system. In addition, all file systems are migrated as Thin and maintained as Thin
on the target Unity system. File systems cannot be migrated individually, only as part
of the VDM server migration.
Prerequisites for CIFS-only VDM import
Import of a CIFS-only VDM and its related file systems from a VNX storage system to
a Unity storage system requires the following prerequisites:
l
Time is synchronized between the VNX and Unity storage systems. The time
difference must be within five seconds. Use the same NTP server on the VNX
Data Mover that hosts the source VDM, as well as the target Unity SPs. Refer to
Configuring Time Services on VNX for information about NTP.
l
One or more pools must be created and available on the target Unity system to
perform a VDM import operation. The pools that are selected should be large
enough to hold the source VDM and all its file systems that are migrated.
Note
Compressed data is uncompressed and deduped data is undeduped for migration.
Therefore, ensure that the target pool has enough capacity to handle these
changes in data size. Check on the source VNX for the amount of space savings
compression and deduplication provide for the data, then determine how much
space would be required for the uncompressed and undeduped data.
l
Before creating the VDM import session, you must do the following:
n
Create a migration interface on the source Data Mover (for IPv4, use
server_ifconfig <server_name> -create -Device <device> -
CIFS-only VDM import
13
Import workflow
name <nas_migration_interface_name> -protocol IP <ipv4>
<ipnetmask> <ipgateway> ; for IPv6, use server_ifconfig
<server_name> -create -Device <device> -name
<nas_migration_interface_name> -protocol IP6 <ipv6/
PrefixLength>) and attach the interface to the source VDM to be migrated
(using nas_server -vdm <vdm_name> -attach
<nas_migration_interface_name>). The interface added on the source
VDM to perform migration must be named with the prefix "nas_migraiton_" so
that the interface can be clearly identified by the migration process. This
interface is used only for the VDM import operation and must not be used as a
production interface. After each VDM import session is committed, this
interface can be re-used by attaching it to the next VDM, and so on.
n
Verify the following:
– The physical Data Mover on which the source VDM is located has at least
one IP interface configured that is not attached to the VDM being migrated.
This IP interface ensures that the source Data Mover can provide
uninterrupted Name Services for the remaining file servers. If this additional
interface is not present, the VDM import session fails.
– (For a source VDM with an AD joined CIFS server only) The migration
interface has been added to the source CIFS server and has a prefix for a
DNS domain that is different from the production interface. To add this
interface when in a DNS zone, use the following command format:
server_cifs <vdm_name> -add
compname=<compname>,domain=<domainname>,if=<nas_migrati
on_interface>,dns=<specific_prefix.domainname>. This
command creates an additional zone in the DNS server for hosting the
migration IP address. This action ensures that the migration interface will
not be used for production. For more information about CLI commands
related to the source system, refer to the VNX Command Line Interface
Reference for File.
– A single CIFS server is configured on the source VDM.
– C$ share is available on the source Data Mover that hosts the VDM and is
not disabled or set to Read-only. The C$ share must be available, otherwise
the import cannot start. If it was disabled or Read-only on the source,
change the corresponding parameters to enable it:
server_param <source_server> -facility cifs -modify
admin.shareC_NotCreated -value 0
server_param <source_server> -facility cifs -modify
admin.shareC_RO -value 0
NOTICE
You must stop and start the service associated with the CIFS facility for
changes to admin.shareC_NotCreated to take effect.
– No NFS exports are configured on the source VDM file systems.
– Local CIFS users are enabled on the source CIFS server. (For AD joined
CIFS servers only) When not enabled, to enable local users on the source
14
Unity Family 4.2 VNX Series Data Import to Unity All Flash or Hybrid, or UnityVSA System User Guide
Import workflow
CIFS server use server_cifs <vdmname> -add
compname=<computername>,domain=<domainname>,local_users.
Refer to Configuring and Managing CIFS on VNX for more information about
enabling local user support on VNX.
– A local user that is a member to the local administrator group of the source
CIFS server must exist on the source CIFS server. This user must have
backup and restore privileges (by default, being a member of the
administrators local group would be enough). Refer to Configuring and
Managing CIFS on VNX for information about local user and group accounts.
– Credentials, username and password, of the remote local CIFS user to use
for the import.
– The extended acl feature is enabled on the source Data Mover that hosts
the VDM (parameter cifs.acl.extacl should have bits 2, 3, and 4 set, decimal
value 28). Use the following command to view the settings:
server_param <source_datamover> -facility cifs -info
acl.extacl
If necessary, use the following command to change the setting:
server_param <source_datamover> -facility cifs -modify
acl.extacl -value 28
– Unknown SID feature has been enabled on the source Data Mover that
hosts the VDM (parameter cifs.acl.mappingErrorAction must be set to
0x0b, decimal value 11). Use the following command to view the settings:
server_param <source_datamover> -facility cifs -info
acl.mappingErrorAction
If necessary, use the following command to change the setting:
server_param <source_datamover> -facility cifs -modify
acl.mappingErrorAction -value 11
– NT security is enabled on the source. Share and Unix security level is not
supported. This is in mount options of the file systems. If necessary, change
the mount option of the file systems.
– The source VDM is not utf8-based.
– The source CIFS server is not a Windows NT 4.0 like CIFS server.
– DNS is configured for the windows domain in the case of a domain joined
CIFS server.
– Other VDMs from the source can reach DNS and domain controller (DC)
after cutover.
– DNS and DCs are reachable on the destination after cutover.
l
For a source VNX system with two Control Stations, the home directory of a user
with the Administrator role, which is used in configuring the import connection,
must exist on the primary Control Station of the VNX. For more information, see
VNX system with two Control Stations on page 65.
l
Before creating an import connection, you must configure a mobility interface IP
address for each SP (A and B) of the target system. (When creating an import
CIFS-only VDM import
15
Import workflow
session, you select the mobility interface IP address of either SPA or SPB to use
as the target import interface. This interface is used to migrate the VNX CIFS
server and file systems.)
l
Before conducting a VDM import, an import connection must be created between
the source VNX system and the target Unity system.
n
If the naming services server (DNS) configured on the Data Mover of the
source VNX cannot be connected using the network interface that is attached
to the source VDM, attach another interface to the VDM. This additional
interface ensures that the source VDM can connect to the naming services
server.
n
If the naming services server can only be connected using the network
interface that is attached to the source VDM, create another network interface
on the Data Mover. This additional network interface ensures that the Data
Mover can connect to the naming services server as well as other clients of the
Data Mover.
Block import
Unisphere allows you to import multiple concurrent block import sessions for either
LUNs or Consistency Group (CG) of LUNs, from the VNX system to the Unity system.
This limit is based on the SAN Copy limits of the source VNX system and is also based
on the number of members in each CG. Block import uses the SAN Copy feature on
the VNX storage system to push data to the Unity storage system. Use the VNX
management IP address and VNX Admin credentials to configure a remote system
connection from the target Unity system to the source VNX system. The VNX SAN
Copy FC or iSCSI initiators is discovered through this connection and the Unity
system is registered as a SANCopy host. Also, all block resources that are eligible for
import are discovered, which includes:
l
l
Pool LUNs, Thin LUNs, and Meta LUNs that are:
n
Not reserved LUN pool LUNs
n
Not LUNs exposed to VNX file
n
Not System LUNs
CGs of LUNs
Before you perform an import of a LUN or CG of LUNs, the reserved LUN pool (RLP)
on the source VNX system should contain at least one free LUN for each LUN planned
for import. Each reserved LUN can vary in size. However, using the same size for each
LUN in the pool is easier to manage because the LUNs are assigned without regard to
size. That is, the first available free LUN in the global reserved LUN pool is assigned.
Since you cannot control which reserved LUNs are being used for a particular import
session or a VNX process such as SnapView™, incremental SAN Copy, or
MirrorView/A, use a standard size for all reserved LUNs. To assist in estimating a
suitable reserved LUN pool size for the storage system, consider the following:
16
l
If you want to optimize space utilization, use the size of the smallest source LUN
as the basis of the calculations. If you want to optimize the total number of source
LUNs, use the size of the largest source LUN as the basis of the calculations.
l
If you have a standard online transaction processing configuration (OLTP), use
reserved LUNs sized at 10-20%. This size tends to be appropriate to
accommodate the copy-on-first-write activity.
l
If you are also using SnapView or MirrorView/A on the VNX LUN, then you may
need additional RLP LUNs.
Unity Family 4.2 VNX Series Data Import to Unity All Flash or Hybrid, or UnityVSA System User Guide
Import workflow
NOTICE
If free reserved LUNs are not available in the RLP, the import session enters an error
state. Add space to the RLP, after which the session can resume. The additional space
does not have to be as high as the number of source LUNs. The RLP LUNs get re-used
once an import session completes.
For more information about the RLP and reserved LUNs, refer to the Unisphere online
help on the source VNX.
Block import prerequisites
The preparation for block import (either LUN or CG of LUNs) is different than the
preparation for file-based (VDM) import. Import of one or more LUNs or a CG of LUNs
from a VNX storage system to a Unity storage system requires the following
prerequisites:
l
SAN Copy is enabled on the VNX storage system
l
For FC-based import:
n
l
Ports zoning is configured between the VNX and Unity storage systems.
For iSCSI-based import:
n
iSCSI interfaces are configured on both the VNX and Unity storage processors.
n
From the VNX storage system - iSCSI IP connections are configured between
the source VNX SPs and target Unity SPs as pairs. For example, VNX SPA is
paired to Unity SPA and VNX SPB is paired to Unity SPB. Also, verify the
connection configuration.
l
A reserved LUN pool (RLP) is configured with LUNs based on LUNs planned for
the import. Refer to the existing VNX Unisphere online help for detailed
information concerning RLP.
l
Hosts are configured on the Unity storage system the same as block hosts or
storage groups on the source VNX storage system from which resources are
imported. If needed, you can reconfigure host access on the Unity system.
Note
Do not use ports that are used by MirrorView for either FC-based or iSCSI-based
import.
Configure a VDM or block import
To configure import for block or file storage resources, use the native Import feature
in Unisphere. Complete the following steps:
1. Configure the mobility (import) interfaces on each SP of the target systems.
Note
Although these interfaces are needed only for importing a VDM and its related file
systems, if you use the same import connection for both file and block import
sessions, the interfaces must be configured.
2. Configure an import connection.
3. Create an import session for the storage resource.
Configure a VDM or block import
17
Import workflow
Note
The interfaces are only required for file import operations, and not for block imports.
Related concepts
About protection and mobility interfaces
Protection and mobility interfaces may be shared network interfaces for replicationrelated and import data or management traffic using the virtual management port.
Each storage processor (SP) must have one or more interfaces. Although import only
requires one interface, the creation of an interface on both SPA and SPB is enforced.
When you create a VDM import session, the VDM-to-Unity SP interfaces are paired
up. Configure these interfaces before you create an associated connection. Interfaces
are needed only for the import of a VDM and its file systems.
Note
The import connection cannot use the replication (MirrorView) interfaces on the VNX.
From a replication perspective, if an interface is shared between replication and
import, you must remove all import sessions to change the interface and remove both
replication and import sessions before deleting the interface.
About import connections
Import requires a configured connection between the source system and target
system. This connection is called an import connection. An import connection handles
either a block import or a VDM and its file systems import.
On the target Unity system, connections must be defined separately for replication
and import but Interfaces can be shared between replication and import. Import
connections are not verified until the session is created
For block, the initiators must be pushed from the VNX (VNX1 or VNX2) source system
to the Unity target system.
Note
Before creating a mobility interface or import connection for a VNX import, configure
the FC zoning when an FC connection is used for block import. If the connection uses
iSCSI, an iSCSI connection is required between the source VNX system to the target
Unity system.
Once an import connection is created, the Unity target system automatically discovers
both file and block resources on the source system.
Note
The SAN Copy Enabler must be installed on the VNX1 storage system so that block
resources on the system can be discovered automatically. Otherwise, only the file
resources are discovered when the import connection is created. VNX2 storage
systems include the SAN Copy Enabler already installed.
18
Unity Family 4.2 VNX Series Data Import to Unity All Flash or Hybrid, or UnityVSA System User Guide
Import workflow
About import sessions
An import session uses a configured import connection and associated interfaces to
establish an end-to-end path for importing data between the source and target
storage resources. The basic operations for an import session are:
1. Create
2. Resume or Pause
3. Cutover
4. Commit
5. Cancel
Note
For a block import session, the commit operation is performed automatically at the
end of cutover.
You can cancel an import session that is in any state (with the exceptions of
Canceling, Canceled, or Cutting Over) before the commit state. For a VDM (either
NFS or CIFS) import session, the cancel operation rolls back the VDM and related file
systems to the source VNX. The cancel operation also deletes the target file systems.
If no file systems exist on the NAS server, the cancel operation deletes the NAS
server. For a LUN or consistency group (CG) import session, the cancel operation
deletes the SAN Copy session for each set of LUN pairs in the import session. It also
disables SAN Copy access to the target LUNs and deletes the target LUNs or CG
associated with the import session.
NOTICE
You cannot upgrade a Unity system when an import session is in progress or create an
import session when an upgrade session is in progress.
Related concepts
19
Import workflow
20
Unity Family 4.2 VNX Series Data Import to Unity All Flash or Hybrid, or UnityVSA System User Guide
CHAPTER 3
Considerations for import
This chapter addresses the following topics:
l
l
l
Restrictions and limitations for NFS-only VDM file import ................................ 22
Restrictions and limitations for CIFS-only VDM file import ................................24
Block import restrictions and limitations............................................................ 26
Considerations for import
21
Considerations for import
Restrictions and limitations for NFS-only VDM file import
The following restrictions and limitations relate to a NFS-only VDM file migration from
either a VNX1 or VNX2 storage system to a Unity storage system:
l
Only Unified VNX (VNX1 and VNX2) storage systems are supported as the source
storage system in a VDM file migration.
l
The source VNX1 OE is 7.1.x or later or the source VNX2 OE is 8.1.x or later.
l
Upgrading a Unity system when an import session is in progress is not supported.
l
Creating an import session when an upgrade session is in progress is not
supported.
l
Unity supports a VDM import session with at most 500 file systems on the source
VDM. UnityVSA supports a VDM import session with at most 32 file systems on
the source VDM.
l
The target pool size may be larger than the pool size of the source VDM and its
migrated file systems.
n
Unity storage systems use a different file system layout than Unified VNX
storage systems. Unity storage systems use UFS64 file systems while VNX
storage systems use UFS32 file systems.
n
Import of dedupe settings is not supported.
n
A versioning file and fast clone are imported as a normal file. Also, a source file
system with file level retention (FLR) is imported as a normal target file system
(UFS64).
l
Only uxfs-type file systems are imported from the VNX1 or VNX2 source VDM.
Import of non-uxfs-type file systems or file systems that are mounted on a Nested
Mount File System (NMFS) file system are not supported.
l
A file system whose mount path contains more than two slashes is not supported.
The target system does not allow file systems with a name containing multiple
slashes, for example, /root_vdm_1/a/c.
l
Import of a file system that is participating in a replication is not supported.
l
Import of a checkpoint or checkpoint schedule is not supported.
l
Restrictions that are related to Quota migration:
l
l
n
Import of group quota or inode quota settings is not supported. (The target
system does not support either.)
n
Import of a tree quota whose path contains single quotation marks is not
supported. (A VNX1 or VNX2 system can create it but it cannot be queried or
modified.)
A VAAI operation is not allowed on either the source or target systems during and
after cutover.
n
A VAAI operation is not allowed on the target system before cutover.
n
A VAAI operation on the source system must finish before cutover.
Limitations that are related to Host access:
n
22
After cutover, read access performance degrades until the related file is
migrated.
Unity Family 4.2 VNX Series Data Import to Unity All Flash or Hybrid, or UnityVSA System User Guide
Considerations for import
n
After cutover, write access performance degrades until the VDM file migration
is completed.
n
After cutover, a host cannot write data when the source file system is in the
read-only mounted state.
n
After cutover, a host cannot access data when the target system's mobility
interface cannot access the source file system, which includes the following
cases:
– The network between the source VDM file migration interface and the
target mobility interface is disconnected.
– The source VDM is not in either the loaded or mounted state.
– The user modifies the source export, which makes the target system's
mobility interface unable to access the source file system.
l
l
l
Protocol restrictions:
n
Import of CIFS and multi-protocol settings and related settings is not
supported. For example, CIFS server, CIFS share path and options, Kerberos
key, CAVA (Common AntiVirus Agent), usermapper, and ntxmap.
n
Import of a VDM using Secure NFS, NFSv4, or pNFS is not supported.
n
Import of FTP or SFTP (File Transfer Protocol), HTTP (Hyper Text Transfer
Protocol), or CEPP (Common Event Publishing Protocol) is not supported.
Rollback restrictions and limitations:
n
After rollback, a host may need to remount the NFS file system if interfaces
configurations are different between the source VDMs and the target NAS
Servers.
n
Only rollback data changes to the source file systems. Rollback of any
configuration changes to the NAS server/file systems on the target storage
system is not supported. For example, if you add an NFS export to a file
system, a rollback does not add the new NFS export to the source VNX1 or
VNX2 storage system.
Configuration restrictions and limitations:
n
Import of NTP configuration is not supported.
n
Import of server parameter settings (VNX1 or VNX2 server_param settings
with the exception of the IP reflect parameter) is not supported.
n
Import of LDAP configuration with Kerberos authentication (CIFS server is not
migrated) is not supported.
n
Import of client certificates, which the LDAP server requires (persona is not
supported on the Unity system), is not supported.
n
Import of customized cipher list for LDAP connection (customized cipher list is
not supported on the Unity system) is not supported.
n
If multiple LDAP servers are configured with different port numbers that are
used by the source VDM, only the server with the port number equal to the
first server is migrated.
n
If both NIS and LDAP are configured and taken into effect for the naming
service on the source VDM, you must select one of them to take effect on the
target NAS server.
n
If local files are configured and taken into effect for the naming service on the
source VDM, you can select whether the local files take effect on the target
Restrictions and limitations for NFS-only VDM file import
23
Considerations for import
NAS server. The search order of the local files is always higher than NIS or
LDAP on the target NAS server.
n
Only enabled network interfaces on the source VDM are imported. Disabled
network interfaces on the source VDM are not imported. (The target system
does not allow you to enable or disable network interfaces.)
n
Many of the mount options for VNX storage systems are not supported on
Unity storage systems. Refer to File system mount options mapping on page
74 for information about the options that Unity supports.
n
Some of the NFS export options for VNX storage systems are not supported
on Unity storage systems. See NFS export options mapping on page 74 for
information about the options that Unity supports.
n
File Level Retention (FLR) file systems can be imported optionally. However,
Unity systems do not support FLR so those file systems are imported as normal
file systems (UFS64).
n
Distributed Hierarchical Storage Management (DHSM)/(Cloud Tiering
Appliance (CTA) may be configured on the source VNX for archiving inactive
files to secondary storage. If DHSM/CTA is configured on the source VNX
system and a VDM import to Unity is run, all the files on the associated file
system are recalled from the secondary storage to the source VNX. Those files
are then imported to Unity as normal files (that is, no stub files are imported).
l
Only limited configuration changes to the source VDM and the target NAS server
are supported. Refer to Change settings of an NFS-only VDM import on page 69
for information about what changes can be made and when.
l
Restoring NDMP backups:
n
The NDMP backup path on VNX is /root_vdm_xx/FSNAME while the same
path on Unity is /FSNAME. If any file system of the source VNX VDM is
protected by NDMP and already backed up, then after VDM file import, those
file systems cannot be restored to Unity using the original path option. A
restore using the original path option fails due to an unavailable destination
path. Instead, use the alternative path option.
Restrictions and limitations for CIFS-only VDM file import
The following restrictions and limitations relate to a CIFS-only VDM file migration from
either a VNX1 or VNX2 storage system to a Unity storage system:
24
l
Only Unified VNX (VNX1 and VNX2) storage systems are supported as the source
storage system in a VDM file migration.
l
The source VNX1 OE is 7.1.x or later or the source VNX2 OE is 8.1.x or later.
l
Upgrading a Unity system when an import session is in progress is not supported.
l
Creating an import session when an upgrade session is in progress is not
supported.
l
Unity supports a VDM import session with at most 500 file systems on the source
VDM. UnityVSA supports a VDM import session with at most 32 file systems on
the source VDM.
l
The target pool size must be large enough to host the source VDM and its
migrated file systems.
Unity Family 4.2 VNX Series Data Import to Unity All Flash or Hybrid, or UnityVSA System User Guide
Considerations for import
n
Unity storage systems use a different file system layout than Unified VNX
storage systems. Unity storage systems use UFS64 file systems while VNX
storage systems use UFS32 file systems.
n
Import of dedupe settings is not supported. During the import session, data is
un-deduped and un-compressed.
n
A versioning file and fast clone are imported as a normal file. Also, a source file
system with file level retention (FLR) is imported as a normal target file system
(UFS64).
l
Only uxfs-type file systems are imported from the VNX1 or VNX2 source VDM.
Import of non-uxfs-type file systems or file systems that are mounted on a Nested
Mount File System (NMFS) file system are not supported.
l
A file system whose mount path contains more than two slashes is not supported.
The target system does not allow file systems with a name containing multiple
slashes, for example, /root_vdm_1/a/c.
l
Import of a file system that is participating in a replication is not supported.
l
Import of a checkpoint or checkpoint schedule is not supported.
l
Restrictions that are related to Quota migration:
l
n
Import of group quota or inode quota settings is not supported. (The target
system does not support either.)
n
Import of a tree quota whose path contains single quotation marks is not
supported. (A VNX1 or VNX2 system can create it but it cannot be queried or
modified.)
Limitations that are related to Host access:
n
After cutover, read access performance degrades until the related file is
migrated.
n
After cutover, write access performance degrades until the VDM file migration
is completed.
n
After cutover, a host cannot write data when the source file system is in the
read-only mounted state.
n
After cutover, a host cannot access data when the target system's mobility
interface cannot access the source file system, which includes the following
cases:
– The network between the source VDM file migration interface and the
target mobility interface is disconnected.
– The source VDM is not in either the loaded or mounted state.
– The user modifies the source export, which makes the target system's
mobility interface unable to access the source file system.
l
l
Protocol restrictions:
n
Import of NFS settings and related settings is not supported. For example,
LDAP, NIS, local password, group and netgroup files, mount options other than
synchronous write, op locks, notify on write, and notify on access.
n
Import of FTP or SFTP (File Transfer Protocol), HTTP (Hyper Text Transfer
Protocol), or CEPP (Common Event Publishing Protocol) is not supported.
Cancel restrictions and limitations:
Restrictions and limitations for CIFS-only VDM file import
25
Considerations for import
n
l
l
Only some configuration changes, such as the target VDM's CIFS shares, or
local users along with data changes to the source file systems are rolled back
to the source VDM.
Configuration restrictions and limitations:
n
Import of NTP configuration is not supported.
n
Only enabled network interfaces on the source VDM are imported. Disabled
network interfaces on the source VDM are not imported. (The target system
does not allow you to enable or disable network interfaces.)
n
File Level Retention (FLR) file systems can be imported optionally. However,
Unity systems do not support FLR so those file systems are imported as normal
file systems (UFS64).
n
Distributed Hierarchical Storage Management (DHSM)/(Cloud Tiering
Appliance (CTA) may be configured on the source VNX for archiving inactive
files to secondary storage. If DHSM/CTA is configured on the source VNX
system and a VDM import to Unity is run, all the files on the associated file
system are recalled from the secondary storage to the source VNX. Those files
are then imported to Unity as normal files (that is, no stub files are imported).
Only limited configuration changes to the source VDM and the target NAS server
are supported during import:
n
Shares
n
Local groups
n
Local users
n
Privileges
n
Home directory
n
Distributed File System (DFS) (only pre-existing DFS shares are synchronized
during a cancel operation)
Those are also the only configuration settings that are synchronized with the
source if the migration is canceled.
Block import restrictions and limitations
The following restrictions and limitations relate to a block import from a VNX storage
system to a Unity storage system:
Note
It is recommended that features like Snapview and MirrorView/A are stopped during
import.
26
l
The source VNX1 Block OE is 5.32.x or later or the source VNX2 Block OE is
5.33.x or later.
l
You can only import from a VNX storage system to a single Unity storage system
at a time. Importing from one VNX to multiple Unity storage systems at the same
time is not supported.
l
Deleting a SAN Copy initiator is not supported.
l
Adding a SAN Copy initiator to a new or existing host is not supported.
l
Deleting VNXSancopyHost is not supported.
l
Adding non-import Unity LUNs to VNXSancopyHost is not supported.
Unity Family 4.2 VNX Series Data Import to Unity All Flash or Hybrid, or UnityVSA System User Guide
Considerations for import
l
Removing host access of import LUNs from VNXSancopyHost is not supported.
l
Replication (sync or async) is not allowed until the import is complete.
l
Snapshots are not allowed until the import is complete.
l
Snapshot schedules are not allowed until the import is complete.
l
Changes to the ReplDest property are not allowed until import is complete.
l
Access to hosts other than VNXSancopyHost (initiators) is not allowed until the
import is complete.
l
For a LUN in an import session:
l
n
LUN addition to a CG is not allowed until the import is complete.
n
LUN removal from a CG is not allowed until the import is complete.
n
LUN extension or shrink are not allowed until the import is complete.
For a CG in an import session:
n
LUN additions to the CG are not allowed until the import is complete.
n
LUN removals from the CG are not allowed until the import is complete.
l
Upgrading a Unity system when an import session is in progress is not supported.
l
Creating an import session when an upgrade session is in progress is not
supported.
l
SAN Copy and MirrorView features cannot be configured on the same FC port as
the Import feature for block on both the VNX and Unity systems.
l
Avoid configuring MirrorView reserved iSCSI ports for block import iSCSI
interfaces.
l
Although hundreds or thousands of LUNs can be created for import, the number of
LUNs importing actively is limited to the concurrent SAN Copy sync limits. The
concurrent executing sessions limit is based on the VNX model:
n
For VNX5700, VNX7500, VNX7600, and VNX8000 models, the limit is 32.
n
For VNX5500 and VNX5800 models, the limit is 16.
n
For VNX5100, VNX5300, VNX5400, and VNX5600 models, the limit is 8.
Note
The SAN Copy limits on the source system can be changed. However, it is highly
recommended that you configure these limits before a Remote System connection is
established between the Unity and VNX systems.
Block import restrictions and limitations
27
Considerations for import
28
Unity Family 4.2 VNX Series Data Import to Unity All Flash or Hybrid, or UnityVSA System User Guide
CHAPTER 4
Configure import using Unisphere
This chapter addresses the following topics:
l
l
l
l
l
l
Configure protection and mobility interfaces..................................................... 30
Configure import connection.............................................................................. 31
Create an import session for file.........................................................................32
Manage import sessions for file..........................................................................34
Create an import session for block..................................................................... 35
Manage import sessions for block...................................................................... 36
Configure import using Unisphere
29
Configure import using Unisphere
Configure protection and mobility interfaces
Before you begin
Protection and mobility (import) interfaces can be shared between replication and
import. For import, only VDM imports require interfaces. Block imports do not require
interfaces.
Protection and mobility (import) interfaces are configured to support VDM imports
and must be created prior to creating an import connection. A mobility interface IP
address is assigned to SPA and SPB on the target Unity system. Once the mobility
interface is configured, you can create the import connection between the Unity
system and the VNX system. Mobility interfaces are not used for block import
sessions.
Ensure the following:
l
The interface port is cabled and connected to a network switch.
l
Both SPs are up and running.
Obtain the following information for each Storage Processor (SP):
l
IP address associated with the interface (replication or import). Although you can
specify an IPv4 or IPv6-based address, ensure that you specify the same type of
address for both SPs.
l
IP address mask or prefix length that identifies the associated subnet.
l
Gateway IP address associated with the interface.
l
If applicable, the VLAN ID (between 1 and 4095) you want to associate the
interface with.
Note
For the network to continue functioning properly, ensure that you set the VLAN ID
only when you have configured the network switch port to support VLAN tagging
of multiple VLAN IDs.
Procedure
1. Under Protection & Mobility, select Interfaces.
2. Perform one of the following actions:
l
To create an interface, select the Add icon. On the Create Interface
window, specify the relevant information:
n
For asynchronous replication or import, from the Ethernet Port list,
select an available Ethernet port.
n
For synchronous replication, from the Ethernet Port list, select Sync
Replication Management Port.
Note
Do not use Sync Replication Management Port for asynchronous
replication or import interfaces.
30
l
To modify an interface, select the interface, and then select the Edit icon.
On the Interface Properties window, specify the relevant information.
l
To delete an interface, select the interface, and then select the Delete icon.
Unity Family 4.2 VNX Series Data Import to Unity All Flash or Hybrid, or UnityVSA System User Guide
Configure import using Unisphere
NOTICE
Before you delete an interface, ensure that the interface is not being used
by any replication or import session.
Configure import connection
Before you begin
Once the mobility interfaces have been configured (required for file import only), you
can create a single import connection between the Unity system and the source VNX
system. The import connection supports either block or file import sessions. You need
to enter the IP address of the source SPA or SPB and the credentials of a user with
administrator privileges on the source system when you create the connection. After
creating the import connection, you are ready to create your file or block import
session.
Ensure the following:
l
For a source VNX system with two control stations, the home directory of the
sysadmin user, which is used in configuring the import connection, must exist on
the primary control station of the VNX. For more information, see VNX system
with two Control Stations on page 65.
l
An import connection does not already exist to the source system.
l
If the connection will be used for a VDM import, ensure mobility interfaces are
configured on each SP of the target system.
l
The relevant SP pair (source and target SPAs or source and target SPBs) are up
and running.
l
For block:
n
If using Fibre Channel, Zoning between VNX and Unity SP pairs is configured.
Avoid using VNX MView ports or Unity Synchronous Replication ports.
n
If using iSCSI, iSCSI interface IP addresses on both SPs on the VNX and Unity
systems are configured.
n
The iSCSI connection pairs between the VNX SPs and the Unity SPs are
created.
Note
Highlight the system name and right click iSCSI, then select Connections
Between Storage Systems > Connections > Add. Select iSCSI IP on SPA,
enter the Target Portal IP address for Unity SPA, then repeat for SPB, and
assign a name for the Connection.
Obtain the SP IP management address and associated user credentials that will be
used to connect to the source system.
Procedure
1. Under Protection & Mobility, select Import > Connections.
2. Perform one of the following actions:
l
To create an import connection, select the Add icon. On the Create
Connection window, specify the relevant information.
l
To modify an import connection, select the import connection, and then
select the Edit icon. On the Connection Properties window, specify the
Configure import connection
31
Configure import using Unisphere
relevant SP (SPA or SPB) IP address, username, and password to
authenticate to the SP of the source storage system.
l
If new import interfaces were added, or existing import interfaces were
deleted, the source system connection may become outdated. Select the
relevant import connection, and then select Verify and Update to update
the source system connection to pick up the latest import interface changes
on the target and source systems.
l
If new source storage resources were added, or existing source storage
resources were deleted or modified after you create an import connection
and before you create an import session to the source system, you need to
re-discover the source storage system resources. Select the relevant import
connection, and then select Discover Import Objects to re-discover the
source system resources.
l
To delete a mobility interface, select the import interface, and then select
the Delete icon.
NOTICE
Before you delete an import connection, ensure that the state of the
associated import session is either cancelled or completed.
Create an import session for file
Before you begin
Although all import sessions are listed and created from the same starting point in the
UI, the steps that appear in the related wizard are based on whether the resource type
for the import session is a NAS server (for NFS or CIFS (SMB)) or a LUN or
consistency group (CG). This procedure is pertinent to a NAS server. To create an
import session for a LUN or CG, see Create an import session for block on page 35.
Ensure that you have first created relevant mobility interfaces and import connection,
and then determine the following:
32
l
The system you want to assign as the import source system. This is based on the
import connection configured on the storage system.
l
The name, pool, storage provisioning, and tiering policy you want to use for the
import storage resource. The system will automatically create a target storage
resource as part of this process.
l
The source NFS or CIFS VDM server must be configured with a separate, nonproduction interface, that has the prefix "nas_migration_xxx", which is used
during the import session to migrate the VDM and file system data through the
Unity system's mobility interface.
l
Verify that the physical Data Mover on which the source VDM is located has at
least one IP Interface configured that is not attached to the VDM being migrated.
This ensures that the source Data Mover will be able to provide uninterrupted
Name Services for the remaining file servers. The VDM import session will fail if
this additional interface is not present.
Unity Family 4.2 VNX Series Data Import to Unity All Flash or Hybrid, or UnityVSA System User Guide
Configure import using Unisphere
Note
If you change settings on the source system (such as attaching an interface to the
source VDM or mounting a file system to the source VDM), you need to discover
these objects before starting an import session. In Unisphere under PROTECTION &
MOBILITY , select Import > Connections and select the import connection and More
Actions > Discover Import Objects.
Procedure
1. Under Protection & Mobility, select Import > Sessions.
2. To create an import session, select the Add icon.
The Select Source to Import screen of the Create Import Session wizard
appears.
3. Select the appropriate Source System, select NAS Server as the Resource
Type, and the VDM by name for the Resource.
Mixed NFS and CIFS import is not supported. For CIFS, the source VDM must
be CIFS only (for example, no exports) and have only one CIFS server.
4. For the Configure Target NAS Server screen, the NAS Server Name is the
same as the source VDM name. Select the target Pool to use for the NAS
server, the target SP Owner (SPA or SPB), and the appropriate Target
Storage Pool for the imported file systems, if different from the pool used for
the NAS server. You can specify the Target Type as File System or VMware
NFS data store (VMNFS) for each file system.
5. For the Modify Target Production Port screen, select the appropriate
Ethernet port under the Target Port column. Leave Allow comparison of
Server Parameters checked, unless you prefer to override the parameter
comparison between the source VNX and the target Unity file servers.
NOTICE
Skipping the server parameters comparison could lead to a disruptive cutover
during import.
Select the Target Import Interface from the list. For Import File System with
FileRetention Enabled, keep No selected if you prefer not to import any file
system that is using FileRetention.
Note
If you prefer to import file systems that are configured for FileRetention, select
Yes to override this selection, with the understanding that FileRetention
settings themselves are not supported on the target Unity system and will not
be imported.
For NFS import, once you specify the necessary information, the system will
generate a summary of the import session information. Go to Step 7. For CIFS
import, go to Step 6.
6. For Specify Source CIFS Server Credentials, specify the username and
password to use to connect with the remote CIFS server. These are for the
local user who is a member of the administrators local group.
Ensure the prerequisites for the source CIFS server configuration have been
completed. See Prerequisites for CIFS-only VDM import on page 13.
Create an import session for file
33
Configure import using Unisphere
Once you specify the necessary information, the system will generate a
summary of the import session information. Go to Step 7.
7. Verify that the import session information appearing in the summary is accurate
and complete.
8. Click Finish to create and start the import session.
The Results window appears and shows the progress of the creation and start
of the import session.
Manage import sessions for file
An import session establishes an end-to-end path for an import operation between a
source and target. The import source and target are remote to each other, so the
session establishes the path that the data follows as it moves from source to target.
To set up an import session for file, see Configure import.
Procedure
1. Under Protection & Mobility, select Import > Sessions.
2. Perform one of the following actions:
Action
Description
Modify a
session
Select a session and click the pencil (View/Edit) icon or double
click a session to modify the name of the session. The file
system to pool mapping and the interface to port mapping
cannot be changed through Unisphere once the target
resources (NAS server, file system, and interface) are created;
however, the CLI does allow you to make these changes to a
session's configuration before the start of import or during an
initial copy failed state.
Pause and
resume a
session
Select a session and under More Actions, click Pause or
Resume. Use Pause to pause an import session that is in either
the Initial Copy or Incremental Copy state. Use Resume to start
an import session that is in the Initialized state, or resume an
import session that has been paused and is in the Initial Copy or
Incremental Copy state.
Cutover
Select a session that is in the ready to cutover state, and under
More Actions, click Cutover to cut over an import session to
promote the target to production mode.
Note
Client accesses are switched from the source VDM, to the
target NAS Server. During the cutover of a CIFS-only VDM
migration, hosts will have I/O interrupted and see a short period
of data unavailability (DU).
Cancel
34
Select a session and under More Actions, click Cancel. You can
cancel an import session that is in any state (with the
exceptions of Cancelling, Cancelled, Cutting Over, or
Committed) before the commit state. The cancel operation rolls
back the VDM and related file systems to the source VNX.
Unity Family 4.2 VNX Series Data Import to Unity All Flash or Hybrid, or UnityVSA System User Guide
Configure import using Unisphere
Action
Description
Note
This operation is not transparent. The host needs to be
remounted to the NFS. For CIFS, hosts will see DU
(disconnection and no access) and may need to re-connect.
Commit
Select a session and under More Actions, click Commit. You
can commit an import session that is in the Ready to Commit
state to finish the import process.
Download
summary
report
Select a session and under More Actions, click Download
Summary Report.
Create an import session for block
Before you begin
Although all import sessions are listed on and created from the same starting point in
the UI, the steps that appear in the related wizard are based on whether the resource
type for the import session is a NAS server or a LUN or consistency group (CG). This
procedure is pertinent to a LUN or consistency group (CG). To create an import
session for a NAS server, see Create an import session for file on page 32.
Ensure that you have first configured FC zoning for the source and target systems or
created an iSCSI connection between the source and target systems and, if
necessary, created relevant interfaces and import connection, and then determine the
following:
l
The import source system, which is based on the import connection configured on
the storage system.
l
The name, pool, storage provisioning, and tiering policy you want to use for the
import storage resource and, depending on the type of pool, whether compression
is enabled. The system will automatically create a target storage resource as part
of this process.
Note
For storage provisioning, determine whether to convert a thin LUN to a non-thin
(thick) LUN, or a thick LUN to a thin LUN. Also, determine whether to enable
compression on a thin LUN in an all-Flash pool. Compression is only supported on
all-Flash pools.
Procedure
1. Under Protection & Mobility, select Import > Sessions.
2. To create an import session, select the Add icon.
The Create Import Session wizard appears.
3. Step through the wizard and specify the relevant information to select the
source to import, configure the target LUN or CG and, if necessary, configure
the host access and session throttle settings for the import session.
Create an import session for block
35
Configure import using Unisphere
The name of the import session will default to
import_sess_<sourceResourceName>_<sourceSystemSerialNumber>_<tar
getSystemSerialNumber>.
In the Target step, the LUN or CG name is the same as the source LUN or CG
name. In case of a naming conflict, the source system name will be appended
with the next available number, such as 01. You should always see a suggested
pool selection based on capacity unless there are no valid pools available. If
necessary, the Target Name and Pool, Tiering Policy, Thin, and Compression of
the associated LUN or LUNs can be modified.
Note
If Thin is not selected, Compression cannot be selected and is disabled. If Thin
is selected, Compression can be selected. Compression is only supported on
all-Flash pools.
In the Access step, select or add a host or hosts that can access the storage
resource.
In the Setting step, specify whether to throttle the import transfer. Transfer
throttle impacts the import speed and host latency for the related LUNs and file
systems that are in use on the source and target storage systems. The default is
set to throttle (checkbox is checked), which means that the session is
throttled. If set to unchecked, import transfer would be unthrottled and allowed
to function at the highest rate possible.
Once you specify the necessary information, the system will generate a
summary of the import session information.
4. Verify that the import session information appearing in the summary is accurate
and complete.
5. Click Finish to create and start the import session.
The Results window appears and shows the progress of the creation and start
of the import session.
Manage import sessions for block
An import session establishes an end-to-end path for an import operation between a
source and target. The data follows the path as it moves from source to target.
To set up an import session for block, see Configure import.
Procedure
1. Under Protection & Mobility, select Import > Sessions.
2. Perform one of the following actions:
36
Action
Description
Modify a
session
Select a session and click the View/Edit icon or double click a
session to modify the name of the session or change the
configuration settings for the transfer throttle and the cutover
threshold percent.
Unity Family 4.2 VNX Series Data Import to Unity All Flash or Hybrid, or UnityVSA System User Guide
Configure import using Unisphere
Action
Description
Pause and
resume a
session
Select a session and under More Actions, click Pause or
Resume. Use Pause to pause an import session that is in either
the Initial Copy or Incremental Copy state. Use Resume to start
an import session that is in the Initialized state, or resume an
import session that has been paused and is in the Initial Copy or
Incremental Copy state, or when a session fails and the cause of
the failure has been fixed.
Cutover
Select a session and under More Actions, click Cutover to cut
over an import session to promote the target to production
mode.
Cancel
Select a session and under More Actions, click Cancel. You can
cancel an import session that is in any state (with the exceptions
of Cancelling, Cancelled, or Cutting Over) before the commit
state. The cancel operation deletes the SAN Copy session for
each set of LUN pairs in the import session and disables SAN
Copy access to the target LUN. It also deletes the target LUN or
CG associated with the import session.
Commit
Disabled since a separate commit action is not needed for a block
import session. This action is performed automatically at the end
of cutover for a block import session.
Manage import sessions for block
37
Configure import using Unisphere
38
Unity Family 4.2 VNX Series Data Import to Unity All Flash or Hybrid, or UnityVSA System User Guide
CHAPTER 5
Configure import using the CLI
This chapter addresses the following topics:
l
l
l
l
l
l
l
l
l
l
l
l
l
l
l
Create mobility interfaces.................................................................................. 40
Create remote system configurations................................................................. 41
View import sessions..........................................................................................42
Create a NAS import session..............................................................................43
View import sessions for file...............................................................................49
Change import session settings for file.............................................................. 50
Cutover import session for file........................................................................... 52
Commit import session for file........................................................................... 53
Cancel a NAS import session............................................................................. 54
Create a block import session............................................................................ 55
View import sessions for block........................................................................... 57
Change import session settings for block...........................................................58
Cut over import session for block.......................................................................59
Cancel a block import session............................................................................ 59
View import session elements............................................................................ 60
Configure import using the CLI
39
Configure import using the CLI
Create mobility interfaces
Create a mobility interface.
Format
/net/if create [-async] [-vlanId <value>] -type {iscsi |
replication} -port <value> -addr <value> [-netmask <value>] [gateway <value>]
Action qualifier
Qualifier
Description
-async
Run the creation operation in asynchronous mode.
-type
Specify the interface type. Value is one of the following:
l
iscsi—Interface for iSCSI storage.
l
replication—Interface for replication-related data or
management traffic.
Note
The replication type is also used to create the mobility interface
which is used during a file import session.
-port
Specify the ID of the SP port or link aggregation that will use the
interface.
Note
For systems with two SPs, a file interface is created on a pair of
symmetric Ethernet ports rather than on a single specified port. Its
current port is defined by NAS server SP and may differ from the
specified port. For example, if the user specifies port spa_eth2, but the
NAS server is on SP B, the interface is created on port spb_eth2.
-vlanId
Specify the virtual LAN (VLAN) ID for the interface. The interface uses
the ID to accept packets that have VLAN tags. The value range is 1–
4095.
Note
If no VLAN ID is specified, which is the default, packets do not have
VLAN tags. The Unisphere online help provides more details about
VLANs.
-addr
Specify the IP address for the interface. The prefix length should be
appended to the IPv6 address and, if omitted, will default to 64. For
IPv4 addresses, the default length is 24. The IPv4 netmask may be
specified in address attribute after slash.
-netmask Specify the subnet mask for the interface.
40
Unity Family 4.2 VNX Series Data Import to Unity All Flash or Hybrid, or UnityVSA System User Guide
Configure import using the CLI
Qualifier
Description
Note
This qualifier is not required if the prefix length is specified in the -addr
attribute.
-gateway Specify the gateway for the interface.
Note
This qualifier configures the default gateway for the specified port’s SP.
Example
The following command creates a replication interface. The interface receives the ID
IF_1:
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /net/if create -type
replication -port eth1_spb -addr 10.0.0.1 -netmask 255.255.255.0 gateway 10.0.0.1
Storage system address: 10.0.0.1
Storage system port: 443
HTTPS connection
ID = IF_1
Operation completed successfully.
Create remote system configurations
Configures a remote system configuration for the local system to access.
Note
For a source VNX system with two control stations, the home directory of a user with
the Administrator role, which is used in configuring the import connection, must exist
on the primary control station of the VNX. See VNX system with two Control Stations
on page 65.
Format
/remote/sys create -addr <value> [-type VNX] -srcUsername
<value> {-srcPassword <value> | -srcPasswordSecure} dstUsername <value> {-dstPassword <value> | -dstPasswordSecure}
[-connectionType {sync | async | both}]
Action qualifiers
Qualifier
Description
-addr
Specify the network name or IP address of the remote
system.
-type
Specify the remote system type. Valid values are:
l
VNX
Create remote system configurations
41
Configure import using the CLI
Qualifier
Description
-srcUsername
For systems that are the source in a replication, type the
username that is used to access the system.
-srcPassword
For systems that are the source in a replication, type the
user password that is used to access the system.
-srcPasswordSecure Specify the password in secure mode. Once you run the
command with this qualifier, you will be asked to type the
password separately.
-dstUsername
For systems that are the destination in a replication
session or VNX in an import session, specify the username
that is used to access the system.
-dstPassword
For systems that are the destination in a replication
session or VNX in an import session, specify the user
password that is used to access the system.
-dstPasswordSecure Specify the password in secure mode. Once you run the
command with this qualifier, you will be asked to type the
password separately.
-connectionType
Specify this qualifier to indicate the type of replication
connection. Valid values are async, sync, or both.
Example
The following command creates a remote system configuration with these settings:
l
Network address is 10.64.75.10.
l
Includes access credentials for when the system is the source or destination.
The configure remote system receives the ID RS_65536:
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /remote/sys create –
addr 10.64.75.10 –type VNX -dstUsername admin1 -dstPassword
Password789!
Storage system address: 10.0.0.1
Storage system port: 443
HTTPS connection
ID = RS_65536
Operation completed successfully.
View import sessions
View details about existing import sessions for both file and block. You can filter on
the session ID.
Format
/import/session [-id <value> | -active | -completed | cancelled] [-type {block | nas}] show
42
Unity Family 4.2 VNX Series Data Import to Unity All Flash or Hybrid, or UnityVSA System User Guide
Configure import using the CLI
Object qualifier
Qualifier
Description
-id
Type the ID of the import session.
-active
Show only active sessions (sessions that are not completed or
cancelled).
-completed Show only completed sessions.
-cancelled Show only cancelled sessions.
-type
Specifies what type of sessions to show. Valid values are :
l
block
l
nas
Example
The following command displays all existing import sessions on the system:
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /import/session show
-detail
Storage system address: 10.0.0.1
Storage system port: 443
HTTPS connection
1:
ID
= import_1
Name
=
import_sess_vdm1_BB0050562C7D2A_FCNCH0972C330D
Session type
= nas
Health state
= OK (5)
Health details
= "The component is
operating normally. No action is required."
State
= Initialized
Progress
= empty
Source system
= RS_65535
Source resource
= vdm1
Target resource
= nas_1
2:
ID
= import_2
Name
= VNX LUN Group 1 import
Session type
= block
Health state
= OK (5)
Health details
= "The component is
operating normally. No action is required."
State
= Initial copy
Progress
=
Source system
= RS_65535
Source resource
= LUNGroup1
Target resource
= res_1
Create a NAS import session
Create a NAS import session.
Create a NAS import session
43
Configure import using the CLI
Note
This command only creates the import session. To start the import session through
the UEMCLI, you must run the /import/session/nas set command and specify
no for the action qualifier -paused.
Prerequisites
Before creating a NAS import session, complete the following configuration tasks:
l
Create interfaces on both the source and target systems for data transfer.
l
Create an import connection from the source VNX to the current Unity-based
target system.
l
Create a target pool.
Format
/import/session/nas create [-async] [-name <value>] -srcSys
<value> -srcRes <value> -targetResPool <value>< [targetImportIf <value>] [-productionIfPortPairs <value>] –
fsPoolPairs <value>] –defaultProductionPort <value> [-flrImport
{yes | no}] [-unixDirectoryService {directMatch | local | nis |
ldap |localThenNis | localThenLdap | none}] [srcLocalCifsAdminUsername <value> {-srcLocalCifsAdminPasswd
<value>|-srcLocalCifsAdminPasswdSecure}] [srcFsImportedAsVMWareDatastore <value>] [srcFsImportedWithCompressionEnabled <value>] [skipServerParamCheck]
Action qualifiers
Qualifier
Description
-async
(Optional) Run operation in asynchronous mode.
-name
(Optional) Specifies the new name of the import session.
Note
If name is not specified, it will be generated in the pattern
import_sess_<srcRes>_<srcSysSerialNumber>_<targetSysSerialNum
ber>[_<index>]
-srcSys
Specifies the source (remote) system.
-srcRes
Specifies the source resource.
-targetResPool
Specifies the default storage pool to store target NAS server configuration
information and file systems.
-targetImportIf
(Optional) Specifies the target replication interface for the import session.
-productionIfPortPairs
(optional) Specifies the source VDM production interfaces and target port pairs.
Values are a comma separated list of mappings between source VDM production
interfaces and target ports.
Note
Use the following format:
source_interface_1:dest_port_1,source_interface_2:dest_port_2
44
Unity Family 4.2 VNX Series Data Import to Unity All Flash or Hybrid, or UnityVSA System User Guide
Configure import using the CLI
Qualifier
Description
-fsPoolPairs
(Optional) Specifies the source file system IDs and target pool pairs. Values are a
comma separate list of mappings between file system IDs and target pool pairs.
Note
Use the format sourceFsId1:destination_pool_friendlyId (sourceFsid
must be an existing supported source file system ID, otherwise validation fails), or
sourceFsId2~sourceFsId3:destination_pool_friendlyId
(sourceFsId2 and sourceFsId3 must be existing supported source file system IDs,
the other file system IDs between sourceFsId2 and sourceFsId3 do not necessarily
need to exist. The create process only takes existing source file system IDs and
skips non-existent file system IDs in the range.). For example, for the input
12:pool_1,15~20:pool_2, source file system IDs with 12, 15, and 20 must exist
but source file systems with IDs starting from 16 to 19 do not need to exist.
-defaultProductionPort
Specifies the target port where NAS server production interfaces will be created
by default.
-flrImport
(Optional) Specifies whether to import FLR enabled file systems. Valid values are:
-unixDirectoryService
l
yes - FLR enabled file systems are imported as normal file systems
l
no - FLR enabled file systems are ignored.
(Optional) Specifies which Unix directory service to import. Directory service is
used for querying identity information for Unix (such as UIDs, GIDs, net groups).
Valid values are:
l
directMatch - Import source unixDirectoryService to target without any
change.
l
local - Use Local files (passwd, group, hosts, netgroup) for querying identity
information for Unix.
l
nis - Use NIS for querying identity information for Unix.
l
ldap - Use LDAP for querying identity information for Unix.
l
localThinNis - Use Local files and then NIS for querying identity
information for Unix.
l
localThinLdap - Use Local files and then LDAP for querying identity
information for Unix.
l
none - Do not use any of Unix directory services.
-srcLocalCifsAdminUsername
(Optional) Specifies the user name for authentication to the CIFS server on the
source VDM.
-srcLocalCifsAdminPasswd
(Optional) Specifies the password for authentication to the CIFS server on the
source VDM.
-srcLocalCifsAdminPasswd
Secure
(Optional) Specifies the password in secure mode.
Note
The user is prompted to input the password and the password confirmation.
(Optional) Specifies what source file systems are imported as VMWare datastore
srcFsImportedAsVMWareDatastore file systems. Values are a comma separated list of source file system IDs with
comma separated value of single file system ID or a range of file system IDs; for
Create a NAS import session
45
Configure import using the CLI
Qualifier
Description
example, sourceFsId1,sourceFsId2~sourceFsId3. sourceFsId1,
sourceFsId2 and sourceFsId3 must be existing supported source file system IDs.
The source file systems with IDs between sourceFsId2 and sourceFsId3 do not
necessarily need to exist. The create process only takes existing source file system
IDs and skips non-existent file systems in the range. For example, for input
13,15~20,25, source file systems with ID 13, 15, 20 and 25 must exist. For source
file systems with IDs starting from 16 to 19, they do not need to exist.
Note
If a VNX file system is specified by this option, it should not contain any tree
quotas or user quotas.
(Optional) Specifies which source file systems are imported with inline
srcFsImportedWithCompressionEn compression enabled. Values are a comma separated list of source file system IDs
abled
with comma separated value of single file system ID or a range of file system IDs;
for example, sourceFsId1,sourceFsId2~sourceFsId3.sourceFsId1,
sourceFsId2 and sourceFsId3 must be existing supported source file system IDs.
The source file systems with IDs between sourceFsId2 and sourceFsId3 do not
necessarily need to exist. The create logic only takes existing source file system
IDs and skips non-existent file systems in the range. For example, for input
13,15~20,25, source file systems with ID 13,15,20 and 25 must exist. For source file
systems with IDs starting from 16 to 19, they do not need to exist.
(Optional) Whether to skip server parameters check (comparison). When selected,
the server parameters check is skipped. In silent mode, the check is not skipped.
Import session creation compares server parameters between VNX and Unity.
When import session creation fails with a Server parameter error, this option allows
the creation to proceed.
-skipServerParamCheck
NOTICE
Skipping the server parameters check could lead to disruptive cutover during
import.
Example
The following command creates an import session with these settings:
Note
The source VDM is a NFS-only VDM.
46
l
Import session name is newName.
l
Source storage system is RS_1.
l
Source storage resource (VDM) is src_vdm_to_migrate.
l
Target resource pool is pool_1.
l
Target import interface is if_3.
l
Source VDM production interface and target port pairs are
source_interface_1:spa_iom_0_eth1 and source_interface_2:spa_iom_0_eth0.
l
Source file system and target pool pairs are 100~200:pool_2 and 255:pool_3.
l
Target port where NAS server production interfaces will be created is
spa_iom_0_eth0.
Unity Family 4.2 VNX Series Data Import to Unity All Flash or Hybrid, or UnityVSA System User Guide
Configure import using the CLI
l
Import FLR enabled file systems.
l
Migrate the direct match UNIX Directory Service.
l
File systems 13, 20 through 25, and 30 are to be imported as VMWare datastore
file systems.
l
Skip the server parameters check.
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! import/session/nas
create -name MyName1 -srcSys RS_1 -srcRes src_vdm_to_migrate targetResPool pool_1 -targetImportIf if_3 -productionIfPortPairs
source_interface_1:spa_iom_0_eth1,source_interface_2:spa_iom_0_eth0 fsPoolPairs 100~200:pool_2,255:pool_3 -defaultProductionPort
spa_iom_0_eth0 -flrImport yes -unixDirectoryService directMatch srcFsImportedAsVMWareDatastore 13,20~25,30 -skipServerParamCheck
Storage system address: 10.0.0.1
Storage system port: 443
HTTPS connection
Using '-skipServerParamCheck' option could lead to disruptive
cutover during migration. Do you want to continue?
yes / no: yes
ID = import_1
Operation completed successfully.
The following command creates an import session with these settings:
Note
The source VDM is a NFS-only VDM.
l
Import session name is newName.
l
Source storage system is RS_1.
l
Source storage resource (VDM) is src_vdm_to_migrate.
l
Target resource pool is pool_1.
l
Target import interface is if_3.
l
Source VDM production interface and target port pairs are
source_interface_1:spa_iom_0_eth1 and source_interface_2:spa_iom_0_eth0.
l
Source file system and target pool pairs are 100~200:pool_2 and 255:pool_3.
l
Target port where NAS server production interfaces will be created is
spa_iom_0_eth0.
l
Import FLR enabled file systems.
l
Migrate the direct match UNIX Directory Service.
l
File systems 13, 20 through 25, and 30 are to be imported as VMware datastore
file systems.
l
File systems 14, 22, 25 through 30 are imported as thin.
l
File systems 31 and 40 through 45 are imported and compressed.
l
Skip the server parameters check.
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! / import/session/nas
create -name MyName -srcSys RS_1 -srcRes src_vdm_to_migrate targetResPool pool_1 -targetImportIf if_3 -productionIfPortPairs
source_interface_1:spa_iom_0_eth1,source_interface_2:spa_iom_0_eth0 Create a NAS import session
47
Configure import using the CLI
fsPoolPairs 100~200:pool_2,255:pool_3 -defaultProductionPort
spa_iom_0_eth0 -flrImport yes -unixDirectoryService directMatch srcFsImportedAsVMwareDatastore 13,20~25,30 -srcFsImportedAsThin
14,22,25~30 -srcFsImportedWithCompressionEnabled 31,40~45 skipServerParamCheck
Storage system address: 10.0.0.1
Storage system port: 443
HTTPS connection
ID = import_1
Operation completed successfully.
The following command creates an import session with these settings:
Note
The source VDM is a CIFS-only VDM.
l
Import session name is newName.
l
Source storage system is RS_1.
l
Source storage resource (VDM) is src_vdm_to_migrate.
l
Target resource pool is pool_1.
l
Target import interface is if_3.
l
Source VDM production interface and target port pairs are
source_interface_1:spa_iom_0_eth1 and source_interface_2:spa_iom_0_eth0.
l
Source file system and target pool pairs are 100~200:pool_2 and 255:pool_3.
l
Target port where NAS server production interfaces will be created is
spa_iom_0_eth0.
l
Import FLR enabled file systems.
l
The user name for authentication to the CIFS server on the source VDM is
cifsadmin1
l
The password for authentication to the CIFS server on the source VDM is
cifspassword1
l
File systems 13, 20 through 25, and 30 are to be imported as VMware datastore
file systems.
l
File systems 14, 22, 25 through 30 are imported as thin.
l
File systems 31 and 40 through 45 are imported and compressed.
l
Skip the server parameters check.
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! import/session/nas
create -name MyName1 -srcSys RS_1 -srcRes src_vdm_to_migrate targetResPool pool_1 -targetImportIf if_3 -productionIfPortPairs
source_interface_1:spa_iom_0_eth1,source_interface_2:spa_iom_0_eth0 fsPoolPairs 100~200:pool_2,255:pool_3 -defaultProductionPort
spa_iom_0_eth0 -flrImport yes -srcFsImportedAsVMWareDatastore
13,20~25,30 -srcLocalCifsAdminUsername cifsadmin1 srcLocalCifsAdminPasswd cifspassword1 -skipServerParamCheck
Storage system address: 10.0.0.1
Storage system port: 443
48
Unity Family 4.2 VNX Series Data Import to Unity All Flash or Hybrid, or UnityVSA System User Guide
Configure import using the CLI
HTTPS connection
Using '-skipServerParamCheck' option could lead to disruptive
cutover during migration. Do you want to continue?
yes / no: yes
ID = import_1
Operation completed successfully.
View import sessions for file
View details about import sessions for file. You can filter on the session ID.
Format
/import/session/nas [{-id <value> | -active | -completed | cancelled}] show
Object qualifier
Qualifier
Description
-id
Type the ID of the import session.
-active
Show only active sessions (sessions that are not completed or
cancelled).
-completed Show only completed sessions.
-cancelled Show only cancelled sessions.
Example
The following command displays file import sessions on the system:
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /import/session/nas
show -detail
Storage system address: 10.0.0.1
Storage system port: 443
HTTPS connection
1:
ID
Name
import_sess_vdm1_BB0050562C7D2A_FCNCH0972C330D
Health state
Health details
normally. No action is required."
State
Progress
Source system
Source resource
Source import interface
Source file systems imported as VMWare datastore
Source file systems imported with compression enabled
Target resource
Target resource pool
Target file system to pool mapping
Target import interface
Target default production port
Target default import port
Target production interface import port mapping
CIFS local administrator username
= import_1
=
= OK (5)
= "The component is operating
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
Initialized
RS_65535
vdm1
nas_migration_1
13,20~25,30
31,40~45
nas_1
pool_1
13~14:pool_1
if_3
spa_iom_0_eth0
spa_iom_0_eth0
filesim8129dm2:spa_iom_0_eth0
admin
View import sessions for file
49
Configure import using the CLI
Change import session settings for file
Change the settings for a NAS import session.
Format
/import/session/nas –id <value> set [-async] [-paused {yes |
no}] -name <value>] [-targetResPool <value>] [-fsPoolPairs
<value>] [-targetImportIf <value>] [-productionIfPortPairs
<value>] [-srcLocalCifsAdminUsername <value> {srcLocalCifsAdminPasswd <value> |
srcLocalCifsAdminPasswdSecure}] [srcFsImportedAsVMwareDatastore <value>] [srcFsImportedWithCompressionEnabled <value>]}
Object qualifier
Qualifier
Description
-id
Type the ID of the import session.
Action qualifiers
Qualifier
Description
-async
Run action in asynchronous
mode.
-name
Specifies the new name of the
import session.
-paused
Specifies whether to pause the
session. Valid values are:
l
yes
l
no
Note
no starts or resumes the import
session.
50
-targetResPool
Specifies the new pool for the
target resource. Applicable only
when the session status is
Initialized or the target NAS
server provision fails.
-fsPoolPairs
Specifies the source file system
IDs and target pool pairs.
Applicable only when the session
status is Initialized or the target
file system provision fails.
-targetImportIf
Specifies the new target
migration interface. Applicable
only when the session status is
Unity Family 4.2 VNX Series Data Import to Unity All Flash or Hybrid, or UnityVSA System User Guide
Configure import using the CLI
Qualifier
Description
Initialized or the target NAS
server provision fails.
-productionIfPortPairs
Specifies the source VDM
production interface and target
port pairs. Applicable only when
the session status is Initialized or
the target production interface
creation fails.
-srcLocalCifsAdminUsername
Specifies the user name for
authentication to the CIFS server
on the source VDM.
-srcLocalCifsAdminPasswd
Specifies the password for
authentication to the CIFS server
on the source VDM.
-srcLocalCifsAdminPasswdSecure
Specifies the password in secure
mode.
Note
The user is prompted to input the
password and the password
confirmation.
-srcFsImportedAsVMWareDatastore
Specifies what source file
systems are imported as VMware
datastore file systems. Only
applies to file import when the
session is initialized.
Note
If a VNX file system is specified
by this option, it should not
contain any tree quotas or user
quotas.
-srcFsImportedWithCompressionEnabled Specifies which source file
systems are imported with inline
compression enabled. Only
applies to file import when the
session is initialized.
Example
The following command changes the NAS import session settings:
Note
This command only makes changes to the import session configuration. To resume
(start) the import session through the UEMCLI, you must run the /import/
session/nas set command and specify no for the action qualifier -paused.
Change import session settings for file
51
Configure import using the CLI
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /import/session/nas
–id import_1 set -name newName -targetResPool pool_2 -targetImportIf
if_3 -productionIfPortPairs
source_interface_1:spa_iom_0_eth1,source_interface_2:spa_iom_0_eth0 fsPoolPairs 100~200:pool_2,255:pool_3 -srcFsImportedAsVMWareDatastore
17~20 - srcFsImportedWithCompressionEnabled 31,40~45
Storage system address: 10.0.0.1
Storage system port: 443
HTTPS connection
Operation completed successfully.
Start or resume an import session
Once an import session is created and optionally modified, it remains in the initialized
state until it is started (or resumed). The following command starts (or resumes) the
example NAS import session:
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /import/session/nas
–id import_1 set -paused no
Storage system address: 10.0.0.1
Storage system port: 443
HTTPS connection
Operation completed successfully.
Cutover import session for file
Cut over an existing NAS import session. Cutting over a session switches the active
host IOs to the target side and initiates the incremental data synchronization from the
source to the target.
Format
/import/session/nas -id <value> cutover [-async] [-netbiosName
<value>] [-cifsServerName <value> -domainUsername <value> {domainPasswd <value> | -domainPasswdSecure}]
Object qualifier
Qualifier
Description
-id
Specifies the ID of the import session.
Action qualifier
52
Qualifier
Description
-async
Run the action in asynchronous mode.
-netbiosName
Specifies new NetBIOS name for source the CIFS server.
-cifsServerName
Specifies the new name for the source CIFS server after
the cutover. SMB (CIFS) server name must be unique on
the network.
Unity Family 4.2 VNX Series Data Import to Unity All Flash or Hybrid, or UnityVSA System User Guide
Configure import using the CLI
Qualifier
Description
Note
If not specified, the default name for renaming the
source CIFS server is the original CIFS server name
prefixed with an underscore (_).
-domainUsername
Specifies the domain administrator name. This name is
required for renaming the source CIFS server and joining
it to the Active Directory. (Used for AD-joined CIFS
server migration only)
-domainPasswd
Specifies the domain user password.
-domainPasswdSecure Specifies the password in secure mode.
Note
The user is prompted to input the password and the
password confirmation.
Example 1
The following command cuts the NFS import session, import_1, over to the target
system:
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /import/session/nas
-id import_1 cutover
Storage system address: 10.0.0.1
Storage system port: 443
HTTPS connection
Operation completed successfully.
Example 2
The following command cuts the SMB import session, import_1, over to the target
system:
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /import/session/nas
-id import_1 cutover -cifsServerName cifs1 -domainUsername user1 domainPasswd password1
Storage system address: 10.0.0.1
Storage system port: 443
HTTPS connection
Operation completed successfully.
Commit import session for file
Commit an existing NAS import session. Committing a session completes the import
process.
Format
/import/session/nas -id <value> commit [-async]
Commit import session for file
53
Configure import using the CLI
Object qualifier
Qualifier
Description
-id
Type the ID of the import session.
Action qualifier
Qualifier
Description
-async
Run the action in asynchronous mode.
Example
The following command commits the import session, import_1.
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /import/session/nas
-id import_1 commit
Storage system address: 10.0.0.1
Storage system port: 443
HTTPS connection
Operation completed successfully.
Cancel a NAS import session
Cancel an existing NAS import session.
Format
/import/session/nas -id <value> cancel [-async] [domainUsername <value> {-domainPasswd <value> | domainPasswdSecure}] [-skipSourceRestore]
Object qualifier
Qualifier
Description
-id
Type the ID of the import session.
Action qualifier
Qualifier
Description
-async
Run the action in asynchronous mode.
-domainUsername
Specifies the domain user with administrative rights to
update the AD (not necessary for standalone CIFS
server).
-domainPasswd
Specifies the domain user password (not necessary for
standalone CIFS server).
-domainPasswdSecure Specifies the password in secure mode (not necessary
for standalone CIFS server).
54
Unity Family 4.2 VNX Series Data Import to Unity All Flash or Hybrid, or UnityVSA System User Guide
Configure import using the CLI
Qualifier
Description
Note
The user is prompted to input the password and the
password confirmation.
-skipSourceRestore
Skip source VDM restore. When specified, the source
VDM restore operations are skipped. Normally, the
cancel action stops the import transport, deletes the
corresponding destination resources, and restores the
source VDM (turns up the source interfaces attached to
the VDM if they are turned down during cutover and
deletes internal export options created by the import for
import transport).
Example
The following command cancels the NAS import session, import_1.
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /import/session/nas
-id import_1 cancel
Storage system address: 10.0.0.1
Storage system port: 443
HTTPS connection
Operation completed successfully.
Create a block import session
Prerequisites
Before creating a block import session, complete the following configuration tasks:
l
Create interfaces on both source and target for data transfer.
l
Create an import connection to a Unity-based target system.
l
Create a block import target (LUN or LUN Group) on the target system.
Format
/import/session/block create [-async] [-name <value>] [throttle {yes | no}] -srcSys <value> -srcRes <value> lunPoolPairs <value> [-cutoverThreshold <value>] [-hosts
<value>] [-importAsVMwareDatastore {yes | no}]
Action qualifiers
Qualifier
Description
-async
Run action in asynchronous mode.
-name
Specifies the name of the import session.
Create a block import session
55
Configure import using the CLI
Qualifier
Description
Note
If name is not specified, it will be generated in the pattern
import_sess_<srcRes>_<srcSysSerialNumber>_<targetSysSerialNum
ber>[_<index>]
Specifies whether to throttle the import transfer. Throttle impacts the
import speed and host latency for the related LUNs and file systems that
are in use on the source and target storage systems. Valid values are:
-throttle
l
yes
l
no
Note
Default is to throttle the import transfer, which means that it is throttled at
less than the full speed.
-srcSys
Specifies the source system.
-srcRes
Specifies the source resource.
-lunPoolPairs
Specifies the LUN pool pairs. A comma separated list of mappings between
the source LUN and the target storage configuration.
Note
Use the format srcLUN1:tgtPool1,…,…. Target LUNs will have the same
properties as those of the source LUN, such as name, isThin, SP, and size.
-cutoverThreshold
The percentage threshold below which the import session becomes ready
to be cutover.
-hosts
Specifies the hosts. A comma separated list of friendly IDs of hosts to give
access to target elements.
Specifies whether the source LUN is to be imported as a VMware
importAsVMwareDatastore datastore (VMFS). This option is only valid for a LUN session and is not
valid for a CG session. Valid values are:
l
yes
l
no
Example
The following command creates an import session with these settings:
56
l
Import session name is lun_17_import.
l
Source storage system is RS_1.
l
Source storage resource is 17.
l
LUN pool pair is 17:pool_1.
Unity Family 4.2 VNX Series Data Import to Unity All Flash or Hybrid, or UnityVSA System User Guide
Configure import using the CLI
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! import/session/block
create -name lun_17_import -srcSys RS_65596 -srcRes 17 -lunPoolPairs
17:pool_1 -importAsVMwareDatastore yes
Storage system address: 10.0.0.1
Storage system port: 443
HTTPS connection
ID = import_1
Operation completed successfully.
View import sessions for block
View details about import sessions for block. You can filter on the session ID.
Format
/import/session/block [{-id <value> | -active | -completed | cancelled}] show
Object qualifier
Qualifier
Description
-id
Type the ID of the import session.
-active
Show only active sessions (sessions that are not completed or
cancelled).
-completed Show only completed sessions.
-cancelled Show only cancelled sessions.
Example
The following command displays block import sessions on the system:
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /import/session/
block show -detail
Storage system address: 10.0.0.1
Storage system port: 443
HTTPS connection
1:
ID
= import_2
Name
= VNX LUN Group 1 import
Session type
= block
Health state
= OK (5)
Health details
= "This import session
is operating normally. No action is required."
State
= Syncing
Progress
= 0%
Source system
= RS_65535
Source resource
= LUNGroup1
Target resource
= res_1
Estimated remaining bytes
= 47185920 (45 M)
Percent remaining for import
= 6
Cutover threshold percent
= 5
Throttle
= no
View import sessions for block
57
Configure import using the CLI
Change import session settings for block
Change the settings for a block import session.
Format
/import/session/block –id <value> set [-async] [-name <value>]
[-paused {yes | no} [-throttle {yes | no}] [-cutoverThreshold
<value>]
Object qualifier
Qualifier
Description
-id
Type the ID of the import session.
Action qualifiers
Qualifier
Description
-async
Run action in asynchronous mode.
-name
Specifies the new name of the import session.
-throttle
Specifies whether to throttle the import transfer. Throttle
impacts the import speed and host latency for the related
LUNs and file systems that are in use on the source and
target storage systems. Valid values are:
l
yes
l
no
Note
Default is to throttle the import transfer, which means that
it is throttled at less than the full speed.
-paused
Specifies whether to pause the import session. Valid values
are:
l
yes
l
no
Note
no starts or resumes the import session.
-cutoverThreshold Specifies the threshold percentage below which the import
session is cutover-ready.
Example
The following command changes the block import session settings for name to
newName, the commitThrottle level to 5, and to not apply the throttle:
58
Unity Family 4.2 VNX Series Data Import to Unity All Flash or Hybrid, or UnityVSA System User Guide
Configure import using the CLI
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /import/session/
block –id import_1 set -name newName -throttle no -cutoverThreshold 5
Storage system address: 10.0.0.1
Storage system port: 443
HTTPS connection
Operation completed successfully.
Cut over import session for block
Cut over and complete an existing block import session. Cutting over a block import
session can be a long and disruptive process. To reduce the period of disruption, set
the cutover threshold as small as possible. By decreasing the cutover threshold to a
small value, a smaller number of changes will need to be transferred after the
application is quiescent. The cutover threshold is a percentage of the LUN size and
hence for larger LUNs it is recommended that the cutover threshold be set to a value
smaller than the default value of 5 percent. Lastly, cut over an import session only
when the session is in the Cutover Ready state. This action ensures that the cutover is
performed when the least number of changes has to be transferred.
After cutover completes successfully, host IOs are switched to the target side and the
import process completes automatically.
Format
/import/session/block -id <value> cutover [-async]
Object qualifier
Qualifier
Description
-id
Type the ID of the import session.
Action qualifier
Qualifier
Description
-async
Run the action in asynchronous mode.
Example
The following command cuts the import session, import_1, over to the target system:
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /import/session/
block -id import_1 cutover
Storage system address: 10.0.0.1
Storage system port: 443
HTTPS connection
Operation completed successfully.
Cancel a block import session
Cancel an existing block import session.
Cut over import session for block
59
Configure import using the CLI
Format
/import/session/block -id <value> cancel [-async]
Object qualifier
Qualifier
Description
-id
Type the ID of the import session.
Action qualifier
Qualifier
Description
-async
Run the action in asynchronous mode.
Example
The following command commits the block import session, import_1.
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /import/session/
block -id import_1 cancel
Storage system address: 10.0.0.1
Storage system port: 443
HTTPS connection
Operation completed successfully.
View import session elements
View details about import status for each element in the active import session, for
example, each LUN in a consistency group (CG).
Format
/import/session/element -importId <value> show
Object qualifier
Qualifier
Description
-importId
Type the ID of the import session.
Example
The following command displays import status for each element in the specified
import session:
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /import/session/
element -importId import_2 show -detail
Storage system address: 10.0.0.1
Storage system port: 443
HTTPS connection
1:
60
Source
Source
Target
Health
Health
system
resource
resource
state
details
=
=
=
=
=
RS_1
lun1
sv_1
OK (5)
"The component is operating normally. No
Unity Family 4.2 VNX Series Data Import to Unity All Flash or Hybrid, or UnityVSA System User Guide
Configure import using the CLI
action is required."
Stage
Iteration
Progress
Source system
Source resource
Target Resource
Health state
Health details
action is required."
Stage
Iteration
Progress
=
=
=
=
=
=
=
=
Incremental Sync
4
10%
RS_1
lun4
sv_2
OK (5)
"The component is operating normally. No
= Incremental sync
= 4
= 0%
View import session elements
61
Configure import using the CLI
62
Unity Family 4.2 VNX Series Data Import to Unity All Flash or Hybrid, or UnityVSA System User Guide
CHAPTER 6
Troubleshooting
This chapter addresses the following topics:
l
l
Information related to import operation problems.............................................. 64
VNX system with two Control Stations..............................................................65
Troubleshooting
63
Troubleshooting
Information related to import operation problems
Before you contact your service provider, use either Unisphere or the Unisphere CLI
to access information about jobs that failed and alert information and check the target
storage system's log files.
Jobs and Alerts information
Use Unisphere to get information about Jobs that fail. Under Events, select Jobs. Use
Jobs to view information on all jobs, including those jobs that are active and those jobs
that are complete or failed. To quickly determine the number of active jobs (those jobs
that are queued or running) and view job progress, use the Jobs icon in the status bar.
To view detailed information about the job, specifically the individual tasks included in
the job and the status of these tasks, select the Details icon. If a task fails, select View
Error for more information.
To get information about Jobs that fail, use the Unisphere CLI. To find the job that
failed, review the Jobs output. The following is an example:
C:>uemcli -d -u Local/admin -p /sys/task/job show
74:
ID
Type
Title
State
=
=
=
=
N-66
Replication Service
Create VNX remote system connection
Failed
Once you have the Job ID, you can retrieve more detailed information about the
failure. The following is an example:
C:>uemcli -d -u Local/admin -p /sys/task/job/step -jobId N-66 show detail
1:
Title
= Register VNX remote system
connection
Status
= Failed
Execution result code
= 105906574
Execution result description = An error occured while trying
to communicate with the remote VNX system. The credentials used
might be incorrect or there may be a network issue while connecting
to the remote VNX system. (Error Code:0x650018e)
Rollback result code
= 4106
Rollback result description = Task was rolled back and
marked as failed. This is because some tasks failed or SP rebooted
during task execution. (Error Code:0x100a)
Alerts provide you with information about the source of an event, the symptoms and
cause, and actions that you can take to resolve it. Any actions that are taken to
resolve an alert must be performed directly on the system on which the alert was
reported.
In Unisphere under Events, select Alerts. In addition to appearing on the Alerts page,
each alert generates a pop-up alert bubble in Unisphere. The alert bubble provides
information about the alert and may also contain a link to a help topic on how to
resolve the problem.
Use the Unisphere CLI commands /event/log show and /event/alert/hist
show to display additional event attributes that provide more detailed event reports
than what appear in Unisphere. For example:
64
Unity Family 4.2 VNX Series Data Import to Unity All Flash or Hybrid, or UnityVSA System User Guide
Troubleshooting
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /event/log show fromTime “2009-11-09 00:00:00.000” –to “2009-11-09 23:59:59.999”
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /event/alert/hist
show
For detailed information about Jobs and Alerts, refer to either the Unisphere Online
Help or the Unisphere Command Line Interface User Guide.
Log information
One of the most useful logs for reviewing errors that are related to setting the file
import connection or creating an import session, or any other file import task,
is /EMC/CEM/log/cemtracer_migration.log.
VNX system with two Control Stations
For a VNX system with two Control Stations, ensure that the following exists before
you set up a file-based import:
l
The home directory of a user with Administrator role exists on the primary Control
Station of the VNX. The home directory is used when you configure the import
connection.
l
When you configure other components for an import operation, the primary
Control Station of the VNX that is used must be the same Control Station as in the
previous bullet item.
You can retrieve information about the primary Control Station of the VNX system
using the VNX command line interface (CLI). The following CLI output is an example
that includes SPA, SPB, and the primary Control Station.
# naviseccli -User Local/joe -Password MyPassword456! -Scope 0 -h
10.50.100.104 domain -list
Node: APM00153042305
IP Address: 10.0.0.1 (Master)
Name: hop21130
Port: 80
Secure Port: 443
IP Address: 10.0.0.2
Name: hop21131
Port: 80
Secure Port: 443
IP Address: 10.0.0.3
Name: Unity_CS0_03
Port: 80
Secure Port: 443
If the primary Control Station of the VNX does not have a user home directory, you
can manually fail over the Control Station. The following is an example set up by
logging on the primary Control Station through SSH.
# /nas/sbin/cs_standby -failover
The system will reboot, do you wish to continue? [yes or no]: yes
Failing over from Primary Control Station...
For more information about this situation and how to resolve it, see Knowledge Based
Article 000489181.
VNX system with two Control Stations
65
Troubleshooting
66
Unity Family 4.2 VNX Series Data Import to Unity All Flash or Hybrid, or UnityVSA System User Guide
APPENDIX A
NFS-only VDM import details
This appendix addresses the following topics:
l
l
l
l
NFS-only VDM import work flow....................................................................... 68
View NFS-only VDM import information.............................................................73
File system mount options mapping................................................................... 74
NFS export options mapping.............................................................................. 74
NFS-only VDM import details
67
NFS-only VDM import details
NFS-only VDM import work flow
Most of the NFS-only VDM import operations are executed from the target Unity
storage system. However, some initial setup operations, such as creating an import
interface on the source VDM, must be executed on the source VNX system.
Prerequisites for an NFS-only VDM import session
Before starting an NFS-only VDM import session, the following conditions must be
met:
1. The source VNX system exists, and the VNX1 OE is 7.1.x or later or the VNX2 OE is
8.1.x or later.
2. (Optional) The specified name for the import session is not used by other import
sessions.
3. The source VDM exists, and is in the loaded state.
4. The source VDM is not under import or has an associated complete import.
5. The source VDM is not configured with CIFS servers, secured NFS, or NFSv4.
6. The maximum allowed deviation in time between the source side Data Mover (DM)
that hosts the VDM and the target side SP that hosts the target NAS server is 5
seconds.
7. There exists only one network interface whose name starts with nas_migration_xx
among all the up network interfaces that are attached to the source VDM. This
interface is used as the source import interface.
8. Verify that the physical Data Mover on which the source VDM is located, has at
least one IP interface configured that is not attached to the VDM being migrated.
9. One import interface of type replication exists on the default production port of
the target SP, uses the same IP protocol (IPv4 or IPv6) and is in the same VLAN
as the source import interface. The target import interface can reach the source
import interface and access all the source base exports. This interface can be
auto-detected, or specified as the target import interface.
10. The default target production port exists, and supports the type file.
11. All the specified target production ports in the interface-port pairs exist, support
the type file, and are on the same SP of the default target production port.
12. All the specified source production interfaces in the interface-port pairs exist, and
are in the up state.
13. The import interface on the source must be dedicated for only the import purpose.
Hosts must not use this interface for access. Ensure it is not used for any other
purpose, for example, used to export NFS exports or CIFS shares to hosts.
14. All the specified source file systems in the file system-pool pairs exist, and are
valid import candidates. (These import candidates are mounted to the source
VDM, and cannot be NMFS, replication destination, root file system, raw file
system, and non-imported FLR file system.).
15. The target pool that is specified to create the target NAS server exists.
16. All the specified target pools in the file system-pool pairs exist.
17. All the specified source file systems in the target VMware data store candidate
exist, and are valid import candidates.
68
Unity Family 4.2 VNX Series Data Import to Unity All Flash or Hybrid, or UnityVSA System User Guide
NFS-only VDM import details
18. There is no active import session on the SP of the default target production port.
19. If the import session is created, the total number of the import candidate source
file systems cannot exceed the limit of total file systems of all active sessions.
20. There is at least one valid source file system that is mounted on the source VDM.
21. There is at least one valid source production interface, which is up, attached to the
source VDM.
22. The total number of valid source production interfaces cannot exceed the limit of
network interfaces for each NAS server on the target Unity system.
23. The specified file systems to be imported as a VMware NFS data store should
have only one export at root directory.
24. NFS export does not contain an unsupported character or characters, such as
comma (,) or double quote (").
25. There are no NFS exports that were only temporarily un-exported and whose path
do not exist anymore. To check for this kind of export run the following command
on the control station: nas_server -query:name==vdm147 fields:exports -format:%q -query:IsShare==False fields:Path,AlternateName,Options -format:"<Path>%s</Path>
\n<AlternateName>%s</AlternateName>\n%s\n" Compare the resulting
list with the ouput of server_export. If there are some differences, you must
delete the old entry in the VDM in the vdm.cfg file. Do the following:
a. Login as root on the control station.
b. Go to the root file system of the VDM (cd /nas/quota/slot_X/
root_vdm_xx/.etc).
c. Edit the file vdm.cfg and remove the line corresponding to the NFS export that
you want to clean (vi vdm.cfg export "/fs4" anon=0).
d. Check that the export does not appear any more in the nas_server -query.
You do not need to reboot the VDM.
Change settings of an NFS-only VDM import
You can change some import settings before the import session starts or during an
initial copy failed status. The changeable parameters include:
l
Pools of the target file system
l
Pool of the target NAS server
l
Ports of the target production interfaces
l
Mobility interface for import
l
Name of import session
Note
The import session name is not limited to an import session start or during an initial
copy failed status and can be changed at any time.
The following changes on the source system are discouraged during an import session:
l
Changes to Quota settings
l
NIS or LDAP configuration changes
l
DNS, gateway, or routing changes
Change settings of an NFS-only VDM import
69
NFS-only VDM import details
l
Creating or deleting file systems
The target system cannot prevent these actions on the source system. However,
these actions can result in the changes not being imported to the target system and
causing the import session to fail.
Start an NFS-only VDM import session
The import session is automatically started after creation in the Unisphere UI.
For UEMCLI or REST, the UEMCLI command and REST operation of start are shared
with the same command and operation of resume to align with the behavior of block
import and replication. You can only start an import session when it is in the Initialized
state. If the import start fails, the import state is kept as Initial Copy with a Minor
failure health state and the health details are set to The migration session
failed to provision target resource. At this time, you can fix the problem
by getting detailed information from the job and tasks and then resume the import
session.
The start of an import session is an asynchronous operation by default and always
returns a success after creating a backend job to run the initial copy. Before the start
of the import, a pre-check is done.
In the event of an SP reboot, affected import sessions fail over to the peer SP. In the
event of a system reboot, import sessions pause and automatically resume when the
system returns.
NFS-only VDM import initial copy
After the start of the import, VDM import enters the initial copy state. The initial copy
consists of three sequential stages:
1. Target NAS server and file system (thin file systems) provisioning
2. Initial data copy
3. Configuration import
Target provisioning
The following is the sequence of provisioning of the NAS server and file systems (thin
file systems) in the target system:
1. The import session is validated to be initialized and all parameters are set
correctly.
2. The target NAS server is created in import target mode with the correct name.
3. The target file system or file systems are created in import target mode with
correct names that exactly match the source mount path.
4. The quota information is dumped from the source file system or file systems to the
matching target file system or file systems. If the file system is imported as a
VMware NFS data store on Unity, quotas import dumping is skipped.
5. A private server is set up for data transfer from the source NFS server to the
target SP. The source VDM exports are updated to include the target import IP
address at the file system root directory.
6. The file system level import session between source side file system and the target
side file system are created and started.
7. The auto-retry mechanism is started.
Initial copy
Once the import target NAS server and file systems are provisioned, the initial copy
job creates and starts the file system level import sessions for the initial data copy
70
Unity Family 4.2 VNX Series Data Import to Unity All Flash or Hybrid, or UnityVSA System User Guide
NFS-only VDM import details
between the source and target file systems. Initial copy does not enter the
Configuration Import stage until all file systems are migrated.
Configuration import
The initial copy job task continuously runs while waiting for the completion of the
baseline copy. Once the baseline copy is complete, it stops the auto-retry mechanism
and starts the configuration import (configuration import task). The VDM
configuration that is imported ensures that the NAS server on the target system
works correctly. The VDM configuration includes:
l
NFS export
l
Network interface
l
Route configuration
l
IP reflect parameter
l
DNS configuration
l
Local file
l
LDAP configuration
l
NIS configuration
l
UNIX Directory Service setting
l
Quota configuration
Once the configuration import completes, the initial copy job prepares for cutover to
reduce the overall time and the DU time for cutting over. After the configuration
import completes, the file import session enters the Ready to Cutover state. If import
failed during initial copy, the configuration import is not rolled back. You can resume
the import operation after fixing the reported issues, and import start can continue
from the last point when it failed.
NFS-only VDM import cutover
Before you run the cut over operation, ensure the following:
l
The source VDM has not been deleted or renamed before cutover.
l
The file system that is mounted on the source VDM has not been renamed,
unmounted, or deleted.
l
The source VDM interface has not been deleted or renamed.
When the initial copy has completed, the file import session enters the Ready to
Cutover state. You can switch the production VDM from source to target so that the
target side NAS server becomes the production side with all data synchronized. The
cutover should be transparent to the users. After cutover, the NFS host clients can
access the new production side without requiring a remount.
You can launch cutover from either Unisphere, UEMCLI, or REST. Cutover starts a
job, which does the following:
1. A pre-cutover validation check.
2. Freeze the source network lock files for import. The job tries to get all the NLM
data from the source VDM and import it to the target system.
3. Freeze the source file systems (frozen file systems ignore NFS request, NFSv3
lock request, and denies NLM lock).
4. Turn down the source client interface or interfaces (public IP interface).
NFS-only VDM import cutover
71
NFS-only VDM import details
5. Unfreeze source file systems.
6. Turn up the target interface or interfaces (public IP interface).
7. Reclaim network lock files in the target system. The job tries to revive all imported
lock files in the target system.
8. Start an incremental copy.
NFS-only VDM import incremental copy
Incremental copy starts after the cutover to the target storage system. It
synchronizes any data updates in the source after the initial data copy starts and
before cutover. During the incremental copy, all data writes to target storage system
are synchronized back to the source as well to guarantee that the data is identical
between the source VDM and target NAS server. Pause and resume operations are
supported during the incremental copy.
Note
The data change synchronized back to the source storage system cannot be paused.
During incremental copy, quota import disables online quota check. It is resumed
during import committing.
NFS-only VDM import commit
When all data is synchronized between the source VDM and target NAS server, the
import session enters the Ready to commit state. You can complete the import
through Unisphere or by running the commit command in UEMCLI or REST.
After the commit operation completes, the new data update on the production
(target) NAS server is no longer synchronized back to the source VDM. All import
specific resources, such as NAS server, file systems, production interfaces, are
cleaned up on the target system. The exceptions to this process are the import
session information and the summary report. That data is removed when the import
related source storage system is deleted from the target storage system. Because the
source VDM is obsolete, the import temporary changes on the source VDM are not
cleaned up during import commit. You cannot cancel the import session and rollback
the imported NAS server to the source VDM after the import session is committed.
NFS-only VDM import pause
You can pause an import session during the Initial Copy state (internally provisioning
target, initial copy, or import configuration) and the Incremental Copy state through
Unisphere, UEMCLI, or REST. This operation is useful when the network load is too
heavy. If the import session is in the Initial Copy state, the pause operation fails the job
executing the Initial Copy. When the import session is paused, the session state
remains unchanged but the health state is not OK. A paused import session can be
resumed.
NFS-only VDM import resume
You can resume a paused import session through Unisphere, UEMCLI, or REST. The
Resume and Start operation (resume an initialized session) actually share the
command. Similar to the Pause operation, the Resume command returns immediately,
and then the file system level import sessions resume one by one internally. The whole
import session returns to the running state when all the underlying file system import
sessions are resumed. It may take a while for the import session health state to
72
Unity Family 4.2 VNX Series Data Import to Unity All Flash or Hybrid, or UnityVSA System User Guide
NFS-only VDM import details
change to the expected OK state. Use the Resume operation to restart the data
transfer or configuration import when the import session fails and the reason for the
failure has been fixed.
NFS-only VDM import cancel
Any time during the import, except the cutting over and committing phase, you can
decide to cancel an ongoing import session. Depending on which state the import
session is in, canceling the import session has different meanings:
l
Before import start, the import session is deleted.
l
After the import starts and before cutover:
l
n
Stops data copy
n
Cleans up the copied data and imported configuration data
n
Cleans up the migrating NAS Server and file systems except the user created
file systems
After cutover and before committing:
n
Stops data copy and data sync
n
Rollbacks to source VDM
n
Cleans up the copied data and imported configuration data
n
Cleans up the importing NAS server and file systems except the user created
file systems
Hosts that are created for NFS exports during the import are not cleaned up. If the
user creates file systems after import cutover, these file systems and the target NAS
server are kept while the target production interfaces are removed. If the import to
the NAS server is kept due to user created file systems, the imported configuration
(UNIX Directory service, DNS) is kept as well.
View NFS-only VDM import information
You can view VDM import session information from Unisphere, UEMCLI, or REST.
After an import session is created, you can query the progress of the session from
UEMCLI or REST. However, this property is only valid when the session is in the Initial
Copy phase or Incremental Copy phase:
l
When the VDM import session is in the Initial Copy phase, the progress reflects
the progress of the whole initial copy, including initial data copy, configuration
import, and quota configuration import.
l
When the VDM import session is in the Incremental Copy phase, the progress just
reflects the progress of the incremental data copy.
Import Summary Report
The Import Summary Report provides information about the import session. The
report can be downloaded during any of the various stages of the Import process (for
example, during Initial Copy, Syncing, Paused, Ready to Cutover, Ready to Commit
states, Canceled, Completed). This report can be meaningful when reviewing or
troubleshooting import session progress. In Unisphere, after creating an import
session, go to More Actions > Download Summary Report, which produces a Zip file
that can be downloaded to the host system. The most relevant file from the download
is the SummaryReport.html.
NFS-only VDM import cancel
73
NFS-only VDM import details
File system mount options mapping
Many of the mount options for VNX storage systems are not supported on Unity
storage systems. Table 1 on page 74 maps the VNX mount options that Unity
supports.
Table 1 Mount option mapping between VNX and Unity
VNX
Unity
Comment
mover_name
vdm
fs_name
description
mount_point
name
Ro
rw
Unity always uses rw. See Ro mount option special
handling.
Rw
rw
Unity always uses rw.
Ro mount option special handling
If a file system is mounted on a VNX with the Ro option, the NFS exports that are
created from this file system are actually read-only to their clients. The clients
although are granted read/write or root privilege.
After import, the NFS shares that are imported to the Unity system will be roexported. If the default access is rw or root, it is degraded to ro (read-only). If default
access is na (no access), it remains unchanged. All rw or root host entries that are
configured on these NFS shares are degraded to roHosts so that the NFS shares will
still be read-only to their clients.
For example, if source VNX export option is access=<IP>, only this IP has access
permission, other clients cannot access the export. The NFS share configuration on
Unity would be: defAccess=na, roHost=<IP>.
If source VNX export option is root=<IP>, the IP has root permission, other clients
have rw permission to this export. The NFS share configuration on Unity would be:
defAccess=ro, roHost=<IP>.
NFS export options mapping
Some of the NFS export options for VNX storage systems are not supported on Unity
storage systems. Table 2 on page 74 maps the VNX NFS export options that Unity
supports.
Table 2 NFS export option mapping between VNX and Unity
VNX (server_export option)
Description
Unity (/stor/prov/fs/
nfs)
Sec=sec
AUTH_SYS(default)
-minSecurity sys
ro
Exports the <pathname> for all NFS clients as read-only.
-defAccess ro
ro=<client>[:<client>]
...
Exports the <pathname> for the specified NFS clients as
read-only.
-roHosts
74
Unity Family 4.2 VNX Series Data Import to Unity All Flash or Hybrid, or UnityVSA System User Guide
NFS-only VDM import details
Table 2 NFS export option mapping between VNX and Unity (continued)
VNX (server_export option)
Description
Unity (/stor/prov/fs/
nfs)
rw=<client>[:<client>]
...
Exports the <pathname> as read-mostly for the specified
NFS clients.
-rwHosts &&-defAccess
ro
root=<client>[:<client
>]...
Provides root privileges for the specified NFS clients.
-rootHosts
access=<client>[:<clie
nt>]...
Provides mount access for the specified NFS clients.
roHosts, rwHosts
access=<-client>[:<client>]
Excludes the specified NFS clients from access even if they
are part of a subnet or netgroup that is allowed access.
No access
ro=<-client>[:<client>]
Excludes the specified NFS clients from ro privileges.
No access
rw=<-client>[:<client>]
Excludes the specified NFS clients from rw privileges.
No access
root=<-client>[:<client>]
Excludes the specified NFS clients from root privileges.
No access
-comment
Comment for the specified NFS export entry.
-descr
NFS export options mapping
75
NFS-only VDM import details
76
Unity Family 4.2 VNX Series Data Import to Unity All Flash or Hybrid, or UnityVSA System User Guide
APPENDIX B
CIFS-only VDM import details
This appendix addresses the following topics:
l
l
CIFS-only VDM import work flow.......................................................................78
View CIFS-only VDM import information............................................................86
CIFS-only VDM import details
77
CIFS-only VDM import details
CIFS-only VDM import work flow
Most of the CIFS-only VDM import operations are executed from the target Unity
storage system. However, some initial setup operations, such as creating an import
interface on the source VDM, must be executed on the source VNX system.
Prerequisites for a CIFS-only VDM import session
Before starting a CIFS-only VDM import session, the following conditions must be
met:
1. The source VNX system exists, and the VNX1 OE is 7.1.x or later or the VNX2 OE is
8.1.x or later.
2. (Optional) The specified name for the import session is not used by other import
sessions.
3. The source VDM exists, and is in the loaded state.
4. The source VDM is not under import or has an associated complete import.
5. The source VDM does not have any NFS exports.
6. The maximum allowed deviation in time between the source side Data Mover (DM)
that hosts the VDM and the target side SP that hosts the target NAS server is 5
seconds.
7. There exists only one network interface whose name starts with nas_migration_xx
among all the up network interfaces that are attached to the source VDM. This
interface is used as the source import interface.
8. Verify that the physical Data Mover on which the source VDM is located, has at
least one IP interface configured that is not attached to the VDM being migrated.
9. One import interface of type replication exists on the default production port of
the target SP, uses the same IP protocol (IPv4 or IPv6) and is in the same VLAN
as the source import interface. The target import interface can reach the source
import interface. This interface can be auto-detected, or specified as the target
import interface.
10. The default target production port exists, and supports the type file.
11. All the specified target production ports in the interface-port pairs exist, support
the type file, and are on the same SP of the default target production port.
12. All the specified source production interfaces in the interface-port pairs exist, and
are in the up state.
13. The import interface on the source must be dedicated for only the import purpose.
Hosts must not use this interface for access. Ensure it is not used for any other
purpose, for example, used to export NFS exports or CIFS shares to hosts.
14. All the specified source file systems in the file system-pool pairs exist, and are
valid import candidates. (These import candidates are mounted to the source
VDM, and cannot be NMFS, replication destination, root file system, raw file
system, and non-imported FLR file system.).
15. The target pool that is specified to create the target NAS server exists.
16. All the specified target pools in the file system-pool pairs exist.
17. All the specified source file systems in the target VMware data store candidate
exist, and are valid import candidates.
78
Unity Family 4.2 VNX Series Data Import to Unity All Flash or Hybrid, or UnityVSA System User Guide
CIFS-only VDM import details
18. There is no active import session on the SP of the default target production port.
19. If the import session is created, the total number of the import candidate source
file systems cannot exceed the limit of total file systems of all active sessions.
20. There is at least one valid source file system that is mounted on the source VDM.
21. There is at least one valid source production interface, which is up, attached to the
source VDM.
22. The total number of valid source production interfaces cannot exceed the limit of
network interfaces for each NAS server on the target Unity system. Refer to the
Unity Support Matrix on Online Support for information about network interface
limits related to NAS servers.
23. A single CIFS server is configured on the source VDM.
24. C$ share is available on the source Data Mover that hosts the VDM and is not
disabled or set to Read-only. The C$ share must be available, otherwise the import
cannot start. If it was disabled or Read-only on the source, change the
corresponding parameters to enable it:
server_param <source_server> -facility cifs -modify
admin.shareC_NotCreated -value 0
server_param <source_server> -facility cifs -modify
admin.shareC_RO -value 0
Note
You must stop and start the service associated with the CIFS facility for changes
to admin.shareC_NotCreated to take effect.
25. Local SMB users are enabled on the source CIFS server.
26. The user performing the import must belong to the source local administrator
group and has backup and restore privileges.
27. The extended acl feature is enabled on the source Data Mover that hosts the VDM
(parameter cifs.acl.extacl should have bits 2, 3, and 4 set, decimal value 28). Use
the following command to view the settings:
server_param <source_datamover> -facility cifs -info acl.extacl
If necessary, use the following command to change the setting:
server_param <source_datamover> -facility cifs -modify
acl.extacl -value 28
28. Unknown SID feature has been enabled on the source Data Mover that hosts the
VDM (parameter cifs.acl.mappingErrorAction must be set to 0x0b, decimal value
11). Use the following command to view the settings:
server_param <source_datamover> -facility cifs -info
acl.mappingErrorAction
Prerequisites for a CIFS-only VDM import session
79
CIFS-only VDM import details
If necessary, use the following command to change the setting:
server_param <source_datamover> -facility cifs -modify
acl.mappingErrorAction -value 11
29. NT security is enabled on the source. Share and Unix security level is not
supported.
30. The source VDM is not utf8-based.
31. The source CIFS server is not a Windows NT 4.0 like CIFS server.
32. DNS is configured for the Windows domain in the case of a domain joined CIFS
server.
33. Other VDMs from the source can reach DNS and domain controller (DC) after
cutover.
34. DNS and DCs are reachable on the destination after cutover.
Change settings of a CIFS-only VDM import
You can change some import settings before the import session starts or during an
initial copy failed status. The changeable parameters include:
l
Pools of the target file system
l
Pool of the target NAS server
l
Ports of the target production interfaces
l
Mobility interface for import
l
Name of import session
l
SMB credentials used by the target system to connect to the source CIFS server.
Note
The import session name is not limited to an import session start or during an initial
copy failed status and can be changed at any time.
The following changes on the source system are discouraged during an import session:
l
Changes to Quota settings
l
DNS, gateway, or routing changes
l
Creating or deleting file systems
The target system cannot prevent these actions on the source system. However,
these actions can result in the changes not being imported to the target system and
causing the import session to fail.
Start a CIFS-only VDM import session
The import session is automatically started after creation in the Unisphere UI.
For UEMCLI or REST, the UEMCLI command and REST operation of start are shared
with the same command and operation of resume to align with the behavior of block
import and replication. You can only start an import session when it is in the Initialized
state. If the import start fails, the import state is kept as Initial Copy with a Minor
failure health state and the health details are set to The migration session
failed to provision target resource. At this time, you can fix the problem
by getting detailed information from the job and tasks and then resume the import
session.
80
Unity Family 4.2 VNX Series Data Import to Unity All Flash or Hybrid, or UnityVSA System User Guide
CIFS-only VDM import details
The start of an import session is an asynchronous operation by default and always
returns a success after creating a backend job to run the initial copy. Before the start
of the import, a pre-check is done.
In the event of an SP reboot, affected import sessions fail over to the peer SP. In the
event of a system reboot, import sessions pause and automatically resume when the
system returns.
CIFS-only VDM import initial copy
After the start of the import, VDM import enters the initial copy state. The initial copy
consists of three sequential stages:
1. Target NAS server and file system (thin file systems) provisioning
2. Initial data copy
3. Configuration import
Target provisioning
The following is the sequence of provisioning of the NAS server and file systems (thin
file systems) in the target system:
1. The import session is validated to be initialized and all parameters are set
correctly.
2. The target NAS server is created in import target mode with the correct name.
3. The target file system or file systems are created in import target mode with
correct names that exactly match the source mount path.
4. All network interfaces of the source VDM are cloned into the target NAS server.
All interfaces are created in disabled mode.
5. All network routing tables relative to the source VDM interfaces are cloned at the
destination.
6. (This step is only applicable when the SMB server is joined to a domain.) The DNS
domain and its corresponding servers are selected from the source VDM and set at
the target NAS server. The DNS domain is selected as follow:
l
The DNS domain configured at the VDM level (nsdomain).
l
The DNS domain at the storage system level matching exactly the domain
name of the VDM's SMB server.
In any other cases, the pre-check fails.
7. The SMB protocol is enabled on the target NAS server and the source CIFS server
configuration is cloned.
Note
All network interfaces that are attached to the source VDM are added to the
target SMB server regardless whether they were or were not at the CIFS server of
the source VDM.
8. The quota information is dumped from the source file system or file systems to the
matching target file system or file systems. If the file system is imported as a
VMware FS data store on Unity, quotas import dumping is skipped.
9. Copy data of all the file systems from the source to the target file systems. The
whole directory and file structure of the file system is parsed and cloned at the
destination. However, only cold data (data not modified within one hour) is copied.
Data that cannot be accessed is skipped during initial copy.
CIFS-only VDM import initial copy
81
CIFS-only VDM import details
Note
Parsing is done only once. If files or directories are created after the parsing is
done, those new nodes are migrated during the incremental copy.
10. Local groups and users are migrated before the CIFS shares.
11. All CIFS shares of the source VDM are cloned into the target NAS server.
12. Source parameters that are migrated during migration of CIFS-only VDM include:
l
acl.extAcl
l
acl.restrictedTakeOwnership
l
admin.shareC_NotCreated
l
admin.shareC_RO
l
allowSnapSureVss
l
cifsclient.timeout
l
LanmanServer.disableNameChecking
l
LanmanServer.IdleUserAutoLogoff
l
LanmanServer.MaxMpxCount
l
nullSession
l
ReadOnly.Comp
l
ReadOnly.Delete
l
set_eas_ok
l
smbsigning
l
srvmgr.diskdrive
l
srvpwd.updtMinutes
l
windowsTimeUpdate
l
virtualDirName
l
updateMode
l
updatePTRrecord
l
cacheMaxGroups
l
cacheMaxHosts
l
SecurityLayer
l
maxNISCacheGroupsCount
l
maxNISCacheUsersCount
l
followabsolutpath
l
followdotdot
l
Traces
After the parameter values are applied, the NAS server is restarted to take the
new values into account.
If import failed during initial copy, the configuration import is not rolled back. You can
resume the import operation after fixing the reported issues, and import start can
continue from the last point when it failed.
82
Unity Family 4.2 VNX Series Data Import to Unity All Flash or Hybrid, or UnityVSA System User Guide
CIFS-only VDM import details
CIFS-only VDM import cutover
Before you run the cut over operation, ensure the following has not occurred:
l
The source VDM has not been deleted or renamed before cutover.
l
The file system that is mounted on the source VDM has not been renamed,
unmounted, or deleted.
l
The source VDM interface has not been deleted or renamed.
l
The source SMB server has not been renamed.
When the initial copy has completed, the file import session enters the Ready to
Cutover state. You can switch the production VDM from source to target so that the
target side NAS server becomes the production side with all data synchronized. During
the cutover, the I/O of SMB host clients to the VDM under import will be interrupted
and a short period of data unavailability (DU) will be observed. After cutover, the SMB
host clients can access the new production side without requiring a remount.
You can launch cutover from either Unisphere, UEMCLI, or REST. Cutover starts a
job, which does the following:
1. A pre-cutover validation check.
2. Forces an CIFS server account password update before the cutover.
Note
Not applicable for a standalone CIFS server.
3. All production network interfaces of the source VDM are disabled. CIFS clients
cannot access data. Only the import network interface remains up.
Note
Data Unavailable (DU) time is impacted by following factors:
l
Number of production client interfaces
l
Number of shares
l
Time to rename and join the source server
4. The local group database file, /.etc/.db.5.localgroups, is copied from the source
VDM to the target NAS Server.
5. The home directory configuration, which is located in /.etc/homedir, is copied
from the source VDM to the target NAS Sever.
6. The Kerberos configuration file, /.etc/krb5.conf, and the file containing the CIFS
account, /.etc/krb5.account, are copied from the source to the target. After the
cutover, regular SMB clients can have access to the SMB server at the target in
the same way as on the source.
Note
Not applicable for a standalone CIFS server.
7. A new CIFS share synchronization is done with the source to get any updates
since the initial share migration was done at the beginning of the initial copy phase.
8. Permission to all the source's CIFS shares is changed to deny any access. This
action is taken to prevent any host access to the source VDM data after the
cutover.
CIFS-only VDM import cutover
83
CIFS-only VDM import details
9. The source CIFS server is renamed to an alternate name that is provided by the
administrator.
10. The production interfaces are enabled at the target. DU ends and clients accesses
are now directed to the target.
11. Start the incremental copy phase.
Note
Data that was not copied during initial copy phase can be accessed after the cutover.
The migration process redirects any I/O operations to non-migrated data to the
source VDM, unless it is migrated.
CFS-only VDM import incremental copy
Incremental copy starts after the cutover to the target storage system. It
synchronizes again the target with the source to ensure that all nodes and data that
were not migrated during the intial copy phase or updated after it, are migrated to the
target. During the incremental copy, all data writes to the target storage system are
synchronized back to the source as well to guarantee that the data is identical
between the source VDM and target NAS server. This operation ensures data
integrity, no data loss, in case the migration session is cancelled after the cutover.
Pause and resume operations are supported during the incremental copy. However,
only the incremental copy process can be paused, data synchronizing between the
target and source is always running.
During incremental copy, quota import disables online quota check. It is resumed
during import committing.
To ensure that the source is always synchronized with the target (for example, to be
able to cancel the migration), any change to the target file system is first done at the
source file system.
Note
If the modification at the source fails, the modification is not applied at the target and
an error is returned to the SMB client. If the source becomes unreachable, the user
data becomes unavailable from the target.
CIFS-only VDM import commit
When all data is synchronized between the source VDM and target NAS server, the
import session enters the Ready to commit state. You can complete the import
through Unisphere or by running the commit command in UEMCLI or REST.
After the commit operation completes, the new data update on the production
(target) NAS server is no longer synchronized back to the source VDM. All import
specific resources, such as NAS server, file systems, production interfaces, are
cleaned up on the target system. The exceptions to this process are the import
session information and the summary report. That data is removed when the import
related source storage system is deleted from the target storage system. Because the
source VDM is obsolete, the import temporary changes on the source VDM are not
cleaned up during import commit. You cannot cancel the import session and rollback
the imported NAS server to the source VDM after the import session is committed.
84
Unity Family 4.2 VNX Series Data Import to Unity All Flash or Hybrid, or UnityVSA System User Guide
CIFS-only VDM import details
CIFS-only VDM import pause
You can manually pause an import session during the Initial Copy state and
Incremental Copy state through Unisphere, UEMCLI, or REST. The whole import
session is paused when all the underlying file system import sessions are paused.
When the import session is paused, the session state remains unchanged but the
health state is not OK. A paused import session can be resumed.
Pause during initial copy suspends the migration of the cold data (data not modified
within one hour) from the source to the target.
Pause during incremental copy only pauses the data copy of hot data (data that
changed during the baseline copy and data that was not accessible during the Initial
Copy phase). The data change to the target is still synchronized with the source so
that the target system is still usable by the SMB clients and rollback is allowed with
data consistency.
CIFS-only VDM import resume
You can resume a paused import session through Unisphere, UEMCLI, or REST. The
Resume and Start operation (resume an initialized session) actually share the same
command. Similar to the Pause operation, the Resume command returns immediately,
and then the file system level import sessions resume one by one internally. The whole
import session returns to the running state when all the underlying file system import
sessions are resumed. It may take a while for the import session health state to
change to the expected OK state. Use the Resume operation to restart the data
transfer or configuration import when the import session fails and the reason for the
failure has been fixed.
CIFS-only VDM import cancel
Any time during the import, except the cutting over and committing phase, you can
decide to cancel an ongoing import session. Depending on which state the import
session is in, canceling the import session has different meanings:
l
Before import start, the import session is deleted.
l
After the import starts and before cutover:
n
Stops data copy
n
Cleans up the copied data and imported configuration data
n
Cleans up the migrating NAS Server and file systems except the user created
file systems
Note
CIFS clients still access the source and the source configuration is intact.
l
After cutover and before committing, the SMB migration synchronizes back to the
source some configuration changes made at the target after the cutover:
n
All network interfaces are disabled at the target. The DU starts from there.
n
All file system data migration is stopped. The data on the source file system are
in synchronization with the data on the target file system.
n
The SMB server Active Directory (AD) account is copied back to the source.
The source can reuse the AD account without any change in AD.
CIFS-only VDM import pause
85
CIFS-only VDM import details
n
The CIFS server at the source is renamed to the production name of the CIFS
server. There is no join. The CIFS can reuse the AD account without any
change.
Note
Since AES256 is not supported on the VNX, regular CIFS clients may need to
clear their kerberos cache (klist purge) to be able to re-connect.
n
The home directory file at the target is copied back to the source.
n
Any add, delete, or update of shares done at the target during the incremental
copy, are propagated back to the source (including Access Control List (ACL)).
There are several limitations relative to Distributed File System (DFS):
– Only DFS links of pre-existing DFS shares at the source are synced.
– DFS shares that are created during incremental copy will be non DFS on
source.
– DFS shares that were DFS at the source will stay DFS
n
Re-enable all production interfaces at the source.
n
The source VDM is restarted to take all configuration updates into account.
The DU ends at the end of this step.
n
The NAS server and file systems at the target are deleted.
Note
The import session is not destroyed to keep access to the downloadable import
report.
If the user creates file systems after import cutover, these file systems and the target
NAS server are kept while the target production interfaces are removed.
View CIFS-only VDM import information
You can view VDM import session information from Unisphere, UEMCLI, or REST.
After an import session is created, you can query the progress of the session from
UEMCLI or REST. However, this property is only valid when the session is in the Initial
Copy phase or Incremental Copy phase:
l
When the VDM import session is in the Initial Copy phase, the progress reflects
the progress of the whole initial copy, including initial data copy, configuration
import, and quota configuration import.
l
When the VDM import session is in the Incremental Copy phase, the progress just
reflects the progress of the incremental data copy.
Import Summary Report
The Import Summary Report provides information about the import session. The
report can be downloaded during any of the various stages of the Import process (for
example, during Initial Copy, Syncing, Paused, Ready to Cutover, Ready to Commit
states, Canceled, Completed). This report can be meaningful when reviewing or
troubleshooting import session progress. In Unisphere, after creating an import
session, go to More Actions > Download Summary Report, which produces a Zip file
that can be downloaded to the host system. The most relevant file from the download
is the SummaryReport.html.
86
Unity Family 4.2 VNX Series Data Import to Unity All Flash or Hybrid, or UnityVSA System User Guide
APPENDIX C
LUN or Consistency Group of LUNs import
details
This appendix addresses the following topics:
l
LUN or Consistency Group of LUNs import work flow....................................... 88
LUN or Consistency Group of LUNs import details
87
LUN or Consistency Group of LUNs import details
LUN or Consistency Group of LUNs import work flow
All LUN or Consistency Group (CG) import operations are executed from the target
Unity storage system.
Prerequisites for a LUN or CG import session
Before starting a LUN or CG import session, the following conditions must be met:
1. The source VNX system exists, and the VNX1 Block OE is 5.32.x or later or the
VNX2 Block OE is 5.33.x or later.
2. (Optional) The specified name for the import session is not used by other import
sessions.
3. SAN Copy is enabled on the source VNX system.
4. The source LUN or CG exists.
5. The source LUN or CG is not under import or has an associated complete import.
6. Depending on the type of import connection that is used between the source and
target systems:
l
For an import using an FC-based connection, FC ports are cabled and ports
zoning is configured between the VNX and Unity storage systems.
Note
Avoid ports that are used for host traffic and MirrorView. On the VNX, SAN
Copy and MirrorView configured on the same ports do not operate. Import
connections cannot be configured. Configure and cable the source SPA FC_1
and SPB FC_1 ports to the target SPA FC_1 and SPB FC_1 ports for SAN
Copy. Also, avoid ports that are used for synchronous replication.
l
l
For an import using an iSCSI-based connection, iSCSI interfaces are configured
on both the source and target systems.
n
Configure iSCSI IP interfaces on SPA and SPB on the source system. Avoid
MirrorView reserved iSCSI ports for block import iSCSI interfaces.
n
Configure iSCSI IP connections between the source and target systems and
verify the connection configuration.
Once the import connections are created, the following has occurred:
n
Management IP connectivity and VNX Admin credentials are verified.
n
VNX SAN Copy FC or iSCSI initiators are discovered and registered.
n
All block resources on the source system that are eligible for import are
discovered.
Note
The discovered objects and their relationships persist.
7. A reserved LUN pool (RLP) is configured:
Note
The size of the RLP LUN created for a source LUN is recommended to be 20% of
the size of the source LUN.
88
Unity Family 4.2 VNX Series Data Import to Unity All Flash or Hybrid, or UnityVSA System User Guide
LUN or Consistency Group of LUNs import details
l
For the import of a single LUN, one RLP LUN is configured.
l
For the import of a CG of LUNs, one RLP LUN is configured for each LUN in
the CG.
Note
An RLP LUN is not tagged to a source LUN for a specific feature. When an RLP
LUN is added to an RLP that is intended for a source LUN, it is possible that a
completely different SnapView or other SAN Copy session can consume the newly
added RLP LUN. It is recommended that other features like SnapView and
MirrorView/A are stopped during import.
8. Configure hosts on the target system the same as the hosts or storage groups on
the source system.
Note
For iSCSI hosts, the hosts should log in to the target system to register the host
initiators on the target system.
Start a LUN or CG import session
The import session is automatically started after creation in the Unisphere UI.
For UEMCLI or REST, the UEMCLI command and REST operation of start are shared
with the same command and operation of resume to align with the behavior of VDM
import and replication. If the import start fails, the import state is kept as Initial Copy
with a Minor failure health state and the health details being set to The import
session failed to provision target resource. At this time, you can fix
the problem by getting detailed information from the job and tasks and then resume
the import session.
The start of an import session is an asynchronous operation by default and always
returns a success after creating a backend job to run the initial copy. Before the start
of the import, a pre-check is done.
In the event of a system reboot, import sessions are paused and resume automatically
when the system returns. Affected LUNs may fail over to the peer SP. If a LUN is
failed over, it would need to be failed back and the session resumed.
LUN or CG import initial copy
When the import session starts, it enters the initial copy state. The target resource
(LUN or CG) is automatically created on the selected target pool from the respective
source LUN or CG and balanced between the target SPs. The SAN Copy limits that
are configured on the source system are used to schedule syncs:
1. From the current SP of the LUN or LUNs in the import session, separate lists are
created for SPA and SPB LUNs from which to find the counts for each SP.
2. If there are available differential sync slots from the concurrent SAN Copy sync
limits, the slots are allocated so from SPA and SPB and the session is changed
from the Pending to Syncing state.
Start a LUN or CG import session
89
LUN or Consistency Group of LUNs import details
Note
Once slots from SPA and SPB are allocated to an import session, no other session
can take those slots until either the session is canceled or completed. If the
session is canceled or completed, the slots are distributed to either existing
sessions (if they can benefit from it) or new pending sessions.
3. Once the import session reaches below the cutover threshold (percentage of data
remaining to be copied), the session is changed from the Syncing to Ready for
Cutover state.
LUN or CG import cutover
When the initial copy has completed, the LUN or CG import session enters the Ready
to Cutover state. Before you run the cutover operation, ensure that the import session
exists and is in the Cutover Ready state.
You can launch cutover from either Unisphere, UEMCLI, or REST. Cutover starts a
job, which does the following:
l
Host access on VNX Source system for source LUN or LUNs is disabled for all
hosts by removing source LUN or LUNs from Host SGs.
Note
It is required that all Host I/O be paused before cutover is issued.
90
l
Differential sync for SAN Copy session is run to sync the last delta.
l
SAN Copy session is deleted.
l
Host access to target LUN or LUNs is enabled for the selected hosts that are
configured on the target system.
Unity Family 4.2 VNX Series Data Import to Unity All Flash or Hybrid, or UnityVSA System User Guide
Download PDF
Similar pages
1993 Paper 11 Question 3
proximity series sliding mounting plate
AudioQuest 3881140095
VDM Digital Multiplexer Recorder
NGS Black Shadow
VDX_Product_Bulletin_v2
NGS Pop Live
AudioQuest VDM-5
NGS Flick-W