Skip to main content
commvault.com commvault.com
Question

3 node HSX cluster configuration completed with warning, node 2 has warning

N
Forum|alt.badge.img+7

we configured HPE Apollo based 3 node HSX cluster and all steps went on smooth ,  however a
at end of cluster configuration, storage pool was not created on 2nd node.

in command center, i can see all 3 nodes listed as MAs and however nothing is showing under storage pool.


Didnt find errors  in commserv CVMA.log.

i see below entries in CVMA.log in 2nd node, 

2488748 25f9ff 03/17 16:32:08 --- Storage pool not configured
2488748 25f9ff 03/17 16:32:08 --- skipping checking RWP protection
2488748 25f9ff 03/17 16:32:38 ### CVMAStorageProtect::is_storagepool_exist() - Storage pool not configured
2488748 25f9ff 03/17 16:32:38 --- Storage pool not configured
2488748 25f9ff 03/17 16:32:38 --- skipping checking RWP protection
2488748 25f9ff 03/17 16:33:08 ### CVMAStorageProtect::is_storagepool_exist() - Storage pool not configured
2488748 25f9ff 03/17 16:33:08 --- Storage pool not configured
2488748 25f9ff 03/17 16:33:08 --- skipping checking RWP protection


2488748 25f9ff 03/17 16:34:08 --- hedvig daemon is up and running..
2488748 25f9ff 03/17 16:34:08 ---  THREADS  [  ]  SENDING WEBSCALE STORAGE ACCESS REQUEST TO MEDIAMANAGER
2488748 25f9ff 03/17 16:34:08 ---  THREADS  [  ]  Response received, next action [2]
2488748 25f9ff 03/17 16:34:08 ---  SERVICE  [  ]  Number of data paths found [12]
2488748 25f9ff 03/17 16:34:08 ---  SERVICE  [  ]  Data mount path for Hedvig vdisk creation [/hedvig/d3]
2488748 25f9ff 03/17 16:34:08 ---  SERVICE  [  ]  Data mount path for Hedvig vdisk creation [/hedvig/d11]
2488748 25f9ff 03/17 16:34:08 ---  SERVICE  [  ]  Data mount path for Hedvig vdisk creation [/hedvig/d14]
2488748 25f9ff 03/17 16:34:08 ---  SERVICE  [  ]  Data mount path for Hedvig vdisk creation [/hedvig/d10]
2488748 25f9ff 03/17 16:34:08 ---  SERVICE  [  ]  Data mount path for Hedvig vdisk creation [/hedvig/d9]
2488748 25f9ff 03/17 16:34:08 ---  SERVICE  [  ]  Data mount path for Hedvig vdisk creation [/hedvig/d4]
2488748 25f9ff 03/17 16:34:08 ---  SERVICE  [  ]  Data mount path for Hedvig vdisk creation [/hedvig/d7]
2488748 25f9ff 03/17 16:34:08 ---  SERVICE  [  ]  Data mount path for Hedvig vdisk creation [/hedvig/d12]
2488748 25f9ff 03/17 16:34:08 ---  SERVICE  [  ]  Data mount path for Hedvig vdisk creation [/hedvig/d8]
2488748 25f9ff 03/17 16:34:08 ---  SERVICE  [  ]  Data mount path for Hedvig vdisk creation [/hedvig/d13]
2488748 25f9ff 03/17 16:34:08 ---  SERVICE  [  ]  Data mount path for Hedvig vdisk creation [/hedvig/d6]
2488748 25f9ff 03/17 16:34:08 ---  SERVICE  [  ]  Data mount path for Hedvig vdisk creation [/hedvig/d5]
2488748 25f9ff 03/17 16:34:08 ---  SERVICE  [  ]  [RWP] enabled storage pool not yet created
2488748 25f9ff 03/17 16:34:08 ---  SERVICE  [  ]  [RWP] processing data drives
2488748 25f9ff 03/17 16:34:08 ---  SERVICE  [  ]  [RWP] data drive {/hedvig/d3] added for protection
2488748 25f9ff 03/17 16:34:08 ---  SERVICE  [  ]  [RWP] data drive {/hedvig/d11] added for protection
2488748 25f9ff 03/17 16:34:08 ---  SERVICE  [  ]  [RWP] data drive {/hedvig/d14] added for protection
2488748 25f9ff 03/17 16:34:08 ---  SERVICE  [  ]  [RWP] data drive {/hedvig/d10] added for protection
2488748 25f9ff 03/17 16:34:08 ---  SERVICE  [  ]  [RWP] data drive {/hedvig/d9] added for protection
2488748 25f9ff 03/17 16:34:08 ---  SERVICE  [  ]  [RWP] data drive {/hedvig/d4] added for protection
2488748 25f9ff 03/17 16:34:08 ---  SERVICE  [  ]  [RWP] data drive {/hedvig/d7] added for protection
2488748 25f9ff 03/17 16:34:08 ---  SERVICE  [  ]  [RWP] data drive {/hedvig/d12] added for protection
2488748 25f9ff 03/17 16:34:08 ---  SERVICE  [  ]  [RWP] data drive {/hedvig/d8] added for protection
2488748 25f9ff 03/17 16:34:08 ---  SERVICE  [  ]  [RWP] data drive {/hedvig/d13] added for protection
2488748 25f9ff 03/17 16:34:08 ---  SERVICE  [  ]  [RWP] data drive {/hedvig/d6] added for protection
2488748 25f9ff 03/17 16:34:08 ---  SERVICE  [  ]  [RWP] data drive {/hedvig/d5] added for protection
2488748 25f9ff 03/17 16:34:08 ---  SERVICE  [  ]  [RWP] processing hedvig meta data drives
2488748 25f9ff 03/17 16:34:08 ---  SERVICE  [  ]  [RWP] hedvig meta data drive [/flache/metadatadir] added for protection
2488748 25f9ff 03/17 16:34:08 ---  SERVICE  [  ]  [RWP] hedvig meta data drive [/hedvig/d2] added for protection
2488748 25f9ff 03/17 16:34:08 ---  SERVICE  [  ]  [RWP] hedvig meta data drive [/hedvig/hpod/data] added for protection
2488748 25f9ff 03/17 16:34:08 ---  SERVICE  [  ]  [RWP] hedvig meta data drive [/hedvig/hpod/log] added for protection
2488748 25f9ff 03/17 16:34:08 ---  SERVICE  [  ]  [RWP] hedvig meta data drive [/mnt/d2] added for protection
2488748 25f9ff 03/17 16:34:08 ---  SERVICE  [  ]  [RWP] hedvig meta data drive [/mnt/d3] added for protection
2488748 25f9ff 03/17 16:34:08 ---  SERVICE  [  ]  [RWP] hedvig meta data drive [/mnt/d4] added for protection
2488748 25f9ff 03/17 16:34:08 ---  SERVICE  [  ]  [RWP] hedvig meta data drive [/mnt/d5] added for protection
2488748 25f9ff 03/17 16:34:08 ---  SERVICE  [  ]  [RWP] hedvig meta data drive [/mnt/f1] added for protection
2488748 25f9ff 03/17 16:34:08 ---  SERVICE  [  ]  DDB mount path for hedvig volume creation [/ws/ddb]
2488748 25f9ff 03/17 16:34:08 ---  SERVICE  [  ]  Client name [det01cvma02.corp.det.gov.ae] ClientID [1568]
2488748 25f9ff 03/17 16:34:08 ---  SERVICE  [  ]  req[0]  MP [/hedvig/d3] MP usage type [2]
2488748 25f9ff 03/17 16:34:08 ---  SERVICE  [  ]  req[1]  MP [/hedvig/d11] MP usage type [2]
2488748 25f9ff 03/17 16:34:08 ---  SERVICE  [  ]  req[2]  MP [/hedvig/d14] MP usage type [2]
2488748 25f9ff 03/17 16:34:08 ---  SERVICE  [  ]  req[3]  MP [/hedvig/d10] MP usage type [2]
2488748 25f9ff 03/17 16:34:08 ---  SERVICE  [  ]  req[4]  MP [/hedvig/d9] MP usage type [2]
2488748 25f9ff 03/17 16:34:08 ---  SERVICE  [  ]  req[5]  MP [/hedvig/d4] MP usage type [2]
2488748 25f9ff 03/17 16:34:08 ---  SERVICE  [  ]  req[6]  MP [/hedvig/d7] MP usage type [2]
2488748 25f9ff 03/17 16:34:08 ---  SERVICE  [  ]  req[7]  MP [/hedvig/d12] MP usage type [2]
2488748 25f9ff 03/17 16:34:08 ---  SERVICE  [  ]  req[8]  MP [/hedvig/d8] MP usage type [2]
2488748 25f9ff 03/17 16:34:08 ---  SERVICE  [  ]  req[9]  MP [/hedvig/d13] MP usage type [2]
2488748 25f9ff 03/17 16:34:08 ---  SERVICE  [  ]  req[10]  MP [/hedvig/d6] MP usage type [2]
2488748 25f9ff 03/17 16:34:08 ---  SERVICE  [  ]  req[11]  MP [/hedvig/d5] MP usage type [2]
2488748 25f9ff 03/17 16:34:08 ---  SERVICE  [  ]  req[12]  MP [/ws/ddb] MP usage type [1]
2488748 25f9ff 03/17 16:34:08 ---  SERVICE  [  ]  SENDING WEBSCALE STORAGE MOUNT PATH REQUEST TO MEDIAMANAGER
2488748 25f9ff 03/17 16:34:08 ---  SERVICE  [  ]  Response received, errorCode [0]
2488748 25f9ff 03/17 16:34:08 ### CVMAStorageProtect::is_storagepool_exist() - Storage pool not configured
2488748 25f9ff 03/17 16:34:08 --- Storage pool not configured
2488748 25f9ff 03/17 16:34:08 --- skipping checking RWP protection
2488748 25f9ff 03/17 16:34:38 ### CVMAStorageProtect::is_storagepool_exist() - Storage pool not configured
2488748 25f9ff 03/17 16:34:38 --- Storage pool not configured

 


Also please let me know where can i find the CVHedvig.log , i could not find it in var/log/commvault.

Also please suggest what should be the best next course of action.

P
Vaulter
Forum|alt.badge.img
  • PB&JVaulter
  • Vaulter
  • March 17, 2025

Hi there Noushad -- generally, HyperScale X installations may be able to register themselves successfully to a CommServe, but likely, some potential installation step may have failed when communicating a request to the CommServe to create the Storage Pool. When HyperScale X installations are performed for a cluster, a ‘cvmanager.log’ spawns on one of the nodes being used during the deployment. That should have a little more information as for what may have gone wrong during the storage pool creation (could be a networking hiccup,for example).

The cvmanager.log has the purpose of just filling in details of what has completed, failed, or not been attempted during a HyperScale X installation -- think of it like a checkpoint monitor that also populates more detailed failure information when HyperScale X installations encounter a problem.
 

Regardless of what the issue may be, in most instances, it’s suggested to contact Commvault Customer Support for further assistance in addressing the issue as the resolution may involve some more detailed command line work that crosses outside of the installer.

N
Forum|alt.badge.img+7

Thank you for the response ​@PB&J 

i will try to find cvmanager.log, also any idea where we can find CVHedvig.log ?

P
Vaulter
Forum|alt.badge.img
  • PB&JVaulter
  • Vaulter
  • March 18, 2025
Noushad wrote:

Thank you for the response ​@PB&J 

i will try to find cvmanager.log, also any idea where we can find CVHedvig.log ?

Generally, CVHedvig.log should be in /var/log/Commvault/Log Files/ of at least one of the nodes, but there may be issues where it doesn’t generate during installation erroneously -- I’d suggest consulting the cvmanager.log for any type of ‘exception’ language, which could lead to further investigation. 

N
Forum|alt.badge.img+7

Hi ​@PB&J ,

Thank you for the response.

if we found or didnt find any errors in the logs,  do you suggest i re-install the HSX software on all 3 nodes and then do cluster configuration again from scratch ?

P
Vaulter
Forum|alt.badge.img
  • PB&JVaulter
  • Vaulter
  • March 19, 2025

Noushad,

I would suggest to open up a case with Commvault Customer Support as the issue could happen again on a retry. Understanding what may have happened with the help of support team, can help avoid the issue from occurring again on a reattempt, not to mention that this issue could possibly occur during expansion of the cluster. 😀 

Reply


Most helpful members this week

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings