Skip to main content
Solved

IntelliSnap

  • Nov 11, 2026 11:03 AM UTC
  • 16 replies
  • 69 views

ApK
Explorer
Forum|alt.badge.img+8

Hi all.

 

I have a mix of HyperScaleX/Commvault Grid servers and Commvault Flex Open MediaAgents, so no Windows MediaAgents.

I’m looking into utilizing IntelliSnap for hardware snapshots of physical servers. The client servers I want to use IntelliSnap on, is a mix of Linux and Windows servers.

When I try to configure the IntelliSnap on the Windows client servers, I’m not able to choose any of the HypeScaleX/Flex Open MediaAgents as the proxy. Does this mean that I cannot use IntelliSnap on Windows servers unless I have a Windows MediaAgent?

 

Thanks

-Anders

Best answer by Karthick R

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

View original

16 replies

Forum|alt.badge.img
  • Vaulter
  • Nov 11, 2026 1:39 PM UTC

Hi Anders,

If you are referring specifically to IntelliSnap for physical Windows File System clients, then yes, this can be expected.

As per the Commvault IntelliSnap documentation, the proxy MediaAgent needs to be compatible with the source volumes being presented and mounted. For Windows File System snapshots, this generally means using a Windows MediaAgent as the proxy. Hence it is not showing the HyperScale(linux MA) I think so.

There may also be additional requirements depending on the source OS, proxy OS, storage array/snapshot engine, and the type of IntelliSnap operation being performed.

I would recommend checking the current configuration against the documented requirements here:

Hope this helps.


ApK
Explorer
Forum|alt.badge.img+8
  • Author
  • Explorer
  • Nov 12, 2026 12:40 PM UTC

​@Karthick R Thanks for your answer.

 

We are going to use the IntelliSnap for all workloads, Windows File system, Linux file system, MSSQL, Oracle etc. 

Are there any reason why IntelliSnap can’t be used cross platform? 

 

Regards

-Anders


Scott Moseman
Vaulter
Forum|alt.badge.img+23

Are you trying to use IntelliSnap for volumes mounted on snappable storage?  If you’re talking about local storage on physical servers, they probably are not supported for IntelliSnap.

https://documentation.commvault.com/11.40/software/supported_storage_arrays.html

Thanks,
Scott
 


Forum|alt.badge.img+19
  • Vaulter
  • Nov 13, 2026 9:36 PM UTC

IntelliSnap proxy for Backup copy process has to be the same OS type as the source client, it has been since SnapProtect feature released in version 8.

I will provide you with an “IA-response” that somehow points to what you already suggested.

The requirement for the IntelliSnap proxy used in backup copy operations to have the same or a newer operating system version as the source client is due to compatibility and technical limitations in how snapshots are mounted and accessed. Here are the main reasons:

  • File System and Volume Manager Compatibility: The proxy must be able to understand and mount the file systems, volume managers, and storage hierarchies present on the source system. If the proxy runs an older or incompatible OS, it may not recognize newer file system features or volume manager metadata, leading to mount or data access failures.

  • Snapshot Mounting and Hierarchy Recreation: During backup copy, Commvault recreates the storage hierarchy from the snapshot metadata on the proxy. This process requires the proxy OS to support all features and drivers used on the source. A mismatch can prevent proper mounting or access to the snapshot data.

  • Driver and Kernel Support: Newer operating systems may introduce changes in device drivers, kernel modules, or storage stack behavior. Using a proxy with an older OS could result in missing support for these changes, causing backup copy jobs to fail.

  • Vendor and Application Requirements: Some storage arrays and applications require the proxy to match the source OS version to ensure consistent snapshot handling and data integrity.

Summary:
The proxy must be the same or newer OS version to guarantee it can correctly mount, read, and process the snapshot data, ensuring reliable backup copy operations and successful restores.

Documentation Links

 

 


Could it been that you are talking about storage intellisnap or just a client base snap


If this workload are all vm then you can do intellisnap from the virtual based and use any of your storage for the intellisnap this will speed up backup process with a good throughput 


ApK
Explorer
Forum|alt.badge.img+8
  • Author
  • Explorer
  • Nov 18, 2026 12:13 PM UTC

​@Scott Moseman 

​@Emmanuel 2027 

 

I want to protect for instance MSSQL on a physical server, take a snapshot of the database, and then do a backupcopy. Keep the snapshot on the storage system to be able to revert the MSSQL.

It could also be volumes mounted on snappable storage to backup the whole FS disk.

 

Regards

-Anders


There is two things here when u say physical do u mean physical box server? Or the vm was discover from a vm 

 

if its a vm physical server db then storage snapshot can be taken via the storage layer 

 

or you can take a backup of the db then make auxiliary copy of it to a secure storage or tape which u can revert to it any time 


ApK
Explorer
Forum|alt.badge.img+8
  • Author
  • Explorer
  • Nov 18, 2026 12:24 PM UTC

​@Emmanuel 2027 

Standalone server, non virtual. 


We can push Commvault to the server  with db and back it  up instead of going through a long route of intellisnap

 because the goal here is to make sure the db is protected 


ApK
Explorer
Forum|alt.badge.img+8
  • Author
  • Explorer
  • Nov 18, 2026 1:12 PM UTC

​@Emmanuel 2027 

I am doing agent backup, I just want to utilize IntelliSnap in the process. I have a couple of servers with 30+TB of databases. With IntelliSnap they are protected in seconds, and when running the backup copy process, the server is not involved in making the snapshot into a streamable copy. With a traditional agent backupm the CPU is heavily loaded during the backup period. 


Forum|alt.badge.img
  • Vaulter
  • Answer
  • Nov 18, 2026 2:02 PM UTC

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


ApK
Explorer
Forum|alt.badge.img+8
  • Author
  • Explorer
  • Nov 18, 2026 2:12 PM UTC

​@Karthick R 

 

Some times it’s not easy to find the documentation, and this part I did not find :-(

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.

 

But thanks for the clarification, I will have to convince my management to give me money for another physical Windows server, just happy that hardware prices have not increased lately ;-)

 

Regards

-Anders

 


Forum|alt.badge.img
  • Vaulter
  • Nov 18, 2026 2:24 PM UTC

Hi Anders,

Glad that helped.

At least you now have the documented requirement to support the case for the additional Windows MediaAgent with management. Hopefully the hardware pricing remains on your side 😄.

Thanks for the discussion and for sharing the use case.

Regards,
Karthick


This was part of the two options I suggested above that you can perform storage level intellisnap for the db if the conventional approach is not accepted 

doing the storage level snapshot is a faster way to take backup of 30Tb but in my own environment I do backup a db of 120tb using the backup model and it takes 8hour to complete the backup 

so snap snapshot backup is faster but it has its own limitations to oracle db 

 

my environment is a big space we hv mixed and i kn both challenges if i hv to advice a client on what to choose 


Scott Moseman
Vaulter
Forum|alt.badge.img+23

​@Emmanuel 2027 

I am doing agent backup, I just want to utilize IntelliSnap in the process. I have a couple of servers with 30+TB of databases. With IntelliSnap they are protected in seconds, and when running the backup copy process, the server is not involved in making the snapshot into a streamable copy. With a traditional agent backupm the CPU is heavily loaded during the backup period. 

 

What type of storage is the database hosted on?

Thanks,
Scott