I posted this a while back...in essence, each volume becomes it's own server
(i.e. client to tsm)....
===========================
Shannon,
We just started using cluster services, and there are a couple of caveats, but
it is very doable. I don't know how much of a difference it makes, but we are
on Netware 6.0.
One of the first things we had to do was edit the sys:nsn/user/smsrun.bas and
change the line:
nlmArray = Array("SMDR", "TSA600")
to
nlmArray = Array("SMDR", "TSA600 /cluster=off", "TSAPROXY")
You need to restart sms on the server or bounce it before it will take effect.
There is documentation on this on Novell's support site, but I am not sure if
it applies to 6.5 or not.
The second thing we did was to move away from the dsmc nlm and start using the
dsmcad nlm to handle the scheduling with the "managedservices webclient
schedule" line in the dsm.opt.
Finally, you will want to copy and load an instance of dmscad for each cluster
resource that you will be backing up and reflect these changes in your resource
load and unload scripts. i.e. for volume1 I make a copy of dsmcad.nlm called
dsmcad1.nlm and load and unload that with the resource.
This is a little simplified, but the other details can be found in the
documentation and the list archive web site. I think we even used google to
find some of this stuff, but it mostly brought us back to the list archive. If
you have any further questions, you can contact me directly.
Thanks,
Joel Lovelien
>>> MHayden AT EPA.STATE.IL DOT US 6/23/2004 11:03:55 AM >>>
Thank You, will let you know what works.
>>> riaanl AT SOURCECONSULTING.CO DOT ZA 6/23/2004 7:57:59 AM >>>
Hi Mark,
I ran into a similar problem on another <cough> backup software.
As this software isnt Novell Cluster aware (which ones are?) we had to
in
the end run the TSA with a /nocluster option.
BUT, before you rush out and do this, this presented its own problems
as the
disks are now presented to the backup software on both the physical
nodes.
We wrote a script that figured out which node was the active node and
only
backed that client up with a client side command line. (surely TSM will
have
somethign similar). This meant that if we wanted to do a restore it was
a
pain as we had to "hunt" between the 2 possible backup clients to find
the
correct date for restore.
If however only one of your clients will "always" be the active node
then
you should have less issues.
I hope this helps, slightly...
Regards,
Riaan
-----Original Message-----
From: Mark Hayden [mailto:MHayden AT EPA.STATE.IL DOT US]
Sent: Wednesday, June 23, 2004 2:38 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Novell Cluster (San volumes not getting backed up)
Sorry if this has been posted, but have not had time to read my
E-mails
for a while. We just upgraded our NetWare to 6.5 on all of our file
Servers. All is well, except the Sans on 4 NetWare Cluster Servers.
For
starters, we just back up these Servers the same as all our Novell
Servers. Tsm does not treat them as a Cluster. Problem, since we have
upgraded Novell to 6.5 TSM does not see the San volumes. I can add
these
volumes to the Object line in the schedule, but will only back up SYS
if
not. We are at 5.2.2.1 Server code, and 5.2.2 on the Novell
client....Has anyone ran into this???? Thank you for your help.
Thanks, Mark Hayden
Informations Systems Analyst
E-Mail: MHayden AT epa.state.il DOT us
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.709 / Virus Database: 465 - Release Date: 6/22/04
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.709 / Virus Database: 465 - Release Date: 6/22/04
|
