Unity Implementation and Administration Lab Guide - Final PDF
Unity Implementation and Administration Lab Guide - Final PDF
kynikon1@mts.ru
Copyright
Copyright © 2017 Dell Inc. or its subsidiaries. All Rights Reserved. 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 [04/17]
Dell EMC believes the information in this document is accurate as of its publication date. The
information is subject to change without notice.
kynikon1@mts.ru
Table of Contents
COPYRIGHT ........................................................................................................................................................... 2
LAB EQUIPMENT LAYOUT ................................................................................................................................... 6
LAB EXERCISE: UNITY UNISPHERE TOUR ....................................................................................................... 9
PART 1: TOUR OF THE UNISPHERE DASHBOARD, SYSTEM VIEW, AND SETTINGS................................................... 10
PART 2: ADDING A NEW USER ACCOUNT WITH A ROLE ASSOCIATED TO IT ........................................................... 19
LAB EXERCISE: STORAGE PROVISIONING .................................................................................................... 22
PART 1: CREATING STORAGE POOLS ................................................................................................................. 24
PART 2: CREATING BLOCK STORAGE LUNS AND CONSISTENCY GROUPS ............................................................ 29
PART 3: CREATING NAS SERVERS 34
PART 4: CREATING FILE SYSTEMS 39
LAB EXERCISE: WINDOWS HOST ACCESS TO BLOCK STORAGE ............................................................. 43
PART 1: CREATE AN ISCSI INTERFACE ............................................................................................................... 44
PART 2: HOST MICROSOFT ISCSI INITIATOR - TARGET DISCOVERY ..................................................................... 45
PART 3: UNISPHERE INITIATOR AND HOST ACCESS ............................................................................................. 47
PART 4: PRESENT THE LUN TO A W INDOWS HOST ............................................................................................. 49
LAB EXERCISE: LINUX HOST ACCESS TO BLOCK STORAGE ..................................................................... 51
PART 1: LINUX HOST ISCSI INITIATOR - TARGET DISCOVERY .............................................................................. 52
PART 2: UNISPHERE INITIATOR AND HOST ACCESS ............................................................................................. 54
PART 3: PRESENT THE LUN TO A LINUX HOST .................................................................................................... 56
LAB EXERCISE: SMB FILE STORAGE ACCESS .............................................................................................. 61
PART 1: CREATE A HIDDEN TOP-LEVEL SMB SHARE OF A FILE SYSTEM ................................................................. 62
PART 2: CREATE A LOWER-LEVEL SMB SHARE OF A FILE SYSTEM ........................................................................ 69
PART 3: CREATE AN SMB SHARE USING COMPUTER MANAGEMENT..................................................................... 74
LAB EXERCISE: NFS FILE STORAGE ACCESS............................................................................................... 78
PART 1: CREATE A TOP-LEVEL ADMINISTRATIVE NFS SHARE OF A FILE SYSTEM ................................................. 79
PART 2: CREATE A LOWER-LEVEL NFS SHARE OF A FILE SYSTEM ...................................................................... 83
LAB EXERCISE: VMWARE DATASTORE ACCESS ......................................................................................... 88
PART 1: ADD VCENTER HOSTS 89
PART 2: PROVISION AND ACCESS VMWARE VMFS DATASTORE .......................................................................... 91
PART 3: PROVISION AND ACCESS VMWARE NFS DATASTORES........................................................................... 96
LAB EXERCISE: HOST I/O LIMITS SETUP ........................................................................................................ 99
PART 1: VERIFY THE STATUS OF THE HOST I/O LIMIT FEATURE ......................................................................... 100
PART 2: CREATE A HOST I/O LIMITS POLICY FOR A LUN ................................................................................... 104
LAB EXERCISE: FILE SYSTEM EXTENSION AND SHRINK OPERATIONS ................................................. 107
PART 1: EXTEND A THIN UFS64 FILE SYSTEM.................................................................................................. 108
PART 2: SHRINK A UFS64 THIN FILE SYSTEM .................................................................................................. 111
LAB EXERCISE: FAST VP SETTINGS ............................................................................................................. 114
PART 1: VERIFY THE STATUS OF THE FAST VP FEATURE ................................................................................. 115
PART 2: OBSERVING FAST VP DATA RELOCATION........................................................................................... 118
LAB EXERCISE: FILE SYSTEM QUOTAS ....................................................................................................... 122
PART 1: CREATE A USER QUOTA 122
Important: The lab exercises in this course are run on the lab setup
detailed here. Review the information in this section to
gain a better understanding of the lab environment and
how you will access it.
The table above details each system within the lab setup. It provides names, IP addressing,
and access credentials.
Note: All of the specific addressing and access credentials are included directly within the lab
exercise steps. It is presented here as a reference if needed and to provide an overview of the
setup.
Each student will be automatically redirected to the Metro view of their specific Student
Desktop Windows system. Access the Desktop charm to get to the Desktop view. The
Desktop view and its Task bar have been pre-configured with application icons needed for the
lab exercises.
Throughout the lab exercises, students will move between the Student Desktop, Windows and
Linux Hosts. Students login to the Windows and Linux hosts using different credentials
depending on the Lab being performed.
1 Launch Mozilla Firefox from the task bar on your Student Desktop.
Enter the URL https://192.168.1.113, and log into Unisphere with the admin user
account and the password Password123!
Click on the System Heath View Block. Three icons appear in the upper right
side of the window. Hover over each icon to view the details.
3 To customize the Dashboard, click the Main link text or use the drop down arrow
in the top left of the window and select Customize.
4 In the Add View Blocks window, select System Alerts, click Add View Block, and
then click Close to return to the Dashboard.
6 Enter My New Dashboard in the Dashboard Name field and click OK.
7 From the My New Dashboard dropdown list, select Customize to add widgets to
the new dashboard.
Select System Capacity and click the Add View Block button.
Add another widget by selecting System Alerts and click the Add View Block
button.
8 Let’s take a look at Unisphere preferences. Click the person icon in the upper right
corner and select Preferences. Note that you can also change the password and
log out here.
9 In the window that opens, hover the mouse over the Optimize for remote access
link.
What is the purpose of this option? _____________________________________
Click the Clear User Cache button next. Click Yes to confirm.
What is the result of the clear user cache function? ________________________
10 Let’s take a look at the help options. Click the Help icon in the top right of the
window to view the sub menu. Click the About link in the sub menu.
Which version of Unisphere is running? _________________________________
Click Close.
The other two sub menu items include a link to the online help main menu page
and a direct link to the dashboard help page.
12 Close the Unisphere help window and return to the Unisphere Dashboard.
Click the Alerts icon to view any recent alerts. If you select the View All Alerts
link, it will bring you to the Alerts page. You can also reach the Alerts page using
the link in the navigation pane on the left.
Are there any alerts displayed? _______________________________________
13 Next to the Alerts icon, click the Jobs icon to view any active jobs. In this case
there are no active jobs shown.
Click the Jobs link in the navigation pane on the left to view the Jobs page.
14 To the left of the Jobs icon, click the View system status icon. Select the View
system details link for more details.
16 Select the Virtual tab. There should be nine Virtual Disk assigned to your
UnityVSA storage system.
17 Now let’s take a look at some system settings. Click the Settings icon in the top
right corner of Unisphere.
The Software and Licenses Information window is displayed. Note that the menu
on the left roughly matches the flow of the Initial Configuration Wizard and that you
can launch the Initial Configuration Wizard near the bottom of window.
The Pre Upgrade Health Checks window is displayed (not shown here). Click the
Perform Health Checks button to perform the health check.
20 Now let’s take a look at the system limits. Click the System Limits link in the
Settings window. Use the slide bar to view all the limits.
What is the Maximum Pool Capacity in Total of your virtual storage system? ____
21 Use the menu on the left to explore the rest of the Settings.
Step Action
1 From the Settings window, navigate to the Users and Groups > User
Management section.
Then from the Manage Users & Groups page, launch the Create User or Group
wizard by clicking on the Add link (+).
2 From the Create User or Group wizard window notice that Local User is the only
option available because LDAP service was not configured for the Unity System.
If LDAP was configured in the Directory Services tab of the System Settings
window both existing LDAP Users and Group could be configured to access
Unisphere.
Username: student
Password: P@ssw0rd
Confirm Password: P@ssw0rd
4 On the Select a Role section, select the Operator role for the New User.
A green check mark specifies that the operation was completed successfully.
7 The new User will be displayed in the Manage Users & Groups page.
Notice that among the information displayed in this page are the User name, role,
and the type of user (Local or LDAP).
8 Now you will test the new User based and the permissions associated with the
role.
First log off from the Unisphere session. (Remember that we are logged as
Admin)
Confirm the Log Out operation. The browser will redirect the page to the Login
screen.
11 The default License Management page is displayed under the Software and
Licenses > License Information section.
Is this user allowed to install a new license? _____________________________
Purpose: In this lab you will assign the storage tier levels to virtual
disks presented to the Dell EMC UnityVSA system. From
that storage space you will then create several
heterogeneous and homogeneous pools. From the pools
you will then create LUNs, Consistency Groups, NAS
servers, and file systems.
Step Action
1 From your Student Desktop system taskbar, launch Mozilla Firefox and
establish a Unisphere session to the UnityVSA-Source system at IP address
192.168.1.113. The login credentials are admin/Password123!
2 Navigate to System > System View > Virtual. You will see nine Virtual Disks
displayed with three different capacities.
Select the first 9.9 GB Virtual Disk so it is highlighted, then move the cursor to
the Details icon in the tool bar and click it. As a note, double clicking the Virtual
Disk will also work.
The Properties window will appear. From the Storage Tier dropdown list, select
the Extreme Performance Tier. Click Apply then click Close. Repeat this
step for the other two 9.9 GB Virtual Disks.
Double-click on the first 19.9 GB Virtual Disk. The Properties window appears.
From the Storage Tier dropdown list, select the Performance Tier. Click
Apply then click Close. Repeat this step for the other two 19.9 GB Virtual
Disks.
Double-click on the first 49.9 GB Virtual Disk. The Properties window appears.
From the Storage Tier dropdown list, select the Capacity Tier. Click Apply
then click Close. Repeat this step for the other two 49.9 GB Virtual Disks.
Note this is one of several places that tiers can be assigned to virtual disks.
3 Navigate to Storage > Pools. Click the + icon to create a new pool. The
Create Pool Wizard opens. In the Name field input: FAST VP-1. Click Next to
continue the wizard.
In the Assign Tier to the Virtual Drive window click Next since we already
performed this step.
In the Select Storage Tiers window, check the box for Tier as this will be a
multi-tiered FAST VP Pool. Click Next to continue the wizard.
In the Select Virtual Drives window, remove the check marks from all virtual
disks except the first one listed in each of the three tiers. Click Next to continue
the wizard.
Leave the Create VMware Capability Profile for the Pool check box
unchecked. Click Next to continue the wizard.
The Results window displays the creation status. Close the window when the
operation completes.
4 Click the + icon to create another new pool. The Create Pool Wizard opens. In
the Name field input: FAST VP-2. Click Next to continue the wizard.
In the Select Storage Tiers window, check off the box for Tier as this will be a
multi-tiered FAST VP Pool. Click Next to continue the wizard.
In the Select Virtual Drives window, remove the check marks from all virtual
disks except the first one listed in each of the three tiers. Click Next to continue
the wizard.
Leave the Create VMware Capability Profile for the Pool check box
unchecked. Click Next to continue the wizard.
The Summary section displays the pool configuration to be created. Verify there
is a single disk in each of the Tiers. Click Finish to begin the creation
operation.
The Results window displays the creation status. Close the window when the
operation completes.
5 Click the + icon to create another new pool. The Create Pool Wizard opens. In
the Name field input: Extreme Performance Pool. Click Next to continue the
wizard.
In the Select Storage Tiers window, check off the Extreme Performance Tier
only as this will be a single tier pool. Click Next to continue the wizard.
In the Select Virtual Drives window, only the one virtual disk will be displayed
and checked. Click Next to continue the wizard.
Leave the Create VMware Capability Profile for the Pool check box
unchecked. Click Next to continue the wizard.
In the Review Your Selections window, verify you have a single 9.9 GB drive in
the Extreme Performance Pool. Click Finish
6 Click the + icon to create another new pool. The Create Pool Wizard opens. In
the Name field input: Performance Pool. Click Next to continue the wizard.
In the Select Storage Tiers window, check off the box for Performance Teir.
Leave the Create VMware Capability Profile for the Pool check box
unchecked. Click Next to continue the wizard.
In the Review Your Selections window, verify you have a single 19.9 GB drive
in the Performance Pool. Click Finish
7 Click the + icon to create another new pool called Capacity Pool. Repeat the
process to add the last 49.9 GB drive (Virtual Disk 9) to the Capacity Pool.
In the Review Your Selections window, verify you have a single 49.9 GB drive
in the Capacity Pool. Click Finish
The Results window displays the creation status. Close the window when the
operation completes.
This lab will show you how to provision block storage LUNs and a Consistency Group with two
or more LUNs.
Step Action
1 In Unisphere, navigate to Storage > Block > LUNs. Click the + icon to create
a new LUN.
Number of LUNs: 1
Name: WIN1 LUN0
Pool: FAST VP-1
Tiering Policy: Start High, Then Auto-Tier
Size: 5 GB
Thin: Checked
Host I/O Limit: No Limit
In the Configure Access section you will not configure host access yet. Click
Next to continue the wizard.
Also click Next in the Snapshot section and Next in the Replication section,
you will not be configuring those features yet.
The Summary section will display the configuration of the LUN to be created as
shown.
The Results window will display the status of the operation. When it completes,
Close the window. The newly created WIN1 LUN0 will be displayed.
Number of LUNs: 1
Name: Linux1 LUN0
Pool: FAST VP-1
Tiering Policy: Start High, Then Auto-Tier
Size: 5 GB
Thin: Checked
Host I/O Limit: No Limit
In the Configure Access section you will not configure host access yet. Click
Next to continue the wizard.
Also click Next in the Snapshot section and Next in the Replication section,
you will not be configuring those features yet.
The Summary section will display the configuration of the LUN to be created as
shown.
The Results window will display the status of the operation. When it completes,
Close the window. The newly created Linux1 LUN0 will be displayed.
3 Select the Consistency Groups tab and click the + icon to create a
Consistency Group. The Create a Consistency Group wizard opens.
In the Name field input: FASTVP_CG. Click Next to continue the wizard.
In the Populate Consistency Group section click the + icon and select Create
new LUNs from the dropdown list.
Number of LUNs: 3
Name: CG_LUN
Pool: FAST VP-1
Size: 5 GB
Thin: Checked
Tiering Policy: Start High, Then Auto-Tier
Host I/O Limit: No Limit
Click OK to continue.
Also click Next in the Snapshot section and Next in the Replication section,
you will not be configuring those features yet.
The Summary section will display the configuration of the Consistency Group
to be created as shown.
4 The Results window displays the status of the operation. Please be patient, the
operation will take a moment to complete. When it completes, Close the
window.
Step Action
1 You will now create a NAS Server for accessing file storage via SMB.
In Unisphere, navigate to Storage > File > NAS Servers. Click the + icon
to create a new NAS Server. A wizard to create the NAS Server opens to
the Configure NAS Server General Settings section. Input the following
configuration:
Password: emc2Admin!
4 In the Configure NAS Server DNS section the Domain and Servers field
is populated:
Domain: hmarine.test
Servers: 192.168.1.50
Click Next.
6 You will now create a second NAS Server which will be used to access file
storage via NFS.
Click the + icon to create a new NAS Server. The wizard to create the
NAS Server opens to the Configure NAS Server General Settings section.
Input the following configuration:
9 In the Configure Unix Directory Service section, check the Enable a Unix
Directory Service using NIS or LDAP.
IP Address: 192.168.1.51
10 In the Configure NAS Server DNS section, check the Enable DNS option.
This exposes further configuration information. Input the following
configuration:
Domain: hmarine.test
Step Action
1 You will now configure a file system for SMB file storage.
In Unisphere navigate to Storage > File > File Systems. Click the + icon to create
a new file system.
A wizard opens for creating the file system. In the Configure the Protocols the File
System Supports section, select the Windows Shares (SMB) radio button.
From the NAS Server dropdown list, the NAS_SMB should be selected as it is the
only NAS Server available configured for SMB.
Name: SMB_fs
Description: File system for NAS_SMB NAS Server
3 In the Configure the File System Storage Characteristics section, input the following
configuration:
4 You will not configure a share for the file system at this time so in the Configure the
Initial Share section click Next to continue the wizard.
You will not configure Snapshots for the file system at this time so in the Configure
Snapshot Schedule section click Next to continue the wizard.
You will not configure Replication for the file system at this time so in the Provide a
Replication Mode and RPO section click Next to continue the wizard.
5 The Summary section displays the details of the file system creation as shown.
The Results section will display the status of the file system creation.
6 You will now configure a file system for NFS file storage.
From the File Systems page, click the + icon to create a new file system.
The wizard to create a file system opens. In the Configure the Protocols the File
System Supports section, select the default of Linux/Unix Shares (NFS) radio
button.
From the NAS Server dropdown list, the NAS_NFS should be selected as it is the
only NAS Server available configured for NFS.
Name: NFS_fs
Description: File system for NAS_NFS NAS Server
8 In the Configure the File System Storage Characteristics section, input the following
configuration:
9 You will not configure a share for the file system at this time so in the Configure the
Initial Share section click Next to continue the wizard.
You will not configure Snapshots for the file system at this time so in the Configure
Snapshot Schedule section click Next to continue the wizard.
You will not configure Replication for the file system at this time so in the Provide a
Replication Mode and RPO section.
10 The Summary section displays the details of the file system creation as shown.
The Results section will display the status of the file system creation.
Step Action
Step Action
Computer(s): WIN1
Click the Connect button.
From the Windows Security window select More choices
Select Use a different account
From the Enter your credentials window, input the following;
Username: \administrator
Password: emc2Local!
Click Ok
Click Yes to any Certificate errors
2 From the WIN1 system taskbar, click the iSCSI Initiator icon to launch the
application.
Select the Discovery tab. Click the Discover Portal button. In the
Discover Target Portal window, in the IP address or DNS name field input:
192.168.3.100
Select the Targets tab. In the Discovered targets section the UnityVSA-
Source IQN is displayed with an Inactive status. Click the Connect button
to connect the initiator to the target.
From the Advanced Settings window, in the Local adaptor dropdown list,
select Microsoft iSCSI Initiator. In the Initiator IP dropdown list, select
192.168.3.106. From the Target portal IP dropdown list, select
192.168.3.100 /3260. Click OK to configure the settings.
Step Action
1 From your Student Desktop system, open the Unisphere session to UnityVSA-
Source navigate to Access > Initiators.
2 Verify the WIN1 Initiator is displayed. You may need to refresh the Unisphere
page.
Note: The initiator displays a green circle with a white check icon along with a
blue square, indicating that the initiator is not yet associated with a host.
In the next step you will register this initiator to a host.
3 Navigate to Access > Hosts. Click the + icon and from the dropdown list select
Host. The Add a Host wizard opens. Input the following configuration:
Name: WIN1
Description: Windows WIN1 host
Operating System: Windows Server
Network Address: 192.168.1.11
Tenant: (not configurable for VSA Community Edition)
4 In the Select Discovered Initiators or Manually Add Initiators section, check the
WIN1 initiator IQN checkbox to register the initiator with the host.
Click Next to continue the wizard.
5 The Summary > Review the host configuration window screen displays the
configuration of the host to be registered as shown.
The WIN1 host will now be listed and indicate it is a registered host by the white
check in the green circle.
6 Navigate to Storage > Block > LUNs and double click on WIN1 LUN0 to open
its properties page.
Select the Host Access tab.
Click the + icon to configure host access to the LUN.
The Select Host Access window opens.
Check the WIN1 host checkbox.
Click OK to configure the host access to the LUN.
Close the properties page window.
This completes part 3 of the lab exercise.
Step Action
1 From the WIN1 RDC session launch, Computer Management from the
desktop or taskbar.
2 Navigate to Storage.
Locate the disk 5 GB. This disk is associated with the LUN you created.
Right click the disk and bring it Online.
Once it displays Not Initialized, right click and select Initialize disk. Use
the default setting and click OK.
Right click the unallocated space and select New Simple Volume. The
New Simple Volume Wizard opens. Click Next to continue the wizard.
In the Specify Volume Size window, accept the default size and click Next
to continue the wizard.
In the Assign Drive Letter or Path window, accept the default settings and
click Next to continue the wizard.
In the Format Partition window, accept the default settings for File System,
Allocation unit size. In the Volume label field input WIN1 LUN0 and
Perform a quick format.
Right click in the window and select New > Text Document.
You have verified host access and successfully written data to the LUN.
If you see the following window after closing Computer Manager. Select
Cancel here.
Step Action
1 From your Student Desktop system desktop or taskbar click the PuTTy
icon to launch the application.
In the PuTTY screen Host Name (or IP address) field input: Linux1 and
click the Open button.
You are now logged in as root to the Linux1 client as indicated by the #
cursor symbol.
2 In this step you will identify the initiator IQN for the Linux system.
more /etc/iscsi/initiatorname.iscsi
Run the following command to start the iscsid process and login to the
Unity iSCSi target:
3
/sbin/iscsiadm –m discovery –t sendtargets –p 192.168.3.100
The output will display the Unity data port IP address, port number, and
IQN.
Start the iSCSI service by issuing the command:
service iscsi start
Verify the service is started by issuing the command:
service iscsi status
Verify the Target IQN and Portal is displayed in the beginning of the
output as shown in the example below.
Step Action
1 Return to your Unisphere session to the UnityVSA-Source system. Refresh your login
if the security session has expired. Navigate to Access > Initiators.
Note: The initiator displays a green circle with a white check icon along with a
blue square indicating that the initiator is not yet associated with a host.
2 Navigate to Access > Hosts. Click the + icon and from the dropdown list select Host.
The Add a Host wizard opens. Input the following configuration:
Name: Linux1
Description: Linux1 host
Operating System: Linux
Network Address: 192.168.1.111
(This is the IP address of eth0 on the Linux host)
Tenant: (not configurable for VSA Community Edition)
3 In the Select Discovered Initiators or Manually Add Initiators section, check the
Linux1 initiator IQN checkbox to register the initiator with the host.
Click Next to continue the wizard.
4 The Summary > Review the host configuration screen displays the configuration
of the host to be registered as shown.
The Linux1 host is now listed as a registered host as indicated by the white check in
the green circle.
5 Navigate to Storage > Block > LUNs and double click on Linux1 LUN0 to open its
properties page.
Select the Host Access tab.
Click the + icon to configure host access to the LUN.
The Select Host Access window opens.
Check the Linux1 host checkbox.
Click OK to configure the host access to the LUN.
Close the properties page window.
This completes part 2 of the lab exercise.
Step Action
1 From your Student Desktop open the existing SSH session to the Linux1
system.
powermt config
The output of the command will display the Psuedo name PowerPath has
assigned to the new LUN. Verify the Pseudo name in the output as shown:
fdisk –l
The command will display all of the disk devices the system can see. Locate the
/dev/emcpowerb in output as shown.
fdisk /dev/emcpowerb
The command launches a wizard to partition the disk. You will create a Primary
partition on the disk with an offset of 128 disk blocks. Enter the bolded
responses at each of the wizard prompts shown.
Command action
e extended
p Primary Partition (1-4) p
fdisk –l
mkfs.ext3 /dev/emcpowerb1
6 Now you will create a mountpoint on the system to mount the disk device to by
running the following command:
mkdir /emcpowerb
Now you will mount the disk device to the mountpoint by running the following
command:
mount
7 Now you will write data to the LUN by creating a file containing some text by
running the following command.
echo “This is a line of text written to the newfile created on the LUN”
> /emcpowerb/newfile
Now verify the data was written to the LUN by running the following command:
cat /emcpowerb/newfile
exit
This concludes the lab. You have configured a data network port on the Dell
EMC UnityVSA, discovered the Target using the Linux native iSCSI Initiator,
attached the Linux host to the Dell EMC UnityVSA LUN, formatted the device,
and wrote data to it!
Purpose: Create SMB shares to a Unity file system and access its
file storage from a Windows SMB client.
Step Action
2 In Unisphere navigate to Storage > File. Select the SMB_fs file system, place a
check in its checkbox and uncheck any other file system. From the More
Actions dropdown list select Create an SMB share (CIFS).
3 A wizard to create a share opens to the Select a source for the new share
section. In the File System field the SMB_fs will be listed. The radio button
option is selected for the File System “SMB_fs”. The option to create the share
on a Snapshot of the file system is grayed-out since there are no snapshots of
the file system.
4 In the Provide SMB share name and path section input the following
configuration:
Local Path: /
5 The Provide SMB share details section of the wizard lets you configure various
advanced SMB properties and offline availability options. In this lab you will
keep the default values.
6 The Summary section of the wizard displays the configuration summary for the
share as shown:
Click the SMB Shares tab. Verify the Top$ share is listed.
Username: hmarine\administrator
Password: emc2Admin!
Click Ok
9 You will now open the file system share by accessing its share name from the
NAS server that is associated with the file system.
10 The share to the file system opens. In the Explorer window, select the View tab.
Ensure the Hidden items is checked as shown below:
You will see the .etc and lost+found folders that are present at the top-level of
all Unity file systems. These folders are used internally by the file system and
should not be disturbed or modified. As an administrator, you can control the
on-disk permissions to this top-level shared area of the file system.
The Top$ (\\NAS_SMB) properties window opens, select the Security tab.
11 A permissions window to the share opens. The Everyone group is listed and
has Full control permissions by default. As the domain administrator you can
add discrete administrative permissions.
12 A window for adding users and groups opens. In the Enter the object names to
select field input: Domain Admins and click the Check Names button. The
group will appear underlined when it is located within the domain.
13 The Domain Admins group is now listed on the permissions. In the Allow
column of checkboxes, check the Full control box. This automatically fills-in
additional permissions checkboxes. Click the Apply button to add the new
permission setting for the Domain Admins group.
Note: Verify the permissions for Domain Admins are Full Control before
proceeding to the next step.
14 To limit access to the top level of the file system you will now modify the
permissions for the Everyone group. In the permissions window highlight the
Everyone group. In the Allow column of checkboxes uncheck all of the
permissions except for List folder contents. Leave that permission checked.
Leave the share open. You will be accessing it in the next part of this lab
exercise.
Step Action
2 Now you will adjust permissions on the folder for specific domain user and group
access. Right-click the Sales_Data folder and select Properties. Select the
Security tab.
You will see the permissions that were set on the Top$ share, are inherited by the
folder. Click the Edit button to add permissions to the folder.
A permissions window for the folder opens. Click the Add button.
3 A window to add users and groups to the folder opens. In the Enter the object
names to select field input: Westcoast Sales; Eastcoast Sales and click the
Check Names button. The groups will appear underlined when they are located
within the domain.
4 The groups are now listed in the permissions window for the folder.
Highlight the Eastcoast Sales group and in the Allow column of checkboxes,
check the Full control permission and click the Apply button to assign the
permission for the group.
Repeat the same permissions assignment for the Westcoast Sales group.
Disconnect the RDC session to the WIN1 system by clicking the Logoff Session
icon on the WIN1 taskbar.
5 From the Student Desktop system, return to your Unisphere session. Login again
if your session has timed out. Navigate to Storage > File > SMB Shares. Click
the + icon to create a new SMB share.
6 The wizard to create an SMB Share opens. Click the grid in the File System field.
A Select a File System for share creation window opens. Select the SMB_fs for
the file system and click Select.
8 Keep the default options for the Advanced wizard section and click Next to
continue.
11 From the Student Desktop system taskbar, launch the RDC application.
You will login to the WIN1 system as a user who is a member of the Westcoast
Sales group.
Username: hmarine\swall
Password: emc2Admin!
Click Ok
Right click in the share window and select New > Text Document. Name the file
Swall. Open the file and write a line of text indicating the current time as seen on
the WIN1 system clock.
Were you able to write this file and save it? __ _____________
Logoff the WIN1 RDC session by clicking the Logoff session icon on the WIN1
Desktop or taskbar.
14 From the Student Desktop system, launch the RDC application again.
15 You will login to the WIN1 system as a user who is a member of the Propulsion
Engineers group.
Username: hmarine\epratt
Password: emc2Admin!
Click Ok
16 From the WIN1 Desktop or system taskbar click the Run icon.
Step Action
Username: hmarine\administrator
Password: emc2Admin!
Click Ok
2 From the WIN1 system taskbar click the Computer Management icon to
launch the application.
4 With the radio button option selected for Another computer, in the field
input: NAS_SMB and click OK.
5 Expand the System Tools tree object. Please be patient, this can take a
moment to complete.
6 Right-click the Shares object and select the New Share option. This
opens a wizard to create a new shared folder. Click Next to continue the
wizard.
7 The wizard will configure a path for the shared folder. Click the Browse
button.
In the Browse for Folder window the structure for the NAS server is
displayed. Single click the SMB_fs file system and it populates the Folder
field.
Click the Make New Folder button. Name the folder Engineering_Data
and click the OK button.
8 The next wizard window names the share. You will accept the default
values here.
9 The next wizard window sets permissions on the folder. Select the radio
button option for Customize permissions and click the Custom button.
The window displays tabs for Share Permissions and Security. The Share
Permissions relates to permissions for seeing the shared item over the
network. The Security tab relates to on-disk permissions for the folder.
You will be modifying both sets of permissions. Select the Share
Permissions tab. For the Everyone group, in the Allow column of
checkboxes, check the Full Control permission. This setting will allow the
share to be seen by all users.
Next you will customize the on-disk permissions for a specific group.
Select the Security tab.
A window to add users and groups to the folder opens. In the Enter the
object names to select field input: Propulsion Engineers and click the
Check Names button. The group will appear underlined when it is located
within the domain.
Click OK to continue.
12 From your Student Desktop access the open session to Unisphere. If the
session has timed out login again. Navigate to Storage > File > SMB
Shares and refresh the page.
Username: hmarine\epratt
Password: emc2Admin!
Click Ok
14 Click the Run icon on the WIN1 system taskbar and in the Open field
input: \\NAS_SMB\Engineering_Data and click OK. A window to the
share will open.
15 Right-click in the share window and select New > Text Document. Name
the file epratt. Open the file and add text to the file indicating the user who
wrote the file and the current time displayed on the WIN1 system. Save
and close the file.
16 Right-click on the file and select Properties. Select the Security tab and
click the Advanced button. Who is the file Owner? _________
______________________
Close the share window and logoff the RDC session to WIN1.
Purpose: Create NFS shares to a Unity file system and access its
file storage from a Linux NFS client.
Step Action
2 Navigate to Storage > File > NFS Shares. Select the + icon to create a
new NFS share.
3 The wizard to create a new NFS share opens to the Select a source for
the new share section. Click the grid in the File System field and a window
opens to select a Unity file system for creating the share. Double-click the
NFS_fs to select it for the share. The radio button option is selected for
the File System “NFS_fs”. The option to create the share on a Snapshot of
the file system is grayed-out since there are no snapshots of the file
system.
4 In the Provide NFS share name and path section input the following
configuration:
5 The wizard now presents the access configuration of the share. You will
configure specific access for a single client having root privileges on the
file system.
In the Access Type field select the Read/Write, allow Root setting.
In the Hosts section, select the Linux1 host by checking its checkbox
and click OK.
7 The wizard presents a Results window for the creation operation. Verify
the operation completed successfully and click Close to exit the wizard.
8 From the Student Desktop system taskbar click the PuTTY icon to launch
the application.
In the PuTTY screen Host Name (or IP address) field input: Linux1 and
click the Open button.
You are now logged in as root to the Linux1 client as indicated by the #
cursor symbol.
10 Now you will create an empty directory at the root of the client to use as a
mount point for mounting to the NFS share.
11 You will now mount the newly created NFS share to the mountpoint.
12 Issue the command: cd /nfs to change directory and access the share on
the file system.
View the content of the file system by issuing the command: ls –la
You will see the .etc and lost+found folders that are present at the root of
the Unity file system. These folders are used internally by the file system
and should not be modified.
13 As the administrator, you have root user access to the file system via this
share.
You can now create sub-folders on the file system to use for additional
shares for the user community. Create a sub-folder on the file system by
issuing the command: mkdir engineering_data
Review the output and record the following information for the folder
Step Action
1 You will now use the newly created engineering_data folder to create a lower-
level NFS share of the file system for a specific NFS user group. To do this you
will change the folder mode bits, owner, and group.
3 You will now unmount the NFS share. First, stop accessing the share by
changing directory out of the mount point, issue the command: cd /
4 Return to your Unisphere session. Refresh your login if the security session has
expired. Navigate to Storage > File > NFS Shares
5 The wizard to create a new NFS share launches. Click the grid in the File
System field to select a file system. From the list highlight the NFS_fs and click
the Select button.
6 The share name and its path are will now be configured.
7 The wizard now presents the access configuration of the share. You will
configure Read/Write access for a subnet.
From the Configure Access window, in the Default Access field keep the default
No Access setting.
In the Access Type field select Read/Write from the dropdown list.
In the Hosts section, click More Actions and from the dropdown list, select Add
Subnet.
The newly added Engineering network is now listed in the Hosts: section.
Select it by checking its checkbox and click the OK button.
8 The wizard presents a summary screen for the NFS share configuration it will
create as shown here:
9 The wizard presents a results window for the creation operation. Verify the
operation completed successfully and click Close to exit the wizard.
10 From the Student Desktop system taskbar, click the PuTTY icon to launch the
application.
In the PuTTY screen Host Name (or IP address) field input: Linux1 and click the
Open button.
You are now logged in as root to the Linux1 client as indicated by the # cursor
symbol.
12 Mount the engineering NFS share to the mount point by issuing the command:
13 You will now test NFS share access using the epallis user who is a member of
the engprop NFS users group.
Verify the text is present in the file by issuing the command: more epallis
Look at the file permissions bits, owner and group by issuing the command: ls –l
14 Now you will test access to the share as another user who is not a member of
the engprop NFS user group. Switch user to swoo by issuing the command: su
swoo
View the content of the epallis file by issuing the command: more epallis
Create a file with some text added to it by issuing the command: echo “this is
some text written to the file as swoo” > swoo
Why could the user read from the share but not write to it?
_______________________________________I
________________________________________________________________
Step Action
2 Before creating VMware storage resources, you need to add VMware hosts
to the storage environment so you can configure host access later.
Navigate to Access > VMware > vCenters. Click + to open the Add
vCenter wizard.
3 To discover your ESXi host, in the Discover ESXi hosts in the vCenter
section enter the following settings:
4 A list opens that includes any ESXi host(s) managed by this vCenter server.
Locate and check ESXi host esxi60-1.hmarine.test.
Note: The job will continue to run in the background if you close the page
before it completes.
Click the Virtual Machines tab. There will not be any VMs listed at this time.
Click the Virtual Drives tab. There will not be any Virtual Drives listed at this
time.
Step Action
You will see the initiator for the ESXi host esxi60-1.hmarine.test.
Note the initiator has a yellow icon indicating there are no logged in initiator paths
A wizard to create a new datastore opens to the VMware Datastore Type section.
3 In the Enter a name for the datastore section input the following:
Name: VMFS_Datastore
Description: VMFS datastore for esxi60-1 host
4 In the Configure the storage for this datastore section, input the following
configuration:
5 In the Configure Access section, click the + icon to define host access to the
datastore.
In the Configure Snapshot Schedule section you will not be configuring snapshots
for the datastore. Click Next to continue.
In the Provide a Replication Mode and RPO section you will not be configuring
replication for the datastore. Click Next to continue.
A Results screen will show the progress and status of the created datastore.
Note: If the browser will display a security certificate warning. Click the Continue
to this website (not recommended) option. You will need to click this twice.
Click Login.
8 The VMware vSphere Web Client opens. From the left navigation pane, navigate
to Home. From the Inventories section, select the Hosts and Clusters object as
shown:
9 If not already expanded, expand the tree vcsa.hmrine.test > Datacenter and select
the esxi60-1.hmarine.test host. Select the Manage tab from the page, and then
select the Storage sub-option and Storage Devices as shown:
The storage associated with this host is listed. The newly created and assigned
storage device is listed along with various details.
10 Now select the Related Objects tab and select the Datastores sub-option as
shown: (You will have to use the slide bar)
You will see the VMFS_Datastore listed with several details including the format
type. The storage resource is now ready for use within VMware.
As you can see, VMware integration with Unity provides ease of storage
provisioning and access. The ESXi host initiator is automatically registered in
Unity. Once created, the storage object is mounted and formatted as a virtual
machine file system, and is ready for use within VMware.
Leave the vSphere Web Client browser tab open, you will use it again in the next
part of the lab exercise.
Step Action
3 In the Enter a name for the datastore section input the following:
Name: NFS_Datastore
Description: NFS datastore for esxi60-1 server
4 In the Configure the storage for this datastore section, input the following
configuration:
Click the + icon to customize access to the datastore for a specific host.
In the Provide a Replication Mode and RPO section you will not be
configuring replication for the datastore. Click Next to continue.
A Results screen will show the progress and status of the created
datastore.
7 Return to the open vSphere Web Client tab. The navigation in the left
pane should be set to Hosts and Clusters with the esxi60-1.hmarine.test
host selected. The Related Objects tab should be selected on the page
with the Datastores sub-option selected as shown.
Confirm the NFS_Datastore that you just created is now available to the
host for VMware use.
From the information listed about the new datastore, record the value
shown for its Type: ___
This demonstrates again the integration Dell EMC Unity provides for
VMware. The NFS datastore has automatically mounted the Unity storage
resource and it is ready for use within VMware.
Step Action
1 From your Student Desktop system open a Unisphere session to the UnityVSA-
Source system at IP address 192.168.1.113
From the Unisphere user interface, open the System Settings window.
3 From the License Management page of the Software and Licenses > License
Information section, look for the Quality of Service (QoS) license.
Verify that the feature has a green check mark in front of it meaning that the license
is installed and the feature is operational.
From the page host I/O limit policies can be created and any existing policies are
displayed. It also has a link to the Host I/O settings page which was viewed in the
previous step.
8 From the Student Desktop system taskbar open a RDC session to WIN1.
Username: \administrator
Password: emc2Local!
Click Ok
Expand the Local Disk (C: ) tree and open the Big_Files folder.
There are some sizeable files located in this folder which will be used to generate
some write I/O to the WIN1 LUN0.
11 Double-click on the WIN1 LUN0 (E: ) disk from the Windows Explorer navigation
pane.
Paste the files into the drive. Wait for the copy operation to complete.
Observe in the graphic the Bandwidth KB/s and Throughput IO/s used by the host
to perform the copy operation.
1 In this part of the lab we are going to create a Host I/O Limits policy and
associate it to WIN1 LUN0.
2 From the page we are able to define Host I/O Limit policies. Limiting I/O
bandwidth and throughput provides more predictable performance in
system workloads between hosts, their applications, and storage
resources.
Click the + icon to create a new limit. The Create Host I/O Limit wizard
opens.
Name: Silver_Policy
Description: Good (Class – Service)
Shared: Unchecked
Limit Type: Absolute Limit (radio button selected)
Maximum IO/S: 800
Maximum Bandwidth: 9000 KBPS
I/O traffic to block storage resources (LUNs, Consistency Groups) can be
limited accordingly to the threshold that is configured here (throughput
and/or bandwidth).
4 In the Select Storage Resources to Associate with the I/O Limit section
select WIN1 LUN0.
Name: Gold_Policy
Description: Better (Class – Service)
Shared: unchecked
Limit Type: Absolute Limit (radio button selected)
Maximum IO/S: 1000
Maximum Bandwidth: 11000 KBPS
Storage Resource: Linux1 LUN0
Create a third policy with the settings below:
Name: Platinum_Policy
Description: Best (Class – Service)
Shared: Checked
Limit Type: Absolute Limit (radio button selected)
Maximum IO/S: 2000
Maximum Bandwidth: 20480 KBPS
Storage Resource: CG_LUN-00, CG_LUN-01, CG_LUN-02
Note there is a Host I/O Limit Silver Policy associated with the LUN.
Observe that both bandwidth and throughput graphics show a line for the
limits. Change the frequency range to Real Time. Wait at least 1 minute for
the graphic to refresh and populate with information. Both I/O measures
should default to zero since there is no write activity from the Host to this
LUN at the moment. The limit lines are still displayed in the graphic.
12 This part of the lab exercise is complete. You have successfully created a
Host I/O Limits absolute policy and associated it with block storage
resource.
Step Action
5 From the FAST VP-2 properties window navigate to the Usage tab.
The NAS servers and file systems that were created in the storage pool
are displayed.
Select the SMB_fs and note the value listed for it in the Total Pool Space
Used (GB) column. ____________
7 From the SMB_fs Properties window change the size field to 10 GB.
Note: Manually extending a thin file resource increases the visible (virtual)
size of the resource without increasing the actual size allocated to the
resource from the pool.
For thick file systems, the extend operation increases the actual space
allocated to the resource from the pool.
9 From the FASTVP-2 Properties page > Usage > select Storage
Resources.
Click the Refresh icon and note the value for the SMB_fs Total Pool
Space Used (GB)
Was there a change in size after the extension of the file system?
_____________________
10 From the Usage tab, select the Capacity option. Record the following:
Have you noticed any changes besides the advertised file system size?
_______
Step Action
1 In this lab section we will manually shrink the capacity of a thin file system
using the Unisphere.
3 From the FAST VP-2 properties window navigate to the Usage tab.
The default Capacity option is selected and the Current Pool Capacity is
displayed.
A bar graph showing space related information for the pool is displayed.
Mouse over the graph to display its used and free space information. The
pool subscribed information is also shown on the page. The subscribed
space used is the percentage of the pool’s total space that has been
requested by its associated storage resources. When this value is over
100%, the pool is oversubscribed. For example, you can create a thin
provisioned file system having a size that is greater than the pool’s
capacity and the pool would then be oversubscribed.
The NAS servers and file systems that were created in the storage pool
are displayed along with the space they are using from the pool and space
consumed by their snapshots.
Review the values displayed in the Total Pool Space Used (GB) column.
Add all of these values together and verify that the sum correlates to the
Pool’s Used space you recorded above.
Select the SMB_fs file system and record its Total Pool Space Used
(GB) value. ____ ___
Click on the Edit icon (pencil) or double-click the selection to open its
properties.
7 A warning message is displayed alerting the user the file system will be
reduced in size with an estimate of how much space will be returned to
the pool.
Did the Pool free space value increase from the value recorded in step 5
above? ________ __
Did the increase in Pool free space correlate to the value recorded in step
7? ____
9 From the FAST VP-2 Properties page, select the Usage tab then select
Storage Resources.
What is the Total Pool Space used by the SMB_fs file system? __
Notice that the space this file system uses from the pool is actually greater
that the file system’s capacity. To explain this, when a new file system is
created it uses space from the pool corresponding to its Minimum
Allocation size which is 3 GB in this case. It also allocates another 3 GB of
space used for tracking the pool slices that the file system uses. This is
metadata needed for file system operations as data gets stored on the file
system and as extensions to the file system are made.
Step Action
1 In this lab we will check if the FAST VP feature is licensed on the system
and verify its status.
From your Student Desktop system open a Unisphere session to the lab
UnityVSA-Source Unity system (IP address 192.168.1.113).
2 To check if FAST VP can be set in our Unity system we must verify if the
feature is licensed and enabled.
3 From the License Management window, look for the FAST VP license.
Verify that the feature has a green check mark in front of it meaning that the
license is installed and the feature is operational.
4 FAST VP settings are managed at the System Settings level and at the
storage resource levels.
Note that the data relocation can be paused and resumed by clicking on the
Pause tab.
The Schedule data relocations can be enabled or disabled using the check
box.
Prior to the change, if there were data scheduled for relocation, then the
FAST VP Settings page will calculate the amount of data to relocate and
update the information on the window.
The FAST VP tab shows the following information for the heterogeneous
pool:
Also note that the data relocation can be manually started from this page
and that the Manage FAST VP system settings window can also be
launched from here by clicking on the blue text.
Step Action
1 This part of the lab demonstrates how to check the data relocation
operation from a LUN and from a storage pool. You are going to perform a
simple write operation to WIN1 LUN0 and observe how FAST VP will
relocate the data depending on the storage tier policy assigned to the
storage resource.
Username: administrator
Password: emc2Local!
Click Ok
3 From the WIN1 Desktop or taskbar click the File Explorer icon.
Expand the Local Disk (C: ) tree and open the Big_Files folder.
There are some sizeable files located in this folder which will be used to
generate some write I/O to the WIN1 LUN0 disk.
4 Select the four 1 GB files, then right click and select copy.
5 Select the WIN1 LUN0 (E: ) disk from the Windows Explorer navigation
pane.
Paste the files into the drive. Wait for the copy operation to complete.
You may notice that the LUN usage values do not increase to match what
was written to the LUN. This is caused by the sparse files used in the copy
operation and client-side caching.
___________________________
You may notice that the data on the LUN is distributed across multiple
tiers and does not reside in only the highest tier. The distribution of data
depends on the tier having space available from the pool. If there is no
space on the highest tier, space is allocated from the next highest tier
having space available for the data. The available space for the tiers
within the pool is not predictable for this lab exercise; it varies based on
past activities you may have performed. You are recording the distribution
above so that when you change the tiering policy, you can see its effect
on the data distribution.
Change the Tiering Policy to Lowest Available Tier and click Apply.
11 In the Start Data Relocation window, enter the following settings if not
already selected:
Note that the Move Down (GB) column is immediately populated with the
total amount of data that is to be allocated to the lowest available tier
possible because of the tiering policy chosen for WIN1 LUN0.
Note: you may need to wait several minutes for the data distribution
values to change. Closing and opening the LUN Properties page will
refresh the data.
Change the Tiering Policy to Start High then Auto Tier and click Apply.
14 Navigate to Storage > Pools. Double click the FAST VP-1 storage pool.
Click Stop Relocation to interrupt the current data relocation. Then click
Start Relocation.
16 In the Start Data Relocation window enter the following settings if not
already selected:
Note that the Move Up (GB) column is immediately populated with the
total amount of data being allocated to a higher tier because of the tiering
policy chosen for WIN1 LUN0.
17 From your Student Desktop open the existing RDC session to WIN1. In
the open File Explorer window delete all the files that were copied to the
WIN1 LUN0 and leave the existing New Text Document file.
This part of the lab exercise is complete. You have successfully observed
the data relocation based on choice of Tiering Policy associated with a
storage resource.
Step Action
The tab is divided in two sections: File System and Quota Tree. The
default section is File System showing the User Quota Report page that
displays the file system storage space consumed per user.
5 From the Create User Quota wizard window, click the + icon to open the
Configure User window.
User: hmarine.test\Swest
8 On the Limits page, specify the Soft Limit and a Hard Limit for the User
Quota.
A Soft Limit, when surpassed, will begin the Grace Period countdown. The
user can continue to write to the file system until the Grace Period expires.
The Grace Period is modifiable and defaults to 7 days.
The Hard Limit stops any write activity when it is reached, regardless of
any Grace Period.
Soft Limit: 1 GB
Hard Limit: 3 GB
9 The quota settings are displayed on the Review Your Selections section
as shown here.
11 The new User Quota will be displayed in the User Quota Report page.
Step Action
Username: hmarine\swest
Password: emc2Admin!
Click Ok
Expand the Local Disk (C: ) tree and open the Big_Files folder.
4 From the WIN1 Desktop or system taskbar click the Run icon.
5 Paste the file into the share. Wait for the copy operation to complete.
Click the Refresh icon to update the information displayed on the User
Quota Report.
Is there any change to storage consumption for the Swest user? ______
Note: You should not see any update to the user quotas when you click
refresh.
7 From the User Quota Report tab of the SMB_fs Properties window click
the Manage Quota Settings link.
8 In the Manage Quota Settings dialog box, you realize that User Quotas
were never enforced.
Click the checkbox for Enforce User Quotas and click OK.
9 From the Quotas tab of the SMB_fs Properties window, click the Refresh
icon to poll updated information about your User Quotas.
10 Verify the User Quota for Scott West has changed its state, and its Soft
Limit Usage has been fully consumed.
You can also verify that there are three other entries in User Quota Report
for the other users (administrator, Swall, and Epratt) who have also
accessed the file system. Notice that there are no limits defined for them.
Also notice that users are list by User ID and not by Windows names.
The Edit Selected User Quota Limits window opens. It displays the User
ID and the Windows Names for the user.
11 Next, you are going to test the Hard Limit defined in the user quota policy
for Scott West.
12 From the Local Disk (C: )\ Big_Files folder, copy 1GBFile-2 and 1GBFile-
3 to the clipboard.
The error message is due to the User Quota’s Hard Limit restricting the
consumable space for the user swest. Click Skip to end the copy
operation.
Verify that only one of the files was copied to the directory.
Click the Refresh icon to update the information displayed on the User
Quota Report.
Notice that the Usage (GB) of the Swest account has increased above 2.0
GB. One of the files could not be copied copy because it caused the 3 GB
hard limit to be exceeded.
Observe that the Soft Limit has been exceeded and the Grace Period (7
days) has been activated.
17 In the User Quota Report page, observe that the User Quota Hard Limit
has been increased to 5.0 GB.
19 From the Local Disk (C: )\ Big_Files folder, copy 750MBFile-1 to the
clipboard.
The copy process should succeed. Verify that the copied files are present
on the share.
Close the Windows Explorer windows and logoff the RDC session.
Step Action
1 In this section of the lab we are going to create a Quota Tree on a file system.
2 From the Quota tab of the SMB_fs Properties window, select Quota Tree on the
left of the window.
4 In the Create Quota Tree wizard, enter the configuration information for the new
quota tree.
Note: The path is relative to the root of the file system SMB_fs and must start with
a forward slash.
Soft Limit: 1 GB
Hard Limit: 3 GB
6 The quota settings are displayed on the Review Your Selections section as shown
here.
A green check mark specifies that the operation was completed successfully.
Step Action
1 In this section you will conduct testing of the Quota Tree configured in the
previous part of this Lab exercise.
Username: hmarine\eplace
Password: emc2Admin!
Click Ok
Expand the Local Disk (C: ) tree and open the Big_Files folder.
6 Paste the files into the share. Wait for the copy operation to complete.
From the Quota tab of the SMB_fs Properties window, click the Refresh
icon to update the information displayed.
Any changes to storage usage for the /Engineering_Data path? ___ ____
The usage for the /Engineering_Data path should have increased to ~2.0
GB.
9 From the Local Disk (C: )\Big_Files folder, copy the 500MBFile-1, and the
750MBFile-1 files.
One of the files will get copied to the share but the copy of the second file
is interrupted with the message displayed here.
The only way to allow this copy operation to complete is to increase the
Hard Limit of the Quota Tree for the /Engineering_Data directory.
From the Quota tab of the SMB_fs Properties window, Select Quota Tree.
Double click the quota for the Engineering_Data path.
12 From the Quota Tree Properties window, notice that the Soft Limit has
been exceeded and the Grace Period (7 days) is activated.
Modify the Hard Limit to 5 GB and click Apply. Then click Close.
14 In the error message left open in a previous step, click Try Again to
continue with the copy operation.
The operation should be successful this time. You should now see two 1
GB files, one 750 MB file and a 500MB file in the share.
Close the Windows Explorer windows and logoff the RDC session.
Step Action
2 From the SMB_fs Properties page, select Quota > Quota Tree. Double
click the quota tree /Engineering_Data.
3 From the Quota Tree Properties window, select the User Quotas tab.
In the Create User Quota wizard, click the + icon to add a user.
Soft Limit: 1 GB
Hard Limit: 3 GB
8 The quota settings are displayed on the Review Your Selections section
as shown here.
Note that the user name is NOT shown, but the User ID that corresponds
with the username is shown. Double click the quota to verify the username
in the Edit Selected User Quota Limits window.
At the top of the Quota Tree Properties this page, check the Enforce User
Quotas checkbox.
Step Action
1 In this section you will test the User Quota configured on the Quota Tree
created previously in this lab exercise.
Username: hmarine\epratt
Password: emc2Admin!
Click Ok
Expand the Local Disk (C: ) tree and open the Big_Files folder.
6 Paste the files into the share. Wait for the copy operation to complete.
7 Now try copying the 500MBFile-1 and 750MBFile1 files from Big_Files to
Engineering_Data.
One of the files will get copied to the share but the copy of the second file
is interrupted with the message displayed here.
From the User Quotas tab in the Quota Tree Properties page, click the
Refresh icon to update the information displayed.
Observe that the usage of the Epratt account has increased due to the
copy operations. The hard limit was exceeded when trying to copy one of
the last two files. Notice that one file did get copied to the share.
Notice that the Soft Limit has been exceeded and the Grace Period (7
days) has been activated.
11 In the error message left open in a previous step, click Try Again to
continue with the copy operation.
The operation should be successful this time. You should now see two
1GB files, one 750MB file and a 500MB file in the share.
The operation completes and all the files copied are on the share.
Close the Windows Explorer windows and logoff the RDC session.
Purpose: In this lab you will move a LUN from one storage pool to
another.
Step Action
2 Navigate to Storage > Block > LUNs. Select the Linux1 LUN0.
This LUN is currently provided from the FAST VP-1 storage pool. You will
move the LUN to a different storage pool on the system. Before moving
the LUN you will access its data from the Linux1 host to see how the
move operation is transparent to the host.
3 Launch a Putty session from the taskbar and establish an SSH session to
the Linux1 system.
You are now logged in as root to the Linux1 client as indicate by the #
cursor symbol.
4 Verify that the host has the LUN mounted by running the df –h command.
Verify in the output a file named newfile and a folder named lost+found.
5 You will now create and run a script that displays the current date and lists
the content of the LUN every two seconds. This script will run during the
LUN move operations to demonstrate how the move is transparent to the
host data access on the LUN
Enter the following: while true; do date; ls –l; sleep 2; echo; done
The script will continue displaying a varying time value on each loop to
indicate it is still running.
Thin; Checked
The right side of the page will display the move session progress. It
should show Running state.
7 Return to your PuTTY session and verify the script is still running. The
second value in the date output will increment with each loop.
This verifies that the move operation does not affect host data access.
Refresh the page. The move session should now show Completed.
9 Initiate another Move operation to return the LUN to the FAST VP-1 pool.
From More Actions select Move.
Thin; Checked
10 Return to your PuTTY session and verify the script is still running with the
second value changing with each loop.
Stop the script by pressing the <Ctrl> <c> keyboard keys at the same
time. The scrip will stop and return the prompt.
11 In the Unisphere session, refresh the screen and verify the move
operation is complete and the Linux1 LUN0 is back on the FAST VP-1
pool.
Step Action
Username: \administrator
Password: emc2Local!
Click Ok
2 From the WIN1 Desktop or taskbar launch File Explorer. Select WIN1
LUN0 drive and open the text document created in the earlier exercise.
Add a line of text to the document: This line was written to the LUN
from WIN1 prior to the initial snapshot.
3 From your Student Desktop system taskbar launch Mozilla Firefox and
establish a Unisphere session to the UnityVSA-Source system and login.
Navigate to Storage > Block > LUNs and select WIN1 LUN0.
4 Select the Snapshots tab and click the + icon to create a snapshot of the
LUN.
The Create Snapshot window opens. In the Name field, replace the
default system provided name with: Initial_snap
In the Description field input the current time as displayed from the
Student Desktop taskbar.
The window displays several Local Retention Policy options with the Pool
Automatic Deletion Policy selected. You will keep this option; it allows the
snapshot to be retained until the pool the LUN was created from reaches
some pre-defined capacity threshold. Then delete the snapshot and return
the space back to the pool. The Retain Until option can be configured to
retain the snapshot to a specified calendar date and time for up to a year.
The No Automatic Deletion option will prevent the snapshot from being
deleted.
5 With the LUN Snapshots tab still open select the Snapshot Schedule
option.
The list displays three system defined schedules. Select the Default
Protection schedule and review its creation and retention times. Select
and review the other two systems defined schedules one at a time.
Click the New Schedule button and the Create Schedule window opens.
The window provides a snapshot frequency granularity that is
hourly/daily/weekly based and also provides a retention policy
configuration. You are going to configure a snapshot schedule that
creates a snapshot every Monday morning at 7:00 AM and is retained for
7 days.
The Daily/Weekly option should be checked along with each day of the
week. Uncheck Tue, Wed, Thu, Fri, Sat, Sun and leave Mon checked.
The Retention Policy section should have the Retain for radio button
selected and set to 7 Days
7 The newly created schedule is now listed in the Snapshot schedule field.
8 Open the existing RDC session to the WIN1 host. From the open File
Explorer window, open the text document on the WIN1 LUN0 drive.
Add the following line of text: This line was written to the LUN from
WIN1 after the initial snapshot was taken.
Step Action
1 You will now access the LUN snapshot from another Windows host –
WIN2.
From your Student Desktop system taskbar, launch the RDC application
and establish an RDC session to the WIN2 host as the local administrator.
Username: \administrator
Password: emc2Local!
Click Ok
From the WIN2 system taskbar, click the iSCSI Initiator icon to launch the
application.
Select the Discovery tab. Click the Discover Portal button. In the
Discover Target Portal window, in its IP address or DNS name field input:
192.168.3.100
Select the Targets tab. In the Discovered targets section the UnityVSA-
Source IQN is displayed with an Inactive status. Click the Connect button
to connect the initiator to the target.
From the Advanced Settings window, in the Local adaptor dropdown list,
select Microsoft iSCSI Initiator.
Name: WIN2
Operating System: Windows Server
Network Address: 192.168.2.11
Check the initiator checkbox and click Next to continue the wizard.
The Results window displays the status of the operation to add the host.
When it has completed successfully Close the window.
The WIN2 host should now be listed in the Hosts window with 1 displayed
in the Initiators column.
4 You will now attach this Snapshot (initial_snap) to the WIN2 host.
Attach the snapshot In Unisphere navigate to Storage > Block > LUNs
and select the WIN1 LUN0 and click the Edit icon to open its properties
page.
Select the Snapshots tab and check the checkbox for the Initial_snap if
not already selected.
From the More Actions dropdown list select the Attach to host action.
Click the + icon to configure access. In the Access Type dropdown list
select Read/Write.
5 Open the existing RDC session to the WIN2 host. From the Desktop or
taskbar, click the Server Manager icon to launch the application.
From the upper right corner Tasks dropdown, select Rescan Storage.
7 From the WIN2 taskbar, launch File Explorer and select WIN1 LUN0
drive. Open the text document.
Is the line of text present in the file that you entered from the WIN1 host
prior to the initial snapshot? ____ _____________________________
Is the line of text present in the file that you entered from the WIN1 host
after the initial snapshot was created? ___ _______________________
_________________________________________________________
8 Add the following line of text to the file: This line was written to the LUN
snapshot from WIN2.
Open the New Text Document again, was the line written to the file?
_____________ ___________________
9 Now you will remove the snapshot disk from the host.
In Server Manager under Disks, right click the 5.00 GB disk and select
Take Offline. In the Take Disk Offline window click Yes to offline the disk.
The disk status is shown as Offline.
Close File Explorer and logoff from the WIN2 RDC session.
From the WIN1 LUN0 Properties page Snapshots tab, the Initial_snap
should still be checked. If not, check it.
From the More Actions dropdown, select Detach from host from the list.
Step Action
1 Open the existing RDC session to the WIN1 host. In its open File Explorer
window with the WIN1 LUN0 drive selected, open the text document.
Is the line of text that was written to the snapshot from the WIN2 host present in
the file? __ ____________________________________________________
Why? _________________________________________________________
Add the following line of text to the file: This line was written to the LUN from
WIN1 after the initial snapshot was taken and before the Restore
operation.
Navigate to File and Storage Services > Disks. Right-click the 5.00 GB disk
and select Take Offline from the list. In the Take Disk Offline window click Yes
to Offline the disk.
3 From your Student Desktop system open the existing Unisphere session.
From the WIN1 LUN0 Properties page Snapshots tab, the Initial_snap should
still be checked. If not, check it.
From the More Actions dropdown, select Restore from the list.
The system will automatically create a backup snapshot of the LUN to preserve
its state before initiating a restore operation. The Restore window provides a
field for the snapshot name and provides a message recommending to quiesce
IO from the host. Click OK to perform the snapshot restore operation.
The LUN has now been restored to the data state that the Initial_snap snapshot
captured.
In the Open Server Manager application right-click the 5.00 GB disk and select
Bring Online from the list. In the Bring Disk Online window click Yes to bring
the disk online.
In the open File Explorer window with the WIN1 LUN0 drive selected, open the
text document.
Is the line of text written to the LUN by WIN1 prior to the initial snapshot present
in the file? __ ___________________________________________________
Is the line of text written to the LUN by WIN1 after the initial snapshot and prior
to the restore present in the file? _ __________________________________
Is the line of text written to the snapshot from WIN2 present in the file?
______________________________________________________________
This completes the LUN Snapshot lab exercise. You have created a LUN
snapshot and a snapshot schedule. You accessed a LUN snapshot to see its
captured data state and wrote to the snapshot. You also performed a Snapshot
restore operation to restore a LUN to the data state captured in the snapshot.
Step Action
2 In Unisphere navigate to Storage > File > File Systems. Click the + icon
to create a new file system.
The Create a File System wizard opens. In the Protocol section, select the
Windows Shares (SMB) radio button. In the NAS Server list, the
NAS_SMB (Replication: None, Multiprotocol:No) is listed for the NAS
Server.
In the Pool field select FAST VP-2. Configure the size to be 5 GB. Leave
all other settings at default. Click Next to continue the wizard.
In the Shares > Configure the Initial Share section, check the SMB Share
(Windows) checkbox. Name the share: DP_FS_share. Click Next to
continue the wizard.
In the SMB Share’s Other Settings > Configure the SMB Share’s Other
Settings section, keep the defaults. Click Next to continue the wizard.
From the Snapshot schedule dropdown select the Protection with longer
retention schedule from the list. Click Next to continue the wizard.
You will not configure Replication; click Next to continue the wizard.
The Summary section displays the details of the file system creation. Click
Finish to perform the creation operation.
The Results section will display the status of the file system creation.
Close the window when the operation completes successfully.
3 Check the DP_fs file system checkbox and click the Edit icon to open its
Properties page.
Select the Snapshots tab and navigate to the Snapshot Schedule page.
It displays the schedule enabled during the file system creation. The
schedule will automatically create snapshots every day at 4:00 AM and
retain them for 7 days.
4 You will now access the DP_fs file system share and create data on it
prior to any snapshot creation.
Username: hmarine\administrator
Password: emc2Admin!
Click OK
5 From the WIN1 system taskbar click the Run icon. In the Open field input:
\\NAS_SMB\DP_FS_share and click the OK button. The share window
opens.
Right-click in the share window and select New > Text Document. Open
the file and input the following text: This line was written to the file
system prior to any snapshot creation.
1 From the existing Unisphere session, from the Snapshots tab, click the + icon
to create a new snapshot.
In the Description field input: This is the first snapshot of the file system. It
is a read-only snap.
2 Open the existing RDC session to WIN1. In the share window, open the New
text document and add the following line to the file: This line was added after
the first read-only snapshot was created.
3 Return to your open Unisphere session. In the Snapshots tab, click the + icon
to create a new snapshot.
In the Name field input: Second_snap_rw. In the Description field input: This
is the second snapshot of the file system. It is a read/write snap.
Select the radio button to set the Access Type to Read/Write (shares).
The page now lists the two manually created snapshots; one read-only snap
and one read/write snap.
4 Open the existing RDC session to WIN1. In the share window, open the New
text document and add the following line to the file: This line was added after
the second read/write snapshot was created.
5 You will now place some data on the NFS_fs file system prior to creating a
snapshot of it.
From your Student Desktop system taskbar click the PuTTY icon to launch the
application and establish an SSH session to the Linux1 system.
In the PuTTY screen Host Name (or IP address) field input: Linux1 and click
the Open button.
Add a line of text to the epallis file by issuing the command: echo “this is text
written to the file prior to the read-only snapshot of the file system.” >>
epallis
The line of text will be appended to the end of the epallis file. Verify the text is
present by issuing the command: more epallis
6 You will now create a read-only snapshot of the NFS_fs file system.
Return to your open Unisphere session. Navigate to Storage > File > File
Systems and select the NFS_fs file system by placing a check in its checkbox
and unchecking any other checkboxes.
Click the Edit icon to open the properties page and select the Snapshots tab.
Click the + icon to create a new snapshot.
In the Name field input: NFS_cvfs. In the Description field input: This is a
read-only snapshot to be accessed via NFS using the .ckpt data path.
Add a line of text to the epallis file by issuing the command: echo “this is text
written to the file after the creation of the read-only snapshot of the file
system.” >> epallis
Verify the text was appended to the end of the epallis file by issuing the
command: more epallis
From the Select a source for the new share window, click on the grid in the File
System field.
From the Select a source for the new share window, select the Snapshot for
File System “DP_fs” radio button.
Leave the Local Path setting as is to create a top-level share. Click Next to
continue the wizard.
In the Advanced > Provide SMB share details section, leave the default settings
in place and click Next to continue the wizard.
The Results screen will display the share creation process. Close the window
when the share is successfully created.
2 Open the existing RDC session to WIN1. It should have an open window to the
DP_FS_share. From the Student Desktop or system taskbar, click the Run icon
to open another window to the read/write snapshot share. In the Open field
input: \\NAS_SMB\DP_fs_RW_snap_share and click the OK button. The share
window opens.
There should now be two open share windows; one to the file system share
DP_FS_share and one to the RW snapshot share DP_fs_RW_snap_share.
From each window, open the existing New Text Document and compare them.
What are the differences between the content of the two files?
___________________________________________________
Why? _______________________________________________
Add the following line of text to the New Text Document opened from the
DP_fs_RW_snap_share: Text added to the RW snapshot.
Open the file from the DP_fs_share. Is the newly added line to the
DP_fs_RW_snap_share present in this file? __________________________
Why? ________________________________________________________
4 You will now access the read-only snapshot of the DP_fs using the snapshot
CVFS mechanism.
From your open DP_FS_share window, right click in the white space and select
Properties.
The Folder versions section lists read-only snapshots of the file system with a
date and time timestamp when the snapshot was taken. You should see the
read-only snapshot you created manually. If time had elapsed for the snapshot
schedule to have automatically created snapshots, they would be listed here.
Select the snapshot you manually created and click the Open button.
A new window opens with the snapshot path listed in its navigation field.
Right-click the New Text Document file to display the list of operations that can
be done to the file. Is the Delete option present?
_______________________________________
Why? _________________________________________________________
5 From the Network >NAS_SMB > DP_FS_share window, right click the New Text
Document to display the list of operations. Is the Delete option present?
_____________________________
Why? ________________________________________________________
6 You can now recover the original file from the read-only snapshot. In the open
dp_fs_share (nas_smb) Properties window, highlight the dp_fs_share folder and
select Restore.
Close the open windows to the file system share and the read-only snapshot.
7 You will now access the read-only snapshot of the file system from the Linux1
NFS client.
Access the existing SSH session to list the content of the NFS share by issuing
the command: ls –la /nfs
Verify you see the epallis file.
Issue the following command to see the file content: more /nfs/epallis
This is the file that resides on the file system. To view and access the read-only
snapshot of the file system, you must explicitly use the hidden .ckpt data path.
You will then see a snapshot folder having a date/time name format for when
the snapshot was created. To see the read-only snapshot, issue the following
command: ls –la /nfs/.ckpt
To access the snapshot, change directory into the snapshot folder name using
the following command: cd /nfs/.ckpt/<snapshot folder name>
List the content of the snapshot by issuing the following command: ls –la
You should see the epallis file.
Look at the file content using the following command: more epallis
Is the content of the epallis file on the snapshot different than the content of the
file on the file system? ___________________________________________
Why? ________________________________________________________
Unmount the file system by issuing the following command: umount /nfs
This completes the lab exercise. You have applied a snapshot schedule to a file
system during its creation. You have created manual Read/Write and read-only
snapshots of file systems and have accessed them.
Step Action
1 In this lab we will create Thin Clones from snapshots of a Base LUN, write
data to the LUN, and then perform a refresh of the Base LUN from the
Thin Clone snapshot.
Note: The lab requires you to go back between Unisphere and the RDC
session to WIN1. Also pay attention to the LUNs as they are presented to
the Windows host. Clones inherit the name of the Base LUN and the disk
numbers increase as the LUNs are made available to the host. In the lab
you will see three 15 GB created, one for the original Base LUN, and one
each for the Thin Clones created.
Number of LUNs: 1
Pool: Capacity
Size: 15 GB
Thin: Checked
Click Next
3 From the Configure Access window, add WIN1 from the list of available
hosts by clicking the “+’ icon.
Click Ok.
Click Next
Username: \administrator
Password: emc2Local!
Click Ok
7 From the WIN1 system taskbar click the Computer Management icon.
Once formatted, open the Base LUN. (Note the Disk number of the drive)
8 Expand the Local Disk (C:) tree and open the Big_Files folder.
Select the first four 1 GB files, and copy the file to the Base LUN.
Note: You may see a window open by Microsoft asking if you want to
format the disk, select Cancel.
Check the Base LUN box and click the Edit icon.
10 From the Base LUN Properties window, select the Snapshots tab.
Click OK.
The snapshot is created. Note the time at which the snapshot was taken.
Also note the Auto-Delete and Attached columns. In order to create a
Thin Clone, these columns should display a status of No.
11 With the Base LUN checked, select Clone from the More Actions
dropdown.
The Populate Thin Clone window appears. You have an option of using an
existing snapshot of the Base LUN or creating a new version of the Base
LUN.
Take the default to create a Clone using the existing snapshot of the Base
LUN. (Snap1_Base_LUN4GB)
Name; TC1_Snap1_Base_LUN4GB
Click Next
Click the + icon, add host WIN1 and close the window.
From the Results page, verify the Thin Clone was created.
Highlight TC1_Snap1_Base_LUN4GB
Perform a Rescan Disks of the storage from Disk Management. Note the
disk numbers for the disks.
Copy the last two remaining files (500MB and 750MB) from Big_Files
folder to the open LUN.
Rescan the bus then bring the other 15 GB LUN Online. (Disk 2) and
open the LUN.
Did the two new files get written to the Base LUN? _________
Select the Snapshots tab. Use the + icon to create a new snapshot.
Name; Snap2_TC1_Base_LUN6GB
Verify the snapshot appears under Snapshots and close the window.
From the Populate Thin Clone page, verify the radio button for Clone
using an existing snapshot of LUN TC1_Snap1_Base_LUN4GB is
selected.
Name; TC2_Snap2_Base_LUN6GB
Click Next.
Verify the Thin Clone was created and close the window
Highlight TC2_Snap2_Base_LUN6GB
Perform a Rescan Disks of the storage from Disk Management. Note the
disk numbers for the disks. A fourth disk appears.
Bring the new 15 GB disk Online and open the LUN. (Disk 4)
Rescan the bus, and Online Disk 2 (The original Base LUN) and open it.
This verifies that changes made to the Clone do not affect the Base LUN.
20 You have taken two snapshots and created two Thin Clones from those
snapshots.
Step Action
1 In this lab section we are going to refresh the contents of the Base LUN
from a Thin Clone snapshot and verify the contents of the Base LUN.
Check the box for Base LUN and select Refresh from the More Actions
dropdown. (uncheck any other LUNs)
The window displays all the available snapshots you can select to refresh
the Base LUN. Read the line at the bottom about eligible snapshots.
Offline the original Base LUN. (Disk 2), then Online the Base LUN.
Open the LUN. It should display the six files since we refreshed the LUN
with the contents of TC2_Snap2_Base_LUN6GB.
5 In Unisphere; From the LUNs page, highlight the Base LUN, Select
Refresh from the More Actions dropdown.
Offline the original Base LUN. (Disk 2), then Online the Base LUN.
Open the LUN. The LUN should display the original 4 GB files since we
refreshed the Base LUN with the contents of Snap1_Base_LUN4GB.
You have refreshed the Base LUN from two different images.
7 The next few steps have you clean up the resources that were created for
the exercise.
To remove Host Access to the LUNs, navigate to the Storage > Block >
LUNs page.
Check the box for WIN1, Click the Trash can icon (Remove Access).
TC1_Snap1_Base_LUN4GB
TC2_Snap2_Base_LUN6GB
10 You have successfully created Thin Clones within a single the Base LUN
family and restored the Base LUN from a snapshot of a Thin Clone.
Step
From your Student Desktop system taskbar, launch Mozilla Firefox and establish
a Unisphere session to the UnityVSA-Source system at IP address
192.168.1.113. Open another tab from the + icon, and establish a Unisphere
session to the UnityVSA-Destination system at IP address 192.168.2.113.
2 The first replication communications channels are the Interfaces used for
replication on both systems. The Interfaces establish an IP connection between
the systems to carry the replicated data.
Note: The Interfaces you will create on both systems are on the same network
so a Gateway will not be required. If Interfaces are created on both systems are
on different networks, the Gateway configuration would be needed.
The User Name and Password fields will be populated with credentials which
are: admin/Password123!
Because Dell EMC UnityVSA only supports Asynchronous replication, the Mode
dropdown list is grayed out with Asynchronous selected. Note: On a physical
Unity system, the Mode dropdown list would also show Synchronous and Both.
5 Now access the UnityVSA-Destination and navigate to Protection & Mobility >
Replication. Select the Connections tab to view the new Connection. Highlight
the connection and click Verify and Update to verify the new connection from
the UnityVSA-Destination perspective. Click Yes to proceed with the verification
operation. The operation takes a moment to complete and will update the
connection. The Replication communications are now complete.
Step Action
1 From the UnityVSA-Source session, navigate to Storage > Block > LUNs.
Select the Replication tab and click the Configure Replication button.
From the Provide a Replication Mode and RPO window, Select Asynchronous
from the Replication Mode dropdown.
3 The next wizard section configures the destination storage resources for
creating the replicated LUN. The Name field defines the name the LUN will have
on the destination system. You will keep the populated name of: WIN1 LUN0
The Pool field defines the destination system storage pool the LUN will be
created from. You will keep the populated pool of FAST VP-1
Thin: Checked
The destination Tiering Policy can also be configured. You will keep the default
policy of Start High Then Auto-Tier
4 The wizard displays a Summary for the configuration of the replication session
as shown here.
The Results section displays the status of the creation operation. Verify the
Overall Results display 100% Completed.
The Properties include: Session Name, Mode, Local Role, Time of Last Sync,
and Replicate Scheduled Snapshots.
The replicated object on the two systems identifies which system allows IO to
the LUN, and what Replication operations can be done to the session.
Check the box for the WIN1 LUN0 Resource. Click the More Actions dropdown
list. Compare its active and grayed out replication operations to the ones
recorded in the previous step. Are they the same or different? ___
______________________
Click the View/Edit icon for the Session Name from the right of the session
name. Expand the window if needed to view the Edit icon.
The replication session is displayed. This will take a minute, use the refresh icon
until the name appears.
Click the More Actions dropdown list. Compare its active and grayed out
replication operations to the ones recorded previously from the UnityVSA-
Source system.
Why? __________
9 Navigate to Storage > Block > LUNs. The WIN1 LUN0 is displayed. It was
created on the destination system by the replication process.
Select the Host Access tab and you will see no host has been granted access
to the LUN. Host access will need to be configured to the LUN so its replicated
data will be accessible to a host should the source site become unavailable and
the replication session failed over.
12 From the WIN2 system taskbar, click the iSCSI Initiator icon to launch the
application.
Select the Discovery tab. Click the Discover Portal button. In the Discover
Target Portal window, in its IP address or DNS name field input: 192.168.3.101
Select the Targets tab. In the Discovered targets section the UnityVSA-
Destination IQN is displayed with an Inactive status. Select it and click the
Connect button to connect the initiator to the target.
In the Connect to Target window, check the Enable multi-path checkbox. Click
the Advanced button.
From the Advanced Settings window, in the Local adaptor dropdown list, select
Microsoft iSCSI Initiator. In the Initiator IP dropdown list, select 192.168.3.107.
From the Target portal IP dropdown list, select 192.168.3.101 /3260. Click OK to
configure the settings.
From the LUN properties page Host Access tab, click the + icon to add host
access to the LUN.
The Select Host Access window opens. From the More Actions dropdown list
select Add Host.
14 The Add a Host wizard opens. Input the following host configuration:
Name: WIN2
Operating System: Windows Server
Network Address: 192.168.2.11
A Summary window displays the information for the host being added. Click
Finish to initiate the Add Host operation.
15 In the Select Host Access window, check the WIN2 checkbox to select the host
and click OK.
The WIN2 host is now configured to access the replicated WIN1 LUN0.
Part 3: Create Remote Replication for a NAS Server and File Systems
Select: NAS_SMB
Click the Edit icon to open the NAS Server properties page.
Select the Replication tab and click the Configure Replication button.
3 The next wizard section configures the destination storage resources for
creating the replicated NAS Server and any of its associated file systems.
The Name field defines the name the NAS Server will have on the
destination system. You will keep the populated name of: NAS_SMB
The Pool field defines the destination system storage pool the storage
resource is created from. You will keep the populated pool of FAST VP-2
The NAS Server replication session details are displayed in the Replication
tab of the NAS_SMB Properties page.
4 From the Storage > File > File Systems tab, select the SMB_fs file
system and click the Edit icon to open its properties page.
Select the Replication tab. The session details are shown for the SMB_fs
file system. The system automatically replicates the existing file systems
that are associated with a NAS Server when the NAS Server is replicated.
In the Session Name field replace the existing name with: SMB_fs_rep
and click OK.
6 Locate the replication session for the DP_fs file system and select it. Then
click the Edit icon to open its details page.
7 Locate the session for the NAS_SMB NAS Server and select it. Click the
Edit icon to open its session details page.
Click the Edit icon for the Session Name. Replace its session name with:
NAS_SMB_rep and click OK.
In the Network Interfaces section, the interface for the NAS_SMB server is
shown. This interface configuration was replicated along with the NAS
Server from the UnityVSA-Source. However, the UnityVSA-Destination
system is connected to a different network. So the interface configuration of
the replicated NAS Server must be changed.
You can now enter a new interface configuration for the NAS Server.
In the Edit NAS Server Interface confirmation window, click Yes to apply
the change.
The interface is now modified for the network that is connected to the
UnityVSA-Destination system. If the NAS Server replication session is
failed over, it will be available on the correct network and be able to provide
data services to users.
Step Action
1 In this part of the lab you will perform replication operations on the
replicated LUN and access its data after the operations.
2 The WIN1 system should have access to the WIN1 LUN0 from the
previous lab exercises.
From the WIN1 system taskbar open File Explorer and select the WIN1
LUN0 (E:).
Open the New Text Document. Add the following line of text to the file:
This line was added from WIN1 before the Failover with sync was
performed.
3 Prior to performing the replication operation Failover with sync, you will
quiesce host IO to WIN1 LUN0 on the UnityVSA-Source system. This will
be done by using Server Manager to offline the disk.
Right-click the 5.00 GB disk and select Take Offline. Click the Yes button
to offline the disk.
The WIN1_LUN0 session State will now be Failed Over with Sync.
5 Access the existing RDC session to WIN1. In the open Server Manager
window, right-click the 5.00 GB disk and select Bring Online. Click the
Yes button to bring the disk online.
Why _______________
In Server Manager, navigate to File and Storage Services > Disks. In the
upper right corner from the Tasks dropdown, select Rescan Storage.
Right-click the 5.00 GB disk and select Bring Online.
7 From WIN2, launch File Explorer, open the New Text document.
Is the line of text added prior to the Failover with sync present in the file?
____
Add the following line of text to the file: This line was added from WIN2
when failed over to UnityVSA-Destination.
8 Next, you will perform the Resume operation on the replication session.
The resume operation keeps the read/write access to the LUN from the
UnityVSA-Destination system and restarts the replication from the
UnityVSA-Destination system to the UnityVSA-Source system.
When completed, the session is displayed with a normal state. (Auto Sync
Configured)
10 At this point the data states of the LUN on the UnityVSA-Destination and
the UnityVSA-Source are the same with the LUN on the UnityVSA-
Destination system being in the read/write state. The LUN on the
UnityVSA-Source is still unavailable for access.
To test this, open the existing RDC session to WIN1. From its open Server
Manager window, try to bring the LUN online again.
11 In the next few steps you will return the replication as it was prior to the
Failover with sync operation. But before doing that, the WIN2 host IO
should be queisced. You will do this using Server Manager to offline the
disk.
Open the existing RDC session to WIN2. From its open Server Manager
window, right-click the 5.00 GB disk and select Take Offline. Click Yes to
offline the disk.
12 You will now perform a Replication Failover operation to return the LUN to
read/write status on the UnityVSA-Source system.
Form the More Actions dropdown list, select the Failover operation.
The replication session will now be shown in the Failed Over state.
13 Open the existing RDC session to the WIN1 system. In the open Server
Manager window, if the disk is not already online, right click the 5.00 GB
disk and select Bring Online. Click the Yes button to online the disk.
Note: The disk may need to be placed offline and then online to be
visable.
From the WIN1 Desktop or system taskbar, open File Explorer and select
the WIN1 LUN0 disk. Open the New Text Document.
Is the line that was written by the WIN2 host during failover present? ___
Note you can use the Disk Manager from Computer Management to bring
the disk online.
14 After the Failover operation, the Replication session is paused and will
need to be restarted by performing a Resume operation.
The session is now shown in the normal state. (Auto Sync Configured)
Step Action
1 In this part of the lab you will perform replication operations on the
replicated NAS Server and its file systems, and then access the data after
the operations.
Username: hmarine\administrator
Password: emc2Admin!
Click Ok
2 Before performing replication operations, you will add some data to the
Top$ share on the SMB_fs file system served by the NAS_SMB NAS
Server.
From the WIN1 taskbar click the Run icon and in the Open field input:
\\NAS_SMB\Top$
A window to the share opens. Right-click in the share and select New >
Text Document. Open the file and add the following line to the file: This
line was added prior to the manual sync operation.
Click the Sync button to perform a manual Sync of the replication session.
Click Yes to perform the sync operation.
4 Return to the RDC session for WIN1. From the WIN1 Desktop or system
taskbar, click the Run icon and in the Open field input: \\NAS_SMB\Top$
A window to the share opens. Open the New Text Document and add the
following line to the file: This line was added prior to the failover
operation.
5 Now you will perform a failover operation for the NAS Server and its
associated file systems. The NAS Server will be failed over first, then the
file systems.
Select the NAS_SMB_rep session. From the More Actions dropdown list
select the Failover operation.
Review the information displayed in the Failover NAS Server and File
System Sessions window.
Verify that SMB_fs and DP_fs sessions are selected for Failover.
The sessions will be listed as Failed Over state with a yellow triangle.
6 Now you will access the data from the UnityVSA-Destination system.
From the WIN1 Desktop or system taskbar, click the Command Prompt
icon.
The command will flush the client DNS Resolver cache. This is used
because the WIN1 client had previously accessed the NAS_SMB NAS
Server on the UnityVSA-Source system where it has an IP address of
192.168.1.115. Therefore, that name to IP address resolution was held in
the client’s DNS cache. The NAS_SMB NAS Server on the UnityVSA-
Destination system is configured for the IP address of 192.168.2.115. The
client DNS cache therefore needs to be flushed in order for it to be able to
access the NAS_SMB NAS Server at its new IP address
7 Now you will access the Top$ share from the NAS_SMB NAS Server.
Is the line of text added prior to the manual sync operation present? ____
Is the line of text added prior to the failover operation present? ___
Why? _____________________________________________________
8 Add the following line to the file: This line was added during failover to
the UnityVSA-Destination system.
Navigate to Protection & Mobility > Replication > Sessions and refresh
the page.
Select the SMB_fs_rep session and from the More Actions dropdown list
select the Failback operation. Click the Yes button to failback the session.
Why? ___________________________________________________
10 Select the NAS_SMB_rep session and from the More Actions dropdown
list, select the Failback operation.
From the Failback NAS Server and File System Sessions window, verify
the associated file systems are selected for Failback.
Select Failback
11 Return to the RDC session to the WIN1 system. In the Command window
flush the DNS client cache by running the following command: ipconfig
/flushdns
From the taskbar click the Run icon and in the Open field input:
\\NAS_SMB\Top$ to access the Top$ share.
Is the line of text added during failover present in the file? _____________
Why? ____________________________________________________
Navigate to Storage > File > NAS Servers. Select the NAS_SMB NAS
Server and click the Edit icon to open its properties page.
Select the Network tab. Review the information in the Network Interfaces
section.
Select the Network tab review the information in the Network Interfaces
section.
14 In this step you will ping the two different IP addresses of the NAS_SMB
NAS Server.
Access the RDC session to the WIN1 system. In the command window
issue the following command: ping 192.168.1.115
The NAS Server network interface that displays Preferred = Yes is the
NAS Server that is the source of the replication session and therefore has
its interface up and available for access. The NAS Server network
interface that displays Preferred = No is the NAS Server that is the
destination of the replication session and should not be reachable for
access. Therefore its interface is down and not accessible.
Step Action
1 In this part of the lab you will take a snapshot of an existing LUN and
replicate the LUN along with the snapshot.
You will then restore the LUN to the original state using the replicated
snapshot.
2 WIN1 should have access to WIN1 LUN0 from the previous lab exercises.
From the WIN1 Desktop or system taskbar open File Explorer and select
the WIN1 LUN0 drive.
Add the following line of text to the file: This is the original data on the
LUN of which we will take a snapshot.
After restoring the LUN from a snapshot, this is what you should
see.
Click OK
Prior to performing the replication operation Failover with sync, you will
quiesce host IO to WIN1 LUN0 on the UnityVSA-Source system. This will
be done by using Server Manager to offline the disk.
The WIN1_LUN0_rep session State will now be Failed Over with Sync.
6 Open the RDC session to the WIN2 system. Login as local administrator.
7 From the WIN2 Desktop or taskbar open File Explorer and select the
WIN1 LUN0 disk. Open the New Text Document.
Is the line of text added prior to the Failover with sync present in the file?
__ ___
Enter some text: This file was written during a Failover operation to
the UnityVSA-Destination.
11 From the Restore window, read the message and click OK. This will
create a backup restore point.
12 Next, you will perform the Resume operation on the replication session.
The resume operation will keep the read/write access to the LUN from the
UnityVSA-Destination system and will restart the replication with the
direction being from the UnityVSA-Destination system to the UnityVSA-
Source system
Select the WIN1_LUN0 session and from the More Actions dropdown list
select Resume. The Resume Session window provides information about
the operation. Review the information and click the Yes button to resume
the replication session.
The session is now displayed with a normal state (Auto sync Configured)
With WIN1 LUN0_rep selected, from the More Actions dropdown list,
select the Sync operation.
14 In the next few steps you will return the replication as it was prior to the
Failover with sync operation. But before doing that, the WIN2 host IO
should be queisced. You will do this using Server Manager to offline the
disk.
From your Student Desktop system open the existing RDC session to
WIN2. From its open Server Manager window, right-click the 5.00 GB disk
and select Take Offline.
15 You will now perform a Replication Failover operation to return the LUN to
read/write status on the VSA-Source system.
Form the More Actions dropdown list, select the Failover operation.
The replication session will now be shown in the Failed Over state.
16 Open the existing RDC session to the WIN1 system. In the open Server
Manager window, right click the 5.00 GB disk and select Bring Online.
Click the Yes button to online the disk.
From the WIN1 Desktop or system taskbar open File Explorer and select
the WIN1 LUN0 disk. Open the New Text Document.
Has the LUN been restored with the original data? ___
17 After the Failover operation, the Replication session is paused and will
need to be restated by performing a Resume operation.
The session is now shown in the normal state. The source of the
replication is again on the VSA-Source system and the replication
destination is to the VSA-Destination system.
The snapshot was used to restore the original state of the source LUN.
1 In this part of the lab you will perform replication operations on the
replicated NAS Server, its file systems and snapshots.
Data will then be restored from a replicated snapshot of the source file
system.
Launch the RDC session to WIN1 and log in as the Domain administrator.
2 Before performing replication operations, you will add some data to the
DP_fs file system served by the NAS_SMB NAS Server.
From the WIN1 taskbar click the Run icon and in the Open field input:
\\NAS_SMB\DP_fs_share.
A window to the share opens. Right-click in the share and select New >
Text Document. Open the file and add the following line to the file:
This file should be seen after restoring a snapshot from the WIN2.
Check the box for DP_fs and select the Edit icon.
Name: Snap1_DP_fs.
Click OK.
6 Return to the RDC session to the WIN1 system. From the WIN1 Desktop
or system taskbar, click the Run icon.
Delete the two lines you created earlier, and add the following.
Click the Sync button to perform a manual Sync of the replication session.
Click Yes to perform the sync operation.
8 Now you will perform a failover operation for the NAS Server and its
associated file systems and snapshots.
Select the NAS_SMB_rep session. From the More Actions dropdown list
select the Failover operation.
Review the information displayed in the Failover NAS Server and File
System Sessions window. Verify that SMB_fs and DP_fs sessions are
selected for Failover.
Return to the RDC session to the WIN1 system. From the WIN1 Desktop
or system taskbar, click the Command Prompt icon.
The command will flush the client DNS Resolver cache. This is used
because the WIN1 client had previously accessed the NAS_SMB NAS
Server on the UnityVSA-Source system where it has an IP address of
192.168.1.115. Therefore the name to IP address resolution was held in
the client’s DNS cache. The NAS_SMB NAS Server on the UnityVSA-
Destination system is configured for the IP address of 192.168.2.115. The
client DNS cache therefore needs to be flushed in order for it to be able to
access the NAS_SMB NAS Server at its new IP address
10 Now you will access the DP_fs share from the NAS_SMB NAS Server.
Is the line of text you added after the manual sync operation present? ___
_________________________________________________
Is the two lines of text added prior to the sync operation present? ____
Why?_____________________________________________________
11 Add the following line to the file: This line was added during failover to
the UnityVSA-Destination system.
Navigate to Protection & Mobility > Replication > Sessions and refresh
the page.
14 Select the NAS_SMB_rep session and from the More Actions dropdown
list, select the Failback operation.
From the Failback NAS Server and File System Sessions window, verify
the associated file systems are selected for Failback.
Select Failback.
From the Desktop or taskbar click the Run icon and in the Open field
input: \\NAS_SMB\DP_fs_share to access the share.
Are the two lines of text added before the sync and failover operations
present in the file? ___________
Why? ____________________________________________________
Step Action
1 In this part of the lab you will create a Proxy NAS Server on the UnityVSA-
Destination system and access a file system snapshot replica.
Click Next
IP Address: 192.168.2.118
Gateway: 192.168.2.1
Click Next.
Password: emc2Admin!
Click Next.
Click Next.
Click Next.
Click Finish.
Verify that the SSH protocol is Enabled. If not, Enable SSH access by
select Enable SSH and clicking the blue Execute tab.
Username: service
Password: Password123!
Open the New Text Document if not present, create a New text document.
Write the; Keep this file for restoring from the NAS proxy server.
Save and Exit the window, leave the share window open.
Name: File_restore
Click OK.
Select Run from the Desktop and open the \\nas_smb\dp_fs_share if not
already open.
18 You have restored a file from a NAS proxy server to the production host.