There are next ways to backup Oracle databases using TSM:
1) using RMAN + TDPO + TSM Client to TSM server by periodic full backups and
incremental backups on other days;
2) using RMAN + DDBoost to Data Domain by periodic full backups and incremental
backups on other days with Data Domain de-dupli
My bad, all Oracle log files are backup objects to TSM unless a special archive
process is used.
I used the TDP to backup the log files straight to TSM, to reduce local disk
needs on the client.
The databases were sent to flat-file on the local disk.
However, the same logic should work for the l
Stefan,
While I prefer to use the rman design as depicted in the Oracle/TSM doco, here
is how I have done this in the past.
Tasks are script based, executed by cron, and use rman so the repository and
catalogs are maintained.
Logs are archived to TSM every 5-30 minutes depending on the system di
Thanks for your reply Rick this helps.
About this "Logs are archived to TSM every 5-30 minutes depending on the
system disk availability."
How does this work and is it really an archive or a backup of archive logs?
Do you just run a dsmc i on the directory that contains the oracle archive
logs, do
Found the problem.
Apparently the upgrade utility requires the account to access the tsm v5
server to be an actual login account. That is, you can ssh to the box as
that id and enter the ID and PWD of the account and get a shell. We had
tried rsh and ssh setups without pwd's (ssh with public/pri
Hi guy's,
A customer of ours is investigating cutting out the Oracle TDP for Oracle
v9 and replacing it with rman backups to disk that get picked up by the TSM
B/A client.
I am wondering if people here are doing this already.
I'm no Oracle or rman man but I wonder if you can create a workable
en
I has said . . .
> It can't find /usr/tivoli/tsm/upgrade/bin/dsmupgrd, which exists:
>:/home/root==>ls -ld /usr/tivoli/tsm/upgrade/bin/dsmupgrd
>-rwxr-xr-x1 root system 21221457 Oct 24 2011
> /usr/tivoli/tsm/upgrade/bin/dsmupgrd
I typed "" when I should have said "".
I think we have it right - the upgrade utilities are installed on the v5
server as you say.
>lpar A - tsm v5 db (source)
upgrade utilities installed
>lpar B - tsm v6 system (destination)
new v6 server
running dsmupgdx
successfully finds dsmserv.opt/dsmserv.dsk o
