Feature request - warning emails

[SAFA_IT]

I have noticed that emails from B&R with 'warning' in the subject line may contain information about a previous error. I think the email should in these cases be marked 'error'.

Example: A DR replication job fails due to an unexpected termination. This appears as an error in the body of the email. The job retries and detects 'Restore point found, but is older than previously replicated one'. This generates a warning. the email is sent out with 'warning' in the subject line, but there is a error that needs resolved.

I would like to see the subject line showing error if an error has been detected in a job.

[PetrM]

Hi David,

Thanks for the idea! But in your case, warning and error are related to different job sessions and you get a notification about the latest one only. If you want to see the full history of job runs in order to find a correlation between the latest warning and a previous error, you may generate html-report in Veeam B&R console.

Thanks!

[SAFA_IT]

Thanks for the feedback - however, in the example I gave, the job is left in a state where no subsequent sessions will update the job, so I would consider that an error. If I get an 'error' email in the evening at home to my phone, I will log in to the server to see what was happening - I wouldn't do that with a warning.

[PetrM]

The main point is that the latest state of the original VM has been successfully replicated and there is no actual data to process within the current session. Therefore, it should be treated as a warning because no urgent remedy actions are required from your side and the latest restore point is fully consistent.

Thanks!

[SAFA_IT]

Unfortunately, that is not the case in this instance. This may be unique to Veeam Cloud Connect replicas, but if the remote connection is dropped, a replica will be created with size 0b. This is the error. When the job retries, it sees the 0b file, treats it as an up to date replica and this is treated as a warning. If you are really lucky, a new replica might be created the next time the job runs, but nearly always the 0b previous replica prevents the job completing properly. Warning emails continue to be sent, but the replica is not getting updated.

It is almost always necessary to delete and reseed the replica in this situation - so I would regard this as an error.

[PetrM]

Hi David,

Well, I think that the real problem is not the job session status whether it is warning or error but:

it sees the 0b file, treats it as an up to date replica

The behavior itself should be fixed, can you please provide a support case ID for this issue?

Thanks!

[SAFA_IT]

Hi Petr,

I didn't really want to get to the issue of support - Veeam B&R support has been excellent for many years, but VCC support is sadly lacking. I have an old case 01957212, this was never resolved as there were delays getting the SP logs. The current issue was resolved by deleting the replica. I emailed the SP yesterday about the new incident, I am still awaiting response.
In reality, I know I am better off reseeding for 5 hours rather than waiting for a response from the SP or Veeam if a case is subsequently opened.

[PetrM]

Ok, I'll ask our QA engineers to check this scenario. Nevertheless, technical issues must be analyzed by our support team. Do not hesitate to request an escalation of the support case if you're not satisfied how it's being handled. One more point to keep in mind is that different technical issues have different level of complexity and some cases require more time for troubleshooting.

Thanks!

[FrancWest]

This specific error is a known issue. See:

veeam-backup-replication-f2/replication ... 66790.html

[18436572]

I'd like to get this resolved too. We run replicas from copies and this error occurs once in a while (maybe 1 in 50 runs). Our setup is a backup job with secondary location in immediate mode. The copy has a post job script to replicate. If the repl job fails, I either wait or run a new backup job to start the 3-job chain again. Thanks.

[FrancWest]

Hi,

can you reply on the thread I refererred to, that way we can put some more pressure on Veeam to fix this issue.

Thanks!

[PetrM]

Hello,

I've just heard back from my colleagues from QA that the issue reported in this topic is the same one which was discussed in the thread mentioned by Franc. I had some doubts because of Cloud Connect specific. I'll speak to the team in order to accelerate fix development but I cannot give any ETA.

Thanks!