Active snapshots limit reached for datastore

[Kirill.Naumenko]

Each time we create a snapshot for a VM we check how many snapshots we have created for backup. This is per Datastore. There is no counter, we check actual situation.

Sorry but how other jobs that stucking on such step - "Active snapshots limit reached for datastore" understand how many snapshots on datastore if Veeam don't have counter about it?
I have more then 80 jobs on different datastores - and I don't understand how many snapshots at different time exist.
I have different datastores -VSAN, ISCSI on Windows,Linux repositories - is it normal to change this parameter for all of them at one time?

[Andreas Neufert]

As I said this was configured in a way that there will be no issues at our 300.000 VMware customers. Individual storages are much faster and do not run into high latency when you create snapshots or snapshot commits. So you need to test maybe in a way by increasing the setting by 1 each day and see if you run into issues.

[Andreas Neufert]

At performance tests we usually use arround 20 snapshots.

[Hoegimator]

Hi all,

We are running v.9.5.0.1922, our vSphere Storage is Cisco Hyperflex v.3.5(2a) with ESXi 6.5u2.

Today I saw the limitation of active Snapshots "Resource not ready: Active snapshots limit reached for datastore".
All the Google researches pointe to the registry entry "MaxSnapshotsPerDatastore (REG_DWORD)", but we don't have that registry entry.

Therefore my first question is, where is that limitation set?
Secondary, is that "MaxSnapshotsPerDatastore" registry still valid?

Thanks for any advise
Joerg