Of course, you are aware that you LM must always be at the highest major level?
So 6.1 lib client with 5.5 LM is not supported.
On 22 apr 2010, at 21:00, Zoltan Forray/AC/VCU wrote:
> I am starting to see more and more of these errors on my 6.1.3.3 server:
>
> 4/22/2010 1:58:23 PM ANRD_1141
IBM removed 6.1.3.0. From my recommendation, i will install 6.1.3.1 or 6.1.3.3
directly. and I will add the "allowreorgtable no" in the dsmserv.opt
Regards,
Fran
- Mensaje original
De: "Billaudeau, Pierre"
Para: ADSM-L@VM.MARIST.EDU
Enviado: jue,22 abril, 2010 17:32
Asunto: TSM
Hi,
I saw the same problem in one of my Customers. This occurred after migrating to
6.1.3.1. In my case I found out it could be a Storage Agent problem. We are
going to upgrade the Storage Agent to 6.1.3.1 version.
Regards
Fran
- Mensaje original
De: Zoltan Forray/AC/VCU
Para: AD
Zoltan,
By any chance, do you have some pools encrypted/some not?
My onsite pool is not encrypted, my offsite is encrypted via TSM app
managed.
Tapes get reused from one pool to the other.
Was wondering if that may enter in to the problem.
I just haven't had time to open a PMR, as it only hits me o
I am starting to see more and more of these errors on my 6.1.3.3 server:
4/22/2010 1:58:23 PM ANRD_1141620605 pvrOpen(pvr.c:1376)
Thread<51658>: Attempt to open volume with conflicting device class IDs:
1, 2
4/22/2010 1:58:23 PM ANRD Thread<51658> issued message from:
4/22/2010 1:58:2
mory to support a commoditized web service.
You want P-series and AIX behind the DB2 and TSM layers, but for the
websphere stuff, I don't know why you'd care.
- Allen S. Rout
__ Information from ESET NOD32 Antivirus, version of virus
signature database 5051 (20100422) __
to use the expesive AIX CPU and
> memory to support a commoditized web service.
>
> You want P-series and AIX behind the DB2 and TSM layers, but for the
> websphere stuff, I don't know why you'd care.
>
>
> - Allen S. Rout
>
> __ Information from ESET NOD32 Antivirus, version of virus
signature database 5051 (20100422) __
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
>
>
>> On Thu, 22 Apr 2010 18:18:14 +0200, km said:
> Inotify has been a part of the kernel since 2.6.13 and is supported
> on all RHEL 5 releases and atleast SLES 10+ so this should work on any
> modern Linux.
That's what I'm hoping.
I've gotten several responses off-list; I'll quote but not attr
tion from ESET NOD32 Antivirus, version of virus signature
database 5051 (20100422) __
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
Really nice!
Inotify has been a part of the kernel since 2.6.13 and is supported
on all RHEL 5 releases and atleast SLES 10+ so this should work on any
modern Linux.
-km
On 21/04, Allen S. Rout wrote:
> I've got a few clients with rather large filesystems: ~6K dirs, ~2.2M
> files, 10 filesystems
>> On Thu, 22 Apr 2010 10:26:05 -0500, Dana Holland
>> said:
> Thanks - we're going to upgrade the RAM to 16gb. But it sounds like I
> don't need to worry about upgrading the processors.
> I didn't realize that it was going to require Websphere. Is this part
> of the Tivoli installation, or
Hi,
In order to resolve problems we have with the current version of
TSM (6.1.2.1) :
- Expiration fails on one large node (14Million entries for one
filespace).
- Database increase 1gb per day.
- Retrieve file on WEB or GUI takes over 30 minutes to list
cessor power. Does
anyone know if this server will be sufficient?
__ Information from ESET NOD32 Antivirus, version of virus signature
database 5050 (20100422) __
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
4G is unlikely to work well.
You are installing a copy of DB2 (for the TSM server) and a copy of
Websphere (for the admin center) under the covers.
If you are planning a small installation and don't have any very strict
timing windows to meet (and they haven't put in any size checks in the
6.2 ins
We're about to set up TSM for the first time. I was surprised to see in
the installation guide that 12gb of RAM is required for 6.2 The server
that we were planning on using only has 4gb - it's an IBM 7026-6H1 -
with a 2-way 1.2ghz power4+ processor. I don't see anything in the
installation gui
Hello All,
Conventional wisdom is that for TSM on Solaris, raw volumes are the way
to go. I have 4 Sun X4540 servers each with 64GB of memory and 48x1TB
internal SATA disks. The whole disk farm is one big ZFS zpool. TSM DB
and Log are on external fast SAN disk.
So far I've been using sequenti
16 matches
Mail list logo
