Avamar VM Backups failing with error "avvcbimage FATAL <42144>: The disk sizes do not match current vm configuration"

           

   Article Number:     499253                                   Article Version: 3     Article Type:    Break Fix 
   

 


Product:

 

Avamar,Avamar Plug-in,Avamar Client for VMware 7.4.100-242

 

Issue:

 

 

Avamar Virtual Machine Image Backups fail with error "avvcbimage FATAL <42144>: The disk sizes do not match current vm configuration"                                                           

 

 

Cause:

 

 

The virtual machine disk size has changed since its previous backup and Avamar is unable to process it due to a change in block IDs.   
   
    This can be confirmed by checking the previous backup size of the virtual machine and its current disk size from vCenter.   
   
    The log shows this change in detail   

2017-04-27 02:24:47 avvcbimage Info <41153>: Using CURL Method2017-04-27 02:24:47 avvcbimage Info <41154>: Re-using vCS Session Cookie2017-04-27 02:24:47 avvcbimage Info <42207>: Download of vss-manifest.zip file: SISCTX2-vss_manifests739.zip, successful2017-04-27 02:24:47 avvcbimage Info <19680>: vmAction runBackupScript: ()2017-04-27 02:24:47 avvcbimage Info <19681>: vmAction runBackupScript: script is skipped because it is null2017-04-27 02:24:47 avvcbimage Info <0000>: [IMG0009] Post-snapshot script:  completed successfully2017-04-27 02:24:47 avvcbimage Info <42142>: A snapshot was created, VM is powered On.2017-04-27 02:24:47 avvcbimage Info <19721>: SetDiskValues from Device Key: '2000'.2017-04-27 02:24:47 avvcbimage Warning <14662>: The VM '[VMDisk02] SISCTX2/SISCTX2.vmx', disk 2000, size changed.2017-04-27 02:24:47 avvcbimage Info <19718>: Found Disk from Device Key: '2000'.2017-04-27 02:24:47 avvcbimage Info <18646>: New method from Snapshot/config: Using '[VMDisk02] SISCTX2/SISCTX2-000002.vmdk'.2017-04-27 02:24:47 avvcbimage Info <14661>: Disk Info:  Current Disk '2000': file(base):'[VMDisk02] SISCTX2/SISCTX2.vmdk', backItUp=1               snapshot(base) file:'[VMDisk02] SISCTX2/SISCTX2-000002.vmdk'               snapshot(curr) file:'[VMDisk02] SISCTX2/SISCTX2-000001.vmdk'               prior size(KB):41943040, current size(KB):52428800, match=0               prior change block ID:  '52 84 43 88 17 c0 66 1c-ba 67 ca 20 2f ab c3 de/8498'               current change block ID:'52 84 43 88 17 c0 66 1c-ba 67 ca 20 2f ab c3 de/8669'               CBTenabled=1, thin=0, independent=0, SCSI=1, diskMode=persistent, backing=DiskFlatVer22017-04-27 02:24:47 avvcbimage FATAL <42144>: The disk sizes do not match current vm configuration for [VMDisk02] SISCTX2/SISCTX2.vmx.  Make sure that VM configuration changes are not made during the backup window.2017-04-27 02:24:47 avvcbimage Info <9772>: Starting graceful (staged) termination, WO Disk sizes do not match current VM configuration (wrap-up stage)2017-04-27 02:24:47 avvcbimage Error <0000>: [IMG0009] Create Snapshot: snapshot creation or pre/post snapshot script failed.2017-04-27 02:24:47 avvcbimage Error <0000>: [IMG0009] Create Snapshot: snapshot creation/pre-script/post-script failed.    
   
                                                                

 

 

Resolution:

 

 

Note that it takes some time for Avamar and vCenter to synchronise.   
   
    1. Check the Virtual Machine disk size by running the following command from the Avamar utility node.   
    mccli vmcache show --name=<Avamar client path for the VM>    
   
    2. Re-sync Avamar with VCenter and test backup.   
   
    Monitor the next scheduled backup.