We need a design document for backup and restore functionality (something like we had for operator) - the only resources I was able to gather are the pull request and a brief description in ENTESB-12436 and RHMI needs here, if there is one, please link it here.

What I'm interested in is:
1) supported scenarios / use cases:

• I have "destroyed" syndesis in my namespace - what is the procedure?
• I have the backup and empty namespace - should that work? If so, how? Do I create manually the resources and everything works?
• What about integrations? They behave funky when I have empty namespace (syndesis server doesn't count with the fact that the image stream for the integration may be missing)
• Creating manual backup only creates database dump and no resources - it is intentional?

2) current state - for example ENTESB-12436 is in productization backlog and has "first list of actions" of which only 1/3 is done
The PVC is not used for backup and the custom resource is not saved in the resources
3) what is still TBD for current release / full functionality