Nasuni Filer Administration Guide

Transcription

1 Nasuni Filer Administration Guide Version 7.2 November 2015 Last modified: November 6, Nasuni Corporation All Rights Reserved

2 Document Information Nasuni Filer Administration Guide Version 7.2 November 2015 Copyright Copyright by Nasuni Corporation. All rights reserved. Information in this document is subject to change without notice and does not represent a commitment on the part of Nasuni. The software described in this document is furnished under a license agreement. The software may be used only in accordance with the terms of the license agreement. It is against the law to copy the software on any medium. No part of this manual may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, for any purpose without the express written permission of Nasuni Corporation. Notice Although Nasuni Corporation has attempted to ensure the accuracy of the content of this manual, it is possible that this document might contain technical inaccuracies, and typographical or other errors. Nasuni assumes no liability for any error in this publication, and for damages, whether direct, indirect, incidental, consequential or otherwise, that might result from such error, including, but not limited to loss of data or profits. Nasuni provides this publication as is without warranty of any kind, either express or implied, including, but not limited to implied warranties of merchantability or fitness for a particular purpose. Trademarks NASUNI, UNIFS, and the ovals logo are Nasuni trademarks and service marks. All other names, brands and products are the property of their respective owners. Contacting Nasuni Corporation Nasuni Corporation 313 Speen Street Natick, MA Telephone: Sales: Fax: [email protected] Technical Support Telephone: NASUNI ( ) [email protected] Technical Support is available 24/7/365 for full production customers.

3 Contents Contents iii Preface xi Audience xi What s in this Book xi Text Conventions xii Product Documentation xiii Electronic Publications xiii Chapter 1: Introducing the Nasuni Filer Nasuni Filer Nasuni Management Console Key Terms Terminology About File Systems About the Cache Cache Capacity Trial Mode Chapter 2: Starting Out Starting with the Nasuni Filer Installing the Nasuni Filer Disaster recovery Creating new volumes Managing the Nasuni Filer Managing data Providing data access to users Sharing data between Nasuni Filers Adding data to volumes Protecting data Managing volumes Nasuni Filer Administration Guide 7.2 iii

4 Contents Security Handling encryption keys Role-based access control SSL certificates Antivirus protection Firewall protection Changing performance Alternatives for configuring your Nasuni Filer Configuring your Nasuni Filer using the Nasuni Filer user interface Configuring your Nasuni Filer using either the user interface or the NMC Configuring the Nasuni Management Console Chapter 3: Login Page Logging in to the Nasuni Filer Resetting Administrative Account (Forgot Password) Navigation Bar on Login Page Help Power Chapter 4: Common Screen Elements Nasuni Corporate Web Site Status Messages Username Name of the Nasuni Filer Navigation Bar Functions Viewing Notifications Viewing the Nasuni Filer Help Viewing the Nasuni Filer Release Notes Shutting Down and Rebooting the Nasuni Filer Logging Out of the Nasuni Filer Changing User Password Pop-up Software Update Notifications Notifications Nasuni Management Console message and notice Chapter 5: Home Page Data Growth Chart New Data in Cache Chart Network Activity Charts Nasuni Filer Administration Guide 7.2 iv

5 Contents Migration Status Snapshot Status Local Cache Status Quality of Service (inbound and outbound bandwidth limit) Volume Status Local Time Status Chapter 6: Volumes Page Viewing Local and Remote Volume Information Local Volume Information Remote Volume Information Managing Volumes Default Volume Default CIFS share Adding a Volume Connecting to a Remote Volume Take a Snapshot Now Viewing Volume Properties Volume properties page for CIFS and NFS volumes and FTP directories Volume properties page for iscsi volumes Data Growth Chart Changing Volume Properties Renaming a Volume Changing iscsi Settings Changing the Volume Quota Directory Quotas File Alert Service Antivirus Service File System Auditing Encryption Key Management Remote Access Enabling or Disabling Auto Cache for Volumes Snapshot Scheduling Sync Scheduling Snapshot Directory Access Snapshot Retention Pinned Folders Auto Caching Folders Nasuni Filer Administration Guide 7.2 v

6 Contents Deleting a Volume CIFS Shares, NFS Exports, and FTP Directories FTP Directories Multiple Volume Protocols Chapter 7: Managing Data Adding Data to Volumes Accessing volumes Adding data to a volume Accessing Data Folder and file access permissions in Windows Folder and file access permissions in UNIX and Linux Accessing data using the FTP/SFTP protocol Mapping a Windows network drive to a CIFS share Accessing an iscsi volume in Windows Mounting a CIFS share in Linux or UNIX Defining NFS datastores using VMware client Mounting an NFS export in Linux or UNIX Web Access Nasuni Mobile Access Nasuni Desktop Client Chapter 8: Remote Access Overview Enabling Remote Access Viewing Remote and Local Volume Connections Connecting to a Remote Volume Configuring a Sync Schedule Synchronization (Merge) Conflicts Synchronization (Merge) Conflict Log File Synchronization (Merge) Conflict Messages Name of Conflicting File Disconnecting from a Remote Volume Chapter 9: File Browser Page What is a Snapshot? File System Browser Selecting Volume, Folder, or Files Actions with Selected Volume, Folder, or Files Global File Locking Nasuni Filer Administration Guide 7.2 vi

7 Contents Restoring Volume, Folder, or Files Using Snapshot Directory Access Accessing CIFS and NFS Snapshot Directories using Windows Accessing CIFS and NFS Snapshot Directories using UNIX Accessing Files in Snapshot Directories Restoring a File or a Folder from a Snapshot Directory Chapter 10: Services Page Data Migration Configuring a CIFS Migration Source Configuring an NFS Migration Source Configuring a CIFS Data Migration Configuring an NFS Data Migration Editing a Data Migration Scheduling a Migration Viewing migration information Rerunning a Migration Procedure Disconnecting from (deleting) a Migration Source Deleting a Migration Procedure Viewing a Migration Log Side Load Starting the Side Load process Viewing and controlling the Side Load process Nasuni Desktop and Mobile Access Mobile Access Desktop Client Nasuni Management Console Remote Support Service Sending Diagnostics to Nasuni Chapter 11: Configuration Page Settings Nasuni Filer Description HTTPS Proxy Configuration Network Configuration About Traffic Groups Configuring Network Settings Quality of Service Settings Nasuni Filer Administration Guide 7.2 vii

8 Contents Adding a Quality of Service rule Changing a Quality of Service rule Deleting a Quality of Service Rule Filer Time Configuration FTP Settings Configuring FTP settings Domain Settings Joining a Nasuni Filer (that has not previously joined any domain) to a domain 272 Joining the Nasuni Filer to an Active Directory domain Viewing Active Directory domains Allowing Active Directory domains to access the Nasuni Filer Leaving an Active Directory domain General CIFS Settings Joining a Nasuni Filer (not previously joined to any domain) to a domain Configuring CIFS settings API Access Keys Encryption Key Management Viewing information about encryption keys Adding (Importing or Uploading) Encryption Keys Downloading (Exporting) Generated Encryption Keys Escrowing Encryption Keys with Nasuni Deleting Encryption Keys Firewall Quota Settings Viewing quota report configuration Adding a new quota report Sending a quota report (capacity report) now Changing an existing quota report Deleting a quota report SSL Certificates Viewing SSL CA-signed Certificates or Self-Signed Certificate Generating SSL CA-signed Certificates or a Self-Signed Certificate Copying Existing SSL Certificates Uploading SSL Certificates Replacing SSL Certificates or SSL Certificate Chains Setting SSL Certificates Saving SSL Certificates Deleting SSL Certificates or Certificate Requests Nasuni Filer Administration Guide 7.2 viii

9 Contents Resetting an SSL Certificate Users and Groups Viewing Permission Groups and Users Adding Permission Groups Editing Permission Groups Deleting Permission Groups Adding Users Editing Users Deleting Users SNMP Monitoring Web Access Branding Automatic Software Updates Cache Settings Global Locking Changing User Password Chapter 12: Status Page Subscription Status Refreshing Subscription License Software Updates Cache Jobs Viewing or cancelling cache jobs High-Availability Status Viewing high-availability hardware appliance status Triggering failover manually Network Status Network Status Traffic Groups Physical Ports Network Activity Charts Platform Status Viewing platform status RAID Arrays (hardware appliances only) RAID Disks (hardware appliances only) Full Disk Encryption (FDE) (hardware appliances only) Enabling Full Disk Encryption Changing the Full Disk Encryption Password CIFS Status Nasuni Filer Administration Guide 7.2 ix

10 Contents CIFS Shares Resetting the CIFS Authentication Cache Resetting All CIFS Clients Disconnecting a Single CIFS Client iscsi Status NFS Status FTP Status Viewing FTP directories and FTP clients Disconnecting FTP clients File Heuristics File Types in snapshots File Sizes in snapshots Chapter 13: Notifications Viewing Notifications Acknowledging Notifications Deleting Notifications Downloading Notifications Chapter 14: Disaster Recovery Side Load and Disaster Recovery Recovering Data with the Nasuni Filer Appendix A: Nasuni Terms of Service and License Agreement Nasuni Corporation Appendix B: Filtering Displays Appendix C: Glossary Index Nasuni Filer Administration Guide 7.2 x

11 Preface Audience This Administration Guide is intended for the IT administrator or person responsible for managing Network Attached Storage (NAS) and Storage Area Networks (SAN) using the Nasuni Filer user interface. What s in this Book This guide contains the following chapters: Chapter 1, Introducing the Nasuni Filer, on page 1 describes the major features and concepts of the Nasuni Filer. Chapter 2, Starting Out, on page 6 gives shortcuts to common tasks that users can perform with the Nasuni Filer user interface. Chapter 3, Login Page, on page 19 explains how to log in to the Nasuni Filer, reset the account, and access online help. Chapter 4, Common Screen Elements, on page 23 explains the user interface elements that are common to all the pages, including status messages, online help, messages, and the procedure for shutting down the Nasuni Filer. Chapter 5, Home Page, on page 32 explains the features of the Home page, including viewing details of Nasuni Filer status. Chapter 6, Volumes Page, on page 41 explains how to add or delete a volume, view volume details, modify volume properties, define CIFS shares and NFS exports and FTP/SFTP directories, manage remote access, and configure snapshots. Chapter 7, Managing Data, on page 137 explains how to add and access data on Windows, Linux, and UNIX systems, including Web Access, Mobile Access, and Desktop Client. Chapter 8, Remote Access Overview, on page 170 explains how to manage remote access, including synchronization. Chapter 9, File Browser Page, on page 176 explains how to select versions of files and folders to download or restore from snapshots. Chapter 10, Services Page, on page 199 explains how to configure data migration, enable remote support, configure Desktop/Mobile Access, and place the Nasuni Filer under the management of the Nasuni Management Console. Nasuni Filer Administration Guide 7.2 xi

12 Preface What s in this Book Chapter 11, Configuration Page, on page 246 explains how to configure the network, the Nasuni Filer description, CIFS settings, time, FTP/SFTP settings, , security and encryption, SSL certificates, firewall, Quality of Service, HTTPS proxy, Active Directory domains, quota settings, automatic updates, SNMP monitoring, cache, users and groups, passwords, and account reset. Chapter 12, Status Page, on page 337 explains the features for monitoring the status of software, network, hardware, subscription, CIFS shares, NFS exports, FTP/SFTP directories, iscsi volumes, and file statistics. Chapter 13, Notifications, on page 371 explains how to view messages about various conditions in the Nasuni Filer. Chapter 14, Disaster Recovery, on page 376 explains how to recover files and folders with the Nasuni Filer in the event of a disaster. Appendix C, Glossary, on page 386 provides definitions of terms related to the Nasuni Filer. Appendix A, Nasuni Terms of Service and License Agreement, on page 384 is the link to the Nasuni Terms of Service and License Agreement. Text Conventions The following text conventions are used in this document: Convention Description 1. Number Used to indicate a step in a task. Bullet Bold Italics Underline Monospace Used for items in a list without any particular order. Used to give emphasis to a word. Also used for named graphical elements. Used to represent options or parameters. Used for hyperlinks, such as links to Web sites. Used to indicate pathnames, filenames, folder names, typed information, and code. Nasuni Filer Administration Guide 7.2 xii

13 Product Documentation Electronic Publications Extensive documentation is available for all aspects of installing, configuring, and operating the Nasuni Filer. The latest version of each of the following documents is available in PDF format at Hardware Getting Started Guide: For setting up the Nasuni Filer on the Nasuni Filer hardware appliance. To download this guide for the NF-50, visit: To download this guide for the NF-200, visit: To download this guide for the NF-400, visit: To download this guide for the NF-440, visit: To download this guide for the NF-400H, visit: To download this guide for the NF-600, visit: Virtualization Getting Started Guide: For installing the Nasuni Filer on a virtual machine within a corporate network. To download this guide, visit: Virtualization Getting Started Guide for Azure: For installing the Nasuni Filer on the Microsoft Azure cloud virtual machine. To download this guide, visit: Virtualization Getting Started Guide for EC2: For installing the Nasuni Filer on the Amazon EC2 cloud virtual machine. To download this guide, visit: Nasuni Filer Administration Guide 7.2 xiii

14 Product Documentation Electronic Publications Initial Configuration Guide: For configuring and deploying the Nasuni Filer after the initial installation on the hardware appliance or virtual machine. To download this guide, visit: Administration Guide: For managing unified storage using the Nasuni Filer. To download this guide, visit: Nasuni Management Console Guide: For managing multiple Nasuni Filers. To download this guide, visit: Nasuni Management Console Quick Start Guide: To quickly get started using the Nasuni Management Console to manage multiple Nasuni Filers. To download this guide, visit: Using Multiple Protocols: Discusses scenarios requiring particular access to data, and how different combinations of protocols can help provide the access that clients need. To download this guide, visit: Third-Party Licensing Guide: Listing of third-party software used in the Nasuni Filer. To download this guide, visit: Nasuni Filer Administration Guide 7.2 xiv

15 Chapter 1: Introducing the Nasuni Filer Nasuni s Enterprise Storage Services deliver an advanced storage solution using a cloud infrastructure. The core technology is a next-generation storage controller the Nasuni Filer that offers the security and performance of traditional storage, while adding unlimited scalability, automatic offsite protection, and global multi-site access to files. The Nasuni system is managed through a single, small-footprint point of control within the enterprise s data center. The Nasuni Filer is an on-premises storage device supporting NFS, CIFS, FTP/SFTP, iscsi, and HTTP/ REST protocols. The Nasuni Filer is fully integrated with Active Directory, Distributed File System (DFS), and Windows Previous Versions. It includes a high-performance cache and takes periodic snapshots that enable file-level restores. The Nasuni Filer is available as a virtual appliance, as a hardware appliance, and as a Microsoft Azure and Amazon EC2 virtual appliance. Its reach and capacity far exceed those of a traditional controller, however, because it does not rely only on memory and local disk to manage its data: it has the entire capacity of the cloud at its disposal. All data is deduplicated, compressed, and encrypted before storage. Multi-site access enables organizations with several locations to work on a single set of shared data. Nasuni s architecture allows multiple storage controllers to have live access to the same volume of data. Organizations benefit by having a simple, safe, and secure way to share data across any number of sites. Nasuni s multi-site access enables capabilities that include: Secure data distribution to remote office/branch office (ROBO). Remote offices forwarding data to a central point. Two-way synchronized read-write. Multi-site access does away with cumbersome replication schemes and slow WAN optimizers. Nasuni Filer Nasuni s Enterprise Storage Services are delivered through the Nasuni Filer, a storage controller that runs in your data center and provides primary storage with built-in backup, offsite protection, and multisite access. With your Nasuni Filer, you manage your volumes and performance using the Web-based Nasuni Filer user interface. Nasuni Management Console The Nasuni Management Console enables you to monitor and manage many Nasuni Filers from one central appliance. Using the Nasuni Management Console, you can view the status of all of your managed Nasuni Filers, as well as configure their settings. With the Nasuni Management Console, you can ensure consistent settings on all your Nasuni Filers. Nasuni Filer Administration Guide 7.2 1

16 Key Terms Key Terms The following terms are helpful in understanding the Nasuni Filer: Nasuni Filer: The storage controller in your data center that integrates with your infrastructure via CIFS, NFS, iscsi, FTP/SFTP, or HTTPS/REST protocols. The Nasuni Filer can be mapped as a network drive. Nasuni Filer user interface: The Web-based graphical user interface with which you configure and manage the Nasuni Filer. The Nasuni Filer user interface is accessible with supported Web browsers including Mozilla Firefox, Internet Explorer, Safari, and Google Chrome. Nasuni Management Console (NMC): The Web-accessible appliance with which you can configure and manage multiple Nasuni Filers. The Nasuni Management Console is accessible with supported Web browsers including Mozilla Firefox, Internet Explorer, Apple Safari, and Google Chrome. Cloud storage: Internet-based, highly protected, unlimited storage. Volume: A set of files and directories (CIFS, NFS, and FTP/SFTP) or blocks of data (iscsi). Share/export: An access point to a folder on a volume that can be shared or exported on your network. Access to a CIFS share can be customized on a user-level or group-level basis. You can create many shares or exports on a volume, for different purposes or audiences. Cache: The local storage of the Nasuni Filer. All data and metadata that is accessed regularly is kept locally in the cache. If requested data is not locally resident, it is staged into the cache and provided for the request. Snapshot: A snapshot is a complete picture of your volume at a specific point in time. Snapshots offer data protection by enabling you to recover data deleted in error or to restore an entire file system. After a snapshot has been taken and is sent to cloud storage, it is not possible to modify that snapshot. Also, see Glossary on page 386. Terminology The following terminology is useful in understanding Nasuni technology: Accessing data from Windows: See Network Drives, including Mapping a Windows network drive to a CIFS share on page 143, Accessing an iscsi volume in Windows on page 144, and Web Access on page 150. Accessing data from Linux and UNIX: See Network Drives, including Mounting a CIFS share in Linux or UNIX on page 147, Mounting an NFS export in Linux or UNIX on page 149, and Web Access on page 150. Alerts and messages: See Notifications, including Notifications on page 371. Allowing access to data on Nasuni Filer: See Shares, Exports, FTP directories, and Remote Access, including Adding a New CIFS Share to a Volume on page 101, Adding an NFS Export to a Volume on page 117, Adding FTP directories for a volume on page 127, and Remote Access on page 83. Nasuni Filer Administration Guide 7.2 2

17 Terminology Backup: See Snapshots, including Snapshot Scheduling on page 88 and Snapshot Retention on page 94. Bandwidth: See Quality of Service (QoS), including Quality of Service (inbound and outbound bandwidth limit) on page 39. Local data: See Cache, including About the Cache on page 4 and Cache Settings on page 333. Maximum capacity: See Quota, including Viewing Local and Remote Volume Information on page 42, Changing the Volume Quota on page 65, and Directory Quotas on page 66. Merging data from other Nasuni Filers with your Nasuni Filer: See Sync, including Sync Scheduling on page 90. Moving data to your Nasuni Filer: See Data Migration, including Configure on page 200. Other Nasuni Filers: See Remote Volumes, including Connecting to a Remote Volume on page 51. Sets of data: See Volumes, including Adding a Volume on page 46. Also, see Glossary on page 386. Nasuni Filer Administration Guide 7.2 3

18 About File Systems About File Systems File system data and metadata are stored locally on the Nasuni Filer. However, permanent storage is in the form of cloud-based storage. Changes in files are sent to cloud storage by the Nasuni Filer, at times that your snapshot schedule specifies and at rates specified by your Quality of Service (inbound and outbound bandwidth) setting. On volumes with global file locking enabled, global locking provides file synchronization independently of the snapshot and synchronization processing. You can also manually initiate snapshots. Note: The Nasuni Filer supports Windows, UNIX, and Linux clients. Client capabilities and behavior vary, depending on the client type and version of the client operating system. File system metadata includes: Standard access control list (ACL) and file system metadata, such as permissions and file size. Version history of operations on files, including creating, updating, deleting, and moving files. Location of file versions. Data is versioned with the ability to go back to a point in time at the volume, directory, and file levels. Volume metadata includes: Version history of operations on the volume, including creating, updating, deleting, and moving the volume. When and by whom the volume was instantiated. Protocol: CIFS, NFS, FTP/SFTP, iscsi, and HTTP/REST. Encryption settings. About the Cache When you first launch the Nasuni Filer, the local cache is empty, although the Cache display on the Home page might reflect the data required to set up the file system. Afterwards, any data written to a volume is staged in the local cache. After one hour, the first snapshot occurs. (To take a snapshot sooner, click Take snapshot now on the Volumes page.) Each file in the cache is deduplicated, compressed, encrypted, and sent to cloud storage. This is the only time that the entire cache is sent to cloud storage. Subsequent snapshots include only the changes between the original version of the files and the most recent version of the files. The cache continuously tracks recently changed data, such as files created or changed since the last snapshot. New data that has been saved to the cache, but has not yet been protected in cloud storage, is classified as new data in cache not yet protected. The most recently used files remain in the cache. Saved data that was written once and rarely used afterwards is eventually removed ( evicted ) from the cache to free up space for data that is accessed more frequently. If one of these evicted files is later requested for reads or writes, the Nasuni Filer retrieves the file from cloud storage and puts it back into the local cache automatically. Nasuni Filer Administration Guide 7.2 4

19 Trial Mode Cache Capacity The cache keeps local copies of working files for fast access to frequently accessed data. When the cache starts to become full, it first removes ( evicts ) files that have already been sent to cloud storage and are rarely accessed, using a least-recently-used (LRU) algorithm. If more space is necessary, a snapshot is performed to protect more data in cloud storage, after which the protected data can then be evicted from the cache. As a result, the cache rarely reaches full capacity. After a snapshot is complete, the cache status displays 0% new data in cache not yet protected, until you change data or create new data. You can continue to use your system normally during each snapshot. The size and status of the cache is displayed on the Home page. Figure 1-1: Cache status. As a default, the Nasuni Filer tries to keep about 30 percent of the cache free to accept new data. Pinning volumes or folders in the cache or manually changing the cache settings can affect the percentage of the cache that is free to accept new data. Trial Mode You are entitled to a free, 14-day, fully-functional evaluation of the Nasuni Filer. After your free trial period has expired, you must upgrade to continue using the product. If the Nasuni Filer is in Trial mode, the Trial Mode indicator appears on the bottom of each page. Figure 1-2: Trial Mode indicator. Clicking this indicator opens the Subscription Status page, which includes details about how much time remains in the Trial period. See Subscription Status on page 338. When your trial period ends, you cannot send any data to or receive data from cloud storage until you upgrade your account. Local data in the cache is accessible. However, if you do not upgrade your account within 30 days after the trial period ends, your data might be deleted. See the Nasuni Filer Terms of Service and License Agreement for details at To upgrade your account from Trial mode, contact your Nasuni account representative for assistance. Nasuni Filer Administration Guide 7.2 5

20 Chapter 2: Starting Out This chapter includes these sections: An overview of some of the tasks that you can perform with the Nasuni Filer, along with links to further information. Note: If this Nasuni Filer is under the control of the Nasuni Management Console, for many of these tasks, you use the Nasuni Management Console to view information or perform actions. For details, see the Nasuni Management Console Guide. A list of available actions on the Nasuni Filer user interface and the Nasuni Management Console. Starting with the Nasuni Filer Installing the Nasuni Filer The Nasuni Filer is already installed on Nasuni hardware appliances. Installing and configuring the Nasuni Filer on a virtual platform is a simple and straightforward process. First, download and install the software on your virtual platform. See the Nasuni Filer Virtualization Getting Started Guide. To install on the Microsoft Azure virtual platform, see Nasuni Filer Virtualization Azure Getting Started Guide. To install on the Amazon EC2 virtual platform, see Nasuni Filer Virtualization EC2 Getting Started Guide. Run the Install Wizard, including entering the Serial Number and Authorization Code, found under the Account section of or on the Account Status page of the Nasuni Management Console. See the Nasuni Filer Initial Configuration Guide. A best practice for Nasuni Filers is to join an Active Directory domain as soon as installation is complete. For details, see Joining a Nasuni Filer (that has not previously joined any domain) to a domain on page 272. Disaster recovery You can perform the disaster recovery procedure for a genuine emergency, or when moving the Nasuni Filer to another location. See Disaster Recovery on page 376. Nasuni Filer Administration Guide 7.2 6

21 Starting with the Nasuni Filer Creating new volumes You use volumes to manage data. If you do not already have a volume set up, you can create a new volume. Note: If this Nasuni Filer is under the control of the Nasuni Management Console, you use the Nasuni Management Console to perform this task. Before creating a new volume, ensure that you have the encryption keys you would like to use. Nasuni recommends creating and uploading your own encryption keys ( Adding (Importing or Uploading) Encryption Keys on page 289). Otherwise, you can specify generating a new encryption key when you create the new volume. Nasuni also recommends safeguarding your encryption keys yourself. You can download generated encryption keys for safeguarding ( Downloading (Exporting) Generated Encryption Keys on page 290). Alternatively, you can escrow encryption keys with Nasuni ( Escrowing Encryption Keys with Nasuni on page 291). To create a new volume on a Nasuni Filer, see Adding a Volume on page 46. You can create CIFS shares ( Adding a New CIFS Share to a Volume on page 101), NFS exports ( Adding an NFS Export to a Volume on page 117), or FTP/SFTP directories ( Adding FTP directories for a volume on page 127) for users to access. If you created a CIFS share, NFS export, or FTP/SFTP directory automatically when you created a new volume, you can check and edit the settings for CIFS shares ( Editing a CIFS Share on page 113), NFS exports ( Editing an NFS Export on page 120), or FTP/SFTP directories ( Editing FTP directories on page 132). Managing the Nasuni Filer You have many options for configuring the Nasuni Filer. You can configure the Nasuni Filer to automatically download and install software updates. To prevent automatic software updates from occurring at inconvenient times, you can specify the days and times for automatic software updates to occur, or prevent automatic software updates entirely. See Automatic Software Updates on page 332. Alternatively, you can manually update the Nasuni Filer software. See Software Updates on page 340. Note: If this Nasuni Filer is under the control of the Nasuni Management Console, you use the Nasuni Management Console to perform this task. You can view the status and expiration date of your subscription. See Subscription Status on page 338. You can also refresh your subscription license. See Refreshing Subscription License on page 339. Note: If this Nasuni Filer is under the control of the Nasuni Management Console, you use the Nasuni Management Console to perform this task. The Notifications page lets you view and acknowledge Nasuni Filer messages. See Notifications on page 371. Note: If this Nasuni Filer is under the control of the Nasuni Management Console, you use the Nasuni Management Console to perform this task. Nasuni Filer Administration Guide 7.2 7

22 Managing data You can configure alerts, which are sent to your account from the Nasuni Filer. You can select various types of alerts to receive. See Settings on page 247. Managing data Providing data access to users You can define the specific data that users can access. You can also define which users can access data. Note: If this Nasuni Filer is under the control of the Nasuni Management Console, you use the Nasuni Management Console to perform this task. You can create a CIFS share, an NFS export, or an FTP/SFTP directory for each directory in the volume that you want to provide access to. You can create many CIFS shares, NFS exports, or FTP/SFTP directories on a volume. See Adding a New CIFS Share to a Volume on page 101, Adding an NFS Export to a Volume on page 117, and Adding FTP directories for a volume on page 127. If you created a CIFS share, NFS export, or FTP/SFTP directory automatically when you created a new volume, you can check and edit the settings for CIFS shares ( Editing a CIFS Share on page 113), NFS exports ( Editing an NFS Export on page 120), or FTP/SFTP directories ( Editing FTP directories on page 132). For each CIFS share, NFS export, or FTP/SFTP directory, you can define which volume and which directory within the volume to share, export, or FTP. You can specify Read-Only access. You can limit which hosts can access the CIFS share, NFS export, or FTP/SFTP directory. For CIFS shares with Active Directory security, you can define groups that can access the CIFS share, and specify Read-Write, or Read-Only, or Deny access for each group. You can add users to or remove users from these groups. You can also specify individual users that can access the CIFS share, and specify Read-Write, Read-Only, or Deny access for each individual user. You can map network drives to CIFS shares in Windows, access iscsi volumes in Windows, and mount CIFS shares or NFS exports in Linux or UNIX. You can access FTP/SFTP directories using the FTP/SFTP protocol. You can also define multiple protocols to access data using CIFS, NFS, and FTP/SFTP. You can enable Web Access to CIFS shares and NFS exports. This allows users to access data using any supported Web browser. See Web Access on page 150. You can enable and install the Nasuni Desktop Client for CIFS shares. This allows users to access data using a simple interface on their own desktop. See Nasuni Desktop Client on page 167. You can enable Mobile Access to CIFS shares. This enables users to access data using mobile devices, including ios-based devices (such as iphone and ipad) and Android phones. See Nasuni Mobile Access on page 157. You can specify details of the Mobile Service, such as adding another port for Mobile Access, limiting how long users remain authenticated on mobile devices, limiting users to only one Nasuni Filer Administration Guide 7.2 8

23 Managing data mobile device, and limiting the types of mobile devices that can use Mobile Access. See Mobile Access: Configuring on page 236. You can enable, disable, and delete individual licenses for the Mobile Access service. See Mobile Access: Managing access by mobile devices on page 237. Sharing data between Nasuni Filers You share data between Nasuni Filers by using volumes. If you do not already have a volume set up on the source Nasuni Filer, you can create a new volume ( Adding a Volume on page 46). Note: If this Nasuni Filer is under the control of the Nasuni Management Console, you use the Nasuni Management Console to perform this task. Volumes are not shared by default. First, you need to enable Remote Access on the source volume. You can then specify Read/Write or Read Only access for the destination Nasuni Filers. See Remote Access on page 83. After the source volume has Remote Access enabled, you connect the destination Nasuni Filers to the source volume. See Connecting to a Remote Volume on page 51. End users access the data through CIFS shares, NFS exports, or FTP/SFTP directories of the destination volume. You define CIFS shares ( Adding a New CIFS Share to a Volume on page 101), NFS exports ( Adding an NFS Export to a Volume on page 117), or FTP/SFTP directories ( Adding FTP directories for a volume on page 127) on the destination volume for users to access. If you created a CIFS share, NFS export, or FTP/SFTP directory automatically when you created a new volume, you can check and edit the settings for CIFS shares ( Editing a CIFS Share on page 113), NFS exports ( Editing an NFS Export on page 120), or FTP/SFTP directories ( Editing FTP directories on page 132). You can schedule when The Nasuni service syncs (synchronizes) the data between Nasuni Filers. See Configuring a Sync Schedule on page 171. Adding data to volumes There are several ways to add data to volumes. The best way to load your data to a volume is by using the Data Migration Service. This feature supports multiple sources and targets for migrations using CIFS or NFS protocols. See Configure on page 200. You can share data from other Nasuni Filers as described in Sharing data between Nasuni Filers on page 9. You can define Web Access to CIFS shares. This enables users to add data to volumes using any supported Web browser. See Web Access on page 150. Note: If this Nasuni Filer is under the control of the Nasuni Management Console, you use the Nasuni Management Console to perform this task. Nasuni Filer Administration Guide 7.2 9

24 Managing data You can define Mobile Access to CIFS shares. This enables users to add data to volumes using mobile devices, including ios-based devices (such as iphone and ipad) and Android phones. See Nasuni Mobile Access on page 157. Note: If this Nasuni Filer is under the control of the Nasuni Management Console, you use the Nasuni Management Console to perform this task. You can enable and install the Nasuni Desktop Client for CIFS shares. This allows users to access data using a simple interface on their own desktop. See Nasuni Desktop Client on page 167. You can map network drives to CIFS shares in Windows (see Mapping a Windows network drive to a CIFS share on page 143), access iscsi volumes in Windows (see Accessing an iscsi volume in Windows on page 144), and mount CIFS shares or NFS exports in Linux or UNIX (see Mounting a CIFS share in Linux or UNIX on page 147 and Mounting an NFS export in Linux or UNIX on page 149). This enables users to add data to volumes using the file management capabilities of Windows, Linux, and UNIX operating systems. You can access FTP/SFTP directories using the FTP/SFTP protocol. See Accessing data using the FTP/SFTP protocol on page 141. Protecting data A snapshot is a complete picture of the files and folders in your file system at a specific point in time. Snapshots offer data protection by enabling you to recover past versions of a file or to restore an entire file system. You can select when and how frequently to perform snapshots. For example, you can configure snapshots to occur only during off-hours when network usage is low. You can schedule snapshots for whenever suits your system best. See Snapshot Scheduling on page 88. You can also take manual snapshots at any time. See Take a Snapshot Now on page 54. For compliance purposes or your own best practices, you can specify to delete older snapshots from cloud storage, based on a configured snapshot retention policy for a specific volume. See Snapshot Retention on page 94. You can restore a file or folder (for a CIFS or NFS volume, or FTP/SFTP directory) or an entire volume (for an iscsi volume) from any location. See Searching for a Folder or File by Name on page 182 and Restoring Volume, Folder, or Files on page 192. Managing volumes The Nasuni Filer offers many options for managing volumes. Note: If this Nasuni Filer is under the control of the Nasuni Management Console, you use the Nasuni Management Console to perform this task. Volumes should have names that describe what data they contain and that users recognize. You can change the name of a volume. See Volume Status on page 40. You can change the name of an iscsi target. See Volume properties page for iscsi volumes on page 59. Nasuni Filer Administration Guide

25 Security You can monitor file statistics. See File Types in snapshots on page 370, File Sizes in snapshots on page 370, and Data Growth Chart on page 34. For CIFS and NFS volumes and FTP/SFTP directories, the volume quota (maximum capacity) enables you to limit the amount of storage space for a volume, including snapshots, which helps you to control your storage costs. You can change the volume quota. See Changing the Volume Quota on page 65. The Nasuni Filer can also send reports to administrators or to users about which directories are near or over their quota. For details about setting a directory quota, see Setting Quota or Rule on page 186. You can delete volumes that are no longer needed. See Deleting a Volume on page 98. Security Handling encryption keys Encryption keys are used to encrypt your data in cloud storage. You can use the Nasuni Filer to manage encryption keys in several ways. Note: If this Nasuni Filer is under the control of the Nasuni Management Console, you use the Nasuni Management Console to perform this task. You can view encryption keys and their settings. See Encryption Key Management on page 287. Nasuni recommends creating and uploading your own encryption keys. You can upload encryption keys to the Nasuni Filer. See Adding (Importing or Uploading) Encryption Keys on page 289. Alternatively, you can specify generating a new encryption key when you create a new volume. The next step is to add specific encryption keys to specific volumes. See Adding Encryption Keys to a Volume on page 81. The next step is to enable (or disable) specific encryption keys for specific volumes. See Enabling Encryption Keys on page 77 or Disabling Encryption Keys on page 79. Nasuni recommends safeguarding your encryption keys yourself. You can download generated encryption keys for safeguarding. See Downloading (Exporting) Generated Encryption Keys on page 290. Alternatively, you can escrow uploaded encryption keys with Nasuni. See Escrowing Encryption Keys with Nasuni on page 291. Note: All automatically generated encryption keys are automatically escrowed with Nasuni. You can delete encryption keys that are not necessary for disaster recovery purposes. See Deleting Encryption Keys on page 293. Nasuni Filer Administration Guide

26 Changing performance Role-based access control Rather than managing the permissions for performing tasks for each individual user, it is simpler to create groups that have specific combinations of permissions, and then assign users to the appropriate groups. You can define users and groups of users, and then assign specific permissions to each group. To control who has permission to perform actions on the Nasuni Filer, you can define users and groups of users, then assign specific permissions. See Users and Groups on page 315. To control who has permission to access CIFS shares that have Active Directory security, you can define users and groups of users, then assign specific permissions. See Editing a CIFS Share on page 113. SSL certificates The user interface of the Nasuni Filer is Web-based. In order to secure this Web site, SSL certificates or self-signed certificates are used. You can view or add SSL certificates or a self-signed certificate that you can use when accessing the Nasuni Filer user interface. See SSL Certificates on page 301. Note: If this Nasuni Filer is under the control of the Nasuni Management Console, you use the Nasuni Management Console to perform this task. Antivirus protection Nasuni offers the option of protecting data with antivirus scanning, and review of files flagged for violations. Note: If this Nasuni Filer is under the control of the Nasuni Management Console, you use the Nasuni Management Console to perform this task. You can enable or disable the Antivirus Service. See Antivirus Service on page 69. You can review antivirus violations. See Reviewing Infected Files on page 71. Firewall protection You can limit which network hosts are allowed to connect to the Nasuni Filer user interface and the Nasuni Support SSH port, which provides firewall protection. See Firewall on page 294. Changing performance There are a number of ways that you can change the performance of the system. The Quality of Service (QoS) settings specify the inbound and outbound bandwidth for moving data to and from the Nasuni Filer. Snapshots are slower during periods of lower bandwidth. Local user read/write operations are not affected. Limiting the bandwidth of inbound and outbound data between specific hours can help decrease network congestion. See Quality of Service Settings on page 263. Nasuni Filer Administration Guide

27 Changing performance The cache is the local storage of the Nasuni Filer. All data and metadata that are accessed regularly are kept locally in the cache. By default, the amount of local cache space reserved for new writes is managed automatically, using an advanced algorithm to optimize cache usage. However, you can override the amount of local cache space reserved for new writes in order to suit your company s workload. Reserving a large portion of the cache for new writes allows snapshots to complete more rapidly, but reduces the amount of data that is kept locally. Conversely, reserving a small portion of the cache for new writes allows keeping more data locally, but increases the time for completing snapshots. See Cache Settings on page 333. Frequent snapshots increase the system load significantly. You can change when and how frequently snapshots occur. See Snapshot Scheduling on page 88. Pinning a folder forces a folder to remain in the local cache at all times. This can improve performance and reduce the time necessary to return accessed data to clients. See Pinning Folders in the Cache on page 188. Nasuni Filer Administration Guide

28 Alternatives for configuring your Nasuni Filer Alternatives for configuring your Nasuni Filer For many settings on the Nasuni Filer, you can perform the configuration either with the Nasuni Filer user interface or with the Nasuni Management Console. The following tables show which settings you can configure with which user interface. Configuring your Nasuni Filer using the Nasuni Filer user interface Some actions can only be performed using the Nasuni Filer user interface, not with the Nasuni Management Console. Affected item Place Filer in NMC control Data Migrations Data Migration sources Data Migration schedules Network Firewall SSL certificates HTTPS proxy On Nasuni Filer Action: Menu Enable: Services Nasuni Management Console Configure, Delete, View: Services View Migrations Create, Delete, View: Services Migration Sources Schedule, Delete, View: Services Migration Schedules Edit: Configuration Network Configuration Charts, Status: Status Network Status Edit: Configuration Firewall Add, Delete, Set, View: Configuration SSL Certificates Edit: Configuration HTTPS Proxy Edit: Configuration Settings Nasuni Filer Administration Guide

29 Alternatives for configuring your Nasuni Filer Configuring your Nasuni Filer using either the user interface or the NMC Some actions can be performed using either the Nasuni Filer user interface or the Nasuni Management Console. Affected item On Nasuni Filer Action: Menu On Nasuni Management Console Action: Menu Nasuni Filer Operations Manual software Updates: Status Updates Update: Filers Software Update update Subscription status View, Refresh: Status Subscription Status Refresh: Account Status Refresh License Send diagnostics Send: Services Send Diagnostics Send: Filers Send Diagnostics to Nasuni Shutdown Power: Power button Shutdown: Filers Shutdown & Reboot Folder Operations Auto cache Enable: File Browser select folder Enable: Volumes File System Browser select folder Pinning folder Pin folder: File Browser select volume Enable: Volumes File System Browser select folder Volume Operations Take snapshot now Take: Volumes All Volumes Take: Volumes Take Snapshot Antivirus violations Review: Volumes select volume Review: Volumes Antivirus Violations File Browse, Download, Search, Restore, Bring Volumes File Browser into cache: File Browser select volume Folder Browse, Search, Restore, Bring into cache: Volumes File Browser File Browser select volume Directory quotas Create: File Browser; Edit: Volumes Volumes File Browser Properties Quotas Nasuni Filer Configuration Place Filer in NMC Enable: Services Nasuni Management View List: Filers control Console Mobile Access Enable: Volumes Mobile Service Settings Manage: Services Mobile Licenses Enable: Filers Mobile Settings Manage: Filers Mobile Licenses Remote Support Enable: Services Remote Support Service Enable: Filers Remote Support Service Active Directory Join: Configuration General Settings View: Filers Security Settings domain Join, Leave, Edit, View: Configuration Domain Settings Time Zone, Server Edit: Configuration Time Configuration Edit: Filers Time Configuration Cache Edit: Configuration Cache Settings Edit: Filers Cache Settings Encryption Keys Upload, Download, Escrow, Delete, View: Configuration Encryption Keys Upload, Send, Escrow, Delete, View: Filers Encryption Keys Automatic Software Edit: Configuration Automatic Updates Edit: Filers Automatic Updates Updates Quality of Service Edit: Configuration Quality of Service Edit: Filers Quality of Service Nasuni Filer Administration Guide

30 Alternatives for configuring your Nasuni Filer Affected item On Nasuni Filer On Nasuni Management Console Action: Menu Action: Menu Users and Groups Add, Delete, Edit: Configuration Users/ Groups Add, Delete, Edit: Console Settings Users/Groups Description Edit: Configuration Filer Description Edit: Filers Description Password Edit: Configuration Change Password Edit: Console Settings Users/ Groups Edit User Volume Configuration Volume Create, Delete, Connect, Disconnect, Edit, Rename: Volumes All Volumes select volume Browse: File Browser select volume Create, Delete, Connect, Disconnect, Rename: Volumes Nasuni Filer Administration Guide

31 Alternatives for configuring your Nasuni Filer Encryption Keys (Volume) CIFS share NFS export iscsi FTP directory Quota Affected item On Nasuni Filer Action: Menu Add, Enable: Volumes select volume Create, Delete, Edit: Volumes select volume Disconnect client, Reset authentication cache, Reset clients: Status CIFS Status Create, Delete, Edit: Volumes select volume Status: Status NFS Status Edit: Volumes select volume Status: Status iscsi Status Create, Delete, Edit: Volumes select volume Status: Status FTP Status Edit: Volumes select volume Report: Configuration Quota Settings On Nasuni Management Console Action: Menu Add, Enable: Volumes Encryption Keys Create, Delete, Edit, Status: Volumes Shares Status: Filers CIFS Create, Delete, Edit: Volumes Exports Status: Filers NFS Edit: Volumes iscsi Status: Filers iscsi Create, Delete, Edit: Volumes FTP Directories Status: Filers FTP Edit: Volumes Quota Report: Filers Quota Reports Auto cache Enable: Volumes select volume Enable: Volumes Sync Schedule Remote Access Enable: Volumes select volume Enable: Volumes Remote Access Sync scheduling Edit sync schedule, Edit snapshot schedule, Edit: Volumes Snapshot Edit snapshot retention: Volumes select scheduling volume Snapshot retention Snapshot directory access File Alert Service Antivirus Service Filer Monitoring Enable snapshot directory access, Enable file alert service, Enable antivirus service: Volumes select volume Enable: Volumes SNMP monitoring Enable: Configuration SNMP monitoring Edit: Filers SNMP Settings Hardware appliance status Status: Status Hardware Status View: Home Hardware Health View: Filers Hardware Traffic groups View: Status Network Status View: Filers Network Network Physical ports File information Chart: Status File Heuristics Chart, Table: Home File Types Written, File Sizes in Snapshots Notifications Filter, Acknowledge, Delete: Notifications Search, Acknowledge, Delete: Notifications Volume Monitoring Size Data not yet Status, Chart: Home Status, Chart: Volumes protected Data growth Snapshot status View: Home View: Volumes select volume View: Volumes Last Snapshot Nasuni Filer Administration Guide

32 Alternatives for configuring your Nasuni Filer Configuring the Nasuni Management Console Some actions can only be performed using the Nasuni Management Console, not with the Nasuni Filer user interface. Affected item Manual software update Send diagnostics to Nasuni Time Zone, Time Server Network Firewall HTTPS proxy SSL certificates Users and Groups Automatic Software Updates Remote Support Service Description Password SNMP monitoring Notifications On Nasuni Management Console Action: Menu Update: Console Settings Software Update Send: Console Settings Send Diagnostics Edit: Console Settings Time Configuration Edit: Console Settings Networking Edit: Console Settings Firewall Edit: Console Settings Proxy Add, Delete, View: Console Settings SSL Certificates Add, Delete, Edit, View: Console Settings Users / Groups Edit: Console Settings Automatic Updates Edit: Console Settings Remote Support Edit: Console Settings Description Edit: user Change Password Edit: Console Settings Settings Edit: Console Settings SNMP Monitoring Search, Acknowledge, Delete: Notifications Nasuni Filer Administration Guide

33 Chapter 3: Login Page When you open the Nasuni Filer user interface in a Web browser, the Login page appears, where you can log in securely using your username and password. Accounts for the administrative management of the Nasuni Filer are called Filer Administrators. Supported Web browsers include Mozilla Firefox, Internet Explorer, Apple Safari, and Google Chrome. See the Nasuni Filer Initial Configuration Guide for a current list of supported Web browsers. At the top of the Login page, you can access online help. See Help on page 22 for details. You can also shut down the Nasuni Filer, if necessary. See Power on page 22 for details. Figure 3-1: Nasuni Filer Log in page. At the bottom of the Login page is a link to the Nasuni corporate Web site. There is also a link to use if you have lost the login password. See Resetting Administrative Account (Forgot Password) on page 21 for details. Nasuni Filer Administration Guide

34 Logging in to the Nasuni Filer Logging in to the Nasuni Filer To log in to the Nasuni Filer: 1. Using your Web browser, open the specified IP address for the Nasuni Filer. The IP address is obtained during installation. For hardware appliances, see the appropriate Hardware Appliance Getting Started Guide. For virtual platforms, see the Nasuni Filer Virtualization Getting Started Guide. The Nasuni Filer Log in page appears. Figure 3-2: Nasuni Filer Log in page. 2. Type your username (case-sensitive) in the Username text box. Note: If you have associated an Active Directory domain group with a permission group, you can log in using Active Directory credentials. See Adding Permission Groups on page Type your password (case-sensitive) in the Password text box. Warning: Performing too many unsuccessful login attempts disables login for 5 minutes. If this happens, wait 5 minutes, then log in with the correct username and password. 4. Click Log in. After you log in, the Nasuni Filer Home page appears. See Home Page on page 32 for details on the features of this page. After you log in, you can change the password, as detailed in Changing User Password on page 336. Nasuni Filer Administration Guide

35 Resetting Administrative Account (Forgot Password) You can begin using the Nasuni Filer immediately to map a network drive as explained in Mapping a Windows network drive to a CIFS share on page 143. You can also mount a CIFS share, as explained in Mounting a CIFS share in Linux or UNIX on page 147. You can also mount an NFS export, as explained in Mounting an NFS export in Linux or UNIX on page 149. Note: If you already have a Nasuni Filer, and this is another Nasuni Filer associated with your account, you must create a volume and CIFS share before you can map a drive. See Chapter 6, Volumes Page, on page 41 for details. You can access FTP/SFTP directories using the FTP protocol. See Accessing data using the FTP/SFTP protocol on page 141. Resetting Administrative Account (Forgot Password) If you have lost the password for the administrative account, this feature resets the administrative account information for this Nasuni Filer, and allows you to create or recreate a Filer Administrator user. No data is deleted and no configurations are changed. After logging in, you can change your password, as detailed in Changing User Password on page 336. Important: For this procedure, you need the Serial Number and Authorization Code for this Nasuni Filer, found under the Account section of or on the Account Status page of the Nasuni Management Console. Note: This procedure does not deauthorize the Nasuni.com account, just the Nasuni Filer administrative account, which is independent of the Nasuni.com account and specific to the Nasuni Filer. Caution: Do not use this process to change between Nasuni.com accounts. To reset the administrative account: 1. Locate the Forgot Password? hyperlink at the bottom of the Login page. 2. Click the hyperlink. The Administrative Account Reset page appears. Figure 3-3: Administrative Account Reset page. Nasuni Filer Administration Guide

36 Navigation Bar on Login Page 3. To proceed, select the Click here to Accept check box. This means that you acknowledge that this Nasuni Filer is to be de-authorized from the account. The Nasuni Filer requires re-activation through the setup wizard. 4. Click Confirm. The registration wizard appears. Note: To exit this screen without resetting the account, click your Web browser s Back button. 5. To re-register and re-create the Filer Administrator for this Nasuni Filer with another username and password, see Setting Up the Nasuni Filer in the Nasuni Filer Initial Configuration Guide. This lets the Filer Administrator log in to the Nasuni Filer user interface. Navigation Bar on Login Page The navigation bar on the Login screen displays the following options: Help. Power. Help Click Help to display the Help menu. Links to the following information are available: Nasuni Filer documentation in PDF format. See Product Documentation on page xiii. Nasuni Filer Release Notes. See Viewing the Nasuni Filer Release Notes on page 25. Nasuni Terms of Service. See Nasuni Terms of Service and License Agreement on page 384. Privacy policy. Service Level Agreement. Contact Nasuni support and sales. Power To shut down the Nasuni Filer, click Power on page 27 for details.. See Shutting Down and Rebooting the Nasuni Filer Nasuni Filer Administration Guide

37 Chapter 4: Common Screen Elements Several useful elements appear on all pages of the Nasuni Filer user interface. Nasuni Corporate Web Site At the bottom of each page is a link to the Nasuni corporate Web site. Figure 4-1: Link to the Nasuni corporate Web site. Status Messages Status messages, such as when the last snapshot occurred, appear on the bottom left of each page. Figure 4-2: Status message. Username In the navigation bar at the top of all pages, the name of the user who is logged in appears with the date of the last login. Figure 4-3: Username logged in. Name of the Nasuni Filer The name of the Nasuni Filer appears in the upper left, under the Nasuni logo. Figure 4-4: Name of Nasuni Filer. Nasuni Filer Administration Guide

38 Navigation Bar Functions Navigation Bar Functions The navigation bar of the Nasuni Filer user interface displays the following useful options: Notifications. Help. Power. Viewing Notifications Urgent notifications that require acknowledgment appear on the Notifications pane. You can view and filter all notifications using the Notifications pane. To view notifications, click the megaphone-shaped Notifications icon at the top right of any page. The Notifications pane appears. Figure 4-5: Notifications pane. Urgent notifications that require acknowledgment appear on the Notifications pane, based on the state of your system. A number to the right of a notification indicates multiple occurrences of the same notification. You can acknowledge a notification by clicking the x. To acknowledge all the urgent notifications, click Acknowledge All. For more information about Notifications, see Chapter 13, Notifications, on page 371. Viewing the Nasuni Filer Help The Nasuni Filer Help is available on the navigation bar at the top of all pages. Click Help to display the Help menu. Links to the following information are available: Nasuni Filer documentation in PDF format. See Product Documentation on page xiii. Nasuni Filer Release Notes. See Viewing the Nasuni Filer Release Notes on page 25. Nasuni Terms of Service. See Nasuni Terms of Service and License Agreement on page 384. Privacy policy. Service Level Agreement. Contact information for Nasuni support and sales. Nasuni Filer Administration Guide

39 Navigation Bar Functions Viewing the Nasuni Filer Release Notes The Release Notes option is available by clicking Help on the navigation bar at the top of all pages. Release Notes for the Nasuni Filer contain the latest information about the latest version, as well as previous versions. Tip: To automatically download and install software updates, see Automatic Software Updates on page 332. To manually update the Nasuni Filer software, see Software Updates on page 340. To view release notes: 1. Click Help on the navigation bar at the top of the page, then select Release Notes from the list. The Release Notes dialog box appears with the latest release notes. Figure 4-6: Release Notes dialog box. 2. Scroll down to review information about the Nasuni Filer software release. Nasuni Filer Administration Guide

40 Navigation Bar Functions 3. To close the release notes dialog box, press the Esc key or click the x at the top of the dialog box. Note: To ensure that you see the latest release notes, reload the page or refresh your browser s cache. Nasuni Filer Administration Guide

41 Navigation Bar Functions Shutting Down and Rebooting the Nasuni Filer The Power (or Shutdown) option is located on the navigation bar at the top of all pages. When you shut down the Nasuni Filer, all users are disconnected from the Nasuni Filer and data is not accessible during the shutdown process. You can choose to shut down the Nasuni Filer immediately, or to perform a snapshot before shutting down. Tip: Consider performing a snapshot before shutting down the Nasuni Filer. See Take a Snapshot Now on page 54 for details. To shut down the Nasuni Filer: 1. Click Power on the navigation bar at the top of the page. The Shutdown Filer dialog box appears. Figure 4-7: Shutdown Filer dialog box. Note: To exit and return to the previous page, click the x at the top of the page, or click Cancel. 2. Enter a Username (case-sensitive) and Password (case-sensitive) that has permission to perform this operation. 3. Select one of the following options: Perform snapshot before shutting down: The Nasuni Filer performs a snapshot before shutting down. This ensures that data is fully protected in cloud storage before shutting down. However, this process can take considerable time, depending on the size of the cache and the amount of changed and new data in the cache. Tip: On the Windows Azure virtual platform, virtual machines that have been shut down continue to incur compute charges. To avoid these charges, use the Windows Azure Management Portal at to stop or delete the virtual machines. Nasuni Filer Administration Guide

42 Navigation Bar Functions Shut down immediately: (Default) Shuts down the Nasuni Filer without performing a snapshot. Data that has not already been captured by a snapshot is not protected in cloud storage. However, data in the cache is not lost. A message on the Nasuni Filer Home page notifies you that the Nasuni Filer is shutting down. If you change your mind, you have 60 seconds to cancel the shutdown. Tip: On the Windows Azure virtual platform, virtual machines that have been shut down continue to incur compute charges. To avoid these charges, use the Windows Azure Management Portal at to stop or delete the virtual machines. Reboot immediately: Reboots the Nasuni Filer without performing a snapshot. In a few moments, the console reloads and the Nasuni Filer Home page re-appears. Note: On a high availability hardware appliance Nasuni Filer, rebooting this node triggers a failover to the other high availability node, if that node is online. Reboot and perform a filesystem check: Reboots the Nasuni Filer and forces a file system check (fsck) on the cache disk when the Nasuni Filer reboots. 4. Click Shutdown. Note: On a high availability hardware appliance Nasuni Filer, rebooting this node triggers a failover to the other high availability node, if that node is online. Note: File system checks (using fsck) are necessary at least every six months. However, a file system check might take hours to complete (depending on the size of the cache) and might interfere with normal operations. To determine if a file system check is actually necessary, the Nasuni Filer periodically performs a background test. If this background test determines that a file system check is not necessary, the next file system check is postponed for another six months. However, if the background test determines that a file system check is necessary, you receive an alert suggesting that you perform a reboot and a file system check. This allows you to select a time for performing a reboot with a file system check that does not interfere with normal operations. Even if you don t receive such an alert, you can choose to perform a reboot with a file system check, for example, if you want to proactively verify the integrity of the cache, such as after an unexpected power loss. Tip: If your Nasuni Filer is a Nasuni Filer hardware appliance or runs in a VMware ESXi environment or Microsoft Hyper-V environment, you can also force a file system check (fsck) by holding down the Shift key during a reboot. When the file system check (fsck) is done, the usual processing continues. The message The Nasuni Filer is shutting down. appears. 5. To stop the shutdown, click the hyperlink marked click here to cancel the shutdown. You have 60 seconds to cancel the shutdown. The message Shutdown cancelled at user request. appears. The shutdown stops. Nasuni Filer Administration Guide

43 Navigation Bar Functions 6. If you do not stop the process, the Nasuni Filer shuts down or reboots, depending on the option chosen in step 3, and the Nasuni Filer user interface is no longer accessible. On the console, a series of shutdown messages appears, and the console automatically closes down. To restart a shutdown Nasuni Filer, you can power on the Nasuni Filer from your platform. Logging Out of the Nasuni Filer The Logout option is available by clicking the user name on the navigation bar at the top of all pages. Logging out of the Nasuni Filer does not affect any operations such as snapshots or file sharing access. To log out of the Nasuni Filer: 1. Click the user name on the navigation bar at the top of the page, then click Logout from the drop-down list. You are logged out of the Nasuni Filer. Figure 4-8: Logout. 2. The Login page appears. You can log back in when needed, as detailed in Logging in to the Nasuni Filer on page 20. Changing User Password You can change the currently logged-in user account password to a new password. Note: This option is not available if you log in using Active Directory credentials. To change the user account password: 1. Click the user name at the top of the page, then select Change Password from the drop-down list. The Change User Password page appears. Figure 4-9: Change User Password page. Nasuni Filer Administration Guide

44 Pop-up Software Update Notifications 2. Enter your current password (case-sensitive) in the Old password text box. 3. Enter the new password (case-sensitive) for your user account in the New password text box. 4. Enter the new password (case-sensitive) again in the Confirm new password text box. 5. Click Save New Password. You are taken to the Home page, where the message Password successfully changed is displayed. Note: If this Nasuni Filer is under the control of the Nasuni Management Console, changes to the password are propagated to the Nasuni Management Console. Pop-up Software Update Notifications If a new software update is available, a pop-up notification appears in the right margin. For example: Figure 4-10: Software update notification. You can acknowledge this notification by clicking the x. To delete notifications, see Deleting Notifications on page 374. You can update the Nasuni Filer software from the hyperlink. See Software Updates on page 340 for more details. Note: Nasuni does not recommend applying software updates during your normal business hours, because this can disrupt access. Apply software updates during off-hours. Notifications You can access notifications using the megaphone-shaped Notifications icon at the top right. Figure 4-11: Notifications icon. A number on the Notifications icon indicates the number of new, unacknowledged, urgent notifications that require acknowledgment. Figure 4-12: Number of new notifications. Nasuni Filer Administration Guide

45 Nasuni Management Console message and notice To view notifications, click the Notifications icon. The Notifications pane appears. Figure 4-13: Notifications pane. Urgent notifications that require acknowledgment appear on the Notifications pane, based on the state of your system. A number to the right of a notification indicates multiple occurrences of the same notification. You can acknowledge a notification by clicking the x. To acknowledge all the urgent notifications, click Acknowledge All. To view all notifications, click View all Notifications. For details on notifications, see Chapter 13, Notifications, on page 371. Nasuni Management Console message and notice If this Nasuni Filer is under Nasuni Management Console control, a message appears at the top of the page. Figure 4-14: Nasuni Management Console message. In addition, a notice appears on the menu bar at the upper right of the page: Figure 4-15: Nasuni Management Console notice. You can disable Nasuni Management Console control by clicking the Nasuni Management Console hyperlink. See Nasuni Management Console on page 243 for more details. Note: If this Nasuni Filer is under the control of the Nasuni Management Console, for many tasks you use the Nasuni Management Console to view information or perform actions. For details, see the Nasuni Management Console Guide. Nasuni Filer Administration Guide

46 Chapter 5: Home Page Home The Home page appears after you log in to the Nasuni Filer. The Home page displays a dashboard with details about the state of the Nasuni Filer. The Home page offers links to the Volumes, File Browser, Services, Configuration, Status, and Notifications pages. The Home page displays the following information for the Nasuni Filer: Messages, including alerts, notifications, and available software updates. Data Growth chart. New Data in Cache chart. Network Activity charts. Migration Status information. Snapshot Status information. Local Cache Status graphic. Quality of Service (inbound and outbound bandwidth) information. Volume Status information. Note: The Home page, and all other pages of the Nasuni Filer user interface, might look different to different users. Also, different menus and actions might be available for different users. This is because different users are assigned different permissions, based on their roles in the role-based access control system. See Users and Groups on page 315 for details. Note: If this Nasuni Filer is under the control of the Nasuni Management Console, menus and menu choices might look different, because you use the Nasuni Management Console to perform these tasks. Nasuni Filer Administration Guide

47 The Nasuni Filer Home page looks like this. Figure 5-1: Home page. You can return to the Home page by clicking the name of the Nasuni Filer in the top left corner. Nasuni Filer Administration Guide

48 Data Growth Chart Data Growth Chart Chart A chart of Data Growth appears at the top of the Home page. Figure 5-2: Data Growth chart. This chart shows the total amount of stored data on the vertical axis versus time along the horizontal axis. The amount of data is shown in units such as KB, MB, GB, and TB. The length of time is shown by month and day. The data growth updates automatically every 5 minutes. You can use the Data Growth chart to monitor the amount of data stored using this Nasuni Filer, and to determine how much data each volume contributes to the total. You can select the time period of this chart by clicking the drop-down list and selecting one of the following time periods: Previous 7 days. Previous 14 days. Previous 30 days. Previous 90 days. All time. You can select which volumes to include or exclude by clicking the available volume names under the chart. If you hover the mouse over any part of the chart, a label appears displaying details about the amount of data in that volume at that date and time. Figure 5-3: Details of data and time on Data Growth chart. To zoom in on a specific range of displayed data, click the chart at the high end of the range you want, then drag to the low end of the range you want, then release. The chart rescales to zoom in on the selected range. To reset the zoom to the default display, click Reset zoom. Nasuni Filer Administration Guide

49 New Data in Cache Chart New Data in Cache Chart A chart of New Data in Cache (not yet protected) appears in the middle of the Home page. Figure 5-4: New Data in Cache chart. This is a bar chart showing the amount of new data in the cache that has not yet been protected in cloud storage. Each volume appears on the vertical axis on the left side. The amount of data for each volume appears as a horizontal bar. If all the data for a volume has already been protected in cloud storage, there is no bar for that volume. You can use this chart to monitor how much data is present in the cache that has not yet been protected in cloud storage. This can be helpful when planning snapshot schedules (see Snapshot Scheduling on page 88) or manually taking snapshots (see Take a Snapshot Now on page 54). If there are any antivirus violations that are not yet protected, the total of antivirus violations is displayed. Nasuni Filer Administration Guide

50 Network Activity Charts Network Activity Charts You can view charts of the network activity of the Nasuni Filer. One chart shows data transmitted to and received from cloud storage. The other chart shows other network traffic to and from the Nasuni Filer. The scale is in Kbits/second or Mbits/second, depending on throughput. There is a chart of Cloud Traffic (upper chart) and a chart of Local Traffic (lower chart). Figure 5-5: Network Activity charts. You can use these charts to monitor network activity during data transfer. Both charts have the same vertical scale. You can select the time period of these charts by clicking the drop-down list and selecting one of the following time periods: Previous Hour. Previous Day. On the Cloud Traffic chart (upper chart), you can select which network activity to include or exclude by clicking Cloud Transmit (for data transmitted to the cloud by the Nasuni Filer), Cloud Receive (for data received from the cloud by the Nasuni Filer), Mobile Transmit (for data transmitted to mobile devices by the Nasuni Filer), or Mobile Receive (for data received from mobile devices by the Nasuni Filer) under the Cloud Traffic chart. On the Local Traffic chart (lower chart), you can select which network activity to include or exclude by clicking UI Transmit (for data transmitted to the user interface by the Nasuni Filer), UI Receive (for data received from the user interface by the Nasuni Filer), Client Transmit (for data transmitted to the client by the Nasuni Filer), Client Receive (for data received from the client by the Nasuni Filer), Migration Transmit (for data transmitted to a data migration by the Nasuni Filer), or Migration Receive (for data received from a data migration by the Nasuni Filer) under the Local Traffic chart. To zoom in on a specific range of displayed data, click the chart at the high end of the range you want, then drag to the low end of the range you want, then release. The chart rescales to zoom in on the selected range. To reset the zoom to the default display, click Reset zoom. Nasuni Filer Administration Guide

51 Network Activity Charts If you hover the mouse over any part of either chart, a label appears displaying details about the amount of network activity at that date and time. Figure 5-6: Details of network activity on Network Activity charts. Nasuni Filer Administration Guide

52 Migration Status Migration Status The status of data migration activities appears at the top of the right-hand column. Figure 5-7: Migration Status. The migration status includes the name of the migration, the target volume, the time and date of the last run, and the status of the migration. To view details of a migration, start or stop a migration, download a log of a migration, or perform other migration activities, click the Migration link or the Settings icon. See Data Migration on page 200 for more details. Snapshot Status View The status of the most recent snapshot appears in the right-hand column. If the snapshot is in progress, a bar chart of the progress appears: Figure 5-8: Snapshot Status when snapshot is in progress. This shows the percentage complete, the total size, and the volume name of the snapshot. If the snapshot is complete, the status of the snapshot appears, including the volume name and the date and time that the snapshot completed: To view details of the volume, click the highlighted volume name in the status. By default, snapshots of unshared volumes occur hourly (every 5 minutes for shared volumes). If the default interval is not suitable, see Snapshot Scheduling on page 88 for details on how to change the snapshot interval. Nasuni Filer Administration Guide

53 Local Cache Status Local Cache Status The status of local storage, namely, the cache, appears in the middle of the right column of the Home page. Figure 5-9: Local Cache Status. The cache status includes a bar chart indicating how much of the cache is in use, the percentage of the cache in use, and the total size of the cache. See About the Cache on page 4 for details on how the cache works in the Nasuni Filer. See Cache Settings on page 333 for information on configuring the cache. If the RAID array is in the process of being rebuilt, a bar chart indicates how much of the RAID array has been rebuilt. Quality of Service (inbound and outbound bandwidth limit) The Quality of Service (QoS) settings indicate the inbound and outbound bandwidth limit of moving data to and from the Nasuni Filer, such as for transmitting snapshots to cloud storage. The current Quality of Service appears in the right column of the Home page. Figure 5-10: Quality of Service. By default, the outbound bandwidth limit for snapshots is 2 megabits per second. However, you can schedule rules for different Quality of Service (QoS) settings on different days and times by clicking the link or the Settings icon. You can also create additional Quality of Service (QoS) rules. See Quality of Service Settings on page 263 for details on adding or changing QoS rules. Nasuni Filer Administration Guide

54 Volume Status Volume Status Status The status of each volume appears on the bottom of the right column of the Home page. Figure 5-11: Volume Status. For each volume, the name of the volume, the size of the volume, and the date and time of the last snapshot appear. You can view details about each volume by clicking the link of each volume name. To view a list of volumes, click the Settings icon. Local Time Status Status You can synchronize the local clock with the configured Network Time Protocol (NTP) server. By default, all Nasuni Filers are set to use Nasuni's NTP server, time.nasuni.com, to set the time daily. To synchronize with the NTP server, click Sync clock with NTP. Figure 5-12: Local Time Status. To configure the NTP server, see Filer Time Configuration on page 268. Nasuni Filer Administration Guide

55 Chapter 6: Volumes Page Volumes From the Volumes page, you can perform the following activities: View the information and properties of local and remote volumes. Add new volumes using the CIFS, NFS, or iscsi protocols. Connect to remote volumes. Initiate a snapshot. Select the Volume Properties page for a volume. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. Note: The Volumes page, and all other pages of the Nasuni Filer user interface, might look different to different users. Also, different menus and actions might be available for different users. This is because different users are assigned different permissions, based on their roles in the role-based access control system. See Users and Groups on page 315 for details. On the Volume Properties page of each volume, you can perform the following activities (see Viewing Volume Properties on page 55): Change the properties of volumes, including volume name and quota (maximum capacity). Create and change CIFS shares, NFS exports, and FTP/SFTP directories. Configure snapshot retention and scheduling. Enable and disable access to snapshot directories. Add, disable, and enable encryption keys for volumes. Configure iscsi security. Configure remote access to volumes. Configure sync schedules. Configure file auditing for the volume. Configure alerts for files with specified name patterns. Configure antivirus protection. Delete a volume. Nasuni Filer Administration Guide

56 Viewing Local and Remote Volume Information Viewing Local and Remote Volume Information Click Volumes, then select All Volumes from the list. The Volumes page displays the following information for all local and remote volumes. Figure 6-1: Volumes page. Note: It can take several minutes for recently published volumes to appear. To refresh the display, click Refresh Connections. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. Nasuni Filer Administration Guide

57 Viewing Local and Remote Volume Information Local Volume Information The following properties appear for each local volume: Name: The name of the volume. You can change this name to something more useful or descriptive, if needed. See Renaming a Volume on page 62 for details. Size (or LUN Size for iscsi volumes): The amount of storage used for the volume, not including snapshots. Protocol: The protocol or protocols of the volume: CIFS, NFS, or iscsi, or a combination of CIFS, NFS, and FTP. Total Shares (CIFS), Total Exports (NFS), or Total FTP Directories (FTP): For CIFS volumes, the total number of CIFS shares. For NFS volumes, the total number of NFS exports. For FTP/ SFTP directories, the total number of FTP/SFTP directories. Volume Pinned: Indicates whether the entire volume, namely, the root folder of the volume, is pinned in the cache: Yes or No. You can pin the volume, or individual folders, to the cache as detailed in Pinning Folders in the Cache on page 188. Remote Access: For CIFS and NFS volumes and FTP/SFTP directories, the setting of remote access to this volume: Enabled or Disabled. New Data in Cache: The amount of new data that has been saved to the cache, but has not yet been protected in cloud storage. View Last Snapshot: Date and time of last snapshot, or No snapshots if there are no snapshots. Remotely accessible volumes are labeled Remotely Accessible Volume. A remotely accessible volume is available remotely for other Nasuni Filers in your Nasuni.com account. To display and change the properties of the remotely accessible volume, click Edit Properties, then click Enabled next to Remote Access. The Remote Access page for that volume appears. See Remote Access on page 83 for more details. Note: iscsi volumes are never remotely accessible. Volumes that are not remotely accessible are labeled Local Volume. A local volume is available locally and is not enabled for remote access. To display and change the properties of the local volume, click Edit Properties, then click Disabled next to Remote Access. The Remote Access page for that volume appears. See Remote Access on page 83 for more details. Remote Volume Information Remote access allows one or more Nasuni Filers to connect, using the Nasuni Service, to a volume associated with another Nasuni Filer. To connect to a remote volume, see Connecting to a Remote Volume on page 51. The following properties appear for each remote volume that is not connected: Name: The name of the remote volume. Connected: Whether this volume is connected: False. Permissions: The current permissions for the remote volume: Read Only or Read/Write. Nasuni Filer Administration Guide

58 Viewing Local and Remote Volume Information Made accessible from: The name of the remote Nasuni Filer where this remote volume is located. The following properties appear for each connected remote volume: Local Name: The local name of the remote volume. Size: The amount of storage used by the remote volume, not including snapshots. Protocol: The protocol or protocols of the remote volume: CIFS or NFS, or a combination of CIFS, NFS, and FTP. Total Shares (CIFS), Total Exports (NFS), or Total FTP Directories (FTP): For remote CIFS volumes, the total number of CIFS shares. For remote NFS volumes, the total number of NFS exports. For remote FTP/SFTP directories, the total number of FTP/SFTP directories. Volume Pinned: Indicates whether the entire volume, namely, the root folder of the volume, is pinned in the cache: Yes or No. You can pin the volume, or individual folders, to the cache as detailed in Pinning Folders in the Cache on page 188. Connected: Whether this volume is connected: True. Permissions: The current permissions for the remote volume: Read Only or Read/Write. Made accessible from: The name of the remote Nasuni Filer where this remote volume is located. New Data in Cache: The amount of new data that has been saved to the remote volume s cache, but has not yet been protected in cloud storage. Last Snapshot: Date and time of last snapshot of the remote volume, or No snapshots if there are no snapshots. Nasuni Filer Administration Guide

59 Managing Volumes Managing Volumes This section describes various aspects of managing volumes. Default Volume When you install the first Nasuni Filer associated with an account, a single default volume (named files ) with an associated shared folder is created. By default, this volume is created using the CIFS protocol. The default volume is configured with the Public authentication mode by default, which means that all users and groups within your network can store and retrieve data on the volume. Tip: Make sure that you download and protect the encryption key for the default volume, in case you need it for disaster recovery or other purposes later. See Downloading (Exporting) Generated Encryption Keys on page 290 for more details. Tip: You can create volumes with CIFS, NFS, or iscsi protocols. Default CIFS share An associated default CIFS share (also named files ) is also created for the default CIFS volume. All users and groups within your network can store and retrieve data from this folder on the volume. Users can map it as a network drive (see Mapping a Windows network drive to a CIFS share on page 143) or mount it (see Mounting a CIFS share in Linux or UNIX on page 147). Nasuni Filer Administration Guide

60 Managing Volumes Adding a Volume Create This section explains how to add a new CIFS, NFS, or iscsi volume. Note: In Trial Mode, the maximum number of volumes you can have is limited to two. See for a worksheet for planning configurations. To add a new CIFS, NFS, or iscsi volume, follow these steps: 1. Click Volumes, then click All Volumes from the list. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. 2. Click Add New Volume. The Add New Volume page appears. Figure 6-2: Add New Volume page. 3. Enter a human-readable name for the volume in the Name text box, for example, New York Office. The name you enter is automatically applied as the encryption key name in the Keyname text box. Note: For iscsi volumes, the iscsi volume name is used to generate the target name. This includes changing any upper-case letters to lower-case, and changing any non- ASCII symbols to their hex code. Nasuni Filer Administration Guide

61 Managing Volumes 4. From the Region drop-down list, specify a region where you want to store your data. You should store your data in a region that is near your users and data centers to reduce data access latencies. In addition, the region you select should be remote from your other operations for geographic redundancy and disaster recovery purposes. You should also consider any compliance requirements for the location of data. Note: Regardless of which region you choose, your data is protected with multiple copies in that region. 5. You can use an existing encryption key, create a new encryption key, or upload an encryption key. To use an existing encryption key, select an encryption key from the Key drop-down list. To create a new encryption key, select Create New Key from the Key drop-down list, then optionally enter a name for the new encryption key in the Keyname text box. Note: If you select Create New Key, the new encryption key is automatically escrowed for you. It is also prudent to download and protect the new encryption key, in case you need it for disaster recovery or other purposes later. See Downloading (Exporting) Generated Encryption Keys on page 290 for more details. To upload an encryption key, follow these steps: a. Select Upload New Key from the Key drop-down list. The Import OpenPGP Key(s) page appears. Figure 6-3: Import OpenPGP Key(s) page. b. Click Choose File, then navigate to the encryption key file. This file should be OpenPGP compatible. c. If an encryption key passphrase is needed, enter the encryption key passphrase in the Key Passphrase text box. d. Click Import Key. The encryption key is imported to the Nasuni Filer. Tip: Imported encryption keys are not automatically escrowed. Save all imported encryption keys to another secure location outside the Nasuni Filer, so that they are available if needed for disaster recovery. Nasuni Filer Administration Guide

62 Managing Volumes 6. From the Network Protocol drop-down list, select a network protocol on your network. This is the protocol you use to access files on a volume. Your choices are: CIFS (Windows clients): This protocol allows Windows users to share files across a network. The CIFS protocol is used on other operating systems besides Windows, including UNIX, Linux, and Mac OSX. NFS (Unix clients): This protocol allows UNIX users to access and share file systems across a computer network using UNIX and Linux. iscsi Target: This protocol allows users to access SAN blocks of data across a computer network using the iscsi protocol. Note: You can enable FTP/SFTP access to a CIFS volume or an NFS volume after the volume is created. See Multiple Volume Protocols on page For CIFS and NFS volumes only, set the maximum volume capacity (in gigabytes) in the Quota text box. A value of 0 or blank specifies an unlimited volume capacity (up to your licensed capacity). Quotas are applied after each successful snapshot. Nasuni recommends that you only increase quotas rather than decrease them. A notification occurs when the volume reaches 90 percent of the quota. Another notification occurs when the volume reaches the quota. If the volume is shared, then the quota is compared to the sum of all Nasuni Filers connected to the volume. 8. For CIFS and NFS volumes only, to automatically create a CIFS share or an NFS export for the new volume, leave the Create a default Share/Export check box selected. 9. For iscsi volumes only, the iscsi Properties pane appears: Figure 6-4: iscsi Properties pane. a. In the Volume Size text box, enter the Volume Size, in GB. Note: All iscsi (SAN) volume data is pinned in the cache. Therefore, the Volume Size of an iscsi volume is limited by the size of the cache. iscsi volumes can use up to 75 percent of the cache. The computed limit is displayed. Note: The Volume Size of an iscsi volume can be increased, if necessary, but not decreased. Nasuni Filer Administration Guide

63 Managing Volumes b. To control which hosts are allowed to connect to this volume, in the Allowed Hosts text box, enter a comma-separated list of the IP addresses or subnet addresses that are allowed to access this volume. If you leave this field blank, all hosts on your network have access to this volume without restrictions. c. To restrict access to this iscsi volume, in the CHAP User Name text box, enter a Challenge- Handshake Authentication Protocol (CHAP) User Name that initiators must log in with. In the CHAP Password text box, enter a Challenge-Handshake Authentication Protocol (CHAP) Password that initiators must log in with. The CHAP Password must be characters long. 10. For CIFS volumes only, if the Nasuni Filer is configured for Active Directory authentication, the CIFS-Specific Properties area appears. Figure 6-5: CIFS-Specific Properties. From the User Authentication drop-down list, select the method for the Nasuni Filer to authenticate users connecting to CIFS shares within this volume: Active Directory or Publicly Available to All Users. Note: If the Nasuni Filer is configured for Active Directory authentication, but is not joined to a domain, a message appears, indicating that the new volume is not usable until the Nasuni Filer joins a domain, at which time you can choose Active Directory or Public authentication. Note: It is not possible to change the authentication mode of a volume after you create the volume. 11. Click Save. A message appears telling you that the new volume creation is complete. Click x to close the message box. The new volume appears on the Home page under Volumes. To add a CIFS share to a new volume, see Adding a New CIFS Share to a Volume on page 101. To add an NFS export to a new volume, see Adding an NFS Export to a Volume on page 117. To add an FTP/SFTP directory to a new volume, see Adding FTP directories for a volume on page 127. To enable another protocol for a volume, see Multiple Volume Protocols on page 134. To map a network drive to an automatically created CIFS share, see Mapping a Windows network drive to a CIFS share on page 143. To access a new iscsi volume in Windows, see Accessing an iscsi volume in Windows on page 144. To mount an automatically created CIFS share in Linux or UNIX, see Mounting a CIFS share in Linux or UNIX on page 147. To mount an automatically created NFS export in Linux or UNIX, see Mounting an NFS export in Linux or UNIX on page 149. Nasuni Filer Administration Guide

64 Managing Volumes To access data using the FTP/SFTP protocol, see Accessing data using the FTP/SFTP protocol on page 141. Nasuni Filer Administration Guide

65 Managing Volumes Connecting to a Remote Volume Connect Remote access allows one or more Nasuni Filers to connect, using the Nasuni Service, to a volume associated with another Nasuni Filer. After you enable remote access to a volume, and grant permissions on a volume, you can connect a Nasuni Filer to the remote volume. To enable remote access and grant permissions on a volume, see Remote Access on page 83. Note: If you connect to a remote volume that has multiple protocols defined (including CIFS, NFS, and FTP), the volume inherits the same protocols as the original volume. If the protocols for the remote volume change, the volume inherits the changed protocols. This might take some time. You can refresh the volume connections in order to inherit the changed protocols immediately. The Nasuni Filer must be running version 6.0 or later software in order to connect to a remote volume that has multiple protocols defined. To connect to a remote volume: 1. Click Volumes, then click Connect to Remote Volume. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. Note: It can take some time for recently published volumes to display on the page. You can click Refresh Connections to refresh the view for new volumes to appear. A list of remote volumes available for a remote connection appears on the page. Figure 6-6: Volumes Published by other Filers. Tip: Shared volumes on Nasuni Filers running version 5.5 or later are not available to Nasuni Filers running versions before version 5.5. To see shared volumes on Nasuni Filers running version 5.5 or later, update the software to version 5.5 or later. Nasuni Filer Administration Guide

66 Managing Volumes The following properties appear for each remote volume that is not connected: Name: The name of the remote volume. Connected: Whether the volume is connected: False. Permissions: The current permissions for the remote volume: Read Only or Read/Write. Made accessible from: The name of the remote Nasuni Filer where this remote volume is located. The following properties appear for each connected remote volume: Local Name: The local name of the remote volume. Size: The amount of storage used by the remote volume, not including snapshots. Protocol: The protocol or protocols of the remote volume: CIFS or NFS, or a combination of CIFS, NFS, and FTP. Total Shares (CIFS), Total Exports (NFS), or Total FTP Directories (FTP): For remote CIFS volumes, the total number of CIFS shares. For remote NFS volumes, the total number of NFS exports. For remote FTP/SFTP directories, the total number of FTP/SFTP directories. Volume Pinned: Indicates whether the entire volume, namely, the root folder of the volume, is pinned in the cache: Yes or No. You can pin the volume, or individual folders, to the cache as detailed in Pinning Folders in the Cache on page 188. Connected: Whether the volume is connected: True. Permissions: The current permissions for the remote volume: Read Only or Read/Write. Made accessible from: The name of the remote Nasuni Filer where this remote volume is located. New Data in Cache: The amount of new data that has been saved to the remote volume s cache, but has not yet been protected in cloud storage. Last Snapshot: Date and time of last snapshot of the remote volume, or No snapshots if there are no snapshots. Nasuni Filer Administration Guide

67 Managing Volumes 2. To access a remote volume that is not connected, click Connect to Volume. The Connect to Remote Volume page appears. Figure 6-7: Connect to Remote Volume page. 3. Optionally, provide a different local name for the volume, if needed, in the Local Name text box. Volume descriptions are important for identification purposes. 4. From the Storage Access drop-down list, select one of the following ways to deal with shares or exports from the remote volume: Inherit storage access points: To inherit the CIFS share or NFS export settings from the remote volume. Create default storage access points: To automatically create a CIFS share or NFS export for the remote volume on your Nasuni Filer, but without inheriting the CIFS share or NFS export settings from the remote volume. Skip creating storage access points: To skip creating a new CIFS share or NFS export. 5. In the Inherit Settings area, select or deselect the setting that you want to inherit from the remotely accessible volume. 6. Click Connect Remote Volume to access the remote volume. The message Your filer has been granted access appears. Click x to close the message. 7. The volume on the remote Nasuni Filer appears in the Remote Volumes list, with a Connected status of True. You can now access data on the selected remote volume. Nasuni Filer Administration Guide

68 Managing Volumes Take a Snapshot Now Take You can take an immediate snapshot of your files, folders, and blocks from the Volumes page. To schedule regular snapshots, see Snapshot Scheduling on page 88. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. Note: To perform consistent point-in-time snapshots of iscsi volumes on Windows systems, you can use the Nasuni VSS Hardware Provider. For details, see API Access Keys on page 285. To take a snapshot now: 1. Click Volumes then click All Volumes from the list. The Volumes page appears. Figure 6-8: Volumes page. 2. For the volume that you want to take a snapshot of, click Take snapshot now. A message Snapshot requested appears. Click x to close the message box. Nasuni Filer Administration Guide

69 Viewing Volume Properties Viewing Volume Properties On the Volumes page, select a volume, then click Edit Properties. The Volume properties page appears. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. The volume properties page displays configuration settings and current values for a specific volume. Volume properties page for CIFS and NFS volumes and FTP directories For CIFS and NFS volumes and FTP/SFTP directories, the Volume properties page looks like this: Figure 6-9: Volume properties page for CIFS volume. To change settings, you can click specific links, or select settings from the Properties drop-down list. Nasuni Filer Administration Guide

70 Viewing Volume Properties The following information appears for each volume: In the Volume Overview area: Name: The name of the local volume, or the local name of the remote volume. To rename the volume, click the status. For details, see Renaming a Volume on page 62. Global Name: (Only visible on remote volumes.) The global name of the remote volume. Owned By: (Only visible on remote volumes.) The remote Nasuni Filer that owns the remote volume. Cloud Provider: The name of the cloud provider for the volume. Region: (Only visible on local volumes.) The location of the cloud provider for the volume. Vault (for Cleversafe volumes only): The name of the Cleversafe vault. Size: The current size of the volume. Quota (Maximum Capacity): The quota (maximum capacity) configuration in GB. The default is Unlimited, up to your licensed capacity. If the quota is not Unlimited, the percentage of the quota that is currently being used also appears. A notification occurs when the volume reaches 90 percent of the quota and when the volume reaches the quota. If the volume is shared, then the quota is compared to the sum of all Nasuni Filers connected to the volume. To change the quota, click the status. For details, see Changing the Volume Quota on page 65. Note: If the licensed capacity is exceeded, you can still store more data temporarily. If your total stored data nears or exceeds your licensed capacity, you receive warnings to increase your licensed capacity. In the File Monitoring area: Note: The File Monitoring area is unavailable for iscsi volumes. File Alert Service: Indicates whether the File Alert Service (automatically notifying you when files or directories with particular names are written to the Nasuni Filer) is Enabled or Disabled. To enable or disable the File Alert Service, click the status. For details, see File Alert Service on page 67. Antivirus Service: Indicates whether the Antivirus Service is Enabled or Disabled. To enable or disable the Antivirus Service, click the status. For details, see Antivirus Service on page 69. Antivirus Violations: Displays any infected files discovered by the Antivirus Service. To view the list of Antivirus Violations, click the status. For details, see Reviewing Infected Files on page 71. In the Security and Encryption area: Encryption Keys: The Name, ID, and Enabled setting of the encryption keys for the volume. To add, disable, or enable encryption keys, click the status. For details, see Encryption Key Management on page 77. Nasuni Filer Administration Guide

71 Viewing Volume Properties In the Access area: Protocol: The protocol or protocols of the volume: CIFS, NFS, or iscsi, or a combination of CIFS, NFS, and FTP. Permissions Policy: (Not visible on remote volumes.) If multiple protocols are enabled, the selected permissions policy for the protocols, from the following: UNIX/NFS Permissions Only Mode: Default mode for NFS volumes. Recommended for primary or heavy NFS use. Not recommended for Windows users. Only the traditional UNIX mode bits control permissions (chmod). Windows can view permissions as access control lists (ACLs), but cannot add or remove access control entries (ACEs). Windows CIFS users can change permissions using the Security tab of the Windows Properties dialog box. NTFS Compatible Mode: Default mode for CIFS volumes on Nasuni Filers joined to Active Directory. Recommended for volumes with only CIFS protocol enabled, or for volumes with CIFS and FTP/SFTP protocols enabled, but with read-only FTP/SFTP or only occasional FTP/SFTP writes. Not recommended for mixed protocol support. Produces full NTFS permissions, as supported on CIFS/SMB. Windows clients obey inheritance rules. NFS and FTP/SFTP protocols cannot see all NTFS permissions and do not obey all access rules in NTFS permissions. NFS and FTP/SFTP protocols obey only the POSIX access control list (ACL) component of inheritance rules. POSIX Mixed Mode: Default mode for none. Recommended for combined CIFS and FTP/SFTP volumes, with light NFS use. Also recommended for CIFS-only volumes with Linux or Mac clients, with UNIX extensions enabled. Access control lists (ACLs) are supported entirely through POSIX ACLs. Windows clients receive mapping of POSIX ACLs to NTFS ACLs. However, the mappings are not as complete as mappings done for NTFS Compatible Mode. NFS clients cannot view the ACLs. The NFSv4 protocol automatically translates the underlying ACLs to NFSv4 ACLs. The common tools for managing POSIX ACLs are not supported on NFSv4. To manage ACLs using NFSv4, you must use the NFSv4 ACL tools. Unauthenticated Access Mode: Default mode for CIFS volumes on Nasuni Filers that are not joined to Active Directory. Recommended for CIFS Public-mode volumes. For CIFS clients, this mode acts as an open share. For all other protocols, this mode acts identically to POSIX Mixed Mode. See Enabling multiple volume protocols on page 135. CIFS Authentication: (Not visible on remote volumes.) (CIFS only) The authentication mode for this volume: Active Directory or Publicly Available. Total Shares (CIFS), Total Exports (NFS), or Total FTP Directories (FTP): Total number of CIFS shares, NFS exports, or FTP/SFTP directories. To add or edit CIFS shares, NFS exports, or FTP/SFTP directories, click the status. For details, see Adding a New CIFS Share to a Volume on page 101, Adding an NFS Export to a Volume on page 117, or Adding FTP directories for a volume on page 127. Remote Access: (Not visible on remote volumes.) The setting of remote access for this volume: Enabled or Disabled. To enable or disable remote access, click the status. For details, see Remote Access on page 83. Nasuni Filer Administration Guide

72 Viewing Volume Properties Remote Access Type: (Only visible on remote volumes.) The type of access permitted to this remote volume: Read/Write or Read Only. For details, see Remote Access on page 83. In the Cache Management area: New Data in Cache: The amount of new data that has been saved to the cache, but has not yet been protected in cloud storage. Pinned Folders: Indicates the number of folders pinned in the cache. To pin folders to the cache, click the status. For details, see Pinning Folders in the Cache on page 188. Auto Caching Folders: Indicates the number of folders with Auto Cache (immediately bringing data from other Nasuni Filers into the local cache) enabled. To enable Auto Cache for folders, click the status. For details, see Enabling Auto Cache for Folders on page 189. To enable or disable Auto Cache for a volume, see Enabling or Disabling Auto Cache for Volumes on page 86. Note: Auto Cache must be enabled for a volume before Auto Cache is enabled for a folder in the volume. In the Snapshots and Synchronization area: Last Snapshot: Date and time of last snapshot, or No snapshots if there are no snapshots. Snapshot Schedule: The schedule for snapshots. If there is no schedule for snapshots, indicates Disabled. To schedule snapshots, click the status. For details, see Snapshot Scheduling on page 88. Sync Schedule: (Only available for remotely accessible volumes.) The schedule of when the volume synchronizes data ( syncs ) from the Nasuni Service, merging local data with data from other Nasuni Filers connected to this volume. If there is no schedule for syncs, indicates Disabled. To schedule syncs, click the status. For details, see Sync Scheduling on page 90. To enable or disable Auto Cache for a volume, see Enabling or Disabling Auto Cache for Volumes on page 86. Note: A sync happens before every snapshot. Note: On volumes with global locking enabled, global locking provides file synchronization independently of snapshot and synchronization processing. Snapshot Directory Access: Indicates whether access to the snapshot directory for the volume is Enabled or Disabled. To enable or disable snapshot directory access for a volume, click the status. For details, see Snapshot Directory Access on page 92. Snapshot Retention: (Not visible on remote volumes.) The snapshot retention policy. To configure a snapshot retention policy, click the status. For details, see Snapshot Retention on page 94. The Delete Volume button appears at the bottom of the Volume properties page for local volumes. To delete a volume, click the button. For details, see Deleting a Volume on page 98. The Disconnect Volume button appears at the bottom of the Volume properties page for remote volumes. To disconnect a volume, click the button. For details, see Disconnecting from a Remote Volume on page 174. Nasuni Filer Administration Guide

73 Viewing Volume Properties The Take snapshot now button appears at the bottom of the Volume properties page. To take a snapshot, click the button. For details, see Take a Snapshot Now on page 54. Volume properties page for iscsi volumes For iscsi volumes, the Volume properties page looks like this: Figure 6-10: Volume properties page for iscsi volume. To change settings, you can click specific links, or select settings from the Properties drop-down list. The following information appears for each volume: In the Volume Overview area: Name: The name of the volume. To rename the volume, click the status. For details, see Renaming a Volume on page 62. Cloud Provider: The name of the cloud provider. Region: The location of the cloud provider. LUN Size: Size of the iscsi volume in GB. Nasuni Filer Administration Guide

74 Viewing Volume Properties In the Security and Encryption area: Encryption Keys: The Name, ID, and Enabled setting of the encryption keys for the volume. To add, disable, or enable encryption keys, click the status. For details, see Encryption Key Management on page 77. In the Access area: Protocol: The protocol used for the volume: iscsi. To edit the iscsi settings, click the Protocol. For details, see Changing iscsi Settings on page 63. Target Name: The iscsi Qualified Name of the iscsi target, in this format: iqn. Date that the naming authority took ownership of the domain, in yyyy-mm format.. followed by the reversed domain name of the authority, such as com.nasuni. : followed by a storage target name specified by the naming authority. Example: iqn com.nasuni:filer.nasuni.net:51 To edit the iscsi settings, click Target Name. See Changing iscsi Settings on page 63. In the Cache Management area: New Data in Cache: The amount of new data that has been saved to the cache, but has not yet been protected in cloud storage. This might not match the amount of data written to the volume, because of the presence of metadata. Volume Pinned: Indicates whether the volume is pinned in the cache: Yes. iscsi (SAN) volume data is always resident (pinned) in the cache. In the Snapshots and Synchronization area: Last Snapshot: Date and time of last snapshot, or No snapshots if no snapshots. Snapshot Schedule: The schedule for snapshots. If there is no schedule for snapshots, indicates Disabled. To schedule snapshots, click the status. For details, see Snapshot Scheduling on page 88. Snapshot Retention: The snapshot retention policy. To configure a snapshot retention policy, click the status. For details, see Snapshot Retention on page 94. The Delete Volume button appears at the bottom of the Volume properties page. To delete a volume, click the button. For details, see Deleting a Volume on page 98. The Take snapshot now button appears at the bottom of the Volume properties page. To take a snapshot, click the button. For details, see Take a Snapshot Now on page 54. Nasuni Filer Administration Guide

75 Viewing Volume Properties Data Growth Chart A chart of Data Growth for the selected volume appears at the bottom of the Volume properties page. Figure 6-11: Data Growth chart for selected volume. This shows the total amount of stored data (on the vertical axis) versus time (along the horizontal axis). This chart includes both data and metadata. The amount of data is shown in units such as KB, MB, GB, and TB. The length of time is shown by month and day. The data growth chart updates automatically every 5 minutes. You can select the time period of this chart by clicking the drop-down list and selecting one of the following time periods: Previous 7 days. Previous 14 days. Previous 30 days. Previous 90 days. All time. If you hover the mouse over any part of the chart, a label appears displaying details about the amount of data in that volume at that date and time. Figure 6-12: Details of data and time on Data Growth chart. To zoom in on a specific range of displayed data, click the chart at the high end of the range you want, then drag to the low end of the range you want, then release. The chart rescales to zoom in on the selected range. To reset the zoom to the default display, click Reset zoom. Nasuni Filer Administration Guide

76 Changing Volume Properties Changing Volume Properties Edit You can change many of the properties of a volume on the Volume properties page. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. Renaming a Volume Rename You can rename a volume. Note: If a snapshot is in progress when you attempt to rename a volume, you receive a message to retry after the snapshot is complete. See for a worksheet for planning configurations. To rename a volume: 1. Click Volumes, then select the volume from the list. The Volumes page appears. 2. Select a volume, then click Edit Properties. The Volume properties page appears. 3. Click the Name of the volume. The Rename Volume dialog box appears. Figure 6-13: Rename Volume dialog box. 4. Enter the new name for the volume in the Name text box. Note: For iscsi volumes, the iscsi volume name is used to generate the target name. This includes changing any upper-case letters to lower-case, and changing any non- ASCII symbols to their hex code. 5. Click Save. Your changes are saved. The confirmation message Successfully changed volume name appears. To exit the dialog box without changing the volume name, click Cancel. Nasuni Filer Administration Guide

77 Changing Volume Properties Changing iscsi Settings Edit You can change the settings of iscsi volumes after the iscsi volume is created. See for a worksheet for planning configurations. To change the settings of an iscsi volume: 1. Click Volumes, then select the iscsi volume from the list. 2. The Volume properties page appears. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. 3. From the Properties drop-down list, select iscsi Settings. The iscsi Settings page appears. Figure 6-14: iscsi Settings page. 4. In the Target Name text box, you can change the Target Name. The Target Name is created automatically using the volume name. However, you can change the Target Name that was automatically generated. The Target Name is the iscsi Qualified Name of the iscsi target, in this format: iqn. Date that the naming authority took ownership of the domain, in yyyy-mm format.. followed by the reversed domain name of the authority, such as com.nasuni. : followed by a storage target name specified by the naming authority. Example: iqn com.nasuni:filer.nasuni.net:51 Nasuni Filer Administration Guide

78 Changing Volume Properties 5. In the Volume Size text box, enter the Volume Size, in GB. Note: All iscsi (SAN) volume data is pinned in the cache. Therefore, the Volume Size of an iscsi volume is limited by the size of the cache. iscsi volumes can use up to 75 percent of the cache. The computed limit is displayed. Note: The Volume Size of an iscsi volume can be increased, if necessary, but not decreased. 6. To control which hosts are allowed to connect to this volume, in the Allowed Hosts text box, you can change the comma-separated list of the IP addresses or subnet addresses that are allowed to access this volume. If you leave this field blank, all hosts on your network have access to this volume without restrictions. 7. To restrict access to this iscsi volume, in the CHAP User Name text box, you can enter a Challenge-Handshake Authentication Protocol (CHAP) User Name that initiators must log in with. In the CHAP Password text box, you can enter a Challenge-Handshake Authentication Protocol (CHAP) Password that initiators must log in with. 8. Click Save. The changes to the iscsi settings are saved. Nasuni Filer Administration Guide

79 Changing Volume Properties Changing the Volume Quota Edit For CIFS and NFS volumes and FTP/SFTP directories, the volume quota (maximum capacity) enables you to limit the amount of storage space for a volume, including snapshots. This helps you to control your storage costs. Although unlimited storage space is available, the volume is limited to the volume quota, which is limited by your licensed capacity. Nasuni recommends that you only increase quotas rather than decrease them. Note: A notification occurs when the volume reaches 90 percent of the quota. Another notification occurs when the volume reaches the quota. If the volume is shared, then the quota is compared to the sum of all Nasuni Filers connected to the volume. If your total stored data nears or exceeds your licensed capacity, you receive warnings to increase your licensed capacity. If the licensed capacity is exceeded, you can still store more data temporarily. See for a worksheet for planning configurations. To modify a volume quota: 1. Click Volumes, then select the volume from the list. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. 2. The Volume properties page appears. The Quota setting is visible. Figure 6-15: Quota setting. 3. Click the Quota setting. The Change Volume Quota dialog box appears. Figure 6-16: Change Volume Quota dialog box. 4. Set the maximum volume capacity by entering a quota value (in gigabytes or fractions of a gigabyte, such as 6.8) in the Quota text box. Entering a 0 configures the quota to an unlimited capacity (up to your licensed capacity). If the volume is shared, then the quota is compared to the sum of all Nasuni Filers connected to the volume. Nasuni Filer Administration Guide

80 Changing Volume Properties 5. Click Save. Your changes are saved. The confirmation message Successfully changed volume quota appears. Directory Quotas Edit You can view, edit, and delete the current directory quota rules and quotas for a volume. Quotas are available for CIFS and NFS volumes and FTP/SFTP directories, but not for iscsi volumes. Note: You set directory quotas on the File Browser page. For details, see Setting Quota or Rule on page 186. Note: You configure directory quota reports on the Configuration page. For details, see Quota Settings on page 297. To view, edit, or delete directory quotas, follow these steps: 1. Click Volumes, then select the volume from the list. 2. The Volume properties page appears. Click Properties, then click Quotas. The Quota page appears. Figure 6-17: Quota page. In the Quota Rules list, each directory quota rule in the volume appears with the Location controlled by the quota rule, an optional address to notify when the data in the location nears or exceeds the Limit, and the Limit for the quota rule. In the Applied Quotas list, each directory quota in the volume appears with the Location controlled by the quota, an optional address to notify when the data in the location nears or exceeds the Limit, the Limit for the quota rule, the Total Used data in the directory, and the Percent Used data in the directory. 3. To edit a directory quota rule or directory quota, click Edit and change the optional address or the Limit. When finished, click Save Quota. Tip: If User Folders Support is enabled for the CIFS share that the directory is in, then the address of the directory owner is used automatically. This eliminates the necessity of manually entering hundreds of addresses for multi-user systems. See step q on page To delete a directory quota rule or quota, click Delete. Nasuni Filer Administration Guide

81 Changing Volume Properties File Alert Service Enable file alert service The File Alert Service triggers an alert (no more than one per day) in the Notifications system when files and directories whose names match patterns you specify are written to the Nasuni Filer. This can be valuable in tracking certain special files for compliance purposes, such as files or directories that contain text like HIPAA. You can use wildcards when you specify each pattern. For example, if you specify *.mp3, you receive an alert (no more than one per day) when any files whose names end in.mp3 are written to the Nasuni Filer. You can also view the file alert logs in the.nasuni/file_alerts directory. Note: File alerts configured here apply only to the local Nasuni Filer, and not to any other Nasuni Filer. To enable file alerts on other Nasuni Filers in a multi-site configuration, you must configure the other Nasuni Filers individually. To administer file alerts consistently on multiple Nasuni Filers, use the Nasuni Management Console. If you have configured settings, you receive an (no more than one per day) when names of files or directories match one of the patterns. To configure settings, see Settings on page 247. Note: If a match is detected, you receive no more than one alert per day. The alert contains the path to a complete log file containing all detected matches. See for a worksheet for planning configurations. To configure the File Alert Service: 1. Click Volumes, then select the volume from the list. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. 2. The Volume properties page appears. The File Alert Service setting is visible. Figure 6-18: File Alert Service setting. Nasuni Filer Administration Guide

82 Changing Volume Properties 3. Click the File Alert Service setting. Alternatively, select File Alert Service from the Properties drop-down list. The File Alert Service page appears. Figure 6-19: File Alert Service page. 4. To enable the File Alert Service, select enabled from the File Alert Service is drop-down list. To disable the File Alert Service, select disabled from the File Alert Service is drop-down list. 5. If the File Alert Service is enabled, enter name patterns in the File/Directory Patterns text box. Enter one name pattern per line. You can use glob syntax wildcards when you specify each pattern, such as the following: Wildcard Meaning Example * Matches any number of any character.? Matches any one character. *.mp3 means any file name that ends with mp3. test.mp? means file names like test.mp3 or test.mp4. [sequence] [!sequence] Matches any character in the specified sequence. Matches any character NOT in the specified sequence. [A-Z]*.* means file names that start with an upper-case letter. [!A-Z]*.* means file names that do not start with an uppercase letter. 6. Click Save. Your changes are saved. Nasuni Filer Administration Guide

83 Changing Volume Properties Antivirus Service Enable antivirus service The Antivirus Service provides protection against viruses and other malware in files on a volume. The Antivirus Service scans every new or modified file for the presence of viruses and other malware. The entire file is scanned, not just the changed part. Files are scanned when included in a snapshot, but not during Global Locking processing. If a scanned file is found to be infected, the authorized administrator has the option to ignore the infection. Only files with no detected malware, or infected files that the authorized administrator deliberately ignores, are allowed into cloud storage. The Nasuni Filer updates antivirus definition files multiple times daily. The Antivirus Service scans container files (such as.zip files) as large as 100 MB, and non-container files as large as 25 MB. You can enable or disable antivirus protection at the volume level. The Antivirus Service setting is inherited by connecting Nasuni Filers. For example, if the Boston Nasuni Filer enables the Antivirus Service for a volume, and the London Nasuni Filer connects to that volume, then the Antivirus Service is also enabled for that volume on the London Nasuni Filer. In such a case, there might be a brief time lag before the London Nasuni Filer inherits that setting. Note: The Antivirus Service is available for CIFS and NFS volumes and FTP/SFTP directories. The Antivirus Service is not available for iscsi volumes. Note: Antivirus violations are displayed in the Nasuni Filer or Nasuni Management Console, and are also logged to the.nasuni/av_violations/ folder of the volume. In the Antivirus log file, each violation entry is of the form: <DATE> <TIME> <TIMEZONE> New AV violation: <SIGNATURE> found: <PATH> Example: :32:33 GMT New AV violation: EicarSignature found: /ei.txt See for a worksheet for planning configurations. Enabling and Disabling Antivirus Service Note: Only the volume owner can enable or disable the Antivirus Service for a volume. In particular, you cannot enable or disable the Antivirus Service for a remote volume. To configure the Antivirus Service: 1. Click Volumes, then select the volume from the list. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. Nasuni Filer Administration Guide

84 Changing Volume Properties 2. The Volume properties page appears. The Antivirus Service setting is visible. Figure 6-20: Antivirus Service setting. 3. Click the Antivirus Service setting. Alternatively, select Antivirus Service from the Properties drop-down list. The Antivirus Service page appears. Figure 6-21: Antivirus Service page. 4. To enable the Antivirus Service, select enabled from the Volume Antivirus Service is dropdown list. To disable the Antivirus Service, select disabled from the Volume Antivirus Service is drop-down list. If you select enabled, then configure the Antivirus Service by performing these steps: a. For volumes on which the CIFS protocol has been enabled only, to check files as they are written to the Nasuni Filer, in addition to the specified Antivirus Service schedule, select enabled from the Check files immediately drop-down list. Otherwise, select disabled from the Check files immediately drop-down list. Note: Enabling Check files immediately can have a small effect on performance. Nasuni Filer Administration Guide

85 Changing Volume Properties b. In the Scanning Schedule area, select the days for Antivirus Service scanning to occur (for example, Sunday to Saturday). Note: In addition to the specified Scanning Schedule, an antivirus scan is performed automatically with every snapshot. c. To specify scanning 24 hours a day, select the 24 Hours/Day check box. Alternatively, select the hour for scanning to start from the Start drop-down list. Select the hour for scanning to stop from the Stop drop-down list. d. For the specified time period, select the frequency for Antivirus Service scanning to occur from the Frequency drop-down list. If the volume does not have Remote Access enabled, your choices are 1, 2, 4, 8, 12, or 24 (hours). If the volume does have Remote Access enabled, your choices are 1, 5, 10, 25, or 30 (minutes), or 1, 2, 4, 8, 12, or 24 (hours). 5. Click Save. Your changes are saved. Reviewing Infected Files Review If the Antivirus Service finds any files infected with a virus or other malware, that information is displayed on the volume s Volume properties page. The authorized administrator must review each infected file before that file is allowed into cloud storage. To review infected files: 1. Click Volumes, then select the volume from the list. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. 2. The Volume properties page appears. The Antivirus Violations setting is visible. Figure 6-22: Antivirus Violations setting. Nasuni Filer Administration Guide

86 Changing Volume Properties 3. Click the Antivirus Violations setting. Alternatively, select Antivirus Violations from the Properties list. The Antivirus Violations page appears. Figure 6-23: Antivirus Violations page. A list appears showing the files that are infected with a virus or other malware. For each file in the list, the complete file path and file name, infection name, and list of available actions appears. 4. For each file in the list, click either Ignore or Delete File. To ignore a detected infection and permit the infected file to enter cloud storage, click Ignore. The Confirm File Ignore dialog box appears. Click Confirm Ignore. The infected file is permitted to enter cloud storage. Note: The Nasuni Filer records the name of the authorized administrator who authorizes ignoring the infected file. Alternatively, to delete the infected file and prevent the infected file from entering cloud storage, click Delete File. The Confirm File Delete dialog box appears. Click Confirm Delete. The infected file is deleted. 5. After all the infected files have been ignored or deleted, the message No data available in table appears. Nasuni Filer Administration Guide

87 Changing Volume Properties File System Auditing Take You can configure extensive file system auditing and logging of operations for a volume. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. Note: It is possible that occasionally a specified operation might not be audited and logged, such as when a Nasuni Filer reboots or restarts. Also, if events occur faster than the auditing, a Lost Events entry is made in the log file. Tip: Log files take up space. To reduce the amount of space necessary for log files, you can: limit the number of event categories to audit, limit which volumes to audit, use filters to reduce the directories or files to audit, and limit the log file retention period. To configure file system auditing for a volume, follow these steps: 1. Click Volumes, then select the volume from the list. 2. The Volume properties page appears. 3. From the Properties drop-down list, select Auditing. The Auditing Configuration page appears. Figure 6-24: Top portion of Auditing Configuration page. 4. To enable file system auditing for this volume, select Auditing Enabled. Nasuni Filer Administration Guide

88 Changing Volume Properties 5. In the Event Types area, select the operations to include in file system auditing, from these choices: Create: Operations that create files, directories, or links. Delete: Operations that delete files or directories. Rename: Operations that rename files or directories. Close: Operations that close files. Security: Changes to file or directory ownership or permission. Metadata: Changes to update time and extended attributes. Write: Operations that write or truncate files. Read: Operations that read files or directories. Note: Some event types generate a greater load and result in greater traffic. 6. In the Audit Logs area, to write audit logs, select Write Audit Logs. Important: If you do not select Write Audit Logs, log files are not written. 7. To delete log files older than a specified number of days, select Prune Audit Logs and enter a number greater than zero in Days to Keep. If Prune Audit Logs is not selected, or if Days to Keep is zero, audit logs are not deleted. Nasuni Filer Administration Guide

89 Changing Volume Properties 8. To audit operations only for specified directories or files, select Exclude by Default and enter the specific directories or files to include in the Include Patterns text box. Figure 6-25: Bottom portion of Auditing Configuration page. Separate the patterns with a comma or by placing a pattern on a new line. You can use glob syntax wildcards when you specify each pattern, such as the following: Wildcard Meaning Example * Matches any number of any character.? Matches any one character. *.mp3 means any file name that ends with mp3. test.mp? means file names like test.mp3 or test.mp4. [sequence] [!sequence] Matches any character in the specified sequence. Matches any character NOT in the specified sequence. [A-Z]*.* means file names that start with an upper-case letter. [!A-Z]*.* means file names that do not start with an uppercase letter. 9. To audit operations for directories or files in the Include Patterns text box, even if those directories or files are logically part of the entries in the Exclude Patterns text box, select Include List Takes Priority. 10. To exclude specified directories or files from audit operations, such as *.tmp files, enter the specific directories or files to exclude in the Exclude Patterns text box. Separate the patterns with a comma or by placing a pattern on a new line. You can use glob syntax wildcards when you specify each pattern, as described in step Click Save. The specified operations for the specified directories and files are audited and written in log files for later use. Nasuni Filer Administration Guide

90 Changing Volume Properties Log file location and format Log files are written to the.nasuni\audit\<filerdescription>\<yyyymmdd> directory, where filerdescription is the description of the Nasuni Filer and yyyymmdd is the date of the log file. Note: If this is a shared volume, entries from multiple Nasuni Filers may appear in the same <filerdescription> directory. Log file names are in the format audit-<timestamp>.csv, where timestamp is the GMT time of the log file. A sample log file name is audit csv. Note: You cannot access the log files from the Nasuni Filer or from the Nasuni Management Console. You must mount the volume and access the appropriate directory. Each line of the log file is a record for a single audited operation. Each record includes the following information, if available: Timestamp (UTC) of the audited operation in the format 10/27/ :31:49 PM. Category of the operation, from the Event Types above. Event type as a subtype of the category, such as the following: Create: Create Directory or Create File. Delete: Delete Directory or Delete File. Read: Read Directory or Read File. Security: Change Owner, Change Permissions, Set ACL, or Set DOS Attribute. Write: Truncate File or Write to File. Path/from of the item. New path/to of the item (if appropriate). User of the item (if appropriate). Group of the user (if appropriate). SID (Active Directory) of the CIFS item (if appropriate). Share name for the item (for volumes on which the CIFS protocol has been enabled only, if appropriate). Volume type of the item: CIFS, NFS, FTP, or Internal. Client IP address that caused the event (for CIFS volumes only, if appropriate). Snapshot timestamp (UTC), if event occurred on an item in a snapshot, in the format 10/27/ :31:49 PM. Each log file contains at most 100,000 records. If additional records must be logged, a new log file is created. Note: It is possible that occasionally a specified operation might not be audited and logged, such as when a Nasuni Filer reboots or restarts. Also, if events occur faster than the auditing, a Lost Events entry is made in the log file. Nasuni Filer Administration Guide

91 Changing Volume Properties Encryption Key Management On the Encryption Keys page, you can view the status of current encryption keys and view information on all encryption keys. You can add an encryption key to a volume, and enable or disable encryption keys. All data on a volume is encrypted using one or more encryption keys before being sent to cloud storage. Volumes may be encrypted with one or more encryption keys, and encryption keys may be used for any number of volumes. There are several actions you can perform on encryption keys, including adding new encryption keys, enabling or disabling encryption keys, escrowing encryption keys with Nasuni, and, under certain circumstances, deleting encryption keys. At least one encryption key must be enabled for a volume, but several encryption keys can be enabled at the same time. When multiple encryption keys are enabled, all of the enabled encryption keys are used to encrypt data in such a way that any one of the encryption keys can decrypt the data. There are several reasons you might want to disable an encryption key, such as, when someone with access to the encryption key leaves the company, or if your enterprise has a policy of rotating encryption keys periodically. When you disable an encryption key, no future data is encrypted with that encryption key. However, all data previously encrypted by that disabled encryption key remains encrypted by that disabled encryption key. For this reason, before you disable an encryption key, you should consider establishing a snapshot retention policy that removes the data that was encrypted with the disabled encryption key. Because volumes must have at least one encryption key associated with them, in practice you add a new encryption key to a volume first, and then disable the existing encryption key. You can delete encryption keys, but only in the case where they are not being used by any volumes. You cannot modify encryption keys stored on the system. For security reasons, encryption keys that you upload cannot be downloaded from the system. You can only download encryption keys that the Nasuni Filer has generated internally. To upload an encryption key, see Adding (Importing or Uploading) Encryption Keys on page 289. See for a worksheet for planning configurations. Enabling Encryption Keys Enable If you have disabled one or more encryption keys for a volume, you can enable them. Note: Several encryption keys can be enabled at the same time. When multiple encryption keys are enabled at the same time, all of the enabled encryption keys are used to encrypt data in such a way that any one of the encryption keys can decrypt the data. To enable encryption keys: 1. Click Volumes, then select the volume from the list. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. Nasuni Filer Administration Guide

92 Changing Volume Properties 2. The Volume properties page appears. The Encryption Keys setting for one or more encryption keys is visible. Figure 6-26: Encryption Keys setting. 3. Click one of the Encryption Keys settings. Alternatively, select Encryption Keys from the Properties drop-down list. The Encryption Keys page appears. Figure 6-27: Encryption Keys page. 4. Click Re-enable for the encryption key you want to enable. The Enable Volume Key page appears. Figure 6-28: Enable Volume Key page. 5. Enter a Username (case-sensitive) and Password (case-sensitive) that has permission to perform this operation. 6. To enable the encryption key, click Save. Your changes are saved. Nasuni Filer Administration Guide

93 Changing Volume Properties Disabling Encryption Keys At least one encryption key must be enabled for a volume. Except for that requirement, you can disable any current encryption key. However, in order to decrypt any data that was encrypted with the current encryption key, the Nasuni Filer must retain the current encryption key, even if that encryption key is disabled. You must add a new encryption key before disabling the current encryption key. Future data for this volume is encrypted using the new encryption key, and not the disabled encryption key. For additional information about encryption keys, see Encryption Key Management on page 287. Note: You can have several encryption keys enabled at the same time. When multiple encryption keys are enabled at the same time, all of the enabled encryption keys are used to encrypt data in such a way that any one of the encryption keys can decrypt the data. To disable encryption keys for a volume: 1. Click Volumes, then select the volume from the list. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. 2. The Volume properties page appears. The Encryption Keys setting for one or more encryption keys is visible. Figure 6-29: Encryption Keys setting. 3. Click one of the Encryption Keys settings. Alternatively, select Encryption Keys from the Properties drop-down list. The Encryption Keys page appears. Figure 6-30: Encryption Keys page. Nasuni Filer Administration Guide

94 Changing Volume Properties 4. Click Disable for the encryption key you want to disable. The Disable Volume Key page appears. Figure 6-31: Disable Volume Key page. 5. Enter a Username (case-sensitive) and Password (case-sensitive) that has permission to perform this operation. 6. To disable the encryption key, click Save. The encryption key is disabled for the volume. You can re-enable encryption keys at a later time, if needed. See Enabling Encryption Keys on page 77 for details. Nasuni Filer Administration Guide

95 Changing Volume Properties Adding Encryption Keys to a Volume Add When you add an encryption key to a volume, all data is encrypted using the encryption key you select. After you add the encryption key, it cannot be removed, but it can be disabled. Note: Several encryption keys can be enabled at the same time. When multiple encryption keys are enabled at the same time, all of the enabled encryption keys are used to encrypt data in such a way that any one of the encryption keys can decrypt the data. To add an encryption key to a volume: 1. Click Volumes, then select the volume from the list. 2. The Volume properties page appears. The Encryption Keys setting for one or more encryption keys is visible. Figure 6-32: Encryption Keys setting. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. 3. Click one of the Encryption Keys settings. Alternatively, select Encryption Keys from the Properties drop-down list. The Encryption Keys page appears. Figure 6-33: Encryption Keys page. Nasuni Filer Administration Guide

96 Changing Volume Properties 4. Click Add to Volume for the encryption key you want to add to the volume. The Add Volume Key page appears. Figure 6-34: Add Volume Key page. 5. Enter a Username (case-sensitive) and Password (case-sensitive) that has permission to perform this operation. 6. To add the encryption key to the volume, click Save. The encryption key is added to the volume. Tip: If you create a new encryption key, make sure that you download and protect the new encryption key, in case you need it for disaster recovery or other purposes later. See Downloading (Exporting) Generated Encryption Keys on page 290 for more details. Nasuni Filer Administration Guide

97 Changing Volume Properties Remote Access Enable On the Remote Access page, you can enable or disable access to the selected volume by your remote offices attached to your Nasuni.com account. If remote access to this volume is enabled, you can select permissions for remote access to this volume. See for a worksheet for planning configurations. Note: If the Nasuni Filer is not running version 6.0 or later software, that Nasuni Filer cannot connect to a remote volume that has multiple protocols defined (including CIFS, NFS, and FTP). Setting Remote Access To set remote access to a volume: 1. Click Volumes, then select the volume from the list. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. 2. The Volume properties page appears. The Remote Access setting is visible. Figure 6-35: Remote Access setting. Nasuni Filer Administration Guide

98 Changing Volume Properties 3. Click the Remote Access setting. Alternatively, select Remote Access from the Properties drop-down list. The Remote Access page appears. Figure 6-36: Remote Access page. 4. To enable or disable access to this volume, from the Remote Access is drop-down list, select either enabled or disabled. Note: If you disable access to a volume that other Nasuni Filers are connected to, those Nasuni Filers still have access to the disabled volume, but only Read Only access. 5. If access to this volume is enabled, from the Remote Access Permissions drop-down list, select either Read Only, Read/Write, or custom. Read Only: All other Nasuni Filers on your account can view the data on the selected volume, but cannot change that data. Read/Write: All other Nasuni Filers on your account can view the data on the selected volume, and can also change that data. custom: You specify the access for each other Nasuni Filer on your account separately. Note: If you choose custom, new Nasuni Filers cannot access the volume until you explicitly provide the type of access. Nasuni Filer Administration Guide

99 Changing Volume Properties 6. If you select custom remote access permissions, then you use the list of other Nasuni Filers on your account. Figure 6-37: Remote Access custom permissions. For each other Nasuni Filer on your account, select the drop-down list beside the name of the Nasuni Filer and select either Disabled, Read Only, or Read/Write. Disabled: This Nasuni Filer cannot view or change the data on the selected volume. Read Only: This Nasuni Filer can view the data on the selected volume, but cannot change that data. Read/Write: This Nasuni Filer can view the data on the selected volume, and can also change that data. 7. Click Save. The specified remote access permissions are applied to the volume. A message appears to confirm your selection. Nasuni Filer Administration Guide

100 Changing Volume Properties Enabling or Disabling Auto Cache for Volumes Enable If you enable the Auto Cache option, new data is brought into the local cache immediately from other Nasuni Filers that are attached to this volume. Otherwise, new data is brought into the local cache from other Nasuni Filers when that data is accessed next. Tip: Because Auto Cache is not enabled by default, new data in the volume comes into the local cache only when requested. If you plan on enabling Auto Cache, ensure that all of the following apply to your deployment: All the Nasuni Filers on which you plan to enable Auto Cache have caches large enough to contain data from the other Nasuni Filers. All the data in the volume is relevant and appropriate for all other sites that access the volume. Network access at each site is not adversely affected by automatically moving large quantities of data. Auto Cache should not be used during the initial transfer of data into a Nasuni Filer or during certain one-time operations, such as a bulk data load. Note: Auto Cache is only available for shared or remote volumes. Note: You enable Auto Cache for individual folders. See Enabling Auto Cache for Folders on page 189. See for a worksheet for planning configurations. To enable or disable Auto Cache: 1. Click Volumes, then select the volume from the list. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. Nasuni Filer Administration Guide

101 Changing Volume Properties 2. The Volume properties page appears. Select Sync Schedule from the Properties drop-down list. The Sync Schedule page appears. Figure 6-38: Sync Schedule page. 3. To enable Auto Cache, select the Auto Cache check box. Alternatively, to disable Auto Cache, clear the Auto Cache check box. 4. If Auto Cache is enabled, you can specify bringing only files greater than or equal to a specified size into the cache automatically. Enter the minimum size (in whole numbers) in the Auto Cache Minimum File Size text box, then select the correct units from the drop-down list. 5. Click Save. Your changes are saved. A message appears to confirm your selection. To enable Auto Cache for individual folders, see Enabling Auto Cache for Folders on page 189. Nasuni Filer Administration Guide

102 Changing Volume Properties Snapshot Scheduling Edit snapshot schedule A snapshot is a complete picture of the files and folders in your file system at a specific point in time. Using snapshots, the Nasuni Filer can identify new or changed data. Snapshots offer data protection by enabling you to recover a file deleted in error or to restore an entire file system. After a snapshot has been taken and is sent to cloud storage, it is not possible to modify that snapshot. With snapshots, you can find, view, and restore past versions of your files quickly. You can restore a single file, a directory, or an entire volume. The Nasuni Filer captures complete snapshots of files at regular intervals and stores all snapshots in cloud storage to protect your files. You can select which days of the week on which to perform snapshots; what time of day to start and stop creating snapshots; and the frequency for creating snapshots. If the volume does not have Remote Access enabled, your frequency choices are every 1, 2, 4, 8, 12, or 24 (hours). If the volume does have Remote Access enabled, your frequency choices are every 1, 5, 10, 15, 25, or 30 (minutes), or 1, 2, 4, 8, 12, or 24 (hours). For example, you can configure snapshots to not occur during work-time and only push new and changed data during off-hours when network usage is low. If there is no new or changed data at the scheduled time of the snapshot, the snapshot does not occur. Warning: Frequent snapshots increase the system load significantly. Tip: On volumes with Global Locking enabled, we recommend reducing the normal snapshot and synchronization frequency of the volume, because Global Locking provides file synchronization independently of the snapshot and synchronization frequency. Note: To perform consistent point-in-time snapshots of iscsi volumes on Windows systems, you can use the Nasuni VSS Hardware Provider. For details, see API Access Keys on page 285. See Quality of Service Settings on page 263 to configure inbound and outbound bandwidth limits. See for a worksheet for planning configurations. To schedule snapshots: 1. Click Volumes, then select the volume from the list. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. 2. The Volume properties page appears. The Snapshot Schedule setting is visible. Figure 6-39: Snapshot Schedule setting. Nasuni Filer Administration Guide

103 Changing Volume Properties 3. Click the Snapshot Schedule setting. Alternatively, select Snapshot Schedule from the Properties drop-down list. The Snapshot Schedule page appears. Figure 6-40: Snapshot Schedule page. 4. Select the days for snapshots to occur (for example, Sunday through Saturday). 5. To specify snapshots 24 hours a day, select the 24 Hours/Day check box. Alternatively, select the time to start snapshots from the Start drop-down list. Select the time to stop snapshots from the Stop drop-down list. 6. Select the frequency for snapshots to be taken and sent to cloud storage from the Frequency drop-down list. If the volume does not have Remote Access enabled, your choices are every 1, 2, 4, 8, 12, or 24 (hours). If the volume does have Remote Access enabled, your choices are every 1, 5, 10, 15, 25, or 30 (minutes), or 1, 2, 4, 8, 12, or 24 (hours). Note: Volumes that do not have remote access enabled only have Frequency options of hours, not minutes. For snapshots more frequent than 1 per hour, enable remote access for the volume. See Remote Access on page 83. Warning: Frequent snapshots increase the system load significantly. 7. Click Save. Your changes are saved. A message appears to confirm your selection. Note: To configure the inbound and outbound bandwidth, see Quality of Service Settings on page 263 for details. Nasuni Filer Administration Guide

104 Changing Volume Properties Sync Scheduling Edit sync schedule You can schedule when, and with what frequency, the selected volume synchronizes data ( syncs or merges) from the Nasuni Service, merging your local data with any new or changed data from other Nasuni Filers connected to this volume. This helps to ensure that everyone in your organization is using the most current data. If you enable the Auto Cache option, new or changed data is brought into the local cache from other Nasuni Filers that are attached to this volume immediately. Otherwise, data is brought into the local cache from other Nasuni Filers when that data is accessed next. Tip: Because Auto Cache is not enabled by default, new data in the volume comes into the local cache only when requested. If you plan on enabling Auto Cache, ensure that all of the following apply to your deployment: All the Nasuni Filers on which you plan to enable Auto Cache have caches large enough to contain data from the other Nasuni Filers. All the data in the volume is relevant and appropriate for all other sites that access the volume. Network access at each site is not adversely affected by automatically moving large quantities of data. Auto Cache should not be used during the initial transfer of data into a Nasuni Filer or during certain one-time operations, such as a bulk data load. You can select which days of the week on which to sync data; at what time of day to start and stop syncing data; and the frequency for syncing data: every 1, 5, 10, 25, or 30 minutes, or every 1, 2, 4, 8, 12, or 24 hours for each volume. For example, you can configure syncs to not occur during work-time and only sync data during off-hours when network usage is low. Warning: Frequent syncs increase the system load significantly. See Quality of Service Settings on page 263 to configure bandwidth limits. See for a worksheet for planning configurations. To schedule syncs: 1. Click Volumes, then select the volume from the list. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. 2. The Volume properties page appears. The Sync Schedule setting is visible. Figure 6-41: Sync Schedule setting. Nasuni Filer Administration Guide

105 Changing Volume Properties 3. Click the Sync Schedule setting. Alternatively, select Sync Schedule from the Properties dropdown list. The Sync Schedule page appears. Figure 6-42: Sync Schedule page. 4. Select the days for syncs to occur (for example, Sunday to Saturday). 5. To specify syncs 24 hours per day, select the 24 Hours/Day check box. Alternatively, select the time to start syncs from the Start drop-down list. Select the time to stop syncs from the Stop drop-down list. 6. Select the frequency for syncs to occur from the Frequency drop-down list. Your choices are every 1, 5, 10, 25, 30 (minutes), or 1, 2, 4, 8, 12, or 24 (hours). 7. To enable Auto Cache (automatically bringing data from other Nasuni Filers into the local cache immediately), select the Auto Cache check box. Alternatively, to disable Auto Cache, clear the Auto Cache check box. See Enabling or Disabling Auto Cache for Volumes on page If Auto Cache is enabled, you can specify bringing only files greater than or equal to a specified size into the cache automatically. Enter the minimum size (in whole numbers) in the Auto Cache Minimum File Size text box, then select the correct units from the drop-down list. 9. Click Save. Your changes are saved. A message appears to confirm your selection. Nasuni Filer Administration Guide

106 Changing Volume Properties Snapshot Directory Access Enable snapshot directory access You can enable access to the snapshot directory to permit browsing the snapshot history and viewing the files and directories for NFS exports, CIFS shares, and FTP/SFTP directories. For more information, see Using Snapshot Directory Access on page 194. Note: Snapshot access can add a significant load to the Nasuni Filer. Note: Snapshot access is not available for iscsi volumes. Note: With volumes on which the CIFS protocol has been enabled, for snapshot directory access to operate, snapshot directory access must also be enabled for the CIFS share. For more details, see step p on page 107. See for a worksheet for planning configurations. To enable access to the snapshot directory for a volume: 1. Click Volumes, then select the volume from the list. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. 2. The Volume properties page appears. The Snapshot Directory Access setting is visible. Figure 6-43: Snapshot Directory Access setting. 3. Click the Snapshot Directory Access setting. The Edit Snapshot Directory Access dialog box appears. Figure 6-44: Edit Snapshot Directory Access dialog box. 4. To enable access to the snapshot directory, select the Snapshot Directory Access Enabled check box. To disable snapshot access, clear the Snapshot Directory Access Enabled check box. Note: The setting of Windows Previous Versions is independent of the setting of Snapshot Access. Nasuni Filer Administration Guide

107 Changing Volume Properties 5. Click Save. Your changes are saved. To exit the dialog box without making any changes, click Cancel. Nasuni Filer Administration Guide

108 Changing Volume Properties Snapshot Retention Edit snapshot retention A snapshot is a complete picture of the files and folders in your file system at a specific point in time. Using snapshots, the Nasuni Filer can identify new or changed data. Snapshots offer data protection by enabling you to recover a file deleted in error or to restore an entire file system. After a snapshot has been taken and is sent to cloud storage, it is not possible to modify that snapshot. For compliance purposes or your own best practices, you can specify to delete older snapshots from cloud storage, based on a configured policy for a specific volume. Snapshot retention policies are configured on the volume level. Snapshot retention policies also work on shared volumes. Caution: Set a snapshot retention policy for any volumes used for backup. Caution: For security purposes, when a snapshot is removed, it is permanently deleted from cloud storage and cannot be recovered. Note: As long as a file is included in any snapshot within your snapshot retention policy, that file is not removed. However, if you delete a file, and none of the retained snapshots includes that file, the file is removed. See for a worksheet for planning configurations. To set a snapshot retention policy for a volume: 1. Click Volumes, then select the volume from the list. The Volume properties page appears. The Snapshot Retention setting is visible. Figure 6-45: Snapshot Retention setting. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. 2. Click the Snapshot Retention setting. Alternatively, select Snapshot Retention from the Properties drop-down list. The Snapshot Retention page appears. Figure 6-46: Snapshot Retention page. Nasuni Filer Administration Guide

109 Changing Volume Properties 3. From the I want to retain drop-down list, select a retention policy option: all snapshots: (Default) Retains all snapshots indefinitely. If you require deleting older snapshots for compliance or other reasons, do not select this option. a set number of snapshots: (Not available if the volume has Remote Access enabled) Enter the Number of snapshots to retain, from 1 to 1 billion (1,000,000,000). For example, if you choose to keep 100 snapshots, then the 100 most recent snapshots are retained, and the rest are deleted automatically. Figure 6-47: Snapshot Retention by number. Warning: You cannot select a set number of snapshots if the volume has Remote Access enabled. snapshots within a given time: Enter the number of Years, Months, or Days for which you want to retain snapshots. For example, if you choose to keep two months worth of snapshots, then snapshots that were taken before then are deleted automatically. Figure 6-48: Snapshot Retention by time. 4. To accept your snapshot retention policy, click Save. Your changes are saved. A message appears to confirm your selection. Nasuni Filer Administration Guide

110 Changing Volume Properties Pinned Folders Edit snapshot retention Pinning a folder specifies that the folder and its contents must remain in the local cache at all times. This can improve performance and reduce the time necessary to return accessed data to clients. You can view pinned folders. You can also disable pinning for folders. Note: Enabling this feature means that the entire folder, and all the folder s contents, remain resident in the cache at all times. This reduces the available cache by the size of the folder. If too much cache space is taken up by pinned folders, an Alert notification is given. Note: Pinning a folder does not bring the folder s data into the cache. If the folder s data is not already present in the cache, you must specifically bring that data to the cache. To check on whether data is resident in the cache, see Browsing a Volume on page 178. To bring data to the cache, see Bringing Data into Cache on page 185. Note: All iscsi (SAN) volume data is already pinned in the cache, so it is not necessary to pin iscsi volumes. To pin a folder in the cache, see Pinning Folders in the Cache on page 188. See for a worksheet for planning configurations. To view pinned folders, or disable pinning for a folder, follow these steps: 1. Click Volumes, then select the volume from the list. The Volume properties page appears. The Pinned Folders setting is visible. Figure 6-49: Pinned Folders setting. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. 2. Click the Pinned Folders setting. Alternatively, select Pinned Folders from the Properties drop-down list. The Pinned Folders page appears. Figure 6-50: Pinned Folders page. 3. To disable pinning for a folder, click Disable for that folder. 4. The Disable Folder Setting dialog box appears. Click Disable Folder Setting. Pinning is disabled for that folder. Alternatively, to not disable pinning for that folder, click Cancel. Nasuni Filer Administration Guide

111 Changing Volume Properties Auto Caching Folders Edit snapshot retention You can view or delete the Auto Cache setting for folders. If Auto Cache is enabled for a folder, new data in that folder is brought into the local cache immediately from other Nasuni Filers that are attached to this volume. Otherwise, new data is brought into the local cache from other Nasuni Filers when that data is accessed next. To view the Auto Cache settings for a folder, follow these steps: 1. Click Volumes, then select the volume from the list. The Volume properties page appears. The Auto Caching Folders setting is visible. Figure 6-51: Auto Caching Folders setting. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. 2. Click the Auto Caching Folders setting. Alternatively, select Auto Caching Folders from the Properties drop-down list. The Auto Caching Folders page appears. Figure 6-52: Auto Caching Folders page. The status of Auto Cache for the volume appears: Allowed or Disabled. To change the Auto cache setting for the volume, click the status. See Enabling or Disabling Auto Cache for Volumes on page To disable Auto Cache for a folder, click Delete for that folder. 4. The Delete Folder Setting dialog box appears. Click Delete Setting. Auto Cache is disabled for that folder. Alternatively, to not disable Auto Cache for that folder, click Cancel. Nasuni Filer Administration Guide

112 Changing Volume Properties Deleting a Volume Delete This section explains how to delete a volume in the Nasuni Filer. Deleting a volume destroys all the volume s data stored in the cache, as well as data stored in cloud storage. Note: Deleting a volume reduces the licensed capacity used; however, the background delete operation can take time to process, depending on the number of files or blocks. The Nasuni Filer might be less responsive during this time. Before deleting a volume, complete the following prerequisites: For volumes with a CIFS share, an NFS export, or an FTP/SFTP directory, you must delete the CIFS share, NFS export, or FTP/SFTP directory before you can delete the volume. For details on deleting a CIFS share, see Deleting a CIFS Share on page 115. For details on deleting an NFS export, see Deleting an NFS Export on page 125. For details on deleting an FTP/SFTP directory, see Deleting FTP directories on page 133. If other Nasuni Filers are connected to the volume, they should disconnect from the volume. See Disconnecting from a Remote Volume on page 174 for details. If the volume is configured for remote access, you must disable remote access on the volume before deleting it. See Remote Access on page 83 for details on disabling remote access. It is necessary to disconnect from iscsi volumes before deleting the iscsi volume, as detailed in Disconnecting from an iscsi volume on page 145. To delete a volume: Caution: You cannot undo this procedure. 1. Ensure that you have deleted the CIFS shares, NFS exports, and FTP/SFTP directories associated with the volume. 2. Click Volumes, then select the volume from the list. The Volume properties page appears. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. Nasuni Filer Administration Guide

113 Changing Volume Properties 3. Click Delete Volume. Alternatively, select Delete from the drop-down list. The Delete Volume page appears. Figure 6-53: Delete Volume page. 4. Read any warnings that appear on the Delete Volume page. Ensure that the prerequisites mentioned above have been satisfied to avoid data loss. 5. Enter a Username (case-sensitive) and Password (case-sensitive) that has permission to perform this operation. 6. Click Delete to delete the volume. Alternatively, to exit this screen without deleting the volume, click your Web browser s Back button. Nasuni Filer Administration Guide

114 Changing Volume Properties CIFS Shares, NFS Exports, and FTP Directories You can view, add, edit, and delete CIFS shares, NFS exports, and FTP/SFTP directories. Note: iscsi (SAN) volumes cannot be shared or exported. Viewing a CIFS Share You can view CIFS shares. To view shared CIFS folders: 1. From the Status drop-down menu, select CIFS Status. The CIFS Shares page appears. Figure 6-54: CIFS Shares page. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. 2. For each shared folder, information about the CIFS share appears, including the Name of the CIFS share, the Path of the shared folder, and available Actions, such as Edit Share and Delete Share. Nasuni Filer Administration Guide

115 Changing Volume Properties Adding a New CIFS Share to a Volume Create On the Volume properties page, you can add CIFS shares to a volume that has the CIFS protocol enabled. Tip: You can only add CIFS shares to a volume that has the CIFS protocol enabled. To create a CIFS volume, see Adding a Volume on page 46. To enable the CIFS protocol for a volume, see Enabling multiple volume protocols on page 135. By default, the Nasuni Filer provides a CIFS share called files for your first CIFS volume on the first Nasuni Filer associated with an account. You can change the configuration settings of this CIFS share, if needed. See Editing a CIFS Share on page 113 for details. See for a worksheet for planning configurations. To add a shared folder to a volume: 1. Click Volumes, then select a volume that has the CIFS protocol enabled from the list. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. 2. The Volume properties page appears. The Total Shares status is visible. Figure 6-55: Total Shares status. 3. Click the Total Shares status. Alternatively, select CIFS Shares from the Properties drop-down list. The CIFS Shares page appears. Figure 6-56: CIFS Shares page. Nasuni Filer Administration Guide

116 Changing Volume Properties 4. Click Add New Share. The Add CIFS Share/Edit Settings page appears. Figure 6-57: Add CIFS Share/Edit Settings page. 5. Click the Folder text box and navigate to an existing folder on the selected volume. Note: To create a folder in Windows, use Windows Explorer to navigate to the root folder of the volume, then create folders as needed. 6. In the Name text box, enter a name for this CIFS share. The following characters are not valid for CIFS share names: < > : " / \? * Also, do not use the $ character at the end of the name of the CIFS share. Windows clients interpret these CIFS shares as hidden. If the Security of this Nasuni Filer is Active Directory, and if User Folders Support is enabled, you can modify the name of the CIFS share to include the wildcard %U to represent the user name. (See step q on page 107.) For example, the wildcard CIFS share name: %U_share for the user rudyg becomes the CIFS share name: rudyg_share If the CIFS share %U_share maps to the folder /homes, then, when the user maps rudyg_share, the resulting location is /homes/rudyg. Tip: For Windows uses, see Naming Files, Paths, and Namespaces. 7. Optionally, enter a descriptive comment in the Comment text box. Nasuni Filer Administration Guide

117 Changing Volume Properties 8. If you want the CIFS share to be visible in the list of CIFS shares when users map the Nasuni Filer, select the Visible Share check box. If the CIFS share is not visible, it does not appear in the list of CIFS shares when users map the Nasuni Filer; however, if you know the CIFS share s name, you can still map the CIFS share directly. 9. If you want the CIFS share folder to be Read Only for users on the network, select the Read Only Share check box. This means that users can access the CIFS share, but have Read Only rights and, therefore, cannot make changes to any of the files in the shared folder. 10. Optionally, click Show Advanced Options. The Advanced Options pane appears. Figure 6-58: Advanced Options pane. a. In the Allowed Hosts text box, enter the IP addresses, IP address/netmask values, or ranges of IP addresses that are allowed to access the CIFS share folder on your network. If you leave this field blank, all users on your network have access to the CIFS share without restrictions. Separate entries with spaces. Nasuni Filer Administration Guide

118 Changing Volume Properties b. In the Block files text box, enter the names of files or directories to make invisible and inaccessible in the share. Enter one name per line. You can use wildcard characters, such as? and *. Do not use the forward slash / character. Note: Using this feature can break compatibility with some clients. c. If the Security of this Nasuni Filer is Public, the Authentication, Groups, and Users options do not appear. Continue with step m on page 107. d. If the Security of this Nasuni Filer is Active Directory, the Authentication, Groups, and Users options appear. To authenticate all users, select Authenticate all Users from the Authenticate drop-down menu. Continue with step m on page 107. Otherwise, to authenticate only specified groups and users, select Authenticate only specified Groups and Users from the Authenticate drop-down menu. This enables the Groups and Users areas. e. To add one group, follow these steps: i. In the Groups area, click Add One. The Name search box appears. Figure 6-59: Add One Name search box. ii. Enter a partial or complete group name, then click Search. The Select Group dialog box appears, containing the partial or complete group name. Figure 6-60: Select Group dialog box. iii. To control the range of the search, select one of the following: All: To search through all groups. Domain only: To search though domain groups only. Native only: To search through native groups only. Nasuni Filer Administration Guide

119 Changing Volume Properties iv. Click Search. A list of groups that match your search appears. Select the group to define access for, then click Add Selected Group. The selected group appears in the Groups area. Figure 6-61: Groups area. f. To add more than one group, follow these steps: i. In the Groups area, click Add Many. The Select Groups dialog box appears. ii. In the Search text box, enter a partial or complete group name. iii. To control the range of the search, select one of the following: All: To search through all groups. Domain only: To search though domain groups only. Native only: To search through native groups only. iv. Click Search. A list of groups that match your search appears. v. Select the groups to define access for, then click Add Selected Groups. The selected groups appear in the Groups area. g. For each group in the Groups list, from the Access drop-down list, select either Read-Write, Read-Only, or Deny. h. To delete a group from the Groups list, click Delete next to the group name. The group is deleted from the list. i. To add one user, follow these steps: i. In the Users area, click Add One. The Name search box appears. Figure 6-62: Add One Name search box. Nasuni Filer Administration Guide

120 Changing Volume Properties ii. Enter a partial or complete user name, then click Search. The Select User dialog box appears, containing the partial or complete user name. Figure 6-63: Select User dialog box. iii. To control the range of the search, select one of the following: All: To search through all users. Domain only: To search though domain users only. Native only: To search through native users only. iv. Click Search. A list of users that match your search appears. Select the user to define access for, then click Add Selected User. The selected user appears in the Users area. Figure 6-64: Users area. j. To add more than one user, follow these steps: i. In the Users area, click Add Many. The Select Users dialog box appears. ii. In the Search text box, enter a partial or complete user name. iii. To control the range of the search, select one of the following: All: To search through all users. Domain only: To search though domain users only. Native only: To search through native users only. iv. Click Search. A list of users that match your search appears. v. Select the users to define access for, then click Add Selected Users. The selected users appear in the Users area. k. For each user in the Users list, from the Access drop-down list, select either Read-Write, Read-Only, or Deny. l. To delete a user from the Users list, click Delete next to the user name. The user is deleted from the list. Nasuni Filer Administration Guide

121 Changing Volume Properties m. To hide files and folders that a user cannot access, leave the Hide Unreadable Files check box selected. This option is selected by default. n. To allow clients to view or restore files using the Previous Versions tab in Windows, select the Enable Previous Versions check box. For details on using Windows Previous Versions, see your Microsoft Windows documentation. o. To enable case sensitivity for file or folder names, select the Case-Sensitive Paths check box. Tip: Using case-sensitive paths improves performance. Note: Even if case-sensitivity is not enabled, non-windows clients such as Linux might still treat the paths as case-sensitive. p. To enable clients to access snapshot directories within the CIFS share, select the Enable Snapshot Directories check box. The volume must have Snapshot Directory Access enabled. For more details, see Snapshot Directory Access on page 92. Note: Snapshot directory access can add a significant load to the Nasuni Filer. Note: When Enable Snapshot Directories is enabled on a CIFS share, you cannot delete directories from the client. Note: The setting of Windows Previous Versions is independent of the setting of Snapshot Directory Access. q. If the Security of this Nasuni Filer is Active Directory, then User Folders Support is available. To enable User Folders Support, select Enabled from the User Folders Support drop-down list. Otherwise, select Disabled from the User Folders Support drop-down list. If enabled, the target folder path for the CIFS share is automatically appended with a folder named for the user. For example, the CIFS share homes that points to the folder /homes mounted by the user rudyg results in a mapping to /homes/rudyg. This can simplify setting up multiple CIFS shares for multiple users. In addition, you can modify the name of the CIFS share to include the wildcard %U to represent the user name. For example, the wildcard CIFS share name: %U_share for the user rudyg becomes the CIFS share name: rudyg_share If the CIFS share %U_share maps to the folder /homes, then, when the user maps rudyg_share, the resulting location is /homes/rudyg. Note: If you use this option, disabling case sensitivity is recommended. Note: Even if Case-Sensitive Paths is not enabled, UNC paths accessed via User Folders Support are case-sensitive. Nasuni Filer Administration Guide

122 Changing Volume Properties Enable r. To enable access by mobile devices, such as iphones and Android phones, select the Desktop and Mobile Access check box. For more details on the Mobile Service, see Nasuni Desktop and Mobile Access on page 235 and Nasuni Mobile Access on page 157. See for a worksheet for planning configurations. Also, to enable access using the Nasuni Desktop Client, select the Desktop and Mobile Access check box. For more details on the Nasuni Desktop Client, see Nasuni Desktop Client on page 167. See for the Nasuni Desktop Client Administrator Guide and the Nasuni Desktop Client User Guide. s. To enable Web Access to files and folders, including creating shared links, select the Web Access check box. The Web Access Settings pane appears. For more details on Web Access, see Web Access on page 150. Continue with specific instructions at Web Access Settings on page 109. t. If the Security of this Nasuni Filer is Active Directory, then Asynchronous I/O is available. This enables concurrent read and write access to the share. To enable Asynchronous I/O, select Enable Asynchronous I/O. Asynchronous I/O is enabled by default. u. To enable support for the SMB2 protocol for Mac OS X clients, select Enhanced Support for Mac OS X. Enabling this can speed up performance for Mac OS X clients. 11. To create the CIFS share, click Save Share. The CIFS share is created and ready for use. In Windows, you can map a drive to a new shared folder as explained in Mapping a Windows network drive to a CIFS share on page 143. In Linux and UNIX, you can mount a CIFS share, as explained in Mounting a CIFS share in Linux or UNIX on page 147. Nasuni Filer Administration Guide

123 Changing Volume Properties Web Access Settings In the Web Access Settings pane, you can specify details about Shared Links. A shared link is a URL that points to a specific file or folder within Web Access. This can be useful for providing a trusted partner or contractor with secure access to a folder or file that they do not have credentials to access directly. For more details on shared links, see Shared Links on page 152. You can control how long until the shared link expires, whether a password is required, and who is allowed to create shared links. Tip: You can change the logo and the primary and secondary colors of the Web Access display for branding purposes. See Web Access Branding on page 330. If Web Access is enabled, the Web Access Settings pane appears. To configure shared links, follow these steps: Figure 6-65: Web Access Settings pane. 1. To allow creating shared links, select Enable Shared Links. 2. If shared links are enabled, enter the maximum number of days until a shared link expires. To specify that there is no limit to the time until expiration, enter 0 (zero). 3. If shared links are enabled, to specify that any shared links must include a password, select Require Password. 4. If shared links are enabled, to allow creating shared links that permit writing to directories, select Allow Writable Shared Links to Directories. 5. If shared links are enabled, select either Allow all Users or Allow only specified Groups and Users from the Shared Link Permissions drop-down list. Nasuni Filer Administration Guide

124 Changing Volume Properties 6. If shared links are enabled, and you selected Allow only specified Groups and Users, you can specify the groups and users who can create shared links by following these steps: a. To add one group, follow these steps: i. In the Groups area, click Add One. The Domain\Name search box appears. Figure 6-66: Add One Name search box. ii. Enter a partial or complete group name, then click Search. The Select Group dialog box appears, containing the partial or complete group name. Figure 6-67: Select Group dialog box. iii. To control the range of the search, select one of the following: All: To search through all groups. Domain only: To search though domain groups only. Native only: To search through native groups only. iv. Click Search. A list of groups that match your search appears. v. Select the group, then click Add Selected Group. The selected group appears in the Groups area. Figure 6-68: Groups area. b. To add more than one group, follow these steps: i. In the Groups area, click Add Many. The Select Groups dialog box appears. ii. In the Search text box, enter a partial or complete group name. Nasuni Filer Administration Guide

125 Changing Volume Properties iii. To control the range of the search, select one of the following: All: To search through all groups. Domain only: To search though domain groups only. Native only: To search through native groups only. iv. Click Search. A list of groups that match your search appears. v. Select the groups, then click Add Selected Groups. The selected groups appear in the Groups area. c. For each group in the Groups list, from the Access drop-down list, select either Read-Write, Read-Only, or Deny. d. To delete a group from the Groups list, click Delete next to the group name. The group is deleted from the list. e. To add one user, follow these steps: i. In the Users area, click Add One. The Name search box appears. Figure 6-69: Add One Name search box. ii. Enter a partial or complete user name, then click Search. The Select User dialog box appears, containing the partial or complete user name. Figure 6-70: Select User dialog box. iii. To control the range of the search, select one of the following: All: To search through all users. Domain only: To search though domain users only. Native only: To search through native users only. Nasuni Filer Administration Guide

126 Changing Volume Properties iv. Click Search. A list of users that match your search appears. Select the user, then click Add Selected User. The selected user appears in the Users area. Figure 6-71: Users area. f. To add more than one user, follow these steps: i. In the Users area, click Add Many. The Select Users dialog box appears. ii. In the Search text box, enter a partial or complete user name. iii. To control the range of the search, select one of the following: All: To search through all users. Domain only: To search though domain users only. Native only: To search through native users only. iv. Click Search. A list of users that match your search appears. v. Select the users, then click Add Selected Users. The selected users appear in the Users area. g. For each user in the Users list, from the Access drop-down list, select either Read-Write, Read-Only, or Deny. h. To delete a user from the Users list, click Delete next to the user name. The user is deleted from the list. 7. Continue with the procedure at step t on page 108. Nasuni Filer Administration Guide

127 Changing Volume Properties Editing a CIFS Share Edit You can edit the features of any CIFS share after you create it. See for a worksheet for planning configurations. To edit the features of a shared folder: 1. Click Volumes, then select a volume that has the CIFS protocol enabled from the list. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. 2. The Volume properties page appears. The Total Shares status is visible. Figure 6-72: Total Shares status. 3. Click the Total Shares status. Alternatively, select CIFS Shares from the Properties dropdown list. The CIFS Shares page appears. Figure 6-73: CIFS Shares page. Nasuni Filer Administration Guide

128 Changing Volume Properties 4. For the CIFS share that you want to edit, click Edit Share. The Add CIFS Share/Edit Settings page appears. Figure 6-74: Add CIFS Share/Edit Settings page. 5. For details about CIFS share settings, see Adding a New CIFS Share to a Volume on page Make your edits, then click Save Share. Your changes are saved. Nasuni Filer Administration Guide

129 Changing Volume Properties Deleting a CIFS Share Delete You can delete a CIFS share. Deleting a CIFS share does not delete any of your data. It deletes the access point to the data. To delete a CIFS share: 1. Click Volumes, then select a volume that has the CIFS protocol enabled from the list. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. 2. The Volume properties page appears. The Total Shares status is visible. Figure 6-75: Total Shares status. 3. Click the Total Shares status. Alternatively, select CIFS Shares from the Properties dropdown list. The CIFS Shares page appears. Figure 6-76: CIFS Shares page. 4. For the CIFS share that you want to delete, click Delete Share. The Confirm Share Delete dialog box appears. 5. The share name appears in the dialog box. Confirm that the correct share is about to be deleted. 6. Click Confirm Delete. The CIFS share is removed. Alternatively, click Cancel to exit the dialog box without deleting the share. Nasuni Filer Administration Guide

130 Changing Volume Properties Viewing an NFS Export You can view existing NFS exports. To view NFS exports: 1. Click Volumes, then select a volume that has the NFS protocol enabled from the list. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. 2. The Volume properties page appears. The Total Exports status is visible. Figure 6-77: Total Exports status. 3. Click the Total Exports status. Alternatively, select NFS Exports from the Properties dropdown list. The NFS Exports page appears. Figure 6-78: NFS Exports page. 4. For each exported directory, information about the NFS export appears, including the Name of the NFS export, the Path of the exported directory, and available Actions, such as Edit Export and Delete Export. Nasuni Filer Administration Guide

131 Changing Volume Properties Adding an NFS Export to a Volume Create You can add an NFS export to a volume that has the NFS protocol enabled. Tip: You can only add NFS exports to a volume that has the NFS protocol enabled. To create an NFS volume, see Adding a Volume on page 46. To enable the NFS protocol for a volume, see Enabling multiple volume protocols on page 135. To add an NFS export to an NFS volume: 1. Click Volumes, then select a volume that has the NFS protocol enabled from the list. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. 2. The Volume properties page appears. The Total Exports status is visible. Figure 6-79: Total Exports status. 3. Click the Total Exports status. Alternatively, select NFS Exports from the Properties dropdown list. The NFS Exports page appears. Figure 6-80: NFS Exports page. Nasuni Filer Administration Guide

132 Changing Volume Properties 4. Click Add New Export. The Add NFS Export/Edit Settings page appears. Figure 6-81: Add NFS Export/Edit Settings page. 5. Click the Directory text box and navigate to the directory you want. 6. In the Name text box, enter a name for this NFS export. The following characters are not valid for NFS export names: < > : " / \? * 7. Optionally, enter a descriptive comment in the Comment text box. 8. In the Allowed Hosts text box, enter the hostname or IP address with optional netmask that is allowed to access the NFS export folder on your network. If you leave this field blank, all users on your network have access to the NFS export without restrictions. Only a single entry is allowed, however, the hostname can contain the * character as a wildcard. 9. From the Access Mode drop-down list, select an access mode. Your choices are: Normal Users Permitted (root_squash): All users who have User IDs (UIDs) greater than zero can map to the NFS export. (Typically, users with a UID of zero (root user) are forcibly mapped to the anonymous NFS UID.) This is the same as root_squash on UNIX systems: it reduces the access rights for a remote superuser (root). All Users Permitted (no_root_squash): All users can map to the NFS export with their normal UID. This is the same as no_root_squash on UNIX systems: it allows remote root users to have root access. Anonymize All Users (all_squash): All users are forcibly mapped to the anonymous NFS UID. This is the same as all_squash on UNIX systems: it converts all users to the anonymous UID and GID. Nasuni Filer Administration Guide

133 Changing Volume Properties 10. If you want the NFS export folder to be Read Only for users on the network, select the Read Only check box. This means that users can access the NFS export, but have Read Only rights and therefore cannot make changes to any of the files that reside in the NFS exported folder. 11. Click Show Advanced Options. Advanced options appear. From the Performance Tuning drop-down list, select the type of Performance Tuning. The choices include the following: Default (sync): Replies to each NFS request only after all data has been stored to disk. This is safer than async, but there is a delay between the store and the reply. No Write Delay (no_wdelay / sync): If NFS deduces a likelihood of a related storage request arriving soon, then NFS s optimization algorithm delays storage. This saves disk writes and can speed performance. However, if NFS deduces incorrectly, this behavior causes a delay in every request. The no_wdelay option eliminates the delay. Asynchronous Replies (async): Replies to requests before the data is stored to disk. Warning: This improves performance, but can result in lost data if the server goes down. 12. To accept your selections, click Save Export. Your changes are saved. A Created NFS Export - <Directory Name> message appears. The NFS export is created and ready for use. The NFS export is available to clients under /nfs/<directory name> and exposes the directory within the volume. To mount an NFS export in Linux or UNIX, see Mounting an NFS export in Linux or UNIX on page 149. Nasuni Filer Administration Guide

134 Changing Volume Properties Editing an NFS Export Edit You can edit the features of any NFS export after you create it. To edit the features of an NFS export: 1. Click Volumes, then select a volume that has the NFS protocol enabled from the list. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. 2. The Volume properties page appears. The Total Exports status is visible. Figure 6-82: Total Exports status. 3. Click the Total Exports status. Alternatively, select NFS Exports from the Properties dropdown list. The NFS Exports page appears. Figure 6-83: NFS Exports page. Nasuni Filer Administration Guide

135 Changing Volume Properties 4. For the NFS export you want to edit, click Edit Export. The Add NFS Export/Edit Settings page appears. Figure 6-84: Add NFS Export/Edit Settings page. For details about NFS export settings, see Adding an NFS Export to a Volume on page Make your edits, then click Save Export. Your changes are saved. Nasuni Filer Administration Guide

136 Changing Volume Properties Multiple hosts for an NFS export Multiple You can enable multiple hosts for a given NFS export. Each host can have different host options, including allowed hosts, access mode, read only, and performance tuning. To enable additional hosts for a given NFS export, follow these steps: 1. Click Volumes, then select a volume that has the NFS protocol enabled from the list. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. 2. The Volume properties page appears. The Total Exports status is visible. Figure 6-85: Total Exports status. 3. Click the Total Exports status. Alternatively, select NFS Exports from the Properties dropdown list. The NFS Exports page appears. Figure 6-86: NFS Exports page. 4. For the export for which you want to define an additional host, click Host Options. The NFS Host Options dialog box appears. Figure 6-87: NFS Host Options dialog box. Nasuni Filer Administration Guide

137 Changing Volume Properties 5. To add new NFS host options, click Add. The NFS Export: Host Options dialog box appears. Figure 6-88: NFS Export: Host Options dialog box. a. In the Allowed Hosts text box, enter a hostname or IP address with optional netmask that is allowed to access the NFS export folder on your network. If you leave this field blank, all users on your network have access to the NFS export without restrictions. Only a single entry is allowed, however, the hostname can contain the * character as a wildcard. b. From the Access Mode drop-down list, select an access mode. Your choices are: Normal Users Permitted (root_squash): All users who have User IDs (UIDs) greater than zero can map to the NFS export. (Typically, users with a UID of zero (root user) are forcibly mapped to the anonymous NFS UID.) This is the same as root_squash on UNIX systems: it reduces the access rights for a remote superuser (root). All Users Permitted (no_root_squash): All users can map to the NFS export with their normal UID. This is the same as no_root_squash on UNIX systems: it allows remote root users to have root access. Anonymize All Users (all_squash): All users are forcibly mapped to the anonymous NFS UID. This is the same as all_squash on UNIX systems: it converts all users to the anonymous UID and GID. c. If you want the NFS export folder to be Read Only for users on the network, select the Read Only check box. This means that users can access the NFS export, but have Read Only rights and therefore cannot make changes to any of the files that reside in the NFS exported folder. Nasuni Filer Administration Guide

138 Changing Volume Properties d. From the Performance Tuning drop-down list, select the type of Performance Tuning. The choices include the following: Default (sync): Replies to each NFS request only after all data has been stored to disk. This is safer than async, but there is a delay between the store and the reply. No Write Delay (no_wdelay / sync): If NFS deduces a likelihood of a related storage request arriving soon, then NFS s optimization algorithm delays storage. This saves disk writes and can speed performance. However, if NFS deduces incorrectly, this behavior causes a delay in every request. The no_wdelay option eliminates the delay. Asynchronous Replies (async): Replies to requests before the data is stored to disk. Warning: This improves performance, but can result in lost data if the server goes down. e. To accept your selections, click Save Options. Your changes are saved. Figure 6-89: NFS Export: Host Options dialog box. 6. To edit existing NFS host options, for the export whose host you want to edit, click Edit. The NFS Export: Host Options dialog box appears. Follow the same steps from step a on page page 123 through step e on page page To delete an existing host, for the export from which you want to delete a host, click Delete. The remove NFS Host Option? dialog box appears. To delete the specified host, click Delete. 8. To save the host options in the NFS Host Options list, click Save. The host options are saved. Alternatively, to exit this screen without changing the export, click the Close button. Nasuni Filer Administration Guide

139 Changing Volume Properties Deleting an NFS Export Delete You can delete an NFS export. Deleting an NFS export does not delete any of your data. It deletes the access point to the data. To delete an NFS export: 1. Click Volumes, then select a volume that has the NFS protocol enabled from the list. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. 2. The Volume properties page appears. The Total Exports status is visible. Figure 6-90: Total Exports status. 3. Click the Total Exports status. Alternatively, select NFS Exports from the Properties dropdown list. The NFS Exports page appears. Figure 6-91: NFS Exports page. 4. For the NFS export you want to delete, click Delete Export. The Confirm Export Delete dialog box appears. 5. Click Confirm Delete. The NFS export is removed. Nasuni Filer Administration Guide

140 Changing Volume Properties FTP Directories You can create, view, edit, and delete FTP/SFTP directories for volumes that have the FTP protocol enabled. This enables you to allow FTP/SFTP access to directories and files without adding new users. Tip: In order to access data using the FTP/SFTP protocol, the following steps are necessary: 1. Create a CIFS or NFS volume. See Adding a Volume on page Enable the FTP protocol on the volume. See Enabling multiple volume protocols on page (Optional) Configure FTP settings. See Configuring FTP settings on page Add a new FTP/SFTP directory. See Adding FTP directories for a volume on page (Optional) Create a permission group that has storage access. See Adding Permission Groups on page (Optional) Create a user in a permission group that has storage access. See Adding Users on page 323. Active Directory users can log in for FTP access just as they do for CIFS access. Also, if anonymous access is enabled, you don't need a specific group or user. 7. Access files using the FTP/SFTP protocol. See Accessing data using the FTP/SFTP protocol on page 141. Viewing FTP directories To view FTP/SFTP directories for a volume, follow these steps: 1. Click Volumes, then select a volume that has the FTP protocol enabled from the list. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. 2. The Volume properties page appears. Select FTP Directories from the Properties drop-down list. The FTP Directories page appears. Figure 6-92: FTP Directories page. For each FTP/SFTP directory, the following information is displayed: Name: The name of the FTP/SFTP directory. Path: The path to the FTP/SFTP directory. Nasuni Filer Administration Guide

141 Changing Volume Properties Adding FTP directories for a volume Tip: You can only create FTP/SFTP directories for volumes that have the FTP protocol enabled. To enable the FTP protocol for a volume, see Enabling multiple volume protocols on page 135. To configure FTP settings for this Nasuni Filer, see Configuring FTP settings on page 270. To create a new FTP/SFTP directory for a volume, follow these steps: 1. On the FTP Directories page for a volume, click Add New FTP Directory. The Add FTP Directory / Edit Settings page appears. Figure 6-93: Add FTP Directory / Edit Settings page. 2. Click the Directory text box and navigate to the directory you want to access using FTP/SFTP. Nasuni Filer Administration Guide

142 Changing Volume Properties 3. In the Name text box, enter a name for this FTP/SFTP directory. The following characters are not valid for FTP/SFTP directory names: < > : " / \? * Tip: For Windows uses, see Naming Files, Paths, and Namespaces. 4. Optionally, enter a descriptive comment in the Comment text box. 5. If you want the FTP/SFTP directory to be read-only, select the Read Only check box. This means that users can access the FTP/SFTP directory, but only have read-only rights and therefore cannot make changes to any of the files or directories in the FTP/SFTP directory. 6. From the Visibility drop-down list, select the visibility of the new FTP/SFTP directory. Your choices are: Default: Every file is visible to the user. However, even if a file is visible to the user, the user might not be able to access the file because of permissions. Hide Unreadable: Files that the user does not have permission to access are not visible to the user. Invisible: No files are visible to the user. However, if a user has the filename of a file, and the appropriate permission, the user can access the file. 7. To control the permissions on new files in this FTP/SFTP directory, there are several choices, which use umask settings to represent read, write, and execute permissions for the user, the group, and others. Select one of the following choices from the Permissions on New Files drop-down menu: No Extra Restrictions (Default): The owner, the group, and all others have all permissions for all files in this FTP/SFTP directory. This is a umask setting of 000, which, for a requested permission of 777, produces 777. Read-Only Others: The owner and the group have all permissions for all files in this FTP/ SFTP directory. Others can only read all files in this FTP/SFTP directory. This is a umask setting of 002, which, for a requested permission of 777, produces 775. Read-Only Groups and Others: The owner has all permissions for all files in this FTP/SFTP directory. The group and others can only read all files in this FTP/SFTP directory. This is a umask setting of 022, which, for a requested permission of 777, produces 755. Restrict Others: The owner and the group have all permissions for all files in this FTP/SFTP directory. Others have no permissions for all files in this FTP/SFTP directory. This is a umask setting of 006, which, for a requested permission of 777, produces 771. Restrict Groups and Others: The owner has all permissions for all files in this FTP/SFTP directory. The group and others have no permissions for all files in this FTP/SFTP directory. This is a umask setting of 066, which, for a requested permission of 777, produces 711. Read-Only Groups, Restrict Others: The owner has all permissions for all files in this FTP/ SFTP directory. The group can only read all files in this FTP/SFTP directory. Others have no permissions for all files in this FTP/SFTP directory. This is a umask setting of 026, which, for a requested permission of 777, produces 751. Nasuni Filer Administration Guide

143 Changing Volume Properties 8. To control which hosts are allowed to connect to this FTP/SFTP directory, in the IP Restrictions text box, enter a comma-separated list of the IP addresses or subnet addresses of the hosts that are allowed to access this FTP/SFTP directory. If you leave this field blank, all hosts on your network have access to this FTP/SFTP directory without restrictions. Note: You cannot use IP Restrictions in conjunction with Allowed Users/Groups in step 9 on page To control the users and groups that have access to the FTP/SFTP directory, from the Allowed Users/Groups drop-down list, select one of the following choices. Everyone: Allows all users and groups to access the FTP/SFTP directory. Anonymous Only: Allows only the anonymous user to access the FTP/SFTP directory. This selection is only available if Anonymous is enabled, as in step 10 on page 132. Specific Users/Groups: Allows you to specify the users and groups that have access to this FTP/SFTP directory. The Allowed Groups and Allowed Users areas appear. Note: You cannot use Allowed Users/Groups in conjunction with IP Restrictions in step 8 on page 129. Tip: A user can access the FTP/SFTP directory if the user is accessing the FTP/SFTP directory from one of the allowed hosts and is either one of the allowed users or a member of one of the allowed groups. Tip: To specify users or groups, the users or groups must have Storage Access enabled. See Users and Groups on page 315. a. To add one group, follow these steps: i. In the Allowed Groups area, click Add One. The Name search box appears. Figure 6-94: Add One Name search box. ii. Enter a partial or complete group name, then click Search. The Select Group dialog box appears, containing the partial or complete group name. Figure 6-95: Select Group dialog box. Nasuni Filer Administration Guide

144 Changing Volume Properties iii. To control the range of the search, select one of the following: All: To search through all groups. Domain only: To search though domain groups only. Native only: To search through native groups only. iv. Click Search. A list of groups that match your search appears. Select the group to define access for, then click Add Selected Group. The selected group appears in the Allowed Groups area. Figure 6-96: Allowed Groups area. b. To add more than one group, follow these steps: i. In the Allowed Groups area, click Add Many. The Select Groups dialog box appears. ii. In the Search text box, enter a partial or complete group name. iii. To control the range of the search, select one of the following: All: To search through all groups. Domain only: To search though domain groups only. Native only: To search through native groups only. iv. Click Search. A list of groups that match your search appears. v. Select the groups to define access for, then click Add Selected Groups. The selected groups appear in the Allowed Groups area. c. To delete a group from the Allowed Groups list, click Delete next to the group name. The group is deleted from the list. d. To add one user, follow these steps: i. In the Allowed Users area, click Add One. The Name search box appears. Figure 6-97: Add One Name search box. Nasuni Filer Administration Guide

145 Changing Volume Properties ii. Enter a partial or complete user name, then click Search. The Select User dialog box appears, containing the partial or complete user name. Figure 6-98: Select User dialog box. iii. To control the range of the search, select one of the following: All: To search through all users. Domain only: To search though domain users only. Native only: To search through native users only. iv. Click Search. A list of users that match your search appears. Select the user to define access for, then click Add Selected User. The selected user appears in the Allowed Users area. Figure 6-99: Allowed Users area. e. To add more than one user, follow these steps: i. In the Allowed Users area, click Add Many. The Select Users dialog box appears. ii. In the Search text box, enter a partial or complete user name. iii. To control the range of the search, select one of the following: All: To search through all users. Domain only: To search though domain users only. Native only: To search through native users only. iv. Click Search. A list of users that match your search appears. v. Select the users to define access for, then click Add Selected Users. The selected users appear in the Allowed Users area. f. To delete a user from the Allowed Users list, click Delete next to the user name. The user is deleted from the list. Nasuni Filer Administration Guide

146 Changing Volume Properties 10. To allow anonymous FTP access, select the Anonymous check box. Tip: If anonymous FTP access is enabled, any user can access the FTP/SFTP directory. 11. To hide ownership details in directories, select Hide Ownership in Listings. This can enhance security. 12. To accept your selections, click Save Directory. The FTP/SFTP directory is created and appears in the list of FTP/SFTP directories. The FTP/ SFTP directory is available to users. Alternatively, to exit this screen without creating an FTP/SFTP directory, click the Reset button. Editing FTP directories To edit the selected FTP/SFTP directory, click Edit Directory, then follow the steps of Adding FTP directories for a volume on page 127. Nasuni Filer Administration Guide

147 Changing Volume Properties Deleting FTP directories To delete the selected FTP/SFTP directory access point (not the data), follow these steps: 1. Click Volumes, then select a volume that has the FTP protocol enabled from the list. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. 2. The Volume properties page appears. Select FTP Directories from the Properties drop-down list. The FTP Directories page appears. Figure 6-100: FTP Directories page. 3. For the FTP/SFTP directory you want to delete, click Delete Directory. The Confirm Directory Delete dialog box appears. 4. Click Confirm Delete. The FTP/SFTP directory is removed. Nasuni Filer Administration Guide

148 Changing Volume Properties Multiple Volume Protocols You can assign CIFS, NFS, and FTP protocols to existing CIFS and NFS volumes. This enables you to allow access to data using multiple protocols. This might be helpful for simplifying access by users or applications. Tip: You cannot assign multiple protocols to a volume to which a volume running a pre-6.0 version is connected. Update the connected volume to version 6.0 or later first, then perform a snapshot for the volume. Note: If this volume has Remote Access enabled and other volumes connect to this volume, the connected volumes inherit the same protocols as this volume. If these protocols change, the connected volumes inherit the changed protocols. This can take some time. You can refresh the volume connections in order to inherit the changed protocols immediately. The connected Nasuni Filer must be running version 6.0 or later software in order to connect to a remote volume that has multiple protocols defined. Tip: In order to access data using the FTP/SFTP protocol, the following steps are necessary: Create a volume. See Adding a Volume on page 46. Enable the FTP protocol on the volume. See Enabling multiple volume protocols on page 135. (Optional) Configure FTP settings. See Configuring FTP settings on page 270. Add a new FTP/SFTP directory. See Adding FTP directories for a volume on page 127. (Optional) Create a permission group that has storage access. See Adding Permission Groups on page 318. (Optional) Create a user in a permission group that has storage access. See Adding Users on page 323. Access files using the FTP/SFTP protocol. See Accessing data using the FTP/SFTP protocol on page 141. Warning: Protocols work in parallel. Enabling an additional protocol to an original protocol does not affect the original protocol. However, writing data to the volume using one protocol can affect the permissions or other metadata used by another protocol. This can inadvertently affect permissions in unexpected ways. Viewing multiple volume protocols To view the protocols that are enabled for a volume, follow these steps: 1. Click Volumes, then select the volume from the list. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. Nasuni Filer Administration Guide

149 Changing Volume Properties 2. The Volume properties page appears. The Protocol status is visible. Figure 6-101: Protocol status. If multiple protocols are enabled for a volume, the protocols are listed. Enabling multiple volume protocols To enable CIFS, NFS, or FTP protocols for a CIFS or NFS volume, follow these steps: 1. Click Volumes, then select a CIFS or NFS volume from the list. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. 2. Select Volume Protocols from the Properties drop-down list. The Enabled Volume Protocols page appears. Figure 6-102: Enabled Volume Protocols page. The currently enabled protocols for the volume are selected. 3. To enable another protocol, select that protocol also. Warning: After enabling a protocol, you cannot disable that protocol. Nasuni Filer Administration Guide

150 Changing Volume Properties 4. From the Volume Permissions Policy drop-down list, select one of the following: UNIX/NFS Permissions Only Mode: Default mode for NFS volumes. Recommended for primary or heavy NFS use. Not recommended for Windows users. Only the traditional UNIX mode bits control permissions (chmod). Windows can view permissions as access control lists (ACLs), but cannot add or remove access control entries (ACEs). Windows CIFS users can change permissions using the Security tab of the Windows Properties dialog box. NTFS Compatible Mode: Default mode for CIFS volumes on Nasuni Filers joined to Active Directory. Recommended for volumes with only CIFS protocol enabled, or for volumes with CIFS and FTP/SFTP protocols enabled, but with read-only FTP/SFTP or only occasional FTP/SFTP writes. Not recommended for mixed protocol support. Produces full NTFS permissions, as supported on CIFS/SMB. Windows clients obey inheritance rules. NFS and FTP/SFTP protocols cannot see all NTFS permissions and do not obey all access rules in NTFS permissions. NFS and FTP/SFTP protocols obey only the POSIX access control list (ACL) component of inheritance rules. POSIX Mixed Mode: Default mode for none. Recommended for combined CIFS and FTP/ SFTP volumes, with light NFS use. Also recommended for CIFS-only volumes with Linux or Mac clients, with UNIX extensions enabled. Access control lists (ACLs) are supported entirely through POSIX ACLs. Windows clients receive mapping of POSIX ACLs to NTFS ACLs. However, the mappings are not as complete as mappings done for NTFS Compatible Mode. NFS clients cannot view the ACLs. The NFSv4 protocol automatically translates the underlying ACLs to NFSv4 ACLs. The common tools for managing POSIX ACLs are not supported on NFSv4. To manage ACLs using NFSv4, you must use the NFSv4 ACL tools. Unauthenticated Access Mode: Default mode for CIFS volumes on Nasuni Filers that are not joined to Active Directory. Recommended for CIFS Public-mode volumes. For CIFS clients, this mode acts as an open share. For all other protocols, this mode acts identically to POSIX Mixed Mode. 5. Click Save. The selected protocol is enabled. Tip: To add a CIFS share to a volume, see Adding a New CIFS Share to a Volume on page 101. To add an NFS export to a volume, see Adding an NFS Export to a Volume on page 117. To add an FTP/SFTP directory to a volume, see Adding FTP directories for a volume on page 127. Tip: To configure CIFS settings for this Nasuni Filer, see Configuring CIFS settings on page 283. To configure FTP settings for this Nasuni Filer, see Configuring FTP settings on page 270. Nasuni Filer Administration Guide

151 Chapter 7: Managing Data This section is about managing data, which includes: Adding data to volumes. Accessing data stored on Nasuni Filers. Adding Data to Volumes There are several ways to move data to a volume, including the following: Automated data migration, as described in Data Migration on page 200. Sync data from other Nasuni Filers, as described in Sync Scheduling on page 90. Copying data from local or network drives to the volume. This section gives details on copying data from local or network drives to the volume. Accessing volumes There are several ways to access Nasuni Filer volumes, including the following: In Windows, you can map network drives to volumes, as described in Mapping a Windows network drive to a CIFS share on page 143. In Windows, you can access iscsi volumes, as described in Accessing an iscsi volume in Windows on page 144. You can use a VMware client, such as the VMware vsphere Client, to define NFS datastores. See Defining NFS datastores using VMware client on page 148. In Linux or UNIX, you can mount volumes, as described in Mounting a CIFS share in Linux or UNIX on page 147 and Mounting an NFS export in Linux or UNIX on page 149. You can access FTP/SFTP directories using an FTP client with the FTP/SFTP protocol. Nasuni Filer Administration Guide

152 Adding Data to Volumes Adding data to a volume After you have established access to a Nasuni Filer volume, you can add data to that volume in several ways. In Windows, you can use Windows Explorer to access volumes mapped to network drives, then copy and paste data to volumes: Figure 7-1: Accessing volume with Windows Explorer. In Windows, you can use command line instructions to navigate to volumes mapped to network drives, then copy data to the volume: Q:\>cd documents_2013 Q:\documents_2013>copy c:\ Nasuni_Filer_Administration_Guide_v3.1.pdf. In Linux or UNIX, you can use command line instructions to navigate to mounted volumes, then copy data to the volume: Station1: User2$ cd docs Station1:docs User2$ ls Nasuni_Filer_Administration_Guide_v3.1.pdf Station1:docs User2$ cp /<source>/ Nasuni_Filer_Administration_Guide_v5.1.pdf. You can access FTP/SFTP directories using an FTP client with the FTP/SFTP protocol. Nasuni Filer Administration Guide

153 Accessing Data Accessing Data There are a variety of ways to access files and folders with Windows, Linux, and UNIX systems. This section gives details on how to access data stored on the Nasuni Filer. Folder and file access permissions in Windows Special default permissions are applied to these folders and files:.nasuni.nasuni/sync_logs/ Files in.nasuni/sync_logs/.nasuni/av_violations/ Files in.nasuni/av_violations/.nasuni/file_alerts/ Files in.nasuni/file_alerts/.nasuni/audit/ Files in.nasuni/audit/ Caution: Do not change the permissions on these folders or files unless it is absolutely necessary. Use caution when changing any permissions. Incorrect permissions can cause problems in access and processing. In Windows, using Active Directory security, all users have Read permission for all files and all folders under the topmost.nasuni folder. However, unless a user also has Read permission for the topmost.nasuni folder, that user cannot access any of those files or folders under the topmost.nasuni folder. By default, only a Filer Administrator has Read permission for the topmost.nasuni folder. If a Filer Administrator wants to allow a user to view the files, the Filer Administrator should change the permission on the topmost.nasuni folder for that user. Tip: In Windows, if a folder gives permission to the group Everyone, unprivileged users might not be able to access the folder. Instead, Nasuni recommends that you assign users to another group that has the desired permission for the folder. Tip: If you are using Active Directory authentication and your Nasuni Filer is joined to an Active Directory server that has Windows Server 2012 domain controllers, and the following conditions occur: The Windows Server 2012 domain controller has Resource SID compression enabled. The client accesses the Nasuni Filer CIFS volume by hostname. The user client is authenticating using access to the CIFS volume based on membership in a domain local group. Then the user is denied access to the CIFS volume. Nasuni Filer Administration Guide

154 Accessing Data Folder and file access permissions in UNIX and Linux In UNIX and Linux, the default permissions for certain folders and files are as follows: Folder or file Permissions.nasuni/ 500.nasuni/sync_logs/ 500 Files in.nasuni/sync_logs/ 444.nasuni/av_violations/ 500 Files in.nasuni/av_violations/ 444.nasuni/file_alerts/ 500 Files in.nasuni/file_alerts/ 444.nasuni/audit/ 500 Files in.nasuni/audit/ 444 If you change the permissions on any of these folders and files, the Nasuni Filer preserves your changes. However, new files still receive the default permissions of 444. The owner of each folder can delete files in that folder. Nasuni Filer Administration Guide

155 Accessing Data Accessing data using the FTP/SFTP protocol If the FTP/SFTP protocol has been enabled for a volume, and FTP/SFTP directories have been added to a volume, you can use FTP/SFTP commands and various applications to access that data. Tip: In order to access data using the FTP/SFTP protocol, the following steps are necessary: 1. Create a CIFS or NFS volume. See Adding a Volume on page Enable the FTP protocol on the volume. See Enabling multiple volume protocols on page (Optional) Configure FTP settings. See Configuring FTP settings on page Add a new FTP/SFTP directory. See Adding FTP directories for a volume on page (Optional) Create a permission group that has storage access. See Adding Permission Groups on page (Optional) Create a user in a permission group that has storage access. See Adding Users on page 323. Active Directory users can log in for FTP access just as they do for CIFS access. Also, if anonymous access is enabled, you don't need a specific group or user. 7. Access files using the FTP/SFTP protocol. See Accessing data using the FTP/SFTP protocol on page 141. To access data using FTP commands, use commands such as these: 1. Enter the following FTP command: ftp <filer DNS filer IP> where <filer DNS filer IP> is the DNS or IP address or hostname of the Nasuni Filer. 2. When prompted, enter a valid username and password for that Nasuni Filer. Note: This user must belong to a permission group that has Storage Access enabled. See Users and Groups on page Navigate to the directory using a command of the form: cd /<ftp_directory>/<folder_name> where <ftp_directory> is the name of the FTP directory and <folder_name> is the name of the folder that the FTP access is defined for. Nasuni Filer Administration Guide

156 Accessing Data Alternatively, follow these steps: 1. Enter the following on the address bar of your Web browser: where <user_name> is the username of the user. This user must belong to a permission group that has Storage Access enabled. See Users and Groups on page 315. <filer> is the IP address or hostname of the Nasuni Filer. <ftp_directory> is the name of the FTP directory. <folder_name> is the name of the folder that FTP access is defined for. 2. When prompted, enter a valid username and password for that Nasuni Filer. Note: This user must belong to a permission group that has Storage Access enabled. See Users and Groups on page A display of the FTP/SFTP directory appears. You can then navigate this directory to access folders and files. Nasuni Filer Administration Guide

157 Accessing Data Mapping a Windows network drive to a CIFS share You can map a Windows network drive to a CIFS share on the Nasuni Filer. Note: You must have CIFS share privileges to access the folder on the Nasuni Filer and map a network drive to it. See Adding a New CIFS Share to a Volume on page 101 and Editing a CIFS Share on page 113 for more details. To map a Windows network drive to a CIFS share: 1. In Windows, right-click My Computer. 2. Select Map Network Drive. The Map Network Drive dialog box appears. Figure 7-2: Map Network Drive dialog box. 3. From the Drive drop-down list, select an available network drive letter to map the CIFS share to. An unused network drive letter is automatically selected. 4. From the Folder drop-down list, select a shared folder on the Nasuni Filer. Alternatively, in the Folder text box, enter the IP address or URL of a shared folder on the Nasuni Filer. For example, \\ \files. Alternatively, click Browse to navigate to the IP address or URL of a shared folder on the Nasuni Filer. For example, \\ \files. 5. If prompted for a username and password, use a username that has data access permissions. Tip: For some Windows platforms, it might be necessary to use <hostname>\ <username> instead of the username, where <hostname> is the IP address or hostname of the Nasuni Filer. 6. Click Finish. 7. With Windows Explorer, select the network drive letter that you mapped. For example: Figure 7-3: Sample mapped drives. Tip: Alternatively, you can enter the path for the CIFS share folder or IP address in Windows Explorer instead of using the Map Network Drive dialog box. Nasuni Filer Administration Guide

158 Accessing Data 8. Open the drive, then drag and drop files that you want to send to the Nasuni Filer. You can now open these files and do your work from this mapped drive. By default, snapshots of unshared volumes are taken every hour (every 5 minutes for shared volumes) to provide you with a backup of your work. Accessing an iscsi volume in Windows You can access an iscsi volume on your Nasuni Filer from Windows. To Windows, the iscsi volume appears as a hard drive. Note: This procedure uses the Windows iscsi Initiator application, which is available for Windows 2000, Windows Server 2003, Windows 2008, Windows 7, and Windows XP. To access an iscsi volume in Windows, follow this procedure: 1. Select Start Administrative Tools iscsi Initiator. The iscsi Initiator opens. 2. Select the Targets tab. 3. In the Target text box, enter the IP address of the Nasuni Filer. 4. Click Quick Connect. The Quick Connect dialog box appears. If you are not using CHAP authentication, the Nasuni Filer should appear in the Discovered targets list with the status Connected. If you are using CHAP authentication, the Nasuni Filer should appear in the list with the status Inactive. 5. Click Done. The Quick Connect dialog box closes. 6. If you are using CHAP authentication, follow these steps: a. Select the Nasuni Filer in the Discovered targets list. b. Click Connect. The Connect to Target dialog box opens. c. Click Advanced. The Advanced Settings dialog box opens. d. Select Enable CHAP log on. e. In the Name text box, enter the CHAP username for this iscsi volume. For details, see step c of step 9 of Adding a Volume on page 46. f. In the Target secret text box, enter the CHAP password for this iscsi volume. For details, see step c of step 9 of Adding a Volume on page 46. g. Click OK. The Advanced Settings dialog box closes. h. Click OK. The Connect to Target dialog box closes. The Nasuni Filer should appear in the list with the status Connected. 7. Click OK. This closes iscsi Initiator. At this point, the iscsi volume appears as a new hard drive to Windows. It is now necessary to partition this new hard drive. 8. Select Start Administrative Tools Computer Management. The Computer Management window opens. Nasuni Filer Administration Guide

159 Accessing Data 9. Select Storage. 10. Select Disk Management. The Initialize Disk dialog box opens. The new hard drive appears in the Select disks pane. 11. Select the new drive. 12. Select GPT (GUID Partition Table). Selecting this option permits sizes larger than 2 TB. 13. Click OK. 14. Right-click the drive and select New Simple Volume from the drop-down list. The New Simple Volume Wizard opens. Click Next. 15. Specify the volume size on the new drive, then click Next. 16. Select a drive letter for the drive, then click Next. Note this drive letter to access the iscsi volume. 17. Enter a volume name, then click Next. 18. Select the file system from the File system drop-down list, then select Perform a quick format, then click Next. 19. Click Finish. The new drive is configured as a Windows drive. 20. The status of the hard drive should be Healthy. You can now access the iscsi volume using the assigned Windows drive letter. In particular, you can add data to the iscsi volume using the Windows drive letter with Windows Explorer or with the Windows command line interface. Disconnecting from an iscsi volume Note: It is necessary to disconnect from iscsi volumes before deleting the iscsi volume. To disconnect from an iscsi volume, follow these steps: 1. Select Start Administrative Tools Computer Management. The Computer Management window opens. 2. Select Storage. 3. Select Disk Management. The Initialize Disk dialog box opens. The hard drive appears in the Select disks pane. 4. Right-click the drive and select Delete Volume from the drop-down list. 5. Click OK. The Computer Management window closes. 6. Select Start Administrative Tools iscsi Initiator. The iscsi Initiator opens. 7. Select the Targets tab. 8. In the Target list, select the target. Nasuni Filer Administration Guide

160 Accessing Data 9. Click Disconnect. The status of the target should become Inactive. However, the target is remembered, in case you want to reconnect to the iscsi volume again. To permanently remove the connection to the iscsi volume, select the Discovery tab, then select the target IP address and click Remove. This removes the target. 10. Click OK. The iscsi Initiator closes. Nasuni Filer Administration Guide

161 Accessing Data Mounting a CIFS share in Linux or UNIX You can mount a CIFS share in Linux or UNIX using the mount.cifs command. There should not be any issues between the CIFS character set and the Linux character set. In most cases, use mount.cifs with the option iocharset=utf-8. CIFS shares are case-sensitive by default, which is consistent with Linux. Note: Even if case-sensitivity is not enabled, non-windows clients such as Linux might still treat the paths as case-sensitive. To ensure that paths are treated as case-insensitive, mount CIFS shares using the nocase option, such as in this command: mount -v -t cifs o nocase,<options> <share IP address> /mnt/<folder> Note: You must have CIFS share privileges to access the folder on the Nasuni Filer. See Adding a New CIFS Share to a Volume on page 101 and Editing a CIFS Share on page 113 for more details. Note: If the Nasuni Filer is running in Active Directory security mode, the Linux clients must connect to the Nasuni Filer as Active Directory users. Tip: Keep in mind the default permissions for certain folders and files in UNIX and Linux. See Folder and file access permissions in UNIX and Linux on page 140. To mount a CIFS share, enter the following command: mount -t cifs -o iocharset=utf-8, user=<username>, domain=<domain-shortname> //<filername>/<sharename> /<localdir> where: username is the username to connect as. domain-shortname is the shortname (not the fully qualified domain name) of the domain. filername is the name or the IP address of the Nasuni Filer. sharename is the name of the CIFS share on the Nasuni Filer. localdir is the name of the local Linux directory. The result of the mount command is to mount the CIFS share in the local directory. Users can then add data to the CIFS volume using copy commands. Tip: You can place the mount command in a script that runs on login and mounts the CIFS share automatically. To disconnect from the CIFS share, use the unmount command. Nasuni Filer Administration Guide

162 Accessing Data Defining NFS datastores using VMware client You can use a VMware client, such as the VMware vsphere Client, to define NFS datastores. To define NFS datastores using a VMware client, follow these steps: 1. On the VMware client, select the host from the list. 2. Select the Configuration tab, then select Storage from the list on the left. 3. In the Datastores area, click Add Storage. The Add Storage dialog box appears. 4. In the Storage Type area, select Network File System, then click Next. 5. In the Properties area, in the Server text box, enter the IP address of the Nasuni Filer. 6. In the Properties area, in the Folder text box, enter the following: /nfs/<name of NFS volume or NFS export> where <name of NFS volume or NFS export> is the case-sensitive name of either the NFS volume or the NFS export. Figure 7-4: Folder text box. 7. In the Datastore Name text box, enter the name that you want to give to this datastore. 8. Click Next, then review the information and click Finish. The datastore appears in the Datastores list. Nasuni Filer Administration Guide

163 Accessing Data Mounting an NFS export in Linux or UNIX You can mount an NFS export in Linux or UNIX using the mount command. Note: You must have export privileges to access the folder on the Nasuni Filer. See Adding an NFS Export to a Volume on page 117 and Editing an NFS Export on page 120 for more details. Tip: Keep in mind the default permissions for certain folders and files in UNIX and Linux. See Folder and file access permissions in UNIX and Linux on page 140. To mount an NFS export in Linux or UNIX, enter the following command: mount -t nfs <IP address>:/nfs/<exportname> <target> where: IP address is the name or the IP address of the Nasuni Filer. exportname is the name of the NFS export on the Nasuni Filer. target is the name of the local directory. Note: The default options for the mount command should work. However, if this does not work, use this version with explicit options: mount -o tcp,nfsvers=3,timeo=600,rsize=16384,wsize=16384,hard This version of the mount command includes these explicit options: TCP. 10-minute timeout. Read and write sizes of 16 KB. Hard mount (soft mounts can corrupt data). These values of rsize and wsize are recommended, but we recommend that you tune them for your system. The result of the mount command is to mount the NFS export in the target directory. Users can then add data to the NFS volume using copy commands. Tip: You can place the mount command in a script that runs on login and mounts the NFS export automatically. Tip: Depending on the specific operating system, performing the mount might also create a graphical icon of the NFS export that enables drag and drop and other GUI actions. To disconnect from the NFS export, use the unmount command. Nasuni Filer Administration Guide

164 Accessing Data Web Access You can access CIFS share data or NFS export data stored in the Nasuni Filer using a Web browser. Some of the actions you can perform depend on the capabilities of the Web browser. Note: To access data in an NFS export, you must enable the CIFS protocol for the NFS volume. See Multiple Volume Protocols on page 134. Note: You must enable Web Access for the CIFS share that you want to access. For details, see Adding a New CIFS Share to a Volume on page 101 or Editing a CIFS Share on page 113. The URL of the Web Access page is similar to the URL of the Nasuni Filer user interface. For example, if you use this URL to access your Nasuni Filer user interface: then the URL of the Web Access page is: After you log in, the Nasuni Web Access page appears. Figure 7-5: Nasuni Web Access page. The Nasuni Web Access page shows a list of the CIFS shares available on this Nasuni Filer. Tip: You can change the logo and the primary and secondary colors of the Web Access display for branding purposes. See Web Access Branding on page 330. Nasuni Filer Administration Guide

165 Accessing Data Opening a CIFS share or directory To open a CIFS share or directory, click the name of that CIFS share or directory. The contents appear as a list. Figure 7-6: Contents of directory. The path to the directory appears above the list on the left. To navigate to a higher point in the directory hierarchy, click one of the directory names in the path. Sorting directory To sort the display, click the Sort button Modified from the list. in the upper right, then select Type, Name, Size, or Uploading file To upload a file to this directory, click the Upload files button Upload Files dialog box appears. above the list on the right. The Figure 7-7: Upload Files dialog box. To navigate to the files to upload, click Choose Files. Alternatively, drag and drop the selected files onto the drag and drop area. Tip: If a file already exists with the same name as the file you are uploading, you are asked to confirm overwriting the existing file. Alternatively, click Done. Nasuni Filer Administration Guide

166 Accessing Data Creating folders To create a folder inside this folder, click the Add Folder button name for the new folder. above the list on the right. Enter a Creating internal links to files or folders To create an internal link URL to a file or folder in Web Access, select the file or folder, then click the Get internal link button above the list on the right. The Share Internal Link dialog box appears. Figure 7-8: Share Internal Link dialog box. You can copy the text of the internal link URL for use elsewhere. The link opens an instance of Web Access and displays the linked object. Shared Links A shared link is a URL that points to a specific file or folder within Web Access. This can be useful for providing a trusted partner or contractor with access to a folder or file that they do not have credentials to access directly. Shared links are only available for CIFS shares. You can control how long until the shared link expires, whether a password is required, and who is allowed to create shared links. To create shared links, Shared Links must be enabled for the CIFS share, and the user must have permission. See Web Access Settings on page 109. To create a shared link to a folder or file, select the item, then click the Share public link button above the list on the right. If the button does not appear, either Shared Links is not enabled for the CIFS share, or the user does not have permission. See Web Access Settings on page 109. Nasuni Filer Administration Guide

167 Accessing Data The Share Public Link dialog box appears. Figure 7-9: Share Public Link dialog box. Click On, then select an expiration date and the type of access. If a password is required, enter the password for this item. Click Create. The Share Public Link dialog box appears, displaying the shared link URL. Figure 7-10: Share Public Link dialog box with shared link URL. You can copy the text of the internal link URL for use elsewhere. The link opens an instance of Web Access and displays the linked object. The link works only until the specified expiration date. If a password is required, the password must be entered to access the linked object. Nasuni Filer Administration Guide

168 Accessing Data You can change the shared link for an item by selecting the item with the shared link and clicking the Share public link button above the list on the right. The Share Public Link dialog box appears. Figure 7-11: Share Public Link dialog box. To view the shared link URL again, click Regenerate. You can toggle the shared link On or Off. You can select an expiration date and the type of access. If a password is required, you can enter the password for this item. Click Update. The Share Public Link dialog box appears, displaying the shared link URL. Opening file To access a file, click the file name. If the file is of a format that the browser can handle (such as graphics, text, or HTML), a preview of the file opens in the browser. Streaming video does not work with self-signed certificates. To add a new certificate, see SSL Certificates on page 301. If the file is of a format that the browser does not recognize, you have the option of downloading the file. Alternatively, right-click the file name, and select the desired action from the browser s drop-down list. Nasuni Filer Administration Guide

169 Accessing Data Viewing details To view details of an item, click the View Details button directory, the Directory Info pane appears. to the right of the item. If the item is a Figure 7-12: Directory Info pane. The name of the directory appears, as well as the date last modified. If the item is a file, the File Info pane appears. Figure 7-13: File Info pane. The name of the file appears, as well as the date last modified and the size. You can view any previous versions of the file available by clicking Click to View. If other versions of the file are available, they appear in a list. To access one of the previous versions, click its date and time in the list. Deleting file or empty directory To delete a file or empty directory, select the item, then click the Delete button dialog box appears. Click Delete to delete the item. Note: The directory must be empty before you delete it. in the upper right. A Showing hidden files To show hidden files, click the Settings button files, select Yes, then click Save. on the left. A dialog box appears. To show hidden Nasuni Filer user interface To go to the Nasuni Filer user interface, click the user name in the top right corner, then select Filer Admin Access from the drop-down list. Nasuni Filer Administration Guide

170 Accessing Data Logging out To logout from this page, click the user name in the top right corner, then select Logout from the dropdown list. Nasuni Corporate Web Site To visit the Nasuni corporate Web site, click the user name in the top right corner, then select Visit Nasuni.com from the drop-down list. Nasuni Filer Administration Guide

171 Accessing Data Nasuni Mobile Access You can access data stored in the Nasuni Filer using mobile devices, including ios-based devices (such as iphone and ipad) and Android phones. Nasuni Mobile Access is available for volumes on which the CIFS protocol has been enabled, but not for NFS-only or iscsi-only volumes. You must enable Nasuni Mobile Access for a CIFS share in order to access its folders and files from mobile devices. For details, see step r of Adding a New CIFS Share to a Volume on page 101, or Editing a CIFS Share on page 113. In addition, the mobile device must be enabled, as described in Mobile Access: Managing access by mobile devices on page 237. Tip: To enable mobile access to a CIFS share for some users, but not all users, create a second CIFS share to the same data as the original CIFS share. Then enable mobile access to the second CIFS share and permit only those specific users to have access to the second CIFS share. You must download and install the appropriate Nasuni Mobile Access application for your platform. See Nasuni Desktop and Mobile Access on page 235. Providing Access to the Nasuni Mobile Access Application to Users The Nasuni Mobile application needs the following information to access your Nasuni Filers: host address, port number, and user credentials. The administrator has several options for providing this information to configure the Nasuni Mobile application for users. Several of these methods simplify login, so that the user does not need to know the host or port. Configuring DNS to Simplify User Login The administrator can configure the company DNS server to simplify user login to your Nasuni Filers. A properly configured DNS includes the host and port necessary for Mobile Access. When the user enters their company address and password into the Nasuni Mobile Access application, the application retrieves the host and port from the DNS to simplify the login. See Mobile Access: Configuring DNS to Simplify User Login on page 239. As a result, the user only needs to enter their company address and password, instead of entering their username, password, host, and port. See Logging in to the Nasuni Mobile Access application on page 158. Providing Link to Users The administrator can create a link to share access information for your Nasuni Filers. This link can include the hostname or IP address, the port number, and the username. The administrator can then this link to users to simplify the process of connecting them to Mobile Access. See Mobile Access: Creating an invitation link on page 238. The link has this form: Since the username is optional, the link might also have this form: Opening this link on the mobile device launches the Nasuni Mobile Access application, and fills in information necessary to log in to the Nasuni Filer. The user can then log in to the Nasuni Mobile Access application using Active Directory credentials, which might include the domain, and their username and password. Nasuni Filer Administration Guide

172 Accessing Data Providing Hostname and Port to Users If the administrator has not configured the company DNS server to simplify user login to your Nasuni Filers, the administrator can, alternatively, directly provide the hostname or IP address of the Nasuni Filer, along with the port. If VPN access is required for your mobile deployment, then the hostname should be the internal hostname or IP address and the port should be 443. If direct external access is allowed for mobile devices, then the administrator should provide the external hostname or IP address and port that has been configured. Those should use network address translation (NAT) to re-direct to the internal hostname or IP address and the port 443, or another port that the Administrator has set up for Mobile Access. Logging in to the Nasuni Mobile Access application If the administrator has configured the company DNS server to simplify user login to your Nasuni Filers, the user must first enter their company address and password. If available, the host and port are retrieved from DNS. Figure 7-14: Initial Login screen. Figure 7-15: Initial Login screen when DNS configured for multiple sites. If the administrator has not configured the company DNS server to simplify user login to your Nasuni Filers, but the user has employed the administrator-created link containing the host and port, the user Nasuni Filer Administration Guide

173 Accessing Data must enter Active Directory credentials, which might include the domain, and username and password. The host and port are provided. Figure 7-16: Login screen when using link. If the administrator has not configured the company DNS server to simplify user login to your Nasuni Filers, and the user has not employed the administrator-created link containing the host and port, a login screen similar to Figure 7-14 on page 158 appears. If the user enters their address and password, another login screen appears so that the user can enter the host and port. The user then logs in to the Nasuni Mobile Access application using their Active Directory credentials. Credentials include the domain, username, and password. The domain is optional, depending upon how Active Directory is configured. Figure 7-17: Login screen when entering host, port, and credentials. Nasuni Filer Administration Guide

174 Accessing Data Using the Nasuni Mobile Access application See for a worksheet for planning Nasuni Mobile Access configurations. This section presents some of the actions you can perform using mobile devices. The actions available depend on which mobile platform you are using. The figures show images from an iphone. The screens might appear different on other mobile platforms. After you log in to the Nasuni Mobile Access application, a list of the CIFS shares available on this Nasuni Filer appears. Figure 7-18: Shares available on mobile device. Nasuni Filer Administration Guide

175 Accessing Data Opening CIFS share or folder To open a CIFS share or folder, tap the name of that CIFS share or folder. The contents appear as a list. Figure 7-19: List of folders. To sort the display, tap the Name, File Type, or Modified list headings. Navigating folder hierarchy To navigate to a higher point in the folder hierarchy, tap the left-facing arrow button, on the top left. Nasuni Filer Administration Guide

176 Accessing Data Viewing file information To view information about a folder or file, tap the information icon showing information including the name, size, and date modified. beside its name. A page appears Tagging file or folder as favorite Figure 7-20: File information. To tag a file or folder as a favorite, tap the star icon on the file or folder icon (not the Favorites icon at the bottom of the display). Favorite files and folders remain on the device for off-line access. Note: The files and folders within a favorite folder are not automatically also favorites. You must tag each item as a favorite separately. Downloading file If the Download button is available, you can download the file to the device by tapping Download. Versions of file or folder To see other versions of a file or folder, tap Versions. If other versions of the file are available, they appear in a list. To access one of the previous versions, tap its entry in the list. Nasuni Filer Administration Guide

177 Accessing Data Opening file To open a file, tap the file name. If the file is of a format that the mobile device can handle (such as graphics, text, or PDF), the file opens. (On some mobile platforms, a new display opens on which you can choose an action.) Figure 7-21: Open PDF file. To the file or a link to the file, tap the link icon at the top of the display. To tag the file as a favorite, which ensures that the file remains on the device for off-line access, tap the star icon on the bottom. Note: The files and folders within a favorite folder are not automatically also favorites. You must tag each item as a favorite separately. At the top of the display is a three-dots icon that offers a menu of options for this file. Nasuni Filer Administration Guide

178 Accessing Data Deleting file or empty folder To delete a file or an empty folder, tap Edit in the upper right corner. Then tap the red minus icon to the left of the file or folder to delete. The Delete button appears. Tap Delete. A dialog appears. Tap Delete to delete the item. Tap Done. Uploading file Figure 7-22: Deleting file. To upload a file to a folder, tap the Uploads icon at the bottom of the display. A new page appears. Tap the plus sign in the upper right. A list of available files on the device appears. Navigate to the file to upload and select it. Then navigate to the destination folder. Tap Upload at the bottom of the display. Figure 7-23: Uploading file. Nasuni Filer Administration Guide

179 Accessing Data Creating folder To create a folder, tap the Uploads icon at the bottom of the display. A new page appears. Tap the plus sign in the upper right. A list of available files on the device appears. Select any file. Navigate to the folder in which to create the new folder. Tap Create Folder. Enter a name for the new folder. Tap Create. A new folder is created. Viewing favorite file or folder To view favorite files or folders, tap the Favorites icon at the bottom of the display. A list of favorite files and folders appears. Favorite files remain on the device for off-line access. Figure 7-24: Favorites list. Note: The files and folders within a favorite folder are not automatically also Favorites. You must tag each item as a favorite separately. Nasuni Filer Administration Guide

180 Accessing Data Settings To specify that you stay logged in even when the Nasuni Mobile Access application is not running, tap Settings at the bottom of the display. Then tap On to the right of Stay Logged In. If you have selected Stay Logged In : To use a passcode instead of the full credentials when logging in, tap Settings at the bottom of the display. Then tap On to the right of Use Passcode. Enter the passcode, then verify the passcode. You can then use this passcode when logging in. Figure 7-25: Configuring Settings. To specify that you be warned before attempting to download data when not on a Wi-Fi connection, tap Settings at the bottom of the display. Then tap On to the right of Warn before downloading when not on a Wi-Fi connection?. Logging out To log out from the Nasuni Mobile Access application, tap Settings at the bottom of the display. Then tap Log Out at the top right. A dialog appears warning you that logging out removes all saved data from the device. To continue anyway, tap Remove Data. Otherwise, tap Cancel. Nasuni Filer Administration Guide

181 Accessing Data Nasuni Desktop Client Nasuni combines the best features of consumer file-sharing applications with the secure and robust storage infrastructure that enterprises demand. The Nasuni Desktop Client provides an easy-to-use, enterprise-friendly service for accessing enterprise data. The Nasuni Desktop Client consists of a simple interface to the Nasuni Filer on the user s computer. The Nasuni Desktop Client is available for the following Windows, Linux, and OSX platforms. Operating System x86 x86 64 Windows XP SP2 Yes Yes Windows Vista Yes Yes Windows 7 Yes Yes Windows 8 / 8.1 Yes Yes Ubuntu and above Yes Yes Cent OS Yes Yes OSX Mountain Lion 10.8 OSX Mavericks 10.9 Yes Yes Installation The Nasuni Desktop Client requires a separate installation and configuration on each end user s computer. For more details, see the Nasuni Desktop Client Administrator Guide and the Nasuni Desktop Client User Guide. Configuration You can configure many features of the Nasuni Desktop Client, including the following: Filer name or IP address, and port. Username for the Nasuni Filer. Password for the Username of the Nasuni Filer. Proxy, including proxy type, proxy server and port, and password. Source CIFS share or subdirectory on the Nasuni Filer. Target directory on your local computer. Preferences You can also specify preferences about the processing of the Nasuni Desktop Client, including the following: Exclude any files or directories by name, using wildcards and regular expressions. Nasuni Filer Administration Guide

182 Accessing Data Time between each attempted synchronization between the Desktop Client and the Nasuni Filer. Direction of data flow between the Nasuni Desktop Client and the Nasuni Filer, including Bi- Directional, Only Filer to Client, and Only Client to Filer. Upload of smaller files to the Nasuni Filer before the expiration of the Sync Frequency. Nasuni Desktop Client controls You can perform a number of actions using the Nasuni Desktop Client controls menu. Creating a new connection to a Nasuni Filer You can create a new connection to a Nasuni Filer. Managing existing connections to Nasuni Filers You can manage existing connections to Nasuni Filers. Changing preferences You can change preferences, including the following: Maximum size of the log file in MB. Level of logging. Maximum bandwidth to use to upload data to the Nasuni Filer and to download data from the Nasuni Filer. Updating the connection to the Nasuni Filer You can update the connection to the Nasuni Filer. Viewing revision information of the Nasuni Desktop Client You can view the revision information of the Nasuni Desktop Client. Stopping the Nasuni Desktop Client You can stop the Nasuni Desktop Client. Nasuni Web page You can open the Nasuni Web page. Latest synced files You can view a list of the last 5 synced files. Using files or folders from the Nasuni Filer You select a source share on the Nasuni Filer. Any files or folders in that source share are available in the target directory you select. Within the target directory, navigate to the files or folders you want to use. You can perform actions on any of these files or folders, including opening, copying, and deleting. Note: The specific results of some actions depend on the Connection Direction. Nasuni Filer Administration Guide

183 Accessing Data Adding files or folders to the Nasuni Filer Any files or folders that you add to the target directory that you select are automatically transferred to the source share on the Nasuni Filer that you selected. Note: The specific results of actions depend on the Connection Direction. Warning: If a file changes on the Nasuni Desktop Client and synchronizes with the Nasuni Filer, the Client version of the file overwrites the Filer version of the file if it already exists. To recover an earlier version of the file, use Filer Versions. Warning: When considering synchronizing data in existing folders, especially when the folders already contain data, verify that you want them synchronized. If you want the data to be separate, creating another directory or share that is not synchronized might be preferable. Copy files or folders from any source. Navigate to the target directory you selected. Within the target directory, navigate to the folder where you want to add files or folders. Paste the files or folders into the folder within the target directory. You can verify that any added files or folders are present on the Nasuni Filer by using the File Browser feature of the Nasuni Filer user interface or the Nasuni Management Console user interface. Nasuni Filer Administration Guide

184 Chapter 8: Remote Access Overview Remote access allows one or more Nasuni Filers to connect, using the Nasuni Service, to a volume associated with another Nasuni Filer. Using remote access, your remote locations (registered under the same Nasuni.com account) can connect and collaborate on the same global file system. Remote access requires a volume owner who oversees: Configuring a snapshot retention policy. Managing volume encryption keys. Managing volume access at other locations. Enabling Remote Access To share a volume with other Nasuni Filers associated with your Nasuni.com account, you first must enable remote access on the volume. See Remote Access on page 83. Viewing Remote and Local Volume Connections To view information about all available remote and local Nasuni Filer connections, you use the Volumes page. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. For details on viewing remote and local volume connections, see Viewing Local and Remote Volume Information on page 42 and Viewing Volume Properties on page 55. Connecting to a Remote Volume For details on connecting to a remote volume, see Connecting to a Remote Volume on page 51. Note: The Nasuni Filer must be running version 6.0 or later software in order to connect to a remote volume that has multiple protocols defined (including CIFS, NFS, and FTP). Nasuni Filer Administration Guide

185 Configuring a Sync Schedule Configuring a Sync Schedule You can set the schedule by which a volume synchronizes data from Nasuni s data service. This merges local data with new or changed data from other Nasuni Filers connected to the same volume. You can control how often changes are synchronized from cloud storage. Remote volumes inherit their initial schedules from the master volume the first time the connection is made. For details on the process of configuring a sync schedule, see Sync Scheduling on page 90. Synchronization (Merge) Conflicts During a synchronization or merge, locally changed data is never overwritten with data from other Nasuni Filers connected to the remote volume. As a result, several different types of merge conflicts are possible: Name conflict: For example, files on two different Nasuni Filers are created or renamed with the same name during the same time interval. Metadata conflict: For example, metadata is changed for the same file on two different Nasuni Filers during the same time interval. Data conflict: For example, the data is changed for the same file on two different Nasuni Filers during the same time interval. If a merge conflict occurs during a synchronization or merge, the Nasuni Filer performs these actions: Creates a merge conflict log file in the.nasuni\sync_logs directory. The file name of the merge conflict log file is the date in GMT format. The merge conflict log file contains entries for each merge conflict. Each entry has details about one specific conflict. See Synchronization (Merge) Conflict Log File on page 171. Creates a merge conflict message that points to the.nasuni\sync_logs directory. See Synchronization (Merge) Conflict Messages on page 172. For name conflicts and data conflicts, changes the name of the conflicting file to include details about the conflict. See Name of Conflicting File on page 173. Optionally, sends an to the administrator, if configured. See Settings on page 247. Note: If you enable Global Locking for a folder, synchronization conflicts do not occur unless the lock on a file is broken manually. See Global File Locking on page 190. Synchronization (Merge) Conflict Log File If there are any merge conflicts, information about the merge conflicts is written to a merge conflict log file. These files are located in the.nasuni\sync_logs directory of the volume where the merge conflict occurred. Nasuni Filer Administration Guide

186 Synchronization (Merge) Conflicts For example, this file: \ny_files\.nasuni\sync_logs\ny_files_new York Office_ csv is a summary of the merge conflicts involving the ny_files volume on the New York Office Nasuni Filer during a merge on In the merge conflict sync_logs files, conflict messages include the domain and user names to make it easier to find pertinent conflicts. The information in the merge conflict file is in CSV format, in this form: Such as: <local timestamp>, <GMT timestamp>, <conflict type>, <file name>, <local user>, <local filer>, <remote user>, <remote filer>, <merge version> :28:25EST, :28:25GMT, name conflict, /folder/file.txt, smith, lfiler, jones, rfiler, Full user names are provided. It is the responsibility of the Filer Administrator to determine how best to resolve merge conflicts. Synchronization (Merge) Conflict Messages To view synchronization conflict messages: 1. Click Notifications. 2. Click All Messages to display all messages. New merge conflicts generate an informational message. You can search for messages about merges. Type Merge in the Search text box. Note: Text searches are case-sensitive. Messages such as the following appear: Figure 8-1: Messages Search text box. Figure 8-2: Message about merge conflicts. Nasuni Filer Administration Guide

187 Synchronization (Merge) Conflicts 3. Download the log file to view the log. Log entries look like this: :28:25EST, :28:25GMT, name conflict, /folder/file.txt, smith, lfiler, jones, rfiler, It is the responsibility of the Filer Administrator to determine how best to resolve merge conflicts. Name of Conflicting File In addition, for name conflicts and data conflicts for CIFS volumes, the file name of the conflicting file is changed to include the conflict information, in this format: <original filename> (<name or data> conflict from with suffix> The conflict information in the new file name includes the domain names (truncated to 16 characters), user names (truncated to 16 characters), and names of the Nasuni Filers (truncated to 16 characters) for the two conflicting parties. For example: Note: The domain name and user name information only appear in the name of the merge conflict file if the volume is connected to Active Directory. My_File (data conflict from with It is the responsibility of the Filer Administrator to determine how best to resolve merge conflicts. Nasuni Filer Administration Guide

188 Disconnecting from a Remote Volume Disconnecting from a Remote Volume Disconnect You can disconnect from a volume at a remote location. Tip: Ensure that you first delete the CIFS shares, NFS exports, and FTP directories for the remote volume from which you want to disconnect. See Deleting a CIFS Share on page 115, Deleting an NFS Export on page 125, and Deleting FTP directories on page 133 for details. Caution: Disconnecting from a volume deletes any data in the cache. To protect recently changed data, you can take an on-demand snapshot before disconnecting from the volume. See Take a Snapshot Now on page 54 for details. To disconnect from a remote volume: 1. Click Volumes. Select a remote volume. The Volume properties page appears. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. 2. Click Disconnect Volume. Alternatively, select Disconnect from the Properties drop-down list. The Disconnect Volume page appears. Figure 8-3: Disconnect Volume page. 3. Read any warnings that appear on the Disconnect Volume page. Ensure that the prerequisites mentioned above have been satisfied to avoid data loss. 4. Enter a Username (case-sensitive) and Password (case-sensitive) that has permission to perform this operation. Nasuni Filer Administration Guide

189 Disconnecting from a Remote Volume 5. To disconnect the remote volume from your Nasuni Filer, click Disconnect. The message Disconnected volume appears. Click x to close the message. Data on the remote volume is no longer accessible. Nasuni Filer Administration Guide

190 Chapter 9: File Browser Page File Browser Synchronous snapshots are saved to cloud storage periodically (as frequently as hourly for unshared volumes; as frequently as every minute for shared volumes), which allows you to roll back a file or an entire directory to any point in its history. You can restore files or folders from a CIFS or NFS volume or FTP directory, and entire iscsi volumes, that are managed by the Nasuni Filer. During a restore procedure, saved data is recovered from cloud storage. Note: The File Browser page, and all other pages of the Nasuni Filer user interface, might look different to different users. Also, different menus and actions might be available for different users. This is because different users are assigned different permissions, based on their roles in the role-based access control system. See Users and Groups on page 315 for details. What is a Snapshot? A snapshot is a complete picture of the files and folders in your file system at a specific point in time. With snapshots, the Nasuni Filer can identify new or changed data. Snapshots offer data protection by enabling you to recover a file deleted in error or to restore an entire file system. After a snapshot has been taken and is sent to cloud storage, it is not possible to modify that snapshot. With snapshots, you can find, view, and restore past versions of your files quickly. You can restore a single file, a directory, or an entire volume. The Nasuni Filer captures complete snapshots of files at regular intervals and stores all snapshots in cloud storage to protect your files. You can select which days of the week on which to perform snapshots; what time of day to start and stop creating snapshots; and the frequency for creating snapshots. If the volume does not have Remote Access enabled, your frequency choices are every 1, 2, 4, 8, 12, or 24 (hours). If the volume does have Remote Access enabled, your frequency choices are every 1, 5, 10, 15, 25, or 30 (minutes), or 1, 2, 4, 8, 12, or 24 (hours). For example, you can configure snapshots to not occur during work-time and only push new and changed data during off-hours when network usage is low. For details, see Snapshot Scheduling on page 88. You can retain all snapshots indefinitely, which is the default. Or, for compliance purposes or your own best practices, you can specify to delete older snapshots from cloud storage, based on a configured policy for a specific volume. For details, see Snapshot Retention on page 94. Nasuni Filer Administration Guide

191 File System Browser File System Browser You can use the file system browser to perform a variety of tasks: Browse folders and files in volumes on the Nasuni Filer. Search for folders and files by name. Filter results by date. Examine multiple versions of folders and files. Download folders and files. Bring volumes, folders, and files into the cache. Pin individual folders in the cache. Enable Global File Locking for volumes. Enable Auto Cache for individual folders. Create quotas for volumes and folders. Restore a file or folder (for a CIFS or NFS volume or FTP directory) or an entire volume (for an iscsi volume). You can do this, for example, if data has been deleted erroneously. For details on restoring data in the event of a disaster, see Disaster Recovery on page 376. In order to access folders and files, ensure that you have performed these necessary tasks: Have configured at least one volume. For more information, see Adding a Volume on page 46. For CIFS and NFS volumes or FTP directories, have shared or exported at least one volume or FTP directory. For more information, see Adding a New CIFS Share to a Volume on page 101, Adding an NFS Export to a Volume on page 117, and Adding FTP directories for a volume on page 127. (Optional) Have configured a snapshot schedule to ensure that reliable, periodic snapshots of the volume are taken. For more information, see Snapshot Scheduling on page 88. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. Ensure that the Nasuni Management Console is running version 5.5 or later. Selecting Volume, Folder, or Files You can select a volume, a folder, or one or more files. You can select by browsing or by searching. Nasuni Filer Administration Guide

192 File System Browser Browsing a Volume Browse To browse folders and files in a volume, follow these steps: 1. Click File Browser. The File System Browser page appears. Figure 9-1: File System Browser page. 2. From the Volume drop-down list, select a volume name. Figure 9-2: Volume drop-down list. The properties of the selected volume are displayed. The volume properties include: Figure 9-3: Volume properties. Volume: The name of the volume and Nasuni Filer. Content Size: The size of the volume and its contents. Ownership: The owner of the volume. Cache Resident: (CIFS and NFS volumes and FTP directories.) Indicates whether the folder is currently in the cache (Yes) or not (No). Note: iscsi volumes are always resident in the cache. Global Locking: (For folders.) Indicates whether Global Locking is enabled for the volume (Enabled). If this Global Locking status is inherited, includes the word Inherited. If the Global Locking mode is Optimized, includes the word Optimized. To enable Global Locking for a volume, see Global File Locking on page 190. Pinning: (For folders.) Indicates whether the folder is pinned in the cache (Enabled). To enable pinning for a folder, see Pinning Folders in the Cache on page 188. Nasuni Filer Administration Guide

193 File System Browser Auto Cache: (For folders.) Indicates whether Auto Cache (automatically bringing data from other Nasuni Filers into the local cache immediately) is enabled for the folder. To enable Auto Cache for a folder, see Enabling Auto Cache for Folders on page 189. The files and folders that reside on the selected volume are displayed. Figure 9-4: Files and folders on the volume. Note: You cannot browse files and folders on an iscsi volume. 3. From the list of files and folders you can select the following: One folder: select the folder you want. The selected folder is highlighted in the list. The properties of the selected folder are displayed. The folder properties include: Figure 9-5: Folder properties. Location: The path to the folder. Content Size: The size of the folder and its contents. Ownership: The owner of the folder. Cache Resident: (CIFS and NFS volumes and FTP directories.) Indicates whether the folder is currently in the cache (Yes) or not (No). Global Locking: If Global Locking is enabled for the volume, indicates whether the folder is Locked or Unlocked. To enable Global Locking for a volume, see Global File Locking on page 190. Nasuni Filer Administration Guide

194 File System Browser Pinning: (For folders.) Indicates whether the folder is pinned in the cache (Enabled). To enable pinning for a folder, see Pinning Folders in the Cache on page 188. Auto Cache: (For folders.) Indicates whether Auto Cache (automatically bringing data from other Nasuni Filers into the local cache immediately) is enabled for the folder. To enable Auto Cache for a folder, see Enabling Auto Cache for Folders on page 189. One file: select the file you want. The selected file is highlighted in the list. The properties of the selected file are displayed. The file properties include: Figure 9-6: File properties. Location: The path to the file. Size: The size of the file. Ownership: The owner of the file. Cache Resident: (CIFS and NFS volumes and FTP directories.) Indicates whether the file is currently in the cache (Yes) or not (No). Lock Status: If Global Locking is enabled for the volume, indicates whether the file is Locked or Unlocked. To enable Global Locking for a volume, see Global File Locking on page 190. If locked by multiple Nasuni Filers, a list appears. Figure 9-7: Locked by multiple Nasuni Filers. Pinning: (For files.) Indicates whether the folder that contains the file is pinned in the cache (Enabled). To enable pinning for a folder, see Pinning Folders in the Cache on page 188. Auto Cache: (For files.) Indicates whether Auto Cache (automatically bringing data from other Nasuni Filers into the local cache immediately) is enabled for the folder that contains the file. To enable Auto Cache for a folder, see Enabling Auto Cache for Folders on page 189. You can now perform actions with the selected folder or file, as described in Actions with Selected Volume, Folder, or Files on page 185. You can also filter the current results by date, as described in Filtering by Date on page 181. Nasuni Filer Administration Guide

195 File System Browser Filtering by Date By default, the current contents of the volume are displayed. To select contents from another date and time from available snapshots, follow these steps: 1. Navigate to a volume as described in Browsing a Volume on page Click the Version drop-down list. A calendar of available dates appears. Select the date, then select the snapshot on that date. The folders and files from that snapshot appear. Note: Some dates do not have snapshots. When you click a date with no snapshots, the message There are no snapshots for the selected date. appears. Folders and files from snapshots display the date and time of the version in addition to their other properties. 3. Select a folder or file from the list. To select multiple individual items from snapshots, use Ctrl+click. To select a range of items from snapshots, use Shift+click. 4. To select the current version of folders and files, click the Version drop-down list and select Current Version. You can now perform actions with the selected folder or files, as described in Actions with Selected Volume, Folder, or Files on page 185. Nasuni Filer Administration Guide

196 File System Browser Searching for a Folder or File by Name Search In addition to browsing for folders and files, you can also search for a specific folder or file by name within a snapshot, and then select it for further actions. Caution: In most cases, snapshots are not in the local cache, and must be brought into the local cache to be searched. As a result, snapshot searches can impact performance. Searching a large number of snapshots proceeds better by using a Nasuni Filer that users are not using heavily at the same time. Note: iscsi volumes do not contain folders or files, so you cannot search them. To search for a folder or file by name in a snapshot, follow these steps: 1. Navigate to a volume as described in Browsing a Volume on page 178. If you intend to restrict the search to a specific directory, navigate to that directory. 2. Click Search. The Search Versions dialog box appears. Figure 9-8: Search Versions dialog box. 3. The default is to search all directories. To limit the search to the currently selected directory (and any subdirectories), select Start from Current Folder. Limiting the search can save time. 4. The default is to search all versions. To specify search dates, click the Date Range box. The Date Range list appears. Figure 9-9: Date Range list. Nasuni Filer Administration Guide

197 File System Browser 5. From the list, select one of these options for the search date: Today: Searches snapshots from today. All Versions: Searches all snapshots regardless of date. This is the default. Caution: Searching all snapshots can take a long time and add extra load to your Nasuni Filer. Last 7 Days (if available): Searches only snapshots from the past 7 days, if there are any available. Caution: Searching large numbers of snapshots can take a long time and add extra load to your Nasuni Filer. Last 30 Days (if available): Searches only snapshots from the past 30 days, if there are any available. Caution: Searching large numbers of snapshots can take a long time and add extra load to your Nasuni Filer. Custom Range: Opens the Custom Range pane for you to select a start date and an end date within which to search snapshots. Figure 9-10: Custom Range pane. Navigate to the start date and the end date during which to search snapshots. Caution: Searching large numbers of snapshots can take a long time and add extra load to your Nasuni Filer. Nasuni Filer Administration Guide

198 File System Browser 6. Enter all or part of the name of the folder or file to search for in the Query text box. Note: You can use glob syntax wildcards when you specify the name, such as the following: Wildcard Meaning Example * Matches any number of any character.? Matches any one character. *.mp3 means any file name that ends with mp3. test.mp? means file names like test.mp3 or test.mp4. [sequence] [!sequence] Matches any character in the specified sequence. Matches any character NOT in the specified sequence. [A-Z]*.mp3 means file names that start with an upper-case letter. [!A-Z]*.mp3 means file names that do not start with an uppercase letter. The search matches the query text within a folder or file name. For example, searching for mount finds items named Mount, mounted, unmounted, and unmount. The search is not case-sensitive. Optionally, you can specify searching for the exact name of the file (including the filename extension) or folder by selecting the Exact Match check box. In this case, searching for mount only finds items named mount. This search is also not case-sensitive. 7. Click Search. The Search Status results appear in a list. Figure 9-11: Search Status results. To cancel a running search before it completes, click Stop Search. 8. After the search completes, click a folder or file in the list to highlight it. 9. Click Navigate to Selected to navigate to the selected item. The folder or file you searched for is selected. You can now perform actions with the selected folder or file, as described in Actions with Selected Volume, Folder, or Files on page 185. Nasuni Filer Administration Guide

199 File System Browser Actions with Selected Volume, Folder, or Files After selecting a volume, folder or files, as described in Selecting Volume, Folder, or Files on page 177, you can perform the following actions: Bring volume, folder, or files into the cache. Create quotas for folders. Download folders and files. Pin individual folders in the cache. Enable Global File Locking for volumes. Enable Auto Cache for individual folders. Restore a file or folder (for a CIFS or NFS volume and FTP directories) or an entire volume (for an iscsi volume). Bringing Data into Cache Bring into cache When a volume, folder, or file is selected that is not already in the cache, you can bring that item into the cache. Note: If the selected data is not already present in the Nasuni Filer s cache, selecting Bring into Cache begins the process of copying the selected data into the cache. This process continues running in the background until all the selected data is copied into the cache. If the size of the selected data exceeds the available space in the cache, then the Nasuni Filer releases already-protected data from the cache to make room for the incoming data. This process affects network bandwidth until it has completed. If the user requests any of the selected data while this process is running, the requested data is copied into the cache immediately. To bring data into the cache, follow these steps: 1. Select a volume, folder or file as described in Selecting Volume, Folder, or Files on page 177. Note: You can only bring data selected from Current Version into the cache. Note: You cannot bring files infected with malware into the cache. 2. Click Bring into Cache. The Bring Into Cache dialog box appears. The dialog box is slightly different with volumes, folders, and files. Figure 9-12: Bring Volume Into Cache dialog box. Nasuni Filer Administration Guide

200 File System Browser a. Information about the volume, folder, or file is displayed, as well as the amount of space currently available in the cache. b. (For volume or folder only) To bring only the metadata of the volume or folder into the cache, but not the data itself, select the Bring Metadata Only check box. c. Click Start Transfer. This begins the process of copying data and metadata into the local cache. When the process is complete, a notification indicates that the process is complete and, if configured, an indicates that the process is complete. Setting Quota or Rule Create You can set a quota on the contents of a volume or a folder. You can configure quota reports to be sent to administrators or users when volumes or folders approach or exceed their quota. To set a volume or folder quota, follow these steps: 1. Select a volume or folder as described in Selecting Volume, Folder, or Files on page Click Set Quota or Rule. The Set Quota or Rule dialog box appears. 3. Verify the location in the Location text box. Figure 9-13: Set Quota or Rule dialog box. Nasuni Filer Administration Guide

201 File System Browser 4. From the Quota Type drop-down list, select one of the following choices: Rule: Applies the specified Limit to any newly created subdirectories of the selected volume or folder. To apply the specified Limit to existing subdirectories, see step 7 on page 187 below. Important: Quotas cannot be nested. Quotas cannot be created anywhere in a directory tree that already has a quota set in one of the parents. Quotas also cannot be created on any parent directory when any of the subdirectories has a quota already. Quota: Applies the specified Limit only to the selected volume or folder. 5. (Optional) To receive reports when the selected volume or folder is near or over its Limit, in the text box, enter a comma-separated list of address. Tip: If User Folders Support is enabled for the CIFS share that the directory is in, then the address of the directory owner is used automatically. This prevents the necessity of manually entering hundreds of addresses for multi-user systems. See step q on page 107. However, if addresses are entered here, the entered addresses override looking up an address from Active Directory. 6. In the Limit text box, enter or select the quota limit (in gigabytes or fractions of a gigabyte, such as 6.8). The current usage is displayed to help you decide on a quota limit. 7. For the Rule quota type, to apply the same Limit to the data in any existing sub-directories of the selected directory, select the Apply to existing sub-directories check box. 8. Click Save Quota or Save Rule to save your changes. Otherwise, click Cancel. The quota is enabled as configured. Downloading Files Download You can download one or more files to your local computer. To download one or more files, follow these steps: 1. Select one or more files as described in Selecting Volume, Folder, or Files on page Click Download File. Downloading features depend on your Web browser. If the file is of a type that your Web browser recognizes (such as a PDF file), the file might download and display directly in the browser. If the Web browser cannot directly display the file, navigate to a location where the file should be saved. Tip: Although users with Perform File Restores/Access Versions permission have the ability to access all files on the file server, clicking Download File results in permission denied. The selected files are downloaded to your local computer. Nasuni Filer Administration Guide

202 File System Browser Pinning Folders in the Cache Pin folder Pinning a folder specifies that the folder and its contents must remain in the local cache at all times. This can improve performance and reduce the time necessary to return accessed data to clients. Warning: Enabling this feature means that the entire folder, and all the folder s contents, remain resident in the cache at all times. This reduces the available cache by the size of the folder. If the amount of data pinned in the cache exceeds the size of the cache, you are not able to access data that is not in the cache. If this occurs, an Alert notification is given. Note: Pinning a folder does not bring the folder s data into the cache. If the folder s data is not already present in the cache, you must specifically bring that data to the cache. To check on whether data is resident in the cache, see Browsing a Volume on page 178. To bring data to the cache, see Bringing Data into Cache on page 185. Note: All iscsi (SAN) volume data is already pinned in the cache, so it is not necessary to pin iscsi volumes. To view pinned folders, or disable pinning for a folder, see Pinned Folders on page 96. See for a worksheet for planning configurations. To pin a folder in the cache, follow these steps: 1. Select a folder as described in Selecting Volume, Folder, or Files on page 177. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. 2. Click Edit Cache Settings. The Folder Cache Settings dialog box appears. Figure 9-14: Folder Cache Settings dialog box. 3. Select Enable Pinning. 4. Click Save Settings. Your changes are saved. Otherwise, to close the dialog box without saving changes, click Close. Nasuni Filer Administration Guide

203 File System Browser Enabling Auto Cache for Folders Enable If you enable the Auto Cache option for a folder, new data in that folder is brought into the local cache immediately from other Nasuni Filers that are attached to this volume. Otherwise, new data is brought into the local cache from other Nasuni Filers when that data is accessed next. Tip: Because Auto Cache is not enabled by default, new data in the folder comes into the local cache only when requested. If you plan on enabling Auto Cache, ensure that all of the following apply to your deployment: All the Nasuni Filers on which you plan to enable Auto Cache have caches large enough to contain data from the other Nasuni Filers. All the data in the folder is relevant and appropriate for all other sites that access the folder. Network access at each site is not adversely affected by automatically moving large quantities of data. Auto Cache should not be used during the initial transfer of data into a Nasuni Filer or during certain one-time operations, such as a bulk data load. Note: Before enabling Auto Cache for a folder, the folder s volume must have Remote Access enabled and Auto Cache enabled. For details, see Setting Remote Access on page 83 and Enabling or Disabling Auto Cache for Volumes on page 86. Note: Auto Cache is only available for shared or remote volumes. Note: If Auto Cache is enabled and you disable Auto Cache, any process bringing data into the cache continues until complete. To enable Auto Cache for a folder, follow these steps: 1. Select a folder as described in Selecting Volume, Folder, or Files on page Click Edit Cache Settings. The Folder Cache Settings dialog box appears. Figure 9-15: Folder Cache Settings dialog box. 3. Select Enable Auto Cache. 4. Click Save Settings. Your changes are saved. Otherwise, to close the dialog box without saving changes, click Close. Nasuni Filer Administration Guide

204 File System Browser Global File Locking Lock The purpose of the Global Locking feature is to prevent conflicts when two or more users attempt to change the same file on different Nasuni Filers. If you enable the Global Locking feature for a directory and its descendants, any files in that directory or its descendants can only be changed by one user at a time. Any other users cannot change the same file at the same time. Typically, when User X opens a file to change it, the application locks the file, preventing access by User Y. Applications and platforms differ on specific behavior. User Y might receive the option of opening a Read-Only copy of the file, opening a copy of the file with a different name, or receiving a notice when User X closes the file. When User X does close the file, User Y can then access the file. Tip: Enabling Global Locking can have an impact on performance, depending on factors that include network congestion, user load, and file sizes. Do not enable Global Locking until after initial data load and after large data migrations. If users do not typically collaborate on the same file at the same time, it is unnecessary to enable Global Locking. You can also manually break the locking of a file. This might become necessary if a user leaves a file open and another user needs to open that file. Warning: If you manually break the locking of a file, this might result in conflicts for the file. See Synchronization (Merge) Conflicts on page 171. Note: If a user continues using a file after the lock is manually broken, the file might become locked again. Enabling Global Locking To enable Global Locking for a folder (which can be a volume) and its descendants, follow these steps: 1. Select a folder as described in Selecting Volume, Folder, or Files on page Click Edit Global Locking Settings. The Global Locking Setting dialog box appears. 3. Select Enable Global Locking. Figure 9-16: Global Locking Setting dialog box. 4. From the Locking Mode drop-down list, select one of the following locking modes: Optimized: Recommended for most applications that don t rely heavily on share access modes. Optimized locking gives the best performance, but lower protocol compatibility. Note: NFS volumes only support Optimized mode locking. Nasuni Filer Administration Guide

205 File System Browser Advanced: Recommended for applications that rely on share access modes. Advanced locking provides the highest global locking compatibility, but might impact performance. 5. Click Save Settings. Your changes are saved. Otherwise, to close the dialog box without saving changes, click Close. Breaking Global Locking To break Global Locking for a file, follow these steps: 1. Select the file as described in Selecting Volume, Folder, or Files on page Click Break Global Lock. The Break Global Lock dialog box appears. Figure 9-17: Break Global Lock dialog box. 3. Click Break Lock. The lock for the file is released, allowing other users to open the file. Otherwise, to close the dialog box without making changes, click Close. Nasuni Filer Administration Guide

206 File System Browser Restoring Volume, Folder, or Files Restore You can restore a stored version of a volume, folder, or files. You might do this if data was erroneously destroyed or corrupted, or if you need a previous version. You can restore the data to its original location, or to another location. To restore data from a snapshot, follow these steps: 1. Select a volume, folder, or files in a snapshot as described in Selecting Volume, Folder, or Files on page 177. Tip: You can tell that you have selected files or a folder in a snapshot if the Version displays a date and not Current Version. 2. Click Restore Folder or Restore File. The Restore Folder or Restore File dialog box appears Figure 9-18: Restore Folder dialog box. 3. Verify the selection in the Selection text box. 4. By default, the file or folder is restored to its original location. To restore the file or folder to another path, click in the Destination box and navigate to the alternative path. Caution: If the file or folder is restored to its original location, it replaces the file or folder of the same name (if any) in that original location. 5. To back up existing files before proceeding, select the Back Up Existing check box. If any files that you selected to restore also exist in your volume, they are copied and retained. Backup files are created with the preface backupxxxx. For example, backup0001.sales.doc. Caution: If Back Up Existing is not selected, the restore overwrites any files with the same name. Nasuni Filer Administration Guide

207 File System Browser 6. To restore the selected files or folder to your system, click Restore File or Restore Folder. The Restore in Progress pane appears. Figure 9-19: Restore in Progress pane. This pane includes the following: The number of folders processed. The number of files processed. Note: Files and folders in the snapshots are not deleted or changed during the restore. The restored files or folder appear in the specified folder. Nasuni Filer Administration Guide

208 Using Snapshot Directory Access Using Snapshot Directory Access For CIFS and NFS volumes, you can browse the recent snapshot history and view files and directories within a volume. Tip: If multiple protocol volumes are enabled, the.snapshot directory is hidden. For NFS volumes, ensure that you have met the following criteria: Configured at least one NFS volume and created at least one NFS export. For more information, see Adding a Volume on page 46 and Adding an NFS Export to a Volume on page 117. Enabled the Snapshot Directory Access option on the Volume properties page. For more information, see Snapshot Directory Access on page 92. Configured (optional) a snapshot schedule to ensure that reliable, periodic snapshots of the NFS volume are taken. For more information, see Snapshot Scheduling on page 88. Caution: If a user creates a directory named.snapshot on an NFS volume, and the Snapshot Directory Access setting is enabled on that volume, the user-created directory might appear to be empty or might hide any user-created content. We suggest that users not create directories named.snapshot on NFS volumes with Snapshot Directory Access enabled. For CIFS volumes, ensure that you have met the following criteria: Configured at least one CIFS volume and created at least one CIFS share. For more information, see Adding a Volume on page 46 and Adding a New CIFS Share to a Volume on page 101. Enabled the Snapshot Directory Access option on the Volume properties page. For more information, see Snapshot Directory Access on page 92. Enabled snapshot access for the CIFS share. For more information, see Adding a New CIFS Share to a Volume on page 101 and Editing a CIFS Share on page 113. Configured (optional) a snapshot schedule to ensure that reliable, periodic snapshots of the CIFS volume are taken. For more information, see Snapshot Scheduling on page 88. Accessing CIFS and NFS Snapshot Directories using Windows A.snapshot directory is located in every directory of a volume that was successfully included in at least one snapshot, and that has not been removed as the result of a snapshot retention policy (see Snapshot Retention on page 94). You can navigate to the.snapshot directory, change the current directory to the.snapshot directory, and locate files within directory trees. Tip: To simplify access to snapshot directories in Windows, map a network drive to a CIFS share, as described in Mapping a Windows network drive to a CIFS share on page 143. Tip: If multiple protocol volumes are enabled, the.snapshot directory is hidden. Each.snapshot directory contains one or more subdirectories that correspond to each snapshot taken, and whose name includes the date and time GMT that it was created, such as 2013_07_22_ GMT. Nasuni Filer Administration Guide

209 Using Snapshot Directory Access Typically, the.snapshot directories are hidden from directory listings. On Windows systems, this includes the dir command and Windows Explorer, although you can configure Windows Explorer to show hidden files and folders. For example, the.snapshot directory is not visible in this listing (in which the CIFS share district has been mapped to the Windows drive X:): X:\>dir Volume in drive X is district Directory of X:\ 03/28/ :12 PM <DIR>. 05/03/ :56 PM <DIR>.. 2 Dir(s) 64,246,075,392 bytes free There are two default directories listed; however, the directory called.snapshot is not visible. However, you can still change to the.snapshot directory (assuming that access to this directory is enabled): X:\>cd.snapshot X:\.snapshot> X:\.snapshot>dir Volume in drive X is district Directory of X:\.snapshot 03/28/ :12 PM <DIR>. 03/28/ :12 PM <DIR>.. 03/28/ :12 PM <DIR> 2013_05_08_ GMT 03/28/ :12 PM <DIR> 2013_05_04_ GMT 03/28/ :12 PM <DIR> 2013_05_03_ GMT 03/28/ :12 PM <DIR> 2013_04_19_ GMT 03/28/ :12 PM <DIR> 2013_04_12_ GMT 03/28/ :12 PM <DIR> 2013_03_28_ GMT 03/26/ :25 PM <DIR> 2013_03_26_ GMT 03/29/ :11 PM <DIR> 2013_03_26_ GMT 0 File(s) 0 bytes 11 Dir(s) 64,246,075,392 bytes free Nasuni Filer Administration Guide

210 Using Snapshot Directory Access You can also access the.snapshot directories using Windows Explorer: Figure 9-20:.snapshot directory in Windows Explorer. Accessing CIFS and NFS Snapshot Directories using UNIX A.snapshot directory is located in every directory of a volume that was successfully included in at least one snapshot, and that has not been removed by a snapshot retention policy. You can navigate to the.snapshot directory, change the directory to the.snapshot directory, and locate files within directory trees. Note: All.snapshot directories have read-only access. You can read the files and directories contained in the snapshot directories; however, you cannot move, delete, or edit files and directories. Tip: If multiple protocol volumes are enabled, the.snapshot directory is hidden. For example, the.snapshot directory is not visible in this listing: Server1: user1$ ls -lah total 32 drwxrwxrwx 5 root wheel 4.0K Apr 13 11:12. drwxr-xr-x 3 user1 staff 102B Apr 13 14:59.. drwxr-xr-x 2 root wheel 4.0K Apr 12 16:59 folder_one drwxr-xr-x 2 root wheel 4.0K Apr 12 14:38 folder_two There are two directories listed; however, the directory called.snapshot is not visible. However, you can still change to the.snapshot directory (assuming that access to this folder is enabled): Server1: User1$ cd.snapshot Server1:.snapshot User1$ For example: sys:local$ cd /mnt/filer/export sys:export$ cd dir1 sys:dir1$ cd dir2 sys:dir2$ cd.snapshot sys:.snapshot$ ls Nasuni Filer Administration Guide

211 Using Snapshot Directory Access Accessing Files in Snapshot Directories The file system for snapshot directories and the content in the directories is read-only. Tip: If multiple protocol volumes are enabled, the.snapshot directory is hidden. Once inside a.snapshot directory, you can list the contents. For example, in UNIX: In Windows: Server1:.snapshot User1$ ls 2013_04_04_ GMT 2013_04_05_ GMT 2013_04_05_ GMT 2013_04_07_ GMT 2013_04_12_ GMT 2013_04_05_ GMT X:\.snapshot>dir 03/28/ :12 PM <DIR>. 03/28/ :12 PM <DIR>.. 03/28/ :12 PM <DIR> 2013_05_08_ GMT 03/28/ :12 PM <DIR> 2013_05_04_ GMT 03/28/ :12 PM <DIR> 2013_05_03_ GMT The directories within a.snapshot directory have names that correspond to the time when each snapshot was taken. For example, this directory: 2013_04_12_ GMT refers to a snapshot that was taken on April 12 th, 2013 at 18:39:17 GMT: You can navigate to one of the listed directories to display the version of the file system that was available from that location at the time of the snapshot. Listing the contents of a snapshot directory can take time, because this data might not be in the local cache and might have to be retrieved from cloud storage. See Searching for a Folder or File by Name on page 182 for more information. The snapshots within the.snapshot directories include the following 45 snapshots, if they are available: The last 10 snapshots. The last 12 hourly snapshots, by hour. The last 7 daily snapshots, by day. The last 4 weekly snapshots, by week. The last 12 monthly snapshots, by month. To access other snapshots, use the Nasuni Filer user interface to access this data. Nasuni Filer Administration Guide

212 Using Snapshot Directory Access Restoring a File or a Folder from a Snapshot Directory You can restore a file or a folder from a snapshot. To restore a file or directory: 1. Navigate to the directory that contains the file or folder to restore. 2. In that directory, navigate to the.snapshot directory. Tip: If multiple protocol volumes are enabled, the.snapshot directory is hidden. 3. In the.snapshot directory, navigate to the directory for the specific snapshot you want. 4. Copy the files or directories from the snapshot directory to the target location. For example, in UNIX: Station1:.snapshot User2$ cd 2013_04_12_ GMT Station1:2013_04_12_ GMT User2$ ls file_1.txt file_3.txt Station1:2013_04_12_ GMT User2$ cp file_1.txt /some/other/ place For example, in Windows: X:\>cd docs X:\docs>cd.snapshot X:\docs\.snapshot>cd 2013_05_18_ GMT X:\docs\.snapshot\2013_05_18_ GMT>dir Volume in drive X is district 05/18/ :56 AM <DIR>. 05/18/ :56 AM <DIR>.. 05/17/ :37 AM 106,502 hw_gs_guide_5.0.pdf 04/09/ :14 PM 2,787,760 Administration_Guide_5.0.pdf X:\docs\.snapshot\2013_05_18_ GMT>copy hw_gs_guide_5.0.pdf c:\ You can also restore folders or files using the Nasuni Filer user interface, as detailed in Restoring Volume, Folder, or Files on page 192. Nasuni Filer Administration Guide

213 Chapter 10: Services Page Services The Services page enables you to: Configure and schedule data migrations, which are an efficient way to copy bulk data into the Nasuni Filer using the Data Migration Service. Configure and perform a Side Load, transferring data from a source Nasuni Filer to a destination (new) Nasuni Filer. The source Nasuni Filer must already be decommissioned. Configure the Mobile Service, which enables access to the Nasuni Filer using mobile devices such as iphones, ipads, and Android phones. Place this Nasuni Filer under the management of the Nasuni Management Console. Enable the Remote Support Service, which simplifies access for Nasuni Technical Support. Send diagnostic information to Nasuni. Note: The Services page, and all other pages of the Nasuni Filer user interface, might look different to different users. Also, different menus and actions might be available for different users. This is because different users are assigned different permissions, based on their roles in the role-based access control system. See Users and Groups on page 315 for details. Note: If this Nasuni Filer is under the control of the Nasuni Management Console, some menus and menu choices might look different, because you use the Nasuni Management Console to perform these tasks. Nasuni Filer Administration Guide

214 Data Migration Data Migration After you have configured the Nasuni Filer, the best way to load your data to a volume is by using the Data Migration Service. This feature supports multiple sources and targets for migrations using the CIFS or NFS protocols. The Data Migration Service copies files; it does not move them. Therefore, the source data is not modified during the migration process. While a migration is running, you can configure and schedule additional migrations to run one after the other. Migration procedures can only run one at a time. Note: Data migration is only available for CIFS and NFS volumes, not iscsi volumes. Note: The Data Migration Service can only migrate files that it has permission to access. Ensure that the user you specify has permission to read all the files in the CIFS share that you plan to copy. If the user cannot read all files in the source CIFS share, then the migration cannot run properly. Therefore, you should specify a user with administrative or backup operator privileges. Note: The Data Migration Service does not maintain the sparseness of sparse files when migrated. Therefore, the size of a migrated sparse file might differ from the size of the source file. Important: The Data Migration Service uses the cache. To ensure that the Data Migration Service has enough space, set Cache Settings to 30 percent or greater. See Cache Settings on page 333. Configure Configuring a data migration procedure requires the following steps: Services View 1. Configuring the migration source, as in Configuring a CIFS Migration Source on page 201 or Configuring an NFS Migration Source on page Configuring the data migration itself, as in Configuring a CIFS Data Migration on page 205 or Configuring an NFS Data Migration on page 213. Since the procedures for CIFS and NFS data migrations are slightly different, they are addressed separately. Nasuni Filer Administration Guide

215 Data Migration Configuring a CIFS Migration Source Create Before you configure a CIFS migration source, ensure that you have a source CIFS volume and CIFS share configured. See Adding a Volume on page 46 and Adding a New CIFS Share to a Volume on page 101 for more information. To configure a migration source for a CIFS share: 1. Click Migration Sources. The Migration Sources page appears. Figure 10-1: Migration Sources page. 2. Click Add CIFS Source. The Create/Reconnect CIFS Migration Source dialog box appears. Figure 10-2: Create/Reconnect CIFS Migration Source dialog box. 3. In the Source Server text box, enter the source server s IP address or hostname. 4. In the Source Share Name text box, enter the name of the CIFS share on the source server. For example, files. Nasuni Filer Administration Guide

216 Data Migration 5. In the User Name and Password text boxes, enter a User Name (case-sensitive) and Password (case-sensitive) that has permission to perform this operation. For any Active Directory CIFS shares, the username must be in the form of domain\username. Note: Depending on the settings of the CIFS share, the username and password might be optional. Note: Ensure that the user you are specifying has permission to read all the files in the CIFS share that you plan to copy. If the user cannot read all files in the source CIFS share, then the migration cannot run properly. Therefore, you should specify a user with administrative or backup operator privileges. 6. To retain the User Name and Password in order to automatically reconnect with the source after rebooting the Nasuni Filer, select Retain Passwords from the Password Retention drop-down list. Alternatively, to not retain passwords, select Do not retain passwords (best security) from the Password Retention drop-down list. Tip: The security best practice is to not retain passwords. Caution: If you select Retain Passwords, Nasuni authorized support personnel who can access the Nasuni Filer s disks could possibly recover the retained User Name and Password. 7. To add the specified CIFS migration source, click Connect to Source. The CIFS migration source that you added is displayed. Figure 10-3: Added CIFS migration source. The migration source is saved for re-use. If you want to disconnect from the migration source, see Disconnecting from (deleting) a Migration Source on page 227. See Configuring a CIFS Data Migration on page 205 to continue. Nasuni Filer Administration Guide

217 Data Migration Configuring an NFS Migration Source Ensure that you have a source NFS volume and NFS export configured before configuring an NFS migration source. See Adding a Volume on page 46 and Adding an NFS Export to a Volume on page 117 for more information. To create a migration source for an NFS export: 1. Click Migration Sources. The Migration Sources page appears. Figure 10-4: Migration Sources page. 2. Click Add NFS Source. The Create/Reconnect NFS Migration Source dialog box appears. Figure 10-5: Create/Reconnect NFS Migration Source dialog box. 3. In the Source Server text box, enter the source server IP address or hostname. 4. In the Source Path text box, enter the source directory path exported by the source server. 5. Click Connect to Source to add the NFS migration source. The NFS migration source that you added is displayed. Figure 10-6: Added NFS migration source. Nasuni Filer Administration Guide

218 Data Migration The migration source is saved for re-use. If you want to disconnect from the source, see Disconnecting from (deleting) a Migration Source on page 227. See Configuring an NFS Data Migration on page 213 to continue. Nasuni Filer Administration Guide

219 Data Migration Configuring a CIFS Data Migration Before you configure a CIFS migration, ensure that you have a source CIFS volume and CIFS share configured, and that you have created a CIFS data migration source. See Volumes Page on page 41, Adding a New CIFS Share to a Volume on page 101, and Configuring a CIFS Migration Source on page 201 for more information. To configure a CIFS data migration: 1. Click Services, then select Add Migration from the list. The Configure Data Migration page appears. Figure 10-7: Configure Data Migration page. Note: If the only migration source is a CIFS source, the Configure Data Migration page does not appear and the Configure CIFS Data Migration page appears automatically. Select Add CIFS Data Migration. Nasuni Filer Administration Guide

220 Data Migration 2. The Configure CIFS Data Migration page appears. Figure 10-8: Configure CIFS Data Migration page. 3. To copy the information for an existing migration, select the existing migration from the Copy Migration drop-down list. 4. In the Migration Name text box, enter a descriptive name for the migration procedure. This is for your own use. Nasuni Filer Administration Guide

221 Data Migration 5. From the Source Share drop-down list, select the source CIFS share. The drop-down list contains the currently defined data migration source CIFS shares. Alternatively, select Add Source. The Add CIFS Migration Source dialog box appears. Figure 10-9: Add CIFS Migration Source dialog box. See Configuring a CIFS Migration Source on page 201 to continue. Then, from the Source Share drop-down list, select the new source CIFS share. 6. In the Source Folder text box, navigate to a source folder from within the source CIFS share to copy data from. You can select multiple source folders, as long as they are all on the same level, that is, subfolders of the same folder. 7. From the Destination Volume drop-down list, select a local target destination volume to copy data to. Tip: Nasuni recommends migrating to an unshared portion of a volume, so users are not accessing or changing data during data migration into that portion of the volume. 8. Optionally, in the Destination Folder text box, select or create a specific folder on the destination volume to copy files to. The Select Destination Folder dialog box appears. Navigate to the desired destination folder. Note: If a destination folder does not already exist, then you can create one by clicking Create Folder. Caution: The migration procedure copies data from a CIFS share to a local volume and directory. Data already on that volume can be overwritten or updated, depending on the state of the Preserve Changes check box. See step 14 on page 210 for details. Nasuni Filer Administration Guide

222 Data Migration 9. Optionally, from the File Permissions drop-down list, select one of these options for handling permissions of migrated data: Apply specified NTFS-style permission sets: Enables the Custom perm area to manage permission sets. See step 11 on page 208 for details. (Advanced) Clone NTFS-Style permissions: Copies the permissions from the source as closely as possible. Copy Data Only, ignores NTFS-style permissions: Only copies the data and ignores the existing permissions. 10. Optionally, enter a file owner in the File Owner text box. This option is only available for the User or Active Directory security mode. You can enter or search for the name of the file owner user. Leaving this text box blank means that files can be accessed as read-write for all associated users. Note: The User security mode is only available if activated by the product license. 11. Optionally, if the File Permissions selection is Apply specified NTFS-style permission sets, the Custom perm area enables you to manage permission sets. Permission sets define the specific users and groups that have access to the copied files. a. Click the Manage icon. The Modify Permission Sets dialog box appears. Figure 10-10: Modify Permission Sets dialog box. b. To edit a permission set, click Edit Permission next to the permission set s label. To delete a permission set, click Delete next to the permission set s label. c. To add a permission set, click Add Permission. The Add Permission Set dialog box appears. Figure 10-11: Add Permission Set dialog box. i. In the Label text box, type a label to describe this permission set. Nasuni Filer Administration Guide

223 Data Migration ii. To add a user, in the Permissions area, click Add Users. The Select Users dialog box appears. Figure 10-12: Select Users dialog box. iii. In the Search text box, enter a partial or complete username, then click Search. A list of user names that contain your search text appears. Select the users to define access for, then click Add Selected Users. The selected users appear in the Permissions area. iv. For each user in the Permissions list, from the Access drop-down list, select either Full Control or Read Only. v. To delete a user from the Permissions list, click Delete next to the user s Name. The user is deleted from the list. vi. To add a group, in the Permissions area, click Add Groups. The Select Groups dialog box appears. Figure 10-13: Select Groups dialog box. vii. In the Search text box, enter a partial or complete group name, then click Search. A list of group names that contain your search text appears. Select the groups to define access for, then click Add Selected Groups. The selected groups appear in the Permissions area. viii. For each group in the Permissions list, from the Access drop-down list, select either Full Control or Read Only. Nasuni Filer Administration Guide

224 Data Migration ix. To delete a group from the Permissions list, click Delete next to the group Name. The group is deleted from the list. x. To add everyone to the Permissions list, click Add Everyone. The group Everyone appears in the Permissions area. From the Access drop-down list, select either Full Control or Read Only. To delete the group Everyone from the Permissions list, click Delete next to Everyone. The group Everyone is deleted from the list. xi. To save the permission set, click Save Permission Set. The permission set is created and appears in the list of permission sets. Otherwise, click Cancel and no changes are made. xii. Click Close to close the Modify Permission Sets page. d. From the Custom Perm drop-down list, select a permission set. 12. In the Exclude Patterns text box, enter a list of names, including wildcards, of folders or files to exclude from the data migration. When you specify folders to exclude, specify the full path without the leading slash (/) or the trailing asterisk (*), in the form RootFolder/SubFolder. You can use these wildcards when you specify each pattern: Wildcard Meaning Example * Matching any number of any character.? Matching any one character. *.mp3 means any file name that ends with mp3. test.mp? means file names like test.mp3 or test.mp4. [sequence] [!sequence] Matching any character in the specified sequence. Matching any character not in the specified sequence. [A-Z]*.* means file names that start with an upper-case letter. [!A-Z]*.* means file names that do not start with an upper-case letter. 13. To delete files that are at the destination but are not at the source, select the Delete removed files check box. This enables you to ensure that the destination files mirror the source files. Caution: This action deletes data from the Nasuni Filer. 14. To prevent overwriting newer files on the destination with older files from the source, select the Preserve Changes check box. This enables you to update files, but not overwrite them with older versions. 15. To specify logging only error messages that might occur during data migration, but not success messages or skip messages, select the Only Log Errors check box. Nasuni Filer Administration Guide

225 Data Migration 16. From the Error Limit drop-down list, select one of the following options: a. Default: The data migration halts after a fixed number of consecutive errors, currently 32. b. 500 Errors: The data migration halts after 500 consecutive errors. c. Unlimited: The data migration does not halt, no matter how many errors occur. 17. From the Next Action drop-down list, select one of the following options: a. Save & Start Immediately: This option saves the data migration configuration, then immediately begins the data migration. Select this when you want to start the data migration at once. b. Save & Schedule Migration: This option saves the data migration configuration, then allows you to immediately schedule the data migration for some future time. Select this when you do not want to begin the data migration now, and you know when you do want to begin the data migration. See Scheduling a Migration on page 220 for more details. c. Just Save: This option saves the data migration configuration without beginning the data migration or scheduling the data migration. Select this when you do not want to begin the data migration now, and you do not know when you do want to begin the data migration. 18. Click Save Migration to save your selections. The Create Data Migration dialog box appears. Click Save/Start Migration. Note: The migration process can overwrite existing files in the destination folder, depending on the state of the Preserve Changes check box. See step 14 on page 210. A status page appears showing the status of current migrations. Figure 10-14: Status of current CIFS migrations. Nasuni Filer Administration Guide

226 Data Migration After the migration starts, the following information appears on the status of the migration: Migration: The name of this migration. Source: The source for this migration. Target: The location on the Nasuni Filer to which the files are copied. Scheduled: Whether or not this migration is controlled by a migration schedule: Yes or No. Status: Current status of the overall migration run, such as: Running, Interrupted, Completed. Current Operation: Activity of the currently running migration. Est. Time: Time estimate for the currently running migration to complete. This estimate can be impacted by a variety of factors, and continually updates as the migration progresses. Est. Rate: Estimated data transfer rate for the currently running migration, in files per minute and in MB per second. Progress: Number of files that have completed for the currently running migration compared to the total number of files to be migrated, as well as amount of data completed compared with the total amount of data to be migrated. For example, 50 of 100 files - 5 GB of 10 GB. A progress bar appears with a percentage complete, based on the number and sizes of files being migrated. You can also view the migration results log. See Viewing a Migration Log on page 229 for more details. You can schedule, remove, and re-run a migration procedure. For more information, see: Scheduling a Migration on page 220. Deleting a Migration Procedure on page 228. Rerunning a Migration Procedure on page 227. Nasuni Filer Administration Guide

227 Data Migration Configuring an NFS Data Migration Before configuring an NFS migration, ensure that you have a source NFS volume and NFS export configured, and that you have configured an NFS migration source. See Adding a Volume on page 46, Adding an NFS Export to a Volume on page 117, and Configuring an NFS Migration Source on page 203 for more information. To configure an NFS data migration: 1. Click Services, then select Add Migration from the list. The Configure Data Migration page appears. Figure 10-15: Configure Data Migration page. Note: If the only migration source is an NFS source, the Configure Data Migration page does not appear and the Configure NFS Data Migration page appears automatically. Click Add NFS Data Migration. Nasuni Filer Administration Guide

228 Data Migration 2. The Configure NFS Data Migration page appears. Figure 10-16: Configure NFS Data Migration page. 3. To copy the information for an existing migration, select the existing migration from the Copy Migration drop-down list. 4. In the Migration Name text box, enter a descriptive name for the migration procedure. This is for your own use. Nasuni Filer Administration Guide

229 Data Migration 5. From the Source Export drop-down list, select the source NFS export. The drop-down list contains the currently defined data migration source NFS exports. Alternatively, select Add Source. The Add NFS Migration Source dialog box appears. Figure 10-17: Add NFS Migration Source dialog box. See Configuring an NFS Migration Source on page 203 to continue. Then, from the Source Export drop-down list, select the new source NFS export. 6. In the Source Directory text box, enter or navigate to a source directory within the NFS export to copy data from. 7. From the Destination Volume drop-down list, select a local target destination volume to copy data to. Tip: Nasuni recommends migrating to an unexported portion of a volume, so that users are not accessing or changing data in that portion of the volume during data migration. 8. Optionally, in the Destination Directory text box, enter or navigate to a specific directory on the volume to copy files to. The Select Destination Folder dialog box appears. Navigate to the desired destination folder. Note: If a destination folder does not already exist, then you can create one by clicking Create Folder. Caution: The migration procedure copies data from an NFS export to a local volume and directory. Data already on the volume can be overwritten or updated, depending on the state of the Preserve Changes check box. See step 11 on page 216. Nasuni Filer Administration Guide

230 Data Migration 9. In the Exclude Patterns text box, enter a list of names, including wildcards, of folders or files to exclude from the data migration. When you specify folders to exclude, specify the full path without the leading slash (/) or the trailing asterisk (*), in the form RootFolder/SubFolder. You can use these wildcards when you specify each pattern: Wildcard Meaning Example * Matching any number of any character.? Matching any one character. *.mp3 means any file name that ends with mp3. test.mp? means file names like test.mp3 or test.mp4. [sequence] [!sequence] Matching any character in the specified sequence. Matching any character not in the specified sequence. [A-Z]*.* means file names that start with an upper-case letter. [!A-Z]*.* means file names that do not start with an upper-case letter. 10. To delete files that are at the destination but are not at the source, select the Delete removed files check box. This enables you to ensure that the destination files mirror the source files. Caution: This action deletes data from the Nasuni Filer. 11. To prevent overwriting newer files on the destination with older files from the source, select the Preserve Changes check box. This enables you to update files, but not overwrite them with older versions. 12. To specify logging only error messages that might occur during data migration, but not success messages or skip messages, select the Only Log Errors check box. 13. From the Error Limit drop-down list, select one of the following options: a. Default: The data migration halts after a fixed number of consecutive errors, currently 32. b. 500 Errors: The data migration halts after 500 consecutive errors. c. Unlimited: The data migration does not halt, no matter how many errors occur. 14. From the Next Action drop-down list, select one of the following options: a. Save & Start Immediately: This option saves the data migration configuration, then immediately begins the data migration. Select this when you want to start the data migration at once. b. Save & Schedule Migration: This option saves the data migration configuration, then allows you to immediately schedule the data migration for some future time. Select this when you do not want to begin the data migration now, and you know when you do want to begin the data migration. See Scheduling a Migration on page 220 for more details. Nasuni Filer Administration Guide

231 Data Migration c. Just Save: This option saves the data migration configuration without beginning the data migration or scheduling the data migration. Select this when you do not want to begin the data migration now, and you do not know when you do want to begin the data migration. 15. Click Save Migration to save your selections. The Create Data Migration dialog box appears. Click Save/Start Migration. Caution: The migration process can overwrite existing files in the destination directory, depending on the state of the Preserve Changes check box. See step 11 on page A status page appears showing the current migrations. Figure 10-18: Current Migrations page. 17. After the migration starts, the following information appears on the status of the migration: Migration: The name of this migration. Source: The source for this migration. Target: The location on the Nasuni Filer to which the files are copied. Scheduled: Whether or not this migration is controlled by a migration schedule: Yes or No. Status: Current status of the overall migration run, such as: Running, Interrupted, Completed. Current Operation: Activity of the currently running migration. Est. Time: Time estimate for the currently running migration to complete. This estimate can be impacted by a variety of factors, and continually updates as the migration progresses. Est. Rate: Estimated data transfer rate for the currently running migration, in files per minute and in MB per second. Progress: Number of files that have completed for the currently running migration compared to the total number of files to be migrated, as well as amount of data completed compared with the total amount of data to be migrated. For example, 50 of 100 files - 5 GB of 10 GB. A progress bar appears with a percentage complete, based on the number and sizes of files being migrated. You can also view the migration results log. See Viewing a Migration Log on page 229 for more details. Nasuni Filer Administration Guide

232 Data Migration To schedule a migration procedure, see Scheduling a Migration on page 220. To remove a migration procedure, see Deleting a Migration Procedure on page 228. To re-run a migration procedure, see Rerunning a Migration Procedure on page 227. Nasuni Filer Administration Guide

233 Data Migration Editing a Data Migration After you configure a data migration, you can edit that data migration. To edit a data migration: 1. Click Services, then select View Migrations from the list. The Current Migrations page appears. Figure 10-19: Current Migrations page. 2. Click Edit. The Configure Data Migration screen appears. See Configuring a CIFS Data Migration on page 205 or Configuring an NFS Data Migration on page 213 for details. Nasuni Filer Administration Guide

234 Data Migration Scheduling a Migration Schedule You can schedule an existing migration to run automatically and periodically. You have the option to schedule a migration to run based on specific days and times, or to run after a specific number of hours or minutes. Scheduling a Migration by Day and Time To schedule a migration by day and time, follow these steps: 1. Click Services, then select View Migrations. The Current Migrations page appears. Figure 10-20: Current Migrations page. Nasuni Filer Administration Guide

235 Data Migration 2. For the migration that you want to schedule, click Schedule. The Editing Migration Schedule page appears. Figure 10-21: Editing Migration Schedule page. 3. From the Scheduling Mode drop-down list, select By Day and Time. 4. Select the days of the week that you want the migration to run. You can select or deselect all days by clicking Select/Deselect all. 5. From the Time drop-down lists, select the hour, minute, and AM or PM label for the time on each selected day for the migration to start running. Note: If you configure multiple migrations on a Nasuni Filer, they do not run at the same time. A migration runs at its scheduled time only if no other migration is running. If two migrations are scheduled for exactly the same time, one migration starts and the other starts when the first one finishes. If the start time for one migration occurs while another migration is running, the migration that has not started is skipped until its next scheduled start time. To help prevent one migration from interfering with another, schedule them farther apart in time. 6. Select the days of the week that you want to suspend a running migration. For example, you might want to suspend migrations from running during weekdays. You can select or deselect all days by clicking Select/Deselect all. Nasuni Filer Administration Guide

236 Data Migration 7. From the Suspend Time drop-down lists, select the hour, minute, and AM or PM label for the time on each selected day to suspend a running migration. Note: Suspended migrations resume at the next scheduled start time. 8. Click Save Schedule. The Scheduled Migrations page appears. Figure 10-22: Scheduled Migrations page. The migration starts running at the next scheduled start time. Scheduling a Migration by Hours and Minutes (at a Frequency) To schedule a migration to run after a specified number of hours and minutes, follow these steps: 1. Click Services, then select View Migrations from the list. The Current Migrations page appears. Figure 10-23: Current Migrations page. Nasuni Filer Administration Guide

237 Data Migration 2. Click Schedule. The Editing Migration Schedule page appears. Figure 10-24: Editing Migration Schedule page. 3. From the Scheduling Mode drop-down list, select Repeat at a Frequency. 4. In the Hours text box, enter the number of hours to wait before restarting the migration procedure. The number of hours can be zero, as long as the number of minutes is not also zero. 5. In the Minutes text box, enter the number of minutes to wait before restarting the migration procedure. The number of minutes can be zero, as long as the number of hours is not also zero. Note: If you configure multiple schedules, they do not run simultaneously. A migration runs after its specified hours and minutes if no other migration is running. 6. Click Save Schedule. The Scheduled Migrations page appears. Figure 10-25: Scheduled Migrations page. The migration starts running after the specified number of hours and minutes. Nasuni Filer Administration Guide

238 Data Migration Viewing Schedules Delete View To view configured data migration schedules: 1. Click Services, then select View Schedules from the list. The Scheduled Migrations page appears. Figure 10-26: Scheduled Migrations page. Migrations that you have scheduled are displayed. Editing a Migration Schedule To modify the schedule for a data migration, click Services, then select View Schedules from the list, then click Edit for the schedule that you want to modify. Deleting a Migration Schedule Delete To delete the schedule for a data migration, click Services, then select View Schedules from the list, then click Delete for the schedule that you want to delete. The message Successfully deleted the schedule appears. This deletes the schedule for the data migration, but not the data migration itself. Nasuni Filer Administration Guide

239 Data Migration Viewing migration information You can view detailed information about a migration. To view migration information: 1. Click Services, then select View Migrations from the list. The Current Migrations page appears. Figure 10-27: Current Migrations page. For each migration in the list, the following information appears: Migration: The name of this migration. Source: The source for this migration. Target: The location on the Nasuni Filer to which the files are copied. Scheduled: Whether or not this migration is controlled by a migration schedule: Yes or No. Status: Current status of the overall migration run, such as: Running, Interrupted, Completed. Current Operation: Activity of the currently running migration. Est. Time: Time estimate for the currently running migration to complete. This estimate can be impacted by a variety of factors, and continually updates as the migration progresses. Est. Rate: Estimated data transfer rate for the currently running migration, in files per minute and in MB per second. Progress: Number of files that have completed for the currently running migration compared to the total number of files to be migrated, as well as amount of data completed compared with the total amount of data to be migrated. For example, 50 of 100 files - 5 GB of 10 GB. A progress bar appears with a percentage complete, based on the number and sizes of files being migrated. You can also view the migration results log. See Viewing a Migration Log on page 229 for more details. Nasuni Filer Administration Guide

240 Data Migration 2. For the migration you want to view, click Info. The Migration Information dialog box appears. The following information appears: Figure 10-28: Migration Information dialog box. Migration Name: The name of this migration. Source: The source for this migration. Destination: The location on the Nasuni Filer to which the files are copied. Delete Removed Files: Whether the migration should delete files that are at the destination but are not at the source: yes (delete) or no (do not delete). Preserve Changes: Whether the migration should prevent overwriting newer files on the destination with older files from the source: yes (do not overwrite) or no (overwrite). Copy NTFS Permissions: Whether the migration should copy permissions from the source: yes (copy permissions) or no (do not copy permissions). File Owner (CIFS only): The name of the file owner user. Is Scheduled: Whether or not this migration is controlled by a migration schedule: yes (is scheduled) or no (is not scheduled). Log Only Errors: Whether the migration should log only error messages that might occur during data migration, but not success messages or skip messages: yes (log only errors) or no (log errors, success messages, and skip messages. Error Limit: The number of errors that halts the data migration. Default is 32; 500; or unlimited. Exclusions: Names, including wildcards, of folders or files to exclude from the data migration. 3. Click Close when done. Nasuni Filer Administration Guide

241 Data Migration Rerunning a Migration Procedure You can rerun a migration if, for example, there were errors during the last run or users have changed files on the source after the migration procedure ran. If you periodically migrate data from one source for backup or disaster recovery purposes, then, when you rerun a migration, the Nasuni Filer migrates the data, but only copies files that have changed, as well as any ACLs or permissions that have changed. It does not start the entire migration again. Tip: If you perform large migrations or frequent migrations, consider using a different Nasuni Filer to migrate data, instead of the Nasuni Filer that your users access. In this way, each Nasuni Filer instance can access the same volume. This is done by enabling remote access for the volume on one Nasuni Filer, and connecting to the now remotely accessible volume on the other Nasuni Filer. To rerun a migration procedure: 1. Click Services, then select View Migrations from the list. The Current Migrations page appears. 2. To rerun a migration procedure, click Start. Figure 10-29: Current Migrations page. Disconnecting from (deleting) a Migration Source Delete You can disconnect from (delete) a migration source, if necessary, without deleting the migration itself. To disconnect from a migration source: 1. Click Services, then select Migration Sources from the list. The Migration Sources page appears. Figure 10-30: Migration Sources page. View 2. Click Delete to the right of the migration source that you want to disconnect from. The Confirm Source Delete dialog box appears. 3. Click Confirm. To exit the dialog box without disconnecting from the migration source, click Cancel. Nasuni Filer Administration Guide

242 Data Migration The migration source is disconnected and does not appear in the Migration Sources list. Deleting a Migration Procedure Delete Use the delete option for migration procedures that you never want to run again. To disconnect from a migration source, without deleting the migration procedure, see Disconnecting from (deleting) a Migration Source on page 227. To delete a migration procedure: 1. Click Services, then select View Migrations from the list. The Current Migrations page appears. Figure 10-31: Current Migrations page. 2. To remove a migration procedure from the queue, click Delete for that procedure. The migration procedure is not saved. Nasuni Filer Administration Guide

243 Data Migration Viewing a Migration Log You can view a log file of the migration process. The log file is also available as a text.csv file within the target migration directory of the migration. From your Web browser, the log is viewable for the most recently run migration procedure. All log files reside in the target directory unless you delete them. An example of a log file name is: migration-log _10755.txt. To view a migration status log: 1. Click Services, then select View Migrations from the list. The Current Migrations page appears. Figure 10-32: Current Migrations page. 2. Click Log. This button is only available if a migration has run and there is a log file to view. The Migration Log window appears. Figure 10-33: Migration Log. Because log files can be very long, only the last 30 lines of the data migration log file appear. To download the full log file, click Download Full File. This text file is in.csv format and contains a detailed record of the migration, including date, time, source, target, where you migrated from and to, and the status of each file and directory being migrated. Note: Any errors during a migration are recorded in the migration log. You can view the full details of any error in this log. Nasuni Filer Administration Guide

244 Side Load Side Load Nasuni supports a Disaster Recovery (DR) process ( Disaster Recovery on page 376) that enables you to recover the Nasuni Filer after a true disaster, such as the loss of a data center. However, most of the time, customers perform the Disaster Recovery process in order to upgrade from one piece of hardware to another. In such a situation, there is a working Nasuni Filer in your data center that contains active data in the cache. Performing the Disaster Recovery process results in a new Nasuni Filer that has an empty cache. The customer often then re-populates the new cache with data, which can require considerable inbound bandwidth from the cloud, and which can take days, weeks, or even months to complete. The Side Load feature enables you to transfer cache data directly from the source Nasuni Filer to the new Nasuni Filer. The source Nasuni Filer must already be decommissioned. Tip: Only one Side Load process is permitted at a time for each Nasuni Filer. Tip: Only the Admin user can perform the Side Load process. Tip: The source Nasuni Filer must be: Running; Decommissioned; Using release 7.0 or above. Warning: If the total data available on the source Nasuni Filer exceeds the available cache space on the new Nasuni Filer, you receive a warning message and notification. You can configure Notifications to notify you by when the Side Load process completes. Nasuni Filer Administration Guide

245 Side Load Starting the Side Load process To start the Side Load process from the source Nasuni Filer to the current Nasuni Filer, follow these steps: 1. On the current or destination Nasuni Filer, click Services, then select Side Load from the list. The Side Load page appears. Figure 10-34: Side Load page. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. 2. In the Host Address text box, enter the host address of the source Nasuni Filer. The source Nasuni Filer must already be decommissioned. 3. In the Username text box, enter the username for the specified source Nasuni Filer. The source Nasuni Filer must already be decommissioned. 4. In the Password text box, enter the password for the specified Username for the specified source Nasuni Filer. The source Nasuni Filer must already be decommissioned. 5. Click Connect and Start. A connection is established with the data of the source Nasuni Filer. Data begins moving to the current Nasuni Filer. After the data transfer starts, you can view the progress of the Side Load process. 6. When the Side Load process completes, the Complete label appears on the bar graph. Tip: Record any information you want to retain from the screen before clicking Done. Click Done. Nasuni Filer Administration Guide

246 Side Load Viewing and controlling the Side Load process To view or control the progress of the Side Load process, follow these steps: 1. Click Services, then select Side Load from the list. If the Side Load process has not yet completed, the Side Load - Status page appears. Figure 10-35: Side Load - Status page. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. The following information appears: Host Address: The host address of the source Nasuni Filer. The source Nasuni Filer must already be decommissioned. Progress: A bar graph indicating the progress of the Side Load process. The percentage of the Side Load process that is complete appears. If the Side Load process is running, the Running label appears. If the Side Load process is paused, the Paused label appears. Data Processed: The amount of data processed (in KB, MB, GB, or TB) and the total amount of data to process (in KB, MB, GB, or TB). Est. Rate: The estimated rate of data transfer (in KB/S, MB/S, GB/S, or TB/S). Est. Time Remaining: The estimated time until the Side Load process is complete. Nasuni Filer Administration Guide

247 Side Load 2. To pause a running Side Load process, click Pause. The Side Load process pauses indefinitely. The bar graph label changes to Paused. Figure 10-36: Side Load - Status page, paused. To continue with the Side Load process after a pause, click Resume. The Side Load process continues. The bar graph label changes to Running. 3. To cancel the Side Load process, click Cancel. The Cancel Side Load dialog box appears. Figure 10-37: Cancel Side Load dialog box. To cancel the Side Load process, click Continue. If the Side Load process is canceled, the bar graph label changes to Canceled. Figure 10-38: Side Load status page, canceled. Tip: Record any information you want to retain from the screen before clicking Done. Nasuni Filer Administration Guide

248 Side Load 4. When the Side Load process completes, the Complete label appears on the bar graph. Tip: Record any information you want to retain from the screen before clicking Done. 5. Click Done. Nasuni Filer Administration Guide

249 Nasuni Desktop and Mobile Access Nasuni Desktop and Mobile Access The Nasuni Desktop and Mobile Access service enables you to access folders and files from mobile devices, including ios-based devices (such as iphone and ipad) and Android phones. The Nasuni Desktop and Mobile Access service enables you to access folders and files using the Nasuni Desktop Client on Windows, OSX, and Linux clients. The Nasuni Desktop and Mobile Access service is available for volumes on which the CIFS protocol has been enabled, but not for NFS or iscsi volumes. Mobile Access To access folders and files from mobile devices, you first perform the following actions: Enable Nasuni Mobile Access for a CIFS share. For details, see step r on page 108 of Adding a New CIFS Share to a Volume, or Editing a CIFS Share on page 113. Optionally, configure Mobile Access settings, as described in Mobile Access: Configuring on page 236. Optionally, manage the access for mobile devices, as described in Mobile Access: Managing access by mobile devices on page 237. On your mobile device, you must perform the following actions: Download and install the appropriate Nasuni Mobile Access application for your platform. The Nasuni Mobile Access application is freely available to your users from the appropriate app store. Log in to the Nasuni Mobile Access application using Active Directory credentials, including domain, username, and password. If only one Active Directory domain is used, the full domain path usually is not necessary. Logging in successfully registers the mobile device with the Nasuni Filer. See Logging in to the Nasuni Mobile Access application on page 158. After logging in to the Nasuni Mobile Access application, you can perform the following tasks (depending on the capabilities of the mobile device): Navigate CIFS shares, folders, and files that you have access to in the Nasuni Filer file system. Sort the contents of folders by name, file type, or date modified. View file information such as file name, file size, and date and time of last modification. Open files that can be opened, including playing video and audio files. Note: Streaming media might not operate for Nasuni Filers that use the default selfsigned certificate. To configure SSL certificates for the Nasuni Filer, see SSL Certificates on page 301. Download and upload files. links to files. View and access previous versions of files. Identify favorite files for easier access. Configure user settings. Nasuni Filer Administration Guide

250 Nasuni Desktop and Mobile Access For details on performing these actions, see Nasuni Mobile Access on page 157. See for a worksheet for planning configurations. Mobile Access: Configuring Mobile Access offers several optional features that you can configure. To configure optional Nasuni Mobile Access features, follow these steps: 1. Click Services, then select Mobile Service Settings from the list. The Mobile Service Settings page appears. Figure 10-39: Mobile Service Settings page. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. 2. To add another port for Mobile Access, enter the port number in the Additional API port text box. The port number must be between 1 and 65535, inclusive. Leave blank to disable an additional port. 3. To limit how long users remain authenticated on mobile devices, enter the maximum length of time in minutes in the Session Expiration text field. To allow unlimited session time, enter 0 (zero). 4. To limit users to only one mobile device, select Limit to a single device. 5. You can limit the types of mobile devices that can use Mobile Access. To allow Android devices to use Mobile Access, select Android. To allow ios devices to use Mobile Access, select ios. To allow Linux systems to use Mobile Access, select Linux. To allow OSX systems to use Mobile Access, select OSX. To allow Windows systems to use Mobile Access, select Windows. Nasuni Filer Administration Guide

251 Nasuni Desktop and Mobile Access 6. To save your changes, click Save. Mobile Access: Managing access by mobile devices Manage You can disable, enable, and delete licenses for mobile devices. See for a worksheet for planning configurations. To manage access to Nasuni Mobile Access by mobile devices, follow these steps: 1. Click Services, then select Mobile Licenses from the list. The Mobile License Usage page appears. Figure 10-40: Mobile License Usage page. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. Note: To access the Mobile License Usage page, the user must belong to a group that has Manage all aspects of the Filer (super user) or Manage Volume security settings permission. For details about assigning users to groups or assigning permissions to groups, see Users and Groups on page To search by Username, Device Type, or Device ID, enter the search information in the Search text box. The list of Licenses is limited to those that contain the Search text. All searches are case-sensitive. 3. To sort by Username, Device Type, Device ID, Logged In status, Enabled status, or Authenticated On date, click on the heading of the column. To sort in the opposite direction, click the heading again. 4. Disabling a mobile device blocks access and, on the next attempt at access, clears the mobile device s cache of any cached files. To disable mobile service on devices, follow these steps: a. Select the check box to the left of each mobile device to disable. b. From the drop-down list, select Disable selected licenses. The selected licenses are disabled for mobile access. Nasuni Filer Administration Guide

252 Nasuni Desktop and Mobile Access 5. Enabling a mobile device allows access by the mobile device. To enable mobile service on devices, follow these steps: a. Select the check box to the left of each mobile device to enable. b. From the drop-down list, select Enable selected licenses. The selected licenses are enabled for mobile access. 6. Deleting a mobile device removes the mobile device from the list, but does not block future access. Instead, the user must log in again the next time they run the Nasuni Mobile Access application. To delete mobile devices, such as when people stop using a mobile device, follow these steps: a. Select the check box to the left of each mobile device to delete. b. From the drop-down list, select Delete selected licenses. The selected licenses are deleted. Mobile Access: Creating an invitation link You can create a link to share access information for your Nasuni Filers. This link can include the hostname or IP address, the port number, and the username. You can then this link to users to simplify the process of connecting them to Mobile Access. To create an invitation link to Nasuni Mobile Access, follow these steps: 1. Click Services, then select Mobile Service Settings from the list. The Mobile Service Settings page appears. Figure 10-41: Mobile Service Settings page. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. Nasuni Filer Administration Guide

253 Nasuni Desktop and Mobile Access 2. Click Invitation Link. The Generate Invitation Link page appears. Figure 10-42: Generate Invitation Link page. 3. Enter the Host and the Port that mobile clients use to access the Web server. Ensure that you provide the port for HTTPS access. 4. Click Generate. A link is generated of the form: where <host_name> and <port_number> are the Host and Port specified in step 3. If Port is 443, <port_number> is omitted from the link. 5. Copy the link, and paste it as a URL into the that you send to users to inform them of the availability of Mobile Access. Mobile Access: Configuring DNS to Simplify User Login Alternatively, the administrator can configure the company DNS server to simplify user login to your Nasuni Filers. The configured DNS entry includes the host and port necessary for Mobile Access. When the user logs into the Nasuni mobile application using their company address and password, the application retrieves the host and port from the DNS to complete the login. To configure the DNS, it is necessary to create a DNS record, with PTR, SRV, TXT, and A record types. All four of these record types are necessary for both single-host and multiple-host configurations. For the PTR record type, the record should be of the form: _nasunifiler._tcp PTR <service-instance>._nasunifiler._tcp where: <service-instance> is the name of the instance of the _nasunifiler._tcp service that the SRV links to. _nasunifiler._tcp is the symbolic service name and the TCP protocol name, and must not be changed. For multiple-service-instance configurations, each service instance must have a PTR record. Nasuni Filer Administration Guide

254 Nasuni Desktop and Mobile Access For the SRV record type, the record should be of the form: <service-instance>._nasunifiler._tcp SRV <priority> <weight> <port> <target>. where: <service-instance> is the name of the instance of the _nasunifiler._tcp service that the SRV links to. Same as in the PTR record. _nasunifiler._tcp is the symbolic service name and the TCP protocol name, and must not be changed. <priority> is the relative priority of this target, from 0 through Lowest number is highest priority. Priority and weight are only relevant when there is more than one SRV record with the same instance. <weight> is the weight, which is used when there is more than one target with the same instance and with the same priority, from 0 through Higher number means greater weight and greater probability. 0 indicates no weighting should be applied. Priority and weight are only relevant when there is more than one SRV record with the same instance. Note: Nasuni Mobile follows the DNS Service Discovery standard (RFC 6763), and properly handles complex configurations with multiple Nasuni Filers using various priorities and weights. If you need assistance in setting up such a configuration, contact Nasuni Support. <port> is the TCP port number where the Nasuni Filer is reachable. Usually: 443. <target> is the DNS name of the target host. Does not have to be in the same domain as the SRV record. For multiple-target configurations, each target must have an SRV and A record. For the TXT record type, the record should be of the form: <service-instance>._nasunifiler._tcp TXT "txtvers=1" "companyfullname=<companyname>" where: <service-instance> is the name of the instance of the _nasunifiler._tcp service that the SRV links to. Same as in the PTR record. _nasunifiler._tcp is the symbolic service name and the TCP protocol name, and must not be changed. <companyname> is the name of the company (optional). For multiple-instance configurations, each service instance must have a TXT record. Note that the "txtvers=1" parameter is necessary. For the A record type, the record should be of the form: <target> A <ip-address> where: <target> is the DNS name of the target host, as in the SRV record. <ip-address> is the IP address of the target. Nasuni Filer Administration Guide

255 Nasuni Desktop and Mobile Access An example of a single-instance DNS configuration looks like this: _nasunifiler._tcp PTR Nasuni\ Mobile._nasunifiler._tcp Nasuni\ Mobile._nasunifiler._tcp SRV mfcolo.nasuni.com. Nasuni\ Mobile._nasunifiler._tcp TXT "txtvers=1" "companyfullname=nasuni Corporation" mfcolo A In this example: Nasuni Mobile is the service instance name of the _nasunifiler._tcp service that the SRV links to. The priority is 0. The weight is 0. The port is The target is mfcolo.nasuni.com. The companyfullname is Nasuni Corporation. The IP address of mfcolo is An example of a single-instance, multiple-target DNS configuration looks like this: _nasunifiler._tcp PTR myfiler._nasunifiler._tcp myfiler._nasunifiler._tcp TXT "txtvers=1" myfiler._nasunifiler._tcp SRV mfcolo.nasuni.com. myfiler._nasunifiler._tcp SRV mfcolo2.nasuni.com. myfiler._nasunifiler._tcp SRV mfcolo3.nasuni.com. mfcolo A mfcolo2 A mfcolo3 A In this example, there are three targets, namely, mfcolo.nasuni.com., mfcolo2.nasuni.com., and mfcolo3.nasuni.com. For multiple-target configurations, each target must have an SRV and A record. In this example, it tries mfcolo.nasuni.com first, then, if that fails, mfcolo2.nasuni.com, then, if that also fails, mfcolo3.nasuni.com. This example illustrates weighting within a given priority, for SRVs with the same instance: _nasunifiler._tcp PTR myfiler._nasunifiler._tcp myfiler._nasunifiler._tcp TXT "txtvers=1" myfiler._nasunifiler._tcp SRV mfcolo-a.nasuni.com. myfiler._nasunifiler._tcp SRV mfcolo-b.nasuni.com. myfiler._nasunifiler._tcp SRV mfcolo2.nasuni.com. myfiler._nasunifiler._tcp SRV mfcolo3.nasuni.com. mfcolo-a A mfcolo-b A mfcolo2 A mfcolo3 A In this example, it first selects either mfcolo-a or mfcolo-b. On average, it selects mfcolo-a about 1/3 of the time and mfcolo-b about 2/3 of the time, based on their respective weights. If neither mfcolo-a nor mfcolo-b answer, then proceed to mfcolo2, and then mfcolo3, based on their respective priorities. Nasuni Filer Administration Guide

256 Nasuni Desktop and Mobile Access Desktop Client To access folders and files using the Nasuni Desktop Client on Windows, OSX, and Linux clients, you first perform the following actions: Enable Nasuni Mobile Access for a CIFS share. For details, see step r on page 108 of Adding a New CIFS Share to a Volume, or Editing a CIFS Share on page 113. On your Windows, OSX, and Linux clients, you must perform the following actions: Download and install the appropriate Nasuni Desktop Client software for your platform. For more details, see the Nasuni Desktop Client Administrator Guide and the Nasuni Desktop Client User Guide. Configure the Nasuni Desktop Client to access your Nasuni Filer. After installing the Nasuni Desktop Client, you can perform the following tasks (depending on the capabilities of the client): Create a new connection to a Nasuni Filer Manage existing connections to Nasuni Filers Use files or folders from the Nasuni Filer Add files or folders to the Nasuni Filer Sort the contents of folders by name, file type, or date modified. View file information such as file name, file size, and date and time of last modification. Open files that can be opened, including playing video and audio files. Download and upload files. links to files. View and access previous versions of files. Identify favorite files for easier access. For details on accessing data using the Nasuni Desktop Client, see Nasuni Desktop Client on page 167. Nasuni Filer Administration Guide

257 Nasuni Management Console Nasuni Management Console Enable The Nasuni Management Console enables you to monitor and manage multiple Nasuni Filers from one central appliance. Using the Nasuni Management Console, you can view the status of all your managed Nasuni Filers, as well as configure their settings, to ensure consistent settings. Note: When a Nasuni Filer is under the control of the Nasuni Management Console, portions of the Nasuni Filer user interface are not accessible, because those functions are now controlled by the Nasuni Management Console. If a Nasuni Filer is under the control of the Nasuni Management Console, you can return that Nasuni Filer to self-management mode at any time. These pages do not appear if the Nasuni Filer is under the control of the Nasuni Management Console: Volumes, and all pages under Volumes. File Browser, and all pages under File Browser. Services pages, including Mobile Service Settings and Mobile Licenses. Configuration pages, including Settings, Filer Description, Quality of Service, Time Configuration, FTP Settings, API Access Keys, Quota Settings, Users/Groups, SNMP Monitoring, Automatic Updates, and Cache Settings. Status pages, including Updates, CIFS Status, iscsi Status, NFS Status, and FTP Status. To enable or disable management of this Nasuni Filer by the Nasuni Management Console: 1. Click Services, then select Nasuni Management Console from the list. The Nasuni Management Console page appears. Figure 10-43: Nasuni Management Console page. 2. From the NMC Management is drop-down list, select either enabled or disabled. Warning: When a Nasuni Filer joins the NMC, all users on the Nasuni Filer are replaced with the users defined in the NMC. 3. Click Save. A confirmation message appears. A message also appears at the top of the screen. Nasuni Filer Administration Guide

258 Remote Support Service Remote Support Service Enable The Remote Support Service allows authorized Nasuni Technical Support personnel to remotely and securely access your Nasuni Filer. This can help Nasuni Technical Support to diagnose and resolve any issues with your Nasuni Filer quickly and proactively. No changes to your corporate firewalls are necessary. This service is disabled by default and is strictly opt-in. You can enable or disable this service at any time. You can also enable this service for a specific period of time. Enabling this service allows Nasuni to offer a higher level of service and support. Tip: If you need technical assistance, contact Nasuni Technical Support and inform them if you have enabled Remote Support Service. You receive an Informational notification whenever the Remote Support Service is enabled or disabled. Note: If the Remote Support Service is enabled, you can change the Timeout value without stopping and restarting the Remote Support Service. To configure the Remote Support Service: 1. Click Services, then select Remote Support Service from the list. The Remote Support page appears. Figure 10-44: Remote Support page. 2. From the Remote Service is drop-down list, select either enabled or disabled. 3. If you select enabled, the Timeout text box appears. Enter the length of time, in minutes, that you want to permit the Remote Support Service access to be enabled. Enter 0 (zero) to allow access for an indefinite amount of time. 4. Click Save. A confirmation message appears. If you entered a nonzero Timeout time, a countdown begins. To disable the Remote Support Service access immediately, click Disable. Nasuni Filer Administration Guide

259 Sending Diagnostics to Nasuni Sending Diagnostics to Nasuni Send If you experience problems that you cannot resolve, you can send diagnostic information to Nasuni Technical Support for troubleshooting purposes. Note: Local diagnostic information is automatically sent when needed, so there is typically no need to do this, unless instructed to by Nasuni Technical Support. Using Send Diagnostics includes more information than the automatic diagnostic information. To send diagnostic information: 1. Click Services, then select Send Diagnostics from the list. The Send Diagnostic Information to Nasuni dialog box appears. Figure 10-45: Send Diagnostic Information to Nasuni dialog box. 2. Enter a Username (case-sensitive) and Password (case-sensitive) that has permission to perform this operation. 3. Click Send Now. The message Diagnostic information was successfully delivered to Nasuni appears. Click the x to close the message box. Nasuni Filer Administration Guide

260 Chapter 11: Configuration Page Configuration The Configuration page enables you to configure the following elements: Settings. Filer description. HTTPS proxy. Network Configuration. Quality of Service. Time Configuration. FTP Settings. Domain Settings. General CIFS Settings. API Access Keys. Encryption Keys. Firewall. Quota Settings. SSL Certificates. Users and Groups. SNMP Monitoring. Web Access branding. Automatic Software Updates. Cache Settings. Global Locking. Passwords. Note: The Configuration page, and all other pages of the Nasuni Filer user interface, might look different to different users. Also, different menus and actions might be available for different users. This is because different users are assigned different permissions, based on their roles in the role-based access control system. See Users and Groups on page 315 for details. Note: If this Nasuni Filer is under the control of the Nasuni Management Console, menus and menu choices might look different, because you use the Nasuni Management Console to perform these tasks. Nasuni Filer Administration Guide

261 Settings Settings Edit You can configure alerts, which are sent to your account from the Nasuni Filer. You can also view the alert messages you receive on the Notifications page. See for a worksheet for planning configurations. To configure settings: 1. Click Configuration, then select Settings from the list. The Settings and Configuration page appears. Figure 11-1: Settings and Configuration page. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. Nasuni Filer Administration Guide

262 Settings 2. If you require TLS (Transport Level Security) security, select the Require TLS check box. If this check box is selected, and the server does not support TLS security, the Nasuni Filer does not use the server. Even if the check box is not selected, TLS security is still used by default if the server supports it. 3. Enter the source address in the From name text box. You can use this source address to filter s or to ensure that s do not go into a spam folder. Note: When sending an alert, the Nasuni service logs into the specified SMTP server using the specified credentials and sends the from the source address. 4. Specify an SMTP server in the SMTP server text box. For example, mail.mycompany.net. 5. Specify an SMTP port number in the SMTP port text box. If you do not specify a value, the default port 25 is used. 6. Optionally, enter a login name (for example, an account) in the Login text box (casesensitive) if your server requires it. For example, [email protected]. Optionally, enter a password (case-sensitive) in the Password text box if your server requires it. 7. In the Send to text box, enter one or more destination addresses for sending alerts to, separated by commas. 8. To receive all Nasuni Filer alerts to your address, select the Receive All Alerts check box. 9. If you do not select the Receive All Alerts check box, select the particular alerts that you want sent to your account, from these choices: Account Alerts: Alerts related to Nasuni.com account license issues, such as expiration and capacity limits. Appliance Alerts: Alerts that occur on the appliance. Capacity Alerts: Alerts related to capacity, such as volume quotas, new quotas, and account limits. Note: If the licensed capacity is exceeded, you can still store more data temporarily. If your total stored data nears or exceeds your licensed capacity, you receive warnings to increase your licensed capacity. Conflict Alerts: Notices that merge conflicts have occurred during a sync. See Synchronization (Merge) Conflicts on page 171. Data Migration Alerts: Alerts triggered due to data migration. General Alerts: Alerts not in the other categories. Snapshot Restore Alerts: When you restore data from a snapshot, this alert notifies you when the restore is complete. Software Updates: Notices that software updates are available. Violation Alerts: Alerts about antivirus violations (infections). See Antivirus Service on page 69. Nasuni Filer Administration Guide

263 Settings 10. To test your settings and then save your settings, click Test & Save. A test message is sent to the specified address for confirmation purposes. Alternatively, click Save to accept your selections without sending a test message. Nasuni Filer Administration Guide

264 Nasuni Filer Description Nasuni Filer Description Edit You can change the name of the Nasuni Filer from the default name assigned when you installed it. The name can be up to 140 characters in length. This name is used as a descriptive name for the Nasuni Filer when you log in to your account at or when you perform a disaster recovery. When you install the Nasuni Filer, a message appears in the message panel prompting you to change the name of the Nasuni Filer. See for a worksheet for planning configurations. To change the Nasuni Filer s description: 1. Click Configuration, then select Filer Description from the list. The Change Nasuni Filer Description page appears. Figure 11-2: Change Nasuni Filer Description page. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. 2. Enter the new name in the Nasuni Filer Name text box. 3. Click Save Filer Description. The message Filer description successfully changed to: <name>. appears. Nasuni Filer Administration Guide

265 HTTPS Proxy Configuration HTTPS Proxy Configuration Edit You can configure the Nasuni Filer to use an HTTPS proxy server, if needed. All HTTPS traffic goes through the proxy server that you specify. Note: If this Nasuni Filer is under the control of the Nasuni Management Console, when you enable or disable the HTTPS proxy, the Nasuni Management Console cannot update the Nasuni Filer settings for about 2 minutes. To configure the HTTPS Proxy: 1. Click Configuration, then select HTTPS Proxy from the list. The HTTPS Proxy Settings page appears. Figure 11-3: HTTPS Proxy Settings page. 2. To enable HTTPS proxy support, select the Enable Proxy Support check box. 3. In the Proxy Server text box, enter the hostname or IP address of a host running the HTTPS proxy. 4. In the Port text box, enter the port number used by the HTTPS proxy server. 5. Optionally, enter a valid username (case-sensitive) as configured by the proxy server in the User Name text box and the password (case-sensitive) in the Password text box. 6. Optionally, in the Do Not Proxy text box, enter a list of hostnames or IP addresses not to proxy (one per line). 7. To test your settings and then save your settings, click Test & Save. Alternatively, click Save to accept your selections without testing. Nasuni Filer Administration Guide

266 Network Configuration Network Configuration Edit The network address configuration is initially set during installation of the Nasuni Filer. However, you can change network settings as required. Changing network settings might temporarily disconnect users accessing the Nasuni Filer. Note: If you need to reconfigure the network, but the Nasuni Filer user interface is not available, you can access network settings using the service menu on the console. See the Nasuni Filer Initial Configuration Guide for details. See for a worksheet for planning configurations. About Traffic Groups Three default traffic groups are available: General: All traffic is in the General traffic group, unless explicitly assigned to a different traffic group. Systems with only one network interface card (NIC) always use the General traffic group. This traffic group is not for any specific purpose. Management: The Management traffic group designates a set of interfaces that carry local customer support access using SSH, and that provide user interface access to the Nasuni Filer. External: The External traffic group designates a set of interfaces that carry cloud traffic, Remote Support Service traffic (if enabled), and Nasuni API traffic. Note: You use the Firewall configuration page to configure what kind of traffic the Nasuni Filer accepts on each traffic group. You cannot combine traffic from two or more traffic groups together. Note: If a proxy is defined such that it is on one of the networks local to the Nasuni Filer, this local proxy is used for cloud traffic, Remote Support traffic, and Nasuni API traffic. Traffic flows on whichever interface can reach the local proxy. Bonding. If you assign more than one device to the same traffic group, the assigned devices are bonded for that traffic group. A bonded interface is a virtual network interface that runs on two or more physical interfaces. The Nasuni Filer offers a transmit-load-balancing bonding mode, which is a high-availability bonding mode with a performance enhancement when sending packets. Bonding also provides failover benefits. This bonding mode monitors the state of the network interface cards (NICs) that are in the bond: if the active device fails, it switches to a different active device. In addition, when transmitting a packet, the system determines (using an internal metric) which device in the bond is least busy, and transmits the packet using that device. When the host sends a packet to the Nasuni Filer, the packet always goes to the active device. Network switch ports to which bonded Nasuni Filer ports are attached must be configured as switchport access with trunk access disabled. Any switch port where a bonded Nasuni Filer port is attached should also not be bridged with any other Nasuni Filer port. The Spanning Tree's blocking, listening, and learning stages should be disabled or bypassed on all switch ports to which a bonded Nasuni Filer port is attached. (Cisco switches have a feature called PortFast that is used to disable these Spanning Tree stages on a port-by-port basis.) Nasuni Filer Administration Guide

267 Network Configuration Bonded Nasuni Filer port members may also be split across more than one switch in order to achieve switch redundancy. However, all switch ports that are attached to members of the same bond must comprise a single broadcast domain (namely, the same VLAN) configured on the switch port. Additionally, if problems exist after deploying a Nasuni Filer bond across more than one switch, reattach all bond members to the same switch. If the problems disappear, then the cause of the problem resides in the configuration of the switches and not in the configuration of the Nasuni Filer. Basic Configuration. Put all available NICs into the General traffic group. The Nasuni Filer uses a single IP address, and all types of traffic use that IP address. Traffic leaving the LAN uses a default gateway available on this LAN. Separating client and cloud traffic. Divide the NICs into General and External traffic groups. The Nasuni Filer uses one IP address for serving CIFS, NFS, FTP, and iscsi traffic, along with the user interface and management protocols, and one IP address for communicating with hosts outside the local network. The default gateway must be specified on the LAN that the External traffic group uses. Separating data and management traffic. Divide the NICs into General and Management traffic groups. The Nasuni Filer uses one IP address for serving CIFS, NFS, FTP and iscsi traffic in addition to communicating with cloud APIs, and a different IP address for the user interface and management protocols. This configuration expects that administrators use a separate back plane network to manage devices more securely. Sample network topologies. This example is for General traffic only. Figure 11-4: General traffic only. Nasuni Filer Administration Guide

268 Network Configuration This example is for General and External traffic. Figure 11-5: General and External traffic. Nasuni Filer Administration Guide

269 Network Configuration This example is for General and Management traffic. Figure 11-6: General and Management traffic. Nasuni Filer Administration Guide

270 Network Configuration This example is for General, External, and Management traffic. Figure 11-7: General, External, and Management traffic. Nasuni Filer Administration Guide

271 Network Configuration Configuring Network Settings To configure network settings, follow these steps: 1. Click Configuration, then select Network Configuration from the list. The Network Configuration page appears. Figure 11-8: Network Configuration page. Nasuni Filer Administration Guide

272 Network Configuration 2. To change the hostname for this Nasuni Filer, enter a new hostname in the Hostname text box. Enter the hostname (15 characters or less) or Fully Qualified Domain Name (64 characters or less) for this Nasuni Filer. You can use ASCII letters a through z, digits 0 (zero) through 9, and hyphens. The Nasuni Filer hostname is automatically registered in the DNS server, so that users can access this host by name. The name that you enter is the name you provide to users so they can access the Nasuni Filer. 3. In the Network Interface Settings area, to manage traffic groups, click Manage Traffic Groups. The Traffic Groups dialog box appears. Figure 11-9: Traffic Groups dialog box. The Traffic Groups dialog box displays a list of the currently available traffic groups. For each traffic group, the traffic group s name and description appears. For more information about traffic groups, a. To add a new traffic group, click Add Traffic Group. The Add Traffic Group dialog box appears. Figure 11-10: Add Traffic Group dialog box. i. In the Name text box, enter a short name for the new traffic group. ii. Optionally, in the Description text box, enter a description of the purpose or characteristics of the new traffic group. iii. Click OK to add the new traffic group. Alternatively, click Cancel to exit without adding a new traffic group. Nasuni Filer Administration Guide

273 Network Configuration b. To edit a traffic group s name or description, click Edit. The Edit Traffic Group dialog box appears. The Edit Traffic Group dialog box is similar to the Add Traffic Group dialog box described in step a above. Enter a new name or description for the traffic group, then click OK. c. To delete a traffic group, click Delete. The traffic group is deleted. d. To save all changes to the traffic groups, including added traffic groups and edited traffic groups, click Save. Alternatively, to exit without saving any changes, click Cancel. Note: You configure the network settings for each traffic group in step 5 below. 4. In the Network Interface Settings area, for each Device in the list, select the Traffic Group from the drop-down list. Figure 11-11: Network Interface Settings area. See About Traffic Groups on page 252 for more details. 5. In the Network Interface Settings area, to configure each Traffic Group, click Edit beside the Traffic Group. The Network Settings page appears. Figure 11-12: Network Settings page. Nasuni Filer Administration Guide

274 Network Configuration From the Network Type drop-down list, select either Static or DHCP. Note: For high availability Nasuni Filer hardware appliances, such as the NF-400H, the only choice is Static. If you select DHCP (Dynamic Host Configuration Protocol), the IP Address, Netmask, and MTU Value fields become unavailable. Note: DHCP may not be enabled on more than one traffic group. If you select Static, you must provide Network Interface Settings and System Settings. See your IT administrator for assistance. Enter the following information: Enter the static IP address in the IP Address text box. The address of a static device must not already be present on the network. The Nasuni Filer verifies this and displays an error if a collision is detected. Note: If you define more than one static device, the Nasuni Filer checks that the subnets specified do not appear more than once. If this is a high-availability hardware appliance Nasuni Filer, enter the Node 1 IP Address and the Node 2 IP Address in their text boxes. Enter a netmask address in the Netmask text box. Enter the MTU value in the MTU Value text box. Tip: MTU settings should not exceed The maximum transmission unit (MTU) is the size (in bytes) of the largest protocol data unit that the layer can pass onwards. A larger MTU brings greater efficiency, because each packet carries more user data, while protocol overheads, such as headers, remain fixed; the resulting higher efficiency means a slight improvement in the bulk protocol throughput. A larger MTU also means processing fewer packets for the same amount of data. However, large packets can occupy a slow link for some time, causing greater delays to following packets, and increasing lag and minimum latency. (Optional) You can specify a gateway for each traffic group. This gateway is used to return traffic for clients outside one of the Nasuni Filer's local networks that do not use the default gateway. In the Gateway text box, enter the IP address for the gateway. Click OK to use these values. Click Cancel to exit this page without making any changes. 6. In the System Settings area, from the Settings Source drop-down list, select one of the following: Note: For high availability Nasuni Filer hardware appliances, such as the NF-400H, the only choice is Static. DHCP (Dynamic Host Configuration Protocol): Provides a network IP address for a host on an IP network automatically. The Default Gateway, Search Domain, Primary DNS Server, and Secondary DNS Server fields become unavailable. Nasuni Filer Administration Guide

275 Network Configuration DHCP with custom DNS: Provides a network IP address for a host on an IP network automatically. The Default Gateway field becomes unavailable. Enter the following information: Enter one or more local search domains in the Search Domain text box, each separated by a space. You must enter valid hostnames. You can use search domains to avoid typing the complete address of domains that you use frequently. The search domains that you enter are automatically appended to names that you specify for purposes such as Active Directory configuration, data migration sources, HTTPS proxy, and NTP server. For example, if you specify the search domain mycompany.com, then typing server1 for one of these purposes would connect to server1.mycompany.com. Enter the IP address for your primary DNS server in the Primary DNS server text box. You must enter a valid hostname or IP address. Enter the IP address for your secondary DNS server in the Secondary DNS server text box (if applicable). You must enter a valid hostname or IP address. Static: Address information must be entered manually. Enter the following information: Enter a default gateway address in the Default Gateway text box. The gateway address must match a subnet of a defined static network. Enter one or more local search domains in the Search Domain text box, each separated by a space. You must enter valid hostnames. You can use search domains to avoid typing the complete address of domains that you use frequently. The search domains that you enter are automatically appended to names that you specify for purposes such as Active Directory configuration, data migration sources, HTTPS proxy, and NTP server. For example, if you specify the search domain mycompany.com, then typing server1 for one of these purposes would connect to server1.mycompany.com. Enter the IP address for your primary DNS server in the Primary DNS server text box. You must enter a valid hostname or IP address. Enter the IP address for your secondary DNS server in the Secondary DNS server text box (if applicable). You must enter a valid hostname or IP address. Nasuni Filer Administration Guide

276 Network Configuration 7. Click Save Network Configuration to accept your entries. The Confirm Network Changes page appears. Figure 11-13: Confirm Network Changes page. 8. Enter a Username (case-sensitive) and Password (case-sensitive) that has permission to perform this operation, then click Submit. Your changes are saved. A message box appears indicating that you will be disconnected briefly from the user interface while the changes are applied. Close this message box and refresh the page, or re-access the Nasuni Filer with your new IP address. Nasuni Filer Administration Guide

277 Quality of Service Settings Quality of Service Settings Quality of Service (QoS) settings specify the inbound and outbound bandwidth limit for moving data to and from the Nasuni Filer, such as snapshots to cloud storage. By default, the outbound bandwidth limit for snapshots is 2 megabits per second, but Nasuni does not recommend keeping that bandwidth. You can change this limit as needed. You can also create additional Quality of Service (QoS) rules for different days and times. A Nasuni Filer can have a maximum of 12 rules. Note: When you create one or more Quality of Service rules, the default Quality of Service bandwidth becomes unlimited during any time that is not defined by a rule. Note: If the inbound Quality of Service is too low, and data must be obtained from cloud storage, data access might be affected. Note: If the outbound Quality of Service is large or unlimited, and the inbound Quality of Service is small, the limited inbound bandwidth for return packets (such as acknowledgements) might affect the outbound bandwidth. You can set inbound and outbound bandwidth limitations for specific days and between specific hours. For example, if you specify 100 kilobits per second outbound for Monday through Friday from 8:00 AM to 3:00 PM, then the Nasuni Filer configures the outbound bandwidth to a maximum of 100 kilobits per second during that period, but does not limit the bandwidth used outside that period. Snapshots are slower during the limited bandwidth period. Local user read/write operations are not affected. Limiting the bandwidth between specific hours can help decrease network congestion. For example, by configuring snapshots to occur every hour with a bandwidth limit of 50 kilobits a second, a large snapshot completes at a slower rate, but with no impact on network speeds. A snapshot cannot run until the running snapshot is completed. See for a worksheet for planning configurations. Nasuni Filer Administration Guide

278 Quality of Service Settings Adding a Quality of Service rule To add a new Quality of Service rule: 1. Click Configuration, then select Quality of Service from the list. The Quality of Service Settings page appears. Figure 11-14: Quality of Service Settings page. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. 2. Click Add Quality of Service Rule. The Add Quality of Service Rule dialog box appears. Figure 11-15: Add Quality of Service Rule dialog box. Note: You cannot have a rule that applies to the same day and hour as another rule. 3. Select the days during which you want to limit bandwidth (for example, Sunday to Saturday). To select or deselect all days, click Select/Deselect all. 4. To apply this rule 24 hours per day for each day selected, select the 24 Hours/Day check box. Nasuni Filer Administration Guide

279 Quality of Service Settings 5. Otherwise, from the Start drop-down list, select the time that you want to start limiting bandwidth on the selected days. From the Stop drop-down list, select the time that you want to stop limiting bandwidth on the selected days. 6. Enter the Outbound Limit value, and select the units from the drop-down list. Use 0 (zero) to specify no limit. 7. Enter the Inbound Limit value, and select the units from the drop-down list. Use 0 (zero) to specify no limit. 8. Click Add Rule to accept your selections. The new rule appears on the Quality of Service Settings page. Changing a Quality of Service rule Edit To change an existing Quality of Service rule: 1. Click Configuration, then select Quality of Service from the list. The Quality of Service Settings page appears. Figure 11-16: Quality of Service Settings page. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. Nasuni Filer Administration Guide

280 Quality of Service Settings 2. Find the rule that you want to change, then click Edit Rule beside that rule. The Edit Quality of Service Rule dialog box appears. Figure 11-17: Edit Quality of Service Rule dialog box. Note: You cannot have a rule that applies to the same day and hour as another rule. 3. Select the days during which you want to limit bandwidth (for example, Sunday to Saturday). To select or deselect all days, click Select/Deselect all. 4. To apply this rule 24 hours per day for each day selected, select the 24 Hours/Day check box. 5. Otherwise, from the Start drop-down list, select the time that you want to start limiting bandwidth on the selected days. From the Stop drop-down list, select the time that you want to stop limiting bandwidth on the selected days. 6. Enter the Outbound Limit value, and select the units from the drop-down list. Use 0 (zero) to specify no limit. 7. Enter the Inbound Limit value, and select the units from the drop-down list. Use 0 (zero) to specify no limit. 8. Click Save Rule to accept your selections. The changed rule appears on the Quality of Service Settings page. Nasuni Filer Administration Guide

281 Quality of Service Settings Deleting a Quality of Service Rule To delete an existing Quality of Service rule: 1. Click Configuration, then select Quality of Service from the list. The Quality of Service Settings page appears. Figure 11-18: Quality of Service Settings page. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. 2. Find the rule that you want to delete, then click Delete Rule beside that rule. The rule is removed from the list. Nasuni Filer Administration Guide

282 Filer Time Configuration Filer Time Configuration Edit You can set the time zone and time server for the Nasuni Filer, which are necessary for notifications and file sharing purposes. The time zone setting you select should be for the region where the Nasuni Filer is physically located. For example, if you are located in the eastern part of the United States, use US/ Eastern. See for a worksheet for planning configurations. To configure the time zone and source settings, follow these steps: 1. Click Configuration, then select Time Configuration. The Filer Time Configuration page appears. Figure 11-19: Filer Time Configuration page. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. 2. From the Time Zone drop-down list, select a time zone. Time zones are listed alphabetically by country (such as Portugal ), city (such as Europe/Zagreb, and abbreviation (such as GMT ). 3. In the Time Server text box, enter the hostnames of one or more valid Network Time Protocol (NTP) servers, separated by commas. By default, all Nasuni Filers are set to use Nasuni's NTP server, time.nasuni.com, to set the time daily. If you cannot open port 123 in your firewall to access time.nasuni.com, you should change to an internal NTP server. You can also specify using NTP services from Active Directory domain controllers. See Domain Settings on page 272. Nasuni Filer Administration Guide

283 Filer Time Configuration 4. Click Save Time Configuration to accept your selection. The message Timezone set; you may be disconnected while your changes are applied. appears. Nasuni Filer Administration Guide

284 FTP Settings FTP Settings You can view and configure FTP/SFTP settings for the Nasuni Filer. These advanced features of the FTP/SFTP protocol apply to all volumes on the Nasuni Filer. Tip: In order to access data using the FTP/SFTP protocol, the following steps are necessary: 1. Create a CIFS or NFS volume. See Adding a Volume on page Enable the FTP protocol on the volume. See Enabling multiple volume protocols on page (Optional) Configure FTP settings. See Configuring FTP settings on page Add a new FTP/SFTP directory. See Adding FTP directories for a volume on page (Optional) Create a permission group that has storage access. See Adding Permission Groups on page (Optional) Create a user in a permission group that has storage access. See Adding Users on page 323. Active Directory users can log in for FTP access just as they do for CIFS access. Also, if anonymous access is enabled, you don't need a specific group or user. 7. Access files using the FTP/SFTP protocol. See Accessing data using the FTP/SFTP protocol on page 141. Configuring FTP settings To configure FTP settings, follow these steps: 1. Click Configuration, then select FTP Settings. The General FTP Settings page appears. Figure 11-20: General FTP Settings page. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. Nasuni Filer Administration Guide

285 FTP Settings 2. Optionally, in the Masquerade Address text box, type an IP address (not a DNS hostname) to present to the client instead of the local server's IP address or DNS hostname. 3. Optionally, in the Idle Login Timeout text box, type the time in seconds to wait before closing an idle connection. Zero (0) means never close an idle connection. 4. Optionally, in the Anonymous Access Username text box, type the username that the user must log in with in order to access any FTP/SFTP directory anonymously. Default: anonymous. The username is case sensitive. 5. Optionally, in the Anonymous Access Group text box, type the group associated with the Anonymous Access Username. 6. Click Save FTP Settings to save your settings. Tip: To enable the FTP protocol for a volume, see Enabling multiple volume protocols on page 135. To add an FTP directory to a volume, see Adding FTP directories for a volume on page 127. Nasuni Filer Administration Guide

286 Domain Settings Domain Settings Microsoft's Active Directory (AD) service is capable of providing security across multiple domains or forests through domain and forest trust relationships. The trusts established between domains allow or deny users access to resources outside their native domain. After you establish the correct trust relationships among your Active Directory servers, you can enable access and permissions for users and groups within the trusted domains. Configuration of trusts between domains is outside the scope of this document. The Nasuni Filer can join one Windows Active Directory domain server and access its users and groups. These users and groups can only be edited through Active Directory tools. The Nasuni Filer joins one domain, called the primary domain. If the customer s environment has valid, active trust relationships between the primary domain and other domains, the Nasuni Filer attempts to discover those domains. You can then select which of the non-primary domains to allow to access the Nasuni Filer. The Nasuni Filer offers support for trusted domains of multiple Active Directory servers. This can simplify enabling access and permissions for users and groups within trusted domains. To use trusted domains of multiple Active Directory servers, you must establish the correct trust relationships among your Active Directory servers. Previously, assistance by Nasuni Support was required to configure and maintain a Nasuni Filer for multiple Active Directory domains and forest trust relationships. However, now the Nasuni Filer directly supports configuration and maintenance in a trusted domain environment. There are two aspects to trusted domain support: authentication and sharing. The authentication aspect allows a user to access a Nasuni Filer's resources in a different domain. The sharing aspect enables Nasuni Filers in different domains to access the same data. Tip: If the Nasuni Filer has never joined an Active Directory domain, the General Settings page displays the Join Domain button to initiate the process of joining the Nasuni Filer to an Active Directory domain. Clicking Join Domain starts a wizard that guides you through the process of joining a Nasuni Filer to a domain. When the Nasuni Filer joins a domain, you are prompted to decide which of any volumes that existed before the join should use Active Directory authentication and which should act as if the Nasuni Filer is still in Public mode. The Domain Settings page offers settings to join the Nasuni Filer to a domain, to enable or disable access by secondary domains, and to leave the current domain. Note: The Domain Settings page is not available until the Nasuni Filer has joined an Active Directory domain. See Joining a Nasuni Filer (not previously joined to any domain) to a domain on page 277. Joining a Nasuni Filer (that has not previously joined any domain) to a domain To join a Nasuni Filer (that has not previously joined any domain) to an Active Directory domain, see Joining a Nasuni Filer (not previously joined to any domain) to a domain on page 277. Nasuni Filer Administration Guide

287 Domain Settings Joining the Nasuni Filer to an Active Directory domain Join Caution: If the Nasuni Filer is already joined to an Active Directory domain, this procedure causes the Nasuni Filer to leave that Active Directory domain. The Nasuni Filer loses the resources of all domains that the Nasuni Filer is aware of, including users and groups. A Nasuni Filer that has left the domain does not provide CIFS access to any clients. To join the Nasuni Filer to an Active Directory domain, follow these steps: 1. Click Configuration, then select Domain Settings from the list. The CIFS Domain Settings page appears. Figure 11-21: CIFS Domain Settings page. The current source domains, if any, appear in the Source Domains list. 2. Continue with step 3 of the Joining a Nasuni Filer (not previously joined to any domain) to a domain procedure on page 278. Nasuni Filer Administration Guide

288 Domain Settings Viewing Active Directory domains View To view Active Directory domains, follow these steps: 1. Click Configuration, then select Domain Settings from the list. The CIFS Domain Settings page appears. Figure 11-22: CIFS Domain Settings page. 2. If the Nasuni Filer is actively joined to Active Directory, and the Nasuni Filer passes the health check, a banner across the top of the page says, The system is actively joined to Active Directory.. 3. If the Nasuni Filer has successfully joined the domain, a list of Source Domains appears. For each Source Domain in the list, the following information appears: Domain: The name of the Active Directory domain. NT Name: The local Windows NT-compatible workgroup name of the Active Directory domain. Enabled: An indication of whether resources in the Active Directory Domain have access to the Nasuni Filer: Yes or No. 4. To update the list of trusted domains that the Nasuni Filer is aware of, click Update Domains. Nasuni Filer Administration Guide

289 Domain Settings Allowing Active Directory domains to access the Nasuni Filer To allow a Source Domain to access the Nasuni Filer, follow these steps: 1. Click Details for the Source Domain that you want to allow to access the Nasuni Filer. The Domain Source Settings dialog box appears. Figure 11-23: Domain Source Settings dialog box. 2. To allow resources in the Source Domain to access the Nasuni Filer, select the Enable Source check box. Otherwise, clear the check box. Note: The Source for the domain that the Nasuni Filer is joined to (the primary domain) cannot be disabled. 3. Click Save to save your changes. Otherwise, click Cancel. Leaving an Active Directory domain Leave Caution: This procedure causes the Nasuni Filer to leave the Active Directory domain. The Nasuni Filer loses the resources of all domains that the Nasuni Filer is aware of, including users and groups. A Nasuni Filer that has left the domain does not provide CIFS access to any clients. To leave an Active Directory domain, follow these steps: 1. To leave the Active Directory domain, click Leave Domain. The Leave the Domain dialog box appears. Figure 11-24: Leave the Domain dialog box. Nasuni Filer Administration Guide

290 Domain Settings 2. In the User Name text box, enter a username that has permissions for removing computers from the Active Directory domain. Note: Avoid using the domain name in this field. The username should NOT be in the following formats: [email protected] or domain\username. 3. In the Password text box, enter the password for the User Name. Confirm this password in the Repeat Password text box. 4. Click Leave to have the Nasuni Filer leave the Active Directory domain. Otherwise, click Cancel. The Nasuni Filer leaves the Active Directory domain. Nasuni Filer Administration Guide

291 General CIFS Settings General CIFS Settings You can configure CIFS settings and, if the Nasuni Filer has never joined an Active Directory domain, join the Nasuni Filer to an Active Directory domain. See Domain Settings on page 272 for details about Active Directory domains. Joining a Nasuni Filer (not previously joined to any domain) to a domain Join If the Nasuni Filer has not previously joined any Active Directory domain before, follow these steps: 1. Click Configuration, then select General Settings from the list. On the General CIFS Settings page, the Join Domain button is available. Figure 11-25: Join Domain button available on General CIFS Settings page. Nasuni Filer Administration Guide

292 General CIFS Settings 2. To join an Active Directory domain, click Join Domain. The CIFS Domain Settings page appears. Figure 11-26: CIFS Domain Settings page. This message appears at the top of the page: The system has not yet joined an Active Directory domain. 3. In the Full Windows Domain text box, enter the fully qualified Active Directory domain name that you want the Nasuni Filer to join. For example, subdomain.domain.com. The Nasuni Filer joins this domain to authenticate users from the Active Directory server. 4. Optionally, in the Workgroup text box, enter a local Windows NT-compatible workgroup name (15 characters maximum) in which the Nasuni Filer can be accessed. To use the default workgroup for the domain, leave this field blank. Some domains need this value if the name cannot be automatically determined. 5. Optionally, in the Computer OU text box, enter a domain organization unit in which the Nasuni Filer is placed. The computer s container is the default location. If you leave this value blank, the Nasuni Filer is placed in a default location. 6. Optionally, to display advanced options, click Show Advanced Options. The Advanced Options pane appears. Figure 11-27: Advanced Options pane. Nasuni Filer Administration Guide

293 General CIFS Settings a. (Optional) In the Domain Controller text box, enter the fully qualified domain name of the primary domain controller. For example, DomainControllerName.domain.com. Entering a Domain Controller name forces the Nasuni Filer to use only that domain controller. However, leaving the Domain Controller text box blank causes the Nasuni Filer to use the primary domain controller on the join, and also allows for domain controller failover. Unless you want only one specific domain controller to be used, leave the Domain Controller text box blank. In particular, if you want support for trusted domains of multiple Active Directory servers, leave the Domain Controller text box blank. b. To use Network Time Protocol (NTP) services provided by domain controllers, select NTP from Domain Controllers. If no NTP services are available from domain controllers, the current NTP server is used. See Filer Time Configuration on page 268. c. To close this display, click Hide Advanced Options. 7. Click Save Settings to save these settings and join the Active Directory domain. To reset settings, click Reset. 8. The Active Directory Authentication dialog box appears. Figure 11-28: Active Directory Authentication dialog box. a. In the User Name text box, enter a username that has permissions for joining computers to the Active Directory domain. Note: Avoid using the domain name in this field. The username should NOT be in the following formats: [email protected] or domain\username. b. In the Password text box, enter the password for the User Name. Confirm this password in the Repeat Password text box. c. Click Continue to have the Nasuni Filer join the Active Directory domain. Otherwise, click Cancel. Nasuni Filer Administration Guide

294 General CIFS Settings 9. If the Nasuni Filer has volumes that were created while the Nasuni Filer was not joined to any domain, the Volume Selection dialog box displays a list of volumes that require a decision about authentication. Figure 11-29: Volume Selection dialog box. For each volume in the list, to enable Active Directory authentication for that volume, select the Enable for Active Directory check box. Volumes that are not enabled for Active Directory authentication act as if the Nasuni Filer is still in Public mode. Note: If a volume ends up with the wrong authentication mode, contact Nasuni Technical Support. Click Continue to continue. 10. If any other Nasuni Filers on your account have been configured for access to the Active Directory domain that you are joining, the Fetching Domain Setting from other Filers dialog box appears. Figure 11-30: Fetching Domain Setting from other Filers dialog box. Configuration information is gathered for any other Nasuni Filers on your account that already joined the Active Directory domain. Note: Nasuni recommends that you allow processing to continue until complete. Nasuni Filer Administration Guide

295 General CIFS Settings 11. If any other Nasuni Filers on your account have been configured for access to the Active Directory domain that you are joining, the Domains and Trusts dialog box displays the Configuration Source drop-down list. Figure 11-31: Domains and Trusts dialog box. From the Configuration Source drop-down list, select one of the existing configurations for access to the domain from another Nasuni Filer. Note: Nasuni recommends that you select one of the existing configurations from the Configuration Source drop-down list, in order to maintain consistent Active Directory configurations among all the Nasuni Filers. Alternatively, select Local Settings to configure settings manually. Click Continue to continue. Nasuni Filer Administration Guide

296 General CIFS Settings 12. If the Nasuni Filer successfully joins the Active Directory domain, the joined domain and all known trusted domains appear in the list of Source Domains. Figure 11-32: New list of Source Domains. The list of Source Domains includes the requested Active Directory primary domain and any associated trusted domains. For each domain in the list, the following information appears: Domain: The name of the Active Directory domain. NT Name: The local Windows NT-compatible workgroup name of the Active Directory domain. Enabled: An indication of whether resources in the Active Directory domain have access to the Nasuni Filer: Yes or No. Note: Only users and groups from enabled Active Directory domains have access to CIFS resources on this Nasuni Filer. To enable or disable whether resources in an Active Directory domain have access to the Nasuni Filer, see Allowing Active Directory domains to access the Nasuni Filer on page 275. To leave the Active Directory domain, see Leaving an Active Directory domain on page 275. Nasuni Filer Administration Guide

297 General CIFS Settings Configuring CIFS settings Edit To configure CIFS settings, follow these steps: 1. Click Configuration, then select General Settings from the list. The General CIFS Settings page appears. Figure 11-33: General CIFS Settings page. 2. If the current security mode is Active Directory, the Domain Settings button is available. To configure Active Directory domain settings, click Domain Settings. The CIFS Domain Settings page appears. See Domain Settings on page 272 for details. Alternatively, if the current security mode is Public, the Join Domain button is available. To join an Active Directory domain, click Join Domain. See Joining a Nasuni Filer (not previously joined to any domain) to a domain on page 277 for details. 3. Alternatively, if the current security mode is Public, the Workgroup text box is available. In the Workgroup text box, enter a local Windows NT-compatible workgroup name (15 characters maximum) in which the Nasuni Filer can be accessed. To use the default workgroup for the domain, leave this field blank. Some domains need this value if the name cannot be automatically determined. 4. Optionally, in the Administrative User(s) text box, enter a list of administrative users, separated by commas or semicolons. These values are domain user accounts. Entering a name provides each specified user with full access to all CIFS shares and rights to change file and folder permissions, regardless of current ACL settings. Nasuni Filer Administration Guide

298 General CIFS Settings 5. Optionally, to display advanced options, click Show Advanced Options. The Advanced Options pane appears. Figure 11-34: Advanced Options pane. Note: For sites with mostly Windows clients, the default settings are best. Note: If this Nasuni Filer is under the control of the Nasuni Management Console, this pane does not appear, because you use the Nasuni Management Console to perform these tasks. a. From the Allocation Roundup Size drop-down list, select the allocation roundup size. Unless you have applications that require disabling this option, select Default (1 MiB). Disabling this option can degrade performance because it rounds up the file sizes on disk. b. From the Protocol Level drop-down list, select the maximum version of the CIFS/SMB protocol that the server negotiates with the client, from the following: CIFS: Common Internet File System protocol, also called SMB 1.0. CIFS & SMB2: Server Message Block version 2.0. SMB 2.0 offers improved performance over SMB 1.0. CIFS & SMB3: Server Message Block version 3.0. SMB 3.0 offers improved performance and security over SMB 2.0. Tip: Best practice is to select CIFS & SMB2. Using SMB2 can improve performance significantly. c. To allow clients to use Portable Operating System Interface (POSIX) semantics, select the Enhanced Support for POSIX Clients check box (selected by default). If you clear this option, POSIX clients can still connect. However, they do not have the full range of file server operations. Tip: CIFS shares that have OSX clients should select the Enhanced Support for POSIX Clients check box. d. To close this display, click Hide Advanced Options. 6. Click Save CIFS Settings to save your settings, or else click Reset. The Change General CIFS Settings? dialog box appears. Note: Changing these settings only affects new CIFS/SMB clients. You must disconnect or reset an existing client's connection to use the new settings. 7. Click Continue Saving. Your CIFS settings are saved. Otherwise, click Cancel. Nasuni Filer Administration Guide

299 API Access Keys API Access Keys The Nasuni VSS Hardware Provider supports creating shadow copies of iscsi volumes for third-party Windows applications. This provider provides a fast, consistent method to take snapshots of iscsi volumes on the Nasuni Filer. For more details, see Using the Nasuni VSS Hardware Provider, available at This consists of two pieces: Nasuni Provider: This is a service that runs on a Windows Server machine (including Windows Server 2003, Windows Server 2008, and Windows Server 2012). This service initiates shadow copies for iscsi volumes on a registered Nasuni Filer. The provider communicates with the Nasuni Filer over HTTPS. Registering the Nasuni Filer with the provider requires the Nasuni Filer IP address, an API key name, and a key passcode. Nasuni Filer API Access Keys: On the Nasuni Filer or Nasuni Management Console user interfaces, the administrator needs to create a Key Name and generate a Key Passcode. To obtain an API Access Key and Passcode, follow these steps: 1. On the Nasuni Filer with the iscsi volume, click Configuration and select API Access Keys from the drop-down menu. The API Access Keys page appears. Figure 11-35: API Access Keys page. 2. Click Add API Key. The Add API Key dialog box appears. Figure 11-36: Add API Key dialog box. 3. In the Name text box, enter a name for this API key. Use a name that is meaningful to you, such as vsskey. Nasuni Filer Administration Guide

300 API Access Keys 4. Click Create Key. The Nasuni Filer generates a Key Passcode for this key. The Successfully Generated API Key dialog box appears. 5. Copy and store the Key Passcode. 6. Click Close. Figure 11-37: Successfully Generated API Key dialog box. 7. The new key appears in the API Access Keys list. 8. To regenerate the Key Passcode, click Update. 9. To delete this key, click Delete. Note: If you update or delete a key, and then add another key, you must re-do the Configuring Nasuni VSS Hardware Provider procedure. Nasuni Filer Administration Guide

301 Encryption Key Management Encryption Key Management The Nasuni Filer automatically encrypts your data at your premises using the OpenPGP encryption protocol, with 256-bit Advanced Encryption Standard (AES-256) encryption as the default encryption. The data remains encrypted in cloud storage. You can escrow your encryption keys with Nasuni (or a trusted third party), or generate and store your own encryption keys. Your data is encrypted and compressed and is never visible to Nasuni. All data on a volume is encrypted using one or more encryption keys before being sent to cloud storage. Volumes may be encrypted with one or more encryption keys, and encryption keys may be used for any number of volumes. There are several actions you can perform on encryption keys, including adding new encryption keys, enabling or disabling encryption keys, escrowing encryption keys with Nasuni, and, under certain circumstances, deleting encryption keys. At least one encryption key must be enabled for a volume, but several encryption keys can be enabled at the same time. When multiple encryption keys are enabled, all of the enabled encryption keys are used to encrypt data in such a way that any one of the encryption keys can decrypt the data. There are several reasons you might want to disable an encryption key, such as, when someone with access to the encryption key leaves the company, or if your enterprise has a policy of rotating encryption keys periodically. When you disable an encryption key, no future data is encrypted with that encryption key. However, all data previously encrypted by that disabled encryption key remains encrypted by that disabled encryption key. For this reason, before you disable an encryption key, you should consider establishing a snapshot retention policy that removes the data that was encrypted with the disabled encryption key. Because volumes must have at least one encryption key associated with them, in practice you add a new encryption key to a volume first, and then disable the existing encryption key. You can delete encryption keys, but only in the case where they are not being used by any volumes. You cannot modify encryption keys stored on the system. For security reasons, encryption keys that you upload cannot be downloaded from the system. You can only download encryption keys that the Nasuni Filer has generated internally. Note: To add an encryption key to a volume, see Adding Encryption Keys to a Volume on page 81. See for a worksheet for planning configurations. Nasuni Filer Administration Guide

302 Encryption Key Management Viewing information about encryption keys View To view information about encryption keys: 1. Click Configuration, then select Encryption Keys from the list. The Encryption Keys page appears. Figure 11-38: Encryption Keys page. On this page, you can view information about each of the encryption keys currently in use, including the encryption key name, fingerprint, encryption key ID, algorithm, length (in bits), whether the encryption key is escrowed by Nasuni, and which volumes use the encryption key. The fingerprint is a cryptographic hash of the encryption key. The key ID is a shorter version of the fingerprint of the encryption key, generally including just the last 8 digits. 2. Optionally, you can click a volume hyperlink to go to the Volume properties page. See Encryption Key Management on page 77 for details. Nasuni Filer Administration Guide

303 Encryption Key Management Adding (Importing or Uploading) Encryption Keys Upload You can generate your own encryption keys using any OpenPGP-compatible program, such as PGP or GnuPG. You can then add (import or upload) the encryption key to the Nasuni Filer. The encryption key is used to encrypt your data before it is sent to cloud storage and decrypt data when it is read back. The Nasuni Filer accepts multiple encryption algorithms for encryption keys. Important: Imported encryption keys are not automatically escrowed. You MUST SAVE all imported encryption keys to another location outside the Nasuni Filer, so that they are available if needed for disaster recovery. All encryption keys associated with a volume must be recovered as part of the disaster recovery process. To escrow encryption keys with Nasuni, see Escrowing Encryption Keys with Nasuni on page 291. To add (import or upload) an encryption key: 1. Click Configuration, then select Encryption Keys from the list. The Encryption Keys page appears. Figure 11-39: Encryption Keys page. 2. Click Upload Encryption Key(s). The Import OpenPGP Key(s) page appears. Figure 11-40: Import OpenPGP Key(s) page. 3. Click Choose File, then navigate to the encryption key file. This file should be OpenPGP compatible. Nasuni Filer Administration Guide

304 Encryption Key Management 4. If an encryption key passphrase is needed, enter the encryption key passphrase in the Key Passphrase text box. 5. Click Import Key. The encryption key is imported to the Nasuni Filer. Tip: Imported encryption keys are not automatically escrowed. Save all imported encryption keys to another location outside the Nasuni Filer, so that they are available if needed for disaster recovery. Note: You cannot download uploaded encryption keys. Downloading (Exporting) Generated Encryption Keys Download If you are using encryption keys generated internally by the Nasuni Filer, you can export (download) and escrow your encryption keys with Nasuni or a trusted third party. To export (download) encryption keys: 1. Click Configuration, then select Encryption Keys from the list. The Encryption Keys page appears. Figure 11-41: Encryption Keys page. 2. Click Download generated keys. Depending on your browser, a message box might appear; if so, navigate to an appropriate folder and save the encryption key file. The encryption key file is saved with a.pgp extension. Tip: If you are planning on trying the disaster recovery functionality during trial mode, download your encryption keys to a safe location first. Nasuni Filer Administration Guide

305 Encryption Key Management Escrowing Encryption Keys with Nasuni Escrow You can escrow your encryption keys with Nasuni. Escrowing an encryption key with Nasuni means that you can, at any time, request the encryption key during a disaster recovery from Nasuni. Your encryption key is protected on Nasuni servers using the same security practices that we use for all encryption keys escrowed with Nasuni. To escrow encryption keys with Nasuni: 1. Click Configuration, then select Encryption Keys from the list. The Encryption Keys page appears. Figure 11-42: Encryption Keys page. 2. For the encryption key that you want to escrow with Nasuni, click Escrow key with Nasuni. The Escrow your encryption key with Nasuni page appears. Figure 11-43: Escrow your encryption key with Nasuni page. Nasuni Filer Administration Guide

306 Encryption Key Management 3. Enter a Username (case-sensitive) and Password (case-sensitive) that has permission to perform this operation. Caution: You are about to permanently escrow your encryption key with the Nasuni Corporation. This process is irreversible. 4. Click Escrow Key. Your encryption key is escrowed with Nasuni. Nasuni Filer Administration Guide

307 Encryption Key Management Deleting Encryption Keys Delete You can delete encryption keys, as long as the encryption key is not currently assigned to a volume and never has been assigned to a volume. Encryption keys that were once assigned to a volume, but are now disabled, might be needed for disaster recovery procedures and so cannot be deleted. To delete an encryption key, follow these steps: 1. Click Configuration, then select Encryption Keys from the list. The Encryption Keys page appears. Figure 11-44: Encryption Keys page. 2. For the encryption key that you want to delete, click Delete This Key. The Delete an OpenPGP Key dialog box appears. Figure 11-45: Delete an OpenPGP Key dialog box. 3. Enter a Username (case-sensitive) and Password (case-sensitive) that has permission to perform this operation. Caution: You are about to permanently delete this encryption key. This process is irreversible. 4. Click Delete. Your encryption key is deleted. Nasuni Filer Administration Guide

308 Firewall Firewall Edit You can limit which network hosts are allowed to connect to the Nasuni Filer user interface and the Nasuni Support SSH port, which provides firewall protection. Note: In addition to this protection, you can also configure separate access to CIFS shares, NFS exports, and FTP/SFTP directories, as detailed in Editing a CIFS Share on page 113, Editing an NFS Export on page 120, and Editing FTP directories on page 132. To configure firewall protection, follow these steps: 1. Click Configuration, then select Firewall from the list. The Firewall page appears. Figure 11-46: Firewall page. Nasuni Filer Administration Guide

309 Firewall 2. In the Traffic Group area, to configure the firewall policy for each Traffic Group, click Edit beside the Traffic Group. The Edit Firewall Policy dialog box appears. Figure 11-47: Edit Firewall Policy dialog box. a. From the Policy drop-down list, select one of the following choices: Note: All policies permit outbound traffic. That traffic is fully controlled by the configuration of the Nasuni Filer's local networks and gateways. All Protocols Permitted: This policy allows all inbound traffic. Deny All Incoming Connections: This policy allows no inbound traffic. Client Protocols Permitted: This policy allows only CIFS, CIFS Web, NFS, FTP, and iscsi inbound traffic. Mobile/Web Clients Permitted: This policy allows only Mobile Access or CIFS Web inbound traffic, such as Web Access. Custom Protocol Selection: This policy allows selected inbound traffic. You can select one or more of the following inbound protocols: Admin UI: Traffic to the user interface. FTP: FTP inbound traffic. iscsi: iscsi inbound traffic. Mobile: Mobile Access inbound traffic. NFS: NFS inbound traffic. SFTP (SSH FTP): SSH FTP inbound traffic. CIFS/SMB: CIFS/SMB inbound traffic. SNMP: SNMP inbound traffic. SSH: SSH inbound traffic. Nasuni Filer Administration Guide

310 Firewall Warning: If you disable Mobile Access and CIFS/SMB Web inbound traffic and enable Admin UI traffic, you might not be able to open the default URL of the Nasuni Filer user interface. Normally, the default URL is redirected from port 80 to port 8443, but this cannot happen when Mobile Access and CIFS Web inbound traffic are disabled. Use this URL to access the Nasuni Filer user interface: Nasuni Filer URL>:8443 b. Click Save to save your changes. Otherwise, click Cancel. 3. In the Filer GUI Hosts text box, enter a comma-separated list of IP addresses or subnet addresses of hosts that you permit to access your Nasuni Filer user interface. If the text box is blank, any host can access your Nasuni Filer user interface. 4. In the Support SSH Hosts text box, enter a comma-separated list of IP addresses or subnet addresses of hosts that you permit to connect to your Nasuni Filer s Support SSH port. If the text box is blank, any host can access your Nasuni Filer s Support SSH port. Note: Setting this field does not prevent the use of the Nasuni Remote Support Service, as detailed in Remote Support Service on page Click Save Firewall Settings to save your entries. The message Updated firewall configuration appears. Tip: If you configure the firewall in such a way that you cannot access the Nasuni Filer user interface, you can reset the firewall using the console for the Nasuni Filer. For the Nasuni Filer hardware appliance, use a keyboard and monitor attached to the hardware appliance. For the Nasuni Filer virtual machine, use the virtual machine console window. The console prompt appears. Press Enter to access the Service menu. The login prompt appears. Enter the username and password. The login username is service, and the default password is service. The Service Menu appears. Enter resetfirewall The firewall resets. Nasuni Filer Administration Guide

311 Quota Settings Quota Settings Report The Nasuni Filer can send reports to administrators or to users about which directories are near or over their quota. You can send reports immediately, or schedule days and times to send reports. Tip: You can use automatic quota reports to monitor usage by setting the threshold to 0 (zero). For details about setting a directory quota, see Setting Quota or Rule on page 186. You must also configure settings and enable Capacity Alerts in order to send quota reports. See Settings on page 247. Viewing quota report configuration To view quota report configuration, follow these steps: 1. Click Configuration, then select Quota Settings from the list. The Quota Settings page appears. Figure 11-48: Quota Settings page. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. A list of the currently configured quota reports includes the days to send reports, the time on those days to begin sending reports, and the types of reports to send at that time. Nasuni Filer Administration Guide

312 Quota Settings Adding a new quota report To add a new quota report, follow these steps: 1. Click Configuration, then select Quota Settings from the list. The Quota Settings page appears. Figure 11-49: Quota Settings page. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. 2. To add a new scheduled quota report, click Add Scheduled Quota Report. The Add Quota Report Schedule dialog box appears. Figure 11-50: Add Quota Report Schedule dialog box. 3. Select the days on which you want to send quota reports. To select or deselect all days, click Select/Deselect all. 4. From the Start drop-down list, select the time that you want to start sending quota reports. 5. To send quota reports to administrators, select Administrative Report. The quota reports are sent to the addresses configured as described in Settings on page 247. The administrator report includes all directories near or over their quota. Nasuni Filer Administration Guide

313 Quota Settings 6. To send quota reports to users, select User Report. The quota reports are sent to the addresses configured as described in Setting Quota or Rule on page 186. The user report includes only the user s directories near or over their quota. 7. In the Report Threshold text box, enter a percentage of the configured directory quota. Quota reports are sent when data nears or exceeds this percentage of the quota. To configure directory quotas, see Setting Quota or Rule on page 186. Tip: You can use automatic quota reports to monitor usage by setting the threshold to 0 (zero). 8. Click Save to save your changes. Otherwise, click Cancel. Sending a quota report (capacity report) now You can send a quota report (capacity report) immediately, even if the quota report threshold is not exceeded. To send a quota report now, follow these steps: 1. On the Quota Settings page, click Send Quota Report Now. The Send Quota Report dialog box appears. Figure 11-51: Send Quota Report dialog box. 2. To send quota reports to administrators, select Administrative Report. The quota reports are sent to the addresses configured in Settings on page 247. The administrator report is sent regardless of whether any directories are near or over their quota. 3. To send quota reports to users, select User Report. The quota reports are sent to the addresses configured in Setting Quota or Rule on page 186. The user report is sent regardless of whether any directories are near or over their quota. 4. In the Report Threshold text box, enter a percentage of the configured directory quota. Quota reports are sent regardless of whether any directories are near or over their quota. To configure directory quotas, see Setting Quota or Rule on page Click Send to send the report. Otherwise, click Cancel. Nasuni Filer Administration Guide

314 Quota Settings Changing an existing quota report To change an existing quota report, on the Quota Settings page, click Edit Report for that report. The Edit Quota Report Schedule dialog box appears. Follow the steps as for Adding a new quota report on page 298, starting with step 3. Deleting a quota report To delete an existing quota report, on the Quota Settings page, click Delete Report. The Delete Scheduled Quota Report dialog box appears. To delete the quota report, click Delete Report. Otherwise, click Cancel. Nasuni Filer Administration Guide

315 SSL Certificates SSL Certificates You can view the SSL CA-signed certificate or self-signed certificate that you can use when accessing the Nasuni Filer user interface. By default, the Nasuni Filer is preloaded with a self-signed SSL certificate that is unique to the Nasuni Filer. You can also generate a new Certificate Request to submit to a Certificate Authority (CA) for signing. When you receive the signed certificate from the CA, you can associate the CA-signed certificate (and optional certificate chain) with the request. After this is done, you can use that CA-signed certificate to manage the Nasuni Filer. Note: If something ever goes wrong with the certificates and you are unable to access the Nasuni Filer user interface, use the service menu on the console of your hardware appliance or virtual machine to reset the certificate to the default self-signed certificate. See Resetting an SSL Certificate on page 314 for details. Note: A notification occurs when the active SSL certificate is less than 30 days from expiring. You can also upload an existing SSL certificate. This can be in the form of an SSL key file, an SSL key and certificate file, an SSL certificate, or an SSL certificate chain. You can then use that uploaded certificate to manage the Nasuni Filer. You can also copy, replace, save, and delete SSL certificates and SSL certificate chains. Viewing SSL CA-signed Certificates or Self-Signed Certificate View To view current SSL CA-signed certificates or self-signed certificate: 1. Click Configuration, then select SSL Certificates from the list. The SSL Certificates page appears. Figure 11-52: SSL Certificates page. The current SSL certificates, self-signed certificates, and SSL certificate requests appear in the list. Nasuni Filer Administration Guide

316 SSL Certificates 2. To view details of a certificate, click the hyperlink of the certificate. The Certificate Details box appears. Figure 11-53: Certificate Details box. The certificate information displayed includes the following: Name: The name of the certificate. Type: The type of certificate. Subject: The string containing the subject of the certificate. Issuer: The string containing the issuing party. Signature type: The type of cryptographic signature of the certificate. Note: The signature type Sha1WithRsaEncryption is being deprecated and should be avoided, if possible. Start Date: The date that the certificate becomes effective. End Date: The date that the certificate is no longer in effect. Common Name: The IP address or fully qualified domain name (FQDN) of the web server that receives the SSL certificate. Country Code: The two-letter ISO abbreviation for the country (for example, US for the United States) where your organization's office is legally registered. State/Province: The full name of the state or province where your organization's office is located. Locality Name: The full name of the city where your organization's office is located. Organization: The name under which your organization is legally registered. 3. Click Close to close this box. Nasuni Filer Administration Guide

317 SSL Certificates Generating SSL CA-signed Certificates or a Self-Signed Certificate Add To generate a new SSL CA-signed certificate or a self-signed certificate: 1. Click Configuration, then select SSL Certificates from the list. The SSL Certificates page appears. Figure 11-54: SSL Certificates page. 2. Click Generate Certificate. The Create SSL Certificate Request page appears. Figure 11-55: Create SSL Certificate Request page. Nasuni Filer Administration Guide

318 SSL Certificates 3. In the Management Name text box, enter the name that you use to refer to this certificate. 4. In the Common Name text box, enter the fully qualified domain name (FQDN) or IP address that you use to access the Nasuni Filer user interface. The optional but most common choice is the Nasuni Filer's fully qualified domain name, which is automatically entered. Note: This MUST match the way users connect to the Nasuni Filer. 5. In the Country Code text box, enter the two-letter country code, such as US. 6. In the State/Province Name text box, enter the name of your state or province, such as Massachusetts. 7. In the Locality text box, enter the name of your city or town, such as Boston. 8. In the Organization Name text box, optionally enter the name of your organization, such as Nasuni. 9. To create a self-signed certificate instead of a certificate request, select Self-Sign Certificate. 10. Click Save Certificate. If you selected Self-Sign Certificate, a self-signed certificate is created. Otherwise, a certificate request is created. 11. If you did not select Self-Sign Certificate, to download the certificate request.csr file, on the SSL Certificates page, click Save Request File next to the name of the certificate request in the list. 12. Submit this certificate request to a Certificate Authority (CA) for signing. 13. When you receive the signed certificate file, select Add Signed Certificate from the Actions drop-down list next to the name of the certificate request in the list. The Add Certificate Files dialog box appears. Figure 11-56: Add Certificate Files dialog box. 14. Click Choose File next to Certificate File, then navigate to the PEM- and DER-encoded X.509 file or PKCS#7 certificate file. 15. Optionally, click Choose File next to Certificate Chain File, then navigate to the SSL certificate chain file. Nasuni Filer Administration Guide

319 SSL Certificates 16. Click Save Certificate. The certificate is installed and becomes available in the list of certificates on the SSL Certificates page. Figure 11-57: SSL Certificates page. Nasuni Filer Administration Guide

320 SSL Certificates Copying Existing SSL Certificates You can create a new SSL CA-signed certificate or self-signed certificate by copying an existing SSL certificate. You might need to copy an SSL certificate as part of a manual process for recreating or updating an SSL certificate. To copy an SSL certificate: 1. Click Configuration, then select SSL Certificates from the list. The SSL Certificates page appears. Figure 11-58: SSL Certificates page. 2. For the SSL certificate that you want to copy, select Copy from the Actions drop-down list next to the name of the certificate in the list. The Copy SSL Certificate dialog box appears. Figure 11-59: Copy SSL Certificate dialog box. 3. In the New Management Name text box, enter the new name that you want to use to refer to this SSL certificate. The default name is the name of the original SSL certificate with (2) appended. All other SSL certificate parameters are copied from the original SSL certificate. 4. To create a self-signed certificate instead of a certificate request, select Self-Sign Certificate. 5. Click Copy Certificate. If you selected Self-Sign Certificate, a self-signed certificate is created. Otherwise, a certificate request is created. Nasuni Filer Administration Guide

321 SSL Certificates 6. If you did not select Self-Sign Certificate, to download the certificate request.csr file, on the SSL Certificates page, click Save Request File next to the name of the certificate request in the list. 7. Submit this certificate request to a Certificate Authority (CA) for signing. 8. When you receive the signed certificate file, select Add Signed Certificate from the Actions drop-down list next to the name of the certificate request in the list. The Add Certificate Files dialog box appears. Figure 11-60: Add Certificate Files dialog box. 9. Click Choose File next to Certificate File, then navigate to the PEM- and DER-encoded X.509 file or PKCS#7 certificate file. 10. Optionally, click Choose File next to Certificate Chain File, then navigate to the SSL certificate chain file. 11. Click Save Certificate. The certificate is installed and becomes available in the list of certificates on the SSL Certificates page. Nasuni Filer Administration Guide

322 SSL Certificates Uploading SSL Certificates Uploading To upload an existing SSL certificate: 1. Click Configuration, then select SSL Certificates from the list. The SSL Certificates page appears. Figure 11-61: SSL Certificates page. 2. Click Upload Certificate. The Add Certificate Files page appears. Figure 11-62: Add Certificate Files page. 3. In the Certificate Name text box, enter the name that you use to refer to this certificate. Nasuni Filer Administration Guide

323 SSL Certificates 4. To add an SSL key file or SSL key and certificate bundle file, click Choose File next to Key File, then navigate to the SSL key file or SSL key and certificate bundle file. 5. If an SSL certificate was not part of a bundle file in step 4, to add an SSL certificate, click Choose File next to Certificate File, then navigate to the SSL certificate file. 6. If an SSL certificate chain was not part of a bundle file in step 4, to add an SSL certificate chain file, click Choose File next to Certificate Chain File, then navigate to the SSL certificate chain file. 7. Enter the Password, if required. 8. Click Save Certificate. The certificate is installed and becomes available in the list of certificates on the SSL Certificates page. Figure 11-63: SSL Certificates page. Nasuni Filer Administration Guide

324 SSL Certificates Replacing SSL Certificates or SSL Certificate Chains You can replace an existing SSL certificate or SSL certificate chain. This might occur if you need an SSL certificate chain file, or if you are replacing one SSL certificate with another one. To replace an existing SSL certificate: 1. Click Configuration, then select SSL Certificates from the list. The SSL Certificates page appears. Figure 11-64: SSL Certificates page. 2. For the SSL certificate that you want to replace, select Replace Certificate/Chain from the Actions drop-down list next to the name of the certificate in the list. The Add Certificate Files dialog box appears. Figure 11-65: Add Certificate Files dialog box. 3. Click Choose File next to Certificate File, then navigate to the PEM- and DER-encoded X.509 file or PKCS#7 certificate file. 4. Optionally, click Choose File next to Certificate Chain File, then navigate to the SSL certificate chain file. Nasuni Filer Administration Guide

325 SSL Certificates 5. Click Save Certificate. The existing certificate is replaced and appears in the list of certificates on the SSL Certificates page. Nasuni Filer Administration Guide

326 SSL Certificates Setting SSL Certificates Set You can select which of several SSL certificates to set as the GUI certificate for the Nasuni Filer. To set a new SSL certificate: 1. Click Configuration, then select SSL Certificates from the list. The SSL Certificates page appears. Figure 11-66: SSL Certificates page. 2. For the SSL certificate that you want to select, click Set as GUI Certificate. The Enable SSL Certificate for Filer GUI dialog box appears. Figure 11-67: Enable SSL Certificate for Filer GUI dialog box. 3. Enter a Username (case-sensitive) and Password (case-sensitive) that has permission to perform this operation, then click Set GUI Certificate. Your changes are saved. Nasuni Filer Administration Guide

327 SSL Certificates Saving SSL Certificates Delete To download and save an SSL certificate: 1. Click Configuration, then select SSL Certificates from the list. The SSL Certificates page appears. Figure 11-68: SSL Certificates page. 2. From the Actions drop-down list next to the name of the certificate or certificate request that you want to save, select Save certificate as zip. The certificate is downloaded and saved as a zip file, in the way your browser handles downloads. Nasuni Filer Administration Guide

328 SSL Certificates Deleting SSL Certificates or Certificate Requests Delete Tip: You cannot delete the active SSL certificate. To delete an SSL certificate or certificate request: 1. Click Configuration, then select SSL Certificates from the list. The SSL Certificates page appears. Figure 11-69: SSL Certificates page. 2. From the Actions drop-down list next to the name of the certificate or certificate request that you want to delete, select Delete. The certificate or certificate request is deleted. Resetting an SSL Certificate If something ever goes wrong with the SSL certificates, and you are unable to access the Nasuni Filer user interface, use the service menu on the console on your hardware appliance or virtual machine to reset the certificate to the default self-signed certificate. To reset the certificate, follow these steps: 1. On the console, log in to the service menu by pressing Enter and signing in. The default login username is service, and the default password is service. 2. On the console, at the command-line prompt, type resetguicert and press Enter. The message Reset GUI SSL certificate to default appears. 3. To confirm, at the command-line prompt, type yes. The message GUI Certificate Reset appears. 4. Re-try the Nasuni Filer user interface with the self-signed certificate. Nasuni Filer Administration Guide

329 Users and Groups Users and Groups The Nasuni Filer provides role-based access control. You can define specific access permissions for permission groups and users to perform actions within the Nasuni Filer user interface. You can define up to 150 groups, each with permissions that you specify, such as Storage Access. You can then define up to 150 users, and assign them to groups, from which users receive permissions. The defined groups and users are for the local Nasuni Filer only. Also, you can associate Active Directory domain groups with a permission group. Note: When a Nasuni Filer goes under the control of the Nasuni Management Console, any existing users and groups on the Nasuni Filer are replaced by the users and groups of the Nasuni Management Console. When a Nasuni Filer is disconnected from the Nasuni Management Console, the Nasuni Filer retains those users and groups that pertain to the Nasuni Filer. There are two default groups, called Filer Administrators and File Restore. Users in the Filer Administrators group receive full access to all aspects of the Nasuni Filer (super user). Users in the File Restore group receive the ability to restore files and access versions. The Filer Administrators group cannot be deleted. There is one default user, created during installation or during an upgrade. The default user is assigned to the Filer Administrators group. There is always at least one user in the Filer Administrators group. Note: These permissions are only for performing actions within the Nasuni Filer user interface. These permissions are completely independent of permissions for access to data. See for a worksheet for planning configurations. Nasuni Filer Administration Guide

330 Users and Groups Viewing Permission Groups and Users To view permission groups and users, follow these steps: 1. Click Configuration, then select Users/Groups from the drop-down list. The Filer Users and Groups Overview page appears. Figure 11-70: Filer Users and Groups Overview page. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. The information displayed includes the following: Total Users: The total number of users, including Native Users and Domain Users. To view a list of users, click Manage Users. Native Users: The number of native users, namely, users explicitly defined and managed using the Nasuni Filer or Nasuni Management Console. To view a list of users, click Manage Users. To add a user, see Adding Users on page 323. Domain Users: The number of domain users, namely, users automatically created because they are members of an Active Directory domain group associated with a permission group. To view a list of users, click Manage Users. To add a permission group with an associated Active Directory domain group, see Adding Permission Groups on page 318. Users with Storage Access: The number of native users who are members of permission groups that have Storage Access enabled. To view a list of users, click Manage Users. To add a permission group that has Storage Access enabled, see Adding Permission Groups on page 318. Total Groups: The total number of permission groups, including Group Associations, Groups Granting Access, and permission groups that do not have Group Associations or Storage Access. To view a list of permission groups, click Manage Groups. Group Associations: The number of permission groups that have Active Directory domain groups associated with them. To view a list of permission groups, click Manage Groups. Nasuni Filer Administration Guide

331 Users and Groups Groups Granting Access: The number of permission groups that have Storage Access enabled. To view a list of permission groups, click Manage Groups. Groups without Members: The number of permission groups that do not have any members. To view a list of permission groups, click Manage Groups. 2. On the Filer Users and Groups Overview page, clicking Manage Users opens the Filer Users page. Figure 11-71: Filer Users page. A list of users appears. The information displayed for each user includes the following: Username: The name of the user. Type: The type of user: either Native or Domain. Native users are explicitly defined and managed using the Nasuni Filer or Nasuni Management Console. Domain users are automatically created because they are members of an Active Directory domain group associated with a permission group. The address of the user. Might be blank if no address is entered. You can change this by clicking Edit User. Groups: The permission groups that the user belongs to. You can change this by clicking Edit User. Storage Access (For Native Users only): An indication of whether Storage Access is enabled for any of the groups that the user belongs to: Yes (if Storage Access is enabled) or No (if Storage Access is not enabled, or if user is a Domain User). Actions: Available actions, such as Edit User and Delete User. The Add User button is also available. See Adding Users on page 323 for details: Nasuni Filer Administration Guide

332 Users and Groups 3. On the Filer Users and Groups Overview page, clicking Manage Groups opens the Filer Groups page. Figure 11-72: Filer Groups page. A list of permission groups appears. The information displayed for each permission group includes the following: Group: The name of the permission group. You can change this by clicking Edit Group. Users: The number of users who belong to the permission group. Permissions: The permissions defined for this permission group. You can change this by clicking Edit Group. Special: Either Domain Group Association, Storage Access Enabled, or blank. You can change this by clicking Edit Group. Note: Domain groups and the members of those groups always have storage access. Actions: Available actions, such as Edit Group and Delete Group (if permission group has no users). The Add Group button is also available. See Adding Permission Groups on page 318 for details: Adding Permission Groups Add You can add up to 150 permission groups to which you can assign users. For each group, you can specify exactly which actions the users in that group have permission to perform. You can associate Active Directory domain groups with a permission group. Note: Before you associate an Active Directory domain group with a permission group, you must join the Nasuni Filer to the domain. See Joining the Nasuni Filer to an Active Directory domain on page 273. Nasuni Filer Administration Guide

333 Users and Groups To add a permission group, follow these steps: 1. Click Configuration, then select Users/Groups from the drop-down list. The Filer Users and Groups Overview page appears. Figure 11-73: Filer Users and Groups Overview page. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. 2. On the Filer Users and Groups Overview page, click Manage Groups. The Filer Groups page appears. Figure 11-74: Filer Groups page. Nasuni Filer Administration Guide

334 Users and Groups 3. Click Add Group. If there are already 150 groups, you must delete an existing group before you can add a new group. The Add New Group dialog box appears. Figure 11-75: Add New Group dialog box. 4. In the Group Name text box, enter the name for this group. The Group Name can have up to 30 characters, including letters, digits, and symbols. 5. From the Access Type drop-down list, select the type of access from the following: User Interface Access: This Access Type allows you to define permissions and, optionally, any associations to Active Directory domain groups. a. In the Permissions list, select or clear the Nasuni Filer permissions that you want to grant to the new group. Warning: Users with Perform File Restores/Access Versions permission have the ability to access all files on the file server. b. (Optional.) To link an Active Directory domain group to this permission group, and allow members of that Active Directory domain group to use their domain credentials to access volumes on Nasuni Filers, the exact domain name and domain group are necessary. In the Group Association text box, enter any text from the domain NT name or the domain group, and click Search. The Select Group dialog box appears. Click Search. From the list of domain groups that include the search text, select the domain NT name and domain group, then click Add Selected Group. Alternatively, enter the exact domain NT name and domain group in the Group Association text box. Nasuni Filer Administration Guide

335 Users and Groups Note: It is not necessary for a permission group to be linked to an Active Directory domain group. Note: Adding a domain group allows all Active Directory users in that group to access the user interface. You do not need to explicitly add those users. If the group membership changes after the group is linked, the new members can still log in. Note: If you use a Group Association, you cannot select Storage Access. Note: Domain groups and the members of those groups always have storage access. Storage Access: To grant data access to users in the new permission group. Note: Storage Access does not grant any access to the Nasuni Filer user interface. Note: If you select Storage Access, you cannot enter a Group Association. 6. (For User Interface Access only.) In the Permissions list, for each of the permissions, select or clear the check box for the permission. Warning: Users with Perform File Restores/Access Versions permission have the ability to access all files in the file server. Tip: Users with Disconnect Users from Access Points permission have the ability to disconnect CIFS or NFS users individually, which is sometimes necessary when there are locked files. 7. (Optional.) (For User Interface Access only.) To link an Active Directory domain group to this permission group, and allow members of that Active Directory domain group to use their domain credentials to access volumes on Nasuni Filers, the exact domain name and domain group are necessary. In the Group Association text box, enter any text from the domain NT name or the domain group, and click Search. The Select Group dialog box appears. Click Search. From the list of domain groups that include the search text, select the domain NT name and domain group, then click Add Selected Group. Alternatively, enter the exact domain NT name and domain group in the Group Association text box. Note: It is optional, but not necessary, to link groups granting User Interface access to Active Directory domain groups. Note: If you use a Group Association, you cannot select Storage Access. Note: The list of available domain groups are from the domains previously joined to the Nasuni Filer. See Joining the Nasuni Filer to an Active Directory domain on page To accept your selections, click Add Group. The permission group is added with the selected permissions. Nasuni Filer Administration Guide

336 Users and Groups Editing Permission Groups Edit You can edit the features of existing groups. To edit a permission group, follow the steps in Adding Permission Groups on page 318, except click Edit Group instead of Add Group. The dialog box is named Edit Group, and you click Save Group at the end. The group and its permissions are changed. Deleting Permission Groups Delete Note: You cannot delete a permission group that has users. Before deleting a permission group with users, edit each user to remove the permission group from the user. Note: You cannot delete the Filer Administrators group. To delete a permission group, follow these steps: 1. Click Configuration, then select Users/Groups from the drop-down list. The Filer Users and Groups Overview page appears. Figure 11-76: Filer Users and Groups Overview page. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. 2. On the Filer Users and Groups Overview page, click Manage Groups. The Filer Groups page appears. Figure 11-77: Filer Groups page. 3. To delete a group, select the group, then click Delete Group. 4. The About to Delete Group dialog box appears. Click Delete Group. The group is deleted. Nasuni Filer Administration Guide

337 Users and Groups Adding Users You can add up to 150 users. For each user, you can specify which permission groups that user belongs to. If this Nasuni Filer is joined to Active Directory, you can also add domain users. Note: Adding a domain group allows all Active Directory users in that group to access the user interface. You do not need to explicitly add those users. To add a user, follow these steps: 1. Click Configuration, then select Users/Groups from the drop-down list. The Filer Users and Groups Overview page appears. Figure 11-78: Filer Users and Groups Overview page. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. 2. On the Filer Users and Groups Overview page, click Manage Users. The Filer Users page appears. Figure 11-79: Filer Users page. Nasuni Filer Administration Guide

338 Users and Groups 3. Click Add Native User. If there are already 150 users, you must delete an existing user before you can add a new user. The Add Native User dialog box appears. Figure 11-80: Add Native User dialog box. a. In the Username text box, enter the name for this user. The Username can have up to 30 characters, including letters, digits, and the following + - _ (at symbol, period, plus sign, minus sign, underline) b. In the text box, enter the address for this user. c. In the Password text box, enter the password for this user. Enter the same password in the Password confirmation text box. d. In the Groups list, for each of the permission groups, select or clear the check box for granting membership to the permission group. e. To accept your selections, click Add User. The user is added with membership in the selected groups. Nasuni Filer Administration Guide

339 Users and Groups 4. If the Nasuni Filer is joined to Active Directory, to add a domain user, click Add Domain User. If there are already 150 users, you must delete an existing user before you can add a new user. The Add Domain User dialog box appears. Figure 11-81: Add Domain User dialog box. Note: Adding a domain group allows all Active Directory users in that group to access the user interface. You do not need to explicitly add those users. You only need to add Active Directory users individually if you do not want to grant access to the entire group. a. In the Username text box, enter the NT compatible name of a user in an Active Directory domain. The Username can have up to 30 characters, including letters, digits, and the following symbols: b. In the Groups list, for each of the permission groups, select or clear the check box for granting membership to the permission group. c. To accept your selections, click Link User. The user is added with membership in the selected groups. Editing Users You can edit the features of existing users. To edit a user, follow the steps in Adding Users on page 323, except click Edit User instead of Add User. The dialog box is named Edit User, and you click Save User at the end. The user and his or her groups are changed. Nasuni Filer Administration Guide

340 Users and Groups Deleting Users Note: You cannot delete the last user in the Filer Administrators group. To delete a user, follow these steps: 1. Click Configuration, then select Users/Groups from the drop-down list. The Filer Users and Groups Overview page appears. Figure 11-82: Filer Users and Groups Overview page. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. 2. On the Filer Users and Groups Overview page, click Manage Users. The Filer Users page appears. Figure 11-83: Filer Users page. 3. To delete a user, select the user, then click Delete User. 4. The About to Delete User dialog box appears. Click Delete User. The user is deleted. Nasuni Filer Administration Guide

341 SNMP Monitoring SNMP Monitoring Enable You can configure SNMP monitoring of Nasuni Filers. The Nasuni Filer supports monitoring via the Simple Network Management Protocol (SNMP) v1, v2c, and v3. The Nasuni Filer exposes the standard SNMPv1 MIB (management information base), as well as the NASUNI-FILER-MIB, SNMPv2-MIB, HOST-RESOURCES-MIB, UCD-SNMP-MIB, UCD-DISKIO- MIB, and IF-MIB. The SNMP server is available on port 161. Each of the displayed MIBs is a link. If you click a link, a page with that MIB information appears. Data available in SNMP updates includes the following: Network information, such as: Inbound and outbound traffic by type and by port Volume information, such as: Size Time of last snapshot Local cache information, such as: Total space Used space Free space Unprotected data Cache hit/miss rate CPU performance information, such as: Percent utilization Load averages Memory usage information, such as: Memory utilization Swap utilization Disk performance information, such as: Number of disk reads and writes per disk Bytes read and written per disk Client information, such as: Number of connected CIFS, iscsi, and Mobile Access clients Snapshot and sync information, such as: Number of merge conflicts Snapshot success (version) count per volume Times for snapshots (start, end, delta) per volume Traps information for anything that would generate an alert Nasuni Filer Administration Guide

342 SNMP Monitoring To configure SNMP monitoring: 1. Click Configuration, then select SNMP Monitoring from the list. The SNMP Monitoring Settings page appears. Figure 11-84: SNMP Monitoring Settings page. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. 2. To enable SNMP v1 and v2c monitoring, select Enable v1,v2c Support. If you enable SNMP v1 and v2c monitoring, in the Community Name text box, enter the SNMP community name for the Nasuni Filer. The default community name is public. Changing the community name from the default improves security. 3. To enable SNMP v3 monitoring, select Enable v3 Support. If you enable SNMP v3 monitoring, enter a Username and Password for SNMP v3 authorization. 4. If you enable SNMP monitoring, in the System Location text box, enter the physical location of the Nasuni Filer. Nasuni Filer Administration Guide

343 SNMP Monitoring 5. If you enable SNMP monitoring, in the System Contact text box, enter the contact information of the person responsible for SNMP monitoring for the Nasuni Filer. 6. If you enable SNMP monitoring, in the Trap Addresses text box, enter a list of IP addresses or hostnames listening for SNMP traps, separated by commas. If you do not want to listen for SNMP traps, leave this blank. If you enter any trap addresses, you can send a test trap by clicking Send Test Trap. 7. Click Save SNMP Settings. The SNMP monitoring settings are saved for this Nasuni Filer. Nasuni Filer Administration Guide

344 Web Access Branding Web Access Branding Edit You can use the Web Access feature to access CIFS share data or NFS export data stored in the Nasuni Filer using a Web browser. You can configure the Web Access display to include elements of your organization s branding, including logo and colors. For information on Web Access, see Web Access on page 150. To enable Web Access, see at step s on page 108. To configure Web Access branding: 1. Click Configuration, then select Web Access Branding from the list. The Web Access Branding page appears. Figure 11-85: Web Access Branding page. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. 2. To include a logo on the Web Access display, click the Logo area and navigate to a logo graphics file. The maximum file size is 500 KB. 3. To change the primary color, which is used for items including Shares, Settings, and Logout on the Web Access display, click the Primary Color area and select a primary color. 4. To change the secondary color, which is used for items including Add Folder, Upload File, and Sort on the Web Access display, click the Secondary Color area and select a secondary color. 5. To revert to the default logo, primary color, and secondary color, click Set Defaults. Nasuni Filer Administration Guide

345 Web Access Branding 6. Click Save. Your settings are saved. Figure 11-86: Web Access Branding page with new logo and colors. The Web Access page appears with the selected logo and colors. Figure 11-87: Web Access page with branding. Nasuni Filer Administration Guide

346 Automatic Software Updates Automatic Software Updates Edit You can configure the Nasuni Filer to automatically download and install updates. You can select which day or days and the time on which to check for auto-updates. By default, this feature is enabled. Tip: To prevent automatic software updates from occurring at inconvenient times, specify the days and times for automatic software updates to occur. To prevent automatic software updates entirely, deselect all days and times. Tip: If this Nasuni Filer is joined to a Nasuni Management Console, update the Nasuni Management Console software before updating the Nasuni Filer software. You can also manually update the Nasuni Filer as detailed in Software Updates on page 340. See for a worksheet for planning configurations. To configure automatic updates: 1. Click Configuration, then select Automatic Updates from the list. The Automatic Updates Configuration page appears. Figure 11-88: Automatic Updates Configuration page. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. 2. Select the days on which you want to allow automatic updates. To select or deselect all days, click Select/Deselect all. 3. From the Time drop-down list, select the time that you want an automatic update to start. 4. Click Save Update Configuration. Your settings are saved. Nasuni Filer Administration Guide

347 Cache Settings Cache Settings Edit The cache performs two different, but related, tasks. First, the cache retains the data that users are most likely to need. Second, the cache also temporarily contains new, incoming data that the Nasuni Filer has not yet sent to permanent storage in the cloud. By default, the Nasuni Filer automatically manages the amount of local cache space reserved for new, incoming data, using an advanced algorithm to optimize cache usage. However, the administrator can manually set the area of the cache reserved for new, incoming data. The area for new, incoming data can be from 5 percent to 90 percent of the cache. The remainder of the cache retains the data locally that users are most likely to need. The larger the area for new, incoming data is, the less data the Nasuni Filer can retain locally, and the more slowly users can access data. It might also be necessary for the Nasuni Filer to frequently retrieve data from the cloud, which could delay access. However, the larger the area for new, incoming data is, the larger the batches of new, incoming data that the Nasuni Filer can send to permanent storage in the cloud, protecting that data from loss. You can estimate the area necessary by examining data usage patterns. For example, if you have a 1 TB cache and must keep 200 GB of data locally, then you can set the area for new, incoming data as high as 80 percent. On the other hand, if you rarely have more than 300 GB in a snapshot, then you can set the area for new, incoming data as low as 30 percent, leaving 70 percent of the cache for local data. By setting the amount of local cache space reserved for new, incoming data, you disable the automatic management of this value. Important: The Data Migration Service uses the cache. To ensure that the Data Migration Service has enough space, set Cache Settings to 30 percent or greater. See Data Migration on page 200. To specify the amount of local cache space to reserve for new, incoming data, follow these steps: 1. Click Configuration, then select Cache Settings from the drop-down list. The Cache Settings page appears. Figure 11-89: Cache Settings page. Nasuni Filer Administration Guide

348 Cache Settings The size of the current cache is displayed. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. 2. From the Select Percentage drop-down list, select either Automatic, or one of the available percentages for new, incoming data. 3. To accept your selections, click Save Cache Settings. The amount of local cache space to reserve for new, incoming data takes on the specified value. Nasuni Filer Administration Guide

349 Global Locking Global Locking Edit This page enables you to configure certain aspects of global file locking. For details about global file locking, see Global File Locking on page 190. Tip: Use caution when making changes to global file locking, and discuss the possible implications of changes beforehand with Nasuni Technical Support. If global file locking is enabled, and Internet connectivity issues prevent a Nasuni Filer from releasing locks on certain files, local users connected to the affected Nasuni Filer might not be able to read or write those files. In order to restore access to these files, you can degrade the type of lock to a read lock. Enabling this feature causes all locks that are not read locks to be denied. This effectively makes any directories with global locks enabled into read-only directories. Only enable this feature if file access is affected for an extended period of time. To degrade global file locking to read locks, follow these steps: 1. Click Configuration, then select Global Locking from the drop-down list. The Global Locking page appears. Figure 11-90: Global Locking page. 2. To degrade global file locking to read locks, select enabled from the Degrade to read locks drop-down list. 3. To accept your selections, click Save Global Locking Setting. The global file locking configuration is changed. Nasuni Filer Administration Guide

350 Changing User Password Changing User Password Edit You can change the currently logged-in user account password to a new password. To change the user account password: 1. Click Configuration, then select Change Password from the list. Alternatively, click the user name at the top of the page, then select Change Password from the list. The Change User Password page appears. Figure 11-91: Change User Password page. 2. Enter your current password (case-sensitive) in the Old password text box. 3. Enter the new password (case-sensitive) you want associated with your user account in the New password text box. 4. Enter the new password (case-sensitive) again in the Confirm new password text box. 5. Click Save New Password. You are taken to the Home page where the message Password successfully changed is displayed. Nasuni Filer Administration Guide

351 Chapter 12: Status Page Status The Status page provides information about the following: Subscription status. Updating the Nasuni Filer software to the latest release. Status of jobs bringing data into the cache, such as Bring into Cache and Auto Cache. High-Availability status (only for high-availability Nasuni Filer hardware appliances). Network status. Platform status. CIFS status. iscsi status. NFS status. FTP status. File heuristics. Note: The Status page, and all other pages of the Nasuni Filer user interface, might look different to different users. Also, different menus and actions might be available for different users. This is because different users are assigned different permissions, based on their roles in the role-based access control system. See Users and Groups on page 315 for details. Note: If this Nasuni Filer is under the control of the Nasuni Management Console, menus and menu choices might look different, because you use the Nasuni Management Console to perform these tasks. Nasuni Filer Administration Guide

352 Subscription Status Subscription Status View You can view your Nasuni subscription status and license information. Links to the Nasuni Terms of Service and License Agreement, Privacy Policy, and Service Level Agreement are available on this page. To view your subscription status: 1. Click Status, then select Subscription Status from the list. The Subscription Status page appears. Figure 12-1: Subscription Status page. If this is a trial subscription, the time left in the trial appears. Figure 12-2: Time left in trial. The following subscription information is displayed: Account Name: Name of the account. Subscription Mode: Standard, Trial, Manual, or Monthly. Subscription Expires: The date on which the subscription expires. Expires in: Time until the subscription expires. Serial Number: The Serial Number for this subscription. Usable Capacity: Total capacity licensed. Note: If the licensed capacity is exceeded, you can still store more data temporarily. If your total stored data nears or exceeds your licensed capacity, you receive warnings to increase your licensed capacity. Global Capacity Used: The amount of the usable capacity actually in use. Max Volumes / Filer: Maximum number of volumes for each Nasuni Filer. Max Filers: Maximum number of Nasuni Filers. Max Remote Access Group Size: Maximum number of Nasuni Filers licensed to simultaneously access a single volume. If this limit is exceeded, you receive a message and you should contact Nasuni Technical Support. Max Remote Access Volumes: Maximum number of volumes that can be enabled for remote access. Nasuni Filer Administration Guide

353 Subscription Status Refreshing Subscription License Refresh Click Refresh subscription license to reload the page with updated information, such as when you purchase a Nasuni Filer or when the license changes. The message Account refresh requested! appears. Click the x to close this message box. Licenses automatically refresh every 24 hours. Nasuni Filer Administration Guide

354 Software Updates Software Updates Updates When a newer version of the Nasuni Filer software is available for installation, you can update the software from the Status page. When you update your software, your Nasuni Filer is updated to the newer version. If updates are not available, a page appears telling you there are no updates at this time. Caution: Updating the software disconnects all users currently using the Nasuni Filer. The Nasuni Filer can take several minutes to reboot. The time to reboot can be longer if one-time upgrade operations are necessary. Note: Nasuni does not recommend applying software updates during your normal business hours, because this can disrupt access. Apply software updates during off-hours. Tip: Check the release notes of all releases between your current release and the most recent release. See Viewing the Nasuni Filer Release Notes on page 25 for details. Tip: If this Nasuni Filer is joined to a Nasuni Management Console, update the Nasuni Management Console software before updating the Nasuni Filer software. To update to the latest release: 1. Click Status, then select Updates from the list. If an update is available, the Updates Are Available page appears. Alternatively, if the Nasuni Filer is currently using the latest version of the software, the No updates available page appears instead. Figure 12-3: Updates Are Available page. Note: If this Nasuni Filer is under Nasuni Management Console control, this page is not available on the Nasuni Filer. Instead, use the Nasuni Management Console to view information or perform actions. Note: File system checks (using fsck) are necessary at least every six months, and are performed when you reboot your Nasuni Filer. However, a file system check might take hours to complete (depending on the size of the cache) and might interfere with normal operations. To determine if a file system check is actually necessary, the Nasuni Filer periodically performs a background test. If this background test determines that a file system check is not necessary, the next file system check is postponed for another six months. However, if the background test determines that a file system check is necessary, you receive an alert suggesting that you perform a reboot and a file system Nasuni Filer Administration Guide

355 Software Updates check. If you do not manually initiate a reboot with a file system check when it is necessary, the file system check is performed after the next reboot, such as after a software update. 2. To review the release notes, click the hyperlink here in the second sentence. Note: Some software updates can take longer to apply than others. Refer to the release notes before applying the update. 3. Click Update. The Update Confirmation page appears. Figure 12-4: Update Confirmation page. 4. To confirm that you want to update the software, enter a Username (case-sensitive) and Password (case-sensitive) that has permission to perform this operation. 5. To update to a newer version, click Apply Update. The Nasuni Filer downloads software updates and reboots the Nasuni Filer. Tip: To avoid any performance issues when updates occur, clear your browser s cache. 6. After the upgrade and the reboot are complete, you are automatically redirected to the Nasuni Filer's home page. Optionally, you can click the hyperlink here to proceed to the Login page after rebooting is complete. 7. Re-log in to the Nasuni Filer with your username (case-sensitive) and password (case-sensitive) after the reboot is completed. Nasuni Filer Administration Guide

356 Cache Jobs Cache Jobs You can view the status of jobs that bring data or metadata into the cache, such as Bring into Cache (see Bringing Data into Cache of the Nasuni Filer on page 76) and Auto Cache (see Enabling Auto Cache for Folders on page 79). You can also cancel jobs that are unnecessary. Viewing or cancelling cache jobs To view or cancel cache jobs, follow these steps: 1. Click Status, then select Cache Jobs from the list. The Cache Job Status page displays a list of cache jobs. Figure 12-5: Cache Job Status page. The following information appears for each cache job: Volume: The name of the volume on which this cache job is occurring. Path in Volume: The path in the volume to the data moving to the cache. Type: The type of cache job, such as Manual (for Bring into Cache) or Auto (for Auto Cache). Data/Metadata: An indication whether data or metadata is moving to the cache. Number of Items: The number of items to transfer. Actions: Actions available for this cache job. 2. To cancel a running cache job in the list, click Cancel. A dialog box appears. Confirm that you want to cancel the job. The job is canceled. Nasuni Filer Administration Guide

357 High-Availability Status High-Availability Status If you are running a high-availability Nasuni Filer hardware appliance, such as the NF-400H, you can view the current status of the Nasuni Filer hardware appliance. Note: The High-Availability Status page is only available for high-availability Nasuni Filer hardware appliances and not available for the Nasuni Filer virtual machine or other Nasuni Filer hardware appliances. You can also manually trigger a failover from the Active node to the Standby node. Important: In ordinary operation, it is unnecessary for you to manually trigger a failover from the Active node to the Standby node, except for testing purposes. If the Active node fails, failover to the Standby node is automatic. Viewing high-availability hardware appliance status To view the current status of the high-availability hardware appliance: 1. Click Status, then select High-Availability Status from the list. The High-Availability Status page appears. Figure 12-6: High-Availability Status page. The following information appears in the Total System Status area for each node: Online status: Indicates whether the node is Online or Offline. Active status: Indicates whether the node is the Active node or the Standby node. Actions: To manually trigger a failover from the Active node to the Standby node, click Trigger Failover. See Triggering failover manually on page 345 for details. Nasuni Filer Administration Guide

358 High-Availability Status The following information appears in the Standby Node Status area: Hardware Model: The model of the high-availability hardware appliance. CPU Count: The number of CPUs in the standby node. CPU Cores: The number of CPU cores per CPU in the standby node. CPU Frequency: The CPU frequency in GHz. CPU Model: The specific model of CPU. System RAM: The total amount of system RAM in GiB. Serial Number: The serial number of the standby node. Power Supplies: The number of power supplies in the standby node. Power Supply Status: The current status of the standby node power supplies. If the status is Alert, you should investigate the situation. Inlet Temperature: The standby node inlet temperature in Celsius and Fahrenheit. Exhaust Temperature: The standby node exhaust temperature in Celsius and Fahrenheit. The following information appears in the Node RAID Disks area: Location: Location of the disk in the hardware appliance. Size: Size of the disk. Hardware ID: The hardware identification number of the disk. Status: Status of the disk. If the status is Alert, you should investigate the situation. Nasuni Filer Administration Guide

359 High-Availability Status Triggering failover manually You can manually trigger a failover from the Active node to the Standby node. Important: In ordinary operation, it is unnecessary for you to manually trigger a failover from the Active node to the Standby node, except for testing purposes. If the Active node fails, failover to the Standby node is automatic. To manually trigger a failover on the high-availability hardware appliance, follow these steps: 1. On the High-Availability Status page, click Trigger Failover. The Trigger HA Node Failover dialog box appears. Figure 12-7: Trigger HA Node Failover dialog box. 2. Enter a Username and Password that has permission to perform this operation. Click Confirm. The Active node reboots and its online status changes to Offline. Within a minute or so, the former Standby node becomes the Active node. During this time, the Standby Node Status information and the Trigger Failover button are not displayed. Note: Until the former Standby node becomes the Active node, data is not accessible on this Nasuni Filer. When the former Active node comes online again, its active status changes to Standby. The Standby Node Status information and the Trigger Failover button are displayed. Nasuni Filer Administration Guide

360 Network Status Network Status You can view current network information for the Nasuni Filer. To change the network configuration, see Network Configuration on page 252. Network Status Status To view the network status: 1. Click Status, then select Network Status from the list. The Network Status page appears. Figure 12-8: Network Status page. Note: Your display might look different from this. The number of entries depends upon the number of configured networks. Nasuni Filer Administration Guide

361 Network Status The following information is displayed: Configured Networks: The number of configured networks. Clicking this link opens the page for Network Configuration on page 252. Traffic Groups: The traffic groups configured for this network. Three traffic groups are available by default: General: All traffic is in the General traffic group, unless explicitly assigned to the Management or External traffic groups. The General traffic group is a dynamic traffic group. The General traffic group is required in any configuration. At least one device must be in the General traffic group. Management: The Management traffic group is for customer support access, SSH access, and user interface access to the Nasuni Filer. Traffic in the Management traffic group is pulled from the General traffic group. External: The External traffic group is for traffic such as cloud traffic, Nasuni API traffic, and external traffic originating outside the LAN. Traffic in the External traffic group is pulled from the General traffic group. If the External traffic group is configured, then all Web, service, and cloud traffic goes through the External traffic group. If you have an External traffic group, you must enter a gateway that is on the same subnet as your External group devices. You can add other traffic groups as needed. To configure traffic groups, see Network Configuration on page 252. Network Devices: The number of network devices. Default Gateway: Default gateway of the network. Hostname: The hostname of the Nasuni Filer. Clicking this link opens the page for Network Configuration on page 252. Network Proxy: The proxy server, if any. Clicking this link opens the page for HTTPS Proxy Configuration on page 251. DNS Information: Including the Search Domains hostnames and the Name Servers IP addresses. 2. Optionally, you can change the network type and other network configuration parameters by clicking the number of Configured Networks. The Network Configuration page appears. See Network Configuration on page 252 for details on network configuration. 3. Optionally, you can change the hostname and other network configuration parameters by clicking the Hostname. The Network Configuration page appears. See Network Configuration on page 252 for details on network configuration. 4. Optionally, you can change the network proxy and other proxy settings by clicking the entry for Network Proxy. The HTTPS Proxy Settings page appears. See HTTPS Proxy Configuration on page 251 for details on proxy configuration. Nasuni Filer Administration Guide

362 Network Status Traffic Groups View The Nasuni Filer supports multiple network interface cards (NICs), in order to segregate different types of traffic and to bind specific Ethernet ports to a particular traffic group. Three traffic groups are available by default: General: All traffic is in the General traffic group, unless explicitly assigned to the Management or External traffic groups. The General traffic group is a dynamic traffic group. The General traffic group is required in any configuration. At least one device must be in the General traffic group. Management: The Management traffic group is for local customer support access using SSH, and for user interface access to the Nasuni Filer. When the Management traffic group is defined, local customer support access using SSH and user interface access to the Nasuni Filer are not available from the General traffic group. External: The External traffic group is for cloud traffic, Remote Support Service (if enabled), and Nasuni API traffic. Traffic in the External traffic group is pulled from the General traffic group. If you have an External traffic group, you must enter a gateway that is on the same subnet as your External group devices. To configure traffic groups, see Network Configuration on page 252. For more details on traffic groups, see About Traffic Groups on page 252. To view information on the Nasuni Filer s traffic groups: 1. Click Status, then select Network Status from the list. The Network Status page appears, including the list of Traffic Groups. Figure 12-9: Network Status page, including list of Traffic Groups. Note: Your display might look different from this. The number of entries depends upon the number of physical ports. For each traffic group, the following information is displayed: Name: Name of the traffic group. Device(s): The devices included in the traffic group. Public IP Address (for Azure-based and EC2-based Nasuni Filers): The public IP address of the device. Type: The network type: Static or DHCP. IP Address (for Azure-based and EC2-based Nasuni Filers, the Internal IP Address): The IP address of the device. For Azure-based and EC2-based Nasuni Filers, if you're running other machines on the EC2 or Azure platforms, you can communicate using the Internal IP Address instead of the publicly accessible address. Nasuni Filer Administration Guide

363 Network Status Netmask: Subnet mask of the IP address. MTU: The MTU (maximum transmission unit) value indicates the maximum size of each block of information that can be sent without the data becoming fragmented. Physical Ports To view information on the Nasuni Filer s physical ports: 1. Click Status, then select Network Status from the list. The Network Status page appears, including the list of Physical Ports. Figure 12-10: Network Status page, including list of physical ports. Note: Your display might look different from this. The number of entries depends upon the number of physical ports. The following information is displayed: Name: Name of the port. MAC: Media Access Control address (MAC address) of the port. Carrier: Indicates whether the network interface card (NIC) senses a carrier signal on the Ethernet cable: yes or no. Speed: Speed of the port in Mbps. Duplex: Type of duplex. Nasuni Filer Administration Guide

364 Network Status Network Activity Charts Charts You can view charts of the network activity of the Nasuni Filer. The scale is in Kbits/second or Mbits/ second, depending on throughput. Charts of Cloud Traffic and Local Traffic by Traffic Type From the left-hand drop-down list, select Display Graphs by Traffic Type. This displays a chart of Cloud Traffic and a chart of Local Traffic. Figure 12-11: Network Activity charts. You can select the time period of these charts by clicking the drop-down list on the right and selecting one of the following time periods: Previous Hour Previous Day On the Cloud Traffic chart (upper chart), you can select which network activity to include or exclude by clicking Cloud Transmit (for data transmitted to the cloud by the Nasuni Filer), Cloud Receive (for data received from the cloud by the Nasuni Filer), Mobile Transmit (for data transmitted to mobile devices by the Nasuni Filer), or Mobile Receive (for data received from mobile devices by the Nasuni Filer) under the Cloud Traffic chart. On the Local Traffic chart, you can select which network activity to include or exclude by clicking UI Transmit (for data transmitted to the user interface by the Nasuni Filer), UI Receive (for data received from the user interface by the Nasuni Filer), Client Transmit (for data transmitted to the client by the Nasuni Filer), Client Receive (for data received from the client by the Nasuni Filer), Migration Transmit (for data transmitted to a data migration by the Nasuni Filer), or Migration Receive (for data received from a data migration by the Nasuni Filer) under the Local Traffic chart. Nasuni Filer Administration Guide

365 Network Status If you hover the mouse over any part of either chart, a label appears displaying details about the amount of network activity at that date and time. Figure 12-12: Details of network activity and time on Network Activity charts. To zoom in on a specific range of displayed data, click the chart at the high end of the range you want, then drag to the low end of the range you want, then release. The chart rescales to zoom in on the selected range. To reset the zoom to the default display, click Reset zoom. Charts of Traffic by Device Layout From the left-hand drop-down list, select Display Graphs by Device Layout. This displays a chart of traffic received and transmitted by the Nasuni Filer as a whole. Figure 12-13: Network Activity chart. You can select the time period of this chart by clicking the drop-down list on the right and selecting one of the following time periods: Previous Hour. Previous Day. You can select which network activity to include or exclude by clicking Transmit (for data transmitted by the Nasuni Filer) or Receive (for data received by the Nasuni Filer) under the chart. If you hover the mouse over any part of either chart, a label appears displaying details about the amount of network activity at that date and time. Nasuni Filer Administration Guide

366 Network Status To zoom in on a specific range of displayed data, click the chart at the high end of the range you want, then drag to the low end of the range you want, then release. The chart rescales to zoom in on the selected range. To reset the zoom to the default display, click Reset zoom. Nasuni Filer Administration Guide

367 Platform Status Platform Status Status You can view the current status of the Nasuni Filer platform, including both virtual machines and hardware appliances. Viewing platform status To view the current platform status: 1. Click Status, then select Platform Status from the list. The Platform Status page appears. Figure 12-14: Platform Status page. Note: Your display might look different from this. The number of entries depends upon the number of configured arrays and disks. The following information appears: Hardware Model (hardware appliances only): The model of the hardware appliance. Platform: The type of platform. For hardware appliances, this includes the model of hardware appliance. For virtual machines, this includes the type of virtual platform. CPUs: The number and speed (in GHz) of CPUs, as well as the number of CPU cores per CPU. CPU Model: The specific model of CPU. System RAM: The total amount of system RAM in GiB. System Node Number (high-availability hardware appliances only): The number of the Active node: 1 or 2. Clicking High-Availability Status opens the High-Availability Status page. Nasuni Filer Administration Guide

368 Platform Status BIOS Firmware Version (hardware appliances only): The version number of the BIOS firmware. Tip: You can update the firmware of Nasuni Filer hardware appliances using commands from the Service menu of the console for the Nasuni Filer. BMC Firmware Version (hardware appliances only): The version number of the hardware appliance s BMC (baseboard management controller) firmware. Tip: You can update the firmware of Nasuni Filer hardware appliances using commands from the Service menu of the console for the Nasuni Filer. Serial Number (hardware appliances only): The serial number of the hardware appliance. Power Supplies (hardware appliances only): The number of power supplies in the hardware appliance. Power Supply Status (hardware appliances only): The current status of the hardware appliance power supplies. If the status is Alert, you should investigate the situation. UPS Status (hardware appliances only): The current status of the hardware appliance s uninterruptible power supply (UPS). If the status is Alert, you should investigate the situation. UPS Battery Status (hardware appliances only): The current status of the hardware appliance s uninterruptible power supply s battery. If the status is Alert, you should investigate the situation. Inlet Temperature (hardware appliances only): The standby node inlet temperature in Celsius and Fahrenheit. Exhaust Temperature (hardware appliances only): The standby node exhaust temperature in Celsius and Fahrenheit. RAID Firmware Version (hardware appliances only): The version number of the hardware appliance s RAID firmware. Tip: You can update the firmware of Nasuni Filer hardware appliances using commands from the Service menu of the console for the Nasuni Filer. RAID Battery (hardware appliances only): Status of the battery for the RAID array. If the status is Alert, you should investigate the situation. Full Disk Encryption (hardware appliances only): Status of Full Disk Encryption (FDE): Not Available, Enabled, or Disabled. See Full Disk Encryption (FDE) (hardware appliances only) on page For hardware appliances, click Identify System and the host system identification light blinks for 120 seconds. This helps personnel to physically locate the Nasuni Filer hardware appliance in the racks. 3. For hardware appliances, to update the hardware appliance status information on this page, click Refresh information. The message Requesting sensor data from system. This can take a few moments appears. Click the x to close the message. Note: Hardware appliance status is automatically updated every 10 minutes. Nasuni Filer Administration Guide

369 Platform Status RAID Arrays (hardware appliances only) For hardware appliances, on the Platform Status page, information about RAID Arrays appears. Figure 12-15: RAID Arrays information. Note: Your display might look different from this. The number of entries depends upon the number of configured arrays and disks. The following RAID array information is displayed: For each array: Total Size: Total size of the RAID array. RAID Level/Type: Level of the RAID array, or type of array, such as SSD. Status: Status of the RAID array. If the status is Alert, you should investigate the situation. RAID Disks (hardware appliances only) For hardware appliances, on the Platform Status page, information about RAID Disks appears. Figure 12-16: RAID Disks information. Note: Your display might look different from this. The number of entries depends upon the number of configured arrays and disks. The following RAID disk information is displayed: For each disk: Nasuni Filer Administration Guide

370 Platform Status Location: Location of the disk in the hardware appliance. Size: Size of the disk. Hardware ID: The hardware identification number of the disk. FDE: Status of Full Disk Encryption (FDE) for the disk. A locked lock icon indicates that FDE is enabled: the disk is encrypted. An unlocked lock icon indicates that FDE is available, but not enabled: the disk is not encrypted. See Full Disk Encryption (FDE) (hardware appliances only) on page 357. Status: Status of the disk. If the status is Alert, you should investigate the situation. Actions: Available actions for the disk. Before physically removing a disk from the RAID array, click Remove. The disk is logically removed from the RAID array. You can then physically remove the disk from the RAID array. Nasuni Filer Administration Guide

371 Platform Status Full Disk Encryption (FDE) (hardware appliances only) The goal of Full-Disk Encryption is to provide encryption for data at rest in the Nasuni Filer. While good physical security can protect access to data in the Nasuni Filer in a data center, data can also leave the data center through drive replacements, due to theft or failure. Encryption of data at rest makes sure that no data can leave the Nasuni Filer by someone removing a drive and the drive remaining useable. Nasuni includes self-encrypting drives (SEDs) in Nasuni Filer hardware appliances, NF-400 and above. SEDs allow for hardware-based encryption of data at rest with little or no performance impact over non-seds. The encryption must be turned on ; otherwise, SEDs behave just like non-seds. Nasuni does not enable the Full Disk Encryption feature for customers. Customers enable the Full Disk Encryption feature themselves when they configure the feature. Tip: Full Disk Encryption must be enabled in the customer license before encrypting SEDs. Full Disk Encryption is enabled in the customer license by default. On the Platform Status page, if Full Disk Encryption has been enabled in the license, an indicator shows that the Nasuni Filer is in one of these states: An unlocked lock icon indicates that FDE is available, but not enabled: the disk is not encrypted. A locked lock icon indicates that FDE is enabled: the disk is encrypted. Customers must provide a password when encrypting the Nasuni Filer and are responsible for keeping that password for possible, but unlikely, future use. Nasuni does not provide passwords or escrow them for customers for this feature. The password requirements are: 8 to 32 characters. Must contain at least one uppercase letter. Case-sensitive. Must contain at least one lowercase letter. Case-sensitive. Must contain at least one number. Must contain at least one non-alphanumeric character (such as < +). The space character is not permitted. An SED and a non-sed are interchangeable when the SED encryption is not enabled. However, a secured SED cannot be used in place of a non-sed. Nasuni Filer Administration Guide

372 Platform Status Enabling Full Disk Encryption To enable Full Disk Encryption, follow these steps: 1. Click Enable Full Disk Encryption. The Enable Full Disk Encryption dialog box appears. Figure 12-17: Enable Full Disk Encryption dialog box. 2. Enter the Password with which to encrypt the SEDs, and verify the password. Warning: You must record the password securely. Nasuni cannot escrow or recover the password. 3. Click Save. Full Disk Encryption is enabled for the SEDs. Nasuni Filer Administration Guide

373 Platform Status Changing the Full Disk Encryption Password To change the Full Disk Encryption password, follow these steps: 1. Click Change FDE Password. The Change Full Disk Encryption Password dialog box appears. 2. Enter the Current Password. Figure 12-18: Change Full Disk Encryption Password dialog box. 3. Enter the New Password with which to encrypt the SEDs, and verify the password. Warning: You must record the password securely. Nasuni cannot escrow or recover the password. 4. Click Save. The password for Full Disk Encryption changes. Nasuni Filer Administration Guide

374 CIFS Status CIFS Status CIFS Shares You can view the status of CIFS shares, as well as the status of clients connected to the Nasuni Filer through CIFS file sharing. To view CIFS status: 1. Click Status, then select CIFS Status from the list. The CIFS Shares page appears. Figure 12-19: CIFS Shares page. The following information is displayed (all columns are sortable): Protocol version: The supported versions of the CIFS or SMB protocol. See Configuring CIFS settings on page 283 for details on the protocol level. CIFS Shares: A table displays, for each CIFS share: Volume: The volume of the CIFS share. Clicking this link opens either the CIFS Shares page for this volume (see Viewing a CIFS Share on page 100), if this Nasuni Filer is not under the control of the Nasuni Management Console, or the Home page (see Home Page on page 32), if this Nasuni Filer is under the control of the Nasuni Management Console. Path in Volume: The path in the volume to the CIFS share. Share Name: The name of the CIFS share. Clicking this link opens either the Add CIFS Share / Edit Settings page for this volume (see Editing a CIFS Share on page 113), if this Nasuni Filer is not under the control of the Nasuni Management Console, or the Home page (see Home Page on page 32), if this Nasuni Filer is under the control of the Nasuni Management Console. Nasuni Filer Administration Guide

375 CIFS Status CIFS Client Status: A table displays, for each client connected to the Nasuni Filer through CIFS file sharing: Share: The name of the CIFS share. User: The name of the connected user. Client: The hostname or IP address of the client. Client Name: The name of the client. Disconnect button: Click Disconnect to disconnect this client from the share. See Disconnecting a Single CIFS Client on page 364. Open Files & Locks: A table displays, for each open file or lock: Share: The name of the CIFS share. Path: The path in the share to each open file or file lock. Type: The type of open file or lock, such as RDWR, RDONLY, or WRONLY. User: The name of the connected user. Client: The hostname or IP address of the client. Client Name: The name of the client. Disconnect button: Click Disconnect to disconnect this client from the share. See Disconnecting a Single CIFS Client on page 364. Nasuni Filer Administration Guide

376 CIFS Status Resetting the CIFS Authentication Cache Reset authentication cache You can reset the CIFS authentication cache to clear all CIFS shares for Nasuni Filer users. You might reset the CIFS authentication cache if instructed by Nasuni Support, or if users are not appearing in a group they are assigned to via Active Directory. To reset the CIFS authentication cache: 1. Click Status, then select CIFS Status from the list. The CIFS Shares page appears. Figure 12-20: CIFS Shares page. 2. Click Reset CIFS Auth Cache. The Reset CIFS Auth Cache dialog box appears. Figure 12-21: Reset CIFS Auth Cache dialog box. 3. Click Reset Auth Cache. This flushes all the cached CIFS authentication data. Nasuni Filer Administration Guide

377 CIFS Status Resetting All CIFS Clients Reset clients You can reset all CIFS clients connected to the Nasuni Filer. You might reset all CIFS clients if instructed by Nasuni Support, or to remove clients. Note: Some CIFS clients automatically re-connect to CIFS shares and can then re-appear in the listing even after the connection is reset. To reset all CIFS clients: 1. Click Status, then select CIFS Status from the list. The CIFS Shares page appears. Figure 12-22: CIFS Shares page. 2. Click Reset All Clients. The Reset All Clients dialog box appears. Figure 12-23: Reset All Clients dialog box. 3. Click Reset Clients. The message All client connections were reset appears. Click x to close the message box. Note: Some CIFS clients automatically re-connect to CIFS shares and can then re-appear in the listing even after the connection is reset. Nasuni Filer Administration Guide

378 CIFS Status Disconnecting a Single CIFS Client Disconnect client You can disconnect a single CIFS client connected to the Nasuni Filer. Note: Some CIFS clients automatically re-connect to CIFS shares and can then re-appear in the listing even after disconnecting them. To disconnect a single CIFS client: 1. Click Status, then select CIFS Status from the list. The CIFS Shares page appears. Figure 12-24: CIFS Shares page. 2. Select a client from the list of clients, then click Disconnect. The Disconnect Client dialog box appears. 3. Click Disconnect Client. The client is disconnected. The message Client connection was reset appears. Click x to close the message box. Nasuni Filer Administration Guide

379 iscsi Status iscsi Status Status You can view the status of iscsi targets and iscsi initiators. To view the iscsi status: 1. Click Status, then select iscsi Status from the list. The iscsi Status page appears. Figure 12-25: iscsi Status page. The following information is displayed: iscsi Targets: A table displays, for each iscsi target: Volume: The name of the iscsi volume. Clicking this link opens either the iscsi Settings page for this volume (see Changing iscsi Settings on page 63), if this Nasuni Filer is not under the control of the Nasuni Management Console, or the Home page (see Home Page on page 32), if this Nasuni Filer is under the control of the Nasuni Management Console. Target IQN: The target IQN (iscsi Qualified Name). Clicking this link opens either the iscsi Settings page for this volume (see Changing iscsi Settings on page 63), if this Nasuni Filer is not under the control of the Nasuni Management Console, or the Home page (see Home Page on page 32), if this Nasuni Filer is under the control of the Nasuni Management Console. LUN Size: The size of the iscsi LUN (logical unit number). iscsi Initiator Status: A table displays, for each iscsi initiator connected to the Nasuni Filer through the iscsi protocol, the Initiator IQN, the Initiator Hostname, and the Initiator IP Address, as well as the Target IQN and the Target Volume. The iscsi Qualified Name includes these fields: iqn. Date that the naming authority took ownership of the domain, in yyyy-mm format.. followed by the reversed domain name of the authority, such as com.nasuni. : followed by a storage target name specified by the naming authority. Example: iqn com.nasuni:filer.nasuni.net:51 Nasuni Filer Administration Guide

380 NFS Status NFS Status Status You can view the status of NFS exports, as well as the status of clients connected to the Nasuni Filer through NFS file exporting. To view NFS status: 1. Click Status, then select NFS Status from the list. The NFS Exports page appears. Figure 12-26: NFS Exports page. The following information is displayed: Protocol version: The supported versions of the NFS protocol. NFS Exports: A table displays, for each NFS export: Volume: The volume of the NFS export. Clicking this link opens either the NFS Exports page for this volume (see Viewing an NFS Export on page 116), if this Nasuni Filer is not under the control of the Nasuni Management Console, or the Home page (see Home Page on page 32), if this Nasuni Filer is under the control of the Nasuni Management Console. Path: The path in the volume to the NFS export. Export Name: The name of the NFS export. Clicking this link opens either the Add NFS Export / Edit Settings page for this volume (see Editing an NFS Export on page 120), if this Nasuni Filer is not under the control of the Nasuni Management Console, or the Home page (see Home Page on page 32), if this Nasuni Filer is under the control of the Nasuni Management Console. Nasuni Filer Administration Guide

381 FTP Status FTP Status You can view FTP/SFTP directories for volumes that have the FTP/SFTP protocol enabled. You can also view the status of FTP/SFTP clients. Tip: In order to access data using the FTP/SFTP protocol, the following steps are necessary: Create a volume. See Adding a Volume on page 46. Enable the FTP protocol on the volume. See Enabling multiple volume protocols on page 135. (Optional) Configure FTP settings. See Configuring FTP settings on page 270. Add a new FTP/SFTP directory. See Adding FTP directories for a volume on page 127. (Optional) Create a permission group that has storage access. See Adding Permission Groups on page 318. (Optional) Create a user in a permission group that has storage access. See Adding Users on page 323. Access files using the FTP/SFTP protocol. See Accessing data using the FTP/SFTP protocol on page 141. Viewing FTP directories and FTP clients To view FTP/SFTP directories, follow these steps: 1. Click Status, then select FTP Status from the list. The FTP Directories page displays a list of FTP/SFTP directories for volumes that have the FTP protocol enabled. A list of any FTP/SFTP clients also appears. Figure 12-27: FTP Directories page. The following information is displayed: Protocol version: The supported versions of the FTP/SFTP protocol. FTP Directories: A table displays, for each FTP/SFTP directory, the following: Volume: The volume for the FTP/SFTP directory. Clicking this link opens either the FTP Directories page for this volume (see Viewing FTP directories on page 126), if this Nasuni Filer is not under the control of the Nasuni Management Console, or the Home page (see Home Page on page 32), if this Nasuni Filer is under the control of the Nasuni Management Console. Nasuni Filer Administration Guide

382 FTP Status Path: The path to the FTP/SFTP directory. Directory Name: The name of the FTP/SFTP directory. Clicking this link opens either the Add FTP Directory / Edit Settings page for this volume (see Editing FTP directories on page 132), if this Nasuni Filer is not under the control of the Nasuni Management Console, or the Home page (see Home Page on page 32), if this Nasuni Filer is under the control of the Nasuni Management Console. FTP Client Status: A table displays, for each FTP/SFTP client, the following: FTP Type: The type of FTP/SFTP client: FTP or SFTP. Host: The host of the FTP/SFTP client. User: The name of the user using the FTP/SFTP client. This user must belong to a permission group that has Storage Access enabled. See Users and Groups on page 315. Disconnecting FTP clients To disconnect an FTP/SFTP client, follow these steps: 1. Click Status, then select FTP Status from the list. The FTP Directories page displays a list of FTP/SFTP clients. Figure 12-28: FTP Directories page. 2. Select a client from the list of clients, then click Disconnect. The Disconnect Client dialog box appears. 3. Click Disconnect Client. The client is disconnected. The message Client was disconnected from the Filer appears. Click x to close the message box. Nasuni Filer Administration Guide

383 File Heuristics File Heuristics Chart You can view the number of each type of file and the number of each size of file stored using the Nasuni Filer. These metrics can be useful for planning storage. To view file metrics: 1. Click Status, then select File Heuristics from the list. The File Heuristics Information page appears. Figure 12-29: File Heuristics Information page. This page displays charts and tables of File Types in snapshots and File Sizes in snapshots. Nasuni Filer Administration Guide

384 File Heuristics File Types in snapshots On the top left side of the page is a pie chart displaying the percentage of files in the most common categories. Files are categorized by extension. For example, the Text category includes files with the extensions.doc,.rtf, and.txt. If you hover the mouse over one of the pie sections, it displays the name of the category, the percentage of that category, some of the extensions included in that category, and the number of files in that category. On the top right side of the page is a table displaying the number of files with the most frequent file extensions. You can sort this table by clicking Extension, Category, or Count. Statistics appear for the most frequent 50 extensions. File Sizes in snapshots On the bottom left side of the page is a bar chart displaying the number of files in each size category, with the size of the files along the horizontal axis and the number of files in each size category along the vertical axis. If you hover the mouse over one of the bars, it displays the name of the size category and the number of files in that category. From the drop-down list, you can select either a Logarithmic Scale or a Numeric Scale for the vertical axis of the bar chart. On the bottom right side of the page is a table displaying the number of files in each of the size categories. You can sort this table by clicking Max Size or Count. Nasuni Filer Administration Guide

385 Chapter 13: Notifications Notifications Notifications are Nasuni Filer messages. You might receive the following types of notifications: Info: The system has performed an action, or has changed its state, in such a way that the user might be interested, but that does not require action or attention. Warning: Something unusual has happened, but the user need not take action. Error: Something unusual or incorrect has occurred, and the user should take notice and try to resolve the situation, if possible. Errors generate messages to the user, if the user has set up . See Settings on page 247 for details. Alert: Something unusual or incorrect has occurred, and the user should take notice and try to resolve the situation, if possible, or contact Nasuni for assistance, if necessary. Alerts generate s to the user, if the user has set up . See Settings on page 247 for details. Examples of alert notifications are: Software update available. Account issues. Local cache issues. Evaluation period expired. Note: The Notifications page, and all other pages of the Nasuni Filer user interface, might look different to different users. Also, different menus and actions might be available for different users. This is because different users are assigned different permissions, based on their roles in the role-based access control system. See Users and Groups on page 315 for details. Nasuni Filer Administration Guide

386 Viewing Notifications Viewing Notifications Urgent notifications that require acknowledgment appear on the Notifications pane. You can view and filter all notifications using the Notifications pane. To view notifications, follow these steps: 1. Click the megaphone-shaped Notifications icon at the top right of any page. The Notifications pane appears. Figure 13-1: Notifications pane. Urgent notifications that require acknowledgment appear on the Notifications pane, based on the state of your system. A number to the right of a notification indicates multiple occurrences of the same notification. You can acknowledge a notification by clicking the x. To acknowledge all the urgent notifications, click Acknowledge All. 2. Click View all Notifications. The Notifications page appears and displays a list of notifications. Figure 13-2: Notifications page. The following information appears for each notification in the list: Severity: The severity of the notification, including Info, Warning, Alert, and Error. For details on the definitions of these notifications, see page 371. Date: The date and time of the notification. Message: The text of the notification. Acknowledged notifications display a checkmark to the right of their severity. At the top of the list is a count of the number of entries shown and the total number of entries. Nasuni Filer Administration Guide

387 Acknowledging Notifications 3. You can select whether to view acknowledged notifications, unacknowledged notifications, or all notifications, as follows: All: To view all notifications, including acknowledged notifications, select All. All notifications are listed. No: To view only notifications that have not been acknowledged, select No. Only unacknowledged notifications are listed. Yes: To view only acknowledged notifications, select Yes. Only acknowledged notifications are listed. 4. To include Alert notifications, select Alert. 5. To include Error notifications, select Error. 6. To include Warning notifications, select Warning. 7. To include Info notifications, select Info. Tip: Info notifications can safely be ignored. 8. To automatically refresh the Notifications page, select Enable Auto Refresh. 9. To move to the next page of notifications (if any), click the right arrow at the top of the page. 10. To move to the previous page of notifications (if any), click the left arrow at the top of the page. 11. To download notifications as a CSV file, click Download CSV. Filtering the Display Filter Using the Filter text box, you can limit the display to items that match the criteria that you enter. See Filtering Displays on page 385 for details. On this screen, the following field names are available: priority: Matches values in the Severity field. message: Matches values in the Message field. Note: If there are many notifications, it might take a little time to display the filtered results. Acknowledging Notifications Acknowledge You can acknowledge notifications. Acknowledging notifications marks them as read, but leaves them in place for further use. By contrast, deleting notifications removes them entirely. When you acknowledge notifications, you are no longer prompted to view them. To acknowledge notifications, follow these steps: 1. List and filter notifications as described in Viewing Notifications on page 372. Nasuni Filer Administration Guide

388 Deleting Notifications 2. Select the notifications that you want to acknowledge. To select all notifications on the page, select the check box to the left of the Severity heading. If there is more than one page of notifications, a message appears detailing how many notifications are selected and the total number of notifications matching the current criteria. Figure 13-3: Selected Notifications message. To select all the notifications matching the current criteria, click the Select all message. To clear the selection, click Clear selection. 3. Click Acknowledge. The Acknowledge Notifications dialog box appears. Figure 13-4: Acknowledge Notifications dialog box. 4. Click Acknowledge Notifications. The selected notifications are acknowledged. Alternatively, to exit this screen without acknowledging any notifications, click the Close button. Deleting Notifications Delete You can delete notifications. Deleting notifications removes them from the list entirely. When you delete notifications, you are no longer prompted to view them. Tip: There are often many notifications such as Snapshot not needed, Antivirus scan started, Updated the Nasuni Filer product license key, and Snapshot for volume... has been scheduled. Unless the Nasuni Management Console is experiencing problems in these areas, you can usually delete all notifications of this kind. To delete notifications, follow these steps: 1. List and filter notifications as described in Viewing Notifications on page Select the notifications that you want to delete. To select all notifications on the page, select the check box to the left of the Severity heading. If there is more than one page of notifications, a message appears detailing how many notifications are selected and the total number of notifications matching the current criteria. Figure 13-5: Selected Notifications message. To select all the notifications matching the current criteria, click the Select all message. To clear the selection, click Clear selection. Nasuni Filer Administration Guide

389 Downloading Notifications 3. Click Delete. The Delete Notifications dialog box appears. Figure 13-6: Delete Notifications dialog box. 4. Click Delete Notifications. The selected notifications are deleted from the list. Alternatively, to exit this screen without deleting any notifications, click the Close button. Downloading Notifications Download You can download notifications to a comma-separated values (CSV) file for further analysis or retention. To download notifications as a CSV file, on the Notifications page, click Download CSV. The notifications are downloaded and saved as a CSV file, according to the configuration of your browser. Nasuni Filer Administration Guide

390 Chapter 14: Disaster Recovery There are a number of reasons for performing a disaster recovery, including: Hardware and software failures. Power outages. Human error. Changing storage platforms. Moving data around the world. True natural disaster. With Nasuni s data services, your data is safely stored offsite in industry-leading data centers. Nasuni s system of automatic, scheduled snapshots protects your data, with no need for additional backups. Snapshots provide a full disaster recovery image of your data, as frequently as every minute. This data is available at any time to any location. You can rapidly get access to your data. To recover the data stored on your Nasuni Filer, you follow the simple steps of downloading the virtual machine again from Nasuni.com, installing the product, and then completing the disaster recovery process. If you have your encryption keys, the whole procedure takes about 15 minutes for a total recovery. Side Load and Disaster Recovery The Disaster Recovery process enables you to recover the Nasuni Filer after a true disaster, such as the loss of a data center. However, most of the time, customers perform the Disaster Recovery process in order to upgrade from one piece of hardware to another. In such a situation, there is a working Nasuni Filer in their data center that contains active data in the cache. Performing the Disaster Recovery process results in a new Nasuni Filer that has an empty cache. The customer must then re-populate the new cache with data, which requires considerable inbound bandwidth from the cloud, and which can take days, weeks, or even months to complete. The Side Load feature enables you to transfer cache data directly from the source decommissioned Nasuni Filer to the new Nasuni Filer. For more details, see Side Load on page 230. Nasuni Filer Administration Guide

391 Recovering Data with the Nasuni Filer Recovering Data with the Nasuni Filer This section explains how to recover your data with the Nasuni Filer in the event of a disaster. Warning: If there is any data in the cache that has not yet been protected in cloud storage, performing a disaster recovery procedure can cause that data to be lost. Before proceeding, perform a manual snapshot (see Take a Snapshot Now on page 54) and ensure that there is no data in the cache (see New Data in Cache Chart on page 35). Tip: Download your generated encryption keys to a safe location before shutting down the Nasuni Filer or performing a disaster recovery procedure on the Nasuni Filer. See Downloading (Exporting) Generated Encryption Keys on page 290 for details. Note: If you were using a hardware appliance, notify Nasuni Technical Support to request a replacement appliance at [email protected]. You can then continue with the following procedure, which allows you to install and operate a virtual appliance to access your data. Note: Downloading and executing the installation program for the virtual appliance is contingent upon the virtual platform you are using. Note: The Nasuni Filer must be shut down before performing this procedure. See Shutting Down and Rebooting the Nasuni Filer on page 27. To recover your data, follow these steps: 1. Obtain the Serial Number and Authorization Code for your Nasuni Filer. You use these in step 5. If you have the credentials to log in to your Nasuni.com account ( account/login/), you can obtain the Serial Number and Authorization Code there. If you do not have these credentials, obtain the Serial Number and Authorization Code from the person who has the credentials. You can also obtain serial numbers and authorization codes on the Account Status page of the Nasuni Management Console. 2. Download the Nasuni Filer software appropriate for your platform. Regardless of which version of the Nasuni Filer software that you used originally, you can download the latest version. Note: You can perform the disaster recovery process to the same version of the software that you were running, or to a newer version than you were running, but not to an older version. 3. Launch the Nasuni Filer install program for your platform. Tip: If your Nasuni Filer is a Nasuni Filer hardware appliance or runs in a VMware ESXi environment or Microsoft Hyper-V environment, you can force a file system check (fsck) by holding down the Shift key during the installation screen. When the file system check (fsck) is done, the usual processing continues. File system checks (using fsck) are necessary at least every six months. However, a file system check might take hours to complete (depending on the size of the cache) and might interfere with normal operations. To determine if a file system check is actually necessary, the Nasuni Filer periodically performs a background test. If this background test determines that a file system check is not necessary, the next file system check is postponed for another six months. However, if the background test determines that a file system check is necessary, you receive an alert suggesting that you perform a reboot and Nasuni Filer Administration Guide

392 Recovering Data with the Nasuni Filer a file system check. This allows you to select a time for performing a reboot with a file system check that does not interfere with normal operations. Even if you don t receive such an alert, you can choose to perform a file system check, for example, if you want to proactively verify the integrity of the cache, such as after an unexpected power loss. 4. Follow the setup wizard. After you have configured your network using the setup wizard, open the specific URL to continue. The Enter your serial number and authorization code wizard page appears. Figure 14-1: Enter your serial number and authorization code wizard page. 5. Enter the Filer Serial Number and Authorization code for this Nasuni Filer, found under the Account section of or on the Account Status page of the Nasuni Management Console. To recover a prior installation, such as during disaster recovery, choose the Nasuni Filer Serial Number of the prior installation. Click Continue to proceed. 6. The Perform Disaster Recovery on existing Filer page appears. Figure 14-2: Perform Disaster Recovery on existing Filer page. Nasuni Filer Administration Guide

393 Recovering Data with the Nasuni Filer Enter Perform Disaster Recovery without the quotation marks in the Confirmation text box, then click Continue to proceed. 7. The second Perform Disaster Recovery on existing Filer page appears. Figure 14-3: Second Perform Disaster Recovery on existing Filer page. If you escrowed your encryption keys with Nasuni, and do not have your encryption keys, and you need Nasuni to de-escrow your encryption keys, select Yes from the drop-down list. Contact Nasuni to receive your encryption keys, then enter your recovered encryption keys and click Continue. Otherwise, select No from the drop-down list, then click Continue. Important: If you have previously escrowed your encryption keys with Nasuni, and you use these escrowed encryption keys as part of the disaster recovery process, you MUST reescrow those encryption keys with Nasuni if you want those encryption keys to continue to be escrowed with Nasuni. After the disaster recovery is complete, the Nasuni Filer treats all encryption keys as if they were not created by this Nasuni Filer. For details, see, Escrowing Encryption Keys with Nasuni on page If you selected No, the Upload Encryption Keys page appears. Figure 14-4: Upload Encryption Keys page. Nasuni Filer Administration Guide

394 Recovering Data with the Nasuni Filer Click Choose File to navigate to your encryption key file, enter the Key Passphrase if necessary, then click Upload Key(s). If several encryption key files are necessary, this page could appear several times. 9. The Ready to perform disaster recovery! page appears. Figure 14-5: Ready to perform disaster recovery! page. Click Continue. Disaster recovery of the Nasuni Filer begins. 10. After recovery, the Filer Recovery Complete page appears. Figure 14-6: Filer Recovery Complete page. Nasuni Filer Administration Guide

395 Recovering Data with the Nasuni Filer 11. Click Continue. The Accept the Terms of Service and License Agreement page appears. Figure 14-7: Accept the Terms of Service and License Agreement page. You can print or download a copy of the Terms of Service and License Agreement by clicking the appropriate icon. Select I accept the Terms of Service, then click Continue. Nasuni Filer Administration Guide

396 Recovering Data with the Nasuni Filer 12. The Enter a username and password for Administration of this Filer page appears. Figure 14-8: Enter a username and password for Administration of this Filer page. Set up your account by creating a Username (case-sensitive) and a Password (case-sensitive). Click Continue. 13. The recovery and restoration process is complete. The Configuration Complete page appears. Figure 14-9: Configuration Complete page. You can reboot the Nasuni Filer, or click the link here to proceed directly to the Login page. 14. The Nasuni Filer becomes available in a few moments. The Login page appears. Figure 14-10: Nasuni Filer Login page. Nasuni Filer Administration Guide

397 Recovering Data with the Nasuni Filer Log in to the Nasuni Filer with your Username (case-sensitive) and Password (case-sensitive). Click Log in. Important: If the previous Nasuni Filer was in Active Directory mode, you must re-join Active Directory to maintain ACL support. With the new instance of the Nasuni Filer running, you have regained access to your volumes and data. You can access volumes and data using the CIFS shares, NFS exports, or FTP directories that you created before the disaster. Folders and files are available. Important: If this Nasuni Filer used a CIFS migration source to perform data migrations, you might need to manually reconnect to that CIFS migration source. See Configuring a CIFS Migration Source on page 201. Tip: If this Nasuni Filer previously accessed a volume with custom permissions for Remote Access, you must explicitly set those permissions for this Nasuni Filer. Important: If you have previously escrowed your encryption keys with Nasuni, and you used these escrowed encryption keys as part of the disaster recovery process, you MUST re-escrow those encryption keys with Nasuni if you want those encryption keys to continue to be escrowed with Nasuni. After the disaster recovery is complete, the Nasuni Filer treats all encryption keys as if they were not created by this Nasuni Filer. For details, see, Escrowing Encryption Keys with Nasuni on page 291. Tip: A best practice for Nasuni Filers is to join an Active Directory domain as soon as disaster recovery is complete. If the previous Nasuni Filer was in Active Directory mode, re-join Active Directory by clicking Save Settings. If the previous Nasuni Filer has not previously joined any domain, see Joining a Nasuni Filer (that has not previously joined any domain) to a domain on page 272. Tip: If the previous Nasuni Filer had Remote Support enabled, you must disable, then enable, Remote Support. See Remote Support Service on page 244. At this point, you can consider using the Side Load process to transfer data to the cache. For more details, see Side Load on page 230. Nasuni Filer Administration Guide

398 Appendix A: Nasuni Terms of Service and License Agreement Nasuni Corporation The Terms of Service and License Agreement for the Nasuni Filer is located at: Nasuni Filer Administration Guide

399 Appendix B: Filtering Displays Filtering the Display On some pages, you can limit the display to items that match the criteria that you enter. In the Filter text box, type the criteria, then click Apply Filter. Here are guidelines for using the Filter text box: Use spaces to separate criteria. The filter matches ALL of the criteria entered. You can enter letters and numerals, not case-sensitive. You can enter the following special ASCII $ % ^ (caret) * = ( ) [ ] { } < > /? (vertical bar) _ (underscore) (accent) ~ (tilde) : (colon), (comma). (period) Do not use the following ASCII symbols to filter: # & + ; (semicolon) (single quote) (double quote) You can enter a lowercase field name, followed by a colon, followed by a value. The field names vary depending on the screen. You can enter a lowercase condition, followed by a colon, followed by a Boolean value. The conditions vary depending on the screen. You can enter a minus sign (-) to negate any criterion. Examples: files volume:files readonly:true Matches any item that contains files in any field. Matches any item that contains in any field. volume:files readonly:true AND that has Read Only enabled. -readonly:true Matches any item that contains files in the Volume field. Matches any item that has Read Only enabled. Matches any item that contains files in the Volume field Matches any item that DOES NOT have Read Only enabled. Nasuni Filer Administration Guide

400 Appendix C: Glossary The following terms are useful in understanding the Nasuni Filer. A Access Control List (ACL) An access control list (ACL) is a list of permissions attached to an object. An ACL specifies which users or system processes are granted access to objects, as well as what operations are allowed on given objects. Active Directory (AD) Microsoft Active Directory (AD) is a directory service for Windows domain networks. It is part of most Windows Server operating systems. Microsoft Active Directory enables administrators to assign policies, deploy software, and apply critical updates to an organization. Active Directory stores its information and settings in a central database. Advanced Encryption Standard (AES) The Advanced Encryption Standard (AES) is a specification for the encryption of electronic data. It has been adopted by the U.S. government and is used worldwide. AES is approved by the National Security Agency (NSA) for top secret information. Authorization Code A 6-character code used in conjunction with a Serial Number to validate an installation. Authorization Codes are good for one use; one successful use causes an authorization code to be changed automatically. Generating a new authorization code for a serial number does not cause a Nasuni Filer or NMC that uses that serial number to stop working. The authorization code is only used once during initial setup of a new or recovered Nasuni Filer or NMC. Because an Authorization Code is only used once, an administrator can safely issue it to a user in order to install a single Nasuni Filer or NMC without revealing Nasuni account credentials. To obtain an Authorization code for a Serial Number, visit or the Account Status page of the Nasuni Management Console. Auto Cache A feature that immediately brings new data into the local cache from other Nasuni Filers that are attached to a volume. Otherwise, new data is brought into the local cache from other Nasuni Filers when that data is accessed next. Nasuni Filer Administration Guide

401 C cache A cache is a computer component that stores data locally so that future requests for that data can be served faster. While all data and metadata are stored in cloud storage, data that requires regular access is kept locally. This includes files that are re-written and data that is read often. If the requested data does not reside locally, it is staged into the cache and provided for the request. Challenge-Handshake Authentication Protocol (CHAP) A protocol that authenticates a user or network host to an authenticating entity. CHAP (Challenge-Handshake Authentication Protocol) See Challenge-Handshake Authentication Protocol (CHAP) on page 387. CIFS (Common Internet File Service) A standard protocol that allows Windows users to share files across a network. copy-on-write (COW) disk The copy-on-write (COW) disk is used during the snapshot process. If any writes to the Nasuni Filer occur during a snapshot, the previous data from the cache disk is copied to the COW disk, and the new data is written to the cache disk. Hence, the term copy-on-write. This allows new writes to take place at any time, even during the snapshot process. D Direct Attached Storage (DAS) Direct-attached storage (DAS) is computer storage that is directly attached to one computer or server and is not, without special support, directly accessible to other ones. The main alternatives to directattached storage are network-attached storage (NAS) and a storage area network (SAN). directory quota A limit on the amount of data in a directory. You can configure that quota reports are sent to administrators or users when directories near or exceed their quota. Dynamic Host Configuration Protocol (DHCP) Dynamic Host Configuration Protocol (DHCP) is a network configuration protocol that provides a network IP address for a host on an IP network automatically. Nasuni Filer Administration Guide

402 E encryption The Nasuni Filer encrypts data sent to cloud storage using the OpenPGP standard, with AES-256 as the default encryption. eviction Data that has been copied from the Nasuni Filer to cloud storage, and that is rarely used again, is eventually removed ( evicted ) from the Nasuni Filer s cache to free up space for new data. If one of these evicted files is later requested for reads or writes, the Nasuni Filer retrieves the file from cloud storage and puts it back into the cache automatically. export A directory on a server volume that a client on your network can access. F file system A method for storing and organizing computer files and the data that they contain in order to make it easy to find and access them. FTP (file transfer protocol) File Transfer Protocol (FTP) is a standard network protocol used to transfer files from one host to another host over a TCP-based network, such as the Internet. G GB/GiB GB is an abbreviation of gigabyte, meaning 1,000,000,000 bytes. Usually used to refer to hard disk capacity. GiB is an abbreviation of gibibyte, meaning 2 30 (1,073,741,824) bytes. Usually used to refer to RAM memory. global file locking The purpose of the global file locking feature is to prevent conflicts when two or more users attempt to change the same file on different Nasuni Filers. If you enable the global file locking feature for a directory and its descendants, any files in that directory or its descendants can only be changed by one user at a time. Any other users cannot change the same file at the same time. You can also manually break the locking of a file. This might become necessary if a user leaves a file open and another user needs to open that file. Nasuni Filer Administration Guide

403 I initiator An initiator functions as an iscsi client. An iscsi initiator sends SCSI commands over an IP network. instance The Nasuni Filer is either a hardware appliance or virtual machine. You can have three Nasuni Filers for each terabyte you are protecting with the Nasuni Service. Internet Small Computer System Interface (iscsi) An Internet Protocol (IP)-based storage networking standard for linking data storage facilities. By carrying SCSI commands over IP networks, iscsi facilitates transferring data over intranets and managing storage over long distances. The protocol allows clients (called initiators) to send SCSI commands (CDBs) to SCSI storage devices (targets) on remote servers. iscsi is a Storage Area Network (SAN) protocol. IQN (iscsi Qualified Name) See iscsi Qualified Name (IQN) on page 389. iscsi (Internet Small Computer System Interface) See Internet Small Computer System Interface (iscsi) on page 389. iscsi Qualified Name (IQN) The iscsi Qualified Name includes these fields: M MB/MiB iqn. date that the naming authority took ownership of the domain, in yyyy-mm format. reversed domain name of the authority, such as com.nasuni. : followed by a storage target name specified by the naming authority. Example: iqn com.nasuni:filer.nasuni.net:51 MB is an abbreviation of megabyte, meaning 1,000,000 bytes. Usually used to refer to hard disk capacity. MiB is an abbreviation of mebibyte, meaning 2 20 (1,048,576) bytes. Usually used to refer to RAM memory. Nasuni Filer Administration Guide

404 metadata Data about data. Metadata describes how and when and by whom a particular set of data was collected, and how the data is formatted. MIB (management information base) A database for managing entities in a network, such as with the Simple Network Management Protocol (SNMP). MTU (maximum transmission unit) The maximum transmission unit (MTU) is the size (in bytes) of the largest protocol data unit that the layer can pass onwards. A larger MTU brings greater efficiency, because each packet carries more user data while protocol overheads, such as headers, remain fixed; the resulting higher efficiency means a slight improvement in the bulk protocol throughput. A larger MTU also means processing fewer packets for the same amount of data. However, large packets can occupy a slow link for some time, causing greater delays to following packets, and increasing lag and minimum latency. MTU settings should not exceed N NAS (Network Attached Storage) See Network Attached Storage (NAS) on page 391. Nasuni Filer The Nasuni Filer is a storage controller that runs in your data center and provides primary storage with built-in backup and offsite protection. The Nasuni Filer is available as both a hardware appliance and a virtual machine. The Nasuni Filer can be used instead of, or in combination with, traditional file servers. It fully supports Windows CIFS Shares as well as Active Directory. A single volume in a Nasuni Filer has unlimited capacity, due to the integration of its caching algorithms with provisioning. Nasuni Filer user interface (UI) The Web-based user interface to the Nasuni Filer. Nasuni Management Console (NMC) The Nasuni Management Console enables you to monitor and manage many Nasuni Filers from one central application. Using the Nasuni Management Console, you can view the status of all of your managed Nasuni Filers, as well as configure their settings. With the Nasuni Management Console, you can ensure consistent settings on all your Nasuni Filers. Using the Nasuni Management Console, you can manage Nasuni Filers even if they are not presently connected. Any configuration changes made will propagate to the Nasuni Filer when it becomes connected. Nasuni's cloud storage The secure unlimited online storage provided through the Nasuni Filer. Nasuni Filer Administration Guide

405 Network Attached Storage (NAS) Network-attached storage (NAS) is file-level computer data storage connected to a computer network. NAS devices are a convenient method of sharing files among multiple computers. NAS systems typically provide access to files using network file sharing protocols such as NFS, SMB/CIFS, or AFP. NFS (Network File System) A protocol and file system for accessing and sharing files across a computer network using UNIX and Linux. NMC (Nasuni Management Console) See Nasuni Management Console (NMC) on page 390. O offsite data protection Storing copies of critical data away from the original data centers to protect this information from natural disasters and accidental or malicious modification. on-demand provisioning The Nasuni Filer simplifies provisioning by offering instant provisioning in increments as small as 1 TB. P pinning Pinning a folder specifies that the folder and its contents must remain in the local cache at all times. This can improve performance and reduce the time necessary to return accessed data to clients. This reduces the available cache by the size of the folder. Pinning a folder does not bring the folder s data into the cache. All iscsi (SAN) volume data is already pinned in the cache, so it is not necessary to pin iscsi volumes. proxy A server that acts as an intermediary for requests from clients seeking resources from other servers. Q Quality of Service Quality of Service (QoS) settings indicate the inbound and outbound bandwidth limits of the Nasuni Filer for data moving to or from the Nasuni Filer, such as transmitting snapshots to cloud storage. quota A limit on the amount of usable storage space on a volume. Nasuni Filer Administration Guide

406 S SAN (Storage Area Network) See Storage Area Network (SAN) on page 392. Serial Number A unique 32-digit hexadecimal number associated with your account for use with Nasuni Filer and Nasuni Management Console (NMC) installations. Each account has multiple Serial Numbers. Unused Serial Numbers may be used to set up a new Nasuni Filer or an NMC. Serial Numbers already in use may be used to recover existing Nasuni Filers or your existing NMC. Serial Numbers are used in conjunction with Authorization Codes. To obtain a Serial Number, visit account/serial_numbers/. share A folder on a volume that can be shared on your network. Access to a share can be customized on a user or group-level basis. snapshot An instantaneous, non-changing, read-only image of a volume. Snapshots let you view any past version of the file system and restore all or part of the version quickly. A snapshot is a complete picture of the files and folders in your file system at a specific point in time. With snapshots, the Nasuni Filer can identify new or changed data. Snapshots offer data protection by enabling you to recover a file deleted in error or to restore an entire file system. After a snapshot has been taken and is sent to cloud storage, it is not possible to modify that snapshot. SNMP (Simple Network Management Protocol) An Internet-standard protocol for managing devices on IP networks. Storage Area Network (SAN) An architecture to attach remote computer storage devices (such as disk arrays, tape libraries, and optical jukeboxes) to servers in such a way that the devices appear as locally attached to the operating system. sync You can schedule when, and with what frequency, the selected volume updates data ( syncs ) from the Nasuni Service, merging your local data with any new or changed data from other Nasuni Filers connected to this volume. This helps to ensure that everyone in your organization is using the most current data. T target A storage resource located on an iscsi server. A target is a storage server instance. Nasuni Filer Administration Guide

407 V versioning The Nasuni Filer provides the versioning necessary to eliminate the need for separate backup and restore procedures. virtual machine A virtual machine is a tightly isolated software container that can run its own operating systems and applications as if it were a physical computer. A virtual machine behaves exactly like a physical computer and contains its own virtual (software-based) CPU, RAM, hard disk, and network interface card (NIC). virtualization Virtualization lets you run multiple virtual machines on a single physical machine, sharing the resources of that single computer across multiple environments. Different virtual machines can run different operating systems and multiple applications on the same physical computer. volume A set of files and directories. A volume can consist of multiple shares. With the Nasuni Filer, each volume can be stored in cloud storage. Nasuni Filer Administration Guide

408 Index (port) Network Time Protocol (NTP) (port) SNMP monitoring (port) SMTP port (port) mobile access 158, 239 VPN for mobile access 158 Web Access (port) user interface 150 A access group 104, 105, 106, 110, 111, 112, 129, 130, 131 Read Only 84, 85, 119, 123, 209, 210 Read-Only 103, 105, 106, 111, 112 read-only 128, 196, 197 read-write 84, 85, 105, 106, 111, 112, 208 snapshot 92, 107, 194 user 105, 106, 111, 112, 118, 123, 130, 131 accessing iscsi volume Windows 144, 145 accessing data FTP protocol 141 account name 338 status 338 user 30, 336 account alerts 248 acknowledging alert 373, 374 ACL 383 ACLs 57, 136 Active Directory 1, 173, 261, 272, 383 administrative user 283 for time 268 leaving domain 275 password 276, 279 permission 283 security configuring 272 server domain name 278 time server 268 trusted domains 272, 279 username 276, 279 Active Directory domain editing 275 joining 272, 273, 277 leaving 275 name 274, 282 viewing 274 workgroup name 274, 282 active node 343 Nasuni Filer Administration Guide

409 Index adding data to volume 138 encryption key to volume 81 export 117 FTP directory 127 NFS export 117 permission group 318, 321 share 101 share folder 101 user permission 323, 324, 325 volume 46 Administration Guide xiv administrative user Active Directory 283 AES alert acknowledging 373, 374 definition examples of 371 message panel 24, 30, 31, 372 notification 30, 371 types of 248 all_squash UNIX 118, 123 Android 157, 235, 236 limiting mobile access to 236 anonymous FTP access 129, 132, 271 antivirus alerts 248 antivirus service 69 Apple Safari 2, 19 appliance alerts 248 Asynchronous I/O 108 auditing 73 file system 73 log file 76 pruning 74 volume 73 authenticating user 104 Authorization Code 6, 21, 377 Auto Cache cache jobs 342 folder 97, 179, 180, 189 volume 86 Auto Refresh 373 automatic updates 332 B backup before restoring 192 BIOS firmware version 354 BMC firmware version 354 branding Web Access 109, 150, 330 breaking file lock 171, 180, 190, 191 Bring into Cache 185, 342 browsing snapshot 194, 197, 198 C cache 2, 4 bringing data into 185 cache jobs 342 capacity 5 folder pinned 58, 96, 188 space reserved 13, 333, 334 status 5, 39 volume pinned 13, 43, 44, 48, 52, 60, 64 cache jobs 342 cancelling 342 viewing 342 Cache Resident 178, 179, 180 Cache Settings 200, 333 cancelling cache jobs 342 capacity cache 5 capacity alerts 248 capacity exceeded warning 56, 65, 248, 338 carrier 349 signal 349 Case-Sensitive Paths 107 case-sensitivity 107, 147 Nasuni Filer Administration Guide

410 Index certificate file 304, 307 name 302, 304, 306, 308 self-signed 12, 301, 303 SSL 301, 302 copying 306 generating 303 replacing 310 setting 312 uploading 308 viewing 301 Certificate Authority 304, 307 certificate request 304, 306 file 304, 307 name 304, 307 Challenge-Handshake Authentication Protocol CHAP 49 changing data migration schedule 224 iscsi setting 63, 64 password 29, 336 Quality of Service rule 265 quota volume 11, 65 volume quota 11, 65 CHAP Challenge-Handshake Authentication Protocol 49 password 49 username 49 chart data growth 34, 61 Local Traffic 36 local traffic 350 network activity 36, 350 new data in cache 35 Chrome 2, 19 CIFS 48 configuring data migration 205 data migration source 201 Mac OSX 48 protocol 43, 44, 48, 52, 57 share 43, 44, 52, 115, 125 snapshot access 92, 107, 194 volume 46 CIFS migration password 202 username 202 CIFS share default 45 deleting 115 editing 113 status 360 Cleversafe vault 56 client disconnecting 363, 364 FTP 368 Linux 242 OSX 242 resetting 362, 363, 364 status 361, 366 Windows 242 cloud provider volume 56, 59 Cloud Traffic chart chart Cloud Traffic 36, 350 compliance and snapshot retention 95 compression 1, 4, 287 Configuration page 246 configuring data migration 200 CIFS 205 NFS 213 conflict alerts 248 connecting to remote volume 51 console 296 default login 314 message 29 password 314 rebooting 28 resetting certificate 301, 314 shutdown 29 username 314 copying migration 206, 214 SSL certificate 306 cores per CPU 344 count CPUs 344, 353 CPU cores per 344 count 344, 353 frequency 344 Nasuni Filer Administration Guide

411 Index creating data migration source CIFS 201 NFS 203 export automatically 48 folder mobile access 165 password 382 share automatically 48 username 382 volume 46 credentials 378 custom permission remote access 85 data adding to volume 138 data growth chart 34, 61 Data Growth chart volume 34, 61 D data migration 199 alerts 248 CIFS 205 configuring 200 CIFS 205 NFS 213 creating source CIFS 201 NFS 203 deleting 228 editing 219 error log 229 error message 210, 216 log 225, 229 name 38, 206, 214 NFS 213 permission 200, 202 removing procedure 228 rerunning 227 schedule changing 224 deleting 224 scheduling 220 by day and time 220 by hours or minutes 222 frequency 222, 223 source deleting 227 disconnecting 227 status 38, 211, 212, 217, 225, 226 to volume 9, 200 view log 225, 229 viewing schedule 224 Data Migration Service 200, 333 decommissioned 230, 231, 376 deduplication 1, 4 default login console 314 share 45 volume 45 default share files 101 default volume files 45 Nasuni Filer Administration Guide

412 Index deleting 115, 125 CIFS share 115 data migration procedure 228 data migration schedule 224 data migration source 227 encryption key 293 FTP directory 133 mobile access 164 NFS 115, 125 NFS export 125 notification 374 notifications 374 permission group 322 Quality of Service rule 267 share 115 snapshot 10, 94, 176 SSL certificate 314 user permission 326 volume 98 Deny 105, 106, 111, 112 Desktop Client 108 destination folder data migration 207 details for volume 42 device mobile access 157, 235 DHCP 260, 261, 348 network type 260 diagnostics 245 password 245 sending to Nasuni Support 245 username 245 directory destination 215, 217 FTP 126, 367 viewing 126, 367 quota 11, 297 directory quota 66 deleting 66 editing 66 rule 66 setting 186 viewing 66 disabling encryption key 79 pinning 96 disaster recovery 47, 227, 250 during trial mode 290, 377 encryption key 47, 289, 290, 291, 377, 379 file 380 procedure 376 snapshot 376 disconnecting client 363, 364 data migration source 227 from volume 174 FTP client 368 remote volume 174 DNS mobile access 158, 239 domain controllers Network Time Protocol services 279 domain groups 316 domain name 276, 278, 279, 304 Active Directory 278 domain users 316, 317 download files 177 folders 177 mobile 162 downloading encryption key 290 file 187 notifications 373, 375 software Nasuni.com account 377 Web Access 154 duplex 349 E editing Active Directory domain 275 CIFS share 113 configuring data migration 219 FTP directory 132 NFS export 120 permission group 322 user permission 325 editing volume name 62 alert 248 configuring 247 Nasuni ii Nasuni Support ii quota 11, 297 setting 8, 247 Nasuni Filer Administration Guide

413 Index enable Web Access 108 enabling 77 encryption key 77 multiple protocols 135 snapshot access 92 encryption key 77, 287 adding 81, 289 adding to volume 81 creating volume 47 deleting 293 disabling 79 disaster recovery 379 downloading 290 enabling 77 escrowing 291 exporting 290 file 47, 289, 290 disaster recovery 380 fingerprint 288 generating 289 importing 289 information 288 key ID 288 password 78, 80, 82, 292, 293 status 56, 60, 77, 78, 79, 81 uploading 289 username 78, 80, 82, 292, 293 volume 56, 60 error data migration log 229 definition 371 log data migration 229 error message during data migration 210, 216 escrowing encryption key 291 with Nasuni 287, 290, 291 with third party 290 expiration subscription 338 Explorer 2, 19 export 2 adding 117 creating automatically 48 creating automatically 48, 53 editing 120 migration source 200, 203 mounting 147, 149 name 118, 366 Read Only 119, 123 status 365, 366 exporting encryption key 290 External traffic group 252, 347, 348 F failover trigger 343, 345 favorite mobile access 162, 163, 165 FDE 357 Nasuni Filer Administration Guide

414 Index file certificate 304, 307 certificate request 304, 307 deleting 94 downloading 177 encryption key 47, 289, 290 file disaster recovery 380 excluding 210, 216 File Sizes chart 370 File Types chart 370 global locking 4, 58, 69, 88, 171, 177, 178, 179, 180, 185, 190, 191 hiding 107 lock breaking 191 locking 190 log data migration 225, 229 mirroring 210, 216 name case-sensitive 107 overwriting 210, 216, 217 owner 180, 208 path 180 permission 202, 208, 210 previous version 107 restoring 10, 177, 185, 198 searching 182 searching for 177, 182 size number 369 synchronization conflict log 171, 172 File Alert Service 67 file alert service status 67, 70, 71 File Browser page 176 file heuristics 369 file information mobile access 162 file lock CIFS 361 file locking 4, 58, 69, 88, 171, 178, 179, 180, 190, 191 breaking 171, 180, 190, 191 File Sizes chart 370 file sizes in snapshot 369, 370 file statistics 369 file system 4 auditing 73 file system browser 177 file system check on reboot 28 file system metadata 4 file type number 369 File Types chart 370 file types in snapshot 369, 370 file version 4 Filer Administrator 19, 139 password 20 username 20 filtering by criteria 385 notifications 373 fingerprint encryption key 288 Firefox 2, 19 firewall policy traffic group 295 firmware BIOS 354 BMC 354 RAID 354 folder access 103, 118, 123, 143, 147, 149 Auto Cache 97, 179, 180, 189 default shared 45 destination 211 downloading 177 excluding from data migration 210, 216 global locking 178, 179, 180 hiding 107 name case-sensitive 107 owner 179 path 179 pinning 178, 180 pinning in cache 96, 188 restoring 10, 177, 185, 192 searching 182 searching for 177, 182 forgot password 21 frequency CPU 344 data migration scheduling 222, 223 scheduling data migration 222, 223 snapshot 89 fsck 28, 340, 377 on reboot 28 FTP 57, 126, 132, 136, 367 anonymous access 129, 132, 271 client 368 disconnecting 368 settings 270 Nasuni Filer Administration Guide

415 Index FTP directories 43, 44 FTP directory 126, 367 adding 127 deleting 133 editing 132 viewing 126, 367 FTP protocol 21, 44, 52, 57, 137, 138, 141, 270 Full Disk Encryption password 358, 359 Full-Disk Encryption 357 G gateway traffic group 260 general alerts 248 General traffic group 252, 347, 348 generating SSL certificate 303 global file locking 4, 58, 69, 88, 171, 177, 178, 179, 180, 185, 190, 191, 335 breaking 171, 180, 190, 191 enabling 190 global file locking, disabling 335 global locking 190, 335 folder 178, 179, 180 global name 56 GnuPG 289 Google Chrome 2, 19 group access 104, 105, 106, 110, 111, 112, 129, 130, 131 permission 209, 315, 318, 319, 320, 321, 322, 323, 324, 325 adding 318, 321 deleting 322 editing 322 viewing 316 group associations 316, 318, 321 Groups Granting Access 317 H hardware appliance console 301, 314 cores per CPU 353 CPU frequency 353 CPU model 353 CPUs 353 high availability 28 locating 354 power supplies 353 power supply status 344, 354 RAM 353 replacing after disaster 377 serial number 353 status 353 temperature 353 Hardware Getting Started Guide xiii hardware status 353 high availability 343 Help 22, 24 help 24 hiding file 107 folder 107 hiding ownership 132 FTP 132 high availability cores per CPU 344 CPU frequency 344 CPU model 344 CPUs 344 hardware appliance 28 status 343 network configuration 260 power supplies 344 RAM 344 serial number 344 Static network type 260 status 343 temperature 344 Home page 32 host options NFS 122, 123, 124 NFS export 122 hostname 118, 123, 201, 203, 251, 258 HTTPS for time 268 HTTPS proxy 261 HTTPS proxy server 251 port 251 Nasuni Filer Administration Guide

416 Index I information volume 56, 59 informational notification definition 371 Initial Configuration Guide xiv internal link 152 Internet Explorer 2, 19 ios 157, 235, 236 limiting mobile access to 236 IP address 49, 64, 103, 118, 123, 129, 143, 201, 203, 251, 260, 261, 262, 348 primary DNS server 261 public 348 secondary DNS server 261 ipad 157, 235 iphone 157, 235 IQN 365 iscsi LUN 365 protocol 43, 48, 57 security 49, 64 setting changing 63, 64 target 48 volume accessing Windows 144, 145 adding 48 iscsi Initiator 144 iscsi Qualified Name 365 joining Active Directory domain 272, 273, 277 key ID encryption key 288 key terms 2 J K L leaving Active Directory domain 275 license 5, 338, 384 licensed capacity 48, 56, 65, 338 exceeding 56, 65, 248, 338 Linux 138, 149 CIFS 48 client 242 mobile access 236 NFS 48 list remote volume 51 local volume 42 local name remote volume 44, 52 local storage status 39 local time status 40 Local Traffic chart 36 local traffic chart 350 local volume changing 43 lock breaking 171, 180, 190, 191 locking file 4, 58, 69, 88, 171, 177, 178, 179, 180, 185, 190, 191 log data migration 225, 229 data migration status 225, 229 merge conflict 172 log file auditing 76 pruning 74 login console default 314 password 19 username 19 Login page 19 logo Web Access 330 Logout 29 logout 29 LUN Size 59, 365 LUN size 43 M MAC address 349 Mac OSX CIFS 48 Management traffic group 252, 347, 348 mapping drive share 143 maximum transmission unit 260 Nasuni Filer Administration Guide

417 Index maximum volumes trial mode 46 Media Access Control address 349 merge synchronization 90, 171 merge conflict log 172 message console 29 panel 30 alert 24, 30, 31, 372 shutdown 28 status 23 synchronization conflict 171, 172 test 249 messages notifications 371 metadata 2, 4, 13, 342 file system 4 volume 4 migration copying 206, 214 log 225, 229 name 38, 206, 214 status 38, 211, 212, 217, 225, 226 mobile download 162 mobile access 157, 167 additional port 236 configuring 236, 238 creating folder 165 deleting 164 device 157, 235 DNS 158, 239 favorite 162, 163, 165 file information 162 invitation link 238 limiting device type 236 limiting time 236 limiting to one device 236 Nasuni Application 157, 158, 160, 235, 238 port service 235 uploading 164 version 162 Wi-Fi 166 monitoring SNMP Nasuni Management Console 327 mounting export 147, 149 share 147 Mozilla Firefox 2, 19 MTU 260 multiple protocols 134 enabling 135 viewing 134 N name account 338 Active Directory domain 274, 282 certificate 302, 304, 306, 308 certificate request 304, 307 data migration 38, 206, 214 export 118, 366 global 56 local for remote volume 53 Nasuni Filer 23, 171 changing 250 port 349 share 102, 201, 360 volume 38, 40, 43, 46, 52, 56, 59, 62, 367 editing 62 setting 46 Windows workgroup 278, 283 Nasuni Application mobile access 157, 158, 160, 235, 238 Nasuni corporate Web site 23, 156 Nasuni Desktop Client 108, 167, 235, 242 Nasuni Filer 2 name 23, 171 changing 250 Nasuni Filer user interface 2 Nasuni Management Console 2, 199, 243 disabling 243 enabling 243 Nasuni Management Console Guide xiv Nasuni Management Console Quick Start Guide xiv Nasuni.com account downloading software 377 remote access 43, 83, 170 native users 316, 317 netmask 103, 118, 123, 260, 349 network configuration high availability 260 password 262, 312 username 262, 312 setup 257 status 346 network activity chart 36, 350 network devices 347 Nasuni Filer Administration Guide

418 Index Network Time Protocol for time 268 NTP 261 port services from domain controllers 279 network type 348 DHCP 260 static 260, 261 New data in Cache volume 35 new data in cache chart 35 NFS 48 configuring data migration 213 data migration source 203 deleting 115, 125 export 43, 44, 52 host options 122, 123, 124 protocol 43, 44, 48, 52, 57 snapshot access 92, 194 VMware 148 volume 46 NFS export deleting 125 editing 120 status 365, 366 NFSv4 ACL 57, 136 NFSv4 protocol 57, 136 NMC Nasuni Management Console 2 no_root_squash UNIX 118, 123 nocase 147 node active 343 standby 343 notification 24, 372 alert 371 deleting 374 near quota 48, 56, 65 sorting by date 373 by severity 373 by text 373 types of 371 Notifications 24 notifications deleting 374 downloading 373, 375 filtering 373 viewing 24, 372 Notifications page 7 NTFS 57, 136 NTP for time 268 Network Time Protocol 261 time server 261 O on-demand snapshot 54 open file 361 OpenPGP 47, 287, 289, 388 OSX client 242 mobile access 236 OSX client 4, 284 overwriting during restore 192 not by sync 171 preventing during data migration 207, 210, 216 owned by 56 P password 20 Active Directory 276, 279 changing 29, 336 CHAP 49 CIFS migration 202 console 314 creating 382 diagnostics 245 encryption key 78, 80, 82, 292, 293 Filer Administrator 20 forgot 21 Full Disk Encryption 358, 359 login 19 network configuration 262, 312 shutdown 27 software update 341 volume deleting 99 disconnect 174 pausing Side Load 233 Nasuni Filer Administration Guide

419 Index permission Active Directory 283 custom remote access 85 file 208, 210 for data migration 200, 202 group 209, 315, 318, 319, 320, 321, 322, 323, 324, 325 adding 318, 321 default 315 deleting 322 editing 322 viewing 316 remote access 84 remote volume 43, 44, 52 user 209, 315, 318, 323, 324, 325, 326 adding 323, 324, 325 default 315 deleting 326 editing 325 permission set 208, 210 adding 208 label 208 selecting 210 permissions Windows 139 PGP 289 physical ports carrier 349 duplex 349 MAC address 349 name 349 speed 349 status 349 pinned folder viewing 96 pinning disabling 96 folder 178, 180 folder in cache 58, 96, 188 volume in cache 13, 43, 44, 48, 52, 60, 64, 96, 188 port 123 Network Time Protocol (NTP) SNMP monitoring SMTP port mobile access 158, 239 VPN for mobile access 158 Web Access 150 carrier 349 duplex 349 HTTPS proxy server 251 MAC address 349 name 349 physical 349 speed 349 port POSIX 57, 136, 284 POSIX ACL 57, 136 POSIX client 284 power 22, 24, 27, 28, 29 power supply status 344, 354 preview 154 previous version file 107 primary DNS 261 primary DNS server IP address 261 privacy policy 22, 24 properties volume 56, 59 protocol CIFS 48 FTP 270 iscsi 48 NFS 48 SMB 284, 360, 366, 367 SMB2 284, 360, 366, 367 SMB3 284, 360, 366, 367 SMBv2 284, 360, 366, 367 SMBv3 284, 360, 366, 367 volume 43, 44, 52, 57, 60 protocols multiple 134 proxy server HTTPS 251 Nasuni Filer Administration Guide

420 Index Q Quality of Service 39 changing rule 265 deleting rule 267 rule 265, 267 quota 65, 177 changing 65 directory 11, 66, 186, , 297 notification near 48, 56, 65 report 11, 297 status 65 volume setting 11, 48, 65 quota limit 187 quota report 186 adding new 298 deleting 300 editing 300 sending now 299 viewing 297 R RAID array 355 disk 355 firmware version 354 level 355 RAID array rebuilding 39 Read Only 43, 44, 52 Read Only access 84, 85, 119, 123, 209, 210 Read/Write 43, 44, 52 Read-Only access 103, 105, 106, 111, 112 read-only access 128, 196, 197 read-write access 84, 85, 105, 106, 111, 112, 208 rebooting 28 after software update 340 console 28 with file system check 28 with fsck 28 refreshing subscription license 339 region 47, 56, 268 Release Notes 25 viewing 25, 341 remote volume 42, 43, 44, 52 remote access 51, 83, 85, 170 connecting to volume 51 disabling 83 disconnecting volume 174 enabling 83, 170 maximum group size 338 maximum volumes 338 Nasuni.com account 43, 83, 170 permission 84 custom 85 remote and local connections 170 setting 83 snapshot frequency 89 status 57, 83 Remote Access Type 58 Remote Support Service 244 remote volume 53, 171 changing 43 connecting to 51 disconnecting 174 list 51 local name 44, 52 local name for 53 maximum number 338 removing data migration procedure 228 removing alert from Home page 373 renaming volume 62 replacing SSL certificate 310 report quota 11, 297 rerunning data migration 227 data migration procedure 227 resetting CIFS authentication cache 362 client 362, 363, 364 SSL certificate 314 resetting certificate console 301, 314 restoring backup before 192 file 10, 177, 185, 198 folder 10, 177, 185, 192 folder from snapshot 192 restoring file or folder snapshot 177, 192, 193 Nasuni Filer Administration Guide

421 Index retention snapshot 58, 60, 77, 95, 287 role-based access control 32, 41, 176, 199, 246, 315, 337, 371 root_squash UNIX 118, 123 S Safari 2, 19 saving SSL certificate 313 schedule snapshot 10, 58, 60, 88, 89, 176 sync 58 scheduling data migration 220 by day and time 220 by hours or minutes 222 snapshot 10, 88, 89, 176 search for files 177 for folders 177 searching file and folder for restore 182 snapshot 182 searching for file 182 folder 182 username 209 secondary DNS 261 secondary DNS server IP address 261 security Active Directory configuring 272 iscsi 49, 64 security mode Active Directory 272 security setting 287 SED 357 self-encrypting drive 357 self-signed certificate 12, 301, 303 sending quota report now 299 Serial Number 6, 21, 338, 377, 378 Service Level Agreement 22, 24 setting name volume 46 remote access 83 SSL certificate 312 volume name 46 settings FTP 270 setup wizard 378 SFTP 1, 4, 57, 136 share 2 access 103 adding 101 creating 101 automatically 48, 53 default 45, 101 deleting 115, 125 editing 113 mapping network drive 143 migration source 200 mounting 147 name 102, 201, 360 Read-Only 103 status 360 viewing 100 visible 103 volume and 2 shared directory 117 shared folder 100, 101, 116 adding 101 shared link 108, 109, 152 shutdown 22, 24, 27, 28 console 29 message 28 password 27 username 27, 341 shutdown option 27 shutdown window 27, 28 shutting down Nasuni Filer 27 Side Load 230, 232, 376, 383 pausing 233 signature type 302 size volume 40, 43, 44, 52, 56 SMB 284 SMB protocol 284, 360, 366, 367 SMB2 284 SMB2 protocol 284, 360, 366, 367 SMB3 protocol 284, 360, 366, 367 SMBv2 protocol 284, 360, 366, 367 SMBv3 protocol 284, 360, 366, 367 SMTP port Nasuni Filer Administration Guide

422 Index snapshot 4 access 58, 107, 194 enabling 92 status 92 and Quality of Service 39, 263 and quota 11, 48, 65 available 197 before disconnecting from remote volume 174 before shutdown 27, 28 browsing CIFS 194, 197, 198 definition 2 deleting 10, 94, 176 detail 4, 12, 88, 176, 263 disaster recovery 376 enabling access 92 file sizes in 369, 370 file types in 369, 370 frequency 89 immediate 54 initial 4 message 23 most recent for volume 40 on-demand 54 restoring file or folder 177, 192, 193 restoring folder and file 192 retention 58, 60, 77, 95, 287 status 94 schedule 10, 54, 58, 60, 88, 89, 176 status 88 scheduling 10, 88, 89, 176 searching 182 searching for file 182 status 38 taking 54 snapshot access 92, 107, 194 status 92 snapshot directories 197 Snapshot Directory Access 58, 92, 107, 194 snapshot restore alerts 248 snapshot retention and compliance 95 status 94 snapshot retention policy 10, 94, 176 snapshot schedule status 88 SNMP monitoring Nasuni Filer 327 Nasuni Management Console 327 port trap 329 v1 328 v2c 328 v3 328 software update 340 software updates 248 source folder data migration 207 Spanning Tree 252 speed port 349 SSL 248 SSL certificate 301, 302 copying 306 deleting 314 generating 303 replacing 310 resetting 314 saving 313 setting 312 uploading 308 viewing 301 standby node 343 static 348 network type 260, 261 Nasuni Filer Administration Guide

423 Index status account 338 cache 5, 39 CIFS share 360 client 361, 366 data migration 38, 211, 212, 217, 225, 226 data migration log 225, 229 encryption key 56, 60, 77, 78, 79, 81 file alert service 67, 70, 71 hardware appliance 353 refresh 354 high availability hardware appliance 343 local storage 39 message 23 network 346 NFS export 365, 366 physical ports 349 power supply 344, 354 quota 65 remote access 57, 83 snapshot 38 snapshot access 92 snapshot retention 94 snapshot schedule 88 subscription 338 sync schedule 90 virtual machine status 353 volume 40 Status page 337 Storage Access 316, 317, 320, 321 storage controller 2 subnet mask 349 subscription expiration date 338 status 338 superuser 118, 123 switch 253 switch ports 252 switchport access 252 sync schedule 58 volume 90 sync schedule configuring 171 conflict 171 status 90 synchronization conflict 171 file name 173 message 171, 172 T taking snapshot 54 terms of service 22, 24 test message 249 text conventions xii Third-Party Licensing Guide xiv time from Active Directory 268 from HTTPS 268 from Network Time Protocol 268 from NTP 268 local time status 40 time server Active Directory server 268 time.nasuni.com 40, 268 time services from domain controllers 279 time.nasuni.com time server 40, 268 traffic group 252, 347, 348 adding 258 configuring 259 deleting 259 editing 259 External 252, 347, 348 firewall policy 295 gateway 260 General 252, 347, 348 Management 252, 347, 348 managing 258 selecting 259 trap SNMP 329 trial mode 5 disaster recover 290, 377 ending 5 expiration 338 maximum volumes 46 upgrading 5 trigger failover 343, 345 trunk access 252 trusted domains Active Directory 272, 279 Nasuni Filer Administration Guide

424 Index U UNIX 57, 136, 138, 149 all_squash 118, 123 CIFS 48 NFS 48 no_root_squash 118, 123 root_squash 118, 123 UNIX client 48 unsynchronized data 4 update password 341 updating software 340 upgrading from trial mode 5 upload Web Access 151 uploading encryption key 289 mobile access 164 SSL certificate 308 UPS battery status 354 status 354 URL Web Access 150 usage metrics 369 user access 105, 106, 111, 112, 118, 123, 130, 131 authenticating 104 domain 316 native 316 permission 209, 315, 318, 323, 324, 325, 326 adding 323, 324, 325 deleting 326 editing 325 user account 30, 336 User Folders Support 107 and directory quota 66, 187 username 20 Active Directory 276, 279 CHAP 49 CIFS migration 202 console 314 creating 382 diagnostics 245 encryption key 78, 80, 82, 292, 293 Filer Administrator 20 for shutdown 27, 341 login 19 network configuration 262, 312 searching for 209 viewing 23 volume deleting 99 disconnect 174 Using Multiple Protocols xiv V vault Cleversafe 56 version and snapshot 10, 88, 176 file 107 mobile access 162 Release Notes 25 version history 4 volume 4 viewing Active Directory domain 274 cache jobs 342 data migration schedule 224 directory FTP 126, 367 FTP directory 126, 367 multiple protocols 134 notifications 24, 372 permission group 316 pinned folder 96 Release Notes 25, 341 share 100 SSL certificate 301 username 23 violation alerts 248 Nasuni Filer Administration Guide

425 Index virtual machine cores per CPU 353 CPU frequency 353 CPU model 353 CPUs 353 RAM 353 status 353 virtual machine status 353 Virtualization Getting Started Guide xiii Virtualization Getting Started Guide for Azure xiii Virtualization Getting Started Guide for EC2 xiii VMware NFS 148 Nasuni Filer Administration Guide

426 Index volume adding 46 data 138 adding CIFS share 101 adding encryption key 81 adding NFS export 117 auditing for 73 Auto Cache 86 browsing 178 CIFS 46 cloud provider 56, 59 creating 46 data adding 138 detail 61 Data Growth chart 34, 61 data migration to 9, 200, 205, 213 default 45 definition 2 deleting 98 password 99 username 99 details 42 disabling remote access 83 disconnect password 174 username 174 enabling remote access 83 snapshot access 92 encryption key 56, 60 disabling 79 enabling 77 export creating 48 information 56, 59 local 42 changing 43 local name for remote volume 53 maximum number 338 metadata 4 name 38, 40, 43, 46, 52, 56, 59, 62, 367 editing 62 setting 46 New Data in Cache 35 NFS 46 pinning in cache 13, 96, 188 properties 56, 59 protocol 43, 44, 52, 57, 60 CIFS 48 iscsi 48 NFS 48 protocols 134, 135 quota 48, 65 setting 11, 48, 65 remote 42, 43, 44, 52 changing 43 renaming 62 restoring folder 192 share 2 creating 48 size 40, 43, 44, 52, 56 snapshot taking 54 status 40 data migration 38 snapshot 38 sync 90 version history 4 Volumes page 45 VPN for mobile access port W warning capacity exceeded 56, 65, 248, 338 definition 371 Web Access branding 109, 150, 330 downloading 154 enable 108 logo 330 settings 109 shared link 109 upload 151 URL 150 Web browsers 2 Wi-Fi mobile access 166 wildcard data migration excluding files 210, 216 wildcard %U 102, 107 Windows 138, 144, 145 client 242 iscsi volume accessing 144, 145 mobile access 236 permissions 139 snapshot access 107, 194 Windows client 48, 284 Windows Explorer 138, 145 Windows Previous Versions 1, 107 Windows workgroup name 278, 283 Nasuni Filer Administration Guide

427 Index wizard setup 378 workgroup name Active Directory domain 274, 282 Nasuni Filer Administration Guide