I have a Backup Copy Job which was created two months ago. Everything was working fine. However, starting from Nov 28, this job keeps generating warnings.
The warning says that it is "Waiting for the next task". But, it only takes 0 second.
I have tried to recreate the job, but the same warning still pops up. Anyone has ideas about this issue?
That's v12 installation which was not upgraded to 12.1 right? Any changes with the source jobs i.e. changing backup chain format (single storage to true per-vm), encryption settings or any other modifications with the source? How the mentioned machines are added to the backup copy job? Thank you!
Yes, it is v12 installation. Not upgraded to 12.1.
I have a VM Backup Job called "DMZ VM Backup" to backup the virtual machines. So, for the Backup Copy Job, I simply add the "DMZ VM Backup" as the object to process. I haven't modified "DMZ VM Backup" for months since it is working normally.
This behavior looks unexpected, can you please raise a support case and let our engineers investigate the root cause? Please share the case ID once you have it. Thank you!