Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

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

Last Updated: 3/16/2021Categories: How toTotal Views: 7967Language:
English

6 like this article

Subscribe to get an email
newsletter with new updates

6 people found this helpful Please provide article feedback:

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.

Purpose

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

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.

Resolution

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

Related Information

Change the Virtual Disk Configuration

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

resizeDisk2.sh

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Aria Automation Orchestrator

Related Versions:

VMware vRealize Orchestrator 7.x

VMware vRealize Orchestrator 7.6.x

VMware vRealize Orchestrator 7.4.x

VMware vRealize Orchestrator 7.3.x

VMware vRealize Orchestrator 7.2.x

VMware vRealize Orchestrator 7.1.x

Take Our Survey

Support Assistant