George,
I believe that the you have something like this:
Clients - network A - Server(sun) - network B - Storage Node (Linux)
\_ Clients
And you want to avoid having to allowing routing of packets from network B
through the sun box onto network A, which in theory is required so that Meta
Data from clients on network A can directly stream Meta Data to the Linux box
on network B, when it becomes the server, yes?
If this is a security concern, as they are two disparate networks, then you may
want to consider looking at SSH and its port forwarding etc as its possible
that you can jury-rig something by changing the ports that clients on network A
use to backup, and aliasing things, buts its going to get really really messy
as far as I can see!
I think you will end up having to allow traffic to route through the sun box,
you can always restrict it to just the NetWorker ports if security is a concern
using some firewall tools.
Regards
Paul
Paul White BSc (Hons), Pre-Sales Systems Engineer
Advanced Digital Information Corporation (ADIC) Europe
Date: Tue, 8 Apr 2003 09:42:33 -0400
From: George Sinclair <George.Sinclair AT NOAA DOT GOV>
Subject: Can the server update an index via a storage node?
Hi,
Is it possible for the primary server to update a client index if it cannot
communicate with the client but the storage node can? In other words, if the
primary server can communicate with the storage node and the storage node can
back up the client, can the primary server update the client's index via the
storage node? Clearly, it could write the index to tape since the index resides
on the main server, but I'm not sure how the index would get updated while
backups are running.
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
