Hi,
I am trying to understand what TSM does with reclamation of large files.
We have a filepool of 10G-volumes and I see the TSM-server moving a 64G
file during reclamation. This file is from an Exchange-backup.
It seems to me that TSM moves the whole file to other volumes and not
just the small part of it that was residing on a volume and causing the
reclamation to start in the first place. A "q vol f=d" tells me that the
current input volume during reclamation is full with no reclaimable
space.
So for me this sounds a lot of waste of disk I/O. I am curiuos to know
if there is a good reason for this behavior or how to avoid it(except
creating larger volumes).
Best regards
Hans C. Riksheim
<html><body><br /><br /><br /><font face="Arial" size="1"><hr>This email
originates from Steria AS, Biskop Gunnerus' gate 14a, N-0051 OSLO,
http://www.steria.no. This email and any attachments may contain
confidential/intellectual property/copyright information and is only for the
use of the addressee(s). You are prohibited from copying, forwarding,
disclosing, saving or otherwise using it in any way if you are not the
addressee(s) or responsible for delivery. If you receive this email by mistake,
please advise the sender and cancel it immediately. Steria may monitor the
content of emails within its network to ensure compliance with its policies and
procedures. Any email is susceptible to alteration and its integrity cannot be
assured. Steria shall not be liable if the message is altered, modified,
falsified, or even edited.</font></body></html>
|
