Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

Dell FluidFS V3 NAS Solutions For PowerVault NX3500, NX3600, And NX3610Administrator's Guide

PDF

Specifying NAS Volumes Using the DMA

In order to perform backup and restore operations, the DMA server must be configured to be able to access the FluidFS cluster.

On each DMA server, you must configure the following:
  • Client VIP (or a DNS name) that the DMA server accesses. If you ever change the client VIP, you must also make the reciprocal change on the DMA servers.

    • NOTE: NDMP has no load balancing built in. A single DMA backing up 10 NAS volumes from a single client VIP forces all 10 sessions to be on the same NAS controller. Therefore, Dell recommends using DNS round‐robin to provide load balancing, by specifying the DNS name of the FluidFS cluster in the DMA.
  • NDMP user name and password (default user name is backup_user).

  • Port that the NDMP server monitors for incoming connections (default port is 10000).

In addition, some DMA servers require the following:
  • Host name of the FluidFS cluster, which uses the following format:
    <controller_number>.<FluidFS_cluster_name>
  • OS type: Dell Fluid File System

  • Product: Compellent FS8600

  • Vendor: Dell Inc.

Most backup applications automatically list the available NAS volumes to back up. Otherwise, you can manually type in the NAS volume path. The FluidFS cluster exposes backup NAS volumes at the following path:

/<NAS_volume_name>

To improve data transfer speed, limit the number of concurrent backup jobs to one per NAS controller.


Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\