At 06:36 AM 4/18/2007, Greg Freemyer wrote:
On 4/15/07, scsijon <[EMAIL PROTECTED]> wrote:
At 08:56 AM 4/15/2007, Darryl Gregorash wrote:
>On 2007-04-14 16:07, Alexey Eremenko wrote:
> > What will happen after "sdX" reaches from sda to sdz ? i.e. if you
> > have over 26 hard disks in your system ?
> >
>If you have that many in your system, I think you should consider
>replacing some of them with much larger drives ;-)
THIS IS NOT A FLAME, but....
personally this change seriously makes me worry
I have scripts and software that create drives with links to those in other
systems as part of the security and backup routines I use, some are to
scsi drives, some are ide and some sata, the drive type in most cases
relates to the function performed on the site or spanning sites
Before I can consider going to 10.3 :-
I shall have to scan, amend, rewrite, binfile at least 20
scripts for cross connection, another 38 for backup and seven security
plus workout how I get around the drive type and now
limited drive identity\numbers problem
and that's just the linux side, how my mini's deal with it I am yet
to imagine,
thankfully I don't have any mainframes any more. I also suspect it means
some ten to twelve thousand dollars additional hardware needed per site,
say a quarter of a million dollars plus extra at the four centres and spares
of course.
I wouldn't of minded the change if the old way worked as well (dual modes)
until things were changed with a boot script "software switch"
I'd also would have liked some warning, (and I suspect others in the same
boat would also have,) well in advance this type of change was going to
happen, surely someone was aware this major change was coming and
could have put out a notice to users/programmers. It's not as if this is a
minor change hda has been around since the ST408/512 drive chains were
created
It means I have at least 200 hours of work ahead in mapping out the changes
needed, let alone arranging things like programming, testing, reviewing,
issuing, checking...etc., say another hundred or so thousand dollars
Well there goes my holiday this year again, and just as I thought things were
finally starting to slow down. I am suppose to be semi-retired
It also means 10.2 will have to last at least two years when we
implement it at
Christmas 07, replacing 8
Maybe we should think sled, but we don't have the money for both, we are
?suppose to be self sufficent and non-profit!
scsijon
I was just thinking about how a new OS release is going to cost you a
huge amount of time and money. Basically the reason is you are using
a Linux Enthusiasts distro as a datacenter solution which you are
apparently investing millions of dollars of
hardware/software/customization around.
You should really evaluate SLES 10.0. It is expensive compared to
OpenSUSE, but it is extremely cheap compared to what you describe. If
you implemented it now you would have another 4 years or so of
supported service. (iirc)
Greg
--
Greg Freemyer
The Norcross Group
Forensics for the 21st Century
to answer a number of comments together.
1/
unfortunately I have "absolutely" no control or input in the software
$$$$, I fought
and lost this battle when SLES9 came out and we were using 7.2. I have been
given some control on the hardware $$ though, so the users are at least not
using P2's any more and have decent screens (35w 19"LCD vs 340w 17" tube
power use, does talk money saving in the budget meeting).
2/
the scripts are unfortunately messy and due to a level of management paranoia,
have to be individually coded else there would only be three.
They contain test and checks against failure of hardware and cross site links
and include such bits as disabling / enabling backup links in the
routers if paths
fail. e.g. backups go to two remote devices (one interstate) as well
as the local
tape silo.
3/
With downsizing that has happened due to the net, i've been waiting for site
shutdowns to ocurr, but they seem to prefer to use the, "large number of sites
with small number of staff in each model", at least.
scsijon
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
