Bug in "Terminate job that exceeds allowed backup window"

[christiankelly]

When you set a "backup window" for a replication job and you go over the time allotted there are a few bad side effects.

1: You get an "Error: Terminated" which I think should read "Error: Job exceeded backup window" or something like that.
2: A much bigger issue is the snapshot does not get removed. I have run up on this a few times so I know it wasn't a fluke but it gives about 5 min for the "Removing snapshot" and then "Timed out waiting for all VDDK disks to close"

It seems like the job wants to terminate so it doesn’t wait for the removing snapshot? In any case it leaves the VM in a bad state that you need to manually consolidate. To recreate this bug you need to have a snapshot that is big enough that it doesn’t apply in under 5 or 10 min.

Thanks,

[Gostev]

Snapshot absolutely must be removed even when the job is terminated. I will ask our QC to try and reproduced that. Do you have a support case for this open with us by any chance? This would help me tremendously.

[christiankelly]

I will open a case upload logs and reference this case. Once done I'll post back with the case number. For now I have stopped using backup windows.

[dlieshout@client.nl]

Any update on this. One customer does have the same issue with B&R 6.5 + patch 1.

[Vitaliy S.]

Unfortunately, I cannot find the OP's support case to verify that, so please contact our support team directly if your customer experiences the same behavior. Thanks!

[Poweruser]

I have the same problem. If terminate is on, job fails.
Please fix.

[Vitaliy S.]

Poweruser, please share your case ID as this would help us to investigate the issue.

[Poweruser]

need to open a case first
should i?

[Vitaliy S.]

Yes, this would allow us to make sure your use case is also resolved.

[Poweruser]

confused... when i open a case, whats the benefit of posting case id here?

[Vitaliy S.]

This is needed, so that we could update this topic with a resolution for future readers This might save some time for them, for example, if there is a hotfix or a KB article created already.