Sunday, 15 November 2015 12:00:15 AM
Success0Start time12:00:15 AMProcessed0.0 KBBackup size30.1 MBSome VMs were not processed during the copy interval
Warning0End time12:35:09 AM (+1)Read0.0 KBDedupe1.0x
Error1Duration0:44:49 Transferred0.0 KB (1x)Compression1.0x
NameStatusStart timeEnd timeProcessedReadTransferredDurationDetails
SERVERNAMEError12:10:15 AM12:00:15 AM (+1)0.0 KB0.0 KB0.0 KB (1x)0:00:00 Incremental copy was not processed during the copy interval
BTobbe wrote:This creates an alert every Saturday and Sunday (almost) that the backup copy job failed: Some VMs were not processed during the copy interval, Incremental copy was not processed during the copy interval.
BTobbe wrote:Another issue that I think might be related to this is that everytime a backup copy job fails, it creates a .vib file with the normal name for that name with the size of 30 844kb and I'm guessing this is because it failed.
BTobbe wrote:Hi Foggy, late reply but we are on 22.214.171.1244 and getting these errors.
BTobbe wrote:About the placeholder restore point, I understood that it comes from that, but will the job copy that restore point as well the next day? Or will that days restore point be missing on the backup copy repo?
foggy wrote:Hi Lucio, using PowerShell script mentioned on the first page of this thread is the recommended workaround.
BTobbe wrote:So I was in contact with support and they contradict what you say. They say that this error will not be removeable if you have running backup jobs on the weekend. I don't really understand why this is the case as mail errors that aren't supposed to be errors is quite annoying as then you might miss an actual error because you just think it's a non issue.
Users browsing this forum: Bing [Bot], Google Feedfetcher and 24 guests