Go to Virtual Machine > Install VMware Tools (or VM > Install VMware Tools).
sudo mkdir /mnt/cdrom sudo mount /dev/cdrom /mnt/cdrom or sudo mount /dev/sr0 /mnt/cdrom tar xzvf /mnt/cdrom/VMwareTools-x.x.x-xxxx.tar.gz -C /tmp/ cd /tmp/vmware-tools-distrib/ sudo ./vmware-install.pl -d sudo reboot
While opening a console for any virtual machine from one particular workstation, the console display is not sized correctly.
To resolve this, you will have to disable Display Scaling.
The console session should populate the full screen.
Today I encountered the issue that I could not run a SureBackup from an ESX server. Although the ESX server (vmkernel) could ping the Veeam Backup server and coudl connect tot the NFS service (Port 111 and 6161).
I finally saw that there was also a Service NFS running. Disabling this service did not help.
At last i just removed the “Service fro NFS” from the Windows 2012 R2 Storage server.
A reboot is needed AND…. the Surebackup run.
So. If you have a Windows Storage server and you install Veeam Backup and Replication on it. Remove the Service for NFS from it to make vPower NFS work.
| Version of ESX | Custom quiescing script directory |
| ESX/ESXi 3.5 Update 1 or earlier |
C:\Windows\<pre-freeze-script.bat>
C:\Windows\<post-thaw-script.bat> |
| ESX/ESXi 3.5 Update 2 or later |
C:\Program Files\VMware\VMware Tools\backupScripts.d\
|
| ESX/ESXi 4.x | C:\Windows\backupScripts.d\ |
| ESXi 5.0 |
C:\Windows\
C:\Program Files\VMware\VMware Tools\backupScripts.d\
|
| ESXi 5.1 and ESXi 5.5 |
C:\Windows\<pre-freeze-script.bat>
C:\Windows\<post-thaw-script.bat> |
Windows:
echo off if "%1" == "freeze" goto doFreeze goto doThaw :doFreeze call c:\windows\pre-freeze-script.bat goto EOF :doThaw call c:\windows\post-thaw-script.bat :EOF
Linux:
For Linux VMs, the scripts should be named
    /usr/sbin/pre-freeze-script     /usr/sbin/post-thaw-script
Both must have 0755 permissions so that they are executable, and should be owned by root.
Veeam:
Make sure that “âEnable VMware Tools quiescence” is enabled, cauusing the scripts to be call to.
I love CLI (Command Line Interface).
It gives you control…
So therefore if I work with ESX and snapshotting:
# vim-cmd vmsvc/getallvms
To get all VM’s andthier ID’s
#Â vim-cmd vmsvc/snapshot.create [ID] [Name]
To create a snapshot
#Â vim-cmd vmsvc/get.snapshotinfo [ID]
To get full information on snapshots on the VM
#Â vim-cmd vmsvc/snapshot.revert [ID]
To revert to a snapshot
#Â vim-cmd vmsvc/snapshot.remove [ID]
To remove a snapshot
# vim-cmd vmsvc/snapshot.removeall [ID]
To remove all snapshots from the VM
Upload the HPPP_x.xx.xx_Linux_X64.rpm to the vMA (/tmp) (with winSCP of FASTscp)
> sudo -s
> rpm -i hppp-linux-1.02.028-1.x86_64.rpm
Starting Power Protector: HP-HPPP[ OK ]
Check if the service is indeed listening on it’s ports:
> netstat -tanp | grep LISTEN
tcp 0 0 0.0.0.0:4679 0.0.0.0:* LISTEN 7813/HP-HPPP
tcp 0 0 0.0.0.0:4680 0.0.0.0:* LISTEN 7813/HP-HPPP
tcp 0 0 :::22 :::* LISTEN 2082/sshd
Default the vMA does not have ports 4679 (http) en 4680 (https) open
Configure communication between HPPP and the HP Network Module:
> sudo -s
>Â iptables -I OUTPUT -p tcp –dport 80 -j ACCEPT
>Â iptables -I INPUT -p tcp –dport 4679 -j ACCEPT
>Â iptables -I INPUT -p tcp –dport 4680 -j ACCEPT
>Â iptables -I INPUT -p udp –dport 4679 -j ACCEPT
>Â iptables -I INPUT -p udp –dport 4680 -j ACCEPT
>Â iptables -I OUTPUT -p udp –dport 4679 -j ACCEPT
>Â iptables -I OUTPUT -p udp –dport 4680 -j ACCEPT
>Â service iptables save
>Â iptables-save
Now you can connect with a web-browser.
Also the commi=unication between the vMA HPPP and the UPS is restored.
If the issue persists, end any vmware-vmrc.exe processes in the Windows Task Manager:
Below document ID:Â c03571575
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03571575&lang=en&cc=us&taskId=101&prodSeriesId=3664763&prodTypeId=12169
A critical issue has been discovered to potentially occur on HP Enterprise Virtual Array (EVA) 4400/6400/8400 and HP EVA P63x0/65×0 systems running controller software version XCS 11001000. The potential for this issue is only on systems running software version XCS 11001000 and that are using VAAI functionality enabled on VMware ESX 4.1/ESX 5.x hosts.
To ensure current and future systems will function as expected with VAAI enabled, XCS controller software version 11001000 is being retired and will be listed as Inactive in the HP controller software support matrix. Contact your HP Services representative for more information on the issue and to schedule an upgrade to the latest controller software that resolves this issue.
This issue affects HP EVA4400/6400/8400 and HP EVA P63x0/P65x0 arrays that are running XCS 11001000.
Contact your HP Services representative for more information on the issue and to schedule an upgrade to XCS version 11001100. The VAAI functionality must be immediately disabled until the controller software is upgraded to 11001100.
WORKAROUND
Disable VAAI functionality on all VMware hosts that access the HP EVA array until the controller software has been upgraded to XCS 11001100.
UPDATE 16-11-2012:
The XCS code be found -> https://h20392.www2.hp.com/portal/swdepot/displayProductsList.do?category=NAS
HP Enterprise Virtual Array (EVA) family with VMware vSphere 4.0, 4.1 and 5.0Â Best practices
[Download]
Running VMware vSphere 4 on HP LeftHand P4000 SAN Solutions
[Download]
Best Practices for deploying VMware and vSphere 4 with VMware High Availability and
Fault Tolerance on HP P4500 Multi-Site SAN cluster
[Download]
HP P4000 LeftHand Solutions with VMware vSphere Best Practices (incl. vSphere 5)
[Download]
3PAR Utility Storage with VMware vSphere
[Download]
HP P2000 Software Plug-in for VMware VAAI
[Download]
HP 3PAR Storage and VMware vSphere 5 best practices
[Download]
Alle LUN’s standaard op Round-Robin zetten:
esxcli storage nmp satp set --default-psp VMW_PSP_RR --satp VMW_SATP_ALUA
Op alle LUN’s welke op Round-Robin staan de IOP’s op 1 zetten:
for i in `esxcli storage nmp device list | grep naa.600` ;Â do esxcli storage nmp psp roundrobin deviceconfig set -t iops -I 1 -d $i; done