Other Blogs

Author: Stefan van Bruggen

Veeam does not have a built-in function to remove restore points manually, it took me a while but after trying a lot of different ways and scripts I have found a way to do it. (Please note that this is a last resort, Veeam should clean-up old restore points by itself)

Go to Backup & Replication -> Backups.

Right-click the job you want to edit and click ‘Remove from configuration’ (Do not delete from disk!).

Open the Windows Explorer and browse to the job’s folder in the backup repository.

Delete the restore points you want to remove, and delete the .VBM file.

Re-import the most recent .VBK file in the Veeam.

Run the following script using the Veeam Powershell to generate a new .VBM file:

So, let’s take a break from all the Powershell creativity and take a look at everybody’s favourite thing in IT: Backups! Failed backups!

(The screenshots are unclear and censored to protect customer information)

The problem here is that Veeam’s replication jobs started failing, stating that an ‘Invalid Snapshot Configuration’ was the problem. Sounds easy, right?
Well, it turns out that this can cause a lot of work to get this fixed, so to save you some time I documented the solution for you.

First I tried consolidation the snapshots, but it greeted me with the following error:

A CID mismatch.. not on my watch! Let’s check this out and start an SSH connection to the ESX-host where these VMs are placed and run some checks:

So, for some reason the snapshots have registered themselves as the parent CID instead of the actual base disk:

We can fix this! Open the .vmdk-files using VIM and simply edit the parent CID to the CID of the base disk.

Customer X had a long ongoing problem with userprofiles getting corrupted due to their antivirus solution holding the ntuser.dat file hostage. It took a while before we found the cause of this problem so we had to think of a quick fix to keep things running.
Another problem was that the locally stored corrupted profile was getting synced to the profile server, causing trouble for users on multiple workstations.

To save time and to give the sysadmins an easy way to clean these corrupted profiles, I automated the process with this (admittedly messy) script.

I’ve also added some workarounds that start the required services used in this script, because in some cases these are not enabled (WinRM, Remote Registry, etc.)

Sadly, the WSUS cleanup wizard neglects to clean up updates that were approved in the past but have been superseded since.

Because these updates tend to use a lot of diskspace, I use a short Powershell script that checks all updates for superseded updates and declines them. After this, the WSUS cleanup wizard can be run again to clear up diskspace.

Posts navigation

This website uses cookies to track the amount of visitors. This website does not store any personal details, I just want to know which posts are the most popular :) If you continue to use this site I will assume that you accept these cookies (or use a browser plugin like Privacy Badger).Ok