Networker

[Networker] cloning to specific storage node fails

2002-09-13 06:04:33
Subject: [Networker] cloning to specific storage node fails
From: Ingo Roschmann <ingo AT VISIONET DOT DE>
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Date: Fri, 13 Sep 2002 06:04:30 -0400
Hi all,

we have one networker server (5.3.3) and one storage node, to each attached
an Exabyte 220 library with 2 tape drives each.
Backup ist configured to write backups to, say, library A and then clone
the save sets to a tape in library B and, vice versa, write the clones of
save sets written to library B, to library A.
For this reason we have configured two clone pools, say pools A and B;
tapes from pool A are located in tape library A, those of pool B in library
B.

What we are experiencing is, that the cloning to pool B is ok, but if we
want to write a clone to pool A, networker suggests "label a new writable
volume for pool A"; the required pool is correct, but the volumes of that
pool in tape library A are ignored.
If we label a tape which is located in tape library B, to pool A, the
cloning succeeds.
It seems as if pool A were restricted to the devices in tape library B, but
it is not - there is no restriction to a specific drive, group, level or
whatever.

What drives me crazy is, that our configuration is totally symmetric, yet
we have this asymmetric behavior!

Any ideas? Database corrupt?
Is there a way checking the database?

Help!

--
Note: To sign off this list, send a "signoff" 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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

<Prev in Thread] Current Thread [Next in Thread>
  • [Networker] cloning to specific storage node fails, Ingo Roschmann <=