After initialization, you can verify elements of the active/passive MirrorView/S configuration by using the nas_server list, nas_server info all, nas_devicegroup -list, nas_devicegroup -info <name>, nas/sbin/nas_mview -info, server_df ALL, nas_fs -info, and nas_disk -list commands.
6. At the prompt, continue with the initialization by typing yes.
Note: If you type no, the initialization aborts with an informational message. Note that both systems are informed about the device group creation.
Example:
Initializing Active-->Passive (new_york-->new_jersey) Do you wish to continue? [yes or no] yes
Updating MirrorView configuration cache Setting up server_3 on new_york
Rebooting server_3 on new_jersey as standby ... done Setting up server_2 on new_york
Rebooting server_2 on new_jersey as standby ... done Creating user account dradmin
Setting acl for server_3 on new_jersey Setting acl for server_2 on new_jersey Updating the Celerra domain information
Creating device group cg_new_york on new_jersey Creating device group cg_new_york on new_york done
7. Exit root by typing:
# exit exit
Note: Initialization of the active/passive MirrorView/S configuration is complete.
Step Action
Step Action
1. Log in to the source VNX for file (new_york) as nasadmin.
2. List all Data Movers by typing:
$ /nas/bin/nas_server -list
id type acl slot groupID state name 1 1 1000 2 0 server_2 2 4 1000 3 0 server_3 3 1 1000 4 0 server_4
3. Switch (su) to root by typing:
$ su Password:
4. List all information for all Data Movers by typing:
$ nas_server -info -all
standby = server_3, policy=manual RDFstandby= slot=2
standby = server_5, policy=auto status :
Note: When run from the source side, the output identifies Data Movers that have remote standbys (in the RDFstandby=
field) and local standbys (standby=), and also indicates a Data Mover serving as a local standby (standbyfor=). When run from the destination, the output indicates which Data Movers are owned by dradmin and serve as remote standbys (in the acl= field and the type= field), and also indicates if a Data Mover serves as a local standby (standbyfor=). The standbyfor=
has a value only if the Data Mover serves as a local standby.
Step Action
5. Exit root by typing:
# exit exit
6. Verify the creation of the device group on the source VNX for file after initialization by typing:
$ nas_devicegroup -list Output:
ID name owner storage ID acl type 1 cg_new_york 0 APM00041700549 0 MVIEW
Note: cg_new_york represents the MirrorView/S-protected data LUNs in the device group. The group in your configuration might have a different name, which is assigned when the device group is created as part of the storage system
configuration process. If you run this command on the source system, the device group cg_new_york has an owner of 0 because new_york is the source system in the active/passive configuration. Manipulation of the device group is done from the source system. If you run this command from the destination, the owner for device group cg_new_york is 500 because the group is owned by the remote administration account (in this case, dradmin). "Activate a failover from the destination VNX for file (active/passive)" on page 56 shows an example of detailed device group information prior to failover activation.
7. Get detailed information about the device group on the source VNX for file by using this command syntax:
# nas_devicegroup -info {<name>|id=<id>}
where:
<name> = name of the device group
<id> = ID assigned to the device group Example:
To get detailed information about the device group on the source VNX for file, type:
$ nas_devicegroup -info cg_new_york Sync with CLARiiON backend ... done name = cg_new_york
description = new_york_as_source
uid = 50:6:1:60:90:60:7:30:0:0:0:0:0:0:0:0 state = Consistent
role = Primary condition = Active recovery policy = Automatic number of mirrors = 9
mode = SYNC owner = 0
mirrored disks = root_disk,root_ldisk,d5,d8,d9,d10,d12,d13,d14, local clarid = APM00041700549
remote clarid = APM00042000817 mirror direction = local -> remote 8. Switch (su) to root by typing:
$ su Password:
Step Action
9. Get information about the MirrorView/S configuration from the source VNX for file by typing:
# /nas/sbin/nas_mview -info Output:
***** Device Group Configuration *****
name = cg_new_york
mirrored disks = root_disk,root_ldisk,d5,d8,d9,d10,d12,d13,d14, local clarid = APM00041700549
remote clarid = APM00042000817 mirror direction = local -> remote
***** Servers configured with RDFstandby *****
id = 1
standby = server_3, policy=manual RDFstandby= slot=2
***** Servers configured as standby *****
id = 4
Note: On the source VNX for file new_york, source server_2 and local standby server_3 have remote standbys, and server_5 is a local standby for server_4.
Step Action
10. Exit root by typing:
# exit exit
11. Display information about the file systems associated with Data Movers on the source VNX for file by typing:
$ /nas/bin/server_df ALL Output:
server_2 :
Filesystem kbytes used avail capacity Mounted on ufs4 413030384 576 413029808 0% /ufs4 ufs3 413030384 576 413029808 0% /ufs3 ufs2 413030384 576 413029808 0% /ufs2 ufs1 413030384 576 413029808 0% /ufs1
root_fs_common 13624 5256 8368 39% /.etc_common root_fs_2 114592 728 113864 1% /
server_3 :
Error 2: server_3 : No such file or directory failed to complete command
server_4 :
Filesystem kbytes used avail capacity Mounted on root_fs_common 13624 5256 8368 39% /.etc_common ufslocal3 206515184 576 206514608 0% /ufslocal3 ufslocal2 413030384 576 413029808 0% /ufslocal2 ufslocal1 413030384 576 413029808 0% /ufslocal1 root_fs_4 114592 712 113880 1% /
server_5 :
Error 2: server_5 : No such file or directory failed to complete command
Note: No information is reported for the standby Data Movers as nasadmin. Information is only reported for the two source Data Movers; server_2 is MirrorView-protected.
Step Action
12. Display information for one of the file systems from the source VNX for file by using this command syntax:
$ nas_fs -info <fs_name>
where:
<fs_name> = name of a specific file system Example:
To view the information for mirrored file system ufs1 on server_2 on new_york, type:
$ nas_fs -info ufs1 Output:
id = 27 name = ufs1 acl = 0 in_use = True type = uxfs worm = off volume = v202
pool = cm_r5_performance member_of = root_avm_fs_group_14 rw_servers= server_2
ro_servers=
rw_vdms = ro_vdms =
auto_ext = no,virtual_provision=no
stor_devs = APM00041700549-0017,APM00041700549-0014,APM00041700549-0013 disks = d14,d9,d12
disk=d14 stor_dev=APM00041700549-0017 addr=c16t1l7 server=server_2 disk=d14 stor_dev=APM00041700549-0017 addr=c32t1l7 server=server_2 disk=d14 stor_dev=APM00041700549-0017 addr=c0t1l7 server=server_2 disk=d14 stor_dev=APM00041700549-0017 addr=c48t1l7 server=server_2 disk=d9 stor_dev=APM00041700549-0014 addr=c0t1l4 server=server_2 disk=d9 stor_dev=APM00041700549-0014 addr=c48t1l4 server=server_2 disk=d9 stor_dev=APM00041700549-0014 addr=c16t1l4 server=server_2 disk=d9 stor_dev=APM00041700549-0014 addr=c32t1l4 server=server_2 disk=d12 stor_dev=APM00041700549-0013 addr=c16t1l3 server=server_2 disk=d12 stor_dev=APM00041700549-0013 addr=c32t1l3 server=server_2 disk=d12 stor_dev=APM00041700549-0013 addr=c0t1l3 server=server_2 disk=d12 stor_dev=APM00041700549-0013 addr=c48t1l3 server=server_2 Note: In the output, the pool reflects a MirrorView pool type. In this example, cm_r5_performance.
Step Action