Hi all,
I'm working on writing some scripts to install and upgrade TSM 6.2 on AIX for a
customer.
Unfortunately this involves deinstalling TSM on occasion. My test systems might
not be the most powerful (0.2 power6 CPU), but it takes the uninstaller over an
hour to remove TSM from the system.
Hi,
while testing with TSM and trying to build a sensible environment TSM gave me a
nice message:
ANR1546W The available space for the server database directory (
/data/tsm01/tsm01 ) is less than 1 GB.
while that is absolutely true, I don't see why this should be a problem. There
is close to
I see this on RHEL too. It takes about 30 minutes of Java cogitation on
my systems, with no feedback of any kind.
On 02/15/11 07:52 AM, Remco Post wrote:
Hi all,
I'm working on writing some scripts to install and upgrade TSM 6.2 on AIX for a
customer.
Unfortunately this involves deinstalling
We have had problems, since our upgrad efrom an i2000 to an i6000 in October
2010. The drives were IBM LTO-3 and now they are HP LTO-5. They disappear from
the OS. If we reboot the library once a week it seems to be fine. Quantum is
either unwilling or unable to provide an answer.
I3AZ is based
It may be an annoyance for testing on a very small database, but
would'nt you want a warning if your database was running out of space
in a production TSM environment?
On Tue, Feb 15, 2011 at 09:57, Remco Post wrote:
> Hi,
>
> while testing with TSM and trying to build a sensible environment TSM
We're running into a problem when trying to change SQLLiteSpeed backups
clients to point to new TSM servers.
The old TSM servers are RHEL4 (on Intel) running TSM server 5.5.5.0 with
efix for APAR IC71586. (kernel 2.6.9-89.0.11.ELsmp)
The new TSM servers are RHEL5 (on Intel) running TSM server 5.
Robert,
On it's face, this sounds like something in the network, with "network"
being between the TSM client side TCP stack and the TSM server side TCP
stack. Have you done any kind of packet tracing to see what's going on?
Best regards,
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Cli
Remco,
I had the same warning too on a production TSM server (SLES 10 SP1), the
database directory had however 4 file systems mounted of 25 GB each that were
used in the database define command during the TSM setup. So plenty of free
database space ...
I've ended up by enlarging the file syste
Presumably, the TSM server Activity Log has been inspected for any session
failure issues, such as too-short timeout values or preemption. And,
hopefully, there's nothing in the client OS which is clobbering network usage
(such as bad anti-virus software).
Unusual possibilities that I could th
IC74005: MESSAGE "ANR1546W THE AVAILABLE SPACE FOR THE SERVER DATABASE
DIRECTORY" IS MISLEADING
APAR statusOPEN
Error description The wording "server database directory" used in
"ANR1546W The
available space for the server database directory (
/home/tsminst1/tsminst1 ) is less than 1GB." can be
Hi Andy,
Yes we did get a tcpdump from the TSM server running RHEL5, and we can see
the server sending a windo size 0 in the ack. This preceeds the session
stop making backup process, and is repeatable.
I've also been told that this failure does not happen while tracing is
enabled in the TSM clie
wow, somebody who can find APARs, thanks, and somebody who bothered to report
this issue.
now, all I'm wondering about IBM will probably change the message, not the
threshold. I don't see why we need 1 GB of free space in the default database
directory, there is still almost nothing in ther
12 matches
Mail list logo
