EMC was able to fix it. What I had to do: delete the Networker client that
was associated with the moved cluster resource. Add the name of the moved
clustered resource as an alias of the *other* clustered resource.
SO: I deleted the Networker client "PSFILE1" (which was the cluster
resource we moved from one cluster group to the other. I added "PSFILE1"
as an alias of PSSQL1 (which is the remaining clustered resource).
And then it ALL Just Worked. :-)
Now, I don't know if I had to do that because I had had Networker clients,
each of which was a network name cluster resource, previously in separate
cluster groups, and so needed an alias, when consolidating cluster groups,
I have other cluster groups which have multiple network name cluster
resources, and they work just fine. BUT on that other cluster, I only have
a Networker client for *one* of those network names, not for multiple
network name cluster resources within the same cluster group (which is
what I have now, with PSSQL1 and PSFILE1).
Anyway, my test backup now works. PSSQL1 sees all shared resources (not
just local drives, which is what had been happening).
--
Michael Leone
Network Administrator, ISM
Philadelphia Housing Authority
2500 Jackson St
Philadelphia, PA 19145
Tel: 215-684-4180
Cell: 215-252-0143
<mailto:michael.leone AT pha.phila DOT gov>
EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU> wrote on
02/24/2011 10:27:01 AM:
> From: Michael Leone <Michael.Leone AT PHA.PHILA DOT GOV>
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Date: 02/24/2011 11:29 AM
> Subject: Re: [Networker] Can not backup up cluster resources after
> moving cluster resources from one cluster group to another cluster group
(MS)
> Sent by: EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU>
>
> Please include the list in responses, thanks.
>
> > > I get "Nothing to save", which is incorrect. Data has certainly
> > > changed on the drive letters associated with PSSQL1. NOTE: I
> >
> > That message to me smacks of networker thinking no filesystems
> > are associated with the virtual client, not of what it thinks
> > has changed on disk.
> > Is the error message associated with savefs: ? (whose job it
> > is to work out what filesystems to backup)
>
> I believe so. It's in the log from the job scheduled in NMC.
>
> > What does a savegrp probe say for each client in the cluster ?
>
> That doesn't seem to be working:
>
> 42506 2/24/2011 10:23:21 AM 2 0 0 5036 4584 0
> admnman004.wrk.ads.pha.phila.gov nsrd savegroup info: starting Special
Job
> Runs (with 1 client(s))
> 32493 2/24/2011 10:23:21 AM 2 0 0 8144 4216 0
> admnman004.wrk.ads.pha.phila.gov savegrp pssql1:probe started
> 0 2/24/2011 10:23:21 AM 2 0 0 8144 4216 0
> admnman004.wrk.ads.pha.phila.gov savegrp savefs -s
> admnman004.wrk.ads.pha.phila.gov -c pssql1 -g "Special Job Runs" -p -l
> full -R -v
> 38758 2/24/2011 10:23:21 AM 2 0 0 5036 4584 0
> admnman004.wrk.ads.pha.phila.gov nsrd savegroup info: Special Job Runs
> running on pssql1
> 40473 2/24/2011 10:23:23 AM 2 0 0 8144 4216 0
> admnman004.wrk.ads.pha.phila.gov savegrp command ' savefs -s
> admnman004.wrk.ads.pha.phila.gov -c pssql1 -g "Special Job Runs" -p -l
> full -R -v' for client pssql1 exited with return code 1.
> 32496 2/24/2011 10:23:23 AM 2 0 0 8144 4216 0
> admnman004.wrk.ads.pha.phila.gov savegrp job (7652468) host: pssql1
> savepoint: pssql1:ALL had ERROR indication(s) at completion.
> 64690 2/24/2011 10:23:23 AM 2 0 0 8144 4216 0
> admnman004.wrk.ads.pha.phila.gov savegrp savegrp:Special Job Runs *
> pssql1:ALL See the file D:\Program Files\Legato\nsr\tmp\sg\Special Job
> Runs\sso.000002 for output of save command.
> 7340 2/24/2011 10:23:23 AM 2 0 0 8144 4216 0
> admnman004.wrk.ads.pha.phila.gov savegrp pssql1:probe failed.
>
> And the output of the save command is
>
> 7184:(pid 5052): nothing to save
> savefs pssql1: failed.
>
>
> > Does it correctly identify the various filesystems as being
> > 'owned' by the correct client ?
>
> No. If I try and backup PSFILE1, I get the drive letters that P: and S:
> (which are the drives I want). If I backup PSSQL1, I get "nothing to
back
> up".
>
> > I presume they're all set to backup 'All' and relying upon the
> > networker client to talk to MCS to determine who owns what.
>
> Correct. PSSQL1 is set to ALL, and is getting nothing. PSFILE1 is set to
> ALL and is getting P: and S:. What I need to do is get P: and S: to be
> backed up by PSSQL1, so I can delete the Networker license for PSFILE1
and
> use it somewhere else.
>
> 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
> with 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 with 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
|