How long it'll take is a complicated subject.  The fileserver's on fast
ethernet, TSM on 155Mbps ATM, so I should get some really good speed, but
restores are slow.  I did some FTP tests, and I'm only getting about 15Mbps
to the file server from anywhere, ATM or Ethernet.  The fileserver disk is
IBM ESS Shark disk, so I doubt that's holding anything back.  I have a
sneaking suspicion the thing's routing through a Token Ring segment.  Our
networking group insists it's a server config problem, and our NT Group says
it's definitely networking.  I'm tempted to schedule some down time, hook up
two servers directly with a crossover cable, and see if that gets some good
transfer times and then take that to the networking group.

Anyway, at 15Mbps, I expect it'll take about 148 hours in sheer wire time,
add a bit for TSM overhead.  6 days is good, right?  I'd figure somewhere
between 12 and 18 hours at Fast Ethernet speed, but until I can expect that
kind of throughput, I'm not going to tell anybody here that number.  If it
goes TU, I expect that'll give me plenty of management backing when I demo
that 15 Mbps.

Matt, sorry about the server going down.  There's a Q VOLUMEUSAGE, I recall
reading about it somewhere, but I can't seem to find the parameters it uses.
Here's a select
select volume_name from volumeusage where node_name='NODENAME' and
copy_type='BACKUP'
but it'll get you both primary and copy pools.  To just do primary, I would
have had to join through stgpools and that might take longer.

Alex Paschal
Storage Administrator
Freightliner, LLC
(503) 745-6850 phone/vmail