Re: TDP for SAP R/3 on Oracle and MS Cluster

TDP for R/3 with Oracle works fine in a MS Cluster.  Go through Appendix F
(Configuring the Backup/Archive Client in a Microsoft Cluster Server
environment) in the Windows Backup/Archive Client Installation and Users
Guide to get information that is unique to clustering.

Here's a generic example of the process:

In our example cluster (NodeA and NodeB)  there are 3 resource groups, each
have their own IP address:
1.  clusgrp - Q: drive for cluster quorum disk
2.  dbgrp - G, H, I, J, L drives for Oracle database files, control files,
logs, etc.
3.  sapgrp - K drive for SAP instance

There will be 6 TSM node names total:
NodeA - Regular nonclustered B/A client for C: drive
NodeB - Regular nonclustered B/A client for C: drive
clusgrp - Regular B/A client for Quorum drive
dbgrp - Regular B/A client for Oracle DB drives
sapgrp - Regular B/A client for SAP drives
SAP -  TDP for R/3 client

Make sure all resource groups are owned by Node A of the cluster then:
1.  Install TSM backup/archive client to default location.
2.  Install TDP for R/3 to default location.
3.  Setup 5 separate TSM options files, one for each resource group for the
regular B/A client (total of 3), one for the nonclustered drives (C:)
regular B/A client, and one for TDP for R3.
      -  Regular options file in default location (c:)
      -  clusgrp options file on Q:
      -  dbgrp options file on I:
      -  sapgrp options file on K:
      -  TDP for R/3 options file on K:
4.  The regular B/A client options file on C: should be configured as
normal, be sure to exclude all the clustered drive letters.
5.  Use the TSM wizard to setup TSM services for the nonclustered B/A
client on the C: drive.
6.  Setup all the options files.  For clustered and TDP options files,
these options are critical with regards to clustering:
      -  tcpclientaddress (should be address of cluster resource group)
      -  nodename (easy to make the same as the cluster resource group, use
any nodename for R3)
      -  passwordaccess generate
      -  clusternode yes
      -  httpport (must be unique for each options file, not needed for R3)
      -  tcpclientport (must be unique for each options file)
      - domain (only include the drives in the resource group)
      -  errorlogname
      -  schedlogname
      -  include/excludes to exclude database files,etc that are handled by
the TDP for R3
7.  Use dsmcutil to install TSM services (i.e. TSM client acceptor, TSM
Scheduler, etc., examples in Appendix F:) for all the cluster groups and
the TDP for R3.  Be sure to point to the correct options file for each.
8.  Fail everything over to node B:
9.  Install TSM backup/archive client to default location.
10.  Install TDP for R/3 to default location.
11.  The regular B/A client options file on C: should be configured as
normal, be sure to exclude all the clustered drive letters.
12.  Use the TSM wizard to setup TSM services for the nonclustered B/A
client on the C: drive.
13.  All the options files for clustered resource groups and TDP for R/3
should be visible since all drives are now owned by NodeB.
14.  Use dsmcutil to install TSM services just like in step 7.
15.  Setup the TSM services and password registry key replication in
Cluster Administrator so they will failover correctly (see Appendix F:
again)
16.  Test failover.  Make sure registry key is replicating the password
correctly.

Backups are scheduled as normal through TSM, although 6 nodes will be
scheduled to get a total backup of the complete cluster.


______________________________
John Monahan
Senior Consultant Enterprise Solutions
Computech Resources, Inc.
Office: 952-833-0930 ext 109
Cell: 952-221-6938
http://www.compures.com




             "Thomas Rupp,
             Vorarlberger
             Illwerke AG"                                               To
             <Thomas.Rupp@ILLW         ADSM-L AT VM.MARIST DOT EDU
             ERKE.AT>                                                   cc
             Sent by: "ADSM:
             Dist Stor                                             Subject
             Manager"                  TDP for SAP R/3 on Oracle and MS
             <[email protected]         Cluster
             .EDU>


             05/12/2003 03:11
             AM


             Please respond to
             "ADSM: Dist Stor
                 Manager"
             <[email protected]
                   .EDU>






Hi TSM-gurus,

Anyone using TDP for SAP R/3 on Oracle and a MS Cluster?
How did you install? How do you start a backup?
I couldn't find a reference for a MS cluster install in the docu,
ADSM-L archive or tivoli website.
I'm running SAP R/3 4.6C, TDP for R/3 3.1 and TSM 5.1 client.

Thanks in advance
Thomas Rupp
Vorarlberger Illwerke AG