04-28-2018 12:26 PM
Why is it that active backup jobs will not just immediately cancel when requested?
Backup Exec 16 seems to be as responsive to a cancel request, as a freight train hauling 500 tons of steel rebar trying to stop.
After sitting here waiting for 10 minutes with four simultaneous deduplication backup jobs at "Cancel Pending", and the server CPU load at about 10%, I gave up and rebooted the Windows server.
On reboot, those jobs are now listed as "Recovered" and have kept on running anyway.
What the....?
,
Is there some way to just simply outright kill these jobs without waiting for "Cancel Pending"?
Do I have to physically disconnect the network cables or go into the Windows network properties and disable all the network adapters, to get it to finally listen to me and stop?
04-28-2018 05:51 PM
This is because BE is not a stand-alone application. It has to invoke a lot of other process to do its job, e.g. VSS. Hence stopping a job invokes stopping these processes first and this takes time. Often these processes are unresponsive and BE still have to wait.
If you want to stop a job immediately, then restart all the BE services.
04-28-2018 07:31 PM