Administrator Guide

Table Of Contents
Check marks appear in all the Allow checkboxes.
6. Click OK.
7. Click two OK buttons.
Both windows close, returning you to the Windows Explorer main window.
8. Close the MMC console.
Create a NAS Thin Clone
During the creation of a NAS thin clone, you cannot modify its size, minimum reserve percentage, or in-use warning limit percentage.
These settings can be changed later.
1. In the NAS panel, select a local container that contains a snapshot.
2. Select the snapshot.
3. Click the Create thin clone link in the Activities panel to open the Create Thin Clone wizard.
4. Either use the default container name or modify the container name.
5. Click Next.
A NAS container size horizontal bar is displayed, along with a minimum reserve slider. The percentages in the slider are not
editable on the create page. The size is inherited from the base container and can be modied after the thin clone is created.
6. Move the slider to adjust the percentages.
7. Click Next.
To create an NFS export and an SMB share, type the name and directory information in the dialog box.
8. Click Next.
9. Review the Create NAS Thin Clone summary.
10. Click Finish.
Client Networks
The client network is used to provide client access to the SMB shares and NFS exports. The client network is assigned one or more
virtual IP addresses (VIPs) that allow clients to access the NAS cluster as a single entity. The client VIP also enables load balancing
between NAS controllers, and ensures failover in the event of a NAS controller failure.
NOTE: Dell recommends that you connect all the client network interfaces and distribute the connections across stacked
network switches for high availability.
NOTE: Dell recommends that you separate the client and SAN network to avoid the following problems:
Congestion caused by client trac and storage trac passing over one network
Issues related to static routes conguration
You can congure up to eight secondary or additional client networks on your NAS cluster. This conguration allows client trac to
be separated and secured. You can congure VLANS for each client network that is available in the NAS cluster.
If the client network is a routed network, you can modify the client network conguration and add more NAS cluster IP addresses for
additional DNS load balancing across multiple client networks. The total number of NAS cluster IP addresses depends on the bonding
mode and NAS appliance models.
A default gateway IP address, bonding mode, and MTU are the same for all the client networks. You cannot congure a unique
default gateway IP address, bonding mode, and MTU for individual client networks.
If client access to the NAS cluster is not through a router (the network has a "at" topology), you can dene one client VIP per NAS
controller. If clients access the FluidFS system through a router, dene a client VIP for each client interface port per NAS controller.
198
NAS Container Operations