On 18/10/11 13:41, Eugene Vilensky wrote:
> On Tue, Oct 18, 2011 at 12:42 AM, Dag Nygren <dag AT newtech DOT fi> wrote:
>> tisdag 18 oktober 2011 03:58:47 skrev du:
>>> But what should this DNS/hosts file entry be?  The client is
>>> configured on the server with the DNS name of the primary interface.
>>
>> E.g. hostname-bu
>> Then you alias that hostname-bu to hostname in the NW client settings.
> 
> Thank you.  I still receive "'System' on 'hostname-bu' must have
> remote access privileges to client 'hostname'," after setting
> hostname-bu as client alias.

Shall I try to simplify this?

Every interface on every server involved in the backup process needs to
resolve. That means the backup server, any storage node that might
backup this client, and the client itself must all be in DNS or hosts
files, with all interfaces included. If an interface is an alternate
interface for a physical client, e.g. just for backups, you should set
it as an alias to the main hostname. If it is a cluster service, you
should NOT under any circumstance add the service name as an alias for
any physical host - this is what the remote access field is for.

I have come across customers who say "We don't put the backup network in
the DNS". This is their choice, but they are making life difficult. By
not doing this they need to add lots of hosts file entries to lots of
machines. The backup server needs entries for all the clients and
storage nodes. The storage nodes need entries for all the clients they
may backup. All the clients need entries for the server and storage
nodes. IMHO it's easier to stick these in the DNS.

If you want to force the backup data over a particular network, then set
the storage node field of the client resource to be the storage node's
name on the backup network. If you want to send the metadata to the
server via the backup network, set the server network interface field.
If you want to send all data from the server to the client over the
backup network, you need to define the client using its name on the
backup network.

Follow these rules and it should work.

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