Hi folks
we have three cases open at Legato since October, 2004 with the same issue. We
also tried 7.1.3 and 7.2 with no effort. The only way to backup our clients in
an Windows Cluster was to roll back to 7.1.1, as Phil already described. There
are no dependencies on any BSM from Legato. If we got a solution or workaround
(so I'm a believer), I let you know.
regards
Klaus
> -----Ursprüngliche Nachricht-----
> Von: Legato NetWorker discussion
> [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] Im Auftrag von
> McDougal, Philip H
> Gesendet: Dienstag, 8. März 2005 21:17
> An: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Betreff: Re: [Networker] Networker v7.1.2 on Windows2003
> cluster as storage nodes
>
>
> Not sure if this is a known issue or not, or even if' it's similar to
> your issue, but I'll send it out in case other's aren't aware.
>
> I had an major problem with my clustered systems and the nsrexecd
> services stopping upon a scheduled backup and then failing the job
> because the RPC wasn't talking.
>
> I have an open case with Legato for this and they are aware of it. My
> environment that kept failing was:
>
> Server = Win2K - 7.1.2
> Clients = win2k3 - 7.1.2
>
> BSM for Exchange and SQL didn't matter. I tried a combination of them
> but they only thing that was in common was 7.1.3 or 7.1.2 on my
> clustered systems and it would stop that service. I went
> back to 7.1.1
> on the clients and kept 7.1.2 on the server and it worked fine.
>
> The Legato Tech and Engineers say it's a client issue. So by rolling
> back your clients, you should then be able to back up your clusters.
>
> If you need more info I'd be glad to disclose it.
>
> Thanks and I hope that helps.
> Phil.
>
>
>
> --------------------------------------------------------
>
>
> Philip McDougal
> Application Support Engineer
> Jenner & Block LLP
> One IBM Plaza
> Chicago IL 60611-7603
> Tel (312) 222-9350
> Fax (312) 840-8879
> PMcDougal AT jenner DOT com
> www.jenner.com
>
> This email may contain privileged or confidential information
> and is for the sole use of the intended recipient(s). Any
> unauthorized use or disclosure of this communication is
> prohibited. If you believe that you have received this email
> in error, please notify the sender immediately.
> --------------------------------------------------------
>
> -----Original Message-----
>
> From: Legato NetWorker discussion
> [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
> On Behalf Of Scott Clous
> Sent: Tuesday, March 08, 2005 2:08 PM
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: Re: [Networker] Networker v7.1.2 on Windows2003 cluster as
> storage nodes
>
> 1. Guessing, are you licensed for clusters?
> 2. Does your hosts file on the backup server correctly have
> their info?
> 3. Does the client definition have the right names for those machines?
> 3.5) Check other setup issues on the cluster.
> 4. I'd suggest reviewing info in docs on backing up clusters, and
> finally, 5. but you need to put this Pathowneringore (with no
> extension)
> as a file in the nsr\bin directory on both physical servers.
>
> Hope that gets you started.
>
> -----Original Message-----
> From: Legato NetWorker discussion
> [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
> On Behalf Of Pierpa
> Sent: Monday, February 21, 2005 12:50 PM
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: [Networker] Networker v7.1.2 on Windows2003 cluster
> as storage
> nodes
>
> Hi all,
> I'm fighting with a NW server v7.1.3 trying to backup 2 W2K3
> systems in
> cluster; these 2 systems share in SAN the same library. A strange, and
> up to me unbelievable thing happens. On the cluster node WITHOUT
> services running, I can see nsrexecd started and also nsrmmd processes
> (#4). On the other node, where the cluster services run, the nsrmmd
> processes continue to restart, and I can't manage backups, of course.
> Additionally, even if nsrmmd processes run, I can't see them using
> rpcinfo -p on this node.
> Is someone aware of this behaviour and may I have suggestions
> about this
> mess ??
>
> Thanks
> Pierpa
>
> --
> Note: To sign off this list, send a "signoff networker" command via
> email to listserv AT listserv.temple DOT edu or visit the list's Web site at
> http://listserv.temple.edu/archives/networker.html where you can also
> view and post messages to the list. Questions regarding this
> list should
> be sent to stan AT temple DOT edu
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>
> --
> Note: To sign off this list, send a "signoff networker" command via
> email to listserv AT listserv.temple DOT edu or visit the list's Web site at
> http://listserv.temple.edu/archives/networker.html where you can also
> view and post messages to the list. Questions regarding this
> list should
> be sent to stan AT temple DOT edu
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>
> --
> Note: To sign off this list, send a "signoff networker"
> command via email
> to listserv AT listserv.temple DOT edu or visit the list's Web site at
> http://listserv.temple.edu/archives/networker.html where you can
> also view and post messages to the list. Questions regarding this list
> should be sent to stan AT temple DOT edu
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listserv.temple DOT edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
