Hi
To start with, they are running a configuration that is not supported by
either Tivoli nor IBM.
Second of all, running this configuration will result in inconsistent data,
and you could question whether or not a complete a full restore of the
system.
The problem you have to describe to your customer, is that there is a large
chance, that they won't be able to restore the cluster environment in case
of a disaster. Therefore, it is in their own interest to move over to the
supported configuration a.s.a.p.
This is not a question of which way to configure the clustered environment,
but instead of moving to the only way that will work.
Best Regards
Daniel Sparrman
-----------------------------------
Daniel Sparrman
Exist i Stockholm AB
Bergk�llav�gen 31D
192 79 SOLLENTUNA
V�xel: 08 - 754 98 00
Mobil: 070 - 399 27 51
"Warren, Matthew
James" To: [EMAIL PROTECTED]
<matthewjames.warre cc:
[EMAIL PROTECTED]> Subject: Re: versioning / expiring
/ multiple
Sent by: "ADSM: backups under same nodename
Dist Stor Manager"
<[EMAIL PROTECTED]
DU>
2002-01-21 13:22
Please respond to
"ADSM: Dist Stor
Manager"
We know the correct way to be backing up the cluster. The customer did not
implement it this way, but we are recommending them to do so.
Before they switch from their current set-up to how we are recommending
they
backup the cluster (With 2 TSM environments on each machine, one for local
disk, the other for shared disk) they would like to know exactly what risk
they are runing with their current setup.
Matt.
-----Original Message-----
From: Mike Yager [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 18, 2002 4:27 PM
To: [EMAIL PROTECTED]
Subject: Re: versioning / expiring / multiple backups under same nodename
Exactly, while im not doing TSM on my clusters (yet) Daniel is correct.
In my MS-clustered environment, I have the following entries in DNS
SRV01
SRV02
CLUSTER1
DB2-01
the last 2 are a "logical" name of the cluster resource. This allows the
"resource" to be managed separately from the physical machine or other
"resources" and/or physical machine.
I would caution you to be careful as you indicated the resources DO show up
as being owned by the controlling node. IE DON'T back it up via that
attachment even if you can see it as when it changes to a new node you will
have a different name as you mentioned....
Please keep us posted as I'll be headed down this road shortly.
-mike
?--
The description you gave tells me there is something wrong with your
configuration.
Normally when you set up TSM to handle clustering, you have one TSM
nodename for each clusternode(M1,M2,M3). These nodenames are only for
backing up local files on the node. Then you have either one nodename for
each clusterresource, or one nodename for all clusterresources. You also
have to bind the nodename to the clusterresource, so that the TSM service
that handles the cluster nodename, moves with the clusterresource.
---------------------------------------------
Michael Yager
IBM Global Services
(919)382-4808
