Hi,
In some instances when I run a Hyper-V replication job with a backup set as the source, the job reports the following warnings.
23/05/2023 09:13:13 :: Latest available restore point is already replicated
23/05/2023 09:13:13 :: Processing finished with warnings at 23/05/2023 09:13:13
Should this really be a warning? I think it should be purely informational.
The error is not in this job. There may be an issue where the backup this replication job is sourced from has failed. But that is a separate issue and should not cause this job to finish with warnings.
Thanks
Simon
-
- Novice
- Posts: 7
- Liked: 3 times
- Joined: Mar 30, 2023 4:34 pm
- Full Name: Simon Buckner
- Contact:
-
- Veeam Software
- Posts: 3697
- Liked: 620 times
- Joined: Aug 28, 2013 8:23 am
- Full Name: Petr Makarov
- Location: Prague, Czech Republic
- Contact:
Re: Warning: Latest available restore point is already replicated
Hi Simon and Welcome to Veeam R&D Forums!
Please let me have some time to research why do we show a warning message in this case. I'll update the topic as soon as I have more details.
Thanks!
Please let me have some time to research why do we show a warning message in this case. I'll update the topic as soon as I have more details.
Thanks!
-
- Veeam Software
- Posts: 3697
- Liked: 620 times
- Joined: Aug 28, 2013 8:23 am
- Full Name: Petr Makarov
- Location: Prague, Czech Republic
- Contact:
Re: Warning: Latest available restore point is already replicated
Hello,
I looked a bit deeper into this behavior and the explanation turned out to be pretty obvious: the main purpose to show the warning in this case is to inform you that there was no data replication otherwise it's easy to overlook a serious issue and find out that the most recent replication was performed long time ago (f.e. one year), it's a potential data loss. Anyway, we'll take into account your idea to make this message informational and will think about changing this behavior if we have enough similar requests.
Thanks!
I looked a bit deeper into this behavior and the explanation turned out to be pretty obvious: the main purpose to show the warning in this case is to inform you that there was no data replication otherwise it's easy to overlook a serious issue and find out that the most recent replication was performed long time ago (f.e. one year), it's a potential data loss. Anyway, we'll take into account your idea to make this message informational and will think about changing this behavior if we have enough similar requests.
Thanks!
Who is online
Users browsing this forum: No registered users and 24 guests