anybody tried to combine that with a HybridFileStore Share yet? Somewhat similar to what is proposed with the ElasticSearch Backup Workflows provided in Store. Might be a great solution to save the space for the additonal copy as well as time.
Preparing to refresh our Environment we have the same question. Documentation doesn’t state anything in regards to additional Workloads that can or cannot be put onto HSX. Just because something works doesn’t mean it is supported or will still work after the next update.Are there plans to Document which Packages can be added to HSX and what Features and Feature Combinations are supported on this Platform?Reaching a bit, when the IndexStore deployed for VSA FileIndexing would also be used for other Activate Indexes and may also be used for HybridFileStore the HSX Node might be brought to it’s knees (assuming it still deploys only on the first Node of a given Pool and doesn’t implement scale out or other resiliency features in HSX context).
Hi JosThat is exactly the thing we do not want I’m afraid. The MediaAgent should stay and be the Coordinator and Coordinator only. The VSAs should be proxies and proxies only. No VSA can communicate with the vCenter, not allowed, they can talk to the ESX to read data via hotadd or nbd. Strictly dividing control and worker plain. Hope that is possible today, if not it should be a feature IMHO.Cheers, Stefan
this is a known and expected behavior according to Devs. Archive Index always triggers a Index Restore, regardless of it being needed or not.We logged CMR 344442 to change this, last we know that is planned for FR29.
we use exactly such a black/white subclient setup for our customers.One “NoBackup” Subclient where all VMs are added that do not need saving, either as distinct named VMs or via Custom-Attribute set in vCenter. StoragePolicy for this pointing to a Commvault Virtual Library, the closest we can get to a Null-Device and Activity is disabled anyways.Another set of Subclients works the same, just with appropriate StoragePolicies for the Retention-Requirements.This setup has the convenient benefit for us that everything that for some reason falls through the cracks is still covered by default-Subclient. If a VM misses its Tag/Attribute or is not added to any Subclient it will nevertheless get a base level of security via default-subclient.Mentioned challenge that VM can be part of multiple Subclients we cover using Workflows. Customer orders a VM to be backed up or not via API (/wapi) where our logic adds the VM to respective Subclient and checks all others to remove conflicting entries. Of
Hi JosGood hint, thanks for that. Considered going that route but abandoned it for couple of points. Main one being that we heavily use Workflows for Automation and with that the qCommand-XML API to configure things. Options on REST-API didn’t always translate well in past, other keywords, other structures, other requirements. Second being API previously omit many options, though trying it now seems got better, options like “excludeFromSLA” that are set are still missing though. Last and major one to me, most of the options are not documented at all or are incorrectly documented (f.E. applicationId for FileSystem supposedly being 33 when that only applies for Windows and must be 29 for Linux or “useGlobalFilters” claiming it uses string-values while API returns integer with no info on what maps to what, etc).Not to keen on starting from scratch under those circumstances and bit too lazy for that if I’m honest 😅BR Stefan
same issue here with rhel 8.7 and Commvault 11.24.86, FRELs and Index Servers dead since updating.
There are multiple Modules and Plugins for Commvault, like the mentioned Powershell CommandLet. In regards to IaC the two most fitting options would be Ansible https://github.com/Commvault/ansible and TerraForm https://registry.terraform.io/providers/Commvault/commvault/latest/docs.Personally can’t recommend either yet. Ansible doesn’t seem to bet much love and barely can do more than start backup or restore from what I know. Terraform is actively developed, got some nice cleanups and enhancements lately, nevertheless it is still very early and can only support a handful of workloads and entities.Maybe check out the Python Plugin, it is basis for some of the other Plugins and can do more https://github.com/Commvault/cvpysdk.Personally am working my way through REST API to build a repo of requests to bootstrap and base-config our next Prod Environment. No IaC at all, but better than a million clicks in Java or Webbrowser :-)
could you share links to those ansible playbooks? I only know the couple on Git. Customer would like to automate Backup & Restore Testing for FileSystem and VSA, having something ot go by would be helpful.
Checked my HSX 2.0 and “firewall-cmd --state” returns the expected “running”are you on HSX 3.x? if so might be a issue in the new Image
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.