Hi Wilbur,
I've seen this before. One thing to try is to create an empty text file called
"pathownerignore" and drop it in the same directory as the NetWorker
executables (usually C:\Program Files\Legato\nsr\bin on Windows or /usr/bin or
/usr/sbin on most flavors of UNIX/Linux). That sometimes forces NetWorker to
back up the correct save sets on the correct clients.
If you're going to use All, I've found that the best practice is generally to
put All in the client resources for the physical nodes, but manually specify
the save set name(s) in the virtual client. If that doesn't work, you may be
stuck manually specifying everywhere.
You can and should test it by putting all three client resources (2 physical
nodes and 1 virtual node) in a group and running savegrp -pv <groupname> from
the server's command line--this runs a preview that doesn't actually back
anything up, but the output will tell you exactly what save sets will be backed
up and what client they belong to.
Another gotcha: make sure the correct CFI are being updated. I've seen cluster
configurations where the data owned by the virtual node gets tracked in one of
the physical clients' CFI, or vice versa (ran into this on an MSCS cluster just
the other day). This can cause problems with recoveries. The workaround for
this is to go into the backup command field in each of the client resources and
enter
save -c <clientname>
This forces NetWorker to update the correct CFI for this client.
If you want more info, these two workarounds are documented in the Admin guide
(although I agree with Stan that the docs on this are, um, not as crystal clear
as they could be).
Hope this helps!
Allison
~~~~~~~~~~~~~~~~~
Cambridge Computer Services
Artists in Data Storage
acorbett AT cambridgecomputer DOT com
~~~~~~~
Date: Wed, 31 May 2006 10:34:28 -0400
From: "Mason, Wilbur" <Wilbur.Mason AT PFIZER DOT COM>
Subject: Re: backing up a MS Cluster client
Siobhan,
I am using 7.1.1. and I have seen where saveset ALL grabs all of the physical
and virtual drives with physical and virtual client definitions. I have had to
explicitly define the drives to get around this issue. Any suggestions? Has
anyone seen this before?
-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
On Behalf Of Siobhán Ellis
Sent: Tuesday, May 30, 2006 6:30 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] backing up a MS Cluster client
Stan,
you just define the physical nodes and the cluster alias as 3 seperate
clients.
The physical nodes will back up the drives only for them, and the cluster
client will backup the clustered data.
Will the physical nodes be storage nodes?
If not, that's it.
BTW, have seen problems with NetWorker not counting SQL licenses properly,
so be careful!
Siobhan ELlis
Independant Consultant
Sydney
Australia
>From: Stan Horwitz <stan AT temple DOT edu>
>Reply-To: Legato NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU>,
>
> Stan Horwitz <stan AT temple DOT edu>
>To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
>Subject: [Networker] backing up a MS Cluster client
>Date: Tue, 30 May 2006 16:57:26 -0400
>
>Until today, I knew nothing about Microsoft clusters. Now I have to set up
>a NetWorker client on an MS Cluster that's running Windows 2003. I have
>all the licenses I need, but I am not sure about how to configure the
>groups. The NetWorker server is running 7.2.1 under Solaris 9, as are the
>two nodes in this cluster.
>
>On page 56 of the Windows Administrators' Guide, it lists some steps to
>install only the NetWorker client software in a cluster, but what do I do
>after installing the software?
>Also, on the same page, it says in section 3 to add the hostname and user
>of each node into the following client resources attributes of the virtual
>clients, Remote Access and Administrator. I do not see an administrator
>client resource; that resource only shows up for the NetWorker server.
>
>How do I distinguish between a NetWorker virtual client and a NetWorker
>physical client?
>
>I can get the cluster item to back up, but it only shows the Q:\ drive in
>the savegroup report. Shouldn't I see information about the virtual nodes'
>disks as well, and also the private disks on each cluster node? I think
>something is missing in my understanding of how this cluster configuration
>works and administrators guide spends most of its coverage on clusters
>explaining how to set up a NetWorker server that's clustered, but that is
>not what I am doing here.
>
>Any suggestions will be appreciated.
>
>To sign off this list, send email to listserv AT listserv.temple DOT edu and
>type
>"signoff networker" in the
>body of the email. Please write to networker-request AT listserv.temple DOT
>edu if
>you have any problems
>wit this list. You can access the archives at
>http://listserv.temple.edu/archives/networker.html or
>via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu
if you have any problems
wit this list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|
