ton@gufalet.let.rug.nl (Ton Roovers) (08/24/90)
Does anybody know what the configuration option retrylimit in the configuration file for fbackup means? The HP-UX System Administration Tasks Manual says: "maximum number of bytes of media to use while retrying the backup of an active file (retrylimit 5,000,000)" I just don't understand that. Ton Roovers systems manager _______________________________________________________________________________ Faculty of Arts and Letters, Groningen University ton@let.rug.nl PO Box 716, NL 9700 AS Groningen, The Netherlands ton@gufalet.UUCP
frank@hpuamsa.UUCP (Frank Slootweg CRC) (08/24/90)
Dear Mr. Roovers, A file is defined as active by "fbackup" if the modification time changes before it finsihes writing the file to tape. I.e., it gets the modification time, starts writing the file to tape and checks the modification time again before it finishes. Since an active file can not be properly backed_up/restored, "fbackup" has to retry or skip the active file. The number of retries for an active file is defined by "maxretries". The maximum amount of media (in bytes) "wasted" by these retries is limited by "retrylimit". Now you might ask *why* is media wasted by a retry? (i.e. Why does "fbackup" not skip back to the beginning of the "bad" file on tape?) I don't know the absolute answer to this but I *think* it is because : - A file on tape does (most of the time) not start on a physical record boundary (i.e. f.e. after a IRG for magtape) and/or - "fbackup" can have its output piped to another program. It is impossible to seek (backward or forward) on a pipe. Hope this help. Please call or mail us if you need further help or information. After all that is what we/software_contracts are for :-) Frank Slootweg, RCE/Teamleader HP-UX Support, Dutch Customer Response Center.