How to Remove VCF Log Management 9.1 Without Uninstall Button and Free Up 2TB Disk Space
Step-by-step guide for VMware/VCF admins and MSP engineers to remove VCF Log Management 9.1 without an uninstall button, reset passwords, and reclaim 2TB of disk space.
Introduction
Are you facing disk pressure caused by VCF Log Management in VMware Cloud Foundation (VCF) 9.1 but can't find an uninstall button? Many administrators encounter this issue, especially when managing log retention and disk reclamation in VCF 9.1. This guide provides clear, actionable steps to remove VCF Log Management 9.1 components manually, reset necessary passwords, and recover up to 2TB of disk space.
Prerequisites / What You Need
Before proceeding, ensure you have the following:
- Administrative access to the VCF 9.1 environment, including SDDC Manager and vRealize Suite components.
- SSH access to the VCF Log Management appliance (VVF 9.1).
- Backup copies of configuration files and credentials.
- Familiarity with Linux shell commands and VMware CLI tools.
- Latest version of VCF 9.1 documentation or VMware KB articles on log management.
Do this now: Verify your access to the VCF Log Management appliance via SSH and confirm you have SDDC Manager credentials ready.
Step 1: Identify Log Management Components and Disk Usage
Start by assessing which components of VCF Log Management are consuming the most disk space.
- SSH into the VCF Log Management appliance:
bash ssh admin@<log-management-appliance-ip> - Check disk usage, focusing on /var/log and /storage partitions:
bash df -h du -sh /var/log/* - Use
journalctlor log rotation tools to evaluate log retention settings.
Action step: Document the largest directories and files consuming disk space. In many cases, log files can reach up to 2TB if retention policies are overly generous.
Step 2: Stop VCF Log Management Services Safely
Since there is no uninstall button, stopping services prevents further disk writes during cleanup.
- Use the following commands to stop log management services:
bash sudo systemctl stop logmanagement sudo systemctl stop vrealize-loginsight - Confirm services are stopped:
bash sudo systemctl status logmanagement sudo systemctl status vrealize-loginsight
Do this now: Ensure all log management-related services are stopped before file removal to avoid corruption.
Step 3: Manual Removal of Log Management Files
Since automated uninstall options are unavailable, manually delete or archive log files and related data.
- Navigate to log storage locations:
bash cd /var/log rm -rf li-* cd /storage/logs rm -rf * - Remove old snapshots or backups that consume space.
- If configured, clean up Elasticsearch indices used by vRealize Log Insight:
bash curl -X DELETE "http://localhost:9200/_all"
Practical tip: Archive critical logs to an external storage before deletion if regulatory compliance requires retention.
Step 4: Reset Password for VCF Log Management Access
If you need to regain or reset passwords for VCF Log Management or vRealize Log Insight:
- Access the VCF Operations Manager UI or appliance shell.
- Use the following command to reset passwords:
bash /opt/vmware/bin/vcf-password-reset.sh - Alternatively, use the vRealize Log Insight CLI:
bash li-reset-password - Update credentials in SDDC Manager to reflect the new password.
Do this now: After password reset, verify login functionality via UI and CLI.
Step 5: Adjust Log Retention Policies to Prevent Future Disk Pressure
Before restarting services, configure log retention to reasonable limits.
| Component | Default Retention | Recommended Retention | Reasoning |
|---|---|---|---|
| vRealize Log Insight | 30 days | 7-14 days | Reduces disk usage and speeds up queries |
| Syslog | 90 days | 30 days | Balances audit needs and storage |
- Modify retention settings through vRealize Log Insight UI:
- Navigate to Administration > Retention Settings.
- Set new retention periods.
- For syslogs, edit
/etc/logrotate.confor relevant config files.
Action: Implement retention policies consistent with your organization's compliance and storage capacity.
Step 6: Restart Log Management Services and Monitor Disk Usage
Once cleanup and configuration are complete:
- Restart services:
bash sudo systemctl start logmanagement sudo systemctl start vrealize-loginsight - Monitor disk space over the next 24-48 hours:
bash watch -n 60 df -h
Pro tip: Use vRealize Operations Manager to monitor disk usage trends and alert for future pressure.
Common Mistakes to Avoid
- Deleting logs without backup: Always back up critical logs if needed for compliance.
- Stopping services abruptly: Ensure proper service stop commands to avoid data corruption.
- Ignoring password sync: After password resets, update all dependent systems to prevent authentication failures.
- Neglecting retention policy updates: Removing logs without adjusting retention leads to recurring disk pressure.
FAQ
Q1: Can I fully uninstall VCF Log Management 9.1 via the UI?
A1: No, VCF 9.1 does not provide an uninstall button for log management components; manual removal is necessary.
Q2: How much disk space can I expect to free after cleanup?
A2: Depending on log retention and activity, up to 2TB or more can be reclaimed.
Q3: Will manual deletion affect system stability?
A3: If done carefully and services are stopped first, manual cleanup is safe. Always back up before starting.
**Q4: How do I prevent log storage from filling up again?
A4: Implement and enforce log retention policies and monitor disk usage continuously.
Q5: What tools help with monitoring disk pressure on VCF appliances?
A5: vRealize Operations Manager and native Linux tools like df, du, and iotop are effective.
Conclusion
Managing disk pressure caused by VCF Log Management 9.1 requires a hands-on approach when uninstall options are unavailable. By following the outlined steps - identifying disk usage, safely stopping services, manually removing log files, resetting passwords, adjusting retention policies, and monitoring disk space - you can free up substantial storage, often exceeding 2TB. This proactive maintenance ensures your VCF environment remains performant and avoids unexpected outages due to disk exhaustion.
Final tip: Schedule regular log management reviews as part of your operational runbook to maintain optimal storage health.
Frequently Asked Questions
Can I fully uninstall VCF Log Management 9.1 via the UI?
No, VCF 9.1 does not provide an uninstall button for log management components; manual removal is necessary.
How much disk space can I expect to free after cleanup?
Depending on log retention and activity, up to 2TB or more can be reclaimed.
Will manual deletion affect system stability?
If done carefully and services are stopped first, manual cleanup is safe. Always back up before starting.
How do I prevent log storage from filling up again?
Implement and enforce log retention policies and monitor disk usage continuously.
What tools help with monitoring disk pressure on VCF appliances?
vRealize Operations Manager and native Linux tools like `df`, `du`, and `iotop` are effective.