Skip to main content
  • EN

I was updating my Lab, and came to this little issue I would like to share with y’all.

I was applying the patch for KB4696 to ensure my 12.3 was fully patched, but then I noticed my free space on the C drive was insufficient.
First thought: easy… let's enlarge the drive (it's virtual), increase it, and continue…
The recovery partition didn't allow me to do so.

Find below the screenshot of the patch installation + steps for being able to extend your drive in case you also need to.

 

 

 

 

 

 

First error, close your VBR Console before continuing… (Palmface)

 

 

 

 

 

 

 

 

Oh boy, here is… 

 

Let's fix this issue to be able to deploy the patch, 
As you can imagine, we will shut down the VM, reboot, and then relaunch the install and continue.

!-->

Here's a breakdown of the methods:
Using Disk Management and Diskpart (Requires disabling and potentially deleting the recovery partition):
Disable the Recovery Partition:
Open an elevated command prompt and run reagentc /disable. This moves the recovery partition's functionality into a file (Winre.wim). 
Delete the Recovery Partition:
Use diskpart to select the disk, list partitions, select the recovery partition, and then delete it with delete partition override.
Extend the C Drive:
In Disk Management, right-click the C drive and select "Extend Volume". Follow the wizard to merge the now-unallocated space. 
Recreate the Recovery Partition:
If you want the recovery partition back, you'll need to create a new partition, format it, and then re-enable WinRE using reagentc /enable. 

 

Now, let's continue with our patching…
I reboot the VM and restart the process. Here are the following steps.

 

 

 

 

 

Done!

 

Now let's update components

 

 

 

ready!

 

 

https://lfconsulting.org/lab-patch-vbr-12-3-kb4696

I hope you find this info useful.
Cheers.

 

This was a common issue during our patching as well so nice with virtual to expand. 😎

Don't forgot to take a configuration backup before this, and store it somewhere on a separate server. In addition, before making any changes to partitions I'd recommend taking a snapshot of the vm first. 

Don't forgot to take a configuration backup before this, and store it somewhere on a separate server. In addition, before making any changes to partitions I'd recommend taking a snapshot of the vm first. 

Totally agree!

Confog backups and snapshots are a must in prod! I cannot imagine my life without them anymore!

This was a lab config, no biggie into deleting and re building.

Cheers.
 

Don't forgot to take a configuration backup before this, and store it somewhere on a separate server. In addition, before making any changes to partitions I'd recommend taking a snapshot of the vm first. 

 

Great suggestion. I always give this top priority. 

I generally delete the recovery partition when I run into this issue.  Another alternative is to download the installer/update package to a different drive as when I attempt to update via the Service Provider Console, the installer is placed in a folder within the Veeam Availability Console folder, but also, with more of the analysis of backups with malware, etc, I’ve found that the log files are growing rapidly and in one case (a physical VBR server), I relocated the logs to the repository drive as noted in KB 1285.

https://www.veeam.com/kb1825

 

Comment


Terms & Conditions