Entries Tagged as 'VEEAM'

VEEAM issues after installing KB4015553

Following error can occure:

“An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full”

Please remove KB4015553 from the Windows Updates. (reboot needed)

Cannot mount vPower NFS VEEAM

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.

VMware Backup Pre- And Post-Commands

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:

To create a sample wrapper script,  you can create a text file and name it vcb.bat.
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.

Veeam: How to Move the VBRCatalog Folder

You will need to make changes to the registry to change the VBRCatalog folder location. To do so:

  • Stop the Veeam Services
  • Edit following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup Catalog
Find the string called CatalogPath, right-click it and choose modify

  • Restart the services mentioned above

80080005 Server execution failed

In one instance we encountered following error on a VEEAM backup environment, where all backup’s failed in the same session. also manually restarting the jobs gave this error:

Unable to subscribe to guest processing components: Retrieving the COM class factory for component with CLSID {D2E3C73F-841A-46B0-A93F-956CCABD3B11} failed due to the following error: 80080005 Server execution failed (Exception from HRESULT: 0x80080005 (CO_E_SERVER_EXEC_FAILURE))

After investigation it seemed that intl.dll was missing in the …\Veeam\Backup and Replication\Backup\VSS folder.

Replacing it fixed the problem.