I hate when I finally muster the pluck to ask some potentially dumb
question on a list and then minutes later a possible resolution emerges...
Looks like our TSM backup administrator "maybe" had the AFS backup
expiration set for some real high value which resulted in the
accumulation of tapes.
Cheers,
Robert
Robert Petkus wrote:
Rainer Toebbicke wrote:
Robert Petkus wrote:
Folks,
I'm using OpenAFS 1.2.11 on Solaris 9 with TSM for backups. The
problem is that while "backup deletedump" successfully removes dump
records from the backup database, tape resources are never reclaimed
by TSM. The net result is that endless tapes are consumed by AFS
with no clear end in sight. Has anyone had this experience or any
suggestions, clues how to proceed.
If you deletedump with the proper -port option and a suitable butc is
running on that port with TSM access, the dump objects are deleted.
At least that is what we observe here. You don't specify -dbonly or
such, do you?
That's what I do as well -- for example: "backup deletedump -to
03/01/06 -p 3"
The dump objects are indeed deleted, at least from the perspective of
AFS. But TSM never reclaims the tapes where those dumps were stored.
Robert
_______________________________________________
OpenAFS-info mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-info
--
Robert Petkus
Brookhaven National Laboratory
Physics Dept. - Bldg. 510A
Upton, New York 11973
Tel. : +1 (631) 344 3258
Fax. : +1 (631) 344 7616
http://www.bnl.gov/RHIC
http://www.acf.bnl.gov
_______________________________________________
OpenAFS-info mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-info
