ViPR 2.2 - What are the ViPR File Provisioning and Protection Facilities?

Table of Contents

Introduction

ViPR supports the provisioning of file systems and the protection of file storage, using snapshots.

There are a number of mechanisms provided for provisioning file storage and protecting file storage:

This article focuses on the capabilities provided by the Service Catalog to demonstrate the support provided by ViPR. However, you can perform the same operations using the API or CLI.

File Provisioning Support in ViPR

The file storage system that are supported are listed in the support matrix: ViPR Support Matrix.

Prerequisite: File Virtual Pools

The file provisioning capabilities depend on the use of supported file storage systems and the creation of one or more file virtual pools from which file systems can be created.

Information on adding file storage systems and on creating file virtual pools is provided in: Create ViPR Virtual Pools for File Storage.

File Provisioning Support from the UI Service Catalog

The Service Catalog provides the following areas:

Additional operation are supported from the Resources > File Systems described here:

Back to Top

File Provisioning Support

ViPR enables file systems to be created and made available as CIFS shares or NFS exports, or both.

The services provided in the Service Catalog enable a file system to be created first and subsequently shared using CIFS or NFS protocols, alternatively, file systems can be created and shared in a single operation.

The table below lists the services that are provided in the ViPR Service Catalog to support file system provisioning.

Back to Top

Create and manage file systems

ViPR provides the ability to create file systems and to make them available as CIFS shares and NFS exports, or both.

The following services are provided to enable the creation and management of file systems.

The Resources > File Systems area enables you to view information about a file share and how it has been made available as a CIFS share or NFS export.

Expanding File Systems on EMC Isilon

When expanding a file system that resides on an EMC Isilon array, you can specify a file system size that is larger than the available capacity.

All Isilon file systems are thinly provisioned and do not consume any capacity when created. Hence, when extending a file system, a client may violate the limit, but the array will always alert when the array is near full utilization.

Back to Top

Create and manage CIFS shares

You can expose a previously created file system as a CIFS share, or you can create a file system and a CIFS share in a single operation. The service catalog also allows you to delete a CIFS share.

The following services support the creation and management of CIFS shares.

Notes on creating CIFS shares are provided in CIFS Share Notes.

Back to Top

CIFS Share Notes

The following notes apply to the creation of CIFS shares from file systems and file system snapshots.

Share Names

The names of CIFS shares created in ViPR can contain alphanumeric characters but cannot contain space, "_" (underscore), or "-" (dash) characters.

Access Permissions

Access permissions for CIFS shares must be configured using Access Control Lists on the storage system that provides the file system.

Mapping a CIFS Share

To map the Windows share as a network drive, you can look at the order or at the Resources > File Systems page to find its location.

The share location is shown in the format:
 \\ComputerName\SharedFolder
Like this:
\\vipr-isi6132.lss.emc.com\tcshare01 

Back to Top

Create and manage NFS exports

You can expose a previously created file system as an NFS export or you can create a file system and NFS export in a single operation.

The following services are provided to enable you to create and manage NFS exports.

In addition the following operations can be performed from the Resources > File Systems page.

General notes on creating NFS exports are provided in NFS Export Notes and the support for creating exports for each file storage system supported by ViPR is described in NFS Export Rules and Permissions.

Back to Top

NFS Export Notes

The following notes apply to the creation of NFS exports from file systems (and file system sub-directories) and file system snapshots.

Sub-directory Exports

You can export sub-directories of a file system. The sub-directory must already exist and cannot be created from within ViPR. Hence, you can only create exports for directories that have been created on the array itself.

Snapshots of file system sub-directories are not supported.

Adding and Modifying an Export Rule

In general, you can add an export rule for each file system or file system snapshot for each security type. The export rules that can be created for an export depend on the storage system. See NFS Export Rules and Permissions for details.

To add an export rule you need to:
  1. Specify the hosts that can access the export. To specify more than one Export Host for a rule, the IP addresses or FQDNs of the hosts can be entered as a comma separated list.
  2. Specify the Security Type for the export rule.
  3. Set permissions to specify access that clients will have to the export: Read/Write (rw), Read Only (ro), or Root (root).
Modifying an export rule allows you to:
  • Add additional endpoints that can access the share
  • Specify the effective user id of anonymous users
  • Specify the permissions for each export. This allows more granular setting of permissions than those configured when the NFS export is created.

Mounting an NFS Export

To mount the NFS export, you can look at the order or at the Resources > File Systems page or, for a snapshot, at the Resources > File Snapshots page, to find its mount point.

For example:
lglw6132:/ifs/sos/Primary_myexp01_a56483f2-ff47-4a48-a072-c3eae75beb6 
				
If you have created a mount-point directory on you system (for example, /mnt/mynfs) the export can then be mounted using:
mount -t nfs lglw6132:/ifs/sos/Primary_myexp01_a56483f2-ff47-4a48-a072-c3eae75beb6 /mnt/mynfs

Back to Top

NFS Export Rules and Permissions

File systems, file system sub-directories, and file system snapshots can be exported as NFS exports and access to exported file systems depends on the security type and the permissions assigned.

The security types supported and the rules that can be created on each supported array are detailed below.

Isilon
Supports sys, krb5, krb5p, krb5i security types, but allows only one rule to be set.

If you have set a rule for sys, for example, you cannot set a further rule for another security type.

VNX
Supports sys, krb5, krb5p, krb5i security types and allows one rule per security type.
NetApp
Supports sys, krb5, krb5p, krb5i security types and allows one rule per security type.
VNXe
Supports sys security type, with one rule.
Data Domain
Supports sys and krb5 security type, with one rule per security type.

The permissions that can be set for an export are detailed in the table below:

Note Image

For VNXe, a file system or sub-directory export must have root permission in order to mount it on a host and write data to it. If an exports has read-write permissions, you can mount it but cannot write data to it.


Back to Top

Create and remove file system quotas

You can create a quota directory at the root of a file system.

In NetApp this is a QTree, for VNX File this is a Quota Tree, and for Isilon this is a Sub-directory with Quota. The size of the directory is a Group Quota Hard limit.

The Service Catalog provides the following services to enable the creation and deletion of file system quotas:

In addition, the Resources > File Systems page enables the quota directories associated with a file system to be displayed and for the following operations to be performed.

Modifying a quota directory enables the size to be changed and, for NetApp, enables the Security Style and Read/Write Cache (oplock) to be enabled.

Back to Top

File System Protection Support

ViPR supports the creation of file system snapshots and enables previously created file system snapshots to be made available as CIFS shares or NFS exports.

The following services are provided in the ViPR Services Catalog.

Back to Top

File system snapshots

You can create snapshots of file systems that you have created and restore the snapshot.

The following services are provided:

Virtual Pool Maximum Snapshots

To be allowed to create a snapshot of a file system, the file virtual pool that the file system is assigned to must be enabled for snapshot. At the UI, you can access the file virtual pool at Virtual Assets > File Virtual Pools, and the number of snapshots allowed for a selected file virtual pool can be set at the Data Protection > Maximum Snapshots field.

Back to Top

Export NFS snapshots

You can make snapshots available as NFS exports.

The following services support the management of NFS mounted snapshots:

In addition the following operations can be performed from the Resources > File Snapshots page.

Note Image

For VNXe, it is not possible to delete an export for a snapshot; the delete operation causes the export to be deleted from ViPR, however, the VNXe has not deleted it. Subsequent attempts to add an export will fail.


General notes on creating NFS exports are provided in NFS Export Notes and the support for creating exports for each file storage system supported by ViPR is described in NFS Export Rules and Permissions.

Back to Top

Export CIFS snapshots

You can make a file system snapshot available as a CIFS share.

The following services support the creation and management of CIFS shares.

Notes on creating CIFS shares are provided in CIFS Share Notes.

Back to Top

File Provisioning for VMware Support

The file systems for VMware enable the creation of file systems and attaching the created file systems, or existing file systems, as a datastore on an ESX host.

Back to Top

File System Resources

The File System Resources view enables the file systems that have been created in ViPR, and are under ViPR management, to be displayed and enables individual file systems to be viewed and managed.

The File Systems table enables you to view the file systems that have been created, their size, the virtual array and virtual pool to which each belongs, and the protocols they support.

The File System page for each resource comprises the areas detailed in the table below.

Back to Top

File System Snapshot Resources

The File System Snapshots page enables the file system snapshots that have been created in ViPR and are under ViPR management to be displayed, and enables individual snapshots to be viewed and managed.

The File Snapshots table enables you to view the snapshots that have been created and select a snapshot in order to view its details.

The Snapshots page for each resource comprises the areas detailed in the table below.

Back to Top

File storage systems under ViPR management

Once a filesystem is under ViPR management, and has been provisioned or exported to a host through a ViPR service, you should no longer use the storage system element manager to provision or export the filesystem to hosts. Using only ViPR to manage the volume will prevent conflicts between the storage system database and the ViPR database, as well as avoid concurrent lock operations being sent to the storage system. You can however continue to use the storage system element manager to manage storage pools, add capacity, and troubleshoot ViPR issues.

Back to Top