Remove components
Removal step 3. Complete backups and handover, review deletion scope, and record the customer acknowledgement before executing removal.
Important: the full-removal command starts the destructive cleanup of Lifecycle Manager. Do not rely on a later confirmation prompt to perform backup or impact review.
1. Confirm the user, host and package
Run on the agreed dedicated Lifecycle Manager host as Linux user dbaasnow:
whoami
hostname -f
cd /opt/software/dbaasnow_v3_0_2026
ls -l uninstall_dbaasnow
Use the matching extracted installation package retained for this deployment. If the staging directory differs, use its actual path.
Confirm the host is the platform being retired. The Linux account is separate from the Broker admin login.
2. Review usage
./uninstall_dbaasnow --help
The standard cleanup in this guide is full Lifecycle Manager removal. An agreed custom removal requires its own dependency/path review.
3. Reconfirm the execution gate
Before the next command, confirm:
- External backups and required records are verified.
- Retained target databases have a continuing owner and monitoring arrangement.
- Cluster and other shared dependencies have been checked or handed over.
- Target DNCollector retirement/reconfiguration is addressed separately where required.
- The owner and operator have acknowledged loss of this platform's console, operations, records, monitoring and notifications.
4. Run full removal
./uninstall_dbaasnow --components all
--components all selects all installed platform components and their supporting services. Enter the Linux account's requested sudo credential at the prompt.
The process removes platform services and associated files/data on the installation host. Follow the output for each selected component.
If terminal recording is used, retain the output outside removal paths and exclude secrets. For example, as an alternative to the command above, capture it in the account's home directory and copy the record to the approved external retention location afterwards:
mkdir -p ~/dbaasnow-removal-records
set -o pipefail
./uninstall_dbaasnow --components all 2>&1 | tee ~/dbaasnow-removal-records/uninstallation.log
Use either the plain invocation or the captured invocation for the run, not both. This log copy is not a substitute for the verified platform backups completed before removal.
5. Review the result
If the process reports a failed component, preserve the first error and identify what has already been removed. Use recovery and support before another attempt.
An elapsed-time summary does not verify every service, package and cleanup path. Complete removal verification.