By default, in a CommCell environment one HyperScale Storage Pool block is configured. Adding additional MediaAgent nodes scales out the existing storage pool. However, you can also configure multiple user defined HyperScale Storage Pool blocks in your CommCell environment.
Before You Begin
-
Perform the checks listed in the Before You Begin section in Setting Up HyperScale Storage Nodes.
-
Install the latest Maintenance Release version on the CommServe server and MediaAgents in the existing storage pools.
For more information on the latest Maintenance Release version, see What's New | Feature Release 11.x | Maintenance Releases in Feature Release 11.X | List of Maintenance Releases for Feature Release 11.X.
For more information on verifying the version information on the CommServe and MediaAgents , see Data Views - Version and Service Pack.
-
Enable root access, if root access is disabled in the storage pool. For more information, see Enabling or Disabling Root Access.
Procedure
To add additional nodes to the Storage Pool, see Setting Up HyperScale Storage Nodes.
What To Do Next
Important
Verify and ensure that all nodes have the same time and timezone settings.
-
Enable ransomware protection for the new node that you added to the HyperScale storage pool.
-
After all the nodes are setup, add the nodes to the existing HyperScale Storage Pool in the CommServe as follows:
-
Using a web browser, launch the Command Center using the following URL:
https://<Commserver hostname>/commandcenter
-
Type the user name and password provided during the setup.
-
Click Login.
-
From the navigation, click Storage > Storage Pools.
The Storage Pool page appears.
-
From the Storage Pools page, click the name of the Storage Pool to which you want to the additional nodes.
-
Click Add nodes.
The Add nodes page appears.
-
From the Nodes list, select the number of nodes which you want to add.
Note
The number of nodes that you can add to a Storage Pool depends on the Resiliency of the Storage Pool.
-
Click Add.
This will add the new nodes to the storage pool.
-
-
Disable root access, if root access was originally disabled in the storage pool. For more information, see Enabling or Disabling Root Access.
Additional Notes
In a 3 node setup, the Deduplication Database (DDB) will be distributed as follows before the expansion:
|
Node 1 |
Node 2 |
Node 3 |
|---|---|---|
|
Partition 1 Partition 2 |
Partition 3 Partition 4 |
Partition 5 Partition 6 |
When the storage pool is expanded to 6 control nodes, the DDB will be automatically re-distributed across the MediaAgents as follows:
Note
As a result, jobs accessing the DDB will be automatically suspended during the process and (automatically) resumed once the DDB partitions are successfully re-distributed across all the partitions. (If there is no data in the DDB (no backups), then a 'configuration-only' move will be initiated.)
|
Node 1 |
Node 2 |
Node 3 |
Node 4 |
Node 5 |
Node 6 |
|---|---|---|---|---|---|
|
Partition 1 |
Partition 3 |
Partition 5 |
Partition 2 |
Partition 4 |
Partition 6 |
DDB partitions will be moved to the new node(s) when they are configured as a Control node until all the Control nodes contain only one partition in each node.