Re: Eisner? Down? (30 days later)

Bill Gunshannon wrote:
In article <3cWdnY4c_JcRWBTUnZ2dnUVZ_gSdnZ2d@xxxxxxxxxxxx>,
"Richard B. Gilbert" <rgilbert88@xxxxxxxxxxx> writes:
Duncan Brown wrote:
Richard B. Gilbert wrote:
It has been about five years since I last did anything with a SWXCR but ISTR that you could save the configuration on a floppy disk and that this floppy would allow you to replace SWXCRs by loading the new with a configuration identical to the old. AIRC I never actually did it.

That is correct, you could save the config to floppy which would save lots of time if replacing the controller. Of course, that depends on the system manager actively saving the latest config to floppy... and from all I've heard I wouldn't bet on that being the case here.

If I had this system in front of me, I would expend a fair amount of effort trying to get the existing SWXCR and disks running again. Failing that, if it was possible to hand-transcribe the current config from the management program (or better yet, save it to floppy) I would try replacing the SWXCR and seeing if I could get it running. If the SXWCR is completely dead/corrupt and the config is not discernable then I would simply rebuild the system onto newer/less insane storage from whatever the latest backups are, and be satisfied with that.

Even if the system is completely recoverable using the existing SWXCR and disks, I would migrate off of that setup ASAP.

That takes money! The SWXCR's chief (only?) virtue is cheap RAID!

And, what good is RAID that leaves the system down for months at a time?


Not much but I don't think that RAID is entirely at fault. It appears from discussion here that the custodian of Eisner has abandoned his post.

If anyone had been "minding the store" the problem almost certainly could have been fixed three or four weeks ago! Either RAID-1 or RAID-5
requires the failure of at least TWO disks to bring the RAID set down!
Failure of the controller, of course, will also do it. The SWXCR is hardly the most reliable technology available these days!

ISTR that a failed RZ series disks gives warning by lighting an amber LED on the front panel; a single glance tells you "dead disk"!

But speculation is not going to get anything fixed. Neither is posting to c.o.v/info-vax.

1. A new custodian for Eisner is needed.
2. Someone must reclaim the mortal remains of Eisner from its current custodian.
3. The new custodian must gain possession.
4. The new custodian must repair what he can and get someone to repair anything he cannot!
5. The new custodian must either have or must install the necessary communications bandwidth!
6. Plug it in, restore, and go!

Given the history so far, I'm not going to hold my breath!

<snip>
.

Relevant Pages

  • Re: Eisner? Down? (30 days later)
    ... but ISTR that you could save the configuration on a floppy disk and that this floppy would allow you to replace SWXCRs by loading the new with a configuration identical to the old. ... you could save the config to floppy which would save lots of time if replacing the controller. ... If I had this system in front of me, I would expend a fair amount of effort trying to get the existing SWXCR and disks running again. ... Failing that, if it was possible to hand-transcribe the current config from the management program I would try replacing the SWXCR and seeing if I could get it running. ...
    (comp.os.vms)
  • Re: Eisner? Down? (30 days later)
    ... that this floppy would allow you to replace SWXCRs by loading the new ... you could save the config to floppy which would save ... effort trying to get the existing SWXCR and disks running again. ...
    (comp.os.vms)
  • Re: Eisner? Down? (30 days later)
    ... but ISTR that you could save the configuration on a floppy disk and that this floppy would allow you to replace SWXCRs by loading the new with a configuration identical to the old. ... you could save the config to floppy which would save lots of time if replacing the controller. ... If I had this system in front of me, I would expend a fair amount of effort trying to get the existing SWXCR and disks running again. ... Failing that, if it was possible to hand-transcribe the current config from the management program I would try replacing the SWXCR and seeing if I could get it running. ...
    (comp.os.vms)
  • Re: Eisner? Down? (30 days later)
    ... ISTR that you could save the configuration on a floppy disk and that this ... you could save the config to floppy which would save lots ... effort trying to get the existing SWXCR and disks running again. ...
    (comp.os.vms)
  • Re: Eisner? Down? (30 days later)
    ... ISTR that you could save the configuration on a floppy disk and that this floppy would allow you to replace SWXCRs by loading the new with a configuration identical to the old. ... you could save the config to floppy which would save lots of time if replacing the controller. ... If I had this system in front of me, I would expend a fair amount of effort trying to get the existing SWXCR and disks running again. ... Failing that, if it was possible to hand-transcribe the current config from the management program I would try replacing the SWXCR and seeing if I could get it running. ...
    (comp.os.vms)