Veeam Plug-In for Oracle RMAN and StoreOnce Catalyst Store limit

It is my understanding that this is a StoreOnce filesystem scalability limit, not a Veeam licensing rule.

NAS shares screens and properties | HPE StoreOnce 3660, 5260 and 5660 Systems User Guide for StoreOnce software version 4.3.x 

Thank you, Jason. the link you shared is for the scenario of using StoreOnce NAS shares as backup target and not using the StoreOnce Catalyst Store. In addition, there is no mention on the filesystem limitation on the link you shared as well. Care to clarify?

My understanding is that HPE explains how StoreOnce Catalyst scales across its user guides and configuration manuals by focusing on system design, object tracking, and filesystem capacity limits. Although HPE doesn’t publish a specific maximum number of files for a Catalyst store, the platform does monitor object counts and enforce filesystem limits, which means scalability needs to be considered during the design phase.

In my opinion, if Veeam has documented a hard limit, it’s likely based on historical support cases and close work between Veeam R&D and HPE to understand how StoreOnce behaves in real‑world scenarios. Veeam would have more detailed, practical insight from these cases, which explains why they document specific limits based on that deeper, hands‑on knowledge.

Planning on using StoreOnce 5720

what have read of this blog post, leduardoserrano has review them this model. 

New HPE StoreOnce 7700 and 5720 Certified as Veeam Primary Repository Ready | Veeam Community Resource Hub

Thanks. Looked at the blog post. No mention on per Catalyst Store’s max. file count limitation again.

Hi ​@sionghoe -

Unless someone from Veeam Product Management actually comments here (which is rare), we cannot say why there is the limit you see from the User Guide. Your best bet is to either inquire to Product Managers directly over on the Veeam Forums, or create a Veeam Support case.

Best.

Thank you, ​@coolsport00 

No problem ​@sionghoe 👍🏻