Syed Jahanzaib Personal Blog to Share Knowledge !

July 26, 2022

Veeam B&R: Virtual disk size is not a multiple of 1KB

Filed under: Veeam B&R — Tags: , — Syed Jahanzaib / Pinochio~:) @ 11:45 AM

Veeam 1KB Disk Error Solved

We are using Veeam B&R ver 9.x application to backup some esxi guests. From past few days we were getting error at one guest (Windows 2008 R2, converted from P2V (using vmware converter) & it’s backup worked well with veeam for long without issue, but after increasing its disk space, it was giving trouble with following errors.

7/18/2022 5:11:33 PM :: Error: Virtual disk size is not a multiple of 1KB.

I tried the veeam knowledge base mentioned here, changed disk size and recalculated, but still getting errors.

This VM have 2 drives assigned, 1st contains OS (C: drive), 2nd drive (G: Drive) contains Oracle DB DATA. To further narrow down the troubleshooting, I included only drive 1 (OS) in the Veeam backup job, and it worked fine. So it was confirmed that the culprit was drive 2 & it was important drive because it contains oracle database folders (ORACLE & USR).


I tried all solutions but couldn’t figured out. As a last resort I did following. I know this workaround is not the proper solution, but since I failed to sort it using my limited knowledge & get the VM backup was crucial, therefore I did following & it worked for me. Luckily I had enough resources to cater the workaround. 6 drivers SSD in Raid-5 made the transition really fast at about 6-7 Gbps.


  • I Stopped all running services on the VM guest related to Oracle/SAP or any un-necessary apps
  • Added new disk (drive3 / H: ) on the effected VM with same size as existing DB drive (disk2 G: )
  • Cloned the partition from old (disk2 G: ) to this new (disk3 H: ) [I used 3rd party DiskGeniusPro tool for cloning by locking partition access, but u can use Robocopy or other tools as well)
  • Using Disk Management, I changed the drive letter & marked the old (disk2 G: ) OFFLINE.
  • Changed the new disk (disk3 H: ) partition drive letter same as older one that is  G:
  • Rebooted the server, & this time all backups went smoothly & SAP ORACLE synching/services are working fine as well
  • Afterwards I removed the OLD faulty partition from the VM.


Another workaround I got from a virtualization expert member at spicework community support named  Supaplex was to

A slightly simpler option would be using a P2V approach inside the virtual machine using a free tool like V2V Converter and specifying your faulty G: disk as source and ESXi as the target. The tool would convert the disk into a fresh new VMDK file automatically, and all you would have to do is just attach it to the virtual machine and remove the old one. Hope that may save you some time in the future if you encounter such a problem again.

Thank you

Syed Jahanzaib

October 26, 2021

Veeam B&R: [nbd] Error: Object reference not set to an instance of an object.

Filed under: Veeam B&R — Tags: — Syed Jahanzaib / Pinochio~:) @ 10:45 AM


  • Veeam B&R 9.5 (Ver installed on Windows Server 2012R2

We were getting failure error on Veeam daily job report for a particular VM guest ,

Preparing backup proxy VMware Backup Proxy for disk Hard disk 1 [nbd]
Error: Object reference not set to an instance of an object.

It was a VM guest that was recently restored via vcenter to another esxi host (under vcsa).

To further troubleshoot, I exported the JOB log using Veeam article, & observed following

[23.10.2021 04:56:01] < 332> cli| Waiting for the next command.
[23.10.2021 04:56:01] < 3936> cli| Next client command: [closeStg].
[23.10.2021 04:56:01] < 3936> cli| :> X:\VMBKP\Daily VM BKP job via VCSA\MY_VM_GUEST.16D2021-10-23T030322.vbk
[23.10.2021 04:56:01] < 3936> cli| Closing storage ‘X:\VMBKP\Daily VM BKP job via VCSA\MY_VM_GUEST.16D2021-10-23T030322.vbk’.
[23.10.2021 04:56:01] < 3936> cli| MTA backup apartment was created successfully, id ‘0x000001EA804A1E10’.
[23.10.2021 04:56:01] < 3048> cli| Thread started. Thread id: 3048, parent id: 3936, role: MTA invoke thread
[23.10.2021 04:56:01] < 3048> cli| Entering MTA invoke thread.
[23.10.2021 04:56:01] < 3048> stg| There is no file ‘HostFS://X:\VMBKP\Daily VM BKP job via VCSA\MY_VM_GUEST.16D2021-10-23T030322.vbk’ in the files cache.
[23.10.2021 04:56:01] < 3936> stg| There is no file ‘HostFS://X:\VMBKP\Daily VM BKP job via VCSA\MY_VM_GUEST.16D2021-10-23T030322.vbk’ in the files cache.
[23.10.2021 04:56:01] < 3936> cli| Storage is closed.

To sort the issue I did following & the issue got resolved

  • Remove the VM from the VEEAM job
  • Remove the VM from inventory from particular ESXI host,
  • Re-added the VM in ESXI
  • Added the VM in VEEAM job

Afterwards, the job ran fine without any error.


Veeam B&R: Win32 Error / Code: 67 Cannot connect to the host’s administrative share

Continued post from


  • Veeam B&R 9.5 (Ver installed on Windows Server 2012R2


After running the daily job, we were observing following failure notice for particular windows 7/10 OS.

Processing WIN10-LOG Error: Failed to connect to guest agent. Errors: ‘Cannot connect to the host’s administrative share. Host: [WIN10-LOG]. Account: [admin]. Win32 error:The network name cannot be found. Code: 67 Cannot connect to the host’s administrative share. Host: []. Account: [admin]. Win32 error:The specified network name is no longer available.

After some R&D , I had to create a new DWORD value in registry at effected windows , & afterwards the issue got resolved.

Edit the registry on effected Windows & perform following

  1. Click Start, click Run, type regedit, and then press ENTER.
  2. Locate and then click the following registry subkey:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
  3. If the LocalAccountTokenFilterPolicy registry entry doesn’t exist, follow these steps:
    1. On the Edit menu, point to New, and then select DWORD Value.
    2. Type LocalAccountTokenFilterPolicy, and then press ENTER.
  4. Right-click LocalAccountTokenFilterPolicy and then select Modify.
  5. In the Value data box, type 1, and then select OK.
  6. Exit Registry Editor.

On a safe side , perform following as well,

  • Disable windows based firewall
  • Disable windows UAC

Reboot the affected windows machine & now RUN the backup job on Veeam B&R server.

Exporting VEEAM job LOGS for troubleshooting purposes

It’s a good idea to export JOB logs in order to troubleshoot the error in depth.

Follow below veeam article

Syed Jahanzaib

April 6, 2018

Veeam B&R 9.5 Update 3 Error: This Veeam Backup & Replication installation can not be updated automatically

Filed under: Microsoft Related, Veeam B&R — Tags: — Syed Jahanzaib / Pinochio~:) @ 2:32 PM

Recently when we tried to apply veeam B&R update 3 , we encountered following error …

This Veeam Backup & Replication installation can not be updated automatically. Please contact Veeam customer support for assistance with manual update.

vbr95up3 error.JPG

After some investigation it found that it can occur dueto either you are running trial or if you have problem with the license files. Therefore as a workaround to enforce Update Pack 3 which was required dueto requirement of addition of Esxi 6.5 Vcenter, I followed below steps …

Rename following files

VeeamLicense.dll > to > VeeamLicense.dll.old
[ available in C:\Program Files\Common Files\Veeam\ ]

veComLic.dll > to > veComLic.dll.old
[ available in C:\Program Files\Common Files\Veeam\Backup And Replication ]

Now run the Update Pack 3 and it will run smoothly.


Once Done, execute Veeam , It may show license is invalid, just ignore and move forward, it may ask you to update component, just do it, when done, close the veeam.

Now go back to

  • C:\Program Files\Common Files\Veeam
  • C:\Program Files\Common Files\Veeam\Backup And Replication

You may see new VeeamLicense.dll veComLic.dll files, just remove them, (or rename them and rename the previous .old VeeamLicense.dll.old & veComLic.dll.old files to original names. (by removing .old from there names)

Now start Veeam again, & hopefully this time all will be fine.


v br 95 up3 final.JPG

Veeam Installation setup Stuck during .Netframework installation in Windows 7 64bit SP1

During Setup launching if it ask to install .net framework and then stuck on its installation phase, close the setup task from task manager, and then disconnect any USB you may have attached to this system, and then re-run the setup and it will work Insha Allah.

SQL installation fail error during Veeam post-run setup

If you are running windows 7 sp1 64bit, and the setup failed sql installation, then downlaod sql express 2012 edition from microsoft , install it and then run the setup or re-run / install.


I heard that if you have veeam 9.5 crack which consists of 2 files, first stop all veeam services, then run the .reg file , then copy veComLic.dll to C:\Program Files\Common Files\Veeam\Backup And Replication. and start veeam services or restart pc.


April 29, 2013

%d bloggers like this: