Removing data from backup that shouldn't be there

[jcpro]

I have a full system backup scheduled every day, I accidentally left an external USB drive plugged in and it proceeded to backup the drive subsequently eating up most of the space on the backup destination.
How do I remove specific data? Is it as simple as deleting the .vib file that contains the data? Will this corrupt the 'chain' in any way?

[Dima P.]

Hi jcpro,
Deleting incremental backup file makes all the subsequent increments non-operational. That being said you can delete an incremental restore point in the middle of the chain and then you have to delete all the subsequent increments too. Last but not the least, it is safe to delete the latest incremental backup in the chain.

[jcpro]

I removed the last file in the backup freeing up quite a bit of space and let it perform it's next regularly scheduled backup, however, it's attempting to do a full complete backup and the backup destination is running out of space again. How can I prevent this behavior and let it just do incrementals like....it's supposed to do.

[Dima P.]

You removed only the latest .vib right?

it's attempting to do a full complete backup and the backup destination is running out of space again

Any chance, you've changed the backup source or backup destination?

[jcpro]

I removed the latest .vib but it keeps trying to create a .vbk
Backup destination is the same, backup source is as it should be sans the eSata drive I had plugged in that caused this problem to begin with.
You can see in the image below it's re-creating the .vbk every time the scheduled backup job runs now but it fails because I don't have enough storage space for another full backup.

[Dima P.]

jcpro,
Thanks. Since that does not look like expected behavior could you please open a support case thru the Endpoint’s Control Panel > Support > Technical Support and let the support team check debug logs.

[jcpro]

What information is included in the support logs that are transmitted?

[Gostev]

All debugs logs that VEB generates.

[Dima P.]

Hello jcpro,

It seems we found a misbehavior in the logic thanks to your case: VEB compares the existing chain with the metadata file and if any restore points are missing (even the latest incremental file) it makes a new full to avoid possible data corruption.

This behavior is unexpected and we will try to fix it in the upcoming releases. Meanwhile, I am sorry for sharing misleading information.

[jcpro]

Thanks for the reply on this, good to know the devs are aware.

[jcpro]

This problem does not appear to have been resolved. I once again accidentally left an eSATA drive plugged in and Veeam Endpoint Backup tried to incorporate it into the nightly backup.
Deleting the newly created .VBK file and subsequent re-running of the backup job results in an entirely new .VBK being created. This is extremely frustrating because this essentially nullifies all previously created backups and forcing the creating of an entirely new backup chain!

[Dima P.]

Indeed, eSATA devices are treated as an internal drives. VEB tried to backup the said drive because you are running Entire PC backup mode, right?

[jcpro]

That is correct.

[Dima P.]

Thanks! To ensure this won’t happen again switch to volume level backup and select only particular volumes as a source.