Skip to main content

How can we help you?

Druva Documentation

Add a NAS device

Phoenix Editions: File:/tick.png Business File:/cross.png Enterprise File:/tick.png Elite

 

The next step in configuring a NAS share for backups is adding the NAS device and mapping it to a NAS proxy. This article guides you through adding a NAS device in the Phoenix Management Console and mapping it to a NAS proxy.

 

Procedure

  1. Log in to the Phoenix Management Console.
  2. The Get Started page is displayed if no NAS devices have been added so far. In the Get Started page, under Add a NAS device, click Add NAS device.

    Get Started - No Device.png

    If NAS devices have already been configured, the Get Started page is not available. To add additional NAS devices, click Add Device.

    Add Device_AllDevices.png
  3. On the Add Device page, enter the following details:

    Add Device.png

Field Description
Device IP/FQDN

IP or Fully Qualified Domain Name(FQDN) of the NAS device.

Note: You can edit the IP/FQDN of the NAS device using the Edit Device option.

Credentials
  • Select existing device credentials or click New Credentials, to add new credentials.
  • Select Use device credentials for auto-discovered shares to assign NAS device credentials to automatically discovered shares. If this option is selected, device credentials will be used to back up and restore shares. 

If you choose to create new credentials, enter the following details in the New Credentials dialog box:

  • Label: A unique label that identifies the credential

  • Username: Enter the device credential username in the Domain\username format for Windows, and in the NASUserName format for Linux. NASUsername is an account with appropriate access rights.

  • Password: Enter the password for the device credential

  • Confirm Password: Re-enter the password for the device credential

 Note:

  • Phoenix validates these credentials when you add shares under the NAS device on the Phoenix Management Console.These credentials are required only for protecting SMB shares.
  • If one user account does not have all required permissions over all folders in an SMB share hierarchy on NetApp, see Least privileges to protect SMB shares on NetApp for the least privileges that need to be assigned to the account for successful backups and restores.

Note: For more information on Dell EMC Isilon credentials and validations, see NAS Device Validations.

Display Name NAS device name that will appear on the Phoenix Management Console.

Vendor

 

Select the NAS vendor from the drop-down. The values are: 

  • Dell EMC Isilon
  • Netapp
  • Hitachi Vantara (HNAS)
  • PureStorage FlashBlade NAS
  • Synology
  • Qnap
  • HPE Storeasy
  • Qumulo
  • Others

You can select Others to enter the name of the vendor of your choice. This field is mandatory. By default, the value in this field is freeNAS.

Note: Currently, Druva Phoenix supports additional features for Dell EMC Isilon devices only, that is, snapshot based approach for backup and skipping stubs.

When you select Dell EMC Isilon, and need these features, then select the Use vendor APIs for faster incremental backups option.

Enter OneFS IP or FQDN and port information in the OneFS Endpoint field.

Note: OneFS is the API interface for Isilon. Based on vendor specific APIs, the above mentioned additional features are supported. 

NAS Proxy Mapping Map this device to registered NAS proxies. If your NAS device has SMB and NFS shares, ensure that you map it to a Windows and Linux proxy.
  1. On the Add Device page, click Save.

Validation checks are performed and the Device Validation window is displayed with the results.

Note: When the agent proxy discovers that a vendor is configured with native APIs, it runs vendor-specific validations that verifies all the privileges on the credentials. For more information on validations, see NAS Device Validations.

  • If both basic and vendor-specific (Isilon) validations are successful, then click Done. The NAS device is added. Druva Phoenix performs backup using the snapshot-based approach. It also identifies and skips the stub files.
    Add device - success.png

Note: If all the Isilon validations are successful, then the vendor specific APIs are supported. OneFS API performs a check for all the stub files in the directory. If a stub file is found, it is skipped during  backup. Also, a changelist is created from the snapshots, which helps to achieve faster incremental backups.

  • If the Isilon validation is not successful, then click Add Device on the Device Validation window. The NAS device is added and traditional backups will be performed. 
    Add device - Failure.png

Note: Basic Validations are performed first and then Isilon Validations are performed. If any Isilon validation fails, then the vendor's APIs are not supported and the Isilon backups will be performed by the traditional approach, and the stub files are processed as regular files.

For more information, see NAS Device Validations.

 

Next steps