Nasuni Filer Best Practices Guide

Transcription

1 Nasuni Filer Best Practices Guide Version 5.0 July Nasuni Corporation All Rights Reserved

2 Document Information Nasuni Filer Best Practices Guide Version 5.0 July 2013 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 may 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 may 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 intersecting ovals logo are Nasuni trademarks and service marks. All other names, brands and products herein are the designations 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 viii Audience viii What s in this Book viii Text Conventions ix Product Documentation x Electronic Publications x Chapter 1: Introducing the Nasuni Filer Nasuni Filer Nasuni Management Console (NMC) Key Terms About File Systems About the Cache Cache Capacity Terminology Chapter 2: Installation Installation Record your Nasuni.com Username and Password Planning multiple Nasuni Filers Planning the installation of each Nasuni Filer Platform installation options Logging in to the Nasuni Filer for the first time If you manage multiple Nasuni Filers, also install the Nasuni Management Console (NMC) Chapter 3: Configuration Configuration For each Nasuni Filer that you are configuring, determine the following information 10 For each volume, configure Encryption Keys Nasuni Filer Best Practices Guide 5.0 iii

4 Contents For each Nasuni Filer, configure the Time Zone and the Time Server (Network Time Protocol) For each Nasuni Filer, configure Active Directory security For each volume, configure Quality of Service rules For each Nasuni Filer, configure settings For each Nasuni Filer, configure Automatic Software Updates For each Nasuni Filer, configure Remote Support Service For each Nasuni Filer, verify the default Volume and Share Enabling Browser-based Access to CIFS data on each volume Enabling Mobile Device Access to CIFS data (iphone, ipad, Android phones) on each volume Configuring SMB2 protocol on each volume Configuring for OS X clients on each volume Configuring Snapshot Retention on each volume If this Nasuni Filer is performing data migrations, disable Remote Access for the volume If this Nasuni Filer is performing data migrations, change the snapshot Frequency to 24 hours for the volume If this Nasuni Filer is a primary file server, change the snapshot Frequency to 10 minutes or longer for the volume If this Nasuni Filer is performing data migrations, schedule snapshots of migration data for nights and weekends If this Nasuni Filer is managing backup data, schedule snapshots for once per day at a time of minimal activity Chapter 4: Operations Operations Managing Volumes Managing Shares and Exports Enabling Remote Access Adding data TO the Nasuni Filer Accessing data FROM the Nasuni Filer Resizing the cache (virtual machine) Moving Nasuni Filer to new host Changing device and network parameters (virtual machine) Verifying licensed capacity Updating Nasuni Filer Software Avoiding performance issues Chapter 5: Security Nasuni Filer Best Practices Guide 5.0 iv

5 Contents Security HTTPS proxy server Firewall protection SSL certificates Encryption keys Role-based access control notifications Antivirus protection SNMP monitoring Change password Snapshot directory access Remote access Snapshot retention File Alert Service CIFS authentication CIFS Share security NFS Export security Mobile service settings Mobile licenses Data Migration Service Remote Support Service Chapter 6: Troubleshooting Troubleshooting Gathering information Performance issues Issues sending data to Nasuni Filer Nasuni Filer connectivity issues File access issues Multiple domain Active Directory issues User interface issues Miscellaneous issues Appendix A: Glossary Appendix B: Nasuni Terms of Service and License Agreement Nasuni Corporation Appendix C: Cache Configuration Nasuni Filer Best Practices Guide 5.0 v

6 Contents Cache Configuration About the cache Cache structure Considerations for configuring the cache Recommended cache size Cache disk and copy-on-write (COW) disk (aka snapshot disk) Increasing cache size Cache size and performance Performance issues from cache misses Automatically releasing data from cache Loading large amounts of data into the Nasuni Filer Downloading large amounts of data from cloud Keeping all data locally (cache resident) Proactively managing the contents of the cache Different Nasuni Filers for different uses Different volumes for different uses Cache Specifications Quality of cache storage Actions affecting the cache Removing data from cache Determining if data is in the cache Bringing data into the cache manually Pinning or unpinning CIFS and NFS volumes in the cache Reserving space in cache Snapshots and the cache Scheduling snapshots Manually starting snapshots Changing Quality of Service rules Changing the size of the cache disk or copy-on-write (COW) disk vsphere Client platform Hyper-V Manager platform Appendix D: Network Traffic Network Traffic Considerations Selecting Traffic Groups Creating Traffic Groups Configuring Traffic Groups Configuring System Settings Nasuni Filer Best Practices Guide 5.0 vi

7 Contents Index Nasuni Filer Best Practices Guide 5.0 vii

8 Preface Audience This Best Practices Guide is intended to assist the IT administrator or person responsible for managing unified storage using the Nasuni Filer storage controller. 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, Installation, on page 5 explains how to plan and install the Nasuni Filer and the Nasuni Filer user interface. Chapter 3, Configuration, on page 10 explains how to configure the Nasuni Filer for optimum performance. Chapter 4, Operations, on page 16 explains how to manage the Nasuni Filer during ordinary operations. Chapter 5, Security, on page 24 presents the Nasuni Filer s many security features. Chapter 6, Troubleshooting, on page 29 explains how to solve problems without the necessity of contacting Technical Support. Appendix A, Glossary, on page 36 provides definitions of terms related to the Nasuni Filer. Appendix B, Nasuni Terms of Service and License Agreement, on page 43 is the link to the Nasuni Terms of Service and License Agreement. Appendix C, Cache Configuration, on page 44 gives details about configuring the cache of the Nasuni Filer. Appendix D, Network Traffic, on page 58 gives details about configuring the Nasuni Filer with your network configuration. Nasuni Filer Best Practices Guide 5.0 viii

9 What s in this Book 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. Used to represent options or parameters. Used for hyperlinks, such as links to Web sites. Used to indicate pathnames, filenames, and folders. Nasuni Filer Best Practices Guide 5.0 ix

10 Product Documentation Electronic Publications The latest version of each of the publications listed below is available in PDF format on the Nasuni Web site. All documentation is available at Hardware Getting Started Guide: For setting up the Nasuni Filer on the hardware appliance. To download this guide for the NF 200, visit: pdf To download this guide for the NF 400, visit: pdf Virtualization Getting Started Guide: For installing the Nasuni Filer on a virtual machine within a corporate network. To download this guide, visit: Nasuni_Filer_Virtualization_GS_Guide.pdf Initial Configuration Guide: For configuring and deploying the Nasuni Filer on a corporate network after the initial installation on the hardware appliance or virtual machine. To download this guide, visit: Nasuni_Filer_Initial_Configuration_Guide.pdf Users Guide: For managing unified storage using the Nasuni Filer. To download this guide, visit: Third-Party Licensing Guide: Listing of third-party software used in the Nasuni Filer. To download this guide, visit: Party_Licenses_Guide.pdf 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: x

11 xi

12 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 unified storage device supporting NFS, CIFS, and iscsi 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 filelevel restores. The Nasuni Filer is available as a virtual or physical 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, encrypted, and compressed 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 snapshots. 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 (NMC) The Nasuni Management Console (NMC) 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 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 Best Practices Guide 5.0 1

13 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, or iscsi, and can be mapped as a network drive. Nasuni Filer user interface: The Web-based graphical user interface with which you can 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-based graphical user interface 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, Safari, and Google Chrome. Cloud storage: Cloud-based, highly protected, unlimited storage. Volume: A set of files and directories (CIFS and NFS) 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 or group-level basis. You can create many shares or exports on a volume. 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. 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 specified by your snapshot schedule and at rates specified by your specified quality of service (outgoing bandwidth). You can also manually initiate snapshots. Metadata includes: Standard access control list (ACL) and file system metadata, such as permissions and file size. Version history, including operations such as creating, updating, deleting, and moving. Location of file versions. Volume protocol: CIFS, NFS, or iscsi. Volume encryption settings. 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. Nasuni Filer Best Practices Guide 5.0 2

14 About the Cache Data is versioned with the ability to go back to a point in time at the volume, directory, and file levels. About the Cache It is generally unnecessary to pay attention to the cache s function or configuration. The cache adapts to your usage of data. The following is an overview of how the cache works. When you first launch the Nasuni Filer, the local cache contains no user data. 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 encrypted, compressed, deduplicated, 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 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 local cache automatically. Cache Capacity The cache keeps 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 in the cache or manually changing the cache settings can affect the percentage of the cache that is free to accept new data. Nasuni Filer Best Practices Guide 5.0 3

15 Terminology Terminology The Nasuni Filer documentation uses certain specific terms for the technology involved. Term Description Cache Data Migration Service Network Drive Notifications Quality of Service (QoS) Quota Remote Volume Sync Volume Local data storage. A Nasuni Filer service that migrates data from defined sources to a Nasuni Filer on a specified schedule. A Windows logical drive that maps to a CIFS share. Alerts and messages within the Nasuni Filer interface. The outbound bandwidth limit for moving snapshots from the Nasuni Filer to cloud storage. The maximum capacity of a volume. A volume on another Nasuni Filer on your Nasuni account that has been made accessible. Merging data from other Nasuni Filers with your Nasuni Filer. A set of data accessible by one of the Nasuni Filer's supported protocols. Nasuni Filer Best Practices Guide 5.0 4

16 Chapter 2: Installation Installation Installation includes all tasks necessary to make the Nasuni Filer and the Nasuni Filer user interface operational. All documentation is available at A. Record your Nasuni.com Username and Password Your Nasuni.com Username and Password are required for administering your account. B. Planning multiple Nasuni Filers See for a worksheet for planning configurations. You can set up different Nasuni Filers for different uses, including the following: Performing data migrations: the goal is to migrate data from outside sources to the Nasuni Filer while minimizing the effect on users. Dedicate a specific Nasuni Filer for data migrations. Applications that access the Nasuni Filer directly: the goal is to maximize performance of the application. Applications that directly access the Nasuni Filer open large numbers of files rapidly and frequently. Primary file server: the goal is timely file access for users. Providing mobile access: the goal is timely but secure file access for mobile users. Standby for disaster recovery: the goal is to have files ready for reasonable user access in case the primary server goes down. The performance is expected to not equal the performance of the primary server. Backup: the goal is to preserve copies of files in case the original file is lost or corrupted. Backup consists of two processes: moving data to the Nasuni Filer s cache, and moving data from the Nasuni Filer s cache to the cloud. Dedicate a specific Nasuni Filer for backup. If you have only a single Nasuni Filer, go to step C, Planning the installation of each Nasuni Filer. If you have multiple Nasuni Filers, you must plan the resources necessary for each Nasuni Filer separately. Each Nasuni Filer should have a different name. Then proceed with step C, Planning the installation of each Nasuni Filer for each Nasuni Filer. To simplify managing multiple Nasuni Filers, install the Nasuni Management Console. Nasuni Filer Best Practices Guide 5.0 5

17 Installation C. Planning the installation of each Nasuni Filer For details, see the Nasuni Filer Initial Configuration Guide. 1. Verify minimum memory: 4 GiB (virtual machine) The Nasuni Filer hardware appliance includes 16 GiB (NF-200) or 32 GiB (NF-400) memory. If applications access the Nasuni Filer directly, consider adding more memory. 2. Verify minimum free hard drive space to run the Nasuni Filer: 136 GB (virtual machine) The Nasuni Filer hardware appliance includes 3 TB or 6 TB (NF-200) or 6 TB or 12 TB (NF-400) hard drive space. 3. Verify minimum number of CPU cores: 2 (more than 2 for optimal performance) (virtual machine) The Nasuni Filer hardware appliance includes 6 cores (NF-200) or 12 cores (NF-400). If applications access the Nasuni Filer directly, consider adding more CPU cores. If this Nasuni Filer is performing data migrations, use the most powerful computer available. 4. Verify minimum hard drive space for cache: 64 GB (virtual machine) The Nasuni Filer hardware appliance includes 3 TB or 6 TB (NF-200) or 6 TB or 12 TB (NF-400) hard drive space. It is not necessary for all the data stored in the Nasuni service to be kept in the cache. The size of the cache should be based on the size of the working set (the amount of data being accessed by users or applications on a regular basis), including metadata. See Appendix C, Cache Configuration, on page 44 for details. If this Nasuni Filer is a standby for disaster recovery, the cache should be sufficient to hold the working set of data. If this Nasuni Filer is managing backup data, the cache should be large enough to hold one backup s worth of data. 5. Verify supported virtualization platforms: VMware ESX 4.1, VMware ESXi 4.1 and 5.0, and Windows Server 2008 R2 Hyper-V SP1 (virtual machine) 6. Verify working network connections For details on configuring for network traffic, see Appendix D, Network Traffic, on page 58. (The Nasuni Filer uses bonding mode 5 (balance-tlb) for high-availability (HA) networking. This has no requirements from the switches.) Nasuni Filer Best Practices Guide 5.0 6

18 Installation D. 7. Verify working connection to the Internet The Nasuni Filer must be able to access Nasuni.com and the cloud storage provider. You can run the console application nasunicheck to confirm DNS connectivity for the Nasuni Filer. If this Nasuni Filer is performing data migrations, use the location with the fastest bandwidth available. If this Nasuni Filer is a standby for disaster recovery, the higher the bandwidth, the better. If this Nasuni Filer is managing backup data, the bandwidth should be sufficient to protect one day s worth of data in cloud storage in less than one day. It takes 1 entire day to protect 1 TB of data with a 100 Mbps connection. 8. Verify corporate firewall configured to open port 8443 (required), port 443 (required) and optionally ports 123 (Network Time Protocol), 161 (SNMP monitoring), and 25 (SMTP) for outgoing traffic Platform installation options There are 2 platform options for installation: For a Nasuni Filer hardware appliance, go to step 1, Nasuni Filer hardware appliance (NF-200 or NF-400). For a virtual machine platform, go to step 2, Installation on virtual machine (VMware or Hyper-V). 1. Nasuni Filer hardware appliance (NF-200 or NF-400) See the Nasuni Filer Hardware Deployment Getting Started Guide. The Nasuni Filer software is already installed. If you re using the NF-200, determine or set the initial IP address in one of these ways: If DHCP is available on the network, make note of the IP address that appears on the LCD panel. Otherwise, connect a monitor and keyboard. Press Enter. Use username service and password service. Enter editnetwork. Enter setall static. Enter a new IP address. Enter save. If you re using the NF-400, determine or set the IP address in one of these ways: If DHCP is available on the network, connect a monitor to the VGA port. Alternatively, search network traffic logs for the MAC address. Alternatively, set the MAC address in the DHCP host to force the Nasuni Filer to a known IP address, then restarting. Alternatively, download the Filer Finder tool: account.nasuni.com/account/get-product/ Otherwise, connect a monitor and keyboard. Press Enter. Use username service and password service. Enter editnetwork. Enter setall static. Enter a new IP address. Enter save. Continue with step E, Logging in to the Nasuni Filer for the first time. Nasuni Filer Best Practices Guide 5.0 7

19 Installation E. 2. Installation on virtual machine (VMware or Hyper-V) For detailed installation instructions, see the Nasuni Filer Virtualization Getting Started Guide. When the Nasuni Filer console screen appears, note the initial IP address. Logging in to the Nasuni Filer for the first time Use the Username and Password that you created for administration of this Nasuni Filer. For details, see the Nasuni Filer Initial Configuration Guide. 1. Verify initial login to Nasuni Filer Use the initial IP address with a Web browser: address>:8443 If a warning appears about the site s SSL security certificate, you can ignore it. 2. When the wizard starts, configure settings for your network For details on configuring for network traffic, see Appendix D, Network Traffic, on page Enter the serial number and authorization code for this Nasuni Filer The Filer Serial Number and Authorization code are found under the Account section of For a new installation, choose an unused Filer Serial Number. To recover a prior installation, such as during disaster recovery, choose the Filer Serial Number of the prior installation. 4. Accept the Terms of Service 5. Create a Filer name 6. Create a Username (case-sensitive) and a Password (case-sensitive) for administration of the Nasuni Filer 7. The Nasuni Filer Home page appears 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 rolebased access control system. See For each volume, configure Quality of Service rules on page If migrating a large amount of data to the Nasuni Filer, consider using Nasuni s bulk Data Migration Service See Automated Data Migration to Nasuni Filer on page 20. Nasuni Filer Best Practices Guide 5.0 8

20 Installation F. If you manage multiple Nasuni Filers, also install the Nasuni Management Console (NMC) The Nasuni Management Console allows you to manage multiple Nasuni Filers from one central application. For details, see the Nasuni Management Console Guide. Continue with configuring the Nasuni Filer at Configuration on page 10. Nasuni Filer Best Practices Guide 5.0 9

21 Chapter 3: Configuration Configuration After installation, you can use the Nasuni Filer user interface to configure the Nasuni Filer. You can configure multiple Nasuni Filers with the Nasuni Management Console (NMC). For more details, see the Nasuni Filer Users Guide and the Nasuni Management Console Guide. All documentation is available at A. For each Nasuni Filer that you are configuring, determine the following information See for a worksheet for planning configurations. Filer Description (Name): Network Configuration (for Static) Default Gateway (IP address): Search Domain: Primary DNS server (IP address): Secondary DNS server (IP address): Domain Settings (Security for Active Directory) Full Windows Domain: User Name: Workgroup: Password: Time Configuration Time Zone: Default is US/Eastern. Time Server: Default is time.nasuni.com. Settings: Default is none. Require TLS: Select / Unselect (Default is Unselected.) From name: (Default is blank.) SMTP server: (Default is blank.) SMTP port: (Default is 25.) Login (Optional.): (Default is blank.) Password (Optional.): (Default is blank.) Send to: (Default is blank.) Receive All Alerts: Select / Unselect (Default is Selected.) Tested?: Yes / No Users and Groups: Default groups are Filer Administrators and File Restore. Default user is admin. Groups: Users: Nasuni Filer Best Practices Guide

22 Configuration B. For each volume, configure Encryption Keys 1. Upload your enterprise s encryption keys It is a best practice to upload and use your enterprise s own encryption keys. Protect your encryption keys. If you ever need to perform a disaster recovery procedure, you need your encryption keys. On Nasuni Filer: Click Configuration, then select Encryption Keys. Click Upload Encryption Keys. On NMC: Click Filers, then click Encryption Keys. Click Upload Encryption Keys. 2. Download and protect encryption keys, in case you need them for disaster recovery If you are using automatically-generated encryption keys, download and protect the encryption keys. If you ever need to perform a disaster recovery procedure, you need your encryption keys. Any generated keys are also securely escrowed with Nasuni automatically. On Nasuni Filer: Click Configuration, then select Encryption Keys. Click Download Generated Keys. C. For each Nasuni Filer, configure the Time Zone and the Time Server (Network Time Protocol) D. On Nasuni Filer: Click Configuration, then select Time Configuration. You can also specify using NTP services from domain controllers: Configuration Domain Settings Show Advanced Options. On NMC: Click Filers, then click Time Configuration Settings. Select Nasuni Filers, then click Edit Filers. For each Nasuni Filer, configure Active Directory security If you are using Active Directory for security, configure Active Directory security on each Nasuni Filer. 1. To join a Nasuni Filer to its first Active Directory domain, click Configuration, then select General Settings, then click Join Domain. 2. To join a Nasuni Filer to an Active Directory domain after its first, click Configuration, then select Domain Settings. 3. To leave an Active Directory domain, click Configuration, then select Domain Settings. Nasuni Filer Best Practices Guide

23 Configuration E. For each volume, configure Quality of Service rules Quality of Service is the outgoing bandwidth limit for sending snapshots to Nasuni s cloud storage. The larger the Quality of Service, the faster incoming data is protected in cloud storage and the more cache space is made available for data. You can create up to 12 different rules that specify the Quality of Service on different days and times. 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. If this Nasuni Filer is performing data migrations, set the Quality of Service to the maximum possible. Higher Quality of Service settings might be possible at night or on weekends, when it does not interfere with other activity. If this Nasuni Filer is managing backup data, set the Quality of Service to the maximum possible. Higher Quality of Service settings might be possible at night or on weekends, when it does not interfere with other activity. On Nasuni Filer: Click Configuration, then select Quality of Service. On NMC: Click Filers, then click Quality of Service. Select Nasuni Filers, then click Edit Filers. F. For each Nasuni Filer, configure settings On Nasuni Filer: To receive alerts by , click Configuration, then select Settings. G. For each Nasuni Filer, configure Automatic Software Updates To configure when to install automatic software updates: On Nasuni Filer: Click Configuration, then select Automatic Updates. On NMC: Click Filers, then click Automatic Updates. Select Nasuni Filers, then click Edit Filers. 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. To manually initiate software updates: On Nasuni Filer: Click Status, then select Updates. On NMC: Click Filers, then click Software Updates. Select Nasuni Filers, then click Update Filers. To avoid interface issues, clear your Web browser s cache after updating software. Updating the software disconnects all users currently using the Nasuni Filer. If this Nasuni Filer is a primary file server, configure automatic software updates during times that do not interfere with users. If this Nasuni Filer is a standby for disaster recovery, configure automatic software updates during times that do not interfere with users. Nasuni Filer Best Practices Guide

24 Configuration H. For each Nasuni Filer, configure Remote Support Service The opt-in Remote Support Service allows authorized Nasuni Technical Support personnel to remotely and securely diagnose and resolve issues with your Nasuni Filer. On Nasuni Filer: Click Services, then select Remote Support Service. On NMC: Click Filers, then click Remote Support. Select Nasuni Filers, then click Edit Filers. I. For each Nasuni Filer, verify the default Volume and Share When you install your first Nasuni Filer, a single default volume (named files ) with an associated CIFS shared folder is created. To view the default volume: On Nasuni Filer: Click Volumes and select from the list. On NMC: Click Volumes, then select the volume. To view the default share: On Nasuni Filer: Click Status, then select CIFS Status. On NMC: Click Filers, then click CIFS. To create a new volume, see Creating a volume. To create a new share, see Creating a new share. J. Enabling Browser-based Access to CIFS data on each volume You can access data stored in the Nasuni Filer using a Web browser. The actions you can perform depend on the capabilities of the Web browser. To enable Browser-based Access: On Nasuni Filer: Click Volumes, select the CIFS volume from the list, then click the Total Shares status. Click Edit Share for the share. Select Show Advanced Options, then select the Browser-based access check box. On NMC: Click Volumes, then click Shares. For the selected share, click Edit. K. Enabling Mobile Device Access to CIFS data (iphone, ipad, Android phones) on each volume 1. Enabling mobile access for a share On Nasuni Filer: Click Volumes, select the CIFS volume from the list, then click the Total Shares status. Click Edit Share for the share. Select Show Advanced Options, then select the Mobile Access check box. On NMC: Click Volumes, then click Shares. For the selected share, click Edit. On your mobile device, download and install the appropriate Nasuni app for your platform. Nasuni Filer Best Practices Guide

25 Configuration 2. Enabling, disabling, and deleting mobile devices On Nasuni Filer: Click Services, then select Mobile Licenses. Select devices, then select Enable, Disable, or Delete. On NMC: Click Filers, then click Mobile Licenses. Select Nasuni Filers, then click Enable, Disable, or Delete. 3. Providing initial login links to users To require VPN access, use the internal host name or IP address, and port 443. To provide direct external access, use the external hostname or IP address and port. L. Configuring SMB2 protocol on each volume Nasuni recommends the SMB2 protocol, which can improve performance. On Nasuni Filer: Click Configuration, then select General Settings. Click Show Advanced Options, then, from the Protocol Level drop-down list, select CIFS & SMB2. M. Configuring for OS X clients on each volume N. CIFS shares that have OS X clients should specify the Enhanced Support for POSIX Clients option. On Nasuni Filer: Click Configuration, then select General Settings. Click Show Advanced Options, then select the Enhanced Support for POSIX Clients check box. Configuring Snapshot Retention on each volume For compliance purposes or your own best practices, you can specify to delete older snapshots from cloud storage. When a snapshot is removed, it is permanently deleted from cloud storage and cannot be recovered. On Nasuni Filer: Click Volumes, then select the volume from the list. Click the Snapshot Retention status. On NMC: Click Volumes, then click Snapshot Retention. For the selected volumes, click Edit Volumes. O. If this Nasuni Filer is performing data migrations, disable Remote Access for the volume Disabling Remote Access reduces processing. On Nasuni Filer: Click Volumes, then select the volume from the list. Click the Remote Access setting. On NMC: Click Volumes, then click Remote Access. For the selected volumes, click Edit Volumes. Nasuni Filer Best Practices Guide

26 Configuration P. If this Nasuni Filer is performing data migrations, change the snapshot Frequency to 24 hours for the volume The strategy is to fill the cache as much as possible and as fast as possible without doing snapshot processing, then perform a snapshot with a full cache. On Nasuni Filer: Click Volumes, then select the volume from the list. Click the Snapshot Schedule setting. On NMC: Click Volumes, then click Snapshot Schedule. For the selected volumes, click Edit Volumes. Q. If this Nasuni Filer is a primary file server, change the snapshot Frequency to 10 minutes or longer for the volume Snapshots can cause performance issues. On Nasuni Filer: Click Volumes, then select the volume from the list. Click the Snapshot Schedule setting. On NMC: Click Volumes, then click Snapshot Schedule. For the selected volumes, click Edit Volumes. R. If this Nasuni Filer is performing data migrations, schedule snapshots of migration data for nights and weekends Otherwise, snapshots of migration data might delay snapshots of other volumes. On Nasuni Filer: Click Volumes, then select the volume from the list. Click the Snapshot Schedule setting. On NMC: Click Volumes, then click Snapshot Schedule. For the selected volumes, click Edit Volumes. S. If this Nasuni Filer is managing backup data, schedule snapshots for once per day at a time of minimal activity On Nasuni Filer: Click Volumes, then select the volume from the list. Click the Snapshot Schedule setting. On NMC: Click Volumes, then click Snapshot Schedule. For the selected volumes, click Edit Volumes. Nasuni Filer Best Practices Guide

27 Chapter 4: Operations Operations This section includes ongoing operations tasks you can perform using the Nasuni Filer user interface. You can manage multiple Nasuni Filers with the Nasuni Management Console (NMC). For more details on any of these topics, see the Nasuni Filer Users Guide and the Nasuni Management Console Guide. All documentation is available at A. Managing Volumes 1. Connecting to a remote volume On Nasuni Filer: Click Volumes. Click Connect to Remote Volume. Select a remote volume to connect to. On NMC: Click Volumes, then click Connect Volume. For the selected share, click Edit Connections. 2. Planning a volume See for a worksheet for planning configurations. Determine the following information to plan the features of a volume: Initial Setup (Volumes --> Add New Volume) Any time (Volumes --> select volume --> Edit Properties) Volume Name: (Can change later.) Region: Location-specific options. (Cannot change later.) Encryption Key: Default is Create New Key. (Can add and select different key later.) Volume Pinned: Default is Disabled. Enabled / Disabled Snapshot Directory Access: Default is Disabled. Enabled / Disabled Remote Access: Default is Disabled. Enabled / Disabled Nasuni Filer Best Practices Guide

28 Operations Initial Setup (Volumes --> Add New Volume) Network Protocol: Default is CIFS. CIFS / NFS / iscsi (For CIFS) Authentication mode: Active Directory/ Public (Cannot change later.) Quota (GB): Default is unlimited capacity, up to the licensed capacity. (Can change later.) Create a default Share/Export: Default is Yes. Select / Unselect (Can create shares or exports later.) Settings below for iscsi protocol only. iscsi Volume Size (GB): Maximum is 75 percent of cache size. (Cannot change later.) iscsi Allowed Hosts: Default is all hosts. (Can change later.) iscsi CHAP User Name and Password: Default is none. User Name: Password: Any time (Volumes --> select volume --> Edit Properties) Sync Schedule: Default is daily at midnight every 5 minutes. Days: Sun Mon Tue Wed Thur Fri Sat Start time: Stop time: Frequency: Auto Cache: Default is Disabled. Enabled / Disabled Snapshot Schedule: Default is daily at midnight every 5 minutes. Days: Sun Mon Tue Wed Thur Fri Sat Start time: Stop time: Frequency: Snapshot Retention: Default is All Snapshots. all snapshots / a set number of snapshots / snapshots within a given time File Alert Service: Default is Disabled. Enabled / Disabled Patterns: Antivirus Service: Default is Disabled. Enabled / Disabled Antivirus Violations: Ignore / Delete (Can change later.) On Nasuni Filer: To configure directory-specific quota notifications, click Versions, select a directory, then click Quota. Nasuni Filer Best Practices Guide

29 Operations 3. Creating a volume On Nasuni Filer: Click Volumes, then click Add New Volume. On NMC: Click Volumes, then click Create Volume. After you create a volume, download and save encryption keys: On Nasuni Filer: Click Configuration, then click Encryption Keys, then click Download Generated Keys. In trial mode, the maximum number of volumes you can have is limited to two. If applications access the Nasuni Filer directly, create an application-specific volume. If this Nasuni Filer is a standby for disaster recovery, create a shared volume that connects to the primary volume. Enable Remote Access for the primary volume, with Read-Write access for the standby Nasuni Filer. Scheduling syncs with a frequent Frequency helps to ensure that data is up to date. Enabling Auto Cache helps to ensure that data is up to date. You can schedule snapshots with an infrequent Frequency, because the standby is not responsible for ensuring that snapshots occur. Nasuni Filer Best Practices Guide

30 Operations B. Managing Shares and Exports You can create multiple CIFS shares or NFS exports for each volume. Each share or export can have different properties and permissions for different purposes and users. 1. Planning a CIFS share See for a worksheet for planning configurations. Determine the following information to plan CIFS shares: Values (Volumes -->select volume --> Total Shares --> Edit Share) Folder: Name: Share Visible?: Select / Unselect (Default is Selected.) Share Read-Only?: Select / Unselect (Default is Unselected.) All settings below are on the Advanced tab: Allowed Hosts: (Default is all.) Authentication (Active Directory security only): Authenticate all Users / Authenticate only specified Groups and Users (Default is Authenticate all Users.) Hide Unreadable Files: Select / Unselect (Default is Selected.) Enable Previous Versions: Select / Unselect (Default is Selected.) Case-Sensitive Paths: Select / Unselect (Default is Selected.) Enable Snapshot Directories: Select / Unselect (Default is Unselected.) User Folders Support (Active Directory security only): Disabled / Enabled (Default is Disabled.) Support Folder Change Notifications (Active Directory security only): Select / Unselect (Default is Selected.) Mobile Access: Select / Unselect (Default is Unselected.) Browser-based Access: Select / Unselect (Default is Unselected.) Nasuni Filer Best Practices Guide

31 Operations C. D. 2. Creating a new share On Nasuni Filer: Click Volumes, select a CIFS volume from the list, then click the Total Shares status. Click Add New Share. On NMC: Click Volumes, then click Shares, then click Create Share. If applications access the Nasuni Filer directly, create an application-specific share. If this Nasuni Filer provides mobile access, create shares specifically for mobile access. Enable Mobile Access. Also, select Read-Only access. Define which specific users or groups have access to each share. Some applications need Case-Sensitive Paths disabled in order to successfully access files. However, disabling Case-Sensitive Paths can cause performance issues. Some applications need Allocation Roundup Size disabled. However, disabling Allocation Roundup Size can cause performance issues. 3. Creating NFS exports On Nasuni Filer: Click Volumes, select an NFS volume from the list, then click the Total Exports status. Click Add New Export. On NMC: Click Volumes, then click Exports, then click Create Export. Enabling Remote Access To enable access to a volume by remote offices attached to your Nasuni.com account: On Nasuni Filer: Click Volumes, select a volume from the list, then click the Remote Access status. On NMC: Click Volumes, then click Remote Access. For the selected volumes, click Edit Volumes. If this Nasuni Filer is performing data migrations, disable Remote Access for the volume. Disabling Remote Access reduces processing. Adding data TO the Nasuni Filer For details, see Appendix C, Cache Configuration, on page 44. If migrating a large amount of data to the Nasuni Filer, consider using Nasuni s bulk data migration service. 1. Automated Data Migration to Nasuni Filer You can use the Data Migration Service to copy data to the Nasuni Filer. a. Specify a data migration source On Nasuni Filer: Click Services, then select Migration Sources from the list. Add a CIFS or NFS migration source. Nasuni Filer Best Practices Guide

32 Operations b. Define a data migration On Nasuni Filer: After configuring at least one migration source, click Services, then select Add Migration. Nasuni recommends migrating to an unshared or unexported portion of a volume, so users are not accessing or changing data during data migration into that portion of the volume. 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. c. Schedule a data migration On Nasuni Filer: After configuring at least one data migration, click Services, then select View Migrations. Select a migration, then click Schedule. 2. Copying data from local or network drives to Nasuni Filer In Windows, you can map volumes on the Nasuni Filer to network drives, then copy data to the mapped drives. In Linux or UNIX, you can use command line instructions to navigate to mounted volumes on the Nasuni Filer, then copy data to the volume. 3. Browser-based Access Using Browser-based Access, you can drag and drop data to the Nasuni Filer with some Web browsers. (Internet Explorer does not currently support this feature.) To enable Browser-based Access, see Enabling Browser-based Access to CIFS data on each volume on page 13. If you use this URL to access your Nasuni Filer: then the URL of the Browser-based Access page is: 4. Mobile Access Using Mobile Access, you can upload data to the Nasuni Filer. To enable Mobile Access, see Enabling Mobile Device Access to CIFS data (iphone, ipad, Android phones) on each volume on page 13. See for a worksheet for planning configurations. E. Accessing data FROM the Nasuni Filer 1. Copying data from Nasuni Filer to local or network drives See Copying data from local or network drives to Nasuni Filer on page 21. Nasuni Filer Best Practices Guide

33 Operations 2. Browser-based Access Using Browser-based Access, you can drag and drop data from the Nasuni Filer with some Web browsers. (Internet Explorer does not currently support this feature.) See Browser-based Access on page Mobile Access Using Mobile Access, you can download data from the Nasuni Filer. See Mobile Access on page 21. F. G. Resizing the cache (virtual machine) For details on resizing the cache, see the Nasuni Filer Virtualization Getting Started Guide. Moving Nasuni Filer to new host H. 1. Download and protect all encryption keys before shutting down Nasuni Filer 2. Perform snapshots on all volumes before shutting down Nasuni Filer 3. Disaster Recovery procedure is available for use on the new host, if necessary 4. Verify network and Internet connectivity after moving the Nasuni Filer Changing device and network parameters (virtual machine) You can use console commands to change network parameters such as the static IP address, netmask, MTU, host name, default gateway, DNS servers, and search domains. You can also view the MAC address, or enable static or DHCP networking. For details, see the Nasuni Filer Initial Configuration Guide. I. J. Verifying licensed capacity On Nasuni Filer: Click Status, then select Subscription Status. On NMC: Licensed capacity appears on the Home page. Click the Nasuni logo. Updating Nasuni Filer Software You can configure the Nasuni Filer to update software automatically. On Nasuni Filer: Click Configuration, then select Automatic Updates. On NMC: Click Filers, then click Automatic Updates. Select Nasuni Filers, then click Edit Filers. Nasuni Filer Best Practices Guide

34 Operations K. Alternatively, you can update software manually. On Nasuni Filer: Click Status, then select Updates. On NMC: Click Filers, then click Software Updates. Select Nasuni Filers, then click Edit Filers. To avoid user interface issues when updates occur, clear your Web browser s cache. Because updating the software disconnects all users currently using the Nasuni Filer, you should choose a date and time that will minimize interruptions. When updates occur, review the release notes for the update. If this Nasuni Filer is a primary file server, configure automatic software updates during times that do not interfere with users. Avoiding performance issues In Windows, disable the Windows Explorer Preview Pane. Using Preview Pane can cause performance issues. Nasuni Filer Best Practices Guide

35 Chapter 5: Security Security The Nasuni Filer includes a number of security features that you can configure. For more details on any of these topics, see the Nasuni Filer Users Guide. All documentation is available at A. B. C. D. HTTPS proxy server You can configure the Nasuni Filer to use a proxy server. All HTTPS traffic goes through the proxy server that you specify. A valid User Name and Password are required. On Nasuni Filer: Click Configuration, then select HTTPS Proxy from the list. Firewall protection You can specify which network hosts are allowed to connect to the Nasuni Filer user interface and the Nasuni Support SSH port. You can also specify firewall limits for individual traffic groups. On Nasuni Filer: Click Configuration, then select Firewall from the list. SSL certificates You use SSL Certificates when accessing the Nasuni Filer's Web-based user interface. You can generate a Certificate Request. You can add signed certificates. You can also create a selfsigned certificate instead of a certificate request. On Nasuni Filer: Click Configuration, then select SSL Certificates from the list. Encryption keys The Nasuni Filer automatically encrypts your data at your premises using your encryption keys that you control. You can upload your encryption keys to use. You can generate keys to use, and then download them for safekeeping. You can also escrow your encryption keys with Nasuni. You can enable and disable encryption keys. On Nasuni Filer: Click Configuration, then select Security/Encryption from the list. On NMC: Click Filers, then click Encryption Keys. Nasuni Filer Best Practices Guide

36 Security E. Role-based access control You can define specific access permissions for groups and users to perform actions within the Nasuni Filer user interface. On Nasuni Filer: Click Configuration, then select Users/Groups from the drop-down list. F. notifications You can configure receiving notifications when certain conditions occur on the Nasuni Filer. On Nasuni Filer: Click Configuration, then select Settings from the list. On Nasuni Filer: To configure directory-specific quota notifications, click Versions, select a directory, then click Quota. G. Antivirus protection H. You can enable or disable antivirus protection for CIFS and NFS volumes. The Antivirus Service scans every new or modified file for the presence of viruses and other malware. On Nasuni Filer: Click Volumes, then select the volume from the menu. Click the Antivirus Service status. On NMC: Click Volumes, then click Antivirus Service. For the selected volumes, click Edit Volumes. SNMP monitoring You can configure monitoring of the Nasuni Filer via the Simple Network Management Protocol (SNMP). On Nasuni Filer: Click Configuration, then select SNMP Monitoring from the list. On NMC: Click Filers, then click SNMP Settings. Select Nasuni Filers, then click Edit Filers. I. J. Change password You can change the user password. On Nasuni Filer: Click Configuration, then select Change Password from the list. Snapshot directory access You can enable or disable access to the directory that holds snapshot data. On Nasuni Filer: Click Volumes, then select the volume from the menu. Click the Snapshot Directory Access status. On NMC: Click Volumes, then click Snapshot Access. For the selected volumes, click Edit Volumes. Nasuni Filer Best Practices Guide

37 Security K. Remote access You can enable or disable access to a volume by your remote offices attached to your Nasuni.com account. On Nasuni Filer: Click Volumes, then select the volume from the menu. Click the Remote Access status. On NMC: Click Volumes, then click Remote Access. For the selected volumes, click Edit Volumes. L. Snapshot retention 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. On Nasuni Filer: Click Volumes, then select the volume from the menu. Click the Snapshot Retention status. On NMC: Click Volumes, then click Snapshot Retention. For the selected volumes, click Edit Volumes. M. File Alert Service N. For compliance and other purposes, you can receive alerts (no more than one per day) when files and directories whose names match patterns you specify are written to the Nasuni Filer. On Nasuni Filer: Click Volumes, then select the volume from the menu. Click the File Alert Service status. On NMC: Click Volumes, then click File Alert Service. For the selected volumes, click Edit Volumes. CIFS authentication When you create a CIFS volume, you can select either Public security or Active Directory authentication for the volume. You cannot change the authentication mode after the volume is created. O. CIFS Share security You can configure a number of security features of CIFS shares. On Nasuni Filer: Click Volumes, then select the CIFS volume from the menu. Select CIFS Shares from the Properties drop-down list. For the CIFS share that you want to edit, click Edit Share. On NMC: Click Volumes, then click Shares. For the selected share, click Edit. 1. Visible Share You can enable whether a share is visible when browsing the Nasuni Filer. Nasuni Filer Best Practices Guide

38 Security P. 2. Read Only Share You can select that a share be read-only, so that users cannot change the contents of the share. 3. Allowed Hosts You can specify which hosts are allowed to access the share. 4. Hide Unreadable Files You can specify that files and folders that the user cannot access do not appear in folder listings. 5. Mobile Access You can enable or disable access to data by mobile devices. 6. Browser-based Access You can enable or disable access to data via Web browsers. 7. Authentication (Active Directory only) If Active Directory security is chosen, you can select whether to authenticate all users, or to authenticate only the groups and users that you explicitly specify. NFS Export security You can configure a number of security features of NFS exports. On Nasuni Filer: Click Volumes, then select the NFS volume from the menu. Select NFS Exports from the Properties drop-down list. For the NFS export that you want to edit, click Edit Export. On NMC: Click Volumes, then click Exports. For the selected export, click Edit. 1. Read Only You can select that an export be read-only, so that users cannot change the contents of the export. 2. Allowed Hosts You can specify which hosts are allowed to access the export. Nasuni Filer Best Practices Guide

39 Security Q. Mobile service settings You can configure a number of security features of Mobile Access. On Nasuni Filer: Click Services, then select Mobile Service Settings from the list. On NMC: Click Filers, then click Mobile Settings. Select Nasuni Filers, then click Edit Filers. R. 1. Session Expiration You can limit how long users can use Mobile Access before reauthenticating. 2. Limit to a single device You can limit users to using a single mobile device. 3. Allowed Devices You can specify which devices to permit Mobile Access on. Mobile licenses You can enable, disable, or delete licenses for Mobile Access. On Nasuni Filer: Click Services, then select Mobile Licenses from the list. On NMC: Click Filers, then click Mobile Licenses. Select Nasuni Filers, then click Enable, Disable, or Delete. S. Data Migration Service You can configure a number of security features of the Data Migration Service. On Nasuni Filer: Click Services, then select View Migrations from the list. 1. File permissions You can specify how to handle existing permissions of copied files, including creating customized permissions rules. 2. Password retention You can select whether or not to retain passwords for automatic reconnection. T. Remote Support Service You can enable or disable remote access to your Nasuni Filer by Nasuni support personnel. On Nasuni Filer: Click Services, then select Remote Support Service from the list. On NMC: Click Filers, then click Remote Support. Select Nasuni Filers, then click Edit Filers. Nasuni Filer Best Practices Guide

40 Chapter 6: Troubleshooting Troubleshooting The purpose of this section is to present information that can help should problems occur. All documentation is available at A. Gathering information The Nasuni Filer provides many sources of information that are useful for diagnosing and solving problems. 1. Pop-up notifications are active messages that appear in the right margin, based on the state of your system Pop-up notifications include messages about disconnected migration sources, recommended hardware resources, and number of notifications. You can check any or all messages on the Notifications page. 2. The Notifications page lets you view and acknowledge Nasuni Filer messages Notifications are searchable and sortable. Informational messages describe system actions or states that do not require action or attention. Warnings describe unusual events that do not require action. Errors describe unusual or incorrect situations that the user should notice and act to resolve. Alerts describe unusual or incorrect situations that the user must act to resolve. On Nasuni Filer: Click Notifications, then click All Messages. On NMC: Click Notifications, then enter the name of the Nasuni Filer in the Filter text box and click Apply Filter. If the user has set up , alerts generate s to the user. See For each Nasuni Filer, configure settings on page Information is available on Network status, CIFS share status, NFS export status, iscsi volume status, subscription status, and software update status On Nasuni Filer: Click Status, then click Subscription Status, Updates, Network Status, CIFS Status, NFS Status, iscsi Status, or File Heuristics Updates to view information. On NMC: Click Filers, then click Network, CIFS, NFS, iscsi, or Software Updates to view comparable information. To view subscription status, click Account Status. Nasuni Filer Best Practices Guide

41 Troubleshooting 4. Information on migrations is available On Nasuni Filer: Click Services, then View Migrations. On NMC: Click Filers, then click Migrations. 5. Information on volumes, including remote access, snapshots, data in cache, pinned volumes, and synchronizations, is available On Nasuni Filer: Click Volumes, then select the specific volume On NMC: Click Volumes, then click Remote Access, Snapshot Schedule, Pinning, or Sync Schedule to view comparable information. 6. Information on files and folders, including whether they are present in the cache and whether they are protected in the cloud, is available On Nasuni Filer: Click Versions, then select the specific file or folder B. Performance issues Performance issues are related to many conditions. 1. Observe how often performance issues occur The frequency daily, hourly, weekly and specific times of performance issues when users begin work, when backups begin might suggest causes. 2. Are the performance issues reproducible at will? If specific activity user access, migrating data causes performance issues, that suggests possible causes. 3. Observe any symptoms associated with performance issues Specific symptoms slow application performance, delays opening files might suggest possible causes. 4. Do applications access the Nasuni Filer directly? Because applications can access large amounts of data rapidly and frequently, application access can be more resource-intensive than user access. In particular, applications that poll the Nasuni Filer continually for metadata, such as document management systems, can cause large amounts of cloud access. 5. Do you access the Nasuni Filer remotely? VPNs can slow down or block access to the Nasuni Filer. 6. Monitor actual resource utilization Nasuni Filer Best Practices Guide

42 Troubleshooting 7. If using Nasuni Filer hardware appliance NF-200 or NF-400, check status of hard drives 8. Verify supported virtualization platforms: VMware ESX 4.1, VMware ESXi 4.1 and 5.0, and Windows Server 2008 R2 Hyper-V SP1 (virtual machine) 9. Verify thin or thick provisioning (virtual machine) With thin provisioning, resources must be allocated on the fly, which can affect performance. 10.Verify minimum memory: 4 GiB (more for heavy loads) (virtual machine) 11.Verify minimum number of CPU cores: 2 (more than 2 for optimal performance) (virtual machine) 12.Verify that server is running properly (virtual machine) 13.With a virtual machine, are other virtual machines running and competing for resources? If other virtual machines are contending for resources, this can affect performance. 14.Verify the type of data store Different data stores local, iscsi, various RAID types offer different performance. 15.Verify write-back cache enabled A write-back cache can improve performance. A write-back cache is a feature of some RAID controllers. 16.Does the performance issue occur during snapshots? There might be a system load issue related to processing snapshots. You can see if a snapshot is in progress by examining the Snapshot Status on the home page. 17.Does the performance issue occur while data is being obtained from cloud storage (faulting)? If data must be obtained from cloud storage, there might be an issue processing access to cloud storage. On Nasuni Filer: Click Versions, then navigate to a specific file or folder and examine its Cache Resident status. To bring a specific file or folder into the cache, click Bring into Cache. Nasuni Filer Best Practices Guide

43 Troubleshooting 18.When and how frequently does syncing occur for a volume? Syncing merges data from other Nasuni Filers to this volume. While this helps to ensure that everyone in your organization is using the most current data, syncs increase the processing load. On Nasuni Filer: Click Volumes, select the volume, then examine the Sync Schedule. On NMC: Click Volumes, then click Sync Schedule. 19.Is Auto Cache enabled for a volume? If Auto Cache is enabled for a volume, there might be an issue processing syncs. On Nasuni Filer: Click Volumes, select the volume, then examine the Auto Cache status. On NMC: Click Volumes, then click Sync Schedule. 20.Is Previous Versions enabled for a CIFS share? If Previous Versions is enabled for a share, there might be an issue processing access to cloud storage. On Nasuni Filer: Click Status, then select CIFS Status. Select the share, click Show Advanced Options, then examine Enable Previous Versions status. On NMC: Click Volumes, then click Shares. For the selected share, click Edit. 21.Are users searching snapshots? Searching snapshots requires accessing large amounts of data from cloud storage. 22.Is the Antivirus Service enabled for volumes? The Antivirus Service adds a processing load. On Nasuni Filer: Click Volumes, select the volume, then examine the Antivirus Service status. On NMC: Click Volumes, then click Antivirus Service. For the selected volumes, click Edit Volumes. 23.Is snapshot retention not equal to all snapshots for a volume? If snapshot retention is set to a set number of snapshots or snapshots within a given time, then processing is necessary to prune unwanted snapshots. On Nasuni Filer: Click Volumes, select the volume, then examine the Snapshot Retention status. On NMC: Click Volumes, then click Snapshot Retention. For the selected volumes, click Edit Volumes. Nasuni Filer Best Practices Guide

44 Troubleshooting 24.Is snapshot directory access enabled? Snapshot directory access can add a significant load to the Nasuni Filer. On Nasuni Filer: Click Volumes, select the volume, then examine the Snapshot Directory Access status. On NMC: Click Volumes, then click Snapshot Access. For the selected volumes, click Edit Volumes. 25.Is a volume deletion in progress? When you delete a volume, the data in that volume must be processed and removed. For large volumes, this can take a considerable amount of time. 26.Is Case-Sensitive Paths enabled for a CIFS share? Using case-sensitive paths improves performance. However, some links and applications might not work if Case-Sensitive Paths is enabled for a share. On Nasuni Filer: Click Status, then select CIFS Status. Select the share, click Show Advanced Options, then examine Case-Sensitive Paths status. On NMC: Click Volumes, then click Shares. For the selected share, click Edit. 27.Examine Quality of Service rules The larger the Quality of Service, the faster incoming data is protected in cloud storage and the more cache space is made available for data. This is especially important if snapshots are taking too long. On Nasuni Filer: Click Configuration, then select Quality of Service. On NMC: Click Filers, then click Quality of Service. Select Nasuni Filers, then click Edit Filers. 28.Is Remote Access enabled for this volume? Enabling Remote Access adds a processing load. On Nasuni Filer: Click Volumes, select the volume, then examine the Remote Access status. On NMC: Click Volumes, then click Remote Access. For the selected volumes, click Edit Volumes. 29.Snapshots, syncs, and data migrations interfere with other processing When snapshots, syncs, and data migrations run, they add a processing load. On Nasuni Filer: Click Volumes, select the volume, then examine the Snapshot and Sync statuses. Click Services, then View Migrations to view data migrations. On NMC: Click Volumes, then click Snapshot Schedule or Sync Schedule. Click Filers, then click Migrations. Nasuni Filer Best Practices Guide

45 Troubleshooting 30.Do you use offline files? If you use offline files, the synchronization that is necessary when connected adds a processing load. 31.Do you use roaming profiles? If you use roaming profiles, bringing the user profile files to the user machine adds a processing load. 32.On Macs, different file views have different performance characteristics C. Issues sending data to Nasuni Filer 1. Nasuni Filer not accepting new data Increase the Quality of Service, especially during times with few users: this allows the Nasuni Filer to protect data in cloud storage, then remove protected data from the cache. Increase the size of the cache. Use the Data Migration Service to copy data to the Nasuni Filer. 2. Multiple migrations don t seem to be running Only one migration runs at a time. Try scheduling migrations for different times. D. Nasuni Filer connectivity issues 1. If you move the Nasuni Filer, verify network and Internet connectivity 2. Verify that server is running properly 3. To reconfigure the network if the Nasuni Filer user interface is not available, you can access network settings using the service menu on the console E. File access issues 1. Users cannot view files Verify that Active Directory users and groups are set up correctly to permit all necessary users to access. 2. Verify that server is running properly Nasuni Filer Best Practices Guide

46 Troubleshooting 3. On Windows clients, files appear locked even when no one is working on them Do not highlight the file name. Do not hover the mouse over the file name so that pop-up file information appears. Disable the Preview Pane in Windows Explorer. 4. Browser-based Access does not work with Internet Explorer Internet Explorer does not currently support this feature. 5. Shares are hidden Ensure that names of shares do not end with the $ character, which makes the shares hidden for Windows clients. In addition, check the setting for Visible Shares, which controls if the share is visible for all client operating systems, regardless of the name of the share. F. G. Multiple domain Active Directory issues You can join and leave multiple Active Directory domains using Domain Settings on the Configuration menu. If issues arise, contact Nasuni Technical Support for assistance. User interface issues 1. Elements grayed out, or long time loading page or elements Verify that Internet Explorer is not in compatibility mode. Verify that the Web browser s security settings are not set on High. 2. If something ever goes wrong with SSL certificates and you are unable to access the Nasuni Filer user interface, use the service menu console to reset the certificate to the default self-signed certificate H. Miscellaneous issues 1. Active Directory connection message in the Nasuni Filer user interface On Nasuni Filer: Click Configuration, then select Domain Settings. Click Update Domains or refresh the page. This forces the test to run again, and the warning often disappears. Nasuni Filer Best Practices Guide

47 Appendix A: 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. C cache A cache is a computer component that stores data 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 36. Nasuni Filer Best Practices Guide

48 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. 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. Nasuni Filer Best Practices Guide

49 F file system A method for storing and organizing computer files and the data they contain to make it easy to find and access them. G GB/GiB GB is an abbreviation of gigabyte, meaning 1,000,000,000 bytes. GiB is an abbreviation of gibibyte, meaning 2 30 (1,073,741,824) bytes. 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 38. iscsi (Internet Small Computer System Interface) See Internet Small Computer System Interface (iscsi) on page 38. iscsi Qualified Name (IQN) The iscsi Qualified Name includes these fields: 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. Nasuni Filer Best Practices Guide

50 M MB/MiB MB is an abbreviation of megabyte, meaning 1,000,000 bytes. MiB is an abbreviation of mebibyte, meaning 2 20 (1,048,576) bytes. 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 above 1500 are supported. N NAS (Network Attached Storage) See Network Attached Storage (NAS) on page 40. 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 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 Nasuni Filer Best Practices Guide

51 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. 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 39. 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 proxy A server that acts as an intermediary for requests from clients seeking resources from other servers. Q quota A limit on the amount of usable storage space on a volume. Nasuni Filer Best Practices Guide

52 S SAN (Storage Area Network) See Storage Area Network (SAN) on page 41. 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. V versioning The Nasuni Filer provides the versioning necessary to eliminate the need for separate backup and restore procedures. Nasuni Filer Best Practices Guide

53 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 Best Practices Guide

54 Appendix B: 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 Best Practices Guide

55 Appendix C: Cache Configuration Cache Configuration The cache is the local storage of the Nasuni Filer. Proper configuration of the cache and related features helps provide the following benefits: Enables access to data. Improves the performance experience of users and applications. Ensures access to data during Internet outages. Reduces use of network bandwidth. This document offers suggestions for configuring the cache of the Nasuni Filer. About the cache The cache is the local storage of the Nasuni Filer. All data and metadata that is accessed regularly is kept locally in the cache ( cache resident ). If requested data is not cache resident, the system accesses the requested data from cloud storage, the data is staged into the cache, and provided for the request. Note: You don t have to keep all data locally. The Nasuni Filer is extremely efficient at keeping only your most-needed data locally, and retrieving data from cloud storage as needed. A cache about 20 percent of your total data size is usually sufficient. The size and status of the cache are displayed on the Home page. Figure C-1: Local Storage Status (cache). Any data written to a volume is first staged in the local cache. The first snapshot preserves each data item from the cache in Nasuni s cloud storage. Subsequent snapshots include only the changes between the original version of the data and the most recent version of the data. Nasuni Filer Best Practices Guide

56 About the cache The cache continuously tracks recently changed data, such as data created or changed since the last snapshot. New data that has been saved to the cache, but that has not yet been preserved in Nasuni s cloud storage, is classified as new data in cache not yet protected. A chart of New Data in Cache (Not yet protected) appears on the Home page. Figure C-2: New Data in Cache chart. The most recently used data remains in the cache, including data, metadata, complete files, or parts of files. Saved data that was written once and rarely used afterwards is eventually released (or evicted ) from the cache to free up space for new data. If any of this released data is later requested for reads or writes, the Nasuni Filer retrieves the data from Nasuni s cloud storage and puts it back into the local cache automatically. Nasuni Filer Best Practices Guide

57 Cache structure Cache structure This figure illustrates the structure of the cache: Figure C-3: Cache structure. The data of pinned volumes is not removed from the cache. If too much cache space is taken up by pinned volumes, an Alert notification is given. iscsi volumes are always pinned in the cache. The total size of all iscsi volumes together can use up to 75 percent of the cache. Reserved space is space set aside in the cache for incoming data. By default, the Nasuni Filer automatically manages the reserved space. The maximum amount of reserved space is 90 percent of the cache size. Snapshots preserve data from the cache in Nasuni s cloud storage. You can configure the frequency of snapshots. The Quality of Service is the limit on bandwidth for snapshots. The value appears on the Home page. Figure C-4: Quality of Service. Nasuni Filer Best Practices Guide

58 Considerations for configuring the cache Considerations for configuring the cache This section discusses points to consider when configuring the cache. Recommended cache size The size of the cache should be based on the size of the working set (the amount of data being accessed by users or applications on a regular basis), including metadata. To help you estimate the size of your working set and your cache, note that Nasuni observes that: The working set is typically 20 percent of the total data set. Generally, the cache should be at least 1.4 times as large as the working set. If performance is paramount, then the cache should be at least 2 times as large as the working set. This way, you will have a buffer zone for data growth before data is removed from the cache. Note: Cache size is independent of licensing. Cache disk and copy-on-write (COW) disk (aka snapshot disk) The size of the copy-on-write (COW) disk is determined by how much data can change while a snapshot is running. For example, a heavily used file server, where a lot of data can change while a snapshot is running, might need a larger copy-on-write (COW) disk than a server used mainly for backups, where the snapshot is scheduled for a time when the backup isn't running. However, if the copy-on-write (COW) disk is too small, then a snapshot might fail, then try again. The snapshot will eventually succeed, but this is very inefficient. Generally, the copy-on-write (COW) disk should be less than one-quarter the size of the cache disk, and no larger than 250 GiB. Increasing cache size For an existing Nasuni Filer, you can only increase the size of the cache and copy-on-write (COW) disks (snapshot disks). This means that you cannot decrease a value once you have increased it. Therefore, make sure you understand your resizing requirements before you make changes. Note: If necessary, you can create a new Nasuni Filer with a smaller cache size, then perform a Disaster Recovery from the existing Nasuni Filer to the new Nasuni Filer. Cache size and performance With a larger cache, more data can be cache resident, and access to that data is faster. On a hardware appliance, more RAM and CPUs also improve performance. Similarly, on a virtual machine, increased physical resources also improve performance. Nasuni Filer Best Practices Guide

59 Considerations for configuring the cache Performance issues from cache misses To determine whether performance issues are caused by cache misses, find out which specific files are having problems. Then see if those files are cache resident, by clicking versions, selecting the volume, navigating to each file, and examining its properties in the Properties pane. If the Cache Resident status is Yes, then the file is cache resident. If all other investigation fails to solve performance issues, contact Nasuni Technical Support to analyze the logs to see if a lot of cache misses are happening. Automatically releasing data from cache If the amount of cache resident data exceeds a specified percentage of the size of the cache, data is released from the cache until the amount of cache resident data no longer exceeds that specified percentage. Before releasing any data from the cache, the Nasuni Filer ensures that the data is stored in the cloud. The Nasuni Filer may perform a snapshot to preserve data in the cloud. Released data is not lost, because the data is stored in the cloud, ready to be retrieved. The Nasuni Filer releases the least recently used data first, using a sophisticated least recently used (LRU) algorithm. Loading large amounts of data into the Nasuni Filer Nasuni s best practices for loading large amounts of data into a Filer involve: Disable remote access temporarily. This makes the snapshots more efficient since they are less concerned with the response time of updates to the remote sites. Decrease snapshot frequency temporarily. This reduces the demand for resources, and allows freer access to the cache. Use the Data Migration Service (DMS) to move data. DMS is cache aware and slows down when the disk fills, instead of overfilling. Allow as much bandwidth (Quality of Service) as can be spared for when snapshots do occur. Nasuni offers a bulk data migration service if you have more data than you want to move over your network, such as when initially moving data into Nasuni s cloud storage. Contact Nasuni Technical Support for details. Downloading large amounts of data from cloud To download data from the cloud to the cache faster, do the following: Make sure that you have sufficient download bandwidth from your ISP. Ensure that the cache space is large enough to receive the data, so the system doesn't have to spend a lot of time making room. You can increase the size of the cache itself, or increase the reserved space percentage. Nasuni Filer Best Practices Guide

60 Considerations for configuring the cache Keeping all data locally (cache resident) To keep all data cache resident, the size of the non-reserved part of the cache must be larger than the total amount of data that you want to keep locally, including metadata. The size of the cache disk must be large enough for the cache. You can then bring all the data into the cache, and pin the volume into the cache. Proactively managing the contents of the cache There are situations where you might need to proactively manage the contents of the cache, because a process might not automatically bring the desired data into the cache. These situations include the following: After performing a restore. After performing a Disaster Recovery procedure that includes unpinned volumes. When performing bulk migrations. You can proactively manage the contents of the cache by performing any of the following actions: Pinning volumes in the cache. Accessing files or folders to ensure that they re brought into the cache. Bringing data into the cache manually, using Bring into Cache on the Versions page. Different Nasuni Filers for different uses Different uses of the Nasuni Filer might have different optimum configurations of the cache. For example, the usage pattern for ordinary user access is different from the usage pattern for backups or data mining. To ensure that each use case receives the most suitable configuration, you can set up different Nasuni Filers for different uses. The Nasuni Filer is intelligent and does its best to adapt to any use, but you can help guarantee the best behavior for each use case by isolating the use cases on different Nasuni Filers. Here are some examples of different uses for Nasuni Filers: Performing migrations: Minimize pinned volumes, infrequent snapshots. Primary file server: Pin volumes of commonly accessed files, moderate Quality of Service, regular snapshots. Hot standby for Disaster Recovery: Minimize pinned volumes, enable Auto Cache, frequent syncs. High-performance application: Pin volumes of commonly accessed files, high Quality of Service, regular snapshots. Nasuni Filer Best Practices Guide

61 Considerations for configuring the cache Different volumes for different uses It is also possible to employ different volumes on the same Nasuni Filer for different purposes. The Nasuni Filer cache adapts to any use (if Reserved Space Percentage is Automatic), but you can also adjust configurations to accommodate volumes with different uses on the same Nasuni Filer. For example, on a single Nasuni Filer, you might want to use one volume for ordinary user access to data and another for backups. To accommodate these two different uses, you might pin the most commonly used user data in the cache. You might also dedicate the Nasuni Filer to performing as a file server M-F 8-7, but then do backups at 3 AM. Nasuni Filer Best Practices Guide

62 Cache Specifications Cache Specifications The following table lists general cache-related specifications for the Nasuni Filer. Note: The Nasuni Filer only supports one cache. Description Maximum number of files in the Nasuni Service. Maximum capacity of files in the Nasuni Service. Default cache size on disk. Default snapshot period. Maximum file size. Value Unlimited Unlimited (may be restricted by license) 64 GB (VM only) 1 hour (after last snapshot) for unshared volume; 5 minutes for shared volume Available cache space at time of write The following table lists the maximum cache size (by platform) that is supported by the Nasuni Filer. The maximum cache size is equal to the required disk size. Virtualization Platform VMware ESX/ESXi 4 or ESX/ESXi 5 using VMFS3 Maximum Cache Size (equals Required Disk Size) Dependent upon VMFS block size (set when the physical disks are formatted): 1 MB block size: 256 GB 2 MB block size: 512 GB 4 MB block size: 1 TB 8 MB block size: 2 TB minus 512 bytes VMware ESX/ESXi 5 using VMFS5 Microsoft Hyper-V 2 TB minus 512 bytes If using physical Raw Disk Mapping (RDM) (aka pass through disks ), then 16 TB. 2 TB If using pass through disks, then 16 TB. Nasuni Filer Best Practices Guide

63 Quality of cache storage Quality of cache storage If you are using a Nasuni Filer hardware appliance, that platform is optimized for the cache. If you are using virtual machines, ensure that the storage platform meets these specifications: Protection, such as 4+1 RAID-5. Multiple spindles. 10K RPM or faster hard drives. Battery-backed write cache ability. Actions affecting the cache This section describes the actions you can perform that affect the cache. Removing data from cache Deleting a volume removes all the volume s data stored in the cache, as well as data stored in Nasuni s cloud storage. Disconnecting from a remote volume removes any data in the cache. Determining if data is in the cache By examining a folder or file in the Versions display, you can determine if a folder or file is currently in the cache (called cache resident ). Bringing data into the cache manually Note: This is optional. Cache management is automatic. If a file or folder is not in the cache, and you want it in the cache, find it in the Versions display, then click Bring into Cache. Note: If accessed data is not in the cache, it is brought into the cache automatically. Nasuni Filer Best Practices Guide

64 Snapshots and the cache Pinning or unpinning CIFS and NFS volumes in the cache You can enable or disable pinning CIFS and NFS volumes. On the Volumes page, select a volume, then click Edit Properties. Click edit next to the Volume Pinned status. From the Volume Pinning is drop-down list, select enabled or disabled. Note: You cannot unpin iscsi volumes. iscsi volumes are always pinned in the cache. Note: Pinning a volume in the cache does not bring that volume s data into the cache. Pinning a volume prevents that volume s data from being removed from the cache. Reserving space in cache By default, the Nasuni Filer automatically manages the amount of local cache space reserved for incoming data, using an advanced algorithm to optimize cache usage. However, you can override the reserved space. The reserved space that you set applies to all volumes on the Nasuni Filer. The maximum amount of reserved space is 90 percent of the cache size. The minimum amount of reserved space is 1 percent of the cache size, or 50 GB, whichever is larger. By setting the amount of reserved space, you disable the automatic management of this value. Click configuration, then select Cache Settings. On the Cache Settings page, select Automatic or one of the available percentages from the Reserved Space Percentage drop-down list. Snapshots and the cache Snapshots preserve data from the cache in the cloud, making that data eligible for removal from the cache, if necessary. Thus, scheduling frequent snapshots can help free up room in the cache for incoming writes. Scheduling snapshots You can schedule snapshots on a per-volume basis. On the Volumes page, select a volume, then click Edit Properties. Click edit next to the Snapshot Schedule status. On the Snapshot Scheduling page, select the days, start time, stop time, and frequency for snapshots. Manually starting snapshots To take a snapshot sooner than the scheduled time, click Take snapshot now on the Volumes page. Changing Quality of Service rules The Quality of Service is the limit on bandwidth for snapshots. The default is 2 megabits per second. To change the Quality of Service rules, click configuration, then select Quality of Service from the list. On Nasuni Filer Best Practices Guide

65 Snapshots and the cache the Quality of Service Settings page, select the days, start time, stop time, and bandwidth limit, from 50 kilobits per second to 25 gigabits per second. You can set up to 12 rules. The larger the Quality of Service, the faster snapshots complete, and the sooner space can become available in the cache. Nasuni Filer Best Practices Guide

66 Changing the size of the cache disk or copy-on-write (COW) disk Changing the size of the cache disk or copy-on-write (COW) disk On the virtual platform, you can change the size of the disk that the Nasuni Filer uses for its cache. On the virtual platform, you can also change the size of the disk that the Nasuni Filer uses for copy-onwrite (COW). 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. Note: There must be sufficient disk space in the datastore to increase the size of the disk. Note: You must shut down the virtual machine to change the size of the disk. Caution: Perform a manual snapshot before changing the size of the disk. Tip: Nasuni recommends using Thick provisioning for all virtual disks. vsphere Client platform Note: If you have taken a VMware snapshot, you cannot change the size of the disk. You must delete the snapshot first. To change the size of the disk on the vsphere Client platform, follow these steps: 1. Launch the VMware vsphere Client. The VMware vsphere Client login window appears. 2. Log in to the vsphere Client with a valid IP address and your user name and password. The vsphere Client opens. 3. In the pane on the left, expand the host to display the list of virtual machines. 4. Click the name of your Nasuni Filer. This is the name you entered when you installed the Nasuni Filer. Information about your Nasuni Filer appears in the right pane. 5. If the virtual machine is running, then shut down the virtual machine using these steps: a. On the Console tab, click in the command line area. b. Press Enter. c. Enter the login name and password for the service console. The default login name is service and the default password is service. d. Enter shutdown. e. Confirm the shutdown by entering yes. The virtual machine shuts down. 6. On the Getting Started tab, click Edit virtual machine settings. Alternatively, on the Summary tab, click Edit Settings. Alternatively, right-click the name of your Nasuni Filer in the list of virtual machines, then select Edit Settings from the drop-down list. Nasuni Filer Best Practices Guide

67 Changing the size of the cache disk or copy-on-write (COW) disk The Virtual Machine Properties dialog box appears. 7. On the Hardware tab, select the desired disk in the Hardware list on the left side. The cache disk is disk 2 and is the largest hard disk. The copy-on-write (COW) disk is the second-largest hard disk. Information about the selected hard disk appears on the right side. 8. Enter or select the new Provisioned Size. The Provisioned Size must be less than or equal to the displayed Maximum Size of that hard disk. The new Provisioned Size must be greater than the previous Provisioned Size. For details on the size of the cache disk, see the Nasuni Filer Initial Configuration Guide. For VMware ESX/ESXi 5 using VMFS5, the maximum cache size is 2 TB minus 512 bytes. For VMware ESX/ESXi 4 or ESX/ESXi 5 using VMFS3, the maximum cache size depends on the VMFS block size (set when you format the physical disks), as follows: For 1 MB block size, the maximum cache is 256 GB. For 2 MB block size, the maximum cache is 512 GB. For 4 MB block size, the maximum cache is 1 TB. For 8 MB block size, the maximum cache is 2 TB minus 512 bytes. 9. Click OK. The size of the selected hard disk changes to the specified size. 10. On the Getting Started tab, click Power on the virtual machine. Alternatively, on the Summary tab, click Power On. Alternatively, right-click the name of your Nasuni Filer in the list of virtual machines, then select Power from the drop-down list, then select Power On from the drop-down list. The virtual machine powers on. After a significant cache resize, the operations after powering on can take some time, with some performance impact during that period. The progress of the cache resize is visible on the Nasuni Filer user interface. Hyper-V Manager platform To change the size of the disk on the Hyper-V Manager platform, follow these steps: 1. Launch Hyper-V Manager. 2. In the Virtual Machines list, click the name of your Nasuni Filer. This is the name you entered when you installed the Nasuni Filer. Information about your Nasuni Filer appears. 3. If the virtual machine is running, then follow these steps: a. In the Virtual Machines list, right-click the name of your Nasuni Filer, then select Shut Down from the drop-down list. Alternatively, in the Virtual Machines list, select the name of your Nasuni Filer, then click Shut Down in the list of actions on the right side. Nasuni Filer Best Practices Guide

68 Changing the size of the cache disk or copy-on-write (COW) disk The Shut Down Machine dialog box appears. b. Click Shut Down. The virtual machine shuts down. 4. In the Virtual Machines list, right-click the name of your Nasuni Filer, then select Settings from the drop-down list. Alternatively, in the Virtual Machines list, select the name of your Nasuni Filer, then click Settings in the list of actions on the right side. The Settings dialog box appears. 5. In the Hardware list on the left side, select the desired hard drive. The default label for the cache hard drive is Hard Drive Cache.vhd. The cache hard drive is the largest hard drive. The default label for the copy-on-write (COW) hard drive is Hard Drive Cow.vhd. Information about the selected hard drive appears on the right side. 6. Click Edit. The Edit Virtual Hard Disk Wizard dialog box appears. 7. Select Expand, then click Next. 8. Enter the New size of the disk. The New size must be less than or equal to the displayed Maximum size of that hard disk. The New size must be greater than the previous size. Then click Next. For details on the size of the cache disk, see the Nasuni Filer Initial Configuration Guide. For Microsoft Hyper-V, the maximum cache size is 2 TB. 9. Click Finish. The size of the disk changes to the specified size. 10. Click OK. The Settings dialog box closes. 11. In the Virtual Machines list, right-click the name of your Nasuni Filer, then select Start from the drop-down list. Alternatively, in the Virtual Machines list, select the name of your Nasuni Filer, then click Start in the list of actions on the right side. The virtual machine restarts. After a significant cache resize, the operations after powering on can take some time, with some performance impact during that period. The progress of the cache resize is visible on the Nasuni Filer user interface. Nasuni Filer Best Practices Guide

69 Appendix D: Network Traffic Network Traffic Considerations Selecting Traffic Groups When configuring settings for your network during installation, you use the Network Interface Settings area. For each Device in the list, select the Traffic Group from the drop-down list. Three default traffic groups are available: Figure D-1: Network Interface Settings area. 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. You cannot combine traffic from two or more traffic groups together. Note: While the default gateway is required to be on the External traffic group, the gateway might not be used if a local proxy is enabled. If a local proxy is enabled, the local proxy is used for cloud traffic, remote support traffic, and Nasuni API traffic, and so traffic will flow on whichever interface can reach the local proxy. Nasuni Filer Best Practices Guide

70 Network Traffic Considerations Note: Any traffic inbound on a port not designated for that traffic, such as CIFS inbound over the management traffic group port, is blocked. To allow all traffic, of any protocol, from any origin host, to all traffic groups, select the Unrestricted Traffic Groups check box in the Firewall configuration. When the Unrestricted Traffic Groups check box is selected, all traffic groups (regardless of the name) are equivalent in what they can be used for. This allows unrestricted inbound access, and all responses reply over the same port as the inbound traffic; all outbound traffic always obeys the traffic group rules. 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 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. 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, 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 used by the External traffic group. 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, 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 more securely manage devices. Nasuni Filer Best Practices Guide

71 Network Traffic Considerations Sample network topologies. This example is for General traffic only. Figure D-2: General traffic only. Nasuni Filer Best Practices Guide

72 Network Traffic Considerations This example is for General and External traffic. Figure D-3: General and External traffic. Nasuni Filer Best Practices Guide

73 Network Traffic Considerations This example is for General and Management traffic. Figure D-4: General and Management traffic. Nasuni Filer Best Practices Guide

74 Network Traffic Considerations This example is for General, External, and Management traffic. Figure D-5: General, External, and Management traffic. Nasuni Filer Best Practices Guide

75 Network Traffic Considerations Creating Traffic Groups After installation of the Nasuni Filer, you can change network settings as required. See for a worksheet for planning configurations. To create a traffic group, follow these steps: 1. On Nasuni Filer: Click Configuration, then select Network Configuration from the menu. The Network Configuration page appears. Figure D-6: Network Configuration page. Nasuni Filer Best Practices Guide

76 Network Traffic Considerations 2. In the Network Interface Settings area, to manage traffic groups, click Manage Traffic Groups. The Traffic Groups dialog box appears. Figure D-7: Traffic Groups dialog box. The Traffic Groups dialog box displays a list of the currently available traffic groups appears. For each traffic group, the traffic group s name and description appears. a. To add a new traffic group, click Add Traffic Group. The Add Traffic Group dialog box appears. Figure D-8: 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. 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 4 below. Nasuni Filer Best Practices Guide

77 Network Traffic Considerations 3. In the Network Interface Settings area, for each Device in the list, select the Traffic Group from the drop-down list. Figure D-9: Network Interface Settings area. 4. In the Network Interface Settings area, to configure each Traffic Group, click Edit beside the Traffic Group. The Network Settings page appears. Figure D-10: Network Settings page. From the Network Type drop-down list, select either Static or DHCP. 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. Note: If you define more than one static device, the Nasuni Filer checks that the subnets specified do not appear more than once. If you select Static as a source, 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. Nasuni Filer Best Practices Guide

78 Network Traffic Considerations Enter a netmask address in the Netmask text box. Enter the MTU value in the MTU Value text box. MTU settings above 1500 are supported. 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. In the Gateway text box, enter the IP address for a gateway to route data outside the local LANs. Click OK to use these values. Click Cancel to exit this page without making any changes. 5. Click Save Network Configuration to accept your entries. The Confirm Network Changes page appears. Figure D-11: Confirm Network Changes page. 6. 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 Best Practices Guide

79 Network Traffic Considerations Configuring Traffic Groups On Nasuni Filer: Also in the Network Interface Settings area, to configure each Traffic Group, click Edit beside the Traffic Group. The Network Settings page appears. Figure D-12: Network Settings page. From the Network Type drop-down list, select either Static or DHCP. 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. Note: If you define more than one static device, the Nasuni Filer checks that the subnets specified do not appear more than once. If you select Static as a source, 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. Enter a netmask address in the Netmask text box. Enter the MTU value in the MTU Value text box. MTU settings above 1500 are supported. 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. Nasuni Filer Best Practices Guide

80 Network Traffic Considerations (Optional) You can specify a gateway for each traffic group. In the Gateway text box, enter the IP address for a gateway to route data outside the local LANs. Click OK to use these values. Click Cancel to exit this page without making any changes. Configuring System Settings In the System Settings area, from the Settings Source drop-down list, select either Static or DHCP as the source for system-wide configuration. Figure D-13: System Settings page. If you select DHCP (Dynamic Host Configuration Protocol), the Default gateway, Search Domain, Primary DNS Server, and Secondary DNS Server fields become unavailable. If you select Static as a source, 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. If the External traffic group is being used, the default gateway address must match that subnet exactly. Nasuni Filer Best Practices Guide

81 Network Traffic Considerations Enter one or more local search domains in the Search Domain text box. If you enter multiple search domains, make sure you include a space between each entry. You must enter valid host names. 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 host name 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 host name or IP address. To configure a proxy in order to reach HTTPS resources on the Internet, select the Configure A Proxy check box. Nasuni Filer Best Practices Guide

82 Index (port) Network Time Protocol (NTP) (port) SNMP monitoring 7 25 (port) SMTP 7, (port) 7, 14, (port) 7, 8 A access browser-based 13, 19, 21, 22 mobile access 22 network drive 21 Active Directory 1, 10, 11, 27, 34, 35, 70 multiple domains 35 Active Directory security 26 alerts 29 allocation roundup size application and 20 allowed hosts 27 CIFS share 19 iscsi 17 antivirus 25 Antivirus Service 17, 32 app installing 13 application allocation roundup size and 20 Case-Sensitive Paths and 20, 33 CIFS share and 20 configuring Nasuni Filer for 5 CPU cores for 6 memory 6 performance 30 volume and 18 authentication CIFS share 19 authorization code 8 Auto Cache 17 disabling 32 enabling 18, 32 sync and 32 B backup bandwidth and 7 cache for 6 configuring Nasuni Filer for 5 dedicated Nasuni Filer for 5 quality of service and 12 snapshot and 15 using cache 5 bandwidth backup 7 data migration 7 for disaster recovery 7 snapshot quality of service 12, 33, 34, 46, 53 Bring into Cache cache 31, 49, 52 Nasuni Filer Best Practices Guide

83 Index browser-based access 27 CIFS volume 13, 19, 21, 22 copying data to Nasuni Filer 21 Internet Explorer and 21, 22, 35 bulk data migration service 8, 20, 48 C cache 2, 3 Bring into Cache 31, 49, 52 Cache Resident data 31, 49, 52 capacity 3 configuration 44 data migration and 15 default size 51 for backup 5, 6 for disaster recovery 6 hardware appliance 6 iscsi volume and 17, 46 maximum sizes 51 minimum virtual machine 6, 51 New Data in Cache (Not yet protected) 45 pinned volume and 46 quality of service and 12, 33, 34 resizing 22, 34, 47, 55 size 6, 44, 47 snapshot and 46, 53 status 3, 44 structure 46 working set and 6, 47 write-back 31 cache disk size 55, 56, 57 cache resident 44 Cache Resident data cache 31, 49, 52 capacity cache 3 quota 4, 17 capacity for files 51 Case-Sensitive Paths application 33 application and 20 CIFS share and 19, 33 certificate SSL 8, 35 CHAP user name and password iscsi 17 CIFS migration source 20 network protocol 1, 2, 17 CIFS authentication 26 CIFS share 4 allowed hosts 19 application and 20 authentication 19 Case-Sensitive Paths and 19, 33 creating 20 planning 19 previous versions 19 Previous Versions and 32 read-only 19 status 29 unreadable files 19 user folders support 19 visible 19 CIFS share security 26 CIFS volume browser-based access 13, 19, 21, 22 cloud specifications 51 cloud storage 3, 4 deleting snapshots from 14 protecting data in 2, 3, 12, 33, 34 retrieving data from 3, 31, 32 sending snapshots to 12 compatibility mode Internet Explorer 35 compliance 26 compression 1, 3 configuring Nasuni Filer application 5 backup 5 data migration 5 disaster recovery 5 file server 5 mobile access 5 connecting to remote volume 16 console 7, 8, 22, 34, 35 copying data to Nasuni Filer browser-based access 21 data migration 34 mobile access 21 network drive 21 copy-on-write (COW) disk 47, 55 COW (copy-on-write) disk 47, 55 CPU cores application 6 data migration 6 hardware appliance 6 minimum virtual machine 6, 31 Nasuni Filer Best Practices Guide

84 Index D data Bring into Cache 31, 49, 52 Cache Resident 31, 49, 52 working set 6, 47 data migration 4, 20 bandwidth for 7 cache and 15 configuring Nasuni Filer for 5 copying data to Nasuni Filer 34 CPU cores for 6 dedicated Nasuni Filer for 5 defining 21 disable remote access for 48 disabling remote access for 14, 20 export 21 information on 30 infrequent snapshot for 15 minimizing snapshots for 48 multiple 34 Nasuni bulk data migration service 8, 20, 48 performance 30, 33 performance and 33 quality of service for 12, 48 scheduling 4, 21, 34 scheduling snapshot for 15 share 21 source 20 disconnected 29 Data Migration Service 28 dedicated Nasuni Filer for backup 5 for data migration 5 deduplication 1, 3 default gateway IP address 10 default share 13, 17 default volume 13 defining data migration 21 deleting snapshot 14, 17, 32 DHCP 7, 22, 66, 68, 69 network type 66, 68, 69 directory snapshot access 16, 33 enabling 19, 33 disaster recovery bandwidth for 7 cache for 6 configuring Nasuni Filer for 5 encryption keys 11 moving Nasuni Filer 22 serial number 8 shared volume 18 software updates 12 disk cache 55, 56 DNS connection 7 primary DNS server 10 secondary DNS server 10 server changing 22 domains multiple Active Directory 35 download data mobile access 22 E editnetwork command 7 alerts 29 configuring 10, 12 Nasuni ii Nasuni Support ii notifications 25 encryption keys 16, 24 downloading 11, 18, 22 escrowing with Nasuni 11 for disaster recovery 11 generated 11, 18 uploading 11 errors 29 escrowing encryption keys 11 ESX VMware 6, 31 ESXi VMware 6, 31 export 2 data migration 21 NFS creating 20 status 29 External traffic group 58 Nasuni Filer Best Practices Guide

85 Index F file alert service 17, 26 file permissions 28 file server configuring Nasuni Filer for 5 snapshot frequency 15 software updates 12, 23 file size 51 file system 2 file system metadata 2 file version 2 files information 30 firewall 24 frequency snapshot 15, 17, 18, 46 sync 17, 18, 32 gateway traffic group 67, 69 General traffic group 58 groups 25 defining 10, 20, 34 G H hard drive space hardware appliance 6 minimum virtual machine 6 status hardware appliance 31 hardware appliance cache 6 CPU cores 6 hard drive space 6 status 31 installing 7 LCD panel 7 memory 6 NF-200 6, 7, 31 NF-400 6, 7, 31 hidden share 35 hide unreadable files 27 high-availability (HA) network 6 HTTPS proxy 70 HTTPS proxy server 24 Hyper-V 6, 8, 31 cache size 51 Manager 56 installing Nasuni app 13 Nasuni Filer 6, 7 serial number 8 virtual machine 8 Internet connection 7, 22 Internet Explorer 21, 22 browser-based access and 21, 22, 35 compatibility mode 35 IP address 7, 8, 66, 67, 68, 70 default gateway 10 primary DNS server 10, 70 secondary DNS server 10, 70 setting 7, 22 VPN 14 iscsi allowed hosts 17 CHAP user name and password 17 network protocol 1, 2, 17 status 29 volume cache and 17 size 17 iscsi volume cache and 46 key terms 2 I K L LCD panel hardware appliance 7 least recently used (LRU) algorithm 48 license 43 licensed capacity verifying 22 Linux 2, 21 logging in 8, 14 login 8, 14 Nasuni Filer Best Practices Guide

86 Index M MAC address 7, 22 Macs 34 Management traffic group 58 maximum transmission unit 67, 68 memory application 6 hardware appliance 6 minimum virtual machine 6, 31 NF NF metadata 2 file system 2 Microsoft Hyper-V cache size 51 migration source CIFS 20 NFS 20 mobile access 27, 28 configuring Nasuni Filer for 5 copying data to Nasuni Filer 21 downloading data 22 enabling 13, 19, 20, 21 Read-Only access 20 share create 20 users and groups 20 worksheet 21 moving Nasuni Filer disaster recovery 22 MTU 22, 67, 68 multiple domains Active Directory 35 multiple Nasuni Filers 5 N name Nasuni Filer 5, 8, 10 volume 16 Nasuni bulk data migration service 8, 20, 48 Nasuni app installing 13 Nasuni Filer 2 configuring application 5 backup 5 data migration 5 disaster recovery standby 5 file server 5 mobile access 5 dedicated for backup 5 for data migration 5 installing 6, 7 serial number 8 virtual machine 8 moving 22 disaster recovery 22 name 5, 8, 10 planning 5 worksheet 5 shutting down snapshot 22 Nasuni Filer hardware appliance NF-200 6, 7, 31 NF-400 6, 7, 31 Nasuni Filer user interface 2 Nasuni Management Console 1, 2, 5, 9, 10, 16 Nasuni.com password 5 username 5 nasunicheck command 7 netmask 67, 68 network configuration password 67 username 67 configuring 10, 34, 58 connection 6, 22, 34 high-availability (HA) 6 parameters 22 settings for 8 setup 64 network drive 21 copying data to Nasuni Filer 21 network protocol 17 CIFS 1, 2, 17 iscsi 1, 2, 17 NFS 1, 2, 17 network status 29 Network Time Protocol NTP 7, 10, 11, 70 port time server 10 network traffic 6, 7, 8, 58 Nasuni Filer Best Practices Guide

87 Index network type DHCP 66, 68, 69 static 66, 68, 69 New Data in Cache (Not yet protected) cache 45 NF-200 memory 6 Nasuni Filer hardware appliance 6, 7, 31 NF-400 memory 6 Nasuni Filer hardware appliance 6, 7, 31 NFS migration source 20 network protocol 1, 2, 17 NFS export creating 20 status 29 NFS export security 27 NMC Nasuni Management Console 1, 2 notifications 29 Notifications page 29 NTP Network Time Protocol 7, 10, 11, 70 time server 10, 70 offline files 34 OpenPGP 37 OS X clients 2 configuring 14 password changing 25 Nasuni.com 5 network configuration 67 password retention 28 performance application 30 data migration 30, 33 data migration and 33 SMB2 and 14 snapshot 31, 33 sync 33 permissions 25, 28 pinned volume 16, 30 cache and 46 O P planning Nasuni Filer 5 worksheet 5 platforms virtual machine 6 port 123 Network Time Protocol 7 port 161 SNMP monitoring 7 port 25 SMTP 7, 10 port 443 7, 14, 21 port , 8 POSIX clients 14 Preview Pane disabling 23, 35 Previous Versions CIFS share and 32 previous versions CIFS share 19 primary DNS 70 server IP address 10 primary DNS server IP address 70 proxy server 24 Public security 26 Q quality of service backup 12 cache and 12, 33, 34 data migration 12, 48 snapshot bandwidth 12, 33, 34, 46, 53 quota maximum capacity 4, 17 R read-only CIFS share 19 Read-Only access mobile access 20 read-only exports 27 read-only share 27 remote access 16, 26, 30, 33 disable for data migration 48 disabling 14, 20, 33 disabling for data migration 14, 20 enabling 18, 20, 33 Remote Support Service 13, 28 Nasuni Filer Best Practices Guide

88 Index remote volume 4 connecting to 16 resizing cache 22, 34, 47, 55 retaining snapshot 14, 17, 32 retention snapshot 14, 17, 32 roaming profiles 34 role-based access control 25 S scheduling data migration 4, 21, 34 snapshot 2, 15, 17, 18 sync 17, 18, 32 secondary DNS 70 server IP address 10 secondary DNS server IP address 70 serial number 8 for disaster recovery 8 installing Nasuni Filer 8 service menu 34, 35 setall static command 7 share 2 CIFS 4 Case-Sensitive Paths and 19, 33 creating 20 planning 19 Previous Versions and 32 status 29 create mobile access for 20 data migration 21 default 13 hidden 35 volume and 2 shared volume disaster recovery 18 shutting down Nasuni Filer snapshot 22 size cache disk 55, 56, 57 SMB 14 SMB2 14 performance using 14 SMTP port 25 7, 10 snapshot 3 backup 15 bandwidth quality of service 12, 33, 34, 46, 53 before shutting down Nasuni Filer 22 cache and 46, 53 definition 2 deleting 14, 17, 32 details 3 directory access 16, 33 enabling 19, 33 disk 47 frequency 15, 17, 18, 46 file server 15 infrequent for data migration 15 initial 3 performance 31, 33 period 51 retaining 14, 17, 32 retention 14, 17, 32 scheduling 2, 15, 17, 18 scheduling for data migration 15 snapshot directory access 25 snapshot retention 26 snapshots minimizing for data migration 48 SNMP monitoring 25 port software 12 updates configuring 12 disaster recovery 12 file server 12 software updates configuring 22, 23 file server 23 status 29 source data migration 20 disconnected 29 SSL certificates 24 SSL security certificate 8, 35 static network type 66, 68, 69 status cache 3 CIFS share 29 iscsi 29 NFS export 29 Status page 29 storage controller 2 Nasuni Filer Best Practices Guide

89 Index subscription status 29 sync 4 Auto Cache and 32 frequency 17, 18, 32 performance 33 scheduling 17, 18, 32 T text conventions ix thick provisioning (virtual machine) 31 thin provisioning (virtual machine) 31 time server Network Time Protocol 10 NTP 10 time.nasuni.com 10 traffic 6 traffic group 58 adding 65 configuring 66 deleting 65 editing 65 External 58 gateway 67, 69 General 58 Management 58 managing 65 selecting 66 U UNIX 2, 21 unreadable files CIFS share 19 unsynchronized data 3 user folders support CIFS share 19 user interface 1 clearing browser cache 23 configuring Nasuni Filer 10 Home page 8 issues 35 not available 34, 35 operations tasks 16 username Nasuni.com 5 network configuration 67 users 25 defining 8, 10, 20, 34 users and groups mobile access 20 version history 2 virtual machine cache minimum 6, 51 CPU cores minimum 6, 31 hard drive space minimum 6 installing 7 Nasuni Filer 8 memory minimum 6, 31 platforms 6 visible CIFS share 19 visible share 26 VMware 8 ESX 6, 31 ESXi 6, 31 VMware ESX/ESXi cache size 51 volume application and 18 creating 18 default 13 definition 2 name 16 pinned 16, 30 planning 16 share 2 size iscsi 17 trial mode 18 VPN 30 IP address and 14 vsphere Client 55 V W warnings 29 Web browsers 2 Windows 1, 2, 4, 21, 23, 35 Windows domain 10 Windows Explorer Preview Pane disabling 23, 35 Windows Previous Versions 1 Nasuni Filer Best Practices Guide

90 Index Windows Server workgroup 10 working set cache and 6, 47 worksheet mobile access 21 planning Nasuni Filer 5 write-back cache 31 Nasuni Filer Best Practices Guide