ADSM-L

Re: Newbie Question cluster backups

2006-09-25 12:46:27
Subject: Re: Newbie Question cluster backups
From: Robben Leaf <robben.leaf AT USBANK DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 25 Sep 2006 09:24:45 -0500
The Windows B/A Client manual has a good description on how to do this in
one of its appendices.

In general terms, you need to define a separate node name for the data to
be backed up from the new drive; get an option file on the new drive; set
up services (TSM Schedules, Client Acceptor, and Remote Agent) on EACH of
the physical hosts that the vnode can fail over to, and set up cluster
services in Windows' Cluster Administrator to control those services.

Some gotchas: For clustered services, make sure you choose an HTTP port and
TCP client port that are different from those used by all other nodes
within the cluster. Make sure the option file has only the drives for that
vnode in its Domain statement. The set of services on the different
physical hosts for that vnode must have IDENTICAL names (i.e. the service
called "TSM Scheduler: VNODENAME" must be named exactly the same way on
every host that that vnode can fail over to). The local services on each
physical host for the vnode must be set to Manual, not Automatic - they
will be controlled by the cluster services. The most straightforward way to
get the password validated for the services on each physical host is to
fail the vnode over to that physical host before you create the services.

Hope this helps - good luck!

Robben



             "Matthews, Gary"
             <gary.matthews@LO
             GICACMG.COM>                                               To
             Sent by: "ADSM:           ADSM-L AT VM.MARIST DOT EDU
             Dist Stor                                                  cc
             Manager"
             <[email protected]                                     Subject
             .EDU>                     [ADSM-L] Newbie Question cluster
                                       backups

             09/25/2006 07:50
             AM


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






Hi,

Have a question about setting a backup. I've inherited a Tivoli backup
solution and am very slowly getting to grips with it ( have a NetBackup
background) and now need help in setting up a new backup. We've a sql
cluster wdccdb01 which has been set up backup the local drives via each
side of the cluster separately (wdccsq01/02) - The clustered disk
resource hold the SQL database and that backs up the SQL agent, so
there's a dsm.opt file  in TSM/baclient locally  for each node  and a
dsm.opt file in TSM/TDPsql locally on each client. Now we've just put on
another drive to the cluster( non SQL) - First time for me to set up a
new backup -  What's the best way to set this backup up

Cheers

Gary


This e-mail and any attachment is for authorised use by the intended
recipient(s) only. It may contain proprietary material, confidential
information and/or be subject to legal privilege. It should not be copied,
disclosed to, retained or used by, any other party. If you are not an
intended recipient then please promptly delete this e-mail and any
attachment and all copies and inform the sender. Thank you.




------------------------------------------------------------------------------
Electronic Privacy Notice. This e-mail, and any attachments, contains 
information that is, or may be, covered by electronic communications privacy 
laws, and is also confidential and proprietary in nature. If you are not the 
intended recipient, please be advised that you are legally prohibited from 
retaining, using, copying, distributing, or otherwise disclosing this 
information in any manner. Instead, please reply to the sender that you have 
received this communication in error, and then immediately delete it. Thank you 
in advance for your cooperation.
==============================================================================

<Prev in Thread] Current Thread [Next in Thread>