Hi Jorge!
You can do it in several steps if you want to, but there is no technical need
to do this. You can upgrade from 5.1 to 5.5 straight away without loosing
anything. The TSM upgradedb process is always downwards compatible.
To my knowledge, there is only one exception: when you're a
Hi All
I'm still running TSM 5.4 on Solaris and need to move to 5.5.
I have been looking at the Server/Client Compatibility matrix and am still a
little unclear what is supported. I have always been used to the idea that two
levels back for client code should be ok. Is this still the case?
I have read the act log of a scheduled backup and I found this
28/05/09 01:13:50 AM COT ANR0530W Transaction failed for session 195942 for
node _SQL (TDP MSSQL Win32) - internal server error detected. (SESSION:
195942)
28/05/09 01:33:52 AM COT ANE4993E (Session: 195941, Node: _SQL) TDP
On May 28, 2009, at 5:02 AM, admbackup wrote:
I have read the act log of a scheduled backup and I found this
28/05/09 01:13:50 AM COT ANR0530W Transaction failed for session
195942 for node _SQL (TDP MSSQL Win32) - internal server error
detected. (SESSION: 195942)
...
That may be a
Michele,
If you truly want one of your databases to get backed up first,
I recommend that you change your backup script to have separate
invocations of the backups, with the second invocation skipping
the one you backed up in the first invocation...
...i.e. something like this:
.
Two other things to verify:
1. Make sure MOUNTWaitfordata is set to yes.
Enter this command:
tdpsqlc set MOUNTWaitfordata=yes
2. Make sure that the program waits for tape mounts.
Add this option to the backup commands in the script file:
/MOUNTWait=Yes
If the ideas above do
Hi,
I did talk to them and we maybe can get the function to send direct SCSI
commands over the fiber. That mean we probably need to have the TSM Server
onsite but the library on a different location.
That can be an option maybe.
The customer have demand that the backup is on another site then
Why back it up at all? can't you just secure the copy the customer gets
every quarter and re-install if needed?
Steven Langdale
Global Information Services
EAME SAN/Storage Planning and Implementation
( Phone : +44 (0)1733 584175
( Mob: +44 (0)7876 216782
ΓΌ Conference: +44 (0)208 609 7400
Guys, I have some new info, with a slightly different problem, I hope it can
help:
This is the message in the rman output file:
RMAN-03009: failure of backup command on ORA_SBT_TAPE_1 channel at
05/28/2009 13:55:26
ORA-19506: failed to create sequential file, name=688053317_5871_1.arc,
parms=
Hi Steven,
I'm thinking about the same thing. And yes the data can be recreated but will
cost money because the data comes from another company.
Again, the time is not a problem. If it takes 50 days to recovery the data.
They will probably say OK for it. It is just that I don't wanna have a
Hi Matt,
Does the TSM Server activity log reveal anything - any of the associated
nodes attempting to log in by being denied?
Also, do you have any 'special characters' in the password? I understand
this has caused problems in the past.
And, of course - has this TDP client ever worked? Or has
Hi,
Sometimes(i do not why) i have the same problem.
Try put
passworddir /opt/tivoli/tsm/client/oracle/bin64
in the dsm.sys file
Kind regards
Jorge Garcia
Date: Thu, 28 May 2009 14:14:43 +0100
From: mlargedellt...@googlemail.com
Subject: Re: [ADSM-L] TDP Oracle failures
To:
When we went from 5.2.x to 5.4.x IBM told us to go to 5.3.0.0 first, then
5.4.0.0 then to the latest.
If you can, practice with a restored copy of your DB to make sure your chosen
method works and to make sure you can restore your DB just in case.
Andy Huebner
-Original Message-
From:
With my 5.5 client I can type in
dsm -virtualnode=anothernode
and log in with an administrator account and do what ever I want
With the 6.1 client when I type in
dsm -virtualnode=anothernode
and log in with an administrator account to do something, it wants to
log in again with the administrator
Hello All,
I want to take raw backup using TSM.My TSM server is on Linux x86_64
platform and Server version is 5.5.0.0 and client version is 5.5.0.1.I can
see the raw volumes in backup window and can backup some of them bur for
some others i get the error
Image backup of volume '/dev/sdeh'
I've been asked to exclude the Public Folder store from one of our Exchange
server backups. What I need to know is, do I do that that in the Exchange
dsm.opt, or in the excfull.cmd, changing the * to the stores separated by
commas. Either way, what would the syntax be for my naming, based on the
Hi Chip,
You cannot do this with your setup below.
Exchange will not allow you to perform FULL backups and
also exclude a database from the backup. It has to do with
the fact that the log files span all databases and
the normal log truncation that accompanies a FULL backup.
This is a
It is possible that RMAN backup and tdpoconf use different dsm.opt (and
different dsm.sys server stanzas). One way to check if the same stanza is
used:
1. Add an invalid option to dsm.sys stanza that you use. E.g
...
bad_option 1
..
2. Run tdpoconf showenv - should fail with ANS0220E (RC400)
The 5.3 clients still work. (Just like your 5.1 and 5.2 clients).
But they are not supported.
The term supported has 2 meanings - the colloquial meaning is that if the
software is supported, it works on the given platform.
Supported for Tivoli software means something more stringent - supported
Is there any way to list out all the file names from the filespace using
the TSM console?
AP
More than that, if you want to continue to use old clients, as I understand
it you are supposed to pay for the privilege. TSM is licensed, and the
licence is revoked when it goes out of support.
Its a two-pronged upgrade strategy... 1 you are unsupported on obsolete
levels and 2 its gonna cost
I've never heard that before.
TSM is licensed by processor core. If you are paying for the correct number
of cores, you can run any version of the client on the machine you want,
AFAIK. You're just on your own in terms of getting help with problems, if
that version is unsupported.
Where you get
Wanda
Maybe I have the wrong end of the stick but see
http://www-01.ibm.com/support/docview.wss?uid=swg21286063 This describes
the end of support for TSM 5.3
Towards the bottom it states
quote
TSM 5.3 customers who have operating systems that are no longer in
mainstream support by their
hi,check permissions on TSM.PWD file
and if oracle user can read the file
i put all of my tdpo nodes password files in /home/oracle
//
goran
On Thu, May 28, 2009 at 3:14 PM, Matthew Large
mlargedellt...@googlemail.com wrote:
Guys, I have some new info, with a slightly different problem, I
24 matches
Mail list logo
