The requirements that apply to every VCF Extension — VCF Operations version, Cloud Proxy, TLS, certificate handling and registry access — are defined once in Technical and Security Requirements.
This page describes only what is specific to VCF Backup Storage Insight: the permissions required on the appliance, the connection to it and the adapter fields.
| Component | Minimum | Verified with |
|---|
| VMware Aria Operations (VCF Operations) | 8.10.0 | current 9.x release |
| Quantum DXi | to be confirmed in the deployment card | to be confirmed in the deployment card |
| Commvault CommServe | 11.x | 11.x |
| Category | Description |
|---|
| Quantum DXi account | A dedicated read-only account on the appliance. The account must be allowed to read the system status, the storage capacity and deduplication statistics and the replication configuration. |
| Commvault account | A dedicated read-only account on the CommServe, allowed to read the storage policy and storage target inventory through the Web Console REST API. |
| One adapter per appliance | Each adapter instance connects to a single appliance. Several appliances are covered by one adapter instance each, and the shared object model joins them into one estate. |
| Cloud Proxy to appliance | HTTPS on port 443 from the Cloud Proxy belonging to the collector group to the management interface of the appliance. |
| TLS | The certificate of the appliance management interface is validated against the system trust store. Self-signed certificates are supported through the Skip TLS certificate validation parameter, intended for lab or explicitly accepted targets. |
- SSH as
root to the Cloud Proxies belonging to the collector group where the adapter is to run. - Log in to the registry:
docker login registry.indevops.com. Use the Harbor robot account designated for that deployment, provided by Indevops. - Pull the image:
docker pull <IMAGE NAME>. The image name is shown on the release page for the version being installed.
- Download the PAK file matching the pre-pulled adapter image.
- In VCF Operations go to
Data Sources > Integrations > Repository > Add and upload the PAK file, selecting both Install the PAK file even if it is already installed and Ignore the PAK file signature checking. - Complete the installation wizard.
- Go to
Administration > Integrations > Repository, filter for INDEVOPS and select the VCF Backup Storage Insight brick. - Select
ADD ACCOUNT. - Fill in the credentials and the instance parameters below.
One credential type, Backup storage credentials, shared by both vendors.
| Field | Definition |
|---|
Username | Account name on the backup storage system |
Password | Password of that account |
| Field | Default | Definition |
|---|
Name | — | Unique name of the adapter instance |
Description | — | Free-text description of the instance |
Vendor | Quantum | Producer of the device this instance connects to: Quantum uses the DXi management API, Commvault reads Storage Targets from a CommServe. Both share the same object model. Part of the instance identity. |
API Host | — | Hostname or IP address of the management interface of the appliance or of the CommServe |
API Port | 443 | Port of the management API |
Credentials | — | Account used for collection, see above |
Collector / Group | — | Collector group that runs the adapter; must contain a Cloud Proxy with the image pre-pulled |
Skip TLS certificate validation | false | Disables certificate verification when connecting to the API. Insecure; keep false on production systems. |
Replication RPO (minutes) | 1440 | Recovery point objective used to evaluate the replication lag. A lag above this value raises the RPO Breached alert. |
Capacity warning threshold (%) | 80 | Used-space level that raises the Capacity Warning alert |
Capacity critical threshold (%) | 90 | Used-space level that raises the Capacity Critical alert |
Collect events | true | Whether appliance events are collected and raised in VCF Operations |
Adapter Memory Limit (MB) | 1024 | Maximum memory the adapter container may use |
Log Level | Normal | Logging verbosity: Debug, Normal or Trace |
