[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-09-04。"],[],[],null,["# FlexGroups and large volumes\n\nBoth volume migration and external replication support ONTAP [FlexGroups](https://docs.netapp.com/us-en/ontap/flexgroup/definition-concept.html) as source volumes.\n\nA FlexGroups volume is a large volume internally built out of multiple FlexVols,\nknown as member volumes or constituents. NetApp Volumes uses\nFlexGroups internally to provide its [large capacity volumes](/netapp/volumes/docs/configure-and-use/volumes/overview#large-capacity-volumes) or large volume feature.\n\nWhen replicating a FlexGroup volume to NetApp Volumes, the\ndestination volume must also be a large volume. The number of constituents on\nthe destination large volume must match with the number of constituents on the\nsource FlexGroup. As external replication can't read this number from the source\nvolume, you must specify it during replication creation using the\n`large-volume-constituent-count` parameter within the\n`hybrid-replication-parameters` parameter block.\n\nThe `large-volume-constituent-count` you provide must meet the following\ncriteria:\n\n- It must be between 2 and 36.\n\n- No odd numbers are allowed, with the exceptions of 3 and 5.\n\nIf your source FlexGroup's constituent count doesn't meet these requirements,\nyou must change the source FlexGroup constituent count to a correct value before\nestablishing an external replication. Once the replication is enabled, you can't\nchange the constituent count on NetApp Volumes. Therefore, don't\nadd constituents to an ONTAP FlexGroup that is already in replication with\nNetApp Volumes.\n\nExternal replications between FlexGroups and large volumes don't support the\n`EVERY_10_MINUTES` replication schedule. However, volume migration uses a fixed\n`HOURLY` replication schedule."]]