Google: Installing the NEA and NMC

Overview

This chapter explains how to download the software and perform the initial installation of the Nasuni Edge Appliance and the Nasuni Management Console (NMC) on a virtual platform.

For additional information on the initial configuration of the Nasuni Edge Appliance, see Nasuni Edge Appliance Initial Configuration Guide. For additional information on the initial configuration of the NMC, see Nasuni Management Console Guide.

Warning: IF YOU EVER NEED TO TRANSITION FROM ONE HYPERVISOR PLATFORM TO A DIFFERENT HYPERVISOR PLATFORM, DO NOT USE ANY OF THE MIGRATION TOOLS OF EITHER HYPERVISOR PLATFORM. INSTEAD, PERFORM A RECOVERY PROCEDURE, USING THE NEW HYPERVISOR PLATFORM AS THE DESTINATION. FOR DETAILS, SEE NEA RECOVERY OR NMC RECOVERY GUIDE.

Warning: DO NOT ATTEMPT TO RESTORE FROM A VIRTUAL MACHINE SNAPSHOT OR BACKUP.

ATTEMPTING TO RESTORE FROM A VIRTUAL MACHINE SNAPSHOT OR BACKUP PUTS THE EDGE APPLIANCE IN AN UNKNOWN STATE IN RELATION TO THE NASUNI ORCHESTRATION CENTER (NOC), AND REQUIRES A DISASTER RECOVERY PROCESS TO BE RECOVERED. THIS MIGHT RESULT IN DATA LOSS.

Important: Installing third-party software on Nasuni appliances is not allowed.

Tip: In the Nasuni model, customers provide their own cloud accounts to store their data. Customers should leverage their cloud provider's role-based access and identity access management features as part of their overall security strategy. Such features can be used to limit or prohibit administrative access to the cloud account, based on customer policies.

Installing the Nasuni Edge Appliance from the Google Marketplace

You can run the Nasuni Edge Appliance in Google Cloud. You can install the Nasuni Edge Appliance using the Google Marketplace.

Warning: DO NOT ATTEMPT TO RESTORE FROM A VIRTUAL MACHINE SNAPSHOT OR BACKUP.

ATTEMPTING TO RESTORE FROM A VIRTUAL MACHINE SNAPSHOT OR BACKUP PUTS THE EDGE APPLIANCE IN AN UNKNOWN STATE IN RELATION TO THE NASUNI ORCHESTRATION CENTER (NOC), AND REQUIRES A DISASTER RECOVERY PROCESS TO BE RECOVERED. THIS MIGHT RESULT IN DATA LOSS.

Important: Edge Appliances and the NMC must be configured with operational DNS servers and a time server (internal or external) within your environment.

Important: Installing third-party software on Nasuni appliances is not allowed.

Important: When using virtual machine Edge Appliances or NMCs, Nasuni recommends running under a hypervisor that is still supported by its vendor. If a customer runs an Edge Appliance or NMC on an unsupported hypervisor version, a warning is logged at boot time. The warning is of the form:

“Nasuni recommends running the Management Console on ESX 7.0 or later.”

Creating a Google Cloud virtual machine (VM)

To create a Google Cloud virtual machine (VM) from the Google Marketplace, follow these steps:

1. Log in to the Dashboard of the Google Cloud Platform.

   

2. Click the Navigation menu icon (three horizontal lines in upper-left corner). The Navigation menu appears.

   

3. Click Marketplace. The Marketplace page appears.

   

4. In the Search Marketplace box, enter “Nasuni”. A list of Nasuni products appears.

   

5. Click Nasuni Edge Appliance.

   The Nasuni Edge Appliance page appears

   

6. Click Get Started.

   The Terms and agreements appear.

   

7. Review and click Accept.

   On the dialog box, click Deploy.

8. The “New Nasuni Edge Appliance deployment” page appears.

   

9. Enter a “Deployment name” for this deployment.

   Alternatively, you can accept the default name generated.

10. From the Zone drop-down list, select a zone for this deployment. Zones determine where data is stored and used. Also, different zones offer different resources and features. Choose a zone that is close to your point of service. For details, see Regions and zones.

11. Scroll down to the “Machine type” area.

    

12. Click the “General purpose” tab.

13. From the Series drop-down list, select the series of the machine type. A series such as “N2” uses Intel CPUs, while a series such as “N2D” uses AMD CPUs. The default series is N2D.

14. From the “Machine type” drop-down list, select a machine type that is n2-standard-8 or greater.

    Alternatively, select Custom. Then enter the number of Cores (8 or more) and the amount of Memory (32 GB or more).

    For recommendations, see Appendix B, “Google Compute Machine Type recommendations,” on page 78.

15. Scroll down to the “Boot Disk” area.

    

16. From the “Boot disk type” drop-down list, select the boot disk type. Select an SSD disk type.

17. In the “Boot disk size in GB” text box, enter the boot disk size. Enter at least 16 GB.\

    To increase the size of the OS disk to 32 GiB for the Nasuni Edge Appliance (NEA) or the Nasuni Management Console (NMC), perform these steps:

    1. Change the size of the OS disk in the virtual machine to 32 GiB.

    2. Reboot the virtual machine.

    Note: Since this procedure interrupts access to the NEA or NMC, schedule this procedure for a time of low usage.

18. Scroll down to the Networking area.

    

19. Add any additional network interfaces that you require.

20. In the Firewall area, enable “Allow TCP port 8443 traffic from the Internet”. Enter any source IP ranges for TCP port 8443 traffic.

21. Also, enable “Allow HTTPS traffic from the Internet”. Enter any source IP ranges for HTTPS traffic.

22. Click Deploy.

    The virtual machine is deployed. This might take several minutes.

23. This virtual machine becomes available in the Deployment Manager list (available from the Navigation menu).

    

24. Click the Name in the list. The deployed item opens.

    

25. Click the Instance. The VM instance Details page appears.

    

26. Click Edit. An editable version of the VM instance details appears.

27. In the “Remote access” area, enable “Enable connecting to serial ports”.

28. (Optional.) You can optionally change the machine type. You must stop the VM instance to edit its machine type.

    From the drop-down list, select a machine type that is n1-standard-4 or greater.

    Alternatively, select Custom. Then enter the number of Cores (8 or more) and the amount of Memory (32 GB or more).

29. Scroll down to the Firewalls area.

    

30. Select both “Allow HTTP traffic” and “Allow HTTPS traffic”.

    To specify firewalls further, from the Navigation menu, select VPC Network, then Firewall. You can define and specify firewall settings.

31. To define a cache disk for the instance, follow these steps:

    Important: It is important to select a proper size for the cache disk, because you cannot resize a cache disk from within Google Cloud. In order to change the size of a cache disk, you must perform a disaster recovery procedure on the Edge Appliance, and define a new cache disk as part of the disaster recovery.

    Tip: For best performance, multiple cache disks are recommended. Contact Nasuni Support for help in configuring multiple cache disks.

    Tip: If deploying multiple virtual disks for use as the appliance cache, as Nasuni recommends, all virtual disks must be identical in size, and the total size of the virtual disks must be equal to the total desired size of the cache. For example, if you want to create 4 virtual disks with a total cache size of 500 GiB, each of the 4 virtual disks must be 125 GiB.

    1. In the “Additional disks” area, click Add new disk. Additional fields become available.

       

    2. Enter a Name for the cache disk, such as “cache-disk”. This name is permanent.

    3. From the Type drop-down list, select the type of disk. Nasuni recommends an SSD persistent disk.

    4. For the “Deletion rule”, enable “Delete disk”.

    5. Enter a Size for the cache disk.

       The size of the cache should be based on the size of the working set (the amount of data being accessed by users or applications on a regular basis), including metadata.

       Important: It is important to select a proper size for the cache disk, because you cannot resize a cache disk from within Google Cloud. In order to change the size of a cache disk, you must perform a disaster recovery procedure on the Edge Appliance, and define a new cache disk as part of the disaster recovery.

    6. Select a type of Encryption.

       

       The default Encryption is “Google-managed key”.

    7. For “Device name”, select how the device name is created.

    8. Click Save. The cache disk is created and appears in the list of disks.

32. To define a COW (cache-on-write) disk for the instance, follow these steps:

    1. Click Add new disk. Additional fields become available.

    2. Enter a Name for the COW disk, such as “cow-disk”. This name is permanent.

    3. From the Type drop-down list, select the type of disk. Nasuni suggests the “Balanced persistent disk” type.

    4. For the “Deletion rule”, enable “Delete disk”.

    5. Enter a Size for the COW disk.

       Important: The size of the COW disk should be at least 1/4 of the size of the cache disk. The COW disk need not be larger than 250 GiB, except in special situations where ingestion might exceed the size of the cache disk, such as during initial ingestion or when ingesting extremely large files. In such cases, you can increase the size of the COW disk. For details, see Resizing the Cache and Snapshot Disks.

    6. Select a type of Encryption.

       

       The default Encryption is “Google-managed key”.

    7. For “Device name”, select how the device name is created.

    8. Click Save. The COW disk is created.

33. Click Save. The changes are saved. This step can take some time.

34. If the State is not Running, click Start. The virtual machine instance starts.

    Important: When using virtual machine Edge Appliances or NMCs, Nasuni recommends running under a hypervisor that is still supported by its vendor. If a customer runs an Edge Appliance or NMC on an unsupported hypervisor version, a warning is logged at boot time. The warning is of the form:

    “Nasuni recommends running the Management Console on ESX 7.0 or later.”

35. (Optional) To view the progress of the Edge Appliance booting, follow these optional steps:

    1. Click “Connect to serial console”. You can then view the interactive serial console.

    2. You can view the starting Edge Appliance with the interactive serial console.

    Tip: The first boot of a Nasuni Edge Appliance might take slightly longer than subsequent boots.

36. After the Edge Appliance boots, you can view the Edge Appliance user interface by clicking the External IP of the virtual machine instance.

37. The Nasuni Edge Appliance is now installed and ready to access using the IP address. See the Nasuni Edge Appliance Initial Configuration Guide for instructions on completing the configuration of the Nasuni Edge Appliance.

Tip: To access the NEA or NMC appliance using the serial console, instead of using the IP address obtained when installing the appliance, follow one of these procedures:

• If the appliance is running on Amazon EC2, see instructions in EC2 Serial Console for Linux instances.

• If the appliance is running on Google Cloud, see instructions in Troubleshooting using the serial console.

• If the appliance is running on Microsoft Azure, see instructions in Azure Serial Console.

All supported hypervisors include a serial console that works with Nasuni. For other hypervisors, consult your vendor’s documentation for connection instructions.

Display considerations with the Google Cloud

Be aware of the following display behavior with the Google Cloud:

• On the Network Configuration page, the Speed displays as “n/a”. This has no impact on performance.

  

• On the Network Status page, the Speed and Duplex display as “n/a”. The MTU defaults to 1460. This has no impact on performance.

  

Installing the NMC from the Google Marketplace

You can run the NMC in Google Cloud. You can install the NMC using the Google Marketplace.

Important: Edge Appliances and the NMC must be configured with operational DNS servers and a time server (internal or external) within your environment.

Warning: DO NOT ATTEMPT TO RESTORE FROM A VIRTUAL MACHINE SNAPSHOT OR BACKUP.

ATTEMPTING TO RESTORE FROM A VIRTUAL MACHINE SNAPSHOT OR BACKUP PUTS THE EDGE APPLIANCE IN AN UNKNOWN STATE IN RELATION TO THE NASUNI ORCHESTRATION CENTER (NOC), AND REQUIRES A DISASTER RECOVERY PROCESS TO BE RECOVERED. THIS MIGHT RESULT IN DATA LOSS.

Important: Installing third-party software on Nasuni appliances is not allowed.

Important: When using virtual machine Edge Appliances or NMCs, Nasuni recommends running under a hypervisor that is still supported by its vendor. If a customer runs an Edge Appliance or NMC on an unsupported hypervisor version, a warning is logged at boot time. The warning is of the form:

“Nasuni recommends running the Management Console on ESX 7.0 or later.”

Creating a Google Cloud virtual machine (VM)

To create a Google Cloud virtual machine (VM) from the Google Marketplace, follow these steps:

1. Log in to the Dashboard of the Google Cloud Platform ( console.cloud.google.com).

2. Click the Navigation menu icon (three horizontal lines in upper-left corner). The Navigation menu appears.

3. Click Marketplace. The Marketplace page appears.

   In the Search Marketplace box, enter “Nasuni”. A list of Nasuni products appears.

4. Click Nasuni Management Console.

   The Nasuni Management Console page appears

5. Accept the Terms of Service.

6. Click Launch.

   The “New Nasuni Management Console deployment” page appears.

7. Enter a “Deployment name” for this deployment.

   Alternatively, you can accept the default name generated.

8. From the Zone drop-down list, select a zone for this deployment. Zones determine where data is stored and used. Also, different zones offer different resources and features. Choose a zone that includes the resources and features you want, and that is close to your point of service. For details, see Regions and zones.

9. Scroll down to the “Machine type” area.

10. Click the “General purpose” tab.

11. From the Series drop-down list, select the series of the machine type. The default series is N2D.

12. From the “Machine type” drop-down list, select a machine type that is n1-standard-4 or greater.

    Alternatively, select Custom. Then enter the number of Cores and the amount of Memory. For guidance, see “NMC Sizing Guidelines” on page 38.

    For recommendations, see Appendix B, “Google Compute Machine Type recommendations,” on page 78.

13. Scroll down to the “Boot Disk” area.

14. From the “Boot disk type” drop-down list, select the boot disk type. Select an SSD disk type.

15. From the “Boot disk size” drop-down list, select the boot disk size. Select at least 16 GB.

16. Scroll down to the Networking area.

17. Add any additional network interfaces that you require.

18. In the Firewall area, enable “Allow TCP port 8443 traffic from the Internet”. Enter any source IP ranges for TCP port 8443 traffic.

19. Also, enable “Allow HTTPS traffic from the Internet”. Enter any source IP ranges for HTTPS traffic.

20. Click Deploy.

    The virtual machine is deployed. This might take several minutes.

21. This virtual machine becomes available in the Deployment Manager list (available from the Navigation menu).

22. Click the Name in the list. The Instance details pane appears.

23. Click the Instance. The Details” page appears.

24. Click Edit. An editable version of the VM instance details appears.

25. In the “Remote access” area, enable “Enable connecting to serial ports”.

26. Scroll down to the Firewalls area.

27. Select both “Allow HTTP traffic” and “Allow HTTPS traffic”.

    To specify firewalls further, from the Navigation menu, select VPC Network, then Firewall. You can define and specify firewall settings.

28. Click Save. The changes are saved. This step can take some time.

29. Click Start. The virtual machine instance starts.

    Important: When using virtual machine Edge Appliances or NMCs, Nasuni recommends running under a hypervisor that is still supported by its vendor. If a customer runs an Edge Appliance or NMC on an unsupported hypervisor version, a warning is logged at boot time. The warning is of the form:

    “Nasuni recommends running the Management Console on ESX 7.0 or later.”

30. (Optional) To view the progress of the NMC booting, click “Connect to serial console”. You can then view the interactive serial console.

31. After the NMC boots, you can view the NMC user interface by using the External IP of the virtual machine instance.

32. The NMC is now installed and ready to access using the IP address. See the Nasuni Management Console Guide for instructions on completing the configuration of the NMC.

NMC Sizing Guidelines

The NMC requires 32 GB of disk space and 16 GiB of memory (RAM).

Use the following CPU and memory guidelines to plan the sizing of the NMC. These guidelines are based on the number of Edge Appliances managed by the NMC, since the NMC memory and CPU utilization relate directly to the number of Edge Appliances managed.

Important: If using Varonis, the NMC should have at least 4 CPUs, 16 GiB memory, and an appropriate corresponding virtual machine.

*If managing more than 200 Edge Appliances, additional backend configuration is necessary for the NMC. Contact Nasuni Support for assistance.

Note: These values are based on CPU and memory utilization for a version 8.5 NMC. Earlier versions of the NMC might require additional resources.

Important: These are general recommendations. Your specific situation might require further resources.

Installing by downloading the Nasuni Edge Appliance or NMC Software

The Nasuni Edge Appliance and Nasuni Management Console (NMC) can run as a virtual appliance on your network and is distributed as a downloadable image. You need to register on the Nasuni Web site for a user account and password to access the download page.

Important: When using virtual machine Edge Appliances or NMCs, Nasuni recommends running under a hypervisor that is still supported by its vendor. If a customer runs an Edge Appliance or NMC on an unsupported hypervisor version, a warning is logged at boot time. The warning is of the form:

“Nasuni recommends running the Management Console on ESX 7.0 or later.”

Important: Installing third-party software on Nasuni appliances is not allowed.

To download the Nasuni Edge Appliance or NMC software from the Nasuni Web site:

1. Log in to your Nasuni account Web site ( https://account.nasuni.com/) and click Downloads.

   The Downloads page appears.

   

2. Select the appropriate format for your virtual environment from these choices:

   • AMAZON EC2: Scroll down to the “Appliance AMIs on EC2” area, and follow the instructions to continue installation using appliance AMIs.

   • AZURE FORMAT: A .vhd file, appropriate for Microsoft Azure environments.

   • GOOGLE CLOUD FORMAT: A disk.raw file contained in a .tar.gz file, appropriate for Google Cloud environments.

   • HYPER-V FORMAT: Hyper-V format is appropriate for Microsoft Hyper-V environments:

     versions 2019 and later.

   • NUTANIX FORMAT: A .qcow2 file appropriate for Nutanix AHV environments.

   • SCALE FORMAT: A file appropriate for Scale HyperCore environments.

   • OVF FORMAT: OVF format is appropriate for VMware ESXi 7.0 and above environments.

3. From the drop-down list, select an available release for the Edge Appliance or NMC. The list of available releases can change.

   

   Note: If you are running a recovery procedure, select the same version family as your existing Edge Appliance to ensure software compatibility. For example, if the existing Edge

   Appliance is running version 9.5.1, you could select version 9.5.4 (which is in the same 9.5.x version family), but not version 9.7.1 (which is in a different version family). If you need to use a different version than those offered, contact Nasuni Customer Support.

   Tip: For update paths, see Compatibility and Support.

   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.

4. Save the Nasuni Edge Appliance software .zip file to a location on your local drive.

   The amount of time to download the Nasuni Edge Appliance software file depends on your Internet connection. The file is approximately 900 MB in size.

   The amount of time to download the NMC software file depends on your Internet connection. The file is approximately 800 MB in size.

5. To continue installing the Nasuni Edge Appliance, see “Installing the Nasuni Edge Appliance into Google Cloud” on page 42.

Installing the Nasuni Edge Appliance into Google Cloud

You can run the Nasuni Edge Appliance in Google Cloud.

Important: Edge Appliances and the NMC must be configured with operational DNS servers and a time server (internal or external) within your environment.

Warning: DO NOT ATTEMPT TO RESTORE FROM A VIRTUAL MACHINE SNAPSHOT OR BACKUP.

ATTEMPTING TO RESTORE FROM A VIRTUAL MACHINE SNAPSHOT OR BACKUP PUTS THE EDGE APPLIANCE IN AN UNKNOWN STATE IN RELATION TO THE NASUNI ORCHESTRATION CENTER (NOC), AND REQUIRES A DISASTER RECOVERY PROCESS TO BE RECOVERED. THIS MIGHT RESULT IN DATA LOSS.

Tip: Before beginning the installation process, you must create a storage bucket.

Important: Installing third-party software on Nasuni appliances is not allowed.

Important: When using virtual machine Edge Appliances or NMCs, Nasuni recommends running under a hypervisor that is still supported by its vendor. If a customer runs an Edge Appliance or NMC on an unsupported hypervisor version, a warning is logged at boot time. The warning is of the form:

“Nasuni recommends running the Management Console on ESX 7.0 or later.”

Creating a Google Cloud virtual machine image for the Edge Appliance

To create a Google Cloud virtual machine image using the Google Cloud Console, follow these steps:

1. On the Google Cloud Console, click the Navigation menu icon at the upper left. From the dropdown menu, select Storage, then select Browser. The Storage browser pane appears.

   

2. From the list of available storage buckets, click the storage bucket that you want to use. The Bucket details pane for the selected bucket appears.

   

3. Click Upload Files, then navigate to the location of the .tar.gz software file that you downloaded in “Installing by downloading the Nasuni Edge Appliance or NMC Software” on page 39. The .tar.gz software file is uploaded, and appears in the Bucket details list.

4. There are several ways to create the virtual machine image from the .tar.gz software file. One way is to use the Cloud Shell, using the following steps:

   1. Open the Cloud Shell by clicking the Activate Cloud Shell icon in the upper right.

      

      The Cloud Shell opens at the bottom of the screen.

      

      The Cloud Shell automatically includes the details of your project.

   2. For First Generation (BIOS) machines, enter this command and press Enter:
      gcloud compute images create <destination-image> --source-uri gs://<bucket-name>/<filename>

      where destination-image is the name of the destination for the image; bucket-name is the name of the storage bucket; filename is the name of the .tar.gz software file.

      The Cloud Shell begins creating the image. This can take several minutes to complete.

   3. For Second Generation (UEFI) machines, enter this command and press Enter:
      gcloud compute images create <destination-image>

      --source-uri gs://<bucket-name>/<filename> --guest-os-features="UEFI_COMPATIBLE"

      where destination-image is the name of the destination for the image; bucket-name is the name of the storage bucket; filename is the name of the .tar.gz software file.

      The Cloud Shell begins creating the image. This can take several minutes to complete.

   4. When the image is created, a Success message appears.

Creating a Google Cloud virtual machine (VM) for the Edge Appliance

To create a Google Cloud virtual machine (VM) using the Google Cloud Console, follow these steps:

1. After the image is created successfully, click the Navigation menu icon at the upper left. From the drop-down menu, select Compute Engine, then select Images. The Images pane appears.

   

2. From the list of images, select the image that you created, then click Create Instance. the “Create an instance” window appears.

   

3. Enter the following information for the instance:

   • Name: Enter a name for the instance. This name cannot be changed.

     

   • Labels: Click here to attach labels to this image. Labels are used with firewalls.

   • Region: From the drop-down list, select a region near to where the Edge Appliance is to be used.

   • Zone: From the drop-down menu, select a zone within the region. Different zones determine what resources are available, and where data is stored and used.

   • Machine type: From the drop-down list, select a Series:

     • For a First Generation (BIOS) machine, select the N1 series and from the Machine type list, select Custom. Select vCPUs and memory.

     • For a Second Generation (UEFI) machine, select the E2, N2, or N2D series and from the Machine type list, select Custom. Select vCPUs and memory.

     For recommendations, see Appendix B, “Google Compute Machine Type recommendations,” on page 78.

     Tip: For details on choosing machines for different generations, see Create a VM with a custom machine type.

   • Firewall: Select both “Allow HTTP traffic” and “Allow HTTPS traffic”.

     

     To specify firewalls further, including allowing TCP ports 443 and 8443, see step 9 on page 49.

4. To define a cache disk for the instance, follow these steps:

   Important: It is important to select a proper size for the cache disk, because you cannot resize a cache disk from within Google Cloud. In order to change the size of a cache disk, you must perform a disaster recovery procedure on the Edge Appliance, and define a new cache disk as part of the disaster recovery.

   Tip: For best performance, multiple cache disks are recommended. Contact Nasuni Support for help in configuring multiple cache disks.

   Tip: If deploying multiple virtual disks for use as the appliance cache, as Nasuni recommends, all virtual disks must be identical in size, and the total size of the virtual disks must be equal to the total desired size of the cache. For example, if you want to create 4 virtual disks with a total cache size of 500 GiB, each of the 4 virtual disks must be 125 GiB.

   1. Click “Management, security, disks, networking, sole tenancy”. This opens further specifications.

   2. Click Disks. This opens options for defining disks.

   3. Click Add new disk. The New disk pane appears.

      

   4. Enter a Name for the cache disk.

   5. From the Type drop-down list, select the type of disk. Nasuni recommends an SSD persistent disk.

      

   6. Enter a Size for the cache disk.

      Important: It is important to select a proper size for the cache disk, because you cannot resize a cache disk from within Google Cloud. In order to change the size of a cache disk, you must perform a disaster recovery procedure on the Edge Appliance, and define a new cache disk as part of the disaster recovery.

   7. Click Done. The cache disk is created and appears in the list of disks.

      

5. To define a COW (cache-on-write) disk for the instance, follow these steps:

   1. Click “Management, security, disks, networking, sole tenancy”. This opens further specifications.

   2. Click Disks. This opens options for defining disks.

   3. Click Add new disk. The New disk pane appears.

   4. Enter a Name for the COW disk.

   5. From the Type drop-down list, select the type of disk. “Local SSD scratch disk” is acceptable for the COW disk.

   6. Enter a Size for the COW disk.

      Important: The size of the COW disk should be at least 1/4 of the size of the cache disk. The COW disk need not be larger than 250 GiB, except in special situations where ingestion might exceed the size of the cache disk, such as during initial ingestion or when ingesting extremely large files. In such cases, you can increase the size of the COW disk. For details, see Resizing the Cache and Snapshot Disks.

   7. Click Done. The COW disk is created.

6. Click Create. The virtual machine instance is created.

   After the instance is created, it appears in the VM instances list.

   

   Important: When using virtual machine Edge Appliances or NMCs, Nasuni recommends running under a hypervisor that is still supported by its vendor. If a customer runs an Edge Appliance or NMC on an unsupported hypervisor version, a warning is logged at boot time. The warning is of the form:

   “Nasuni recommends running the Management Console on ESX 7.0 or later.”

7. (Optional) To view the progress of the Edge Appliance booting, follow these optional steps:

   1. Click the instance created, then click Edit.

   2. Select “Enable connecting to serial ports”.

   3. Click Save.

   4. Click “Connect to serial console”. You can then view the interactive serial console.

      

   5. You can then view the interactive serial console.

      

   Tip: The first boot of a Nasuni Edge Appliance might take slightly longer than subsequent boots.

8. After the Edge Appliance boots, you can view the Edge Appliance user interface by clicking the External IP of the virtual machine instance.

9. Configure firewall rules to allow TCP ports 443 and 8443, by following these steps:

   1. For the selected virtual machine instance in the VM instances list, click the three dots in the right-hand column.

      

   2. From the drop-down list, select “View network details”. The “Network interface details” pane appears.

   3. In the left-hand column, select Firewall. The firewall rule pane appears.

   4. Click “Create firewall rule”. The “Create a firewall rule” pane appears.

      

   5. Enter a name for this firewall rule.

   6. Select “ingress” and “Allow”.

      

   7. For “Protocols and ports”, select “Specified protocols and ports” and select “tcp”.

      Then enter “443, 8443” for the allowed ports.

      

   8. Configure other features as your installation requires.

   9. Click Create.

      This firewall rule is created.

   10. Apply this firewall rule to the virtual machine instance you created in step 6 on page 48.

10. The Nasuni Edge Appliance is now installed and ready to access using the IP address. See the Nasuni Edge Appliance Initial Configuration Guide for instructions on completing the configuration of the Nasuni Edge Appliance.

Display considerations with the Google Cloud for the Edge Appliance

Be aware of the following display behavior with the Google Cloud:

• On the Network Configuration page, the Speed displays as “n/a”.

  

• On the Network Status page, the Speed and Duplex display as “n/a”. The MTU defaults to 1460. This has no impact on performance.

  

Installing the Nasuni Management Console (NMC) into Google Cloud

You can run the Nasuni Management Console (NMC) in Google Cloud.

Warning: DO NOT ATTEMPT TO RESTORE FROM A VIRTUAL MACHINE SNAPSHOT OR BACKUP.

ATTEMPTING TO RESTORE FROM A VIRTUAL MACHINE SNAPSHOT OR BACKUP PUTS THE EDGE APPLIANCE IN AN UNKNOWN STATE IN RELATION TO THE NASUNI ORCHESTRATION CENTER (NOC), AND REQUIRES A DISASTER RECOVERY PROCESS TO BE RECOVERED. THIS MIGHT RESULT IN DATA LOSS.

Tip: Before beginning the installation process, you must create a storage bucket.

Important: Installing third-party software on Nasuni appliances is not allowed.

Important: When using virtual machine Edge Appliances or NMCs, Nasuni recommends running under a hypervisor that is still supported by its vendor. If a customer runs an Edge Appliance or NMC on an unsupported hypervisor version, a warning is logged at boot time. The warning is of the form:

“Nasuni recommends running the Management Console on ESX 7.0 or later.”

Creating a Google Cloud virtual machine image for the NMC

To create a Google Cloud virtual machine image using the Google Cloud Console, follow these steps:

1. On the Google Cloud Console, click the Navigation menu icon at the upper left. From the dropdown menu, select Storage, then select Browser. The Storage browser pane appears.

   

2. From the list of available storage buckets, click the storage bucket that you want to use. The Bucket details pane for the selected bucket appears.

   

3. Click Upload Files, then navigate to the location of the .tar.gz software file that you downloaded in “Installing by downloading the Nasuni Edge Appliance or NMC Software” on page 39. The .tar.gz software file is uploaded, and appears in the Bucket details list.

4. There are several ways to create the virtual machine image from the .tar.gz software file. One way is to use the Cloud Shell, using the following steps:

   1. Open the Cloud Shell by clicking the Activate Cloud Shell icon in the upper right.

      

      The Cloud Shell opens at the bottom of the screen.

      

      The Cloud Shell automatically includes the details of your project.

   2. Enter this command and press Enter: gcloud compute images create <destination-image> --source-uri gs://<bucket-name>/<filename>

      where destination-image is the name of the destination for the image; bucket-name is the name of the storage bucket; filename is the name of the .tar.gz software file.

      The Cloud Shell begins creating the image. This can take several minutes to complete.

   3. When the image is created, a Success message appears.

Creating a Google Cloud virtual machine (VM) for the NMC

To create a Google Cloud virtual machine (VM) using the Google Cloud Console, follow these steps:

1. After the image is created successfully, click the Navigation menu icon at the upper left. From the drop-down menu, select Compute Engine, then select Images. The Images pane appears.

   

2. From the list of images, select the image that you created, then click Create Instance. the “Create an instance” window appears.

   

3. Enter the following information for the instance:

   • Name: Enter a name for the instance. This name cannot be changed.

     

   • Labels: Click here to attach labels to this image. Labels are used with firewalls.

   • Region: From the drop-down list, select a region near to where the NMC is to be used.

   • Zone: From the drop-down menu, select a zone within the region. Different zones determine what resources are available, and where data is stored and used.

   • Machine type: From the drop-down list, select a machine type that is n1-standard-4 or greater.

     Alternatively, select Custom. Then enter the number of Cores (8 or more) and the amount of Memory (32 GB or more).

     

     For recommendations, see Appendix B, “Google Compute Machine Type recommendations,” on page 78.

   • Firewall: Select both “Allow HTTP traffic” and “Allow HTTPS traffic”.

     To specify firewalls further, select VPC Network, then Firewall. You can define and specify firewall settings.

     

4. To define a disk for the instance, follow these steps:

   1. Click “Management, security, disks, networking, sole tenancy”. This opens further specifications.

   2. Click Disks. This opens options for defining disks.

   3. Click Add new disk. The New disk pane appears.

      

   4. Enter a Name for the disk.

   5. From the Type drop-down list, select the type of disk. Any type of disk is appropriate, except for “Local SSD scratch disk”.

      

   6. Enter a Size for the disk.

   7. Click Done. The disk is created and appears in the list of disks.

      

5. Click Create. The virtual machine instance is created.

   After the instance is created, it appears in the VM instances list.

   

   Important: When using virtual machine Edge Appliances or NMCs, Nasuni recommends running under a hypervisor that is still supported by its vendor. If a customer runs an Edge Appliance or NMC on an unsupported hypervisor version, a warning is logged at boot time. The warning is of the form:

   “Nasuni recommends running the Management Console on ESX 7.0 or later.”

6. (Optional) To view the progress of the NMC booting, follow these optional steps:

   1. Click the instance created, then click Edit.

   2. Select “Enable connecting to serial ports”.

   3. Click Save.

   4. Click “Connect to serial console”. You can then view the interactive serial console.

      

   5. You can then view the interactive serial console.

      

7. After the NMC boots, you can view the NMC user interface by clicking the External IP of the virtual machine instance.

8. The NMC is now installed and ready to access using the IP address.