Extend a vRealize Orchestrator 7.x appliance's Disk 2 partition in case of insufficient free space
search cancel

Extend a vRealize Orchestrator 7.x appliance's Disk 2 partition in case of insufficient free space

book

Article ID: 344602

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

This procedure increases the free space on Disk 2 logs and database partitions of the vRealize Orchestrator appliance host.

Symptoms:
  • vRealize Orchestrator service will experience issues if there is unavailable free space on Disk 2 /storage/log or /storage/db partitions.
  • You can not free space by removing old or no longer needed files on these partitions.


Environment

VMware vRealize Orchestrator 7.4.x
VMware vRealize Orchestrator 7.1.x
VMware vRealize Orchestrator 7.2.x
VMware vRealize Orchestrator 7.x
VMware vRealize Orchestrator 7.6.x
VMware vRealize Orchestrator 7.3.x

Resolution

Pre-requisites

  1. Shutdown vRealize Orchestrator and remove all snapshots.
Note:  Snapshots and snapshot chains will prevent base disk modifications.
  1. If no other backup solutions provide a full VMDK backup in your environment, then a full clone is recommended.  See the Impacts / Risks section above regarding backups.
  2. Increase Disk 2 with a minimum of 25% (10GB > 12.5GB) or higher by right-clicking the virtual machine in the inventory and selecting Edit Settings.

Procedure

  1. Power on the vRealize Orchestrator appliance host virtual machine.
  2. Upload the resizeDisk2.sh script to /tmp
  3. Log in with secure shell connection as the root user.
  4. Run the /tmp/resizeDisk2.sh script
    Note: The script will generate resize.log file in the current directory
  5. Run df -h /dev/sdb* command to verify the partitions were successfully resized.
  6. Verify that you can login to the vRealize Orchestrator
  7. Verify that you see recent log entries in /var/log/vco/app-server/server.log
Note: It is possible two service restarts occur post execution of the above steps.  The second reboot is imposed by the change of the database fingerprint which is picked up by Control Center's monitoring services.
  1. Verify that you see recent log entries in /storage/db/pgdata/serverlog


Additional Information

Change the Virtual Disk Configuration

Impact/Risks:
  • Before you perform this procedure, you must backup the vRealize Orchestrator appliance.
  • In case of issues, collect the resize.log file and restore the vRealize Orchestrator appliance to the backup state before applying the changes.
    • Contact VMware support and provide the resize.log file.


Attachments

resizeDisk2.sh get_app