PDFUse Cases
Pool use cases
This section describes different CLI use cases for pools.
Create a pool using drives with specific characteristics
This example applies to hybrid Flash arrays, which only support traditional pools.
Retrieve the list of storage profiles
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /stor/config/profile -configurable show
Storage system address: 10.0.0.1
Storage system port: 443
HTTPS connection
1: ID = profile_22
Description = SAS RAID5
Drive type = SAS
RAID level = 5
Maximum capacity = 4611148087296 (4.1T)
Stripe length = Maximum capacity
Disk group = dg_16
Maximum drives to configure = 5
Maximum capacity to configure = 1884243623936 (1.7T)
2: ID = profile_30
Description = SAS RAID10 (1+1)
Drive type = SAS
RAID level = 10
Maximum capacity = 9749818597376 (8.8T)
Stripe length = 2
Disk group = dg_13, dg_15
Maximum drives to configure = 10, 10
Maximum capacity to configure = 1247522127872 (1.1T), 2954304921600 (2.6T)
3: ID = profile_31
Description = SAS RAID10 (2+2)
Drive type = SAS
RAID level = 10
Maximum capacity = 9749818597376 (8.8T)
Stripe length = 4
Disk group = dg_13, dg_15
Maximum drives to configure = 8, 8
Maximum capacity to configure = 2363443937280 (2.1T), 952103075840 (886.7G)
Configure a new pool
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /stor/config/pool create -name MyPool -description "My custom pool" -storProfile profile_22 -diskGroup dg_16 -drivesNumber 5
Storage system address: 10.0.0.1
Storage system port: 443
HTTPS connection
ID = GP_4
Operation completed successfully.
Configure a dynamic pool
You can configure dynamic pools for all-Flash models of Unity running OE version 4.2.x or later. New pools created for these models are dynamic pools by default. Dynamic pools implement advanced RAID technology. In dynamic pools, a RAID group is spread across drive extents in multiple drives. The required spare space is also spread across drive extents in multiple drives. When a drive fails, the extents on the failed drive are rebuilt to spare space extents within the pool.
When you configure dynamic pools, you can select different capacity drives from different drive groups with the same Flash drive types to create a tier. The total drive count of the drive type must be at least the stripe width plus one. For example, the total drive count for a RAID 4 + 1 group must be at least 6.
Step 1: View the list of available drive groups
View the list of available drive groups, as shown in the following example:
[Request]
Uemcli /stor/config/dg show
[Response]
Storage system address: 127.0.0.1
Storage system port: 443
HTTPS connection
1: ID = dg_2
Drive type = SAS Flash 2
FAST Cache = yes
Drive size = 196971960832 (183.4G)
Vendor size = 200.0G
Rotational speed = 0 rpm
Number of drives = 12
Unconfigured drives = 12
Capacity = 2363663529984 (2.1T)
Recommended number of spares = 0
2: ID = dg_3
Drive type = SAS Flash 2
FAST Cache = yes
Drive size = 393846128640 (366.7G)
Vendor size = 400.0G
Rotational speed = 0 rpm
Number of drives = 12
Unconfigured drives = 6
Capacity = 4726153543680 (4.2T)
Recommended number of spares = 0
Step 2: View the list of storage profiles
View the list of storage profiles, as shown in the following example:
[Request]
Uemcli /stor/config/profile show
[Response]
Storage system address: 127.0.0.1
Storage system port: 443
HTTPS connection
1: ID = profile_1
Type = Dynamic
Description = SAS Flash 2 RAID5 (4+1)
Drive type = SAS Flash 2
RAID level = 5
Maximum capacity = 97373737844736 (88.5T)
Stripe length = 5
Disk group =
Maximum drives to configure =
Maximum capacity to configure =
Step 3: Configure the dynamic pool
Configure the dynamic pool with the specified drive groups and profiles. Optionally set -type to dynamic and make sure that the -drivesNumber value for each drive type is not less than the drive group's RAID group width plus one:
uemcli /stor/config/pool create –name mypool -diskGroup dg_2,dg_3 -drivesNumber 4,2
-storProfile profile_1 -type dynamic
Storage system address: 127.0.0.1
Storage system port: 443
HTTPS connection
ID = pool_13
Operation completed successfully.[Request]
Configure a traditional pool for an all-Flash model
You can configure traditional pools for all-Flash models of Unity running OE version 4.2.x by explicitly setting the Type attribute to traditional. If you do not set Type to traditional when you create a pool in the Unisphere CLI, a dynamic pool is created.
Step 1: View the list of storage profiles
View the list of storage profiles, as shown in the following example:
[Request]
uemcli /stor/config/profile -traditional -configurable show
[Response]
Storage system address: 127.0.0.1
Storage system port: 443
HTTPS connection
1: ID = tprofile_2
Type = Traditional
Description = SAS Flash 2 RAID5 (8+1)
Drive type = SAS Flash 2
RAID level = 5
Maximum capacity = 95010661072896 (86.4T)
Stripe length = 9
Disk group = dg_34, dg_26
Maximum drives to configure = 9, 9
Maximum capacity to configure = 60189403250688 (54.7T), 2232208064512 (2.0T)
2: ID = tprofile_4
Type = Traditional
Description = SAS Flash 2 RAID5
Drive type = SAS Flash 2
RAID level = 5
Maximum capacity = 95010661072896 (86.4T)
Stripe length = Maximum capacity
Disk group = dg_34, dg_26
Maximum drives to configure = 9, 10
Maximum capacity to configure = 60189403250688 (54.7T), 2691354329088 (2.4T)
Step 2: Configure the traditional pool
Configure a traditional pool with the specified profile. Make sure you set -type to traditional and that the -drivesNumber is a multiple of the RAID group width.
uemcli /stor/config/pool create -name test -diskGroup dg_34 -drivesNumber 9
-storProfile tprofile_2 -type traditional
[Response]
Storage system address: 127.0.0.1
Storage system port: 443
HTTPS connection
ID = pool_6
Operation completed successfully.
Add drives to an existing pool
Retrieve the list of existing pools
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /store/config/pool show
Storage system address: 10.0.0.1
Storage system port: 443
HTTPS connection
1: ID = SPL_1
Name = Performance
Description =
Free space = 408944640 (390G)
Capacity = 1099511627776 (1T)
Drives = 6 x 250GB SAS
Number of drives = 6
Unused drives = 1
RAID level = 5
System pool = yes
2: ID = SPL_2
Name = Capacity
Description =
Free space = 1319413953331 (1.2T)
Capacity = 13194139533312 (12T)
Drives = 8 x 2GB NL-SAS
Number of drives = 8
Unused drives = 0
RAID level = 6
System pool = yes
3: ID = SPL_3
Name = Extreme Performance
Description =
Free space = 209715200 (200M)
Capacity = 322122547200 (300G)
Drive type = EFD
Number of drives = 4
Unused drives = 0
RAID level = 5
System pool = yes
Retrieve the list of recommended disk groups for the selected pool
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /stor/config/dg recom –pool SPL_3
Storage system address: 10.0.0.1
Storage system port: 443
HTTPS connection
1: ID = DG_4
Drive type = EFD
Drive size = 107374182400 (100G)
Number of drives = 4
Allowed numbers of drives = 4
Capacity = 419430400 (400G)
Extend the existing pool
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /stor/config/pool –id SPL_3 extend –diskGroup DG_4 –drivesNumber 4
Storage system address: 10.0.0.1
Storage system port: 443
HTTPS connection
ID = SPL_3
Operation completed successfully.
File sharing use cases
This section describes different use cases for NAS server file sharing.
Create a NAS server with multiprotocol file sharing
Create the NAS server
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /net/nas/server create -name MyFS1 -sp spa -pool pool_0 -mpSharingEnabled yes -unixDirectoryService ldap -defaultUnixUser fred2 -defaultWindowsUser "fred2"
ID = nas_1
Operation completed successfully.
View the NAS server details
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /net/nas/server show -detail
1: ID = nas_1
Name = MyFS1
NetBIOS name =
SP = spa
Storage pool = pool_0
Tenant =
Interface =
NFS enabled = yes
NFSv4 enabled = no
CIFS enabled = no
Workgroup =
Windows domain =
Organization unit =
Multiprotocol sharing enabled = yes
Unix directory service = ldap
Default Unix username = fred2
Default Windows username = fred2
Extended Unix credentials enabled = no
Credentials cache retention = 15
Health state = OK_But (7)
Health details = "The component cannot
operate normally - additional configuration steps are
required. Please ensure configuration of Unix directory
service. Please ensure configuration of CIFS server."
Configure LDAP and upload the Certificate Authority certificate
Configure LDAP
uemcli /net/nas/ldap -server nas_1 set -ip 10.0.0.1,10.0.0.1 -port 636 -protocol ldaps authType simple -bindDn "cn=administrator,cn=User,dc=emc,dc=com" - bindPasswd "Ldap123!" -baseDn "dc=emc,dc=com"
Operation completed successfully.
Upload the Certificate Authority certificate:
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! -upload -f " MyCert.pem" /net/nas/ldap -server nas_1 -type CACertificate
Operation completed successfully.
View the LDAP configuration:
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /net/nas/ldap show -detail
[Response]
1: NAS server = nas_1
Servers = 10.0.0.1, 10.0.0.1
Port = 636
Protocol = ldaps
Verify certificate = yes
Authentication type = simple
Bind DN = cn=administrator,cn=User,dc=emc,dc=com
Use CIFS account =
Principal =
Realm =
Base DN = dc=emc,dc=com
Profile DN =
Configure SMB for the NAS server
Create the interface for the NAS server
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /net/nas/if create -server nas_1 -port eth0_SPA -addr 10.0.0.1 -netmask 255.255.255.0
ID = if_0
Operation completed successfully
Configure the NAS server as an SMB server
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /net/nas/cifs create -server nas_1 -domain spb.sspg.lab.emc.com -username Administrator -passwd password1
ID = cifs_1
Operation completed successfully.
View the NAS server health state
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /net/nas/server show -detail
Storage system address: 10.0.0.1
Storage system port: 443
HTTPS connection
1: ID = nas_1
Name = auto_mig_vdm_6380
SP = spa
Storage pool = pool_24
Tenant =
Interface = if_24
CIFS enabled = yes
Multiprotocol sharing enabled = no
Unix directory service = none
Default Unix username =
Default Windows username =
Username translation =
Health state = OK (5)
Health details = "The component is operating normally. No action is required."
Type = 64
Migration Destination = yes
Preferred production interfaces overridden =
Preferred production IPv4 interface = auto
Preferred production IPv6 interface = auto
Preferred backup and DR test IPv4 interface = auto
Preferred backup and DR test IPv6 interface = auto
Source preferred production IPv4 interface =
Source preferred production IPv6 interface =
Share the file system between NFS and SMB
Create the multiprotocol file system
/stor/prov/fs create -name MyFS -server nas_1 -pool pool_0 -size 1000M -type multiprotocol -accessPolicy native
ID = res_1
Operation completed successfully.
Create an NFS share for the multiprotocol file system
/stor/prov/fs/nfs create -name NFSshare -fs res_1 -path / -defAccess rw
ID = NFSShare_1
Operation completed successfully.
Create an SMB share for the multiprotocol file system
/stor/prov/fs/cifs create -name CIFSshare -fs res_1 -path / -comment "cifsshare"
ID = SMBShare_1
Operation completed successfully
Generate and review the user mapping report
Generate the user mapping report
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /net/nas/server -id nas_1 update -userMapping -dryRun
Storage system address: 10.0.0.1
Storage system port: 443
HTTPS connection
Operation completed successfully.
Retrieve the user mapping report
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! uemcli -download /net/nas/server -id nas_1 -type mappingReport
Operation completed successfully.
>ls mappingReport_2014-11-18_18-08-00.txt
Resource configuration use cases
This section describes use cases for configuring different storage resources.
Identify pool capacity and configure a resource
Identify the SP where the server to be used is located by default
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /net/nas/server –id nas_1 show
Storage system address: 10.0.0.1
Storage system port: 443
HTTPS connection
1: ID = nas_1
Name = MySFS1
CIFS enabled = yes
NFS enabled = no
SP = spa
Interface = if_1
Check the maximum capacity of the appropriate pool on the identified SP
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /stor/config/pool show -detail
Storage system address: 10.0.0.1
Storage system port: 443
HTTPS connection
1: ID = pool_1
Name = TestPool
Description =
Total space = 6266625720320 (5.6T)
Current allocation = 2684354560 (2.5G)
Remaining space = 6263941365760 (5.6T)
Subscription = 111967084544 (104.2G)
Subscription percent = 1%
Alert threshold = 70%
Drives = 4 x 3.1T SAS Flash 3
Number of drives = 4
RAID level = 10
Stripe length = 2
Rebalancing = no
Rebalancing progress =
Health state = OK (5)
Health details = "The component is operating normally. No action is required."
FAST Cache enabled = no
Protection size used = 32768 (32.0K)
Auto-delete state = Idle
Auto-delete paused = no
Auto-delete pool full threshold enabled = yes
Auto-delete pool full high water mark = 95%
Auto-delete pool full low water mark = 85%
Auto-delete snapshot space used threshold enabled = no
Auto-delete snapshot space used high water mark = 25%
Auto-delete snapshot space used low water mark = 20%
2: ID = pool_2
Name = Test1
Description =
Total space = 43403328880640 (39.4T)
Current allocation = 57982058496 (54.0G)
Remaining space = 43345346822144 (39.4T)
Subscription = 1627792605184 (1.4T)
Subscription percent = 3%
Alert threshold = 70%
Drives = 15 x 600.0G SAS;
2 x 200.0G SAS Flash 2;
8 x 6.0T NL-SAS;
2 x 800.0G SAS Flash 2
Number of drives = 27
RAID level = Mixed
Stripe length = Mixed
Rebalancing = no
Rebalancing progress =
Health state = OK (5)
Health details = "The component is operating normally. No action is required."
FAST Cache enabled = yes
Protection size used = 2147483648 (2.0G)
Auto-delete state = Idle
Auto-delete paused = no
Auto-delete pool full threshold enabled = no
Auto-delete pool full high water mark = 95%
Auto-delete pool full low water mark = 85%
Auto-delete snapshot space used threshold enabled = no
Auto-delete snapshot space used high water mark = 25%
Auto-delete snapshot space used low water mark = 20%
Configure a resource
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /stor/prov/fs create –name FileSystem01 -descr “NFS shares” –pool capacity –server nas_1 –size 1TB –type nfs
Storage system address: 10.0.0.1
Storage system port: 443
HTTPS connection
ID = res_1
Operation completed successfully.
Replication configuration use case
This section describes the use cases for configuring replication for block or file storage resources.
Before you begin
Before you proceed with configuring replication, ensure that you complete the following:
- Create identical storage resources on the source and destination systems.
- Configure replication interfaces for each SP on the source and destination systems.
- On the destination system, the relevant storage resources and NAS servers are individually created with the -replDest attribute set to yes.
- For file replication, ensure the following:
- Start with creating identical NAS servers on both the systems, and then create identical file systems.
- Configure the NAS server on the destination system with a name other than the NAS server name on the source system.
- Configure file systems on the destination system with the same name as the file systems on the source system.
Configure local replication
Local replication is applicable to asynchronous replication only. Local replication is not applicable to synchronous replication.
Replication interfaces and connections do not apply to local replication. When using the CLI or the REST API, once you create the identical source and destination storage resources or NAS servers on the storage system, you can proceed to configure a replication session. When using Unisphere, you only need to create the source storage resources or NAS servers on the storage system. Unisphere does not allow you to create a session with an existing destination. A DR_ is concatenated onto the resource name for local destinations to ensure that the source and destination names on the same system are unique (that is, LUN names need to be unique).
Note the following:
- For a disaster recovery scenario, it is recommended that the destination storage resource and NAS server are configured on a storage pool other than the pool used for the source storage resource and NAS server.
- For a migration scenario, which means migrating the source storage resource and NAS server to a destination storage resource and NAS server on the same pool, use the CLI to configure local replication. The Unisphere GUI does not allow local replication between storage resources and NAS servers on the same pool.
Configure asynchronous replication
Before you begin
If you are configuring asynchronous replication for a tenant, create a pool for the tenant on the destination system that matches the corresponding pool on the source system (if one exists). Then add the tenant to the destination system, using the same UUID and VLANs as the tenant on the source.
If you are configuring asynchronous replication in a coexisting synchronous and asynchronous replication topology, create the asynchronous replication destination NAS server with both the -replDest and the -backupOnly attributes set to yes. These attributes must be set to yes on the asynchronous replication destination NAS server when the source NAS server is synchronous replicated; otherwise, the asynchronous replication session cannot be created.
Procedure
- Configure the replication interfaces on each SP of the source and destination systems.
- Configure a replication connection using the Asynchronous connection mode.
- For file storage, create a replication session for the NAS server associated with the file storage.
Storage resources included in a NAS server automatically get replicated when a replication session is first configured for the NAS server. The replication session for the storage resources will inherit the same attributes as the associated replication session of the associated NAS server. For the storage resources you do not want participating in replication, you can choose to remove the associated replication sessions manually.
- Create a remote replication session for the storage resource.
You only need to configure replication interfaces and connections for the first replication session between two systems. The same connection can be used again for subsequent replication sessions between the same systems.
Configure synchronous replication
Only remote replication is supported for synchronous replication.
Procedure
- Identify the Synchronous Replication Fibre Channel (FC) ports on each system.
To determine the FC port used for synchronous replication, in the CLI console, run the command /remote/sys show -detail. Port information, similar to the following example, will appear in the output:
Synchronous FC ports = spb_fc4, spa_fc4For more information, see the Unisphere CLI User Guide.
- Zone the Synchronous Replication FC ports between the systems.
If the source and destination systems are co-located, instead of zoning, you can choose to use direct-connected FC cables between the SPs.
- Configure the replication interfaces on each SP of the source and destination systems based on the connection mode you want:
- For synchronous replication support (Synchronous connection mode), use the Synchronous Replication Management Ports on each SP of both the systems.
- For asynchronous and synchronous replication support (Both connection mode), in addition to the replication interfaces for Synchronous Replication Management Ports, configure additional interfaces using the Ethernet Ports on each SP of the source and destination systems.
- Configure the replication connection between source and destination systems from the source system only.
- For synchronous replication support, specify the Synchronous connection mode.
- For asynchronous and synchronous replication support, specify the Both connection mode.
- Create the synchronous replication session.
You only need to configure replication interfaces and connections for the first replication session between two systems. The same connection can be used again for subsequent replication sessions between the same systems.
Create a replication interface
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:
- The interface port is cabled and connected to a network switch.
- Both SPs are up and running.
Obtain the following information for each Storage Processor (SP):
- 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.
- IP address mask or prefix length that identifies the associated subnet.
- Gateway IP address associated with the interface.
- If applicable, the VLAN ID (between 1 and 4095) you want to associate the interface with.
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.
Ensure that you create replication interfaces on each SP.
Procedure
- Run the following command to create the interface on SP A:
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /net/if create -type replication -port eth1_spa -addr 10.0.1.1 -netmask 255.255.255.0 -gateway 10.0.1.0
Storage system address: 10.0.0.1 Storage system port: 443 HTTPS connection ID = IF_1 Operation completed successfully. - Run the following command to create the interface on SP B:
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /net/if create -type replication -port eth1_spb -addr 10.0.1.2 -netmask 255.255.255.0 -gateway 10.0.1.0
Storage system address: 10.0.0.1 Storage system port: 443 HTTPS connection ID = IF_2 Operation completed successfully.
View interfaces
Storage system address: 10.0.0.1
Storage system port: 443
HTTPS connection
1: ID = IF_0
Type = iscsi
Port = eth0_spa
VLAN ID = 0
IP address = 3ffe:80c0:22c:4e:a:0:2:7f/64
Subnet mask =
Gateway = fe80::20a8bff:fe5a:967c
SP = spa
2: ID = IF_1
Type = replication
Port = eth1_spa
VLAN ID = 1
IP address = 10.0.1.1
Subnet mask = 255.255.255.0
Gateway = 10.0.1.0
SP = spa
3: ID = IF_2
Type = replication
Port = eth1_spb
VLAN ID =
IP address = 10.0.1.2
Subnet mask = 255.255.248.0
Gateway = 10.0.1.0
SP = spb
Create a replication connection
Before you begin
Ensure that you have set up relevant replication interface pairs, one on each SP, on the source and destination systems. Obtain the following information:
- For remote replication, the IP address and associated user authentication credentials to connect to the remote system.
- For local replication, the password associated with your user account.
- The connection mode you want to use for the replication: Asynchronous, Synchronous, or Both.
If a replication connection already exists and you plan to add a different mode of file replication, do not attempt to create a new connection. Change the existing replication connection mode to Both. Also, ensure that you have the appropriate interface types configured to support both asynchronous replication (eth2, eth3) and synchronous replication (sync replication mgmt port).
- Run the following command:
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /remote/sys create –addr 10.1.1.1 –srcUsername admin1 -srcPassword Password456! –dstUsername admin2 –dstPassword Password986! -connectionType async
Storage system address: 10.0.0.1 Storage system port: 443 HTTPS connection ID = RS_1 Operation completed successfully.
View settings for remote storage systems
Storage system address: 10.0.0.1
Storage system port: 443
HTTPS connection
1: ID = RS_1
Name = MyTargetSystem
Address = 10.1.1.1
Model = Unity 300
Serial number = FCNCH01234567A90
Connection type = async
Source interfaces = N/A
Local interfaces = N/A
Remote interfaces = N/A
Operational status = OK (0x2)
Health state = OK (5)
Health details = "Communication with the replication
host is established. No action is
required."
Synchronous FC ports = spb_fc4, spa_fc4
Create a replication session for block storage
Before you begin
Complete the following:
- For remote replication:
- Identify the remote system that will act as the replication destination.
- Create relevant replication interfaces, replication connection, and a storage resource on the remote system that will act as the destination.
- For local replication, create a storage resource that will act as the destination.
- Determine the replication synchronization mode you want. You can specify asynchronous (async), synchronous (sync), or manual synchronization (manual).
- For asynchronous replication, determine the Recovery Point Objective (RPO) for the replication session.
- Run the following command to create a synchronous replication session between the LUN "LUN_1" on the source system and the LUN "LUN_2" located on the remote system "RS_2":
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /prot/rep/session create -name REP1 -srcRes LUN_1 –dstType remote -dstSys RS_2 –dstRes LUN_2 –syncType auto –rpo 0
Storage system address: 10.0.0.1 Storage system port: 443 HTTPS connection ID = 81604378625_FCNCH097274B3A_0000_81604378627_FCNCH097274B37_0000 Operation completed successfully.
Create an asynchronous replication session for file storage
Before you begin
Complete the following:
- For remote replication:
- Identify the remote system that will act as the replication destination.
- Create relevant replication interfaces, replication connection, and a storage resource on the remote system that will act as the destination. The storage resource on the destination system must have the same size
- For local replication, create a storage resource that will act as the destination.
- For file replication, create a replication session on the NAS server associated with the file storage.
- For asynchronous replication, determine the Recovery Point Objective (RPO) for the replication session.
If you are configuring asynchronous replication in a coexisting synchronous and asynchronous replication with one source resource topology, create the asynchronous replication destination NAS server with both the -replDest and the -backupOnly attributes set to yes. These attributes must be set to yes on the asynchronous replication destination NAS server when the source NAS server is synchronous replicated; otherwise, the asynchronous replication session cannot be created.
Procedure
- Run the following command to create an asynchronous replication session between the NAS servers:
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /prot/rep/session create -async -srcRes nas_1 –dstType remote -dstSys RS_2 –dstRes nas_2 auto –rpo 02h30m
Job ID = N-86 Operation completed successfully. - Run the following command to create an asynchronous replication session between the file system "res_7" on the source system and the file system "res_8" located on the remote system "RS_2", with an RPO set to 2 hours 30 minutes and automatic synchronization:
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /prot/rep/session create -async -srcRes res_7 –dstType remote -dstSys RS_2 –dstRes res_8 –syncType auto –rpo 02h30m
Job ID = N-89 Operation completed successfully.
Create a synchronous replication session for file storage
Before you begin
Complete the following:
- For remote replication:
- Identify the remote system that will act as the replication destination.
- Create relevant replication interfaces, replication connection, and a storage resource on the remote system that will act as the destination. The storage resource on the destination system must have the same size.
- For local replication, create a storage resource that will act as the destination.
- For file replication, create a replication session on the NAS server associated with the file storage.
Procedure
- Run the following command to create a synchronous replication session between the NAS servers:
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /prot/rep/session create –name MyNSRep1 -srcRes nas_1 –dstType remote –dstSys RS_1 –dstRes nas_1
Storage system address: 10.0.0.1 Storage system port: 443 HTTPS connection ID = 103079215106_FCNCH097274999_0000_103079215106_FCNCH0972749A9_0000 Operation completed successfully. - Run the following command to create a synchronous replication session between file systems on the source system and the remote system:
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /prot/rep/session create –name MyFSRep1 -srcRes res_1 –dstType remote –dstSys RS_1 –dstRes res_1
Storage system address: 10.0.0.1 Storage system port: 443 HTTPS connection ID = 171798691844_FCNCH097274999_0000_171798691844_FCNCH0972749A9_0000 Operation completed successfully.
View replication sessions
Storage system address: 10.0.0.1
Storage system port: 443
HTTPS connection
1: ID = 81604378635_FCNCH097274B3A_0000_81604378637_FCNCH097274B37_0000
Name = REP2
Session type = nas server
Synchronization type = auto
Resource type = NAS Server
Destination type = remote