Hello,
My config is as follow:
1 primary server / 4 distributed, a HP MSL6030 30 slot shared over FC.
On teo of the distibuted server, the backup behave as if they aren't waiting for the lib to get free up.
In the log on "working" server i see from the time the job should start line saying "Job can not be start" then "Check device availablity"
Then the job starts properly once the library has been released by other machines.
In the log of "non-working" server I have sequence as follow:
- Jon cab not be started
- Check device availabilty
- then the job move from Ready to Active
- then I have a failure to connect to Media.
- Waiting by +/-30min+
- then job start on a blamk tape, discarded the one it should use.
so, instead of using one tape for all my job (as it fits), I use two (while I still have 100% backup anyway)
HAs anyone ever seen that before ?
Thanks,
Chris
My config is as follow:
1 primary server / 4 distributed, a HP MSL6030 30 slot shared over FC.
On teo of the distibuted server, the backup behave as if they aren't waiting for the lib to get free up.
In the log on "working" server i see from the time the job should start line saying "Job can not be start" then "Check device availablity"
Then the job starts properly once the library has been released by other machines.
In the log of "non-working" server I have sequence as follow:
- Jon cab not be started
- Check device availabilty
- then the job move from Ready to Active
- then I have a failure to connect to Media.
- Waiting by +/-30min+
- then job start on a blamk tape, discarded the one it should use.
so, instead of using one tape for all my job (as it fits), I use two (while I still have 100% backup anyway)
HAs anyone ever seen that before ?
Thanks,
Chris