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.
Here's why I ask. We have a primary server running on a Solaris box and
a storage node running on a Redhat linux box. The primary server can
back up any host, but it's currently configured to only backup a few
specified machines. These hosts are outside the purview of the storage
node. It cannot back them up. So, the storage node backs up everyone
else. However, since the primary server can see everyone, of course it
would be able to communicate with any of the clients to update their
index entries. Now, we want to switch the two machines, making the Linux
machine the primary server and the Solaris machine the storage node
server. We do have a Linux server license that we have not yet used. The
Linux host would continue to backup the same clients that it does now
and likewise with the Solaris machine, BUT because the Linux host would
now be handling all the client indexes, how would it update the indexes
for the clients that are being backed up by the Solaris box? Clearly,
the data would be sent to the storage node (in this case the Sun
machine) and it's attached library, and since the index resides on the
Linux box, it would have no trouble writing this to tape to its attached
storage, but if I understand things correctly, the client's index is
updated while the client is backing up, so if the primary server cannot
see the client, I don't see how it will be able to update the client's
index; unless, of course, there's a way to have the storage node pass
this information to the primary server.
Will we be forced to rig the primary server so it can access these
clients just as the Solaris machine now does? We can do that, in which
case both primary server and storage node would be able to see
everything, but we were hoping to avoid it.
Any help would be appreciated.
Thanks.
George
George.Sinclair AT noaa DOT gov
--
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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
