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?
Are there any known limitations? (e.g multi attach + encryption)
Is a CLI change required, does the openstack cmd support it?
Does this RFE impact / need to be included into the control plane podification?
Does this RFE benefit/impact DCN?
Does this RFE benefit/impact shift on stack?
Can this feature be turned on or used in an existing environment?
Does this feature affect another DFG or product?
Does this feature depend on another RFE?
How will the feature affect Upgrades?
How will the feature affect performance or scaling?
What are the test cases for this RFE?
Are there CI implications?
Does it have documentation impact and require early planning with the doc team?
Are there known packaging challenges?
Are there any security considerations?
How much upstream resistance might there be to this feature?
Will this feature require new or different support skills?
Will this be required for knowledge transfer to GSS?
Will this feature impact existing partners or certification programs?
API Deprecation/Compatibility?
Are any GUI impact/changes required (Horizon)?