Sysadmin #1 started amdump this morning to correct a failed dump from
last night. Sysadmin #2 needed to restore a file, and started
amrecover on the backup machine. Sysadmin #2 was unaware of the
running backup process and used amtape to change slots. OOPS, both
sysadmins got really weird errors, not quite descriptive of the
actual problem (that you cant dump and restore at the same time).
Maybe a check could be
Actually, I have two tapedrives (used with chg-multi) and I do sometimes
restore while dumping or flushing... It is possible to dump and
restore at the same time, when not using the same tapedrive.
So there could or (should ?) be a "device lock" ?
As far as I tested it, any "amtape xxx" waits or errors out until the
tape is free. No need for a "device lock", as that is already done
in the Unix kernel.
What error message did they get that was confusing?
--
Paul Bijnens, Xplanation Tel +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM Fax +32 16 397.512
http://www.xplanation.com/ email: Paul.Bijnens AT xplanation DOT com
***********************************************************************
* I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, *
* quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, *
* kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... *
* ... "Are you sure?" ... YES ... Phew ... I'm out *
***********************************************************************
|
