ADSM-L

Re: TSM Scheduler in a Solaris TDP for Oracle Environment

2001-12-10 09:47:27
Subject: Re: TSM Scheduler in a Solaris TDP for Oracle Environment
From: Bill Mansfield <WMansfield AT SOLUTIONTECHNOLOGY DOT COM>
Date: Mon, 10 Dec 2001 08:44:48 -0600
One needs to create 2 stanzas in the dsm.sys file, one for regular backups,
one for Oracle.  Each "Servername" line starts a new stanza.  You'll also
need to set a nodename if you're sending the Oracle data to a different
domain.

dsm.sys:
           Servername         Aserver
           TCPPort            1500
           TCPServeraddress   Aserver
           passwordaccess generate
           nodename    client
           ...
           Servername      Aserver_Orc
           TCPPort            1500
           TCPServeraddress   Aserver
           passwordaccess  prompt
           nodename   client_orc
           ...

In Oracle TDP dsm.opt file:
              Servername   Aserver_Orc

In the regular dsm.opt file:
              Servername   Aserver
_____________________________
William Mansfield
Senior Consultant
Solution Technology, Inc




                    Vic Marshall
                    <vic.marshall@PHOE       To:     ADSM-L AT VM.MARIST DOT EDU
                    NIXSM.COM>               cc:
                    Sent by: "ADSM:          Subject:     TSM Scheduler in a 
Solaris TDP for Oracle Environment
                    Dist Stor Manager"
                    <[email protected].
                    EDU>


                    12/10/2001 04:31
                    AM
                    Please respond to
                    "ADSM: Dist Stor
                    Manager"






Greetings TSM'ers,

I have a question regarding using the TSM scheduler in an Oracle TDP
environment (Solaris7) the vital statistics are:

TSM Server version 4.1.4 on Windows NT4, SP6A.
TSM Client version 4.2 on Solaris V2.7.
TDP for Oracle V2.2 for Solaris.

The TDP requires PASSWORDACCESS         PROMPT to be set in the options
file, to enable the scheduler to backup the oracle data via the TDP.

This now has the knock on effect of stopping the schedules for all other
filespace backups on that particular server, as PASSWORDACCESS must be set
to GENERATE.

I can setup a cron command to backup all non-oracle filespaces, but i would
rather use the built in TSM scheduler if possible.

Surely someone else has hit upon this problem,

Thanks in advance,

Vic


http://www.phoenixitgroup.com
******************Internet Email Confidentiality Footer*******************

Phoenix IT Group Limited is registered in England and Wales under company
number 3476115.  Registered Office: Technology House, Hunsbury Hill Avenue,
Northampton, NN4 8QS

Opinions, conclusions and other information in this message that do not
relate to the official business of our firm shall be understood as neither
given nor endorsed by it.

No contracts may be concluded on behalf of our firm by means of email
communications.

Confidentiality: Confidential information may be contained in this message.
If you are not the recipient indicated (or responsible for delivery of the
message to such person), you may not take any action based on it, nor
should
you copy or show this to anyone; please reply to this email and highlight
the error to the sender, then delete the message from your system.

Monitoring of Messages: Please note that we reserve the right to monitor
and
intercept emails sent and received on our network.
Warning:  Internet email is not 100% secure. We ask you to understand and
observe this lack of security when emailing us. We do not accept
responsibility for changes made to this message after it was sent

Viruses: Although we have taken steps to ensure that this email and any
attachments are free from any virus, we advise that in keeping with good
computing practice the recipient should ensure they are actually virus
free.
<Prev in Thread] Current Thread [Next in Thread>