Hi All,
This is a duplicate of another post that I started about 2 years ago (pasted below and linked here). I am still having the same issues as a resolution was never reached, but now we are breaching our backup window.
In the previous thread, there were suggestions around updates and B2D folder structure, which I have followed, but for some reason, the jobs insist on beginning simultaneously.
The version is fully patched, and I have followed the suggestion in the previous thread (here).
Can anyone offer some new hope, 2 years later?
Cheers
Craig.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Hi all,
I would like some help or advice about a strange situation that is occurring with a daily rotation of multiple B2D jobs configured as separate jobs, with separate selection lists via a policy.
I have followed the Symantec best practices advice and configured a GFS rotation with a SATA HDD for each day (Mon-Thurs), 3 weekly drives (Weekly1-3) and 3 monthly drives (Monthly1-3).
Each separate drive has it's own B2D folder and each of these folders have been added to the corresponding pool (i.e. Daily Pool, Weekly Pool, Monthly Pool), which the jobs reference.
I have set the number of concurrent jobs to 1 on both the device and the general preferences, however, no matter what I do, 2 jobs run concurrently every night, which breaches our backup window due to some overlap in processes running.
If the jobs are run consecutively, we make the window and the throughputs are double if we run concurrently.
Can anyone please shed some light on why 2 jobs are running concurrently, even though I have selected that only 1 run?
Thanking in advance,