What Is Commvault Global Active Device
To understand what is commvault global active device, look at how backup software talks to storage. It is an integration between Commvault backup tools and Hitachi Global Active Device storage arrays. Hitachi Global Active Device mirrors storage volumes across two separate arrays in real time. Both storage systems stay active and accept read and write requests at the same time. Commvault uses this active-active setup to run snapshots and backups from either site. If one storage array fails, bac
Active Directory + IoT Device Identity Management: the complete guide
Architecture patterns, implementation strategies, and security best practices. Delivered to your inbox.
To understand what is commvault global active device, look at how backup software talks to storage. It is an integration between Commvault backup tools and Hitachi Global Active Device storage arrays.
Hitachi Global Active Device mirrors storage volumes across two separate arrays in real time. Both storage systems stay active and accept read and write requests at the same time. Commvault uses this active-active setup to run snapshots and backups from either site. If one storage array fails, backup jobs keep running on the second array without stopping.
How what is commvault global active device works in practice
In a standard setup, two Hitachi storage arrays sit in different data centers. The storage software creates a virtual volume that spans both physical arrays. Host servers see this pair of volumes as one single disk.
When an engineer or an AI agent triggers a backup, Commvault talks to the storage array. The backup software picks one side of the mirrored pair to take a hardware snapshot. Taking the snapshot on the secondary array keeps extra load off the primary production array. After the snapshot finishes, Commvault mounts that copy and moves the data to backup media.
An external quorum device watches both storage arrays to prevent split-brain errors. If a network link drops, the quorum device picks one array to stay online. Commvault detects the surviving array and routes future snapshot tasks to that active side. Engineers do not need to rewrite backup schedules when a site goes offline.
Security and operational tradeoffs in storage management
Running active-active storage backups requires broad permissions across multiple systems. Commvault needs admin keys for both Hitachi storage arrays to create and delete snapshots. Engineers and automation scripts also need role permissions to run backup jobs and restore data.
Most teams rely on static service accounts to link the backup server to the storage arrays. Static keys create a major risk if an attacker or a flawed script steals them. Role checks inside the backup tool only control who can click a button or start a job. Once a session starts, the user or agent often holds wide permissions for the whole session.
Active Directory + IoT Device Identity Management: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
Native storage logs track volume creation, but they miss the human context behind a request. If an engineer queries a restored database volume, storage logs do not show the query text. Static roles also cannot inspect the data flowing back to a user during a restore test. Sensitive fields like emails, phone numbers, card numbers, or national IDs return in plain text. Without query-level checks, teams must manage another set of standing credentials across two data centers.
Teams must also watch replication lag and network health between the two sites. High write volume can strain the link between the primary and secondary storage arrays. When engineers debug these replication issues, they often log in directly to storage management consoles. Giving engineers direct console keys widens the blast radius of a single mistake.
Govern statements and responses across databases and APIs
Good config and scoped roles are needed setup. They do not check single queries in flight or mask sensitive fields in returned rows. Across Postgres, MySQL, SQL Server, MongoDB, ClickHouse, Kubernetes APIs, SSH, and internal HTTP endpoints, hoop.dev runs beside each supported service as an open-source proxy, a sidecar for your database or API.
First, hoop.dev guardrails block banned queries before they run. Then hoop.dev data masking rewrites matched sensitive values in responses in memory. The audit trail records every statement and verdict per resource. Furthermore, hoop.dev holds SOC 2 Type II and is open source on GitHub.
Frequently asked questions
Does Global Active Device replace regular backups?
No, active-active storage replication is not a replacement for offline backups. If a bad script deletes data on one volume, the deletion copies to the second array right away. You still need Commvault snapshots and separate backup copies to recover from logical data loss.
What happens to backup jobs if the primary storage array goes down?
The Hitachi storage cluster shifts all read and write traffic to the secondary array. Commvault senses the path change and directs snapshot requests to the surviving array. Backup and restore tasks continue without manual fixes from the storage team.
How do teams protect sensitive data inside restored storage snapshots?
Teams often mount snapshots to test servers so engineers can check data or debug apps. To protect private records during these checks, teams add controls at the database query level. Data masking rewrites matched fields like card numbers or emails in query results during the session.
Short role checks help teams work fast. Simple rules make each review clear. Good logs keep every team safe. Scoped keys stop bad changes early.