Skip to main content

Object limits for SnapMirror Business Continuity

Contributors netapp-ahibbard netapp-aherbin
PDFs

When preparing to use and managing SnapMirror Business Continuity, be aware of the following limitations.

Consistency groups in a cluster

Consistency group limits for a cluster with SM-BC are calculated based on relationships and depend on the version of ONTAP used. Limits are platform-independent.

ONTAP version Maximum number of relationships

ONTAP 9.8-9.9.1

5

ONTAP 9.10.1

20

ONTAP 9.11.1 and later

50

Volumes per consistency group

The maximum number of volumes per consistency group with SM-BC is platform independent.

ONTAP version Maximum number of volumes supported in a consistency group relationship

ONTAP 9.8-9.9.1

12

ONTAP 9.10.1 and later

16

Volumes

Volume limits in SM-BC are calculated based on the number of endpoints, not the number of relationships. A consistency group with 12 volumes contributes 12 endpoints on both the primary and secondary cluster. Both SM-BC and SnapMirror Synchronous relationships contribute to the total number of endpoints.

The maximum endpoints per platform are included in the following table.

S. No Platform Endpoints per HA for SM-BC Overall sync and SM-BC endpoints per HA

ONTAP 9.8-9.9.1

ONTAP 9.10.1

ONTAP 9.11.1 and later

ONTAP 9.8-9.9.1

ONTAP 9.10.1

ONTAP 9.11.1 and later

1

AFF

60

200

400

80

200

400

2

ASA

60

200

400

80

200

400

SAN object limits

SAN object limits are included in the following table. The limits apply regardless of the platform.

Object in an SM-BC relationship Count

LUNs per volume

256

LUN maps per node

  • 4096 (ONTAP 9.10 and later)

  • 2048 (ONTAP 9.9.1 and earlier)

LUN maps per cluster

  • 8192 (ONTAP 9.10 and later)

  • 4096 (ONTAP 9.9.1 and earlier)

LIFs per SVM (with at least one volume in an SM-BC relationship)

256

Inter-cluster LIFs per node

4

Inter-cluster LIFs per cluster

8
Related information