Feature request - extend plugins version compatibility

[radek.havel]

Hi to all,

I raised the point to Veeam support originally and I was advised to open my point to this forum.

We are heavily using Veeam plugins for SQL, Oracle and Agent. Customer do not allow login connection from VBR server to VM machine based on security standards they use.

It is causing hard time every time for every VBR update where is mandatory also update all 120 VM machines with Veeam plugin. If we do not update it we will be not able to do further VBR updates.

I would like to have new feature which would allow us to run older Plugin versions with even limited about new feature support ? It i surprised for us that Veeam plugin database backups just simply stop working.

We migrated from Spectrum Protect where we could have very old Storage Protect for Databases installed still working normally.

We got opened Case #07564441

Thank you in advance

[Andreas Neufert]

Hello Radek, we support one version/update back in order to update the Enterprise Application Plug-ins after the Backup server was updated.

Or do you speak about the persistent guest components? https://helpcenter.veeam.com/docs/backu ... ml?ver=120

[radek.havel]

Hi Andreas,

yes it is about standalone Veeam plugins for Agent, SQL, Oracle. We got those deployed on RHEL, Windows OS for our customer.

[Andreas Neufert]

Veeam Plug-in for Microsoft SQL:
"Veeam Backup & Replication supports two latest versions of Veeam Plug-ins. For example, Veeam Backup & Replication 12.3 supports Veeam Plug-in 12.3 and 12.2."
https://helpcenter.veeam.com/docs/backu ... ml?ver=120

Veeam Plug-in for Oracle RMAN:
"Veeam Backup & Replication supports two latest versions of Veeam Plug-ins. For example, Veeam Backup & Replication 12.3 supports Veeam Plug-in 12.3 and 12.2."
https://helpcenter.veeam.com/docs/backu ... ml?ver=120

For the Agents there is a compatibility matrix:
https://helpcenter.veeam.com/docs/backu ... ml?ver=120

Does this address your question/feedback?

[radek.havel]

Hi Andreas,

yes this is very thin compatibility. We basically need to update 120 VM Veeam plugins right after VBR update to be able to do further VBR updates. We would like to have compatibility for major version like 12.x which would give us more space even we will not be on last features and security patches for plugin. Is my demand understandable this way ? Thank you in advance

[Andreas Neufert]

I think my answer to this one was somehow lost in the maintenance update.

Yes, I understand. We have a feature for automatically managing updates of the plug-ins and agents. It is called Protection Groups. You can use them as well just to update the plug-ins but still use the local processing.

Protection group will daily check for updates of Agents/Plug-ins (whatever is selected). As well it manages certificate base authentication from Agent to Veeam Backup & Replication. I suggest to do a test with some of the servers, specifically for the transition.
Potentially do the change as a new full is anyway planned then. (Old restore points might be needed to restore with the recovery token from the previous processing) if you need to access older backups.

For the RMAN plug-ins it is important to define as well the channel definition.

Central Management (Protection Groups) for SQL plug-in will follow in future releases.