[Networker] daily networker contention...
2012-02-28 09:19:23
I have a storage node that has two AFTD's and two tape drives. I have Oracle
DBA's that insist
they are better at manually backing up their databases than NetWorker will ever
be. I have a
script that manages staging of data from the AFTD's onto tape.
Every day between 9am, those three facts gang up and
the DBA's run multiple save commands that write save sets onto the AFTD's and
then run clone
commands to copy them to offsite tapes to go to the vault, the staging script
sees that the
DBA's have done this and decide to stage some data off one of the AFTDs to the
tape pool. The
clone grabs the AFTD, the stage grabs the tape drive - and then both wait for
the other to be
done. Eventually, the first DBA inspired clone that got the other AFTD and the
other tape
drive finishes and the second DBA clone uses that tape because it's in the
correct pool and
then the stage gets the AFTD and writes to the tape it has been holding onto.
Does anyone else experience that staging and cloning seem to get their
resources in opposite
order and thus go out of their way to try to deadlock themselves?
Oh, I'm running NW 7.6.3.1 on RHEL6 64-bit servers.
--
Frank Swasey | http://www.uvm.edu/~fcs
Sr Systems Administrator | Always remember: You are UNIQUE,
University of Vermont | just like everyone else.
"I am not young enough to know everything." - Oscar Wilde (1854-1900)
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Networker] daily networker contention...,
Francis Swasey <=
|
|
|