A way to ignore "Latest available restore point is already replicated" warning?

[DonZoomik]

Scenario

• Many backup jobs on source site, running multiple times a day
• Several backup copy jobs to target disaster recovery site, once a day (limited bandwidth)
• One replication job, configured to only take data from backup copies
• Replication job is configured to run after one of backup jobs

Many backup and copy jobs are required to keep data size reasonable so we could run monthly data validations within 24 hour window.

As there is no deterministic way to start replication after all data is copied (backup copy jobs can complete effectively in any order), we have to run replication job many times a day and it eventually gets replicas updated over the day. However this means constant warning state as many replicas are already up to date.

Is there a way to ignore this warning? Similar to DisableVMwareToolsNotFoundWarning registry flag that removes warning for VMs without VMware tools.

[PetrM]

Hello,

There is no registry value to disable the warning message but we will think about an implementation of such registry value if we have enough similar requests for this functionality.

Thanks!

[rbienvault]

I have too sometimes these warnings.
Avoiding to get them will be great.

[bricekar]

dear ,

we get also the same issue with that message quite boring to ignore.
thx for the ignoring process message.. that will come

see you

[PetrM]

Thanks for your feedback, it's much appreciated! We have not yet decided on the proposed improvement as we still continue tracking requests for this functionality.

Thanks!

[Gostev]

As there is no deterministic way to start replication after all data is copied

What about using the BackupCopyLookForward behavior mod?

[DonZoomik]

AFAIK this only applies to backup copy, not replication. This will still not trigger replication when all backup copies have completed...?

[Gostev]

I missed the fact that you were talking about replication jobs, sorry.