Dell PowerStore 1200T EMC PowerStore Configuring NFS - Page 17

File-level retention, Con DHSM server, Con file-level retention

Page 17 highlights

3. Enter the requested information while noting the following: ● Snapshots must have been created before creating the NFS export. ● Local Path must correspond to an existing folder name within the file system that was created from the host-side. ● The value specified in the NFS Export Details, Name field, along with the NAS server name, constitutes the name by which hosts access the export. ● NFS export names must be unique at the NAS server level per protocol. However, you can specify the same name for an SMB share, and NFS exports. 4. Once you approve the settings, click Create NFS Export. The NFS Export displays on the NFS Export page. 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. Configure DHSM server 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. 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. Configure file-level retention File-level retention is configured at file system creation. For details, see Create file system. NOTE: Retention period parameters can be modified at a later time. Configure NFS Exports 17

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26

3.
Enter the requested information while noting the following:
Snapshots must have been created before creating the NFS export.
Local Path
must correspond to an existing folder name within the file system that was created from the host-side.
The value specified in the
NFS Export Details
,
Name
field, along with the NAS server name, constitutes the name by
which hosts access the export.
NFS export names must be unique at the NAS server level per protocol. However, you can specify the same name for an
SMB share, and NFS exports.
4.
Once you approve the settings, click
Create NFS Export
.
The NFS Export displays on the
NFS Export
page.
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.
Configure DHSM server
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.
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
.
Configure file-level retention
File-level retention is configured at file system creation. For details, see
Create file system
.
NOTE:
Retention period parameters can be modified at a later time.
Configure NFS Exports
17