Contributors netapp-forry netapp-aherbin

NetApp Data Availability Services (NDAS) subscriptions are available in several capacity configurations.

Size Capacity Managed Max Files NDAS Portal Instance Catalog Instances

Small

10 TB

5 Million

1 x m5.xlarge

2 x r5.2xlarge

Medium

50 TB

50 Million

1 x m5.2xlarge

2 x r5.2xlarge

Medium

200 TB

50 Million

1 x m5.2xlarge

2 x r5.2xlarge

Large (release 1.1 & later)

200 TB

100 Million

1 x m5.4xlarge

2 x r5.4xlarge

Notes:
  • Managed Capacity is displayed as its physical size, defined as the size taken by the files on disk after compression or deduplication, as measured by ONTAP, across all primary clusters managed by NDAS, in terabytes.

  • The amount of Capacity Managed is displayed as follows:

    When the NDAS release is…​ The capacity in TBs of volumes protected to cloud is its…​

    1.1 or later

    physical size

    1.0.x

    logical size – the actual size of the files in the volume as seen by the app - when the source cluster is running ONTAP 9.4 or later

    physical size, when the source cluster is running ONTAP 9.3

  • Once the managed capacity limits have been reached, no further data protection relationships can be created. However, all existing volumes will continue to be protected with existing schedules.

  • Max Files refers to the sum of the number of files from all volumes in source clusters protected to cloud. In addition to these base files, changed files in each daily incremental Snapshot copy are also stored in the NDAS catalog. It is estimated that the number of files that change every day averages 2% of Max Files. With one year of the daily retention count that NetApp Data Availability Services currently supports, that amounts to limits of 5M catalog entries and 50M catalog entries for small and medium data capacities, respectively. If the daily change rate is more than 2%, an alert is displayed in the app dashboard to indicate when the catalog entries exceed the 5M or 50M limit.