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

Enlarging vSphere Replication appliance disk and creating a partition needed for Java heap dumps after upgrade (67739)

Last Updated: 5/10/2021Categories: Best PracticesTotal Views: 6233Language:
Chinese (Simplified)English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Details

This article outlines the steps needed to create additional partitions for the Java heap dump after an in-place upgrade of the vSphere Replication appliance to 8.2. The partition is automatically created for vSphere Replication appliance 8.2 and above but is not in case of upgrades.

Note:

This is an optional setup required only if you would want to provide the Java heap dump for investigation in case of major VR service failure.

The Java heap dumps may contain sensitive data that are not usually required for investigation any issues with the product.

Solution

 To manually create the heap dump partition, use the following steps:

Edit HMS VM settings (it can be done while the VM is running) - enlarge second disk with 4GB from 13 to 17 GB.

Open HMS VM and make sure that /dev/sdb partition is enlarged. This could not happen immediately but could take up to several minutes for the OS to detect the changes. To do so you can use /fdisk -l and look for /dev/sdb - the size should be the new one (17GB). If it is not just wait a bit and re-run the command until you see the new size.

Once the OS has detected the physical disk size change and enlarges the partition (verified at step 3) we have to enlarge the physical volume using the command:

pvresize /dev/sdb

Verify new physical volume size using the command:

pvs

You should see the new size in PSize and PFree should be the size of the extention space which is currently free on the physical volume.

Verify the volume group support_vg is also enlarged along with the underlying physical volume with the command:

vgs

You should see the new size in VSize and VFre should be the size of the extention space which is currently free on the volume group.

If this is not the case try re-scanning the physical volume and volume groups by running the following commands:

pvscan

vgscan

Then run the vgs command again to verify the size of support_vg volume group as explained above.

Create a new logical volume named heapdump with size 4GB:

lvcreate -L 4G -n heapdump support_vg

Verify that logical volume is created using the following command:

lvscan

Verify heapdump volume is ACTIVE and verify its size. More info about the new logical volume can be seen. If  you run the command:

lvdisplay

Format the newly created logical volume:

mkfs.ext3 /dev/support_vg/heapdump

Mount the newly created logical volume to the heapdump directory:

sudo mount /dev/support_vg/heapdump /opt/vmware/heapdump

Update fstab file so that mounting the new partition will be done automatically after reboot:

Backup file use the command:
cp /etc/fstab /etc/fstab.old

Add the following line at the end in /etc/fstab:
/dev/support_vg/heapdump /opt/vmware/heapdump ext3 rw,nosuid,nodev,exec,auto,nouser,async 0 1

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)English

Attachments

Additional Resources

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

KB
•
升级到 vSphere 7.0 时安全策略预检查失败 (67853)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere Replication

VMware vSphere

Related Versions:

VMware vSphere Replication 8.x

Take Our Survey

Support Assistant