Best Practices Guide. Version 7.2. November 2015 Last modified: November 16, Nasuni Corporation All Rights Reserved

Transcription

1 Best Practices Guide Version 7.2 November 2015 Last modified: November 16, Nasuni Corporation All Rights Reserved

2 Document Information Best Practices Guide Version 7.2 November 2015 Copyright Copyright by Nasuni Corporation. All rights reserved. Information in this document is subject to change without notice and does not represent a commitment on the part of Nasuni. The software described in this document is furnished under a license agreement. The software may be used only in accordance with the terms of the license agreement. It is against the law to copy the software on any medium. No part of this manual may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, for any purpose without the express written permission of Nasuni Corporation. Notice Although Nasuni Corporation has attempted to ensure the accuracy of the content of this manual, it is possible that this document 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 ovals logo are Nasuni trademarks and service marks. All other names, brands and products are the property of their respective owners. Contacting Nasuni Corporation Nasuni Corporation 313 Speen Street Natick, MA Telephone: Sales: Fax: info@nasuni.com Technical Support Telephone: NASUNI ( ) support@nasuni.com 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 Services Nasuni Filer Nasuni Management Console 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 this information Nasuni Filer Best Practices Guide 7.2 iii

4 Contents For each volume, configure Encryption Keys On the Nasuni Management Console, configure Active Directory security Place each Nasuni Filer under the control of the Nasuni Management Console 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 first Nasuni Filer, verify the default Volume and Share Enabling multiple protocols to access a volume Enabling Web Access to CIFS shares on each volume Enabling Mobile Access to CIFS shares (ios and Android devices) on each volume. 16 Enabling Desktop Client access to CIFS shares Configuring for OS X clients on each volume Configuring Snapshot Retention on each volume If this Nasuni Filer is performing data migrations, follow these steps 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 managing backup data, schedule snapshots for once per day at a time of minimal activity Chapter 4: Operations Operations Managing Volumes Managing Shares, Exports, and FTP/SFTP directories 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) Enabling global file locking for a folder Verifying licensed capacity Updating Nasuni Filer Software Avoiding performance issues Nasuni Filer Best Practices Guide 7.2 iv

5 Contents Chapter 5: Security Security HTTPS proxy server Firewall protection SSL certificates Encryption keys Role-based access control notifications Antivirus protection File System Auditing SNMP monitoring Change password Snapshot directory access Remote access Snapshot retention File Alert Service CIFS authentication CIFS share security NFS export security FTP/SFTP directory 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: Nasuni Terms of Service and License Agreement Nasuni Corporation Nasuni Filer Best Practices Guide 7.2 v

6 Contents Appendix B: Cache Configuration Cache Configuration About the cache Cache structure Considerations for configuring the cache 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 folders 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 Supported techniques for changing the size of a disk Using the VM user interface to increase the size of the cache disk or copy-on-write (COW) disk 56 Using the Disaster Recovery procedure to change the size of the cache disk or copy-on-write (COW) disk Using a new COW disk to change the size of the COW disk Appendix C: Network Traffic Network Traffic Considerations Nasuni Filer Best Practices Guide 7.2 vi

7 Contents Selecting Traffic Groups Creating Traffic Groups Configuring Traffic Groups Configuring System Settings Appendix D: Port 443 Outbound Details Port 443 Outbound Details Amazon Web Services (AWS) Microsoft Azure Appendix E: Glossary Index Nasuni Filer Best Practices Guide 7.2 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 12 explains how to configure the Nasuni Filer for optimum performance. Chapter 4, Operations, on page 20 explains how to manage the Nasuni Filer during ordinary operations. Chapter 5, Security, on page 30 presents the Nasuni Filer s many security features. Chapter 6, Troubleshooting, on page 36 explains how to solve problems without the necessity of contacting Technical Support. Appendix A, Nasuni Terms of Service and License Agreement, on page 45 is the link to the Nasuni Terms of Service and License Agreement. Appendix B, Cache Configuration, on page 46 gives details about configuring the cache of the Nasuni Filer. Appendix C, Network Traffic, on page 60 gives details about configuring the Nasuni Filer with your network configuration. Appendix E, Glossary, on page 74 provides definitions of terms related to the Nasuni Filer. Nasuni Filer Best Practices Guide 7.2 viii

9 Preface 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. Also used for named graphical elements. Used to represent options or parameters. Used for hyperlinks, such as links to Web sites. Used to indicate pathnames, filenames, folder names, typed information, and code. Nasuni Filer Best Practices Guide 7.2 ix

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

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

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

13 Nasuni Management Console Nasuni Management Console The Nasuni Management Console enables you to monitor and manage many Nasuni Filers from one central appliance. Using the Nasuni Management Console, you can view the status of all of your managed Nasuni Filers, as well as configure their settings. With the Nasuni Management Console, you can ensure consistent settings on all your Nasuni Filers. Key Terms The following terms are helpful in understanding the Nasuni Filer: Nasuni Filer: The storage controller in your data center that integrates with your infrastructure via CIFS, NFS, iscsi, FTP/SFTP, or HTTPS/REST protocols. The Nasuni Filer can be mapped as a network drive. Nasuni Filer user interface: The Web-based graphical user interface with which you configure and manage the Nasuni Filer. The Nasuni Filer user interface is accessible with supported Web browsers including Mozilla Firefox, Internet Explorer, Safari, and Google Chrome. Nasuni Management Console (NMC): The Web-accessible appliance with which you can configure and manage multiple Nasuni Filers. The Nasuni Management Console is accessible with supported Web browsers including Mozilla Firefox, Internet Explorer, Apple Safari, and Google Chrome. Cloud storage: Internet-based, highly protected, unlimited storage. Volume: A set of files and directories (CIFS, NFS, and FTP/SFTP) or blocks of data (iscsi). Share/export: An access point to a folder on a volume that can be shared or exported on your network. Access to a CIFS share can be customized on a user-level or group-level basis. You can create many shares or exports on a volume, for different purposes or audiences. Cache: The local storage of the Nasuni Filer. All data and metadata that is accessed regularly is kept locally in the cache. If requested data is not locally resident, it is staged into the cache and provided for the request. Snapshot: A snapshot is a complete picture of your volume at a specific point in time. Snapshots offer data protection by enabling you to recover data deleted in error or to restore an entire file system. After a snapshot has been taken and is sent to cloud storage, it is not possible to modify that snapshot. Nasuni Filer Best Practices Guide 7.2 2

14 About File Systems About File Systems File system data and metadata are stored locally on the Nasuni Filer. However, permanent storage is in the form of cloud-based storage. Changes in files are sent to cloud storage by the Nasuni Filer, at times specified by your snapshot schedule and at rates specified by your specified quality of service (inbound and outbound 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 encryption settings and volume protocol: CIFS, NFS, FTP/SFTP, or iscsi. Note: The Nasuni Filer supports Windows, UNIX, and Linux clients. Client capabilities and behavior vary, depending on the client type and the client operating system version. 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. Nasuni Filer Best Practices Guide 7.2 3

15 Terminology 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 data in the cache or manually changing the cache settings can affect the percentage of the cache that is free to accept new data. 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 inbound and 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. Also see Glossary on page 74. Nasuni Filer Best Practices Guide 7.2 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. Providing FTP/SFTP access to data, especially for users without the usual authentication. 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 7.2 5

17 Installation C. Planning the installation of each Nasuni Filer For details, see the Nasuni Filer Initial Configuration Guide Verify minimum memory: 4 GiB (virtual machine) Recommended minimum memory is 6 GiB. A very light load might require only 4 GiB. A heavy load might require 8 GiB or more. If applications access the Nasuni Filer directly, consider adding more memory. For comparison, the Nasuni Filer hardware appliance includes 12 GiB (NF-200) or 32 GiB (NF-400, NF-400H, and NF-440) memory. Verify minimum free hard drive space to run the Nasuni Filer: 352 GB (virtual machine) The minimum free hard drive space must include the cache. See step 4 below. For comparison, the Nasuni Filer hardware appliance includes 6 TB (NF-200 and NF-400), 11 TB or 22 TB (NF-440), or 12 TB or 24 TB (NF-400H) hard drive space. Verify minimum number of CPU cores: 2 (more than 2 for optimal performance) (virtual machine) For comparison, the Nasuni Filer hardware appliance includes 6 cores (NF-200, NF-400, and NF-400H) or 12 cores (NF-440). 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. Verify minimum hard drive space for cache: 250 GB (virtual machine) For comparison, the Nasuni Filer hardware appliance includes 6 TB (NF-200 and NF-400), 11 TB or 22 TB (NF-440), or 12 TB or 24 TB (NF-400H) 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 B, Cache Configuration, on page 46 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. Verify supported virtualization platforms: VMware ESXi 5.0, 5.1, 5.5, and 6.0; and Windows Server 2008 R2 SP1 and Windows Server 2012 Hyper-V (virtual machine) Nasuni Filer Best Practices Guide 7.2 6

18 Installation Verify working network connections For details on configuring for network traffic, see Appendix C, Network Traffic, on page 60. (The Nasuni Filer uses bonding mode 5 (balance-tlb) for high-availability (HA) networking. This has no requirements from the switches.) 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. Nasuni Filer Best Practices Guide 7.2 7

19 Installation 8. Verify corporate firewall configured to open required ports The following ports should be open, as required: Port number Associated protocols Used for Inbound (to Nasuni Filer) Outbound (from Nasuni Filer) 8443 HTTPS Access Nasuni Filer administrative interface. 443 HTTPS Nasuni Management Console Administrative Access; Web Access; Desktop and Mobile Access: Nasuni Desktop Client (Windows, Linux, and OSX clients) and Mobile Access (ios and Android clients). Optional (but not recommended), open to Nasuni Filer for external management access direct or via NAT. Optional, but required if using Web Access, or Desktop and Mobile Access and external access is desired without VPN. Optional, open to Nasuni Management Console for external management access direct or via NAT. N/A At a minimum, open to *.nasuni.com, *.amazonaws.com, and *.windows.net Note: Firewalls that process and log port 443 traffic from the Nasuni Filer can affect performance when the Nasuni Filer is communicating with the cloud. If you must use IP addresses (not recommended), see Appendix D, Port 443 Outbound Details, on page NTP (Network Time Protocol) Connecting to Network Time Protocol (NTP) servers. N/A Optional, if connecting to external Network Time Protocol (NTP) servers. 161 SNMP (Simple Network Management Protocol) Connecting to Simple Network Management Protocol (SNMP) services. N/A Optional, if using external Simple Network Management Protocol (SNMP) trap addresses. 25 SMTP (Simple Mail Transfer Protocol) Simple Mail Transfer Protocol (SMTP) processing for outgoing messages. N/A Optional, if using external servers for for Nasuni Filer messages. Nasuni Filer Best Practices Guide 7.2 8

20 Installation D. Platform installation options There are 4 platform options for installation: For a Nasuni Filer hardware appliance, go to step 1, Nasuni Filer hardware appliance (NF-200, NF-400, NF-400H, and NF-440). For a virtual machine platform, including VMware and Hyper-V, go to step 2, Installation on virtual machine (VMware or Hyper-V). For the Microsoft Azure virtual platform, go to step 3, Installation on Microsoft Azure virtual platform. For the Amazon EC2 virtual platform, go to step 4, Installation on Amazon EC2 virtual platform Nasuni Filer hardware appliance (NF-200, NF-400, NF-400H, and NF-440) See the Nasuni Filer Hardware Deployment Getting Started Guide. The Nasuni Filer software is already installed. If you re using the NF-200, NF-400, or NF-400H, 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-440, connect a monitor to the VGA port, then determine or set the IP address in one of these ways: If DHCP is available on the network, view the console. 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, on the console, press Enter. Use username service and password service. Enter editnetwork. Enter setall static. Enter a new IP address. Enter save. To configure idrac (Integrated Dell Remote Access Controller), see the idrac Configuration Procedure. Continue with step E, Logging in to the Nasuni Filer for the first time. 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. Continue with step E, Logging in to the Nasuni Filer for the first time. Nasuni Filer Best Practices Guide 7.2 9

21 Installation Installation on Microsoft Azure virtual platform For detailed installation instructions, see the Nasuni Filer Virtualization Getting Started Guide for Azure. Note the initial IP address. Continue with step E, Logging in to the Nasuni Filer for the first time. Installation on Amazon EC2 virtual platform For detailed installation instructions, see the Nasuni Filer Virtualization Getting Started Guide for EC2. Note the initial IP address. E. 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 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. When the wizard starts, configure settings for your network For details on configuring for network traffic, see Appendix C, Network Traffic, on page 60. 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 or on the Account Status page of the Nasuni Management Console. 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. Accept the Terms of Service Create a Nasuni Filer name or description Create a Username (case-sensitive) and a Password (case-sensitive) for administration of the Nasuni Filer Nasuni Filer Best Practices Guide

22 Installation 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 role-based access control system. See For each volume, configure Quality of Service rules on page 14. If migrating a large amount of data to the new Nasuni Filer, consider using Nasuni s bulk data migration service 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. Place Nasuni Filers under the control of the Nasuni Management Console (NMC). Continue with configuring the Nasuni Filer at Configuration on page 12. Nasuni Filer Best Practices Guide

23 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 Administration Guide and Nasuni Management Console Guide. All documentation is available at A. For each Nasuni Filer that you are configuring, determine this 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: Filer Admins and File Restore. Default user: admin. Groups: Users: Nasuni Filer Best Practices Guide

24 Configuration B. For each volume, configure Encryption Keys 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. Download and protect encryption keys generated by the Nasuni Filer, 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. On the Nasuni Management Console, configure Active Directory security Click Console Settings, then click Domain Settings. D. Place each Nasuni Filer under the control of the Nasuni Management Console The Nasuni Management Console allows you to manage multiple Nasuni Filers from one central application. For details, see the Nasuni Management Console Guide. On Nasuni Filer: Click Services, then select Nasuni Management Console. E. For each Nasuni Filer, configure the Time Zone and the Time Server (Network Time Protocol) 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. Nasuni Filer Best Practices Guide

25 Configuration F. For each Nasuni Filer, configure Active Directory security If you are using Active Directory for security, configure Active Directory security on each Nasuni Filer To join a Nasuni Filer to its first Active Directory domain, click Configuration, then select General Settings, then click Join Domain. To join a Nasuni Filer to an Active Directory domain after its first, click Configuration, then select Domain Settings. To leave an Active Directory domain, click Configuration, then select Domain Settings. G. For each volume, configure Quality of Service rules Quality of Service is the inbound and outbound bandwidth limit for moving data to and from the Nasuni Filer, such as sending snapshots to Nasuni s cloud storage. The larger the outbound Quality of Service, the faster incoming data is protected in cloud storage and the more cache space is made available for data. The best performance generally occurs with the Unlimited setting, but this depends on your enterprise s use of the network and the amount of bandwidth available to the Nasuni Filer. Inbound Quality of Service is Unlimited by default. 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 outbound 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 outbound 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 the inbound Quality of Service is too low, and data must be obtained from cloud storage, data access might be affected. If the outbound Quality of Service is large or unlimited, and the inbound Quality of Service is small, the limited inbound bandwidth for return packets (such as acknowledgements) might affect the outbound bandwidth. 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. H. For each Nasuni Filer, configure settings On Nasuni Filer: To receive alerts by , click Configuration, then select Settings. On NMC: Click Filers, then click Settings. Select Nasuni Filers, then click Edit Filers. Nasuni Filer Best Practices Guide

26 Configuration I. 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. J. 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. K. For first 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 Volumes, then click Shares. To create a new volume, see Creating a volume on page 22. To create a new share, see Creating a new share on page 24. Nasuni Filer Best Practices Guide

27 Configuration L. Enabling multiple protocols to access a volume You can use multiple protocols, including CIFS, NFS, and FTP/SFTP, to access data. On Nasuni Filer: Click Volumes, select the NFS volume from the list, then click Properties and select Volume Protocols. Select protocols for volume. On NMC: Click Volumes, then click Protocols. For selected volume, click Edit. Note: You cannot enable Global Locking for a volume that has multiple protocols enabled. See Enabling Global Locking on page 23. M. Enabling Web Access to CIFS shares 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 Web Access: On Nasuni Filer: Click Volumes, select the volume with the CIFS protocol enabled from the list, then click the Total Shares status. Click Edit Share for the share. Select Show Advanced Options, then select the Web Access check box. On NMC: Click Volumes, then click Shares. For the selected share, click Edit. Select Show Advanced Options, then select the Web Access check box. For both: To enable Shared Links, select Enable Shared Links. N. Enabling Mobile Access to CIFS shares (ios and Android devices) on each volume Enable Mobile Access in order to use the Nasuni Desktop Client, or to access data using ios and Android devices Enabling Mobile Access for a share On Nasuni Filer: Click Volumes, select the volume with the CIFS protocol enabled from the list, then click the Total Shares status. Click Edit Share for the share. Select Show Advanced Options, then select the Desktop and Mobile Access check box. On NMC: Click Volumes, then click Shares. For the selected share, click Edit. Select the Desktop and Mobile Access check box. On your mobile device, download and install the appropriate Nasuni app for your platform. 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. Nasuni Filer Best Practices Guide

28 Configuration 3. Providing initial login links to users On Nasuni Filer: Click Services, then select Mobile Service Settings from the list. Click Invitation Link. On NMC: Click Filers, then click Mobile Settings. Click Invitation Link for the selected Nasuni Filer. To require VPN access, use the internal hostname or IP address, and port 443. To provide direct external access, use the external hostname or IP address and port. O. Enabling Desktop Client access to CIFS shares The Nasuni Desktop Client consists of a simple interface to the Nasuni Filer on the user s computer. The Nasuni Desktop Client is available for Windows, Linux, and OSX platforms. The Nasuni Desktop Client requires a separate installation and configuration on each end user s computer. For more details see the Nasuni Desktop Client Administrator Guide and the Nasuni Desktop Client User Guide. To enable Desktop Client access: On Nasuni Filer: Click Volumes, select the volume with the CIFS protocol enabled from the list, then click the Total Shares status. Click Edit Share for the share. Select Show Advanced Options, then select the Desktop and Mobile Access check box. On NMC: Click Volumes, then click Shares. For the selected share, click Edit. Select the Desktop and Mobile Access check box. P. Configuring for OS X clients on each volume 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. On NMC: Click Filers, then click CIFS Settings. Select Nasuni Filers, then click Edit Filers. Select the Enhanced Support for POSIX Clients check box. Q. 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. Nasuni Filer Best Practices Guide