Can cloning be done to different media in same tape library?

Yes (as previously noted, as well as "LTO Ultrium-3" media type selected), yes and yes.
Curious indeed, right?

In media pools have you selected any target devices in selection criteria? Have you also got labelled clone tapes available? The LTO3 Clone Pool also has clone pool selected as pool type?

I would dispute that, if you are cloning (making a copy) the destination pool needs to be configured as a clone pool. However if you are staging it does not need to be part of a clone pool but can be - never quite figured the logic of that one out!

Hrvoje has the best idea (as usual!) - post the config here and we can tell you what is wrong with it or get even more confused

--Client info dump for data zone server: djcraft--
--------------------------------------------------------------------
type: NSR client;
name: djcraft.backup.cc.wmich.edu;
server: djcraft.backup.cc.wmich.edu;
client id: \
1225ff5f-00000004-3c20fb0f-3c20fb0e-00010000-0a0a1df2;
scheduled backup: Enabled;
comment: ;
Save operations: ;
archive services: Disabled;
schedule: Default;
browse policy: week-3;
retention policy: week-3;
statistics: elapsed = 1045712, index size (KB) = 245773,
amount used (KB) = 245773, entries = 1419917;
index message: ;
index operation start: ;
index progress: ;
index operation: Idle;
index save set: ;
directive: ;
group: ;
save set: "NMCASA:/gst_on_djcraft/lgto_gst";
save set MBT: ;
priority: 500;
remote access: ;
remote user: ;
password: ;
backup command: savepsm.sh;
application information: ;
ndmp: No;
executable path: ;
server network interface: ;
aliases: djcraft.backup.cc.wmich.edu,
backup.it.wmich.edu, djcraft;
index path: ;
owner notification: ;
parallelism: 32;
archive users: ;
storage nodes: nsrserverhost, thumper2.backup.cc.wmich.edu;
recover storage nodes: nsrserverhost, thumper2.backup.cc.wmich.edu;
clone storage nodes: nsrserverhost, thumper2.backup.cc.wmich.edu;
hard links: Disabled;
short filenames: Disabled;
hostname: djcraft.backup.cc.wmich.edu;
administrator: entries_deleted_by_TB
ONC program number: 390109;
ONC version number: 2;
ONC transport: TCP;
client OS type: Solaris;
CPUs: 4;
NetWorker version: 7.3.4.Build.558;
enabler in use: Yes;
licensed applications: ;
licensed PSPs: ;


--Client info dump for storage node: thumper2--
-------------------------------------------------------------------
type: NSR client;
name: thumper2.backup.cc.wmich.edu;
server: djcraft.backup.cc.wmich.edu;
client id: \
f05eb6ff-00000004-4a0839a0-4a08399f-281a0000-ac1e0a14;
scheduled backup: Enabled;
comment: ;
Save operations: ;
archive services: Disabled;
schedule: Full Every Wednesday;
browse policy: week-3;
retention policy: week-3;
statistics: elapsed = 1044795, index size (KB) = 0,
amount used (KB) = 0, entries = 0;
index message: ;
index operation start: ;
index progress: ;
index operation: Idle;
index save set: ;
directive: Unix standard directives;
group: Default;
save set: /nsr;
save set MBT: /nsr;
priority: 500;
remote access: ;
remote user: ;
password: ;
backup command: ;
application information: ;
ndmp: No;
executable path: ;
server network interface: ;
aliases: thumper2, thumper2.backup.cc.wmich.edu,
thumper2.admin.private,
thumper2.test.admin.private;
index path: ;
owner notification: ;
parallelism: 32;
archive users: ;
storage nodes: thumper2.backup.cc.wmich.edu,
djcraft.backup.cc.wmich.edu;
recover storage nodes: thumper2.backup.cc.wmich.edu,
djcraft.backup.cc.wmich.edu;
clone storage nodes: djcraft.backup.cc.wmich.edu;
hard links: Disabled;
short filenames: Disabled;
hostname: djcraft.backup.cc.wmich.edu;
administrator: entries_deleted_by_TB
ONC program number: 390109;
ONC version number: 2;
ONC transport: TCP;
client OS type: Solaris;
CPUs: 4;
NetWorker version: 7.3.2.Build.364;
enabler in use: Yes;
licensed applications: ;
licensed PSPs: ;


--Info dump for pool: LTO3 Clone Pool--
--------------------------------------------------------
type: NSR pool;
name: LTO3 Clone Pool;
comment: ;
enabled: Yes;
pool type: Backup Clone;
archive only: No;
label template: Default Clone;
retention policy: week-3;
groups: ;
clients: ;
save sets: ;
levels: ;
devices: ;
store index entries: No;
auto media verify: No;
Recycle to other pools: No;
Recycle from other pools: No;
volume type preference: LTO Ultrium-3;
max parallelism: 0;
mount class: default;
WORM pool: No;
create DLTWORM: No;
source: ;
hostname: djcraft.backup.cc.wmich.edu;
administrator: deleted_entries_by_TB
ONC program number: 390109;
ONC version number: 2;
ONC transport: TCP;


--Info dump for pool: LTO3 Clone--
------------------------------------------------
type: NSR pool;
name: LTO3 Clone;
comment: Pool for cloning to LTO3 drives;
enabled: Yes;
pool type: Backup Clone;
archive only: No;
label template: Default Clone;
retention policy: week-3;
groups: ;
clients: ;
save sets: ;
levels: ;
devices: "rd=thumper2:/dev/rmt/1cbn",
"rd=thumper2:/dev/rmt/2cbn";
store index entries: No;
auto media verify: No;
Recycle to other pools: No;
Recycle from other pools: No;
volume type preference: ;
max parallelism: 0;
mount class: default;
WORM pool: No;
create DLTWORM: No;
source: ;
hostname: djcraft.backup.cc.wmich.edu;
administrator: entried_deleted_by_TB
ONC program number: 390109;
ONC version number: 2;
ONC transport: TCP;

On which host is your AFTD? In initial post you said you wish to clone that - is this on server or storage node? Based on preferance in clone storage node for that client (server or storage node) this is where your target gets loaded. If this is server, NW will keep expecting this on server despite having storage node listed at second place.

If you are cloning data for client:

name: thumper2.backup.cc.wmich.edu;

It needs to write to the configured clone storage node during the clone which is:

clone storage nodes: djcraft.backup.cc.wmich.edu;


Looking at the target pool for clone pool LTO3 Clone you have restriction to drives (devices) on thumper 2:

devices: "rd=thumper2:/dev/rmt/1cbn",
"rd=thumper2:/dev/rmt/2cbn";

My guess is if you amend the LTO3 pool to either remove all drives ticked or to add the drives on djcraft then this will clone correctly.

This was it! I had to modify the client settings of my storage node, "thumper2", and add "thumper2" to "Clone storage nodes". For some reason, I didn't think I would have to add itself as a clone storage node. After doing that, NetWorker no longer complained that it could not find the correct media. It was the media error that was throwing me off and thinking it was some kind of pool problem. In a sense, I guess it was in that the pool couldn't address the drives I had statically configured to work with the remote devices on "thumper2". Since "thumper2" wasn't on list of allowed clone storage nodes, the criteria wasn't met and the pool failed to find what it needed.\

Sometimes this product seems like a Rube Goldberg machine. It's a good product, but so many knobs and switches to play with to get it working just right... Thanks for all the help! It is, as always, greatly appreciated.

Well, its more a case of being well organized. The best thing you can do is plan your media and device usage carefully, ensure your media pools are configured correctly with a reasonable level of selection criteria - once it gets mixed up its very difficult to get back into correct order!