Pre-requisites
- Shutdown vRealize Orchestrator and remove all snapshots.
Note: Snapshots and snapshot chains will prevent base disk modifications.
- 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.
- 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
- Power on the vRealize Orchestrator appliance host virtual machine.
- Upload the resizeDisk2.sh script to /tmp
- Log in with secure shell connection as the root user.
- Run the /tmp/resizeDisk2.sh script
Note: The script will generate resize.log file in the current directory - Run df -h /dev/sdb* command to verify the partitions were successfully resized.
- Verify that you can login to the vRealize Orchestrator
- 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.
- Verify that you see recent log entries in /storage/db/pgdata/serverlog