You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
summary: 'You can define a custom protection domain layout, where each node is associated with one and only one custom protection domain. By default, each node is assigned to the same default custom protection domain.'
6
+
---
7
+
= Custom protection domains
8
+
:icons: font
9
+
:imagesdir: ../media/
10
+
11
+
[.lead]
12
+
You can define a custom protection domain layout, where each node is associated with one and only one custom protection domain. By default, each node is assigned to the same default custom protection domain.
13
+
14
+
If no custom protection domains are assigned:
15
+
16
+
* Cluster operation is unaffected.
17
+
* Custom level is neither tolerant nor resilient.
18
+
19
+
If more than one custom protection domain is assigned, each subsystem will assign duplicates to separate custom protection domains. If this is not possible, it reverts to assigning duplicates to separate nodes. Each subsystem (for example, bins, slices, protocol endpoint providers, and ensemble) does this independently.
20
+
21
+
NOTE: Using custom protection domains assumes that no nodes share a chassis.
22
+
23
+
The following Element API methods expose these new protection domains:
24
+
25
+
* GetProtectionDomainLayout - shows which chassis and which custom protection domain each node is in.
26
+
* SetProtectionDomainLayout - allows a custom protection domain to be assigned to each node.
27
+
28
+
Contact NetApp support for further details on using custom protection domains.
29
+
30
+
== Find more information
31
+
32
+
link:api/index.html[Manage storage with the Element API]
Copy file name to clipboardExpand all lines: docs/reference_hcc_config_maximums.adoc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,4 +23,4 @@ If you exceed these tested maximums, you might experience issues with NetApp Hyb
23
23
24
24
.Configuration maximums
25
25
26
-
NetApp Hybrid Cloud Control supports VMware vSphere environments with up to 100 ESXi hosts and 1000 virtual machines (comparable to a small vCenter Server Appliance configuration).
26
+
NetApp Hybrid Cloud Control supports VMware vSphere environments with up to 500 NetApp compute nodes. It supports up to 20 NetApp Element Software based storage clusters.
Copy file name to clipboardExpand all lines: docs/task_hcc_manage_accounts.adoc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -89,7 +89,7 @@ If you configured users on the storage cluster with LDAP, those accounts show a
89
89
. Log out of NetApp Hybrid Cloud Control.
90
90
. link:task_mnode_manage_storage_cluster_assets.html#edit-the-stored-credentials-for-a-storage-cluster-asset[Update the credentials] for the authoritative cluster asset using the NetApp Hybrid Cloud Control API.
91
91
+
92
-
NOTE: It might take the NetApp Hybrid Cloud Control UI up to 15 minutes to refresh the inventory. To manually refresh inventory, access the REST API UI inventory service `https://[management node IP]/inventory/1/` and run `GET /installations/{id}` for the cluster.
92
+
NOTE: It might take the NetApp Hybrid Cloud Control UI up to 2 minutes to refresh the inventory. To manually refresh inventory, access the REST API UI inventory service `https://[management node IP]/inventory/1/` and run `GET /installations/{id}` for the cluster.
Copy file name to clipboardExpand all lines: docs/task_hcc_manage_storage_clusters.adoc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,7 +48,7 @@ NOTE: Only remote storage clusters that are not currently managed by a managemen
48
48
49
49
. Select *Add*.
50
50
+
51
-
NOTE: After you add the storage cluster, the cluster inventory can take up to 15 minutes to refresh and display the new addition. You might need to refresh the page in your browser to see the changes.
51
+
NOTE: After you add the storage cluster, the cluster inventory can take up to 2 minutes to refresh and display the new addition. You might need to refresh the page in your browser to see the changes.
52
52
53
53
. If you are adding Element eSDS clusters, enter or upload your SSH private key and SSH user account.
Copy file name to clipboardExpand all lines: docs/task_hcc_manage_vol_management.adoc
+36-42Lines changed: 36 additions & 42 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,11 +24,11 @@ You can manage volumes in NetApp Hybrid Cloud Control in the following ways:
24
24
* <<Apply a QoS policy to a volume>>
25
25
* <<Edit a volume>>
26
26
* <<Clone volumes>>
27
+
* <<Add volumes to a volume access group>>
27
28
* <<Delete a volume>>
28
29
* <<Restore a deleted volume>>
29
30
* <<Purge a deleted volume>>
30
31
31
-
32
32
== Create a volume
33
33
You can create a storage volume using NetApp Hybrid Cloud Control.
34
34
@@ -47,40 +47,37 @@ NOTE: The default volume size selection is in GB. You can create volumes using s
47
47
1GiB = 1 073 741 824 bytes
48
48
49
49
. Select a block size for the volume.
50
-
. From the Account list, select the account that should have access to the volume.
50
+
. From the *Account* list, select the account that should have access to the volume.
51
51
+
52
-
If an account does not exist, click *Create New Account*, enter a new account name, and click *Create*. The account is created and associated with the new volume.
52
+
If an account does not exist, click *Create New Account*, enter a new account name, and click *Create Account*. The account is created and associated with the new volume in the *Account* list.
53
53
54
54
+
55
55
NOTE: If there are more than 50 accounts, the list does not appear. Begin typing and the auto-complete feature displays values for you to choose.
56
56
57
-
. To set the Quality of Service, do one of the following:
58
-
.. Select an existing QoS policy.
59
-
.. Under QoS Settings, set customized minimum, maximum, and burst values for IOPS or use the default QoS values.
57
+
. To configure the Quality of Service for the volume, do one of the following:
58
+
59
+
* Under *Quality of Service Settings*, set customized minimum, maximum, and burst values for IOPS or use the default QoS values.
60
+
* Select an existing QoS policy by enabling the *Assign Quality of Service Policy* toggle and choosing an existing QoS policy from the resulting list.
61
+
* Create and assign a new QoS policy by enabling the *Assign Quality of Service Policy* toggle and clicking *Create New QoS Policy*. In the resulting window, enter a name for the QoS policy and then enter QoS values. When finished, click *Create Quality of Service Policy*.
62
+
60
63
+
61
64
Volumes that have a Max or Burst IOPS value greater than 20,000 IOPS might require high queue depth or multiple sessions to achieve this level of IOPS on a single volume.
62
65
63
66
. Click *Create Volume*.
64
67
65
68
66
69
== Apply a QoS policy to a volume
67
-
You can apply a QoS policy to an existing storage volume by using NetApp Hybrid Cloud Control.
68
-
70
+
You can apply a QoS policy to existing storage volumes by using NetApp Hybrid Cloud Control. If instead you need to set custom QoS values for a volume, you can <<Edit a volume>>. To create a new QoS policy, see link:task_hcc_qos_policies.html[Create and manage volume QoS policies^].
69
71
70
72
.Steps
71
73
. Log in to NetApp Hybrid Cloud Control by providing the NetApp HCI or Element storage cluster administrator credentials.
72
74
. From the Dashboard, expand the name of your storage cluster on the left navigation menu.
73
75
. Select *Volumes* > *Overview*.
74
-
. In the *Actions* column in the volumes table, expand the menu for the volume and select *Edit*.
75
-
. Change the Quality of Service by doing one of the following:
76
-
.. Select an existing policy.
77
-
.. Under Custom Settings, set the minimum, maximum, and burst values for IOPS or use the default values.
78
-
+
79
-
NOTE: If you are using QoS policies on a volume, you can set custom QoS to remove the QoS policy affiliation with the volume. Custom QoS override QoS policy values for volume QoS settings.
76
+
. Select one or more volumes to associate with a QoS policy.
77
+
. Click the *Actions* drop-down list at the top of the volumes table, and select *Apply QoS Policy*.
78
+
. In the resulting window, select a QoS policy from the list and click *Apply QoS Policy*.
80
79
+
81
-
TIP: When you change IOPS values, increment in tens or hundreds. Input values require valid whole numbers. Configure volumes with an extremely high burst value. This enables the system to process occasional large block, sequential workloads more quickly, while still constraining the sustained IOPS for a volume.
82
-
83
-
. Select *Save*.
80
+
NOTE: If you are using QoS policies on a volume, you can set custom QoS to remove the QoS policy affiliation with the volume. Custom QoS values override QoS policy values for volume QoS settings.
84
81
85
82
86
83
== Edit a volume
@@ -155,36 +152,36 @@ NOTE: Cloned volumes do not inherit volume access group membership from the sour
155
152
. Log in to NetApp Hybrid Cloud Control by providing the NetApp HCI or Element storage cluster administrator credentials.
156
153
. From the Dashboard, expand the name of your storage cluster on the left navigation menu.
157
154
. Select the *Volumes* > *Overview* tab.
158
-
. Select each volume you want to clone and click the *Clone* button that appears.
159
-
. Do one of the following:
160
-
* To clone a single volume, perform the following steps:
161
-
.. In the *Clone Volume* dialog box, enter a volume name for the volume clone.
155
+
. Select each volume you want to clone.
156
+
. Click the *Actions* drop-down list at the top of the volumes table, and select *Clone*.
157
+
. In the resulting window, do the following:
158
+
159
+
.. Enter a volume name prefix (this is optional).
160
+
.. Choose the access type from the *Access* list.
161
+
.. Choose an account to associate with the new volume clone (by default, *Copy from Volume* is selected, which will use the same account that the original volume uses).
162
+
.. If an account does not exist, click *Create New Account*, enter a new account name, and click *Create Account*. The account is created and associated with the volume.
162
163
+
163
164
TIP: Use descriptive naming best practices. This is especially important if multiple clusters or vCenter Servers are used in your environment.
164
165
165
-
.. Select an account access level:
166
-
** Read Only
167
-
** Read/Write
168
-
** Locked
169
-
** Replication Target
170
-
171
-
.. Select a size in GB or GIB for the volume clone.
172
166
+
173
167
NOTE: Increasing the volume size of a clone results in a new volume with additional free space at the end of the volume. Depending on how you use the volume, you may need to extend partitions or create new partitions in the free space to make use of it.
174
168
175
-
.. Select an account to associate with the volume clone.
176
169
+
177
-
If an account does not exist, click *Create New Account*, enter a new account name, and click *Create*. The account is created and associated with the volume.
178
-
179
170
.. Click *Clone Volumes*.
171
+
NOTE: The time to complete a cloning operation is affected by volume size and current cluster load. Refresh the page if the cloned volume does not appear in the volume list.
180
172
181
-
* To clone multiple volumes, perform the following steps:
182
-
.. In the *Clone Volumes* dialog box, enter an optional prefix for the volume clones in the *New Volume Name Prefix* field.
183
-
.. Select a new type of access for the volume clones or copy the access type from the active volumes.
184
-
.. Select a new account to associate with the volume clones or copy the account association from the active volumes.
185
-
.. Click *Clone Volumes*.
173
+
== Add volumes to a volume access group
174
+
You can add a single volume or a group of volumes to a volume access group.
175
+
176
+
.Steps
177
+
. Log in to NetApp Hybrid Cloud Control by providing the NetApp HCI or Element storage cluster administrator credentials.
178
+
. From the Dashboard, expand the name of your storage cluster on the left navigation menu.
179
+
. Select *Volumes* > *Overview*.
180
+
. Select one or more volumes to associate with a volume access group.
181
+
. Click the *Actions* drop-down list at the top of the volumes table, and select *Add to Access Group*.
182
+
. In the resulting window, select a volume access group from the *Volume Access Group* list.
183
+
. Click *Add Volume*.
186
184
187
-
NOTE: The time to complete a cloning operation is affected by volume size and current cluster load. Refresh the page if the cloned volume does not appear in the volume list.
188
185
189
186
== Delete a volume
190
187
You can delete one or more volumes from an Element storage cluster.
@@ -202,11 +199,8 @@ IMPORTANT: Persistent volumes that are associated with management services are c
202
199
. From the Dashboard, expand the name of your storage cluster on the left navigation menu.
203
200
. Select *Volumes* > *Overview*.
204
201
. Select one or more volumes to delete.
205
-
. Do one of the following:
206
-
+
207
-
* If you selected multiple volumes, click the *Delete* quick filter at the top of the table.
208
-
* If you selected a single volume, in the *Actions* column of the Volumes table, expand the menu for the volume and select *Delete*.
209
-
. Confirm the delete by selecting *Yes*.
202
+
. Click the *Actions* drop-down list at the top of the volumes table, and select *Delete*.
203
+
. In the resulting window, confirm the action by clicking *Yes*.
210
204
211
205
== Restore a deleted volume
212
206
After a storage volume is deleted, you can still restore it if you do so before eight hours after deletion.
You can view both your storage and compute assets in your system and determine their IP addresses, names, and software versions.
18
18
19
-
You can view storage information for your multiple node systems and any NetApp HCI Witness Nodes associated with two-node or three-node clusters.
19
+
You can view storage information for your multiple node systems and any NetApp HCI Witness Nodes associated with two-node or three-node clusters. If link:concept_hcc_custom_protection_domains.html[custom protection domains^] are assigned, you can see which protection domains are assigned to specific nodes.
20
20
Witness Nodes manage quorum within the cluster; they are not used for storage. Witness Nodes are applicable only to NetApp HCI and not to all-flash storage environments.
21
21
22
22
For more information about Witness Nodes, see link:concept_hci_nodes.html[Nodes definitions].
0 commit comments