Hi,

I just added a second storage node server (new_snode, uses a 45 day
temporary enabler). The system sees it just fine, and I can inventory,
mount and unmount tapes with no problems, but backups just hang waiting
for a writable tape. The previous storage node server (old_snode) is now
running only one tape library (STK) while the other library (SDLT) is
now on the new storage node server. I still have the old jukebox entry
(rd=old_snode:SDLT) listed but it's disabled. The new jukebox entry is:
rd=new_snode:SDLT

When I launch a backup, NetWorker just sits there requesting a writable
tape. It never loads the tape in the device. If, however, I manually
mount the tape then the group runs just fine. There are two appendable
tapes in this pool loaded in the library and inventoried so they show a
location on the new storage node server. All of the affected clients in
the group list the following values in the Storage node field:

new_snode
old_snode
primary

Also, the client entry for the server has the same order. I found if I
did not list the new storage node server under the primary server nsr
resource then the backups would run but then when it went to write out
the client's index it would hang. Adding the new_snode to the field
fixed this, but again, this only works if I manually mount the tape.
Otherwise, NetWorker just hangs waiting. How do I fix this?

Thanks.

George

--
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
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=