1. What is the nature and description of the request? Important

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

• Customer's Core Problem: Customer has a strict organizational policy against permanent sudo privileges on servers. They are willing to use sudo manually for restore/maintenance but must be able to remove it for daily backups.
• Customer's Finding: My initial analysis shows that the backup.yml playbook and its tasks/subtasks do not appear to contain “become: true”, leading the customer to challenge why permanent sudo is required for backup operations.
• Urgency: The issue has been escalated by the customer as a critical blocker for their AAP production environment.
• Latest updates : 

1. This is already in the email with Dylan Silva and Chad Ferman and Nicholas Chia
2. The customer already tried and noticed that the backup runs successfully without sudo; however they have not tested if the resulting backup can be successfully restored.

3. How would you like to achieve this? (List the functional requirements here)

This RFE is for two things : 

• (Either) Request an official agreement that Red Hat supports backup operations without needing a sudo and release a document on that.
• (Or) Make necessary changes to the existing/upcoming AAP so that backup can be done without SUDO

4. List any affected known dependencies: Doc, UI etc.. : NA

5. Github Link if any : NA

6. Additional details of customer : 

hey have 2 different type of setup : All these are AAP 2.5 

1. Containerized Growth-technology (all in one) - around 3 of such setup (installer managed DB)
2. Containerized AAP “cluster” (2*VMs for controllers; 2*VMs for PAH, 2*VMs for Gateway etc)

• Using Installed managed database on external VM
• Here they have plans to move the Database out to “customer provided” in the future during the next upgrade