Thank you Joseph,
While I only have one instance per machine for these particular customers, I
do have some others' that have 3-4 instances per machine that would like
Rman backups. Changing the filespace name to a sid is very good
suggestion.
I originally moved the tdpo and dsm files because they were linked and I
didn't want them confused with the BA client's files. I will break the link
and put them back in thier place so I can give this a try.
I have already made the oracle rman node their own separate policy and set
the mgmt class to 1-0-0-0. Different instances have different retention
policies (within Oracle). Each night I run backup, the backup script sets
these retention periods, then does crosschecks, and then deletes the expired
sets.
Thank you again for your help.
-----Original Message-----
From: Wholey, Joseph (IDS DM&DS) [mailto:joseph_wholey AT ML DOT COM]
Sent: Monday, February 09, 2004 6:21 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: TDPO configuration file locations
Jason,
It goes as follows. When initiating a TDP backup, the tdpo.opt file is
referenced. That calls the dsm.opt which in turn calls the dsm.sys.
The tdpo.opt and the dsm.opt should be in
/opt/tivoli/tsm/client/oracle/bin64. (just bin if you're not running 64 bit)
The dsm.sys has to be in the /opt/tivoli/tsm/client/api/bin64 directory. In
this directory Break the symlink to /usr/bin. Comment out the Inclexcl
statement. Change password access from generate to
prompt.
I also strongly recommend creating a seperate domain for your database
backups as does the manual. Set the management class to 1-0-0-0. You can
also set it as the default management class.
You should also consider changing the filespace name to something other than
adsmorc. In the event that you have multiple oracle instances on the same
client, it is much more managable when they each
have a unique name. e.g If the database gets "put to rest", you can simply
delete the filespace for that database. Not so easy if you have 3 or 4
databases all writing to filespace adsmorc. (you
set the filespace name in the tdpo.opt file). You will need to create a
unique tdpo.opt file for each database.
Regarding your question, when is the data going to expire. The answer is
NEVER until you run a deletion script.
Joe
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Harris, Jason (DIS)
Sent: Monday, February 09, 2004 5:42 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: TDPO configuration file locations
I use Tivoli Data Protection for Oracle 2.2.1, BA and API client 5.2.0 on
Oracle 9.2, Solaris 9. TSM is on Solaris 8.
When starting a TDPO channel, the tdpo.conf is referenced. Within
tdpo.conf, a dsm.opt is referenced. In documentation, filespace /adsmorc
must be bound to correct management class in the dsm.sys file or else the
backups will be attached to the policy's default management class. Does
anyone know where this dsm.sys should be ? Should it be in the same
directory as dsm.opt ? Should it be in the API directory ? TDPO directory
? BA directory ? Our backups are never expiring off of the TSM server,
the /adsmorc filespace keeps getting bigger and it should not.
Does anyone know how to find out which mgmt class TDPO backups are bound to
?
Any help would be greatly appreciated.
Jason Harris
Enterprise Business Solutions
Department of Information Services
Voice: (360) 725-5217
Pager: (360) 971-1091
============================================================================
==
If you are not an intended recipient of this e-mail, please notify
the sender, delete it and do not read, act upon, print, disclose,
copy, retain or redistribute it.
Click here for important additional terms relating to this e-mail.
<http://www.ml.com/email_terms/>
============================================================================
==
|
