Hi Brian! Thank you very much for your reply! You are right, the UNIX guys are looking into AFS volume backups. I'm trying to talk them out of it, because I don't like backup utilities that rely on their own expiration methods. Somewhere down the line they will forget running cleanup jobs and you will end up with a growing amount of obsolete backups on your TSM server. We have several TDP for Oracle clients which use their own expiration. It requires a lot of manual monitoring and sometimes backup files are left behind by Oracle. The 2.2 version delivers the TDPOSYNC clean-up utility for this. One of the UNIX guys will put the problems they have with file backup through the TSM AFS client in writing so I can put it on the ADSM-L list. I think it has something to do with the restore of mountpoints or something like that. Thanks again! Kindest regards, Eric van Loon KLM Royal Dutch Airlines
-----Original Message----- From: Brian T. Huntley [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 03, 2002 21:51 To: [EMAIL PROTECTED] Subject: Re: AFS backup Howdy, Eric... It depends on which AFS backup client you are using. If you use the file backup client, TSM controls the retention of the files just as any other filesystem. If you use the volume backups, however, you will need to do the controls through AFS. We backed-up our 500GB AFS cell by volume for quite awhile due to the performance benefits, but found it required an absolutely silly amount of tape storage to retain backups as far back as we had to go. So, we made the shift to file backups, and, although it is MUCH slower than the volume dumps, we've accepted that limitation to make our tape requirements a bit more reasonable. I'd be happy to discuss further, if you are interested. Oh, also, you really need the AFS manuals to be able to get the full story on AFS backups through TSM. There are some sections that directly address connecting AFS and TSM. HTH, -b -- +-----------------------------------------------------------------------+ | Brian T. Huntley Systems Administrator | | Campus Information Services, Clarkson University | | Ph/FAX: 315.268-6723/6570 | | [EMAIL PROTECTED] www.clarkson.edu/cis | +-----------------------------------------------------------------------+ UNIX *is* user friendly. It's just selective about who its friends are. On Wed, 3 Apr 2002, Loon, E.J. van - SPLXM wrote: // Hi *SM-ers! // We are implementing our first AFS backup clients and I'm looking through the // AFS part of the AIX client manual. It's rather limited. // The AIX guys say that the AFS client does it's own version control (like // most of the TDP clients). They thus say that I have to create separate nodes // on TSM for the AFS backup and these node should be assigned to a policy // domain containing a copygroup with VEREXIST=1 VERDEL=0 RETEXTRA=0 RETONLY=0 // so that the client can do it's own versioning. // Since I cannot find any information about policy set recommendations, I // doubt this very much. // Can anybody who's using the AFS client shed some light on this? Thanks in // advance!!! // Kindest regards, // Eric van Loon // KLM Royal Dutch Airlines // // // ********************************************************************** // For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. // ********************************************************************** // //
