Re: Automating RMAN Backup Through TSM
Gus, I wanted to let you know that my scheduling configuration is working well... Thank you very much for the solution you forwarded to me. Brian Jin Bae Chi [EMAIL PROTECTED]@VM.MARIST.EDU on 10/30/2002 12:20:30 PM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by:ADSM: Dist Stor Manager [EMAIL PROTECTED] To:[EMAIL PROTECTED] cc: Subject:Re: Automating RMAN Backup Through TSM Brian, I had the same problem and folks from this group helped me on that. Here is what I got from Neil. I followed what he said and it's working! Hope this help. Gus --- I have here our preferred method for starting Rman with the TSM Scheduler: When using the TSM scheduler to automate the TDP Oracle backups, the differences in how these two clients work must be taken into account. - The scheduler runs as root and would need passwordaccess generate. - The TDP Oracle backup runs as an Oracle user and need passwordaccess prompt. Since the TDP client requires passwordaccess prompt, automating the TSM scheduler process on the client machine often encounters various issues. The following steps should assist with clarifying how to setup this type of configuration for a working environment. To setup the TSM Scheduler for the TDP Oracle node, it is critical that the password for the node on the TSM Server be set so that the password will not expire. Then setup the TDP Oracle to use PasswordAccess prompt and setup the TSM Scheduler (for the tdp oracle backup) to use PasswordAccess generate. To use only one dsm.sys file, ensure there is a symbolic link to this single dsm.sys file so it can be seen from the API directory (/opt/tivoli/tsm/client/api/bin) and the TDP can find and use this dsm.sys. In this one dsm.sys file, there will normally be more than one ServerName stanza when using the TDP Oracle on the same machine. One ServerName stanza for the filesystem backups and another ServerName stanza for the TDP Oracle backups (which need passwordaccess prompt). To assist with setting up the TSM Scheduler for the TDP Oracle node, you would need to create a third ServerName stanza in this dsm.sys file. In general, the dsm.sys file would be similar to the following: servername TSMbackup COMMMETHOD tcpip TCPServeraddressxxx.xxx.xxx.xxx TCPPORT1500 NODENAME Client PASSWORDACCESSgenerate servername TSMOracle COMMMETHOD tcpip TCPServeraddress xxx.xxx.xxx.xxx TCPPORT1500 PASSWORDACCESSprompt servername TDPSched COMMMETHOD tcpip TCPServeraddressxxx.xxx.xxx.xxx TCPPORT1500 NODENAME TDPNode PASSWORDACCESSgenerate You would have three dsm.opt files. One for the Backup/Archive client that would normally be located in the /opt/tivoli/tsm/client/ba/bin directory. Based on the dsm.sys example above, this would contain the line: servername TSMbackup There would be a second dsm.opt file (which could have a different filename, such as dsmoracle.opt) for the TDP for Oracle. Based on the dsm.sys example this user option file for the Oracle client would contain the line: servername TSMOracle and would have passwordaccess prompt. There would be a third dsm.opt file (which could have a different filename, such as dsmsched.opt) for the TDP for Oracle scheduler. Based on the dsm.sys example this user option file for the Oracle client would contain the line: servername TDPSched and would have passwordaccess generate and have the NodeName for the TDP Oracle client specified. Environment variables would need to be utilized with the Oracle backup to point to the user option file. This would be specified in the TDPO_OPTFILE with the DSMI_ORC_CONFIG variable. For example: DSMI_ORC_CONFIG /opt/tivol/tsm/client/oracle/bin/dsmoracle.opt When starting the TSM Scheduler for the TDP Oracle backups, you will need to use the -SErvername parameter and specify which stanza should be used. Based on the example dsm.sys the scheduler command would be such as: dsmc sched -SE=TDPSched For the TDP backup, the script file for the command schedule backup will be launched by the scheduler daemon. Then within the command script launch the RMAN backup script. Regards, Neil Rasmussen Software Development TDP for Oracle [EMAIL PROTECTED] Jin Bae Chi (Gus) System Admin/Tivoli Data Center 614-287-5270 614-287-5488 Fax [EMAIL PROTECTED] [EMAIL PROTECTED] 10/30/02 11:13AM Hi All: I'm currently running my TDP for Oracle backup manually from a UNIX prompt. I'd like to automate this through TSM. I 'm confused. Has anyone automated this process? If so, I'd like to hear some suggestions or recommendations on setting it up. OS: AIX 4.3.3 TSM: 4.2.1.10 TDP: 2.2.1 Thanks, Brian
Re: TDP for Oracle
Hi Joseph, I'm not so sure they can run concurrently. I have two versions of Oracle on a server with one being 32 bit and the other being 64 bit. Someone may be able to tell you how to get around the link of libobk.a to /usr/lib/libobk.a, but I think that's part of the problem. Originally, I tested backing up the 32 bit version and then I proceeded to test the 64 bit version. My 64 bit backup wouldn't work until I set the link of libobk.a properly. If someone knows of a way to do it, I'd really be interested in knowing Brian Wholey, Joseph (TGA\\MLOL) [EMAIL PROTECTED]@VM.MARIST.EDU on 11/11/2002 09:48:24 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by:ADSM: Dist Stor Manager [EMAIL PROTECTED] To:[EMAIL PROTECTED] cc: Subject:TDP for Oracle Can the 32 bit verstion of TDP co-exist with the 64 bit version. i.e. can they run concurrently on the same client?
Re: Automating RMAN Backup Through TSM
Hello Christy,
Please verify that you have /usr/lib in your search path. Also, what is
$LD_LIBRARY_PATH set to? One step you may want to retry is the relink of
RMAN and TDP
for Oracle. (make -f ins_rdbms.mk LLIBMM=/usr/lib/libobk.a ioracle)
Also, one thing that caused me problems was that I accidentally installed
32bit TDP for Or-
acle when I should've installed 64bit TDP for Oracle.
I noticed that you do not have an ENV setting in your backup script. I
would add this to your RMAN script to set the TDPO_OPTFILE variable. I
have an entry like
this --- 'ENV
=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
Let me know how you're doing. As of now, I'll be in the office until
9:00 or 10:00 p.m., EST.
Brian
Christy Wu, T.F. [EMAIL PROTECTED]@VM.MARIST.EDU on 11/06/2002
10:37:27 AM
Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED]
Sent by:ADSM: Dist Stor Manager [EMAIL PROTECTED]
To:[EMAIL PROTECTED]
cc:
Subject:Re: Automating RMAN Backup Through TSM
Brian,
I did all steps in the TDPO setup guide. As to the libobk.a, I've linked it
to /usr/lib/libobk.a which in turn pointing to the library file of TSM.
Chris
- Original Message -
From: Brian Dade [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, November 04, 2002 11:28 PM
Subject: Re: Automating RMAN Backup Through TSM
Hello Christy,
This sounds like an error that I had prior to getting my backup to save
to
tape. Have you verified that you're using the correct library file,
libobk.a ?
Brian
Christy Wu, T.F. [EMAIL PROTECTED]@VM.MARIST.EDU on 10/30/2002
10:48:58 PM
Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED]
Sent by:ADSM: Dist Stor Manager [EMAIL PROTECTED]
To:[EMAIL PROTECTED]
cc:
Subject:Re: Automating RMAN Backup Through TSM
Hi Brian,
I have similar setup to your but unfortunately not able to get the rman
backup to tape. I tried to isolate the problem without TSM by simply
using
rman to backup to an internal 4mm tape drive but get an error that unable
to
initialize the subsystem (SBT) layer. Is there any configuration need to
be
specified in using the tape device?
Bypass the TSM and use the native rman command to backup to an internal
4mm
tape drive, I used following:
rman target / nocatalog
run {
allocate channel t1 type 'sbt_tape';
backup tablespace tools;
}
I expect the command to backup to tape, but it failed with the error I
stated above. Any configuration I need to do with 'sbt_tape' under
Oracle?
Hope you can give me some hints here. Thanks.
Chris
- Original Message -
From: Brian Dade [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, October 31, 2002 12:13 AM
Subject: Automating RMAN Backup Through TSM
Hi All:
I'm currently running my TDP for Oracle backup manually from a UNIX
prompt.
I'd like to automate this through TSM. I 'm confused. Has anyone
automated this process? If so, I'd like to hear some suggestions or
recommendations on setting it up.
OS: AIX 4.3.3
TSM: 4.2.1.10
TDP: 2.2.1
Thanks,
Brian
Re: Automating RMAN Backup Through TSM
Hello Christy,
This sounds like an error that I had prior to getting my backup to save to
tape. Have you verified that you're using the correct library file,
libobk.a ?
Brian
Christy Wu, T.F. [EMAIL PROTECTED]@VM.MARIST.EDU on 10/30/2002
10:48:58 PM
Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED]
Sent by:ADSM: Dist Stor Manager [EMAIL PROTECTED]
To:[EMAIL PROTECTED]
cc:
Subject:Re: Automating RMAN Backup Through TSM
Hi Brian,
I have similar setup to your but unfortunately not able to get the rman
backup to tape. I tried to isolate the problem without TSM by simply using
rman to backup to an internal 4mm tape drive but get an error that unable
to
initialize the subsystem (SBT) layer. Is there any configuration need to be
specified in using the tape device?
Bypass the TSM and use the native rman command to backup to an internal 4mm
tape drive, I used following:
rman target / nocatalog
run {
allocate channel t1 type 'sbt_tape';
backup tablespace tools;
}
I expect the command to backup to tape, but it failed with the error I
stated above. Any configuration I need to do with 'sbt_tape' under Oracle?
Hope you can give me some hints here. Thanks.
Chris
- Original Message -
From: Brian Dade [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, October 31, 2002 12:13 AM
Subject: Automating RMAN Backup Through TSM
Hi All:
I'm currently running my TDP for Oracle backup manually from a UNIX
prompt.
I'd like to automate this through TSM. I 'm confused. Has anyone
automated this process? If so, I'd like to hear some suggestions or
recommendations on setting it up.
OS: AIX 4.3.3
TSM: 4.2.1.10
TDP: 2.2.1
Thanks,
Brian
Automating RMAN Backup Through TSM
Hi All: I'm currently running my TDP for Oracle backup manually from a UNIX prompt. I'd like to automate this through TSM. I 'm confused. Has anyone automated this process? If so, I'd like to hear some suggestions or recommendations on setting it up. OS: AIX 4.3.3 TSM: 4.2.1.10 TDP: 2.2.1 Thanks, Brian
Re: Automating RMAN Backup Through TSM
Gus, This will be a big relief. Hopefully, it will work just as well for me too. Thank you very much for the information. Brian Jin Bae Chi [EMAIL PROTECTED]@VM.MARIST.EDU on 10/30/2002 12:20:30 PM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by:ADSM: Dist Stor Manager [EMAIL PROTECTED] To:[EMAIL PROTECTED] cc: Subject:Re: Automating RMAN Backup Through TSM Brian, I had the same problem and folks from this group helped me on that. Here is what I got from Neil. I followed what he said and it's working! Hope this help. Gus --- I have here our preferred method for starting Rman with the TSM Scheduler: When using the TSM scheduler to automate the TDP Oracle backups, the differences in how these two clients work must be taken into account. - The scheduler runs as root and would need passwordaccess generate. - The TDP Oracle backup runs as an Oracle user and need passwordaccess prompt. Since the TDP client requires passwordaccess prompt, automating the TSM scheduler process on the client machine often encounters various issues. The following steps should assist with clarifying how to setup this type of configuration for a working environment. To setup the TSM Scheduler for the TDP Oracle node, it is critical that the password for the node on the TSM Server be set so that the password will not expire. Then setup the TDP Oracle to use PasswordAccess prompt and setup the TSM Scheduler (for the tdp oracle backup) to use PasswordAccess generate. To use only one dsm.sys file, ensure there is a symbolic link to this single dsm.sys file so it can be seen from the API directory (/opt/tivoli/tsm/client/api/bin) and the TDP can find and use this dsm.sys. In this one dsm.sys file, there will normally be more than one ServerName stanza when using the TDP Oracle on the same machine. One ServerName stanza for the filesystem backups and another ServerName stanza for the TDP Oracle backups (which need passwordaccess prompt). To assist with setting up the TSM Scheduler for the TDP Oracle node, you would need to create a third ServerName stanza in this dsm.sys file. In general, the dsm.sys file would be similar to the following: servername TSMbackup COMMMETHOD tcpip TCPServeraddressxxx.xxx.xxx.xxx TCPPORT1500 NODENAME Client PASSWORDACCESSgenerate servername TSMOracle COMMMETHOD tcpip TCPServeraddress xxx.xxx.xxx.xxx TCPPORT1500 PASSWORDACCESSprompt servername TDPSched COMMMETHOD tcpip TCPServeraddressxxx.xxx.xxx.xxx TCPPORT1500 NODENAME TDPNode PASSWORDACCESSgenerate You would have three dsm.opt files. One for the Backup/Archive client that would normally be located in the /opt/tivoli/tsm/client/ba/bin directory. Based on the dsm.sys example above, this would contain the line: servername TSMbackup There would be a second dsm.opt file (which could have a different filename, such as dsmoracle.opt) for the TDP for Oracle. Based on the dsm.sys example this user option file for the Oracle client would contain the line: servername TSMOracle and would have passwordaccess prompt. There would be a third dsm.opt file (which could have a different filename, such as dsmsched.opt) for the TDP for Oracle scheduler. Based on the dsm.sys example this user option file for the Oracle client would contain the line: servername TDPSched and would have passwordaccess generate and have the NodeName for the TDP Oracle client specified. Environment variables would need to be utilized with the Oracle backup to point to the user option file. This would be specified in the TDPO_OPTFILE with the DSMI_ORC_CONFIG variable. For example: DSMI_ORC_CONFIG /opt/tivol/tsm/client/oracle/bin/dsmoracle.opt When starting the TSM Scheduler for the TDP Oracle backups, you will need to use the -SErvername parameter and specify which stanza should be used. Based on the example dsm.sys the scheduler command would be such as: dsmc sched -SE=TDPSched For the TDP backup, the script file for the command schedule backup will be launched by the scheduler daemon. Then within the command script launch the RMAN backup script. Regards, Neil Rasmussen Software Development TDP for Oracle [EMAIL PROTECTED] Jin Bae Chi (Gus) System Admin/Tivoli Data Center 614-287-5270 614-287-5488 Fax [EMAIL PROTECTED] [EMAIL PROTECTED] 10/30/02 11:13AM Hi All: I'm currently running my TDP for Oracle backup manually from a UNIX prompt. I'd like to automate this through TSM. I 'm confused. Has anyone automated this process? If so, I'd like to hear some suggestions or recommendations on setting it up. OS: AIX 4.3.3 TSM: 4.2.1.10 TDP: 2.2.1 Thanks, Brian
RMAN Sbtape Error
Hi,
I'm running AIX v4.3.3 and TDP v2.2.0 for an Oracle v8.1.7 database client. I
verified that I'm using the correct libobk.a. Has anyone encountered the
following error during execution of their backup script?
run {
allocate channel t1 type 'sbt_tape' parms
'ENV=(TDPO_OPTFILE=
)';
backup
filesperset 5
format 'df_%t_%s_%p'
(database);
release channel t1;
RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-00571: ===
RMAN-00569: === ERROR MESSAGE STACK FOLLOWS ===
RMAN-00571: ===
RMAN-03007: retryable error occurred during execution of command: allocate
RMAN-07004: unhandled exception during command execution on channel t1
RMAN-10035: exception raised in RPC: ORA-19554: error allocating device, device
type: SBT_TAPE, device name:
ORA-19557: device error, device type: SBT_TAPE, device name:
ORA-27000: skgfqsbi: failed to initialize storage subsystem (SBT) layer
ORA-19511: Unknown SBT error code = 0, errno = 0
RMAN-10031: ORA-19624 occurred during call to DBMS_BACKUP_RESTORE.DEVICEALLOCATE
Thanks in Advance!
Brian
Re: RMAN Sbtape Error
Thanks for bringing it to my attention. Brian Clarence Beukes [EMAIL PROTECTED] on 07/30/2002 07:31:01 PM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc:(bcc: Brian Dade/DutyFreeAmericas) Subject: Re: RMAN Sbtape Error ENV=(TDPO_OPTFILE= This paramater should include the fully qualified path of the TDP options file. Clarence Beukes Advisory IT Specialist - Tivoli Certified Consultant Geomar SSO Mid Range and Application Support Discipline Location: IBM Park Sandton, IA2G Tel: +27 (0) 11 302-6622 Cell: +27 (0) 82 573 5665 E-mail: [EMAIL PROTECTED]
E-mail Notification, Backup Complete
I'm running TSM v4.2.1.10 on AIX v4.3.3. I'd like to send e-mail to the computer operators so they know when they can log on to continue their nightly processing. Any ideas? Thanks, Brian
Re: dsmserv.opt
What platform are you on? AIX? Burak Demircan [EMAIL PROTECTED] on 04/19/2002 06:15:17 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc:(bcc: Brian Dade/DutyFreeAmericas) Subject: dsmserv.opt Hi, Does anybody have original dsmserv.opt file for version 4.2? If yes could you send it to me. Regards, Burak
Errors Using EBU For v7.3.4 Database On AIX 4.3.3
Hi, I have an oracle database v7.3.4. I'm also using EBU v2.2 and TDP v2.1.10. I'm pretty sure that I have all of my environment variables set correctly, including $NSR_CLIENT for the oracle id. Although I opened a tar with Oracle Support and I used their Metalink website to get information about NSR_CLIENT and adding oracle as an admin, they're not responding to my questions. I also added the oracle id as an admin user in the Tivoli Server Administration interface. Can anyone tell me why I get the following errors during execution of my backup script? oracle@global: ./ebu backup_WDFATST Oracle7 Enterprise Backup Utility: Release 2.2.0.5.0 - Production on Fri Apr 12 08:44:23 2002 Copyright (c) Oracle Corporation 1979, 1996. All rights reserved. CORE Version 3.5.4.0.0 - Production NLSRTL Version 3.2.4.0.0 - Production ORACLE_HOME = /oracle/product/7.3.4 System name:AIX Node name: global Release:3 Version:4 Machine:000936494C00 Tape API: Release 1.1 Tape Management Software: Release 9.9.9.9 Vendor API: DISK Api (Oracle internal only) backing up to /usr/tivoli/tsm/client /api/bin BACKUP job started with pid=50834 on 12-APR-02 08:44 Starting parsing of command script backup_WDFATST backup offline database db_name=WDFATST archivelog=none parallel=2 log=/oracle/product/7.3.4/obackup/log/full-cold-backup.log Ending parsing of command script Starting Catalog Database verification Catalog Database verified Ending Catalog Database verification Starting Instance Manager verification Found Instance Manager (brd) process running with pid = 76940 Ending Instance Manager verification Starting Target Database state verification Connecting to Target Database ORACLE_SID: WDFATST ORACLE_HOME: /oracle/product/7.3.4 DBNAME: WDFATST Username: internal Connected to idle instance. Issuing Statement: STARTUP PFILE=?/dbs/init@.ora DBA MOUNT; Database mounted. Target database state OK Ending Target Database state verification Database Backup job 41 started on 12-APR-02 08:44 Starting Database configuration verification No registration update is needed Target Database information is up to date in catalog Ending Database configuration verification Starting Database job building, involved files are: Parameter file /oracle/product/7.3.4/dbs/initWDFATST.ora Control file /oracle/accting/local/control1 Datafile /wdfa01/system01.dbf Datafile /wdfa01/system02.dbf Datafile /wdfa01/system03.dbf Datafile /wdfa01/system04.dbf Datafile /wdfa03/temp01.dbf Datafile /wdfa01/tools01.dbf Datafile /wdfa02/users01.dbf Datafile /wdfa02/users02.dbf Datafile /wdfa06/users03.dbf Datafile /wdfa05/apd01.dbf Datafile /wdfa01/apd02.dbf Datafile /wdfa01/apd03.dbf Datafile /wdfa06/apx01.dbf Datafile /wdfa03/ard01.dbf Datafile /wdfa02/arx01.dbf Datafile /wdfa03/fad01.dbf Datafile /wdfa02/fax01.dbf Datafile /wdfa03/fndd01.dbf Datafile /wdfa06/fndx01.dbf Datafile /wdfa03/glbald01.dbf Datafile /wdfa02/glbald02.dbf Datafile /wdfa05/glbalx01.dbf Datafile /wdfa01/glbalx02.dbf Datafile /wdfa01/gld01.dbf Datafile /wdfa06/gld02.dbf Datafile /wdfa01/gld03.dbf Datafile /wdfa02/gljed02.dbf Datafile /wdfa04/gljed01.dbf Datafile /wdfa05/gljed03.dbf Datafile /wdfa06/gljex01.dbf Datafile /wdfa05/gljex02.dbf Datafile /wdfa04/gltempd01.dbf Datafile /wdfa05/gltempx01.dbf Datafile /wdfa02/glx01.dbf Datafile /wdfa05/glx02.dbf Datafile /wdfa04/glx03.dbf Datafile /wdfa04/hrd01.dbf Datafile /wdfa05/hrx01.dbf Datafile /wdfa03/pod01.dbf Datafile /wdfa06/pox01.dbf Datafile /wdfa04/ramsd01.dbf Datafile /wdfa04/ramsd02.dbf Datafile /wdfa06/ramsd03.dbf Datafile /wdfa06/ramsx01.dbf Datafile /wdfa03/rgd01.dbf Datafile /wdfa06/rgx01.dbf Datafile /wdfa04/shrd01.dbf Datafile /wdfa04/shrd02.dbf Datafile /wdfa05/shrx01.dbf Datafile /wdfa05/shrx02.dbf Datafile /wdfa02/discvr01.dbf Datafile /wdfa02/rbs2_01.dbf Datafile /wdfa03/rbs2_02.dbf Datafile /wdfa02/rbs2_03.dbf Datafile /wdfa06/rbs2_04.dbf Ending Database job building Starting Shutdown of target database for offline backup Issuing Statement: SHUTDOWN IMMEDIATE; Database dismounted. Database shutdown. Ended Shutdown of target database for offline backup Starting backup to tape Number of parallel I/O streams: 2 Oracle block size: 8192 bytes Disk input/output size: 131072 bytes Maximum tape I/O size: 262144 bytes Buffer size per I/O stream: 1048576 bytes Starting BFS 18821018615472 on
TDP For Oracle, EBU Install
Hello, I'd like to know if a manual still exists for installing TDP For Oracle using EBU instead of RMAN (AIX v4.3.3 OS)? I need to set this up for an old Oracle v7.3.4 database. Everything I've located refers to RMAN. I found a large ADSM manual, but it doesn't discuss anything about an AIX install. Thanks in advance! Brian
