Well, I have customers running both AIX and RHEL, and my experience this far is
that AIX still outperforms RHEL on I/O performance. It might be that the
systems running AIX usually have more expensive/higher performance equipment
connected to them than their RHEL counterpart.
I also prefer the
Yes, it is. There are very few things I would say this about, but this is one
of 'em.
For a RHEL box to match the performance capabilities it would have to be
installed on Power as well (which it can be). I think the evidence I've seen
both in experience and raw numbers has shown the power
How did tape Q0 get into the library? Did you manually load a batch of
tapes in this library without checking them in thru the bulk I/O?
If that is the case, you can just checkin the tapes.
You can try:
Check in volumes that are already labeled:
checkin libvolume NAS_QI6000 search=yes
I think he was looking for Power vs x86 in price/performance.
I.E If you spend 50K on Power systems and 50K on x86 systems. which
could produce more I/O throughput.
(If not, that's what I'd like to hear an update on)
From what I remember from previous discussions, x86/linux would come out
on
The paradigm has shifted quite a bit since the hey-day of AIX systems. Back
then, you would custom configure a substantial AIX system, and require premium
service from IBM, with fast response from them. RS/6000s were renowned for
reliability, though, with very few core system problems (most
Roger
Before running the DELete VOLHistory with FORCE=YES, try running an AUDIT
LIBRary LIBE CHECKLabel=Barcode from the library client.
Perversely, it doesn't report the discrepancies it discovers in the
activity log on either the library client or the library manager (at least
on v5.5), but
Must not have been clear. Sorry about that. For every 1 proc or core
of Power you would need 4 or more of x86 (even at their best level). I
have seen the numbers from Intel comparing Newer x86 processors to
Power6 and they are just below the Power 6 (using 2x's the number of
cores). The
We just ran an initial backup of a Windows 2003 MS SQL server with TSM
6.2.2.0 client code. We got the following errors:
ANE4987E (Session: 172392, Node: MHDHSMSQL) Error
processing '\\mhdhsmsql\c$\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\Data\tempdb.mdf': the object is in
use by
Think you need a statement like the following.
Exclude *:\...\*.mdf
That will exclude all .mdf on any drive iin any directory including the root.
Gary Lee
Senior System Programmer
Ball State University
phone: 765-285-1310
-Original Message-
From: ADSM: Dist Stor Manager
