Backup copy - Misleading e-mails?

[perjonsson1960]

Folks,

Now and then I get an e-mail from B&R saying that the backup copy job failed. In the mail in says "Error" for one or more VMs, with the explanation that "Incremental copy was not processed during the previous copy interval". In the job list in the B&R console it also says "Failed" in the "Last Result" column. But when I click on the job and look at the job log, it says "Success" on all VMs. Why is B&R sending an e-mail that to me seems misleading and, quite frankly, wrong. I think that it should only be a warning, if anything.

PJ

[Dima P.]

Hello PJ,

Can you please check if RPO monitor is configured or not? Thanks!

[perjonsson1960]

All my backup copy jobs are Periodic Copy. RPO Monitor seems to be available only with Immediate Copy.

[Gostev]

"No backup created" situation has always been an error in our severities paradigm, so the email is correct and not misleading. I would rather have our support look at why the job session shows Success for all VMs in your case

[foggy]

Not being able to perform a backup is not a warning but a failure, indeed. The job status inconsistency in the job list and the job log is not expected, could you please open a case so our engineers could take a closer look and make sure you're looking at the right session entry?

[perjonsson1960]

Hmm... This is strange... This particular backup copy job has a "starting at" time of 11:45 every day. I'm looking in the history; The session on June 16 shows "Success" on the job and on the three servers in the job. The session on the 17th shows "Failed" on the job, and "Failed" on one of the servers:

2021-06-17 11:46:00 :: Latest restore point is already copied
2021-06-18 11:45:13 :: Incremental copy was not processed during the previous copy interval
2021-06-18 11:45:13 :: Processing finished with errors at 2021-06-18 11:45:13

And the session today, the 18th, shows "Failed" on the job, but "Success" on all three servers.

I suppose that I am being confused by the fact that the e-mail was sent when the copy interval (that started yesterday) expired today, seemingly 24 hours too late, even though it probably isn't... But what I don't understand is what caused the error in the first place, because "Latest restore point is already copied" is not an error. That happens now and then in various jobs here and there.

Bottom line; Perhaps the e-mail is not misleading, but confusing.

[foggy]

Logs should tell the exact reason for the failure so opening a case is recommended.

[joachim.suess]

Hi gostev,

you wrote:
"No backup created" situation has always been an error in our severities paradigm, so the email is correct and not misleading. I would rather have our support look at why the job session shows Success for all VMs in your case.

But this is about the reporting of copy jobs. so if there is no data to copy and "latest restore point is already copied", the reporting of the copy job has to be successful because everything that is in source has been copied to target.
what i expect is a report of a failed backup job.

I have that misleading reporting mails at a customer situation, where 3 backup jobs are included in one copy job. but the three backup jobs have not the same scedule, so for me, it is expected that some VMs copy daily, some every two days and the rest only once per week.

so why should the copy be in status "failed", when it is expected that the most source VMs have not been backed up?
when there is message "Latest restore point has already been copied", the status has to be "Success"!

best regards
Joe

[foggy]

You expect this since you've intentionally configured such a schedule for the source jobs. While there could be cases where the customer expects the copy job to copy data and the source job didn't create the restore point for whatever reason - and in this case, we need to warn him.