We recently added 40 GBs to our backup diskpool in an effort to speed
up our backup processes. In large part that has worked, however, now we
find the tape devices sit idle all night and, to make matters worse, the
migration process from the diskpool to tape (a six 3590 3494 library)
does not seem to engage more than one drive. So I believe we are actually
worse off now because we have merely moved the bottleneck from the client
to the server to the diskpool to the tape device and now our tape drives
sit idle most of the night. I have contacted TSM support (we are at 4.12)
and they indicated that the migration processes setting (which has been
set as high as 6) does not translate to tape drive mounts as I might have
imagined. Instead in a logic I found difficult to follow, processes are
linked to nodes or at least node filespaces in the backup pool. From
their perspective there appears to be no way to specify migration tape
mounts.
What we are aiming for is a large enough diskpool to buffer the
entire night's backup volume and then to run our copypool process for
offsiting our copy tapes followed by a migration of the data from the
diskpool to the resident tapes in the library (disk caching is not really
a goal at this time). We can throw a couple hundred GBs at the diskpools,
but that is no help if we can't get the data off the disks in a timely
manner. If we could get the offload to both the copypool and the local
library to take place on multiple drives I think our plan could succeed.
Can anyone shed any light on how we might achieve our aims?
Kind regards,
Hagen Finley
Longs Drugs
begin:vcard
n:Finley;Hagen
tel;cell:925-260-8538
tel;fax:925-210-6809
tel;home:209-577-1671
tel;work:925-210-6694
x-mozilla-html:FALSE
adr:;;;;;;
version:2.1
email;internet:[EMAIL PROTECTED]
fn:Hagen Finley
end:vcard
