Reverse Incremental trying Full backup

[fquinnAPT]

Hi Guys,

I had this issue open under case 01374028

We have a reverse incremental job that was set to do a full BU on the 1st Monday of each month (for example)
When this Monday arrives there is limited space available on the repository to get a full job in and the BU fails
The next night it continues to try a full BU....even when you disable the option

Now in a situation where we cannot get this job completed ...

Support have said the only option here is to run a Full BU....They tried using a tool to fix this but were unsuccessful.

Surely this has raised its head previously ?

[PTide]

Hi,

Have you tried deleting the trailing .vrbs and then rescanning repository? That should work if the total size of .vrbs that you delete is equal or larger than full backup size. Another option would be to temprarily relocate your chain to some other storage or, if your license allows, add your current repo to scale-out repository.

[fquinnAPT]

I do not see a trailing .vrbs ..where would i see this?

What i have is a vbk file for the incomplete job

[PTide]

I do not see a trailing .vrbs ..where would i see this?

Typically reverse incremental chain consists of .vbk and a chain of .vrb files. You say that you have only 1 .vbk in your repository - is that .vbk valid?

[fquinnAPT]

I have 2 .vbk files and all of my .vrb files

One VBK is the original in tact VBK

The second is the one that keeps getting created when a new job is started ...as i have said it keeps try to create a full due to the option being set on the job in the first place ....I only want an incremental job not another full VBK

[veremin]

As far as I'm aware, support team can assist you with editing .vbm file, so that, it has no reference to incomplete full backup. Once the correction is done, you can proceed with deleting the incomplete .vbk file. Thanks.

[fquinnAPT]

Ya Like I say ...Support case was open and this was attemped but it did not work...I was asked to complete a full BU...I guess I should re open and have this escalated?

if you have a VM over 1TB in size it poses a big issue

[veremin]

Yep, you can escalate the case and see whether an engineer of the higher tier would be more successful.

In future it might be worth making sure that there is space for at least two .vbk files on your primary repository, especially, if you enable periodic full backup.

Thanks.

[fquinnAPT]

Agreed...but in some cases you take over after someone else has implemented

[veremin]

Understood.

So for now you have to either stuff repository with additional space or disable periodic full backup, since you cannot afford it at the moment.

Thanks.