Testing and Restoring the Nasuni Filer in a Disaster Recovery Scenario

Transcription

1 Testing and Restoring the Nasuni Filer in a Disaster Recovery Scenario Version 7.8 April 2017 Last modified: July 17, Nasuni Corporation All Rights Reserved

2 Document Information Testing Disaster Recovery Version 7.8 April 2017 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 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 clients.

3 Contents Testing Disaster Recovery Purpose Prerequisites Simulating a Disaster Scenario Scenario Overview Considerations for the Nasuni Management Console Downloading Encryption Keys Simulating a Disaster Downloading and Installing the Nasuni Filer Software Configuring the Nasuni Filer Recovering the Nasuni Filer Side Load Starting the Side Load process Viewing and controlling the Side Load process Index Testing Disaster Recovery iii

4 Purpose This document explains the steps for testing the Disaster Recovery process for restoring the Nasuni Filer in a simulated Disaster Recovery scenario. The Nasuni Filer allows data recovery from the cloud to be nearly instantaneous. In a Disaster Recovery scenario, the Nasuni Filer can reduce the total time to recover data to approximately 15 minutes. The Disaster Recovery test process consists of: Downloading generated encryption keys. Identifying the account with which the Nasuni Filer is associated. Re-installing the Nasuni Filer. Performing Side Load procedure, if available. The Side Load feature enables you to transfer cache data directly from the source Nasuni Filer to the new Nasuni Filer. We assume that you are performing this test on a Nasuni Filer installed on a virtual machine. We further assume that you are testing the Disaster Recovery process using generated encryption keys. Prerequisites Before you begin testing the Disaster Recovery procedure, you should meet the following prerequisites: The Nasuni Filer is installed and properly configured on your network. Data is copied to a volume in the Nasuni Filer. At least one snapshot has been successfully completed on a volume with data. If performing the Side Load procedure, the source Nasuni Filer must be running, not yet decommissioned, and using release 7.0 or above. The Side Load feature enables you to transfer cache data directly from the source Nasuni Filer to the new Nasuni Filer. Testing Disaster Recovery 1

5 Simulating a Disaster Scenario Simulating a Disaster Scenario This section describes how to simulate a disaster scenario for the Nasuni Filer, to illustrate the process of disaster recovery. Important: You must have a local volume to perform a disaster recovery procedure. Note: You can also simulate a disaster scenario for the Nasuni Management Console. The procedure is similar. Scenario Overview This section explains how to simulate a disaster recovery by shutting down the Nasuni Filer. Before you shut down the Nasuni Filer, make sure you know the names of your volumes and the data stored in them. After the disaster recovery is complete, you can confirm that your new Nasuni Filer has the correct volumes and associated data. Note: When a reboot is requested, a notification is logged that the reboot was requested and by whom the reboot was requested. Considerations for the Nasuni Management Console If this Nasuni Filer is under the control of the Nasuni Management Console, first remove the Nasuni Filer from the control of the Nasuni Management Console. Click Services, then select Nasuni Management Console from the list. Select disabled from the NMC Management is drop-down list, then click Save. Testing Disaster Recovery 2

6 Simulating a Disaster Scenario Downloading Encryption Keys On the source Nasuni Filer, follow this procedure to download your generated encryption keys: 1. Click Configuration, then select Encryption Keys from the list. The Encryption Keys page appears. Figure 1-1: Encryption Keys page. 2. Click Download Generated Keys. Depending on your browser, a message box may appear; if so, navigate to an appropriate folder and save this file. The key is saved with a.pgp extension. For more details, see Chapter 11 of the Nasuni Filer Administration Guide. You can download this guide at Simulating a Disaster Follow this procedure to simulate a disaster scenario: 1. Click Status, then select Subscription Status from the list. The Subscription Status page appears. Figure 1-2: Subscription Status page. The following subscription information is displayed: Account Name: Name of the account. Serial Number: The serial number for this subscription. Note the Account Name and the Serial Number for this Nasuni.com account. You can also obtain serial numbers on the Account Status page of the Nasuni Management Console. Testing Disaster Recovery 3

7 Simulating a Disaster Scenario 2. If you have defined data migrations that you want to use after the disaster recovery, ensure that you record information about the data migrations before shutting down the Nasuni Filer. Click Services, then click View Migrations. 3. If performing a Side Load procedure using the source Nasuni Filer, DO NOT shut down the Nasuni Filer. Continue with Downloading and Installing the Nasuni Filer Software on page If NOT performing a Side Load procedure, perform a shutdown of the original Nasuni Filer by following these steps: a. It is important to ensure that all data has been protected in cloud storage before shutting down the Nasuni Filer. You can do this manually by performing snapshots on all volumes: select each volume from the Volumes list, then click Take snapshot now. Wait until the New Data in Cache (not yet protected) chart on the Home page shows that there is no unprotected data. This process can take considerable time, depending on the size of the cache and the amount of changed and new data in the cache. Alternatively, during the shutdown process you can specify performing a snapshot before shutting down. b. Click Power on the navigation bar at the top of the page. The Shutdown Filer dialog box appears. Figure 1-3: 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. Testing Disaster Recovery 4

8 Simulating a Disaster Scenario 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, the Nasuni Filer shuts down and the Nasuni Filer user interface is no longer accessible. At this point, the Nasuni Filer that has been shut down simulates a Nasuni Filer after a disaster. The remainder of this document describes how to recover from a disaster. Continue with Downloading and Installing the Nasuni Filer Software on page 6. Testing Disaster Recovery 5

9 Downloading and Installing the Nasuni Filer Software Downloading and Installing the Nasuni Filer Software The first step in recovering from a disaster is to download and install the Nasuni Filer software. To download the Nasuni Filer software from the Nasuni Web site: 1. Obtain the Serial Number and Authorization Code for your Nasuni Filer. You use these in step 3 on page 16. 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 there. If you do not have these credentials, obtain the Serial Number and Authorization Code from the person who has the credentials. You can also obtain the Serial Number and Authorization Code on the Account Status page of the Nasuni Management Console. 2. Download the Nasuni Filer software appropriate for your platform. Regardless of which version of the Nasuni Filer software that you used originally, you can download the latest version. Note: You can perform the disaster recovery process to the same version of the software that you were running, or to a newer version than you were running, but not to an older version. 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. 3. Unzip the Nasuni Filer software file. 4. Install the Nasuni Filer. For details, see Installing the Nasuni Filer on Virtual Platforms. You can download this guide at Testing Disaster Recovery 6

10 Downloading and Installing the Nasuni Filer Software 5. 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-4: Nasuni Filer installation progress screen. Tip: You can force a file system check (fsck) by holding down the Shift key during this screen. When the file system check (fsck) is done, the usual processing continues. 6. After a few moments, the Nasuni Filer console screen appears, including the initial IP address. Figure 1-5: 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. 7. Record the Assigned IP Address displayed on the console screen. Testing Disaster Recovery 7

11 Configuring the Nasuni Filer Configuring the Nasuni Filer Now that the Nasuni Filer software is installed, you must configure the new Nasuni Filer. Follow this procedure to configure 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. When you attempt to access the Nasuni Filer Home page for the first time, a message may appear indicating that the security certificate is not trusted. You can still access the site to proceed with the initial configuration procedure. Testing Disaster Recovery 8

12 Configuring the Nasuni Filer 2. The Enter the Network Parameters for this Filer page appears. Figure 1-6: Enter the Network Parameters for this Filer page. 3. In the Host Name 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 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. Testing Disaster Recovery 9

13 Configuring the Nasuni Filer 4. In the Network Interface Settings area, for each Device in the list, select the Traffic Group from the drop-down list. Figure 1-7: Network Interface Settings area. You can define your own traffic groups. See step 5 below. 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-8: Network Settings page. From the Network Type drop-down list, select either Static or DHCP. If you select DHCP (Dynamic Host Configuration Protocol), the IP Address, Netmask, and MTU Value fields become unavailable. Note: DHCP may not be enabled on more than one traffic group. If you select Static, you must provide Network Interface Settings and System Settings. See your IT administrator for assistance. Enter the following information: Enter the static IP address in the IP Address text box. The address of a static device must not already be present on the network. The Nasuni Filer verifies this and displays an error if a collision is detected. Note: If you define more than one static device, the Nasuni Filer checks that the subnets specified do not appear more than once. If this is a high-availability hardware appliance Nasuni Filer, enter the Node 1 IP Address and the Node 2 IP Address in their text boxes. Enter a netmask address in the Netmask text box. Testing Disaster Recovery 10

14 Configuring the Nasuni Filer 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. 6. In the System Settings area, from the Settings Source drop-down list, select either Static or DHCP as the source for system-wide configuration. Figure 1-9: 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. Testing Disaster Recovery 11

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

16 Configuring the Nasuni Filer 9. The Review the Network Settings page appears. Figure 1-10: Review the Network Settings page. To accept the network settings, click Confirm. To return to the previous page to change network settings, click Back. 10. The Configuring Network Settings page appears. Figure 1-11: Configuring Network Settings page. Testing Disaster Recovery 13

17 Configuring the Nasuni Filer 11. For high availability Nasuni Filer hardware appliances, the Filer HA-Pair Synchronization page appears. Figure 1-12: Filer HA-Pair Synchronization page. It can take some time for the synchronization process to complete. When the process completes, click Continue. 12. You are automatically directed to the specified IP address (or you can click the link here ). Testing Disaster Recovery 14

18 Recovering the Nasuni Filer Recovering the Nasuni Filer After configuring the network settings for the new Nasuni Filer, you must enter your Nasuni.com serial number and authorization code, accept the end-user license agreement, and enter a user name and password for the user who is a Filer Administrator of the Nasuni Filer. Important: Internet connectivity (HTTPS port 443) is a prerequisite for setting up the Nasuni Filer, or to update software during the installation. To recover your Nasuni Filer, follow these steps: 1. If you are performing a Side Load procedure, prepare the source Nasuni Filer by following these steps: a. Access the console for the 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-13: Console prompt. 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-14: Service Menu. Note: For security, use the changepassword command to change the password for the service console. c. To prepare the source Nasuni Filer for the Side Load process that is part of the disaster recovery procedure, enter preparedr at the prompt. Warning: During the preparedr command procedure, the volumes on the 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. Testing Disaster Recovery 15

19 Recovering the Nasuni Filer The preparedr command runs. The following processing occurs: Figure 1-15: Result of preparedr command. CIFS services are stopped. All volumes on the source Nasuni Filer are set to read-only. Final snapshots are performed in order to empty the cache of the source Nasuni Filer. Note: The source Nasuni Filer is not decommissioned at this point. This occurs after you perform step 4 on page 17. d. After the preparedr command finishes, and displays the message that it is finished, to exit the console commands, enter quit. 2. On the current Nasuni Filer, open the URL obtained in step 12 on page 14. The Enter your serial number and authorization code wizard page appears. Figure 1-16: Enter your serial number and authorization code wizard page. 3. On the current Nasuni Filer, enter a Filer Serial Number and Authorization code, 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. Click Continue to proceed. Note: If this Nasuni Filer was reset, and this Nasuni Filer was under the control of the Nasuni Management Console, and if you are using the Filer Serial Number of a prior installation, you must wait 1 hour from the time that you reset the Nasuni Filer before entering the Filer Serial Number and Authorization code and clicking Continue. Testing Disaster Recovery 16

20 Recovering the Nasuni Filer 4. The Perform Disaster Recovery on existing Filer page appears. Figure 1-17: 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 source Nasuni Filer is decommissioned. 5. The second Perform Disaster Recovery on existing Filer page appears. Figure 1-18: Second Perform Disaster Recovery on existing Filer page. If you escrowed your encryption keys with Nasuni, and do not have your encryption keys, and you need Nasuni to de-escrow your encryption keys, select Yes from the drop-down list. Contact Nasuni to receive your encryption keys, then enter your recovered encryption keys and click Continue. Otherwise, select No from the drop-down list, then click Continue. Important: If you have previously escrowed your encryption keys with Nasuni, and you use these escrowed encryption keys as part of the disaster recovery process, you MUST re-escrow those encryption keys with Nasuni if you want those encryption keys to Testing Disaster Recovery 17

21 Recovering the Nasuni Filer continue to be escrowed with Nasuni. After the disaster recovery is complete, the Nasuni Filer treats all encryption keys as if they were not created by this Nasuni Filer. For details, see, Escrowing Encryption Keys with Nasuni on page 320 of the Nasuni Filer Administration Guide. You can download this guide at documentation. 6. If you selected No, the Upload Encryption Keys page appears. Figure 1-19: Upload Encryption Keys page. Click Choose File to navigate to your encryption key file, enter the Key Passphrase if necessary, then click Upload Key(s). All uploaded encryption keys should be at least 2048 bits long. If several encryption key files are necessary, this page could appear several times. 7. The Ready to perform disaster recovery! page appears. Figure 1-20: Ready to perform disaster recovery! page. Click Continue. Disaster recovery of the Nasuni Filer begins. 8. After recovery, the Filer Recovery Complete page appears. Figure 1-21: Filer Recovery Complete page. Testing Disaster Recovery 18

22 Recovering the Nasuni Filer 9. Click Continue. The Accept the Terms of Service and License Agreement page appears. Figure 1-22: 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. Testing Disaster Recovery 19

23 Recovering the Nasuni Filer 10. The Enter a username and password for Administration of this Filer page appears. Figure 1-23: Enter a username and password for Administration of this Filer page. Set up your account by creating a Username (case-sensitive) and a Password (case-sensitive). An indicator of password strength appears. Although password strength is not enforced, you should use strong passwords. Click Continue. 11. The recovery and restoration process is complete. The Configuration Complete page appears. Figure 1-24: Configuration Complete page. You can reboot the Nasuni Filer, or click the link here to proceed directly to the Login page. Testing Disaster Recovery 20

24 Recovering the Nasuni Filer 12. The Nasuni Filer becomes available in a few moments. The Login page appears. Figure 1-25: Nasuni Filer Login page. Log in to the Nasuni Filer with your Username (case-sensitive) and Password (case-sensitive). Click Log in. Important: If the previous Nasuni Filer was in Active Directory mode, you must re-join Active Directory to maintain ACL support. 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 disaster. Folders and files are available. Important: If this Nasuni Filer used a CIFS migration source to perform data migrations, you might need to manually reconnect to that CIFS migration source. See Configuring a CIFS Migration Source on page 215 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 disaster recovery process, you MUST re-escrow those encryption keys with Nasuni if you want those encryption keys to continue to be escrowed with Nasuni. After the disaster recovery is complete, the Nasuni Filer treats all encryption keys as if they were not created by this Nasuni Filer. For details, see, Escrowing Encryption Keys with Nasuni on page 320 of the Nasuni Filer Administration Guide. You can download this guide at documentation. Tip: A best practice for Nasuni Filers is to join an Active Directory or LDAP domain as soon as disaster recovery is complete. If the previous Nasuni Filer was in Active Directory or LDAP mode, re-join Active Directory or LDAP by clicking Save Settings. If the Testing Disaster Recovery 21

25 Recovering the Nasuni Filer 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 305 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. Select disabled from the NMC Management is drop-down list, then click Save. 13. After verifying that the new Nasuni Filer is running and includes all the expected data, you can delete the old Nasuni Filer. If any of the Nasuni Filer s CIFS shares had Shared Links defined, 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-26: Shared item requiring regeneration. Testing Disaster Recovery 22

26 Side Load Side Load Nasuni supports a Disaster Recovery (DR) process that enables you to recover the Nasuni Filer after a true disaster, such as the loss of a data center. However, most of the time, clients perform the Disaster Recovery process in order to upgrade from one piece of hardware to another. In such a situation, there is a working Nasuni Filer in your data center that contains active data in the cache. Performing the Disaster Recovery process results in a new Nasuni Filer that has an empty cache. The client often then re-populates the new cache with data, which can require considerable inbound bandwidth from the cloud, and which can take days, weeks, or even months to complete. The Side Load feature enables you to transfer cache data directly from the source Nasuni Filer to the new Nasuni Filer. The source Nasuni Filer must already be decommissioned. Tip: You cannot perform the Side Load procedure apart from performing the Disaster 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 source Nasuni Filer must be: Running; Decommissioned; Using release 7.0 or above. Warning: If the total data available on the source Nasuni Filer exceeds the available cache space on the new Nasuni Filer, you receive a warning message and notification. Important: Before performing the Side Load procedure, you must run the preparedr command on the console of the source Nasuni Filer as described in step 1 on page 15. You can configure Notifications to notify you by when the Side Load process completes. Testing Disaster Recovery 23

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

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

29 Side Load 2. To pause a running Side Load process, click Pause. The Side Load process pauses indefinitely. The bar graph label changes to Paused. Figure 1-29: 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-30: 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-31: Side Load status page, canceled. Tip: Record any information you want to retain from the screen before clicking Done. Testing Disaster Recovery 26

30 Side Load 4. When the Side Load process completes, the Complete label appears on the bar graph. Tip: Record any information you want to retain from the screen before clicking Done. 5. Click Done. Testing Disaster Recovery 27

31 Index 8443 port 8 account name 3 ACL 21 Active Directory 12, 21 Authorization Code 6 authorization code 16 console 15 console commands 16 creating password 20 username A C D decommissioned 1, 16, 17, 23, 24, 25 DHCP 10, 11, 12 network type 10, 11 disaster recovery encryption key 17 file 18 downloading software Nasuni.com account 6 encryption key disaster recovery 17 file 3 disaster recovery 18 encryption keys uploading 18 E F file encryption key 3 file disaster recovery 18 Filer Administrator 15 fsck 7 gateway traffic group 11 G H high availability network configuration 10 HTTPS proxy 12 IP address 10, 12 primary DNS server 12 secondary DNS server 12 I Testing Disaster Recovery 28

32 keys uploading 18 K M maximum transmission unit 11 MTU 11 N name account 3 Nasuni.com account downloading software 6 netmask 10 network configuration high availability 10 Network Time Protocol NTP 12 network type DHCP 10, 11 static 10, 11, 12 NTP Network Time Protocol 12 time server 12 P password creating 20 shutdown 4 strength 20 pausing Side Load 26 port preparedr 15, 16 preparedr command 15, 23 primary DNS 12 primary DNS server IP address 12 secondary DNS 12 secondary DNS server IP address 12 serial number 6, 16 setting up Nasuni Filer 15 shared link regenerating 22 shutdown 4, 5 password 4 power 4 username 4 shutdown window 5 Side Load 1, 23, 25 pausing 26 snapshot before shutdown 4 static network type 10, 11, 12 traffic group gateway 11 uploading encryption keys 18 username creating 20 for shutdown 4 S T U regenerating shared link 22 R Testing Disaster Recovery 29