Networker

Re: [Networker] Sanity Check: Restore to Windows Cluster Resource

2008-06-05 12:47:34
Subject: Re: [Networker] Sanity Check: Restore to Windows Cluster Resource
From: "Cox, Shawn" <Shawn.Cox AT PCCA DOT COM>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Thu, 5 Jun 2008 11:41:47 -0500
It is working for me Client is 64bit v7.4sp2 and Server v7.2.2 Windows Server 
2003.
On the Client resource for the virtual node I have SYSTEM@node1 and 
SYSTEM@node2 for remote access.

However, I do not have the security scope restriction that you require so this 
may not help you much.


--Shawn



-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On 
Behalf Of Geoffrey Duke
Sent: Thursday, June 05, 2008 11:12 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] Sanity Check: Restore to Windows Cluster Resource

Hi,



I've been working with EMC support on an issue I have with a Windows Cluster
environment. I've got a two-node cluster, with a single Cluster Resource
(virtual node) client. I have been successful in backing up the physical
nodes and the cluster resource client with no real problem. I can recover
files only be running the restore operation on the physical node on which
the cluster resource is presently mounted. This true of both the GUI and
CLI.



What I would like to be able to do is to run the recovery on either node,
selecting the cluster resource client as both the source and destination.
When I attempt this, I get an error message indicating that I need the
"remote access all clients" privilege. I really don't want to give the
server administrator of a cluster rights to every networker client. I would
like the "remote access" attribute of the client to suffice.



I've been told by a third party consultant that this should work, and that
he has other clients where this does work. However, I've opened an issue
with EMC, and over the past few weeks, as I tried to explain how the
administrator of a client system wasn't necessarily also a Networker
administrator, they have decided that the product is working as designed.



Is anyone who uses Networker with Windows Clustering able to perform this
kind of recovery? Was there some special way that you configured the "remote
access" attributes for the cluster members?



Currently running:  Networker Client 7.3.4 ,  Networker Server 7.3.3



--Geoff

Geoffrey Duke
802.656.1172 |  <http://www.uvm.edu/~gcd> System Administrator |
<http://www.uvm.edu/ets> Enterprise Architecture & Administration |
<http://www.uvm.edu/> University of Vermont






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