Mark,
If the Netware guys don't care about sys:system then why would you? However, I'm not
sure that will fix the problem. My guess is that its more a case of an
'underdeveloped' nlm. Novell is constantly coming out with new versions of the tsa
nlms to address irregularities related to TSM.
Hi everyone,
We're running TSM 4.1.14 on OS/390 V2R9. I want to move a UNIX client from
the current TSM server to a brand new TSM server for testing. Can anyone
tell me how to accomplish this?
Thanks
Blue Cross Blue Shield of Florida, Inc., and its subsidiary and
affiliate companies are
Ready for painless fun? I knew you were!
for each filesystem you have in /etc/fstab do this in dsm.sys
VirtualMountPoint $FILESYSTEMNAME
I just tried this on the /home fs of one of our servers here ( they're all a little
busy to be doing a full incremental right now, though I'm going to try
Yes, it's easy.
You need to define a device class of TYPE FILE. The devclass name can be
anything you want.
MAXCAPACITY should be large enough to contain a DB backup.
The directory should be the pathname where you want the file to go.
You can define it via the command line or the browser
Upgrade to TSAUP7.EXE from Novell support.
-Original Message-
From: Mark Morrison [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 07, 2001 9:29 AM
To: [EMAIL PROTECTED]
Subject: Netware TSA500.nlm problem.
I'm having a problem with one of my servers and the TSA500.NLM file. The
I do think that you have to upgrade the ADSM version. If I remember
correctly LTO is support as from version TSM 4.X. Be sure to have a look at
www.tivoli.com.
Greetings
Karel Bos
-Oorspronkelijk bericht-
Van: Peter Daransky [mailto:[EMAIL PROTECTED]]
Verzonden: woensdag 7 november
I experienced the same problem after applying NW 5.1SP3 to my Novell servers. You need
to download the tsa5up7 (tid#2960255) from Novell, and apply it to the NW server
according to Novell's instructions. back ups should run ok then.
Jose R. Palomo
Network Administrator
California Energy
If you are just testing, just change the dsm.sys file on the client so that
tcpserveraddress points to the new TSM server. Register the client on the
new server, and let it back up to the new server until your testing is done.
The old backups will stay intact so you can use them if you need them
Coolness,
thanks for the hint. It is even in the readme, no hint about ext3 there so we
must assume ext3 is not yet supported. Luckily ext3 is sort of ext2 release
2.5, so the developers shold not have to much problems supporting ext3. ;)
The linux client for 4.2.0 supports reiserfs; I'm using
The linux client for 4.2.0 supports reiserfs; I'm using it on an intel/SuSE
7.2 system. I don't know about ext3.
Tom Kauffman
NIBCO, Inc
-Original Message-
From: Wayne T. Smith [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 07, 2001 9:24 AM
To: [EMAIL PROTECTED]
Subject: Re:
hi,
We use Oracle EBU and it's always failing on the same file with message
id
EBU-7009 (see log excerpt below). The file is 1660MB in size (quite
large), but our TSM disk storage pool is configured with no size limit.
Oracle says EBU-7xxx errors are relayed from the underlying backup system
Edit the dsm.sys file to create a stanza for the new server. Then edit the
dsm.opt file to point at that new stanza.
Kelly J. Lipp
Storage Solutions Specialists, Inc.
PO Box 51313
Colorado Springs, CO 80949
[EMAIL PROTECTED] or [EMAIL PROTECTED]
www.storsol.com or www.storserver.com
Define the client node on the new server, and then point the
TCPServeraddress line in the dsm.sys file to the new server.
You could even set it up where the client can use both servers. Just have
two stanzas, one for each server in the dsm.sys file.
-dnr
-Original Message-
From: ADSM:
Forgot to mention: We are a re-charge service out of the Central Computer
Services (mainframe) group.
Most of our users are Windows and Mac (soon to be Max OS-X .. IBM!!!)
They love/hate our service. If it wasn't for us they'd either be:
1) doing no backups
2) backups that are stored in
Recently upgraded from TSM Server 3.7.2 to TSM 4.1.40. Upgraded all windows clients
to 4.1.30. Problem we're experecing is delayed backup times on our windows clients.
We have seen no changes on our Mac, Unix, or Netware clients. Times have increased in
some cases over 300 percent. Anyone
O.k
Over the last few days I was able to test the throughput from a couple
different servers experiencing this problem. Here is what I have found.
I have verified that that ports my servers are connected to (on the
backbone) are 100/meg Full Duplex. Also the server NIC card is set to
100/meg
Running TSM 4.1 on OS390R10. Does TSM fill up data (db, log, stgpool) volumes
sequentially or does it spread the data across the available disk volumes? In other
words, if I have a 3 volume database, log, or disk storage pool, and it is 1/3 full,
will I have one full volume and 2 empty ones
Yes. Look for the dsmserv upgrade db documentation. I don't recall
whether it's in the server readme or in the manual, but it's there
somewhere.
Alex
-Original Message-
From: Bradley Wallace [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, November 06, 2001 10:42 AM
To: [EMAIL PROTECTED]
I asked the same question back not too long ago (you can always check the
archives at WWW.ADSM.ORG).
Basic answer was, yes, it spreads the data out across the various STG pool
volumes.
As for the DB, I believe it fills them, one at a time, this speaking from
my experiences when I move DB
I have a TSM/AIX server v4.2.1.6 running under AIX 4.3.3 on an H70. TSM is the
only application running on this box. I have about 300 Unix and NT clients
backing up close to 500 GB of incremental everyday on this server. TSM server
database size is 87.5 GB and 75% utilized. TSM server log size is
We have just installed the 4.2.1.0 client code on a Linux system with
a mixture of ext2 and reiserfs file systems. A 'dsmc inc' command will
consistently back up all but one of the file systems. The file system
can be backed up successfully if it is specified explicitly on the
command line ('dsmc
ADSM _should_ be able to backup a read only filesystem as adsm ( tsm, whatever )
shouldn't be writing to the filesystem to back it up ( that's what the adsm server is
for ), unless you're executing dsmc from withing that filesystem, at which point you
would be attempting to write dsmerror.log.
Can anyone tell me what the IDLE column in the SUMMARY table is?
Is it just overall idle time or is it time when the TSM server is waiting for
the client to come back and acknowledge a transaction, etc.
If I'm in a manual session and don't execute a function for a while, is it
incrementing that
I had an nt server that i backed up,but then an operator with readonly
privilage logged the server onto the network and the files would not backup
until the administrator logon the box with his user id. Form this i think
that a read only file does not backup. Could be wrong.
-Original
I didn't get any response the first time so I am posting this again with
a different subject line.
We get lots of ANE4007E and ANE4987E client messages logged into our TSM
server activity log. Short of trying to keep up with excludes for the
often changing file names is there a way to have the
Hello TSM'rs
I'm losing my mind these days with this,
Why when I checkout 10 tapes and add 10 new tapes in and try to checkin do
I get Library Full errors? I just did a restore from one tape and was just
repalcing the existing weeks tapes back. What is wrong ?
TIA
Patrick
Any ideas where /which nodes should be running out , and what parameters
should be set?
Thanks
-Original Message-
From: Daniel Sparrman [SMTP:[EMAIL PROTECTED]]
Sent: Monday, November 05, 2001 12:06 PM
To: [EMAIL PROTECTED]
Subject: Re: Clustering Nodes
If you mean
Try disable events actlog ane4987 nodename=*
and disable events actlog ane4007 nodename=*
Tim Rushforth
City of Winnipeg
-Original Message-
From: Steve Bennett [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 07, 2001 4:05 PM
To: [EMAIL PROTECTED]
Subject: client error msgs in
Works great! Tim, you are my hero.
Rushforth, Tim wrote:
Try disable events actlog ane4987 nodename=*
and disable events actlog ane4007 nodename=*
Tim Rushforth
City of Winnipeg
-Original Message-
From: Steve Bennett [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 07, 2001
What library and version of TSM do you have?
What command did you use to checkout and checkin tapes?
David Longo
[EMAIL PROTECTED] 11/07/01 05:24PM
Hello TSM'rs
I'm losing my mind these days with this,
Why when I checkout 10 tapes and add 10 new tapes in and try to checkin do
I get Library
Folks,
Server: Win2K TSM 4.2.1.6
Library: Qualstar 8210
Drives: HP Ultrium 1 (Don't know for sure if they are 215s or 230s)
I'm not seeing the drives correctly with the TSM Device Driver. Device type
and TSM device type both show as unknown.
According to the device support list these drives
Petur -
This problem was fixed in fixtest 11 (the 4.1.3.11 api). You may obtain it
from the IBM ftp server, ftp://service.boulder.ibm.com.
Switch to the
/storage/tivoli-storage-management/patches/client/v4r1/Windows/v413
directory, then retrieve and install the self-installing fixtest,
Charles Anderson wrote:
ADSM _should_ be able to backup a read only filesystem as adsm ( tsm, whatever )
shouldn't be writing to the filesystem to back it up ( that's what the adsm server is
for ), unless you're executing dsmc from withing that filesystem, at which point you
would be
33 matches
Mail list logo
