You need to have bascially 3 installs on a cluster. One for each LOCAL node (to get 
local drives and system objects - registry) and one for the cluster name 
(clusternode=yes in dsm.opt file)
 
xyz Cluster - dsm.opt - located on both nodes (depends which one is active) and it has 
clusternode=yes in dsm.opt file.
 
node 1 and 2 - dsmlocal.opt - no metion of cluster, therefore will backup all local 
drives and registry
 
Create 2 backup schedules - one for dsmlocal.opt (local backups) which are set to 
automatic start.
                                          - one for dsm.opt (cluster name) which will 
be set to manual start
 
In cluster Admin, create a group for the dsm.opt service (ex; TSM Backup Schedule for 
Cluster) and set all nodes to be able to start it. (Make sure you create a seperate 
group in the Cluster Admin!!! - so if something goes wrong just with the Tivoli 
services it will not fail over the whole machine)
 
So what you will see on the TSM server is:
 
Node1
Node2
Cluster name for node1 and node2
(3 schedules for 2 boxes)
 
If you have any more questions email me.
 
Joe Cascanette

        -----Original Message----- 
        From: Daniel Sparrman [mailto:[EMAIL PROTECTED]] 
        Sent: Tue 3/19/2002 2:38 PM 
        To: [EMAIL PROTECTED] 
        Cc: 
        Subject: Re: Backing up NT server with print queues
        
        
        
        Hi
         
        If this is a Microsoft Cluster, you should have some kind of cluster group. 
However, it doesn't have to contain any disk resources. Disk resources are not 
necessary to use TSM cluster services. All you have to have is a MS cluster group. The 
client shouldn't be running at both cluster nodes at the same time, as this will 
endanger the possibility of restoring the cluster.
         
        Just install TSM client software on both nodes, add the necessary 
resources(See Using TSM in a clustered Windows environment), which should be attached 
to the correct cluster group
         
        Best Regards
         
        Daniel Sparrman

        -----------------------------------
        Daniel Sparrman
        Exist i Stockholm AB
        Bergk䀬lav䀧en 31D
        192 79 SOLLENTUNA
        V䀸el: 08 - 754 98 00
        Mobil: 070 - 399 27 51
        

        -----"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> wrote: -----
        
        To: [EMAIL PROTECTED]
        From: Bill Boyer <[EMAIL PROTECTED]>
        Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
        Date: 03/19/2002 07:28PM
        Subject: Backing up NT server with print queues
        
        We have a client with the following configuration:
        
        2 NT servers running in a cluster. These servers are for the entire
        enterprise's printer definitions. The run this in a cluster for fail-over
        capability, so the users can still print even if a server goes down.
        
        They want to be able to backup and recover this print server with TSM.Since
        I don't believe that there is any disk cluster resources, I would think that
        if we were to just run the B/A client on each server in the cluster and back
        it up, they would be able to re-create this environment in the event of a
        total site disaster.
        
        Anyone have ANY suggestions of how to back and/or recover in this scenerio?
        
        TIA,
        Bill Boyer
        DSS, Inc.
        



Reply via email to