Unity Configuration and Implementation - SRG

Welcome to Unity Implementation and Configuration.
Copyright ©2016 EMC Corporation. All Rights Reserved. Published in the USA. EMC believes the information in this publication is accurate as o f its publication date. The information is subject
to change without notice.
THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN
THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. The trademarks, logos, and service marks (collectively "Trademarks")
appearing in this publication are the property of EMC Corporation and other parties. Nothing contained in this publication sh ould be construed as granting any license or right to use any
Trademark without the prior written permission of the party that owns the Trademark.
EMC, EMC² AccessAnywhere Access Logix, AdvantEdge, AlphaStor, AppSync ApplicationXtender, ArchiveXtender, Atmos, Authentica, Authentic Problems, Automated Resource Manager,
AutoStart, AutoSwap, AVALONidm, Avamar, Bus-Tech, Captiva, Catalog Solution, C-Clip, Celerra, Celerra Replicator, Centera, CenterStage, CentraStar, EMC CertTracker. CIO Connect,
ClaimPack, ClaimsEditor, Claralert ,cLARiiON, ClientPak, CloudArray, Codebook Correlation Technology, Common Information Model, Compuset, Compute Anywhere, Configuration
Intelligence, Configuresoft, Connectrix, Constellation Computing, EMC ControlCenter, CopyCross, CopyPoint, CX, DataBridge , Data Protection Suite. Data Protection Advisor, DBClassify, DD
Boost, Dantz, DatabaseXtender, Data Domain, Direct Matrix Architecture, DiskXtender, DiskXtender 2000, DLS ECO, Document Sciences, Documentum, DR Anywhere, ECS, elnput, E-Lab,
Elastic Cloud Storage, EmailXaminer, EmailXtender , EMC Centera, EMC ControlCenter, EMC LifeLine, EMCTV, Enginuity, EPFM. eRoom, Event Explorer, FAST, FarPoint, FirstPass, FLARE,
FormWare, Geosynchrony, Global File Virtualization, Graphic Visualization, Greenplum, HighRoad, HomeBase, Illuminator , InfoArchive, InfoMover, Infoscape, Infra, InputAccel, InputAccel
Express, Invista, Ionix, ISIS,Kazeon, EMC LifeLine, Mainframe Appliance for Storage, Mainframe Data Library, Max Retriever, MCx, MediaStor , Metro, MetroPoint, MirrorView, Multi-Band
Deduplication,Navisphere, Netstorage, NetWorker, nLayers, EMC OnCourse, OnAlert, OpenScale, Petrocloud, PixTools, Powerlink, PowerPath, PowerSnap, ProSphere, ProtectEverywhere,
ProtectPoint, EMC Proven, EMC Proven Professional, QuickScan, RAPIDPath, EMC RecoverPoint, Rainfinity, RepliCare, RepliStor, ResourcePak, Retrospect, RSA, the RSA logo, SafeLine, SAN
Advisor, SAN Copy, SAN Manager, ScaleIO Smarts, EMC Snap, SnapImage, SnapSure, SnapView, SourceOne, SRDF, EMC Storage Administrator, StorageScope, SupportMate, SymmAPI,
SymmEnabler, Symmetrix, Symmetrix DMX, Symmetrix VMAX, TimeFinder, TwinStrata, UltraFlex, UltraPoint, UltraScale, Unisphere, Universal Data Consistency, Vblock, Velocity, Viewlets, ViPR,
Virtual Matrix, Virtual Matrix Architecture, Virtual Provisioning, Virtualize Everything, Compromise Nothing, Virtuent, VMAX, VMAXe, VNX, VNXe, Voyence, VPLEX, VSAM-Assist, VSAM I/O
PLUS, VSET, VSPEX, Watch4net, WebXtender, xPression, xPresso, Xtrem, XtremCache, XtremSF, XtremSW, XtremIO, YottaYotta, Zero-Friction Enterprise Storage.
Copyright 2016 EMC Corporation. All rights reserved. Unity Configuration and Implementation 1
This course covers the configuration and implementation of the Unity storage platform
using the next generation GUI and CLI interfaces.
This course is segmented into four distinct topics that describe the tasks performed to
deploy a physical or virtual Unity system. The first topic focuses on the initialization and
Initial Setup of a UnityVSA system. The second topic provides a better understanding of
how to provision block and file storage for hosts. On the third topic we will demonstrate
how to enable and configure special Unity storage resource features such as FAST VP and
FAST Cache. And in the last module, the course will describe the configuration of native
protection features for Unity data storage.
This module focuses on the initialization of the virtual deployment of a Unity system using
installation tools and utilities, and its initial setup via Unisphere wizard.
If a UnityVSA system is deployed on a dynamic network that includes a DHCP server and a
DNS server, an IP address can be assigned automatically to the management interface.
However, if you would rather manually assign a static IP address to the management port
there are four methods that follow.
A static IP address can be assigned to the Management interface of the UnityVSA when the
OVA package is deployed using the OVF Template wizard in vSphere. Also, from vSphere
client interface it is possible to run the svc_initial_config command from the Console tab to
initialize the management port.
Alternatively, the Unity Connection Utility or the InitCLI applications can be run from a
Windows host to discover and configure the network settings for the management interface.
When deploying the Virtual Unity system OVA file in vSphere, it is possible to configure the
IPv4 and/or IPv6 address for the management interface from the properties page of the
Deploy OVF Template Wizard from the vSphere client. If no configuration is done in this
page, the virtual system will try to get a dynamic IP address from a DHCP server when it is
powered on. If the network includes a DHCP server and a DNS server, then an IP address
can be assigned automatically to the management interface.
From the vSphere Web Client, the same configuration is done in the Customize template
page.
The svc_initial_config command is used to setup initial system configuration or change an
already set IPv4 and IPv6 management address. The command configures the system with
a given friendly name and the network parameters for the management interface.
From the vSphere client, the implementer must open the Console for the deployed virtual
Unity system and login with the service account (default credentials are service/service).
Then using the syntax shown in the slide run the svc_initial_config command to assign an
IP address to the management interface.
An example of the command output is displayed here.
Alternatively the svc_diag command can be run to retrieve high-level information about the
“basic” system state of the UnityVSA. This information will include the virtual Unity system
serial number. The system serial number will be used to identify it in the list of discovered
systems when running the Unity Connection Utility.
An example of the command output is displayed here.
The Configuration Worksheet found in Appendix A of the Unity Series Installation Guide
contains the Connection Utility section with a table of information to be filled out prior to
initializing the system. Record the system serial number, along with a friendly name to
identify the system in the network and the management address information.
The Unity Connection Utility software is available for download from the EMC Online
Product Support page. It must be installed on a Windows host in the same subnet as the
UnityVSA. There is no need to install or update the Java version since Connection Utility has
the required 32 bit JAVA Platform Standard Edition 1.8 embedded into it.
When executing the utility the Auto-discover method must be selected from the Welcome
page. The Discover engine will search the network for unconfigured systems and list them.
The UnityVSA system can be identified using its serial number and then selected to be
configured.
In the Configure Network Information page select the option to use a static IPv4 and/or
IPv6 address. Then enter a friendly name and assign the static network address for the
management interface.
Review the information and then click Configure to apply the settings to the UnityVSA
management interface. The Deploy page will display the status of the configuration process,
which can take up to 10 minutes. Once the process is done a blue check mark is displayed
and the Finish and Start Unisphere buttons are enabled. Click Finish to close the wizard.
The InitCLI.exe tool is available for download from the EMC Online Product Support page.
The tool must be run from a Windows host in the same subnet as the UnityVSA.
The discover parameter will search the network for available systems to be configured and
will list the information about the system including its serial number (ID) shown in the first
box . The output qualifier specified the output format as NVP (Name Value Pair) or CSV
(Comma Separated Value).
The discovered UnityVSA system can then be configured by using the configure parameter
and specifying the serial number of the system, and the IP address, subnet mask, gateway
and a friendly name.
This video demo shows how the UnityVSA can be initialized by running the svc_initial_config
command from the vSphere Console to the SPA and by running the Connection Utility from
a Windows host.
After initializing the UnityVSA system, the user can open an internet browser session to the
system management port and log into Unisphere with the default credentials
(admin/Password123#) to configure the system. Unisphere will launch the Initial
Configuration wizard to walk the user through the initial setup of Unisphere and prepare
the system for use. After the initial setup is concluded the wizard can be launched at any
time from the settings window.
The wizard sequence is displayed here and will be demonstrated on a video.
The first time the wizard is launched the Copyright page will display the End User License
Agreement (EULA) and will require that the user check the radio button to accept it in order
to continue to the next step. The next step requires the user to change the admin and
service user passwords from their default values (service password can be set to have the
same password as the admin user). The Unisphere licenses page allows the user to obtain
the Unisphere license file online and upload to the system.
The next pages allow the configuration of DNS and system time synchronization support. A
pool can be also configured for provisioning file or block storage. This pool is also a
requirement for creating a NAS server (optional). Other optional settings involve configuring
alert notifications via emails or SNMP traps, and iSCSI interfaces for block storage.
After running the Initial Configuration wizard, the management of licenses for the available
features can be done from the Software and Licenses section of the Settings configuration
window in Unisphere. A product license can be selected from the list to have its description
displayed. To unlock features, license keys must be installed.
For the virtual systems, the license keys are based on the system’s UUID (Universally
Unique Identifier). These keys which are included in the License (.lic) files can be obtained
through the Get License Online link in the window. The user must provide the virtual
system UUID and the license authorization code (LAC) ID to download the license file
locally.
The license file must then be transferred to a computer with access to the virtual Unity
system. By clicking on the Install License link, the user can upload the license file from
the local machine to the storage system after accepting the license agreement.
This video shows the Initial setup of the UnityVSA with the Initial Configuration wizard in
Unisphere when accessing the system for the first time.
This module covered how to initialize a virtual version of the Unity platform using
installation tools and utilities. This module also demonstrated how to perform the initial
configuration of the UnityVSA using the next generation user interface.
This module focuses on the navigation of the new Unisphere user interface. The module
also describes how to customize the dashboard to display different views for system health
status monitoring and system performance monitoring charts. Provisioning of block and file
storage to hosts are discussed in the module too.
The next-generation Unisphere graphical user interface is built on HTML5 technology with
support on a wide range of browsers, such as Google Chrome v33 or later, Internet Explorer
v10 or later, Mozilla Firefox v28 or later and Apple Safari v6 or later. The interface has a
more contemporary look and feel with a navigation pane, a main page, sub-menus, and a
top menu.
The navigation pane on the left has the Unisphere options for provisioning storage, provide
host access, protect the data and monitor the system operation.
The main page is where the navigation pane selection is displayed - it could be information
retrieved from the system, or configuration options for storage provisioning, host access,
and data protection. In this example the page shows the Dashboard content.
A sub-menu with different tabs (links) on the top of the main page provides additional
options for the navigation pane selection.
The top menu on the right-corner has links for the system alarms, job notifications, help
menu, and the configuration of Unisphere preferences and global settings.
The Unisphere Main Dashboard provides a quick view of the storage system status including
the health information. A user can create its own Customized dashboard and save it. The
customized dashboards can be modified and deleted.
View blocks can be added to a dashboard. These view blocks can be used to view a
summary of system storage usage, monitor system alerts, view health of storage and
system resources, and provide graphs of system performance at a high-level.
To add view blocks to the selected Dashboard the user must open the sub-menu on the top,
select the desired block and click the Add View Block button.
Under the System option, select the Performance, then select the Dashboard for the
system that will include the performance charts. The time range for all the charts displayed
in the performance dashboard is configured using the Custom link on the top of the main
page. Select the start and end dates and times of the values displayed. Then select Update
to get the latest data.
To include additional performance metric charts click on the add Charts button, then select
the resource type from the list of performance charts. From the selected performance chart,
choose the available metrics for the resource type to be displayed. Then select Generate
Charts.
This video demo shows the next-generation Unisphere user interface navigation and
dashboard information.
Storage pools must be created prior to provisioning block or file storage to a host. It is
possible to create custom pools by selecting the quantity, type, and RAID configuration for
the disks in the pool.
In Unisphere, select Pools under the Storage section on the navigation pane. Click on the
“add sign” link in the Pools page to launch the Create Pool wizard. In the wizard window,
enter the pool name, and optionally the pool description. Then click Next.
The wizard will display the available storage tiers. The user can select the tier and change
the RAID configuration for the selected tier.
The user can then select the amount of disks from the selected tier to add to the pool.
FAST Cache can also be enabled in the pool.
The allocation of storage resources to a SAN host involves the creation of the host
configuration in Unisphere and the association of the storage resource with the host profile.
Before a SAN host can access storage, a Host configuration must be defined for it based on
the protocol used for connectivity. For hosts that will connect to the storage resource using
the Fibre Channel protocol the initiator World Wide Name (WWN) of the host HBAs must be
entered. For iSCSI storage hosts, the iSCSI Qualified Name (IQN) must be provided, as
well as the CHAP secret if used to authenticate iSCSI sessions.
Once the storage resource (LUN, Consistency Group or VMFS datastore) is created it can
then be associated with the SAN host, and the level of access set.
To create a Host configuration for the SAN host that will connect to a LUN or Consistency
Group using the Fibre Channel or iSCSI protocols the procedure described here must be
executed. From Unisphere select the Hosts option from the Access section.
On the Hosts page click on the + link and select Hosts.
On the Add Host wizard window select the name for the host profile and optionally provide a
description for the host. Then select the host operating system and leave the network
address field empty.
On the Select iSCSI Initiators page select the iSCSI initiators the host will use from the list
of auto-discovered initiators, or click on the Create Initiator button. On the Create iSCSI
Initiator window enter the SAN host IQN and the CHAP credentials then click Create.
On the Select Fibre Channel Initiators page select an existing host FC initiator if already
discovered, or click on the Create Initiator button. On the Create Fibre Channel
Initiator window enter the SAN host HBA WWN and click Create.
On the Summary page review the Host configuration then click the Finish button to accept
the changed configuration.
The initiators will be registered and the host added to the list of hosts.
To create LUNs select the Block page under the Storage Section in Unisphere. The LUNs page
will be displayed with a list of existing LUNs with its size and percentage of allocated capacity.
You can then launch the Create a LUN wizard by clicking on the “ add sign” link.
Then follow the wizard steps:
• Provide the name and description for the LUN
• Select the storage pool to use and define the LUN size.
• Provide access to the SAN host using the host configuration that was previously
created (with a defined connectivity protocol).
• Define the access level of the SAN host to the LUN.
• Optionally configure local and remote protection for the LUN, tiering policy and Host
I/O limits.
• Review the LUN to be created on the Summary page then click Finish
The results of the process will be displayed.
To create Consistency Groups select the Block page under the Storage Section in Unisphere.
Then select the Consistency Groups page from the top menu. The Consistency Groups page will
be displayed with a list of existing Consistency Groups with its size and percentage of allocated
capacity. You can then launch the Create a Consistency Group wizard by clicking on the “add
sign” link.
• Provide the name and description for the Consistency Group
• On the Populate Consistency Group page click on the “add sign” link to open the Configure
LUNs window.
• Define the number of LUNs, and name. The name of the LUNs will be the combination
of the name and a sequenced number.
• Select the storage pool to use and the size of the LUNs.
• If the selected pool is tiered then it is possible to choose the tiering policy.
• Host I/O limits can also be defined before saving the configuration.
• Provide access to the SAN host using the host configuration that was previously
• Define the access level of the SAN host to the LUN
• Optionally configure local and remote protection.
• Review the Consistency Group to be created on the Summary page then click Finish
This video demo shows how to provision block storage to hosts using the next-generation
Unisphere user interface.
The allocation of storage resources (file system or NFS datastore) to a NAS client involves
the creation of the host configuration in Unisphere, the creation of a NAS server enabling
the sharing protocols and the association of the storage resource with the host profile.
Before a NAS client can access storage, a Host configuration must be defined for it by
providing its network name and IP address.
A NAS server must be created using at least one data interface created from an available SP
Ethernet port. Protocols must be configured prior to sharing the file storage resource.
Then a file storage resource (File System) can be created using the newly created NAS
server, shared using the configured protocols and associated with a host profile with a
defined level of access.
To create a NAS Server to enable file-level access to Unity storage volumes, select the File
page under the Storage section in Unisphere.
Then select the NAS Servers page from the top menu. The NAS Servers page will be
displayed with a list of existing NAS Servers, its associated SP and the replication type
configured.
You can then launch the Create a NAS Server wizard by clicking on the “add sign” link.
The NAS server is created with the following parameters:

• NAS Server name.
• Associated storage pool
• Associated Storage Processor and its network interface
• Ethernet port for NAS Server traffic: IP address, subnet mask and gateway
• VLAN ID for traffic transferred through the NAS Server.
• Configuration of the sharing protocol: SMB, NFS or multiprotocol
• Configuration of the Unix Directory Services and DNS services
• Optionally enable and configure replication to a destination
• Review the NAS Server to be created on the Summary page then click Finish
To enable the Anitivirus Service on a NAS Server, select the File page under the Storage
section in Unisphere. Then select the NAS Servers page from the top menu.
From the list of existing NAS Servers select the one that was previously created, and click
on the “pencil” icon to edit its properties.
On the NAS Server Properties window open the Security. Check the box to enable the
service, then download the existing virus checker configuration file (viruschecker.conf).
Open the file with a text editor and add the list of IP addresses of virus checker servers to
connect to.
Then upload the modified configuration file to the system.
To create a storage resource that will be connected by the host via the NFS (Linux/UNIX) or
SMB/CIFS (Windows) protocols, you must create a file system with a share.
From Unisphere, select the File option under the Storage section. The File Systems page
shows a list of existing file systems with its size, allocated capacity, and the NAS Server and
pools they are associated with.
Click on the “add” link to launch the Create a File System wizard.
The steps of the wizard include:
• Configure the Protocols the file system will support
• Select the NAS Server to associate with the file system
• Enter a name and optional description for the file system
• Select the storage pool to create from and the size of the file system
• Optionally select a tiering policy
• Provide a name for the share
• For Windows Shares it is possible to configure additional SMB settings
• For Linux/UNIX Shares it is possible to associate it with a host profile and set the
access level: read-only, read/write, and read/write, allow root.
• Optionally configure local and remote data protection
• Review the File system to be created then click Finish
This video demo shows how to provision file storage to hosts using the next-generation
Unisphere user interface.
The allocation of block or file storage resources to an ESXi involves the creation of the host
configuration in Unisphere, and the association of the provisioned storage resource with the
host profile.
Before an ESXi host can access the Unity provisioned storage, a Host configuration must be
defined for it by providing its network name and IP address.
Then a storage resource (NFS or VMFS datastore) can be created, and associated with the
host profile with a defined level of access.
This procedure describes how to create a Host configuration for a ESXi host that will
connect to an NFS, VMFS, or VVol datastore.
From Unisphere select the VMware option from the Access section.
On the vCenters page click on the + link.
On the Add vCenters wizard window enter the IP address of the vCenter Server and its
login credentials. Then click the Find button to discover the ESXi hosts managed by the
vCenter Server.
Select the ESXi host that will be associated with the host configuration profile.
To create a VMware datastore select the VMware option under the Storage Section in
Unisphere. The Datastores page will be displayed with a list of existing datastores with its
size and percentage of allocated capacity. You can then launch the Create VMware
Datastore wizard by clicking on the “ add sign” link.
• Select the type of datastore: File (NFS), Block (VMFS), VVol (File) or VVol (Block)
• Provide the name and description for the LUN
• Select the storage pool to use.
• Define the tiering policy and the datastore size.
• Provide access to the ESXi host using the host configuration that was previously
• Define the access level of the ESXi host to the datastore.
• Optionally configure local and remote protection for the datastore.
• Review the datastore to be created on the Summary page then click Finish
This video demo shows how to provision VMware datastores to ESXi hosts using the next-
generation Unisphere user interface.
This module covered the navigation of the new Unisphere user interface. The module also
described how to customize the dashboard to display different views for system health
status monitoring and system performance monitoring charts. Provisioning of block and file
storage to hosts was discussed in the module too.
This module focuses on the configuration of special Unity Operating Environment features
using the Unisphere GUI interface.
FAST Cache can be created on licensed physical Unity systems with available SAS Flash 2
drives. In Unisphere, the FAST Cache can be created when running the Initial Configuration
wizard, or when accessing the system settings page.
In the Settings page, select the FAST Cache option under the Storage Configuration
section. Then select the FAST Cache disks from available SAS Flash drives and choose
whether to enable FAST Cache for existing pools. The process will create RAID Groups, add
storage to FAST Cache and enable it for existing storage pools (if the checkbox was
selected).
After the FAST Cache is created it can be expanded by adding more SAS Flash 2 disks to it,
have disks removed from it, or it can be deleted.
For both physical or virtual deployments of Unity systems, if the FAST VP license is installed
tiered storage pools can be created to optimize disk utilization. These storage pools will
consist of multiple tiers: extreme performance, performance and/or capacity. Data
relocation within these multi-tier pools are based on relative activity level.
FAST VP operation can be configured and adjusted at the system, storage pool, LUN and file
system levels.
To change system-level data relocation configuration on the Unity system, click on the
Settings icon on the top of the page, then under the Storage Configuration section select
the FAST VP option. The FAST VP settings page displays whether scheduled relocations
are enabled for the system.
The Relocation Schedule defines the timeframe during which FAST VP relocations are
allowed to occur. Users can select which days, and the timeframe during those days, for
relocations to occur. Relocations will continue to cycle as long as the Relocation Window is
open.
The user can manually pause (hit the pause button) and resume (hit the resume button)
the scheduled data relocations on the system, change the data relocation rate, disable and
re-enable scheduled data relocations, and modify the relocation window.
From Unisphere select Pools under the Storage section.
Select the pool and click on the pencil icon to edit its properties. Then navigate to the FAST
VP tab. The page will display the information of the tiers that are part of the pool including
the amount of data to be moved up and down between the tiers.
From the same page it is also possible to take the pool out of the data relocation schedule
and manually start the data relocation.
From Unisphere select Block or File under the Storage section.
Select the storage resource (LUN, Consistency Group or File System) and click on the pencil
icon to edit its properties. Then navigate to the FAST VP tab. The page will display the tier
distribution of Block and File Storage resources. From this page it is then possible to change
the selected tiering policy for data relocation.
This video demo shows how to enable FAST VP and FAST Cache in Unisphere.
Configuring Virtual Volumes (VVols) involve some tasks that are performed on the storage
system and some that are done by the vSphere administrator. First the storage
administrator must create the storage pools that will be associated with VMware Capability
profiles. Capability Profile definitions include thin or thick space efficiency, user defined set
of strings, storage properties (drive type and RAID level), and a service level to identify it.
Then VVol datastores can be created based on the selected storage pool and capability
profile. The Protocol Endpoints are automatically created when a host is granted access to a
VVol datastore.
In vSphere the administrator must register the storage array which is providing the VVol
datastores as a storage provider, and create storage policies that will allow provision of
virtual machines. Once the virtual machines are created using the storage policies, the
user will be able to see the underlying volumes created by vSphere presented on the Virtual
Volumes page of the VMware datastores section in Unisphere.
This video demo shows how virtual volumes (VVols) are provisioned in Unisphere.
Quality of Service (QoS) can be set on physical or virtual deployments of Unity systems and
is supported on LUNs, snapshots, and VMFS Datastores.
QoS is either enabled or disabled in a Unity system. All host I/O limits are active if the
feature is active. Host I/O limits are active as soon as policies are created and assigned to
the storage resources.
From the Unisphere GUI, open the Settings window and select Performance under the
Management section. Then click on the Resume button to enable the use of Host I/O limits
by the system.
The host I/O limit policies are based on maximum IOPS (IOs per second) and maximum
bandwidth in KBPS (kilobytes per second) or MBPS (megabytes per second), or both.
To create a host I/O limit policy in Unisphere select Performance under the system section.
Then click on the “add sign” link. On the Create Host I/O Limit wizard window provide the
name for the policy and optional description then enter the maximum threshold for the
policy: maximum IOPS and/or maximum bandwidth. Then check the box if the I/O limit
policy is to be shared. If the box is unchecked, each resource will be assigned the specified
limits. If the box is checked then the resources the policy is assigned to are treated as a
group, and all the resources share the limits applied.
Then finally assign the policy to the desired storage resources.
Host I/O limit policies can also be created via command line interface using the uemcli
syntax shown here.
This video demo shows how to set Host I/O limits to provisioned storage and monitor
Quality of Service (QOS) performance in Unisphere.
EMC recommends that quotas are configured before the Unity system becomes active in a
production environment. Quotas can be configured after a file system is created.
Default quota settings can be configured for an environment where the same set of limits
are applied to many users. The following parameters can be configured at the Manage
Quota Settings window: Quota policy, and default user quota limits: soft limit, hard limit
and grace period.
Quotas can also be created for individual users, and quota trees configured for each
directory or subdirectory, with default limits defined for users at the quota tree level.
To manage the default quota settings, you must select and edit the properties of a file
system. From Unisphere select File under the Storage section. Then select the file system
and click on the pencil icon to edit its properties.
From the File System properties page select the Quota tab. Then click on the Manage
Quota Settings link on the top right-corner of the window.
The default quota policy is File Size .
Check the box to enable the enforcement of user quotas at the file system level.
Then change the default soft and hard limits for those quotas. Then specify the grace period
for which users of the file system can remain over the soft limit before it becomes the hard
limit. Click OK when done to apply the changes.
To define explicit quotas for individual users at the file system level, from Unisphere select
File under the Storage section, then select the desired file system and click on the pencil
icon to edit its properties. On the User Quota Report page click on the “add” sign to create
a user quota.
Then from the User name section of the Create a User Quota wizard click on the “add”
sign to configure a user. Select the user type (host type) and enter the domain/name, Unix
name or User ID. Click on Add user. The user is displayed in the list of users – select it and
click on next to advance to the next screen. Enter the soft and hard limits and click next.
Review the summary of changes and click the finish button. The progress and conclusion of
the operation will be displayed on the Results page. Close it once the operation is done.
Observe that that new user quota is displayed on the User Quota Report page.
Quota trees can be created for each directory or subdirectory that will be created in the file
system. To create a quota tree select the File system under the File Systems option of the
File page from the Storage section in Unisphere. Then click on the “pencil” icon to edit the
file system properties. Navigate to the Quota tab, and select the Quota Tree option.
Then click on the “add symbol” icon to launch the Create Quota Tree wizard.
Define the path (relative to the file system root) of the directory you want to apply the
quota.
Then assign the soft and hard limits for the quota policy. Review the configuration on the
Summary page and click Finish to apply the settings to the quota. The next page will show
the results of the operation. Click Close to terminate the wizard.
For each quota tree it is necessary to define default limits and explicit quotas for users at
the quota tree level.
Select the quota tree and click on the “pencil” to edit its properties.
On the Quota Tree Properties window, click on the Enforce User Quotas checkbox, and
define the default soft and hard limits. Then click on the “add symbol” to launch the
Create User Quota wizard. Click on the “add symbol” to open the Configure User window.
Enter the user type (host type), the domain/user name (in case of Windows users), Unix
Name or the User ID. Then click on the Add User button. Click Next to advance the wizard.
Enter the soft and hard limits for the user. Review the configuration and click Finish.
This video demo shows how to set default quotas, user quotas and tree quotas for a file
system.
This module covered the configuration of special Unity Operating Environment features
using the Unisphere GUI interface.
This module focuses on the configuration of data protection solutions for Unity storage
systems using the Unisphere user interface.
Data at Rest Encryption is a licensed feature available only for physical deployments of
Unity systems. The encryption state is set the first time a license is applied.
Once set, the encryption state cannot be changed without completely reinitializing the array
(which removes all data and configuration).
From the Unisphere GUI, open the Settings window and select Encryption under the
Management section. From this page it is possible to verify the status of the Controller
Based Encryption, perform the manual off-array backup of the keystore file, and download
audit logs and checksum. Keystore file backup is very important to ensure the integrity of
the drive’s data encryption keys.
This video demo shows how to enable the DARE support in a Unity system and how to
backup the keytore file.
Unity supports Unified Snapshots which provide point-in-time copies of data for both block
and file resources. The supported storage resources are: LUNs and Consistency Groups, File
Systems, and VMFS or NFS Datastores. VVol datastores are not supported.
Snapshots can be enabled for automatic creation when creating a new LUN, Consistency
Group, File System or supported VMware Datastore. Snapshots can be also manually
created from the properties window of a supported storage resource.
Auto-delete and expiration can be configured so that snapshots are automatically deleted at
a specified time or based on user defined storage consumption thresholds.
During the creation of one of the supported storage resources, it is possible to enable the
automatic creation of Snapshots and define a frequency and retention.
There are 3 options of system defined retention policies which creates the Snapshots
everyday at 8:00 AM: Default Protection (2 days retention), Protection with Shorter
Retention (1 day retention) and Protection with Longer Retention (7 days retention).
Optionally the user can create customized Snapshot schedules defining the frequency (days
or hours) and the retention period. This can be done from the same page of the wizard, or
by selecting the Snapshot Schedule option under the Data Protection section in Unisphere.
To manually create the Snapshots for a supported storage resource, the user must navigate
to the storage section in Unisphere that corresponds to the storage resource. Then from the
relevant storage resource page (LUNs, Consistency Groups, File Systems, Datastores)
select the storage resource and click on the pencil to edit its properties.
On the properties window select the Snapshots tab. From the Snapshots tab click on the
“add symbol” to create the Snapshot.
The Create a Snapshot window is displayed with a system-generated name for the
Snapshot based on the date and time of its creation. The user can change this name with a
more friendly one if desired.
Then select a retention policy for the Snapshot.
When creating Snapshots for File Systems, and NFS datastores it is also possible to define
the Snapshot can be shared as read/write or read-only (as a hidden file system).
Click OK to save the changes.
The newly created Snapshot will be shown on the list and can be edited/modified.
For more details and a video demo explaining the configuration and management of Unified
Snapshots on Unity systems please refer to the Unity Snapshots eLearning.
Remote Replication sessions are created on storage resources for Block, File and VMware
datastores. And all are done in a similar manner.
For Block, the replication is created on a LUN or a group of LUNs in the case of a
Consistency Group. For File, the replication is configured on a NAS server and file systems.
For VMware the storage resource is either going to be a LUN-based VMFS datastore (Block)
or a file system-based NFS datastore (File).
A wizard to configure replication is also available when running the wizard that creates each
one of the mentioned storage resources. Each wizard provides an option to automatically
create the replication on the resource. Each resource replication creation is nearly identical
to the other resources.
For resources already created, replications can be created manually from their Properties
page. As with the wizard, the replication creation from the resource Properties page is
nearly identical to the other resources.
Before a remote replication session can be created, the interfaces that will be used by the
two systems must be configured: IP-based connections for asynchronous replications and
Fibre Channel connectivity between systems SPs for synchronous replications.
Then a replication connection must be created to establish the connection between the
replication interfaces, with the credentials for both systems, and the replication mode.
To create Replication interfaces for an Asynchronous Replication session, from Unisphere
select Replication under the Data Protection section.
Then from the Replication management page select Interfaces from the top menu.
With the Interfaces section selected the + icon is used to create new Replication
Interfaces. On the creation screen, an available Ethernet Port from the system must be
selected. An IP address and subnet mask must be provided for both SPs. Gateway
addressing is optional and a VLAN ID configuration is also provided if needed.
The Replication Interfaces must be created on both the source and destination systems, so
this step must be repeated on the peer system.
After the Replication Interfaces are created, a Replication Connection is created between
the two systems. This only needs to be created on one of the replicating systems. The
requirements of the connection include the remote system management IP address and its
management credentials. The local system management password is also required. Finally
a replication mode must be selected from the drop-down. Choices are Asynchronous,
Synchronous or Both. For Asynchronous replication the Mode must be set Asynchronous or
Both. If Both is selected, Asynchronous and Synchronous sessions can be configured
between the two systems.
After the Replication Connection between the systems has been created, the connection
can be verified from the peer system using the Verify and Update option. This option can
also be used to update Replication Connections if anything has been modified with the
connection or the interfaces. The updated Connection status will be displayed.
Asynchronous Replication sessions can be created as part of the wizard that creates any
Unity storage resource. Replication sessions can also be created from the storage resource
Properties page; a VMware NFS Datastore, a NAS Server or a file system.
In this example from the properties window of a NAS Server, the “Configure Replication”
button is presented to create a replication session. It starts a wizard with a number of steps
to configure the replication session.
The Replication Settings step requires the “Replication Mode”, “RPO”, and “Replicate To”
settings for the session. The mode must be set to Asynchronous to create an Asynchronous
replication session.
The next step defines what resources on the destination system the replicated item will
use. The Name, Pool and Storage Processor settings are required.
In the example NAS Server replication shown, the NAS Server has an associated file system
and a separate replication session will be created for it. The table details the destination
resources that will be used for the file system. It can be selected and edited to further
define its destination resources.
The wizard presents a Summary screen for the configured replication.
In the example, sessions for the NAS Server and its associated file system will be created.
After the Finish button is clicked the Results page displays the progress of the destination
resource creation and the session is created.
The replication Interfaces for Synchronous replication are created in a similar fashion as
seen with Asynchronous replication. The requirement for Synchronous replication is that the
Interfaces are created on the Sync Replication Management Port of each SP. This is a virtual
device that uses the same physical network connection as the SP Management port. The
interfaces are configured on the same network as the SP Management but can use a
different network if VLANs are used.
The Replication Interfaces need to be configured on both the source and destination
systems.
After the Replication Interfaces are created, a Replication Connection is created between
the two systems. This only needs to be created on one of the replicating systems. The
requirements of the connection include the remote system management IP address and its
management credentials. The local system management password is also required. Finally
a replication mode must be selected from the drop-down. Choices are Asynchronous,
Synchronous or Both. For Synchronous replication the Mode must be set Synchronous or
Both. If Both is selected, Synchronous and Asynchronous sessions can be configured
between the two systems.
After the Replication Connection between systems has been created, the connection can be
verified from the peer system using the Verify and Update option. This option can also be
used to update Replication Connections if anything has been modified with the connection
or the interfaces. The updated Connection status will be displayed.
Synchronous Replication sessions can be created as part of the wizard that creates the
storage resource: a Block LUN, a Consistency Group or a VMware VMFS Datastore.
Synchronous Replication sessions can also be created from the storage resource Properties
page.
From the LUN Properties page example, the “Configure Replication” button is presented to
create a replication session. It starts a wizard with a number of steps to configure the
replication session. The Replication Settings step requires the “Replication Mode” and
“Replicate To” settings for the session. The Mode must be set to Synchronous to create a
Synchronous replication session.
The next step defines what resources on the destination system the replicated item will
use. The Name and Pool settings are required. A Tiering Policy drop-down is also available.
The wizard presents a Summary screen for the configured replication.
In the example, the session settings for the replication and destination are displayed.
After the Finish button is clicked the Results page displays the progress of the destination
resource creation and the session is created.
When the Create a Session wizard is completed the created sessions can be viewed from
the Replications page by selecting the Sessions section. From this same page it is possible
to manage the sessions: pause, resume, sync, failover, failover with sync and failback.
For more details and a video demo explaining the configuration and management of
Asynchronous and Synchronous Replication of Unity systems please refer to the Unity
Replication eLearning.
This module covered the configuration of data protection solutions for Unity storage
systems using the Unisphere user interface.
This course covered the configuration and implementation of the Unity storage platform
using the next generation GUI interface.
This concludes the training.

Unity Configuration and Implementation - SRG

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Unity Configuration and Implementation - SRG

Încărcat de

Drepturi de autor:

Formate disponibile

Welcome to Unity Implementation and Configuration.

An example of the command output is displayed here.

An example of the command output is displayed here.

The wizard sequence is displayed here and will be demonstrated on a video.

On the Hosts page click on the + link and select Hosts.

The results of the process will be displayed.

The results of the process will be displayed.

The NAS server is created with the following parameters:

The results of the process will be displayed.

Then upload the modified configuration file to the system.

The results of the process will be displayed.

On the vCenters page click on the + link.

The results of the process will be displayed.

Then finally assign the policy to the desired storage resources.

The default quota policy is File Size .

Then select a retention policy for the Snapshot.

Click OK to save the changes.

This concludes the training.

S-ar putea să vă placă și