What is the nature and description of the request?

With the current implementation of ODAP operator, backup and restore is per cluster and can only be changed cluster wide. Individual namespace administrators should be able to use the operator independently of each other and also be able to create different DPA and backup locations to facilitate different ways of doing backup and using different backup locations for different purposes. 

Why does the customer need this? (List the business requirements here)

An administrator should have the ability to create different kinds of backups of the same application, perhaps also using different data locations.

Examples might be, frequent backup should go only to snapshots, daily backups should go to an additional backup location for short term backup, and a 3rd one weekly might require to be stored in a different backup location.

How would the customer like to achieve this? (List the functional requirements here)

1. allow the definition individual backup names per namespace 
2. allow the installation of the operator into multiple individual namespaces to allow individual backup location definitions per namespace
3. allow the installation of the operator into multiple individual namespaces to allow individual Data Protection Applications per namespace
4. allow the installation of the operator into multiple individual namespaces to allow namespace administrators to individually manage the backup/restore and it's resources

For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.

1. an individual backup in two different namespaces can be created using the same name in both namespaces 
2. two different backup location definitions can be created in two different namespaces, one per namespace
3. two different Data Protection Applications can be created in two different namespaces, one per namespace
4. a namespace administrator can define, change, and perform individual backups/restores and schedules while another namespace administrator can do this independently in his own namespace