Hi Anders,
Thanks for the clarification. For standalone physical SQL Servers with 30+ TB databases, I agree that IntelliSnap with Backup Copy is a good fit for what you are trying to achieve.
With IntelliSnap, SQL/VSS quiesces the database and an application-consistent hardware snapshot is created on the supported storage array. Once the snapshot completes, the application is released. During Backup Copy, the snapped LUN is mounted to the configured proxy MediaAgent, and the proxy reads the snapshot and streams the data to the backup storage.
So your point is correct: the production SQL Server is involved in creating the application-consistent snapshot, but the longer data movement for the 30+ TB dataset can be handled through the proxy instead of having the production server perform the full streaming backup.
Regarding why your Linux-based HyperScale X/Flex Open MediaAgents are not available under Use Proxy, the SQL Server IntelliSnap subclient documentation states:
https://documentation.commvault.com/11.44/commcell-console/configuring_sql_server_intellisnap_subclient.html
The MediaAgent must have an operating system level that is the same or higher than the client computer.
For a Windows SQL Server client, I would therefore use a compatible Windows MediaAgent as the IntelliSnap Backup Copy proxy, running the same or a later supported Windows Server level than the source. The proxy would also need the necessary FC/iSCSI connectivity and array access so that the snapshot LUNs can be presented and mounted.
So I would look at the design as:
Physical Windows SQL Server → Supported storage array → IntelliSnap → Windows proxy MediaAgent → Backup Copy storage
Your HyperScale X/Flex Open environment can still remain part of the overall backup/storage architecture; the additional Windows MediaAgent would provide the Windows-compatible snapshot mount and Backup Copy path.
For the 30+ TB databases, it is also worth looking at Allow multiple data readers for Backup Copy and configuring an appropriate number of streams. This can parallelize the Backup Copy, provided the proxy, SAN, network and destination storage can sustain the additional throughput.
Before implementing it, I would validate the exact storage-array model and snapshot engine, Windows/SQL versions, database and log LUN layout, FC/iSCSI zoning and LUN presentation, MPIO requirements, and whether the specific SQL/storage combination supports the required snapshot and recovery operations.
I would also validate hardware revert separately. Retaining the array snapshot does not by itself mean every SQL/storage configuration supports an application-consistent revert.
Based on what you have described, I would therefore continue with the IntelliSnap + Backup Copy approach and add/designate a suitable Windows MediaAgent proxy, rather than switching the 30+ TB databases back to a traditional streaming backup.
Regards,
Karthick