12-07-2012 01:00 AM
Hi - Did you change some of the default retention settings? i have run vPV for more than 6 days and never run into this problem, with default settings. how many instances are you managing?
you can run standard checks on the VA to see if there are some really large unused files on the VA if in case you have downloaded or ftp-ed some files into the VA.
OPTIONALLY - ADD more DISKS.
add another disk of say 30 gb size or more, format it as a linux filesystem.
then use sym-links to point /var/opt/OV/databases/pv to the new partition
copy over old db files to new location and then restart pv.
remember to add the new disk to mounts so that the disk is mounted automatically on reboot.
Good news is all this can be done without doing a reboot.
I recommend you log an enhancement on vPV to partition the disk as volumes, using LVM so that it is possible to extend volumes easily.
12-07-2012 02:16 AM
I redeployed the appliance but before that I increased partition to 100GB.
I did not change retention policies. I managed 6 vcenter (3000+ VMs).
I would prefer to use LVM in future if possible. Also would be nice to have some easy way to add diskspace to be used by DB.
What user and password should I use to access console of appliance?
12-07-2012 02:20 AM
Kalle, the root password is mentioned in the release notes. the default password for root user is vperf*viewer.
Please change this to a password of your choice.