Share backups for Manila use an approach that looks like the backups for Cinder. During the Bobcat release, SAP implemented all related backup APIs, as well as a generic NFS backup driver, which works similarly to the generic shares migration, and also makes use of the manila-data service.

This implementation is still considered experimental, and we will graduate the APIs upstream as soon as we can confirm they are stable and that there are no major bugs in the implementation.

What are the use cases this RFE is solving?

High Level view on how the feature works

Is this feature driver dependent or driver related?

Yes, only NetApp for now. 

Can this feature be turned on or used in an existing environment?

Yes, could be enabled with upgrade. 

Does this feature depend on another RFE?

Experimental API in upstream

How will the feature affect performance or scaling?

Any effect would be on backend side, not something that can be  mitigated or impacted by manila

What are the test cases for this RFE?

https://review.opendev.org/c/openstack/manila-tempest-plugin/+/841015 

Are there CI implications?

Once API is graduated, we can run some of the tests, bulk of it rests on NetApp

Does it have documentation impact and require early planning with the doc team?

Config, admin, user documentation

How much upstream resistance might there be to this feature?

None, NetApp has implemented in Caracal, currently experimental.

Will this feature require new or different support skills?

Primarily vendor feature, any bugs or customer cases would need to involve NetApp.

Will this be required for knowledge transfer to GSS?

Demo would be helpful, to showcase workflow. 

Will this feature impact existing partners or certification programs?

Testing functionality would be almost entirely on NetApp, as currently they are the only one supporting it.