Yes, that's true. They changed something in the database.
Mostly the upgradedb-command is issued automaticly when you install
the package. Otherwise run it manually
[EMAIL PROTECTED] 19/01 4:55
Dear all
i just upgrade TSM 4.1.0 to 5.1.5.0. I have some question
I shuold
Hi TSMers,
During scheduled backup few TSM clients are getting failed to take backup of
NTUSER.DAT/LOG files with return code 12, How can I avoid this, Please
kindly share your thoughts.
TSM server 5.1.7.0, TSM clients 5.1.x and 5.2.x.
01/18/04 18:56:44 ANE4987E (Session: 332401, Node:
Hi,
These files belong to the user profile of the SAPServiceBS user that is
a Windows user account used by a service currently running on your
nodes. I don't think that it is necessary to backup these files (at
least I usually exclude them). However you might try to use the Open
File Support, I
Hi,
Anyone useing NetApp´s Open System Snap Vault or an equivalent product that
replicate data to a datacenter where TSM runs backup?
And can discuss this offlist?
//Henrik
---
The information contained in this message may be
If the Install / Upgrade only took a few min to maybey 5min, it didnt upgrade the DB.
We went from 4.1.6 to 5.1.0 and the Software was upodated but we had to run the
upgrade DB manually per Tivoli Tech support. If you were to upgrade to 5.1.7 the
upgrade db does happen automgically, in
The last full backup is an active version. (just as the log-backups made afterwards)
Since you didn't make any full backups for a month, the TSM-server didn't see that
filespace for a month (...\data\...).
The last backup should be removed manually. (del filespace ...)
Jeroen
-Original
Actually correct syntax is:
exclude.dir *:\...\logcaster
Note that there should be no terminating slash at the end of the
specification.
Regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED]
Eric,
You cannot do this. You must log on to the TSM Server under the
NODENAME that performed the backups. The Direct Query
function in version 1 worked the same way.
It allowed you to query a specific server and database name,
but the NODENAME queried was always the one logged in to.
Data
I had this problem and have had to set max mount points to 999.
-Original Message-
From: Chandrashekar, C. R. (Chandrasekhar)
[mailto:[EMAIL PROTECTED]
Sent: Monday, January 19, 2004 3:37 AM
To: [EMAIL PROTECTED]
Subject: NTUSER.DAT/LOG getting failed during backup!
Hi TSMers,
During
I have good news, my problem is fixed. After having the issues with ADSM/TSM
restores, I tried to mitigate my issues by ftp'ing the data to another machine. After
the ftp, the checksums on the files did not match. I tried rcp and again, the
checksums did not match.
So, armed with that
From the Unix client manual:
complete
Restores the entire path, starting from the root, into the specified
directory. The
entire path includes all the directories except the file space name.
So the client is correctly.
The only way I can think of to accomplish what you want is to
One of our TSM clients is a Linux mail server with the message store
in the /var file system. About a month ago the mail store was switched
to local tape backup and excluded from TSM coverage using an exclude.dir
statement in the include/exclude file. Expiration processes have been
stuck in that
From: Andrew Raibeck [mailto:[EMAIL PROTECTED]
Actually correct syntax is:
exclude.dir *:\...\logcaster
Note that there should be no terminating slash at the end of the
specification.
You are correct, sir. Apologies.
--
Mark Stapleton ([EMAIL PROTECTED])
ANE4987E has been treated as RC 4 since the consistent return codes
feature was introduced in version 5.1. Check the client dsmsched.log and
dsmerror.log files for other error messages that might be contributing to
the RC 12.
Note that message ANS1448E was being issued at one time in the TSM
... please provide me with some links where can i read something (how to)
about upgrading TSM 5.1.8.0 and AIX 4.3.3 on TSM 5.2 and AIX 5.2, what to
do first , etc.
thanks in advance.
G.
Eric, the Server detected system error means that a problem occurred on
the TSM server. Check the TSM server activity log around the timeframe
when the ANS1301E message occurred to see what was going wrong.
Regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
We ran into a situation over the weekend that I have not seen mentioned
before, and I was hoping that someone might be able to shed some light on
what occurred.
TSM server has a 3583 library attached to it, connected via SAN. TSM has
been running for almost a year, using LAN-free backups for two
We are looking at an upgrade from 4.2.1.15 to some version that supports LTO
Gen 2 drives, which I hear is 5.2 or later...
I have the 5.0 media.
Are all the versions between 5.0 and 5.2.x downloadable, or is there another
step that requires a media set?
What is the oldest/most stable version
Hello. I'm a newer Tivoli user, all at 5.2.2, server on Linux ES 2.1-27 and
clients on AIX, Linux Win2003. I'm using a fiber connected IBM 3582 LTO-2
library with two LTO 2 drives for a few months now. All appears to be
working fine... backups (manual auto), restores, copies, archives all have
Hot Diggety! Jolliff, Dale was rumored to have written:
We are looking at an upgrade from 4.2.1.15 to some version that supports
LTO Gen 2 drives, which I hear is 5.2 or later...
Nope, LTO-2 support arrived in 5.1.6.1. There are *serious* problems with
some of the 5.1.6 tree to the point where
In article [EMAIL PROTECTED], Roger Nadler
[EMAIL PROTECTED] says:
Has anyone seen these errors before?
01/15/2004 01:30:57 sessSendVerb: Error sending Verb, rc: -50
01/15/2004 01:30:58 ANS1809W Session is lost; initializing session reopen
procedure.
Hello Roger
The return code -50 says that
21 matches
Mail list logo
