Nasuni Filer Recovery Guide

Transcription

1 Nasuni Filer Recovery Guide In the Event of a True Disaster Important: If this is a true disaster, and the original source Nasuni Filer is no longer available, proceed immediately to Downloading and Installing the Nasuni Filer Software on page 12. Version 8.0 April 2018 Last modified: April 20, Nasuni Corporation All Rights Reserved

2 Document Information Recovery Guide Version 8.0 April 2018 Copyright Copyright Nasuni Corporation. All rights reserved. Notice The Information in this document is subject to change without notice and does not represent a commitment on the part of Nasuni Corporation ( Nasuni ). The software and services described in this document are furnished under terms and conditions found at The software and services may be used only in accordance with such terms. These terms are subject to change from time to time, so you should check our website from time to time for the latest terms. This document contains the confidential and proprietary information of Nasuni and may not be used or disclosed to any third party except as specifically set forth in such terms and conditions and any confidentiality agreement in place with Nasuni. No part of this manual may be reproduced in any form or by any means, electronic or mechanical, including photocopying and recording, without the express written permission of Nasuni. Licensed users may contact Nasuni for access to additional copies. Although Nasuni has attempted to ensure the accuracy of the content of this document, it is possible that this document might contain technical inaccuracies, typos or other errors. Nasuni assumes no liability for any error in this document and disclaims all damages that might arise from the use of this document, whether direct, indirect, incidental, consequential or otherwise, 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, the NASUNI logo, and UNIFS are registered trademarks and/or service marks of Nasuni Corporation. All other marks are the property of their respective owners. Contacting Nasuni Corporation Nasuni Corporation One Marina Park Drive Boston, MA Telephone: Sales: info@nasuni.com Technical Support Telephone: NASUNI ( ) support@nasuni.com Technical Support is available 24/7/365 for full production customers.

3 Contents In the Event of a True Disaster i Electronic Publications iv Release Notes for Nasuni Documentation Set v Recovery In the Event of a True Disaster Introduction Side Load and Recovery Considerations before Performing the Recovery Procedure Overview of Recovery Process Preparing the Original Source Nasuni Filer (if available) Downloading and Installing the Nasuni Filer Software Recovering the Nasuni Filer Performing the Side Load process Starting the Side Load process Viewing and controlling the Side Load process Verifying the Volumes Shutting Down the Original Source Nasuni Filer Appendix A: Backup Keys Backup Keys Index Recovery Guide iii

4 Electronic Publications 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-60, visit: Nasuni_Filer_HW_GS_Guide_NF-60.pdf To download this guide for the NF-200, visit: Nasuni_Filer_HW_GS_Guide_NF-200.pdf To download this guide for the NF-400, visit: Nasuni_Filer_HW_GS_Guide_NF-400.pdf To download this guide for the NF-440, visit: Nasuni_Filer_HW_GS_Guide_NF-440.pdf To download this guide for the NF-600, visit: Nasuni_Filer_HW_GS_Guide_NF-600.pdf Installing the Nasuni Filer on Virtual Platforms: For installing the Nasuni Filer on a virtual machine within a corporate network. To download this guide, visit: Installing the Nasuni Filer on the Azure Platform: For installing the Nasuni Filer on the Microsoft Azure cloud virtual machine. To download this guide, visit: Recovery Guide8.0 iv

5 Release Notes for Nasuni Documentation Set Installing the Nasuni Filer on the EC2 Platform: For installing the Nasuni Filer on the Amazon EC2 cloud virtual machine. To download this guide, visit: 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: Nasuni_Filer_Initial_Configuration_Guide.pdf Administration Guide: For managing unified storage using the Nasuni Filer. To download this guide, visit: Nasuni_Filer_Administration_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: 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: Party_Licensing_Guide.pdf Release Notes for Nasuni Documentation Set Date (As Of) Changes Provided details of how restoring a folder affects current contents of folder, in Administration Guide and NMC Guide. Added many suggestions for VM installation, in Installing on VM and Suggestions for VM Installation. Recovery Guide8.0 v

6 Release Notes for Nasuni Documentation Set Date (As Of) Changes Added examples for how to specify allowed hosts for CIFS shares, in Administration Guide and NMC Guide. Clarified behavior when deleting directories containing blocked files, in Administration Guide, NMC Guide, Mobile Access Guide, Mobile Access User Guide, Web Access User Guide, Web Access Shared Links, and Initial Configuration Guide. Warned that CIFS folders with Advanced Global Locking might have access issues with Linux clients, in Global Locking Guide, Administration Guide, and NMC Guide. Clarified rules for Filer-forced snapshots, in Snapshot Processing. Clarified non-support for Hyper-V Dynamic Memory, in Suggestions for VM Installation. Added numerous Mac OS X details and suggestions, in Mac OS X Best Practices Guide Added details of new considerations affecting Mac client performance, in Mac OS X Performance Guide. Clarified when updates to antivirus database occur, in Best Practices Guide, Administration Guide, and NMC Guide. Added support for Varonis and other systems that use Advanced Message Queuing Protocol (AMQP), in Administration Guide and NMC Guide. Added explanations of Safe Delete feature, in Administration Guide and NMC Guide. Added a description of the NMC API, in NMC API. Cautioned about deleting files deleted from folder that two different Nasuni Filers have enabled Global Locking on, in Administration Guide. Global Locking Guide. and NMC Guide. Clarified supported instance types, in Installing the Nasuni Filer on the EC2 Platform. Added procedures for accessing software through Azure Marketplace, in Configuring Customer-Provided Azure Tenant. Updated screen shots and procedures for SSL certificates, in Administration Guide. Updated screen shot, in Configuring Customer-Provided Azure Tenant. Fixed incorrect screen shot, in DFS Configuration Guide. Added procedure for removing Revit Worksharing Monitor, in Revit Configuration Guide. Recovery Guide8.0 vi

7 Release Notes for Nasuni Documentation Set Date (As Of) Changes Added information about time to generate an encryption key, in Best Practices Guide, Encryption Key Best Practices, NMC Guide, Recovery Guide, and Administration Guide. Added considerations about MTU on the EC2 platform, in Installing the Nasuni Filer on the EC2 Platform. Noted that enabling "Snapshot Directory Access" prevents directories from being deleted, in NMC Guide, Administration Guide, and Best Practices Guide. Clarified behavior of Security indication when permission of remote volume is set to Disabled, in NMC Guide. Noted that you cannot create an internal link to folders created by using the "%U" wildcard, in several documents. Clarified the relative size of the COW disk, in Cache Configuration Guide and Installing on Virtual. Added tip on hard links with Linux and Mac OS X clients using global locking with CIFS, in Administration Guide. Updated default number of cores to 4, in Initial Configuration Guide and Installing on Virtual. Added tip on case-sensitive volumes and multiple volume protocols, in Administration Guide. Added tip on using Windows net use command, in Administration Guide and Initial Configuration Guide. Added details of the suggested usage, in Revit Configuration Guide. Clarified how Auto Cache works, in Administration Guide and NMC Guide. Specified that the user names for CIFS Administrative Users should not have the leading domain, in Administration Guide. Added tip about Embedded Host Client for installing the Nasuni Filer into VMware ESXi using the vsphere Web interface, in Installing on Virtual. Added description of backup keys, which enable recovery of Nasuni Filers that don t have owned volumes or snapshots, in Administration Guide and Recovery Guide. Updated procedure for installing Nasuni Filer and NMC on Microsoft Azure platform, in Configuring Customer-Provided Azure Tenant for the Nasuni Filer. Recovery Guide8.0 vii

8 Release Notes for Nasuni Documentation Set Date (As Of) Changes Added the Device ID and Logged In fields to the Mobile Licenses table, in NMC Guide. Added description of Prioritize Snapshot feature, in NMC Guide and Administration Guide. Created tip for error when installing to non-default location on Hyper-V, in Installing on Virtual Clarified when the file syncs occur related to Global Locking, in Cache Configuration Guide, Best Practices Guide, Global Locking Guide, and Administration Guide. Clarified processing when a Nasuni Filer goes under the control of a Nasuni Management Console, in NMC Guide and Administration Guide. Added details about how certain types of loads can affect syncs, in NMC Guide, Merge Conflicts Guide, and Administration Guide. Warned that downloading large files from the NMC can take a long time, in NMC Guide. Added warning against saving encryption key files to volume, in Best Practices Guide, NMC Guide, Recovery Guide, and Administration Guide. Updated copyright, trademark, disclaimer, and liability statements, in most documents. Updated maximum Azure disk size to 4,095 GiB, in Best Practices Guide, Cache Configuration Guide, Initial Configuration Guide, Resizing Cache Guide, Installing on Virtual Platforms, and Suggestions for VM Installation Added procedure for possible notification during snapshot or sync, in NMC Guide and Administration Guide. Added details about the Clam AntiVirus (ClamAV ) open-source antivirus engine, in Best Practices Guide, NMC Guide, Third-Party Licensing Guide, and Administration Guide. New screenshots, in Installing the Nasuni Filer on the EC2 Platform. Added reminders to keep COW disk in proportion to cache disk when changing the size of the cache disk, in Cache Configuration and several other documents. Selecting the Secure transfer required feature for an Azure Storage account does not affect the operation of the Nasuni Filer, in Configuring Customer-Provided Azure Storage for the Nasuni Filer and Installing Nasuni Filer on Customer-Provided Azure Storage Getting Started Guide. Recovery Guide8.0 viii

9 Release Notes for Nasuni Documentation Set Date (As Of) Changes Corrected the default number of cores for a Nasuni Filer, in Best Practices Guide, Initial Configuration Guide, and Installing on Virtual Platforms. Clarified the processing for recovery after resetting the administrative account, in Recovery Guide, Administration Guide, and NMC Guide. Clarified the prerequisites for performing the Side Load procedure, in Recovery Guide, Administration Guide, and Side Load Guide. Clarified the default outbound Quality of Service, in Best Practices Guide, Cache Configuration Guide, Administration Guide, and NMC Guide. Added material about enabling Auditing to help mitigate ransomware, in Best Practices Guide, Administration Guide, and NMC Guide. Clarified meaning of Restrict Anonymous setting for CIFS, in Administration Guide and NMC Guide Added material on Cloud I/O and Cloud Credentials, in Administration Guide and NMC Guide. Added discussion of chunk size and related topics, in Best Practices Guide, Cache Configuration Guide, Administration Guide, and NMC Guide. Rewrote section on General CIFS Settings to clarify processing in different situations, in Administration Guide and NMC Guide. Added details about how long notifications are retained, in Administration Guide and NMC Guide. Added procedure for obtaining JSON format of shares configuration in NMC, in NMC Guide. Clarified use of DFS for failover, in DFS Configuration and Best Practices Guide. Reconciled the recovery procedures, in Administration Guide and Recovery Guide. Removed mentions of default volume and default CIFS share, in Best Practices Guide, Best Practices Guide, and Administration Guide. Clarified best use cases for Side Load procedure, in Side Load Feature. Added warnings against restoring a virtual machine from a virtual machine snapshot or backup, in Cache Configuration Guide and Installing on Virtual Platforms. Recovery Guide8.0 ix

10 Release Notes for Nasuni Documentation Set Date (As Of) Changes Added information about how permissions affect the ability to download files, in Administration Guide and NMC Guide. Added procedure for SMB3 encryption, in Administration Guide, Security Features, and NMC Guide. Added instructions for Snapshot ran out of internal space error, in Administration Guide and Best Practices Guide. Updated the supported Cleversafe/IBM Cloud Object Storage version to Added details of auditing becoming disabled if Varonis or AMQP destinations are removed, in Administration Guide and NMC Guide. Added details of the use of encryption keys with remote volumes, in Encryption Key Best Practices. Added details of auditing output types, including Varonis, AMQP, and local CSV, in NMC Guide. Clarified details of NTFS Exclusive Mode and NTFS Compatible Mode, in Administration Guide and others Formatting and pagination, in Data API doc. Added Varonis integration, in Administration Guide and NMC Guide. Clarified NMC procedure for changing SMB protocol. Added procedure for installing NMC using Azure Resource Manager, in Installing the Nasuni Filer on the Azure Platform. Clarified that displayed size might differ from external size indications, in Administration Guide and other documents. Clarified the distinction between private cloud, customer-controlled public cloud, BYOC, and public cloud in many docs. Changed name of Private-Cloud-Getting-Started-Guide-Azure to GS-Guidefor-Azure-BYOC. Added link to NASUNI-FILER-MIB for SNMP support, in Administration Guide. Added NTFS Exclusive Mode to available permissions for volume, in Administration Guide and other documents. Created Upgrading Nasuni Filers to Use Case-Insensitive Volumes procedure. Clarified that changes to the Snapshot Retention setting go into effect when the next snapshot occurs, and that it is normal to temporarily see more snapshots than the Snapshot Retention setting would suggest, in Administration Guide and NMC Guide. Recovery Guide8.0 x

11 Release Notes for Nasuni Documentation Set Date (As Of) Changes Added detailed instructions in volume creation procedures about preferring case-insensitive CIFS volumes, in Administration Guide, Best Practices Guide, and Worksheets for Configuring NMC, Nasuni Filers, Volumes, and Shares. Added best practices for handling historical SIDs before adding data, in Administration Guide, Best Practices Guide, and NMC Guide. Removed references to fsck, since it is unnecessary with OS7, in Administration Guide, NMC Guide, Recovery Guide, Installing on Virtual. Recovery Guide8.0 xi

12 In the Event of a True Disaster Important: If this is a true disaster, and the original source Nasuni Filer is no longer available, proceed immediately to Downloading and Installing the Nasuni Filer Software on page 12. Introduction This document explains the steps for performing the Recovery process for restoring a Nasuni Filer. The Nasuni Filer allows data recovery from the cloud to be nearly instantaneous. In a recovery scenario, the Nasuni Filer can reduce the total time to recover data to approximately 15 minutes. Note: You can also recover the Nasuni Management Console. The procedure is similar. There are a number of reasons for performing a recovery of a Nasuni Filer, including: Changing virtual machine platforms (VMware, Microsoft Hyper-V, Microsoft Azure, Amazon EC2). Nasuni Hardware Appliance or virtual machine hardware refresh. Moving data around the world. Human error. Hardware and software failures. True disaster. With Nasuni s data services, your data is safely stored offsite in industry-leading data centers. Nasuni s system of automatic, scheduled snapshots protects your data, with no need for additional backups. Snapshots provide a full recovery image of your data, as frequently as every minute. This data is available at any time to any location with an Internet connection. Recovery Guide 1

13 Side Load and Recovery You can rapidly get access to your data. To recover the data stored on your Nasuni Filer, you follow the simple steps of downloading the Nasuni Filer software from Nasuni.com, installing the software, and then completing the Recovery process. If you have your encryption keys, the whole procedure takes about 15 minutes for a total recovery. Side Load and Recovery The Recovery process enables you to recover the Nasuni Filer after a true disaster, such as the loss of a data center. However, most of the time, customers perform the Recovery process in order to change from one platform to another. In such a situation, there is already an operational Nasuni Filer that contains active data in its cache. Performing the Recovery process results in a new Nasuni Filer that has an empty cache. The customer must then manually re-populate the new cache with data, which requires considerable inbound bandwidth from the cloud, and which can take days, weeks, or even months to complete. The Side Load feature enables you to transfer cache data directly from the original source decommissioned Nasuni Filer to the new destination Nasuni Filer. For more details, see Performing the Side Load process on page 27. Tip: While the Side Load process typically reduces the time necessary to populate the cache of a Nasuni Filer, this is not always the case. For example, situations that involve many small files might not experience significant time savings, due to the overhead of handling the metadata for each file. Considerations before Performing the Recovery Procedure Here are some considerations before performing the recovery procedure. Important: To perform a recovery procedure, one of the following must be true: The original source Nasuni Filer must have at least one local volume, and at least one snapshot of the local volume must have completed. A backup key must have been generated. See Appendix A, Backup Keys, on page 33. Warning: If the original source Nasuni Filer has any data in the cache that has not yet been protected in cloud storage, performing a recovery procedure can cause that data to be lost. Before proceeding, perform a manual snapshot (see step 15 on page 8) and ensure that there is no data in the cache. Important: Internet connectivity (HTTPS port 443) to the new destination Nasuni Filer is a prerequisite for setting up the Nasuni Filer, or to update software during the installation. Tip: Download your generated encryption keys to a safe location before shutting down the original source Nasuni Filer or performing a recovery procedure on the original source Nasuni Filer. See step 10 on page 6 for details. Recovery Guide 2

14 Overview of Recovery Process Warning: Do NOT save encryption key files to a volume on a Nasuni Filer. You will NOT be able to use these to recover data. This is NOT how to upload encryption keys to a Nasuni Filer. Note: If you are using a hardware appliance as the original source Nasuni Filer, notify Nasuni Technical Support to request a replacement appliance at support@nasuni.com. You can then continue with the following procedure, which allows you to install and operate a virtual appliance to access your data. Note: Downloading and executing the installation program for the virtual appliance is contingent upon the virtual platform you are using. Tip: Only the Admin user can perform the Side Load process. Tip: To perform the Side Load procedure, the original source Nasuni Filer must be: Running; Decommissioned; Using release 7.0 or above. Overview of Recovery Process The Recovery process consists of the following steps: Preparing the Original Source Nasuni Filer (if available) on page 4. Downloading any generated encryption keys. Removing the Nasuni Filer from control of the Nasuni Management Console (NMC). Performing snapshots. Recording information to configure the new destination Nasuni Filer. Preparing the new destination Nasuni Filer. Downloading and Installing the Nasuni Filer Software on page 12. Recovering the Nasuni Filer on page 15. Adding encryption keys. Rejoining any previously joined Active Directory or LDAP domains. Adding the Nasuni Filer to the control of the Nasuni Management Console (NMC). Performing the Side Load process on page 27. Verifying the Volumes on page 31. Shutting Down the Original Source Nasuni Filer on page 32. Recovery Guide 3

15 Preparing the Original Source Nasuni Filer (if available) Preparing the Original Source Nasuni Filer (if available) If the original source Nasuni Filer is running and accessible, prepare the original source Nasuni Filer by following these steps: 1. Verify that the original source Nasuni Filer is installed and properly configured on your network. 2. Verify that the original source Nasuni Filer has at least one local volume, and that at least one snapshot on the original source Nasuni Filer has successfully completed on a local volume. Alternatively, verify that a backup key has been generated. See Appendix A, Backup Keys, on page To verify that the original source Nasuni Filer has at least one local volume, follow these steps: a. Click Volumes. The Volumes drop-down menu appears. b. Click All Volumes. The Volumes page appears. Figure 1-1: Volumes page. c. In the Local Volumes area, there should be at least one volume. 4. To verify that at least one snapshot on the original source Nasuni Filer has successfully completed on a local volume, follow these steps: a. Click Volumes. The Volumes drop-down menu appears. b. Click All Volumes. The Volumes page appears. In the Local Volumes area, at least one volume should have a Last Snapshot entry with a date and time. Recovery Guide 4

16 Preparing the Original Source Nasuni Filer (if available) 5. If performing the Side Load procedure, verify that the original source Nasuni Filer is running and not yet decommissioned by using a Web browser to navigate to the hostname or IP address of the Nasuni Filer. The Nasuni Filer should appear and not display the Filer Decommissioned message. 6. On the original source Nasuni Filer, record the information for volumes for later verification by following these steps: a. Click Volumes. The Volumes drop-down menu appears. b. Click All Volumes. The Volumes page appears. c. Record the names and other information for all volumes. 7. If running the Side Load procedure, record the hostname or IP address of the original source Nasuni Filer. To view the hostname, click Configuration, then select Network Configuration from the list. The Network Configuration page appears. Figure 1-2: Network Configuration page. The Host Name appears near the top of the page. 8. If running the Side Load procedure, record the username and password of an administrative user on the original source Nasuni Filer. 9. Remove the original source Nasuni Filer from control of the Nasuni Management Console (NMC) by following these steps: a. Click Services, then select Nasuni Management Console from the list. The Nasuni Management Console page appears. Figure 1-3: Nasuni Management Console page. b. From the NMC Management is drop-down list, click disabled. c. Click Save. Recovery Guide 5

17 Preparing the Original Source Nasuni Filer (if available) 10. On the original source Nasuni Filer, download any generated encryption keys by following these steps: a. Click Configuration. From the drop-down list, click Encryption Keys. The Encryption Keys page appears. Figure 1-4: Encryption Keys page. b. Click Download Generated Keys. Depending on your browser, a message box might appear; if so, navigate to an appropriate folder and save this file. The key is saved with a.pgp extension. Safeguard this encryption key file. For more details, see Chapter 11 of the Nasuni Filer Administration Guide. You can download this guide at Warning: You MUST have the encryption keys for the original source Nasuni Filer in order to recover the Nasuni Filer. Warning: Do NOT save encryption key files to a volume on a Nasuni Filer. You will NOT be able to use these to recover data. This is NOT how to upload encryption keys to a Nasuni Filer. 11. If you escrowed any encryption keys with Nasuni, contact Nasuni Technical Support. Warning: You MUST have the encryption keys for the original source Nasuni Filer in order to recover the Nasuni Filer. 12. If the original source Nasuni Filer was under the control of the Nasuni Management Console (NMC), download the encryption keys for the NMC by following these steps: a. Click Console Settings, then click Encryption Keys in the left-hand column. The Encryption Keys page displays a list of encryption keys on the Nasuni Management Console. b. If the Nasuni Management Console s generated encryption key is available for download, on the Encryption Keys page, click Download Generated Key. The generated encryption key is saved in the form of a.pgp file. Safeguard this encryption key file. Recovery Guide 6

18 Preparing the Original Source Nasuni Filer (if available) 13. Obtain the Serial Number and Authorization Code for the original source Nasuni Filer. You use these in step 12 on page 19. There are several ways to obtain the Serial Number and Authorization Code: You can obtain the Serial Number and Authorization Code for the original source Nasuni Filer on the Account Serial Numbers page of the Nasuni Management Console. Otherwise, if you have the credentials to log in to your Nasuni.com account ( account.nasuni.com/account/login/), you can obtain the Serial Number and Authorization Code for the original source Nasuni Filer there. Otherwise, If you do not have these credentials, obtain the Serial Number and Authorization Code for the original source Nasuni Filer from the person who has the credentials. 14. If you have defined data migrations that you want to use after the disaster recovery, record information about the data migrations by following these steps: a. On the original source Nasuni Filer, click Services, then select View Migrations from the list. The Current Migrations page appears. Figure 1-5: Current Migrations page. For each migration in the list, the following information appears: Migration: The name of this migration. Source: The source for this migration. Target: The location on the Nasuni Filer to which the files are copied. Scheduled: Whether or not this migration is controlled by a migration schedule: Yes or No. Status: Current status of the overall migration run, such as: Running, Interrupted, Completed. Current Operation: Activity of the currently running migration. Est. Time: Time estimate for the currently running migration to complete. This estimate can be impacted by a variety of factors, and continually updates as the migration progresses. Est. Rate: Estimated data transfer rate for the currently running migration, in files per minute and in MB per second. Recovery Guide 7

19 Preparing the Original Source Nasuni Filer (if available) Progress: Number of files that have completed for the currently running migration compared to the total number of files to be migrated, as well as amount of data completed compared with the total amount of data to be migrated. For example, 50 of 100 files - 5 GB of 10 GB. b. For each migration, record this information to recreate the migration on the new destination Nasuni Filer. c. For scheduled migrations, click Services, then select View Schedules from the list. The Scheduled Migrations page appears. Figure 1-6: Scheduled Migrations page. Migrations that you have scheduled are displayed. d. For each scheduled migration, record this information to recreate the migration schedule on the new destination Nasuni Filer. 15. Perform snapshots on all volumes by following these steps: a. Click Volumes, then click All Volumes from the list. The Volumes page appears. Figure 1-7: Volumes page. b. For the volume that you want to take a snapshot of, click Take snapshot now. A message Snapshot requested appears. Click x to close the message box. Recovery Guide 8

20 Preparing the Original Source Nasuni Filer (if available) c. Return to the Home page. A chart of New Data in Cache (not yet protected) appears. Figure 1-8: New Data in Cache chart. d. Wait until the New Data in Cache chart shows no unprotected data. Tip: This process can take considerable time, depending on the size of the cache and the amount of changed and new data in the cache. Warning: If all snapshots have not completed, some data might not be protected in the cloud. 16. Perform the preparedr procedure on the original source Nasuni Filer by following these steps: a. Access the console for the original source Nasuni Filer. For the Nasuni Filer hardware appliance, use a keyboard and monitor attached to the hardware appliance. For the Nasuni Filer virtual machine, use the virtual machine console window. The console prompt appears. Figure 1-9: Console prompt. Recovery Guide 9

21 Preparing the Original Source Nasuni Filer (if available) b. Press Enter to access the Service menu. The login prompt appears. Enter the username and password. The login username is service, and the default password is service. The Service Menu appears. Figure 1-10: Service Menu. Note: For security, use the changepassword command to change the password for the service console. c. To prepare the original source Nasuni Filer for the Side Load process that is part of the recovery procedure, enter preparedr at the prompt. Warning: During the preparedr command procedure, the volumes on the original source Nasuni Filer are set to read-only and any necessary final snapshots are performed. This processing temporarily impacts access to data on this Nasuni Filer. The preparedr command runs. The following processing occurs: Figure 1-11: Result of preparedr command. CIFS services are stopped. All volumes on the original source Nasuni Filer are set to read-only. Final snapshots are performed in order to empty the cache of the original source Nasuni Filer. Note: The original source Nasuni Filer is not decommissioned at this point. d. After the preparedr command finishes, and displays the message that it is finished, to exit the console commands, enter quit. 17. If performing a Side Load procedure using the original source Nasuni Filer, DO NOT shut down the Nasuni Filer. Continue with Downloading and Installing the Nasuni Filer Software on page 12. Recovery Guide 10

22 Preparing the Original Source Nasuni Filer (if available) 18. If NOT performing a Side Load procedure, perform a shutdown of the original source Nasuni Filer by following these steps: a. Ensure that all data has been protected in cloud storage before shutting down the Nasuni Filer. b. Click Power on the navigation bar at the top of the page. The Shutdown Filer dialog box appears. Figure 1-12: Shutdown Filer dialog box. Note: To exit and return to the previous page, click the x at the top of the page, or click Cancel. c. Enter a Username (case-sensitive) and Password (case-sensitive) that has permission to perform this operation. d. Select Perform snapshot before shutting down. This option performs a snapshot before shutting down the Nasuni Filer. This ensures that data is fully protected in cloud storage before shutting down. However, this process can take considerable time, depending on the size of the cache and the amount of changed and new data in the cache. e. Click Shutdown. The message The system is shutting down. Click here to cancel the shutdown. appears at the top of the Home page. f. To stop the shutdown, click the hyperlink marked here. You have 60 seconds to cancel the shutdown. The message Shutdown cancelled at user request. appears at the top of the Home page. The shutdown stops. g. If you do not stop the shutdown, after 60 seconds, the Nasuni Filer shuts down and the Nasuni Filer user interface is no longer accessible. Continue with Downloading and Installing the Nasuni Filer Software on page 12. Recovery Guide 11

23 Downloading and Installing the Nasuni Filer Software Downloading and Installing the Nasuni Filer Software The first step in recovering is to download and install the Nasuni Filer software on the new destination Nasuni Filer. To download the Nasuni Filer software from the Nasuni Web site: 1. If you have not already done so, obtain the Serial Number and Authorization Code for the original source Nasuni Filer. You use these in step 12 on page 19. There are several ways to obtain the Serial Number and Authorization Code: You can obtain the Serial Number and Authorization Code for the original source Nasuni Filer on the Account Serial Numbers page of the Nasuni Management Console. Otherwise, if you have the credentials to log in to your Nasuni.com account ( account.nasuni.com/account/login/), you can obtain the Serial Number and Authorization Code for the original source Nasuni FIler there. Otherwise, if you do not have these credentials, obtain the Serial Number and Authorization Code for the original source Nasuni FIler from the person who has the credentials. 2. Launch your Web browser. 3. Log in to your Nasuni account Web site ( and click Downloads. The Downloads page appears. Figure 1-13: Downloads page. Recovery Guide 12

24 Downloading and Installing the Nasuni Filer Software 4. Select the appropriate format for your virtual environment from these choices: OVF FORMAT: OVF format is appropriate for VMware ESXi 5.5 and above environments. HYPER-V FORMAT: Hyper-V format is appropriate for Microsoft Hyper-V environments. Note: There are two versions of the Microsoft Hyper-V software available: 2012 and pre (2008 R2 SP1). Select the appropriate version for your Microsoft Hyper-V environment. 5. Download the Nasuni Filer software appropriate for your platform. Regardless of which version of the Nasuni Filer software that you used originally, you can download the latest version. Note: You can perform the Recovery process to the same version of the software that you were running, or to a newer version than you were running, but not to an older version. Note: If you already have the software installation file, you do not have to download it again. However, the software installation file must not be older than the version you are recovering. 6. Download the Nasuni Filer software.zip file to a location on your local drive. The amount of time to download the Nasuni Filer software file depends on your Internet connection. The file is approximately 600 MB in size. 7. Unzip the Nasuni Filer software file. 8. Install the Nasuni Filer. For details of installation on a virtual platform, see Installing the Nasuni Filer on Virtual Platforms. You can download this guide at documentation. Recovery Guide 13

25 Downloading and Installing the Nasuni Filer Software 9. Launch the Nasuni Filer. The Nasuni Filer screen appears with a plain white bar on the bottom that indicates the progress of the installation. Figure 1-14: Nasuni Filer installation progress screen. 10. After a few moments, the Nasuni Filer console screen appears, including the initial IP address. Figure 1-15: Nasuni Filer console screen. Tip: If you ever must log into the console service screen, press Enter and sign in. The default login username is service, and the default password is service. 11. Record the Assigned IP Address displayed on the console screen. You use this to access the Nasuni Filer user interface using a Web browser. Recovery Guide 14

26 Recovering the Nasuni Filer Recovering the Nasuni Filer Now that the Nasuni Filer software is installed, you can recover the new destination Nasuni Filer. Important: Internet connectivity (HTTPS port 443) is a prerequisite for setting up the Nasuni Filer, or to update software during the installation. Follow this procedure to recover the Nasuni Filer: 1. Open a Web browser and enter the IP address of the Nasuni Filer using this command: address>:8443 where <IP address> is the IP address from step 11 on page 14. When you attempt to access the Nasuni Filer Home page for the first time, a message might appear indicating that the security certificate is not trusted. You can still access the site to proceed with the initial configuration procedure. 2. The Enter the Network Parameters for this Filer page appears. Figure 1-16: Enter the Network Parameters for this Filer page. 3. In the Hostname or FQDN box, a default hostname for the Nasuni Filer appears. You can accept the default hostname or change it to a customized hostname. The name that you enter is the name that you provide to users so they can access the Nasuni Filer. You can use ASCII letters a through z, digits 0 through 9, and hyphens. Note: The Nasuni Filer attempts to register the hostname in the DNS server, so that users can access this host by name. 4. In the Network Interface Settings area, for each Device in the list, select the Traffic Group from the drop-down list. Figure 1-17: Network Interface Settings area. You can define your own traffic groups. See step 5 below. Recovery Guide 15

27 Recovering the Nasuni Filer 5. Also in the Network Interface Settings area, to configure each Traffic Group, click Edit beside the Traffic Group. The Network Settings page appears. Figure 1-18: 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 might not be enabled on more than one traffic group. If you select Static, you must provide Network Interface Settings and System Settings. See your IT administrator for assistance. Enter the following information: Enter the static IP address in the IP Address text box. The address of a static device must not already be present on the network. The Nasuni Filer verifies this and displays an error if a collision is detected. Note: If you define more than one static device, the Nasuni Filer checks that the subnets specified do not appear more than once. 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. This gateway is used to return traffic for clients outside one of the Nasuni Filer's local networks that do not use the default gateway. In the Gateway text box, enter the IP address for the gateway. Click OK to use these values. Click Cancel to exit this page without making any changes. Recovery Guide 16

28 Recovering the Nasuni Filer 6. In the System Settings area, from the Settings Source drop-down list, select either Static, DHCP, or DHCP with custom DNS as the source for system-wide configuration. Figure 1-19: System Settings page. DHCP (Dynamic Host Configuration Protocol): Provides a network IP address for a host on an IP network automatically. The Default Gateway, Search Domain, Primary DNS Server, and Secondary DNS Server fields become unavailable. DHCP with custom DNS: Provides a network IP address for a host on an IP network automatically. The Default Gateway field becomes unavailable. Enter the following information: Enter one or more local search domains in the Search Domain text box, each separated by a space. You must enter valid hostnames. You can use search domains to avoid typing the complete address of domains that you use frequently. The search domains that you enter are automatically appended to names that you specify for purposes such as Active Directory configuration, data migration sources, HTTPS proxy, and NTP server. For example, if you specify the search domain mycompany.com, then typing server1 for one of these purposes would connect to server1.mycompany.com. Enter the IP address for your primary DNS server in the Primary DNS server text box. You must enter a valid hostname or IP address. Enter the IP address for your secondary DNS server in the Secondary DNS server text box (if applicable). You must enter a valid hostname or IP address. Recovery Guide 17

29 Recovering the Nasuni Filer Static: Address information must be entered manually. Enter the following information: Enter a default gateway address in the Default Gateway text box. The gateway address must match a subnet of a defined static network. Enter one or more local search domains in the Search Domain text box, each separated by a space. You must enter valid hostnames. You can use search domains to avoid typing the complete address of domains that you use frequently. The search domains that you enter are automatically appended to names that you specify for purposes such as Active Directory configuration, data migration sources, HTTPS proxy, and NTP server. For example, if you specify the search domain mycompany.com, then typing server1 for one of these purposes would connect to server1.mycompany.com. Enter the IP address for your primary DNS server in the Primary DNS server text box. You must enter a valid hostname or IP address. Enter the IP address for your secondary DNS server in the Secondary DNS server text box (if applicable). You must enter a valid hostname or IP address. 7. To configure a proxy in order to reach HTTPS resources on the Internet, select the Configure A Proxy check box. 8. Click Continue to proceed. 9. The Review the Network Settings page appears. Figure 1-20: Review the Network Settings page. To accept the network settings, click Confirm. To return to the previous page to change network settings, click Back. Recovery Guide 18

30 Recovering the Nasuni Filer 10. The Configuring Network Settings page appears. Figure 1-21: Configuring Network Settings page. 11. You are automatically directed to the specified IP address (or you can click the link here ). The Enter your serial number and authorization code wizard page appears. Figure 1-22: Enter your serial number and authorization code wizard page. 12. Enter the Filer Serial Number and Authorization code, as recorded previously in step 13 on page 7. Click Continue to proceed. Note: If the administrative account for this Nasuni Filer was reset (such as, for a forgotten password), and this Nasuni Filer was under the control of the Nasuni Management Console, and if you are using the Filer Serial Number for that prior installation, you must wait 1 hour from the time that you reset the administrative account for the Nasuni Filer before entering the Filer Serial Number and Authorization code and clicking Continue. Recovery Guide 19

31 Recovering the Nasuni Filer 13. The Perform Disaster Recovery on existing Filer page appears. Figure 1-23: Perform Disaster Recovery on existing Filer page. Enter Perform Disaster Recovery in the Confirmation text box, then click Continue to proceed. Note: After performing this step, the original source Nasuni Filer is decommissioned. Recovery Guide 20

32 Recovering the Nasuni Filer 14. The second Perform Disaster Recovery on existing Filer page appears. Figure 1-24: Second Perform Disaster Recovery on existing Filer page. If you escrowed your encryption keys with Nasuni, and you need Nasuni to de-escrow your encryption keys, select Yes from the drop-down list. Contact Nasuni to receive your encryption keys, then enter your recovered encryption keys, and click Continue. Continue with step 16 on page 22. Important: If you have previously escrowed your encryption keys with Nasuni, and you use these escrowed encryption keys as part of the Recovery process, you MUST re-escrow those encryption keys with Nasuni if you want those encryption keys to continue to be escrowed with Nasuni. After the recovery is complete, the Nasuni Filer treats all encryption keys as if they were not created by this Nasuni Filer. For details, see, Escrowing Encryption Keys with Nasuni on page 353 of the Nasuni Filer Administration Guide. You can download this guide at Otherwise, select No from the drop-down list, then click Continue. 15. If you selected No, the Upload Encryption Keys page appears. Figure 1-25: Upload Encryption Keys page. a. Click Choose File to navigate to your encryption key file. This is the.pgp file that you saved in step b on page 6. Recovery Guide 21

33 Recovering the Nasuni Filer b. Enter the Key Passphrase if necessary, then click Upload Key(s). All uploaded encryption keys should be at least 2048 bits long. c. If several encryption key files are necessary, this page could appear several times. 16. The Ready to perform disaster recovery! page appears. Figure 1-26: Ready to perform disaster recovery! page. Click Continue. Recovery of the Nasuni Filer begins. 17. After recovery, the Filer Recovery Complete page appears. Figure 1-27: Filer Recovery Complete page. Recovery Guide 22

34 Recovering the Nasuni Filer 18. Click Continue. The Accept the Terms of Service and License Agreement page appears. Figure 1-28: Accept the Terms of Service and License Agreement page. You can print or download a copy of the Terms of Service and License Agreement by clicking the appropriate icon. Select I accept the Terms of Service, then click Continue. Recovery Guide 23

35 Recovering the Nasuni Filer 19. The Enter a username and password for Administration of this Filer page appears. Figure 1-29: Enter a username and password for Administration of this Filer page. a. Set up an administrator for the new destination Nasuni Filer by creating a Username (casesensitive) and a Password (case-sensitive). An indicator of password strength appears. Although password strength is not enforced, you should use strong passwords. b. Click Continue. 20. The Recovery process is complete. The Configuration Complete page appears. Figure 1-30: Configuration Complete page. You can reboot the Nasuni Filer, or click the link here to proceed directly to the Login page. Note: When a reboot is requested, a notification is logged that the reboot was requested and by whom the reboot was requested. Recovery Guide 24

36 Recovering the Nasuni Filer 21. The Nasuni Filer becomes available in a few moments. The Login page appears. Figure 1-31: Nasuni Filer Login page. a. Log in to the Nasuni Filer with the Username (case-sensitive) and Password (case-sensitive). b. Click Log in. Important: If the previous Nasuni Filer was in Active Directory mode, you must re-join Active Directory to maintain ACL support. Similarly, if the previous Nasuni Filer was in LDAP mode, you must re-join LDAP. With the new instance of the Nasuni Filer running, you have regained access to your volumes and data. You can access volumes and data using the CIFS shares, NFS exports, or FTP directories that you created before the recovery. Folders and files are available. Important: If this Nasuni Filer used a CIFS migration source to perform data migrations, you might need to manually reconnect to that CIFS migration source. See Configuring a CIFS Migration Source on page 240 of the Nasuni Filer Administration Guide. You can download this guide at Tip: If this Nasuni Filer previously accessed a volume with custom permissions for Remote Access, you must explicitly set the permissions of that volume for this Nasuni Filer. Important: If you have previously escrowed your encryption keys with Nasuni, and you used these escrowed encryption keys as part of the Recovery process, you MUST re-escrow those encryption keys with Nasuni if you want those encryption keys to continue to be escrowed with Nasuni. After the recovery is complete, the Nasuni Filer treats all encryption keys as if they were not created by this Nasuni Filer. For details, see, Escrowing Encryption Keys with Nasuni on page 353 of the Nasuni Filer Administration Guide. You can download this guide at Recovery Guide 25

37 Recovering the Nasuni Filer Tip: A best practice for Nasuni Filers is to join an Active Directory or LDAP domain as soon as recovery is complete. If the previous Nasuni Filer was in Active Directory or LDAP mode, re-join Active Directory or LDAP. If the previous Nasuni Filer has not previously joined any domain, see Joining a Nasuni Filer (that has not previously joined any domain) to a domain (for Nasuni Filers running versions before 7.8) on page 339 of the Nasuni Filer Administration Guide. You can download this guide at Tip: If this Nasuni Filer was under the control of the Nasuni Management Console, return it to the control of the Nasuni Management Console. Click Services, then select Nasuni Management Console from the list. From the NMC Management is dropdown list, select enabled, then click Save. Tip: If this Nasuni Filer previously connected to a remote volume, you must manually reconnect to the remote volume after recovery. Note: For any volume that is either Pending Delete or Pending Delete Approval, the pending deletions might be cancelled after the volume's Nasuni Filer is recovered. 22. If any of the original source Nasuni Filer s CIFS shares had Shared Links defined, and Shared Links Global User is not enabled for the share, these links must be regenerated. Use Web Access to view links that must be regenerated, and regenerate them. The items requiring regeneration look like this: Figure 1-32: Shared item requiring regeneration. Note: Internal links do not need to be regenerated. Recovery Guide 26

38 Performing the Side Load process Performing the Side Load process Important: You can only perform the Side Load procedure as part of the entire Recovery procedure. In particular, before performing the Side Load procedure, you must perform the procedure Preparing the Original Source Nasuni Filer (if available) on page 4, which includes running the preparedr command on the console of the original source Nasuni Filer, as described in step 16 on page 9. Also, before performing the Side Load procedure, you must perform the procedure Recovering the Nasuni Filer on page 15, which includes the original source Nasuni Filer becoming decommissioned, as described in step 13 on page 20. Most of the time, customers perform the Recovery process in order to upgrade from one piece of hardware to another. In such a situation, there might actually be a working source Nasuni Filer that contains active data in the cache. However, performing the Recovery process results in a new destination Nasuni Filer that has an empty cache. The customer must often manually re-populate the new cache with data, which can require considerable inbound bandwidth from the cloud, and which can take days, weeks, or even months to complete. The Side Load feature enables you to transfer cache data directly from the original source Nasuni Filer to the new destination Nasuni Filer. Tip: You can only perform the Side Load procedure as part of performing the Recovery procedure. Tip: Only one Side Load process is permitted at a time for each Nasuni Filer. Tip: Only the Admin user can perform the Side Load process. Tip: The original source Nasuni Filer must be: Running; Decommissioned; Using release 7.0 or above. Warning: If the total data available on the original source Nasuni Filer exceeds the available cache space on the new destination Nasuni Filer, you receive a warning message and notification. You can configure Notifications to notify you by when the Side Load process completes. Recovery Guide 27

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

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

41 Performing the Side Load process 2. To pause a running Side Load process, click Pause. The Side Load process pauses indefinitely. The bar graph label changes to Paused. Figure 1-35: Side Load - Status page, paused. To continue with the Side Load process after a pause, click Resume. The Side Load process continues. The bar graph label changes to Running. 3. To cancel the Side Load process, click Cancel. The Cancel Side Load dialog box appears. Figure 1-36: Cancel Side Load dialog box. To cancel the Side Load process, click Continue. If the Side Load process is canceled, the bar graph label changes to Canceled. Figure 1-37: Side Load status page, canceled. 4. When the Side Load process completes, the Complete label appears on the bar graph. Tip: Record any information you want to retain from the screen before clicking Done. 5. Click Done. Recovery Guide 30

42 Verifying the Volumes Verifying the Volumes After completing the recovery procedure, you can verify the volumes on the new destination Nasuni Filer. This compares the names and other information of current volumes with the names and other information of volumes previously recorded in step 6 on page 5. To verify the volumes, follow these steps: 1. On the new destination Nasuni Filer, click Volumes. The Volumes drop-down menu appears. 2. Click All Volumes. The Volumes page appears. 3. Compare the names and other information of all volumes with those previously recorded. Recovery Guide 31

43 Shutting Down the Original Source Nasuni Filer Shutting Down the Original Source Nasuni Filer When you are satisfied that the original source Nasuni Filer is no longer necessary, you can shut down the original source Nasuni Filer, if it has not been shut down already. To shut down the original source Nasuni Filer, follow these steps: 1. Ensure that all data has been protected in cloud storage. 2. On the navigation bar at the top of the page, click Power. The Shutdown Filer dialog box appears. Figure 1-38: Shutdown Filer dialog box. Note: To exit and return to the previous page, click the x at the top of the page, or click Cancel. 3. Enter a Username (case-sensitive) and Password (case-sensitive) that has permission to perform this operation. 4. Select Shut down immediately. Since all data has already been protected in cloud storage, it is not necessary to perform a snapshot. Also, since this Nasuni Filer is no longer necessary, rebooting is not needed. 5. Click Shutdown. The message The system is shutting down. Click here to cancel the shutdown. appears at the top of the Home page. 6. To stop the shutdown, click the hyperlink marked here. You have 60 seconds to cancel the shutdown. The message Shutdown cancelled at user request. appears at the top of the Home page. The shutdown stops. 7. If you do not stop the shutdown, after 60 seconds, the original source Nasuni Filer shuts down and the original source Nasuni Filer user interface is no longer accessible. Recovery Guide 32

44 Appendix A: Backup Keys Backup Keys A backup key is a type of encryption key that is used to ensure that it is possible to recover a Nasuni Filer that has no owned volumes. Without a backup key, it is not possible to recover a Nasuni Filer that has no owned volumes. If a Nasuni Filer has no owned volumes and no backup key, after 2 days, the following notification is sent: Because this Filer has no volumes or backup keys, you cannot currently perform a disaster recovery on this Filer. On the Encryption Keys page, you can generate a backup key to enable disaster recovery. You can generate a backup key on the Encryption Keys page. Figure A-1: Encryption Keys page. Important: The time to generate an encryption key can vary widely, depending on the hardware (real or virtual) that the Nasuni Filer is executing on. Encryption keys are generated in the background, so as to not block use of the Nasuni Filer during generation. Recovery Guide8.0 33

45 Backup Keys The Generate Key button is available if the Nasuni Filer has no owned volumes and no backup key. Alternatively, you can upload an encryption key for use as a backup key. If a backup key has been generated or uploaded for a Nasuni Filer, the backup key appears in the list of encryption keys on the Encryption Keys page. Figure A-2: Encryption Keys page. A generated backup key is automatically escrowed with Nasuni. You can also download a generated backup key and safeguard it yourself. If the backup key is the only encryption key for the Nasuni Filer, you cannot delete the backup key. When recovering the Nasuni Filer using a backup key, indicate whether or not you need Nasuni to provide an escrowed backup key on the second Perform Disaster Recovery on existing Filer page. Then obtain your backup key, either from Nasuni or from your own safekeeping, and upload your backup key on the Upload Encryption Keys page. Recovery Guide8.0 34