Skip to content

Author: Luciano Batalha

Object type requires hosted I/O

After power outage the VM will not power-on and throws the following error:

Object type requires hosted I/O

Login to the ESXi host over ssh.
Browse to the VM folder containing the disk files.

Run the following command:

vmkfstools -x check “test.vmdk”
Disk needs repaired

vmkfstools -x repair “test.vmdk”
Disk was successfully repaired.

Start VM

“Scan or remediation is not supported on because of unsupported OS …” for certain operating systems

 

The VMware wrote this  workaround, so you can manually add the operating system to the list for VMware Update Manager.

  1. Connect to your vCenter Server Appliance per SSH and log in
  2. Create a backup of the vci-integrity.xml file:
mkdir /backup && cp /usr/lib/vmware-updatemgr/bin/vci-integrity.xml /backup/
  1. Modify the vci-integrity.xml file by opening the file using vi editor:
vi /usr/lib/vmware-updatemgr/bin/vci-integrity.xml
  1. Locate the <vci_vcIntegrity> ….. </vci_vcIntegrity> section
  2. Enter edit mode by hitting the insert or the letter i button
  3. Before the </vci_vcIntegrity> line, add the following lines, depending on the operating system configured in your virtual machine. If entering both versions of the same OS (ie: Windows 2019 AND 2022), see the below Note section
  • For Debian 11 (32 bit):
    <supportedLinuxGuestIds>
      <debian11Guest/>
    </supportedLinuxGuestIds>
  • For Debian 11 (64 bit):
    <supportedLinuxGuestIds>
      <debian11_64Guest/>
    </supportedLinuxGuestIds>​​​​​​
  • For Red Hat Enterprise Linux 9 (64 bit):
    <supportedLinuxGuestIds>
      <rhel9_64Guest/>  
    </supportedLinuxGuestIds>

Some Linux have same issue, for that follow the list of all supported Linux Guest OS IDs

asianux3Guest
asianux3_64Guest
asianux4Guest
asianux4_64Guest
asianux5_64Guest
centosGuest
centos64Guest
coreos64Guest
debian4Guest
debian4_64Guest
debian5Guest
debian5_64Guest
debian6Guest
debian6_64Guest
debian7Guest
debian7_64Guest
debian8Guest
debian8_64Guest
oracleLinuxGuest
oracleLinux64Guest
rhel7Guest
rhel7_64Guest
rhel6Guest
rhel6_64Guest
rhel5Guest
rhel5_64Guest
rocklinux_64Guest
fedoraGuest
fedora64Guest
sles12Guest
sles12_64Guest
sles11Guest
sles11_64Guest
sles10Guest
sles10_64Guest
opensuseGuest
opensuse64Guest
ubuntuGuest
ubuntu64Guest
otherlinuxguest
otherlinux64guest

EMC DD – Error: Failed to call RPC function ‘DDBoostFcWriteFile’: Failed to open file ‘

To resolved this issue in version 12 follow this procedure:

1) Download the fix https://storage.veeam.com/Fix_550082_e27e09c2c3.zip  and unzip it to a temporary location.
2) When possible, stop the Veeam Installer service
3) Then go to this location: C:\Windows\Veeam\Backup
4) Rename the VeeamDeploymentDll.dll to VeeamDeploymentDll.dll.orig
5) Copy the DLL from this fix you unzipped to the same location (C:\Windows\Veeam\Backup)
6) Repeat steps 4 and 5 for the additional locations below as needed (some paths may not exist on all managed servers, replace in all that do):

C:\Program Files (x86)\Veeam\Backup Transport\GuestInteraction\VSS\Packages

C:\Program Files\Common Files\Veeam\Backup and Replication\Mount Service\Packages

C:\Program Files\Veeam\Backup and Replication\Backup Catalog

C:\Program Files\Veeam\Backup and Replication\Backup\Packages

C:\Program Files\Veeam\Backup and Replication\Enterprise Manager

C:\Program Files\Veeam\Veeam Distribution Service\Packages

7) Start the Veeam Installer Service
8) Retry the backups

 

Round Robin ESXi

Best practices to add in your ESXi if you have this storage.

  • To storage Compelant  – esxcli storage nmp satp rule add -s “VMW_SATP_ALUA” -V “COMPELNT” -P “VMW_PSP_RR” -O “iops=3”
  • To storage PowerMAx – esxcli storage nmp satp rule add -s “VMW_SATP_SYMM” -V “EMC” -M “SYMMETRIX” -P “VMW_PSP_RR” -O “iops=1”
  • To storage Huawei – esxcli storage nmp satp rule add -V HUAWEI -M XSG1 -s VMW_SATP_DEFAULT_AA -P VMW_PSP_RR -c tpgs_off
  • To storage IBM – esxcli storage nmp satp set –default-psp VMW_PSP_RR –satp VMW_SATP_SVC
  • To storage Dell Unity – esxcli storage nmp satp rule add –satp “VMW_SATP_ALUA_CX” –vendor “DGC” –psp “VMW_PSP_RR” –psp-option “iops=1″ –claim-option=”tpgs_on”
  • To storage Huawei  . esxcli storage nmp satp rule add -V HUAWEI -M XSG1 -s VMW_SATP_DEFAULT_AA -P VMW_PSP_RR -O iops=1 -c tpgs_off

The Datastore still appears because there is an active process or an iso mounted/snapshot.

The Datastore still appears because there is an active process or an iso mounted/snapshot.

First select your cluster -> right click -> datastore -> and rescan

Second, go to vCenter select the datastore and check Check which host you didn’t unmount on, also you can go to the VM tab of this datastore and check if you have a VM.

Login to ESXi over ssh and check this outpu

lsof | grep name of datastore

Run this esxcli storage filesystem list find storage UUID and send me this output.

lsof | grep storage uuid

Replace the naa.

Run this command vsish -e ls /storage/scsifw/devices/<“naa. id of your datastore”>/worlds/ |sed ‘s:/::’ |while read i;do ps |grep $i;done

Check the lock file/ process file  to unmount the datastore

 

Veeam – Issue after patch to version 12.0.0.1420_20230718

After installing the patch 12.0.0.1420_20230718 we got this issue when open the console “could not create unique index “backups_tem_id_idx” checking the logs we can found this.

[23.08.2023 10:54:36.982] <21> Error        could not create unique index “backups_temp_id_idx” (Veeam.Backup.Common.CPsqlException)
[23.08.2023 10:54:36.982] <21> Error        [CExceptionHandlingDBAccessorDecorator]
[23.08.2023 10:54:36.982] <21> Error        —————————————————————-
[23.08.2023 10:54:36.982] <21> Error        Stored procedure execution failed:
[23.08.2023 10:54:36.982] <21> Error        —————————————————————-
[23.08.2023 10:56:27.923] <01> Error        Backup service has failed.

This is a known issue and Veeam provide the hotfix. Please download the hotfix from here and follow the next steps: https://storage.veeam.com/Fix_550096_f09100c493.zip

1. Make sure your build version is 12.0.0.1420 P20230718

2. Make sure no Jobs or Restores are running.

3. Run veeam_backup_12.0.0.1420_PrivateFix_TF550096.exe as Admin

Remove vSphere Replication flag from VM

In my case the customer removed the vSphere replication appliance, so I needed removed all vsphere replications.

  1. Login to ESXi
  2. Execute this command to list the VMS
    vim-cmd vmsvc/getallvms | awk ‘$3 ~ /^\[/ {print $1}’
  3. Execute this command to remove the flag (you need replace VM id)
    vim-cmd hbrsvc/vmreplica.disable 1011