Remove selected restore points from backup copy jobs

[emak]

Hi

We are using Veeam B&R 9.5 Update 2. One of our tasks is to make a backup copy to a cloud provider. As there are sensitive data in it, the backup is encrypted. With this setup we have to pay for the amount of used space (quite logical and fully ok).

Situation
We have a server with a big amount of data we would like to backup additionally to the cloud for a certain period (30days). In order to keep the used space to a minimum we chose forever incremental backup without active full backup with 30 restore points and a monthly full backup for archival purposes. As previously mentioned is the backup file encrypted.

When the copy job fails it was normally best to run an "Active Full" backup and I was expecting to take it a bit more space until the oldest full backup expired.

Problem

Our problem is that the backup shows 31 restore points in the cloud when we actually have 34. The "missing" three restore points are all expired (27.03.18, 21.02.18 and 28.05.17). Unfortunately selected restore points from the cloud can't be removed. When discussing it with Veeam support (Case #02618820) there seems really not to be a way in order to cleanup backup copy jobs (even not with the latest B&R update).

We went on with our cloud provider and he removed the files physically on the storage but they still show up in our Veeam B&R and still use the space. In order to clean that we were asked to deliver our encryption password by Veeam support which I can't and won't do...

What happened is that the used space somehow is not released and the cloud provider decided himself to give us a higher quota in order to ensure the backups were running. So now we are paying for storage we do not need and if I want to clean it up it has to do with fiddling with databases and modify the VBM file. This can't seriously be the solution in 2018...

Request
Give the customer a possibility to remove selected restore points from backup copy jobs in the cloud or another valid solution in order to cleanup the space.

[Iain_Green]

I am surprised that by removing the points and performing a re scan on the cloud repository the space did not clear??

[emak]

After having talked with a different service engineer from our cloud provider it turned out that only 1/3 files were effectively deleted. After successful removal of the remaining files and a rescan, followed by a run of the backup-copy job the space is now freed but the problem persists and the missing files have to be manually updated in the *.vbm file in order to not show up longer on our side.