Powerstore - Configuring CIFS
Powerstore - Configuring CIFS
Configuring SMB
3.x
July 2022
Rev. A02
Notes, cautions, and warnings
NOTE: A NOTE indicates important information that helps you make better use of your product.
CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid
the problem.
WARNING: A WARNING indicates a potential for property damage, personal injury, or death.
© 2020 - 2022 Dell Inc. or its subsidiaries. All rights reserved. Dell Technologies, Dell, and other trademarks are trademarks of Dell Inc. or its
subsidiaries. Other trademarks may be trademarks of their respective owners.
Contents
Additional Resources.....................................................................................................................5
Chapter 1: Overview...................................................................................................................... 6
SMB support.........................................................................................................................................................................6
Planning considerations..................................................................................................................................................... 6
Contents 3
Create an event publisher............................................................................................................................................... 25
Enabling an event publisher for a NAS server............................................................................................................25
Enable event publisher for a file system......................................................................................................................26
4 Contents
Preface
As part of an improvement effort, revisions of the software and hardware are periodically released. Some functions that are
described in this document are not supported by all versions of the software or hardware currently in use. The product release
notes provide the most up-to-date information about product features. Contact your service provider if a product does not
function properly or does not function as described in this document.
Additional Resources 5
1
Overview
This chapter contains the following information:
Topics:
• SMB support
• Planning considerations
SMB support
PowerStore T model supports SMB 1 through SMB 3.1.1. When SMB support is enabled on the NAS server, you can create
SMB-enabled file systems. The NAS server with SMB support can either be stand-alone or Active Directory domain-joined.
Domain-joined NAS servers are placed in the OU=Computers, OU=EMC NAS Servers organizational unit by default.
SMB file systems and shares have the following advanced protocol options:
NOTE: These options, except for Oplocks Enabled, are disabled by default.
Planning considerations
Review the following information before configuring NAS servers and file systems:
File storage support is only available with PowerStore T model appliances. File storage is not supported with PowerStore X
model appliances.
6 Overview
3. Create a domain account in Active Directory.
Creating network VLANs and IP addresses is optional for NAS servers. If you plan to create a VLAN for NAS servers, the VLAN
cannot be shared with the PowerStore T model management, or storage networks. Also, be sure to work with your network
administrator to reserve the network resources and configure the network on the switch. See the PowerStore Networking
Guide for PowerStore T Models for details.
Deployment requirements
NAS services are only available on PowerStore T model appliances. If you are running PowerStore X model appliances, this
service is not available.
You must have chosen Unified during initial configuration of your PowerStore T model appliance. If you chose Block
Optimized while running the Initial Configuration Wizard, NAS services were not installed. To install NAS services, you will
need to have your system reinitialized by a customer support representative. Reinitializing the system:
● Sets the appliance back to the factory state.
● Removes all configuration that was done on the system through the Initial Configuration Wizard.
● Removes any configuration that is performed in PowerStore after initial configuration.
Other considerations
Both nodes on the appliance must be up and running to create a NAS server. If one of the nodes is down on the appliance, NAS
server creation will fail.
Documentation resources
Refer to the following for additional information:
Overview 7
2
Create NAS servers
This chapter contains the following information:
Topics:
• Overview of configuring NAS servers
• Create NAS server for SMB (Windows-only) file systems
• Change NAS server settings
Prerequisites
Obtain the following information:
● Network port, IP Address, Subnet Mask/Prefix Length, Gateway information for the NAS Server.
NOTE: IP Address and Subnet Mask/Prefix Length are mandatory.
● VLAN identifier, if the switch port supports VLAN tagging.
NOTE: You cannot reuse VLANs that are being used for the management and storage networks.
● If you are configuring a stand-alone NAS server, obtain the workgroup and NetBIOS name. Then define what to use for the
stand-alone local administrator of the SMB server account.
● If you are joining the NAS server to the Active Directory (AD), ensure that NTP is configured on your storage system. Then
obtain the SMB computer name (used to access SMB shares), Windows domain name, and the username and password of a
domain administrator or domain user who has a sufficient domain access level to join the AD.
Steps
1. Select Storage > NAS Servers.
2. Select Create.
3. Continue to work through the Create NAS Server wizard.
NOTE: If you select both SMB and NFS protocols, you automatically enable the NAS server to
support multiprotocol. Multiprotocol configuration is not described in this document.
Windows Server Settings
Select Standalone to create a stand-alone SMB server or Join to the Active Directory Domain to
create a domain member SMB server.
If you join the NAS server to the AD, optionally Select Advanced to change the default NetBios name
and organizational unit.
DNS
If you selected to Join to the Active Directory Domain, it is mandatory to add a DNS server.
Optionally, enable DNS if you want to use a DNS server for your stand-alone SMB server.
User Mapping
The User Mapping page displays if you have selected to join the active directory domain.
Keep the default Enable automatic mapping for unmapped Windows accounts/users, to support
joining the active directory domain. Automatic mapping is required when joining the active directory
domain.
Next steps
Once you have created the NAS server for SMB, you can continue to configure the server settings, or create file systems.
Select the NAS server to continue to configure, or modify the NAS server settings.
Steps
1. Select Storage > NAS Servers > [nas server].
2. On the Network page, optionally configure the network interfaces or the routes to external networks as described in
Configure NAS server networks.
3. On the Naming Services page, optionally add, modify, or delete NAS server DNS servers.
NOTE: You cannot disable DNS for NAS servers that support SMB file sharing and that are joined to an Active Directory
(AD).
Prerequisites
Passive mode FTP is not supported.
Steps
1. Select Storage > NAS Servers > [nas server] > Sharing Protocols > FTP tab.
2. Under FTP, if Disabled in on, slide the button to Enable.
3. Optionally also enable SSH FTP. Under SFTP, if Disabled in on, slide the button to Enable.
4. Select which type of authenticated users have access to the files.
5. Optionally, show the Home Directory and Audit options.
● Select or clear the Home directory restrictions. If disabled, enter the Default home directory.
● Select or clear Enable FTP/SFTP Auditing. If checked, enter the directory location of where to save the audit files, and
the maximum size allowed for the audit file.
6. Optionally, Show Messages, and enter a default welcome message, and message of the day.
7. Optionally, show the Access Control List, and add a list of users, groups, and hosts that are allowed, or denied FTP access.
8. Select Apply.
Steps
1. Select Storage > NAS Servers > [nas server].
2. On the Network page, click Add to add another file interface to the NAS server.
3. Enter the File Interface properties.
NOTE: You cannot reuse VLANs that are being used for the management and storage networks.
4. You can perform the following on a File Interface by selecting a file interface from the list. Click:
Option Description
Modify To change the properties of the file interface properties.
Delete To delete the file interface from the NAS server.
Ping To test the connectivity from the NAS server to the external IP address.
Preferred To define which interface PowerStore should default to using when multiple production and backup
Interface interfaces have been defined.
Prerequisites
You can use the Ping option from the File Interface card to determine if the file interface has access to the external resource.
Steps
1. Select Storage > NAS Servers > [nas server] > Network > Routes to External Services.
2. Click Add to enter the route information in the Add Route wizard.
Steps
1. Select Storage > NAS Servers > [nas server] > Protection .
2. Under NDMP Backup, if Disabled is on, slide the button to change to Enabled.
3. Enter a password for the New Password.
The user name is always ndmp.
4. Re-enter the same password as the new password in Verify Password.
5. Click Apply.
Next steps
Leave the NDMP page, and return back to the NDMP page to validate that NDMP is enabled.
Steps
1. Select Storage > NAS Servers > [nas server] > Security > Kerberos.
2. If Disabled is on, slide the button to change to Enabled.
3. Enter the name of the Realm.
4. Enter the Kerberos IP Address and click Add.
5. Enter the TCP Port to use for Kerberos. 88 is the default port.
6. Click Apply.
Steps
1. From PowerStore Manager go to the Storage > NAS Servers > [nas server] > Security > Antivirus tab.
2. If Disabled is on, slide the button to change to Enabled.
3. If you do not have a current CAVA configuration file available:
a. Click Retrieve Current Configuration.
b. Complete the CAVA configuration file template.
c. Upload the updated CAVA configuration file.
4. Click Enabled and Apply to enable Antivirus scanning.
Prerequisites
Ensure that there is a NAS server that is configured to support the SMB protocol as described in Configuring NAS servers.
Steps
1. Select Storage > File Systems and click Create.
2. Continue to work through the Create File System wizard.
Option Description
Select Type Select General file system type
Select NAS Select a NAS server enabled for SMB.
Server
Advanced SMB Optionally choose from the following:
Settings ● Sync Writes Enabled
● Oplocks Enabled
● Notify on Write Enabled
● Notify on Access Enabled
● Enable SMB Events Publishing
For details see File system advanced settings for SMB shares.
File System Provide the file system name, and the size of the file system.
Details
The file system size can be from 3 GB to 256 TB.
NOTE: All thin file systems, regardless of size, have 1.5 GB reserved for metadata upon creation.
For example, after creating a 100GB thin file system, PowerStore T model immediately shows 1.5 GB
used. When the file system is mounted to a host, it shows 98.5 GB of usable capacity.
This is because the metadata space is reserved from the usable file system capacity.
Protection Optionally, provide a protection policy for the file system. PowerStore supports both snapshots and
Policy replication for file storage protection.
Summary Review the summary. Go back to make necessary updates.
3. Click Create File System.
The file system is displayed in the File System list, and if you created an SMB Share, it is displayed in the SMB Share list.
Oplocks Enabled (Enabled by default) Opportunistic file locks (oplocks, also known as Level 1 opslock)
enable SMB clients to buffer file data locally before sending it to a server. SMB
clients can then work with files locally and periodically communicate changes to the
storage system rather than having to communicate every operation over the network
to the storage system. This feature is enabled by default for Windows (SMB) and
multiprotocol file systems. Unless your application handles critical data or has specific
requirements that make this mode or operation unfeasible, leaving the oplocks enabled
is recommended.
The following oplocks implementations are supported:
● Level II oplocks, which informs a client that multiple clients are accessing a file, but
no client has yet modified it. A level II oplock lets the client perform read operations
and file attribute fetches by using cached or read-ahead local information. All other
file access requests must be sent to the server.
● Exclusive oplocks, which informs a client that it is the only client opening the file.
An exclusive oplock lets a client perform all file operations by using cached or
read-ahead information until it closes the file, at which time the server must be
updated with any changes that are made to the state of the file (contents and
attributes).
● Batch oplocks, which informs a client that it is the only client opening the file. A
batch oplock lets a client perform all file operations by using cached or read-ahead
information (including opens and closes). The server can keep a file opened for
a client even though the local process on the client machine has closed the file.
This mechanism curtails the amount of network traffic by letting clients skip the
extraneous close and open requests.
Enable SMB Events publishing Enable the processing of SMB events for this file system.
Steps
1. Select Storage > File System > SMB Share.
2. Click Create and continue to work through the Create SMB Share wizard.
Option Description
Select File Select a file system that has been enabled for SMB.
System
Select a snapshot Optionally, select one of the file system snapshots on which to create the share.
of the file system
Only snapshots are supported for file system protection policies. Replication is not supported for file
systems.
SMB Share Enter a name, and local path for the share. When entering the local path:
Details ● You can create multiple shares with the same local path on a single SMB file system. In these cases,
you can specify different host-side access controls for different users, but the shares within the file
system have access to common content.
● A directory must exist before you can create shares on it. If you want the SMB shares within the
same file system to access different content, you must first create a directory on the Windows host
that is mapped to the file system. Then, you can create corresponding shares using PowerStore.
You can also create and manage SMB shares from the Microsoft Management Console.
PowerStore also created the SMB Share path, which uses the host to connect to the share.
The export path is the IP address of the file system, and the name of the share. Hosts use either the
file name or the share path to mount or map to the share from a network host.
Next steps
Once you create a share, you can modify the share from PowerStore or using the Microsoft Management Console.
To modify the share from PowerStore, select the share from the list on the SMB Share page, and click Modify.
Protocol Encryption Enables SMB encryption of the network traffic through the share. SMB encryption is
supported by SMB 3.0 clients and above. By default, access is denied if an SMB 2 client
attempts to access a share with protocol encryption enabled.
You can control this by configuring the RejectUnencryptedAccess registry key on the
NAS Server. 1 (default) rejects non-encrypted access and 0 allows clients that do not
support encryption to access the file system without encryption.
Access-Based Enumeration Filters the list of available files and directories on the share to include only those to
which the requesting user has read access.
NOTE: Administrators can always list all files.
Branch Cache Enabled Copies content from the share and caches it at branch offices. This allows client
computers at branch offices to access the content locally rather than over the WAN.
BranchCache is managed from Microsoft hosts.
File-level retention
File-level retention (FLR) enables you to prevent modifications or deletion of locked for a specified retention period. Protecting
a file system using FLR enables you to create a permanent, and unalterable set of files and directories. FLR ensures data
integrity and accessibility, simplifies archiving procedures for administrators and improves storage management flexibility.
There are two levels of file-level retention:
● Enterprise (FLR-E) - Protects data from changes that are made by users and storage administrators using SMB, NFS, and
FTP. An administrator can delete an FLR-E file system which includes locked files.
● Compliance (FLR-C) - Protects data from changes that are made by users and storage administrators using SMB, NFS,
and FTP. An administrator cannot delete an FLR-C file system which includes locked files. FLR-C complies with SEC rule
17a-4(f).
The following restrictions apply:
● File-level retention is available on unified PowerStore system 3.0 or later.
● FLR is not supported in VMware file systems.
● Enabling a file-level retention for a file system and the level of FLR are set at file system creation time and cannot be
modified.
● FLR-C does not support restoring from a snapshot.
● When refreshing using a snapshot, both file systems must be of the same FLR level.
● When replicating a file system, source and destination file systems must be of the same FLR level.
● A cloned file system has the same FLR level as the source (cannot be modified).
The FLR mode is displayed in the File Systems screen.
Prerequisites
File-level retention requires DHSM server credentials.
DHSM server is also required for Window hosts that want to use FLR and are required to install FLR toolkit that enables
managing FLR-enabled file systems.
Steps
1. Select Storage > NAS Servers > [NAS server] > Protection > DHSM.
2. If disabled, slide the button to Enabled.
3. Enter the user name and password for the DHSM server and verify the password.
4. Select Apply.
Steps
1. Select Storage > File Systems > [file system] > Security & Events > File-Level Retention.
2. Set the retention period parameters:
● Minimum retention period - Specifies the shortest period for which an FLR-enabled file system can be protected (default
value is one day).
● Default retention period - Used when a file is locked and a retention period is not specified (default value is one year).
● Maximum retention period - Specifies the longest period for which an FLR-enabled file system can be protected (default
value is infinite).
3. Optionally, set the advanced settings:
● Automatic file locking - You can specify whether to automatically lock files in an FLR-enabled file system and set a policy
interval that determines the time period between file modification and automatic lock (policy interval default value is one
hour).
● Automatic file deletion - You can specify whether to automatically delete locked files after their retention period is
expired. The first scan for locating files for deletion is seven days after the feature is enabled.
4. Select Apply.
Types of quotas
There are three types of quotas you can put on a file system.
User quota on a quota tree Limits the amount of storage that is consumed by an individual user storing data on
the quota tree.
Quota Limits
Table 6. Hard and Soft Limits
Type Descriptions
Hard A hard limit is an absolute limit on storage usage.
If a hard limit is reached for a user quota on a file system or quota tree, the user cannot write
data to the file system or tree until more space becomes available. If a hard limit is reached
for a quota tree, no user can write data to the tree until more space becomes available.
Additional information
For more information on quotas, see the Dell EMC PowerStore File Capabilities White Paper.
Steps
1. Select Storage > File Systems > [file system] > Quotas.
2. Select Storage > File Systems > [file system] > Quotas > Properties.
3. Slide the Disabled button to the right until it is Enabled.
4. Enter the default Grace Period for the user quota on the file system which will count down time after the soft limit is met
until the hard limit will be met.
5. Enter a default Soft Limit, and a default Hard Limit and click Update.
Prerequisites
You must enable Quotas and set the User Quota defaults before you can add a User Quota to a files system. See Enable User
Quotas.
Steps
1. Select Storage > File Systems > [file system] > Quotas > User.
2. Select Add on the User Quota page.
3. In the Add User Quota wizard, provide the requested information. To track space consumption without setting limits, set
Soft Limit and Hard Limit to 0, which indicates no limit.
4. Select Add.
Steps
1. Select Storage > File Systems > [file system] > Quotas > Tree Quotas.
2. Select Add.
3. Slide the Enforce User Quota to the right to enabled User Quota defaults on the Tree Quota.
4. Provide the requested information.
● Enter a Grace Period to count down the time between the soft and hard limit. You will begin to receive alerts once the
grace period is reached.
● To track space consumption without setting limits, set the Soft Limit and Hard Limit fields to 0, which indicates no
limit.
5. Select Add.
Steps
1. Select Storage > File Systems > [file system] > Quotas > Tree Quotas.
2. Select a path, and click Add User Quota.
3. On the Add User Quota screen, provide the requested information. To track space consumption without setting limits, set
the Soft Limit and Hard Limit fields to 0, which indicates no limit.
Overview
PowerStore enables you to replicate NAS servers asynchronously between a local system and a remote system. Replication
occurs at a NAS server level - all the file systems within the replicated NAS server are replicated to the remote system. RPO is
configured at the NAS server level and is identical across all associated file systems.
It is not required to define separate protection policies for NAS servers. The same protection policies can be applied to both
block and file replication.
You can fail over a replication session to the remote system. Failover occurs for all the file systems within the failed over NAS
server.
The following pre-requisites are required to enable file replication:
● A file remote system
● A File Moblility network must be configured and mapped (see Networking Guide for PowerStore T models on the
PowerStore Documentation page at https://www.dell.com/powerstoredocs).
● A protection policy that includes a replication rule.
For detailed information about NAS server replication procedures, see Protecting your Data on the PowerStore Documentation
page at https://www.dell.com/powerstoredocs.
Events publishing
CEE enables third-party applications to receive event information from the storage system upon accessing file systems.
The Common Event Enabler (CEE) provides an event publishing solution for PowerStore clients that allow third-party
applications to register and receive event notification and context from the storage system when accessing file systems.
Receiving event notification enables you to take event-driven actions on the storage to prevent security threats such as
ransomware or unauthorized access.
The CEE Common Events Publishing Agent (CEPA) consists of applications that are designed to process SMB and NFS files
and directory event notifications. The CEPA delivers both event notification and associated context to the application in one
message. Context can consist of file metadata or directory metadata that is needed for business policy decisions.
To enable CEE CEPA support, you must enable CEE CEPA and create an Event Publishing Pool on the NAS server.
An Event Publishing Pool defines the CEPA servers and the specific events that trigger notifications.
After configuring the NAS server, you can enable events publishing on the file system from which you want to receive events.
When a host generates an event on the file system over SMB or NFS, the information is forwarded to the CEPA server over
an HTTP connection. The CEE CEPA software on the server receives the event and publishes it, thus enabling the third-party
software to process it.
To use the Events Publishing Agent, it is required to have a PowerStore system with at least one NAS server configured on the
network.
For additional information about CEPA which is part of the Common Event Enabler (CEE), see Using the Common Event Enabler
on Windows Platforms on https://www.dell.com/support.
Prerequisites
To create an event publishing pool, you must have an Events Publishing (CEPA) server FQDN.
Steps
1. Select Storage > NAS Servers.
Steps
1. Select Storage > NAS Servers.
2. Select NAS Settings.
3. Select Event Publishers and then select Create.
4. Continue to work through the Create Event Publisher wizard.
Steps
1. Select Storage > NAS Servers > [nas server].
2. On the Security & Events page, select Events Publishing.
3. Select an Event Publisher from the list and enable it.
4. Select whether to enable the event publisher for all the file systems that are defined on the NAS server.
Steps
1. Select Storage > File Systems > [file system].
2. On the Protection page, select Events Publishing.
3. Enable the event publisher for the file system and select the protocol.
4. Click Apply.