IntelliSnap

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:

• IntelliSnap - Advanced Snapshots - Windows File System iDataAgent
• MediaAgent: System Requirements
• https://documentation.commvault.com/11.46/commcell-console/intellisnap_frequently_asked_questions_windows_file_system_idataagent.html

Hope this helps.

​@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

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
 

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

• IntelliSnap Backup: System Requirements (compatible)
• Backup Copy Operations for Microsoft Hyper-V
• IntelliSnap - Frequently Asked Questions - Windows File System (FS) iDataAgent