From time to time we see backup copy jobs at customers who is running "forever", meaning showing run time for lets say 70 hours, even when we have set the internval to 1 day.
This is solved by starting the server. Sometimes it works just to take the services, but often we have to reboot the server.
What could cause this?
As an bad programmere I would have a "if more than 24 hours than fail and restart the job)
The last sentence was of course just a joke since I am not a programmer..
Primary it is "Waiting for the new copy interval".
Dont want to create 8 cases for this..
But I see this sometimes at different customer sites. Somestimes it also can be explained if the service provider has been down for some time for maintenance. But primary that is not the reason and it still occurs. Even when other backup copy jobs at same server works fine against the same service provider and repository.
frankive wrote:Primary it is "Waiting for the new copy interval".
Do you mean the job is waiting for the new copy interval to start while it should be already started (according to the schedule) and new restore points are waiting on the source?
experienced the same again with a customer. 11 days without offsite backup, due to he didnt receive any email alerts either since the job did go on forever..
# 01203298
