Patch Name: PHCO_23861 Patch Description: s700_800 10.20 fbackup(1M)/frecover(1M) cumulative patch Creation Date: 01/05/23 Post Date: 01/06/05 Hardware Platforms - OS Releases: s700: 10.20 s800: 10.20 Products: N/A Filesets: OS-Core.SYS-ADMIN OS-Core.UX-CORE OS-Core.ADMN-ENG-A-MAN Automatic Reboot?: No Status: General Release Critical: No Path Name: /hp-ux_patches/s700_800/10.X/PHCO_23861 Symptoms: PHCO_23861: Enhancement request for Ultrium tape drive support. PHCO_21263: When trying to selectively recover a file from a DLT7000 fbackup tape archive using the command line, "frecover -xovf /dev/rmt/5m -i filename" the following error messages were displayed: frecover(1003): backup id does not match expected value frecover(1061): attempt to continue recovery with new backup id? [yes no] If the user enters "no", frecover immediately terminates. If the user enters "yes", frecover continues but fails to recover the file and finally terminates. Note: it is also possible to get the following error messages instead of or in addition to the 1003/1061 errors. frecover(1004): backup time does not match expected value frecover(1062): attempt to continue recovery with new backup time? [yes no] A complete restore works fine. Using the remote form of the device name also works but is too slow. For example, the command using the remote form of the device name is entered as: "frecover -xovf hostname:/dev/rmt/5m -i filename" PHCO_18135: s700_800 10.20 cumulative fbackup(1M)/frecover(1M) patch 1. A warning return value is introduced to notice the operator that fbackup ends with the warnings. The following explanations can be found in fbackup(1M) man page: fbackup returns one of the following values: 0 upon normal completion. 1 if it is interrupted but allowed to save its state for possible restart. 2 if any error conditions prevent the session from completing. 4 if any warning conditions are encountered. If warnings occur, the operator should verify the fbackup logs to justify the sanity of the backup taken. 2. fbackup does not save all directories when doing an incremental backup, and frecover can not restore parent directories from an incremental fbackup file if the parent directories have been deleted. The operator will see the following messages: frecover(1060): /XXXX not on media frecover(1017): cannot chdir to directory /XXXX 3. fbackup will loop and consume lots of CPU time without proceeding to backup any data when there exists a negative group ID in /etc/group or a negative user ID. PHCO_17865: The frecover command can not recover a file selectively if the file size is greater than 4GB. The user will see the following error message: frecover(1003): backup id does not match expected value PHCO_16031: 1. fbackup/frecover does not have fast search capability on DLT tape devices. 2. fbackup/frecover does not allow index file size > 99999999. PHCO_14176: When a volume change is needed, frecover prompts the user and then reads from /dev/tty to receive the expected carriage return. If there is no terminal associated with the frecover process, frecover aborts because it cannot open /dev/tty. PHCO_13839: This patch for fbackup is part of the 10.20 ACE 2 bundle which adds networking enhancements to 10.20. New networking features supported in ACE 2 include NFS Version 3.0, AutoFS, and CacheFS. PHCO_9228: The fbackup command on HP-UX 10.20 may hang when log or group names exceed 8 characters in length in the /etc/passwd or /etc/group files. This patch corrects this problem. PHCO_9188: The fbackup command on HP-UX 10.20 cannot read old volume headers written by a pre-10.20 fbackup execution. The operator will see the following error: fbackup(3205): unable to read a volume header Note the operator will see this error as well if the tape is new or has been used by another backup utility such as cpio. Defect Description: PHCO_23861: Enhancement request for ultrium tape drive support. Resolution: Add Ultrium tape drive support to fbackup/frecover. PHCO_21263: frecover was fast-searching trying to selectively recover a file from a DLT7000 fbackup archive when it ran into an embedded fbackup archive file. In other words the fbackup file being searched, itself, contained another fbackup file. As frecover was parsing file headers it hit the file headers from the embedded backup which did not match identifying backup session information. frecover got confused and could not continue correctly. frecover fast search logic for DLTs could not handle embedded fbackup files during selective recoveries. Resolution: Enhanced file-header parsing to initiate recovery skipping over the embedded fbackup file and resync'ing to continue fast searching for target file(s). Now, frecover provides correct handling of embedded fbackup files encountered while fast searching a tape for one or more files. With this patch, the user will not encounter the messages listed below unless mismatch errors are the result of either an error reading a tape volume header, or encountering a tape volume that is either out of sequence or is from another fbackup session. The messages are: frecover(1003): backup id does not match expected value frecover(1061): attempt to continue recovery with new backup id? [yes no] -or- frecover(1004): backup time does not match expected value frecover(1062): attempt to continue recovery with new backup time? [yes no] Also enhanced error recovery logic to make better use of viable volume header information in the event of an error encountered while loading or changing tape volumes. PHCO_18135: 1. fbackup does not notice the operator in its return value that the warnings occur. 2. The logical condition to the directory files is ignored in the incremental backups. 3. The user ID or group ID is used to compute an index into a table. The hashing algorithm can not handle a negative ID. Resolution: 1. fbackup reurns 4 if any warning conditions are encountered. 2. fbackup saves all directories as needed. 3. The hashing algorithm is modified to contain the case of negative UID and GID. PHCO_17865: The frecover command can not recover a file selectively if the file size is greater than 4GB. This is due to an incorrect data typecast from 64 bits to 32 bits. Resolution: A 64 bit data type was truncated due to using an incorrect data typecast. PHCO_16031: 1. fbackup/frecover currently does not have fast search capability on DLT tape devices. This patch includes fast search capability, so that selective recovery time on DLT devices can be greatly reduced. Since DLT does not have the advantage of setmarks as DDS does, you will not see the same performance gains as with DDS fast searching; DLT makes use of filemarks, which were already there for checkpointing. You should get a measurable gain in performance over the file-by-file searching previously used on DLT devices, and that gain percentage only increases the further into the tape it has to go to find your file. Updated fbackup(1m) and frecover(1m) man pages are included in this patch. 2. The current fbackup volume header allows only 8 digits for the index file size. If your index file size is greater than 99999999, then when you try to recover the index file or the volume header information (frecover -I or -V), the index file size is truncated to 8 digits. With -I, this means the index file that is created is truncated. With -V, this means the index file size that is reported is incorrect; it is the truncated value. PHCO_14176: When a volume change is needed, frecover prompts the user and then reads from /dev/tty to receive the expected carriage return. If there is no terminal associated with the frecover process, frecover aborts because it cannot open /dev/tty. This is especially a problem for those who use a chgvol script when using -c , where the operator may likely not leave open the window from which they started an frecover of a large number of volumes. PHCO_13839: New functionality to support networking features in 10.20. PHCO_9228: The fbackup command on HP-UX 10.20 may hang when log or group names exceed 8 characters in length in the /etc/passwd or /etc/group files. This patch corrects this problem. PHCO_9188: The fbackup command on HP-UX 10.20 cannot read old volume headers written by a pre-10.20 fbackup execution. The operator will see the following error: fbackup(3205): unable to read a volume header Note the operator will see this error as well if the tape is new or has been used by another backup utility such as cpio. SR: 8606164293 8606127419 1653190629 1653294280 5003457515 4701360347 4701411835 5003423483 5003375626 5003403410 4701378117 1653189639 1653191163 Patch Files: /usr/lib/nls/msg/C/fbackup.cat /usr/sbin/fbackup /usr/sbin/fbackuprdr /usr/sbin/fbackupwrtr /usr/lib/nls/msg/C/frecover.cat /usr/sbin/frecover /sbin/frecover /usr/share/man/man1m.Z/fbackup.1m /usr/share/man/man1m.Z/frecover.1m what(1) Output: /usr/lib/nls/msg/C/fbackup.cat: None /usr/sbin/fbackup: $Revision: 78.18.1.11 $ PATCH_10_20: hpux_rel.o util.o main.o main2.o main3. o reset.o parse.o search.o inex.o pwgr.o fli st.o 01/05/23 /usr/sbin/fbackuprdr: $Revision: 78.18.1.11 $ PATCH_10_20: hpux_rel.o reader.o 01/05/23 /usr/sbin/fbackupwrtr: $Revision: 78.18.1.11 $ PATCH_10_20: hpux_rel.o util.o writer.o writer2.o ta pe.o rmt.o vdi.o 01/05/23 /usr/lib/nls/msg/C/frecover.cat: None /usr/sbin/frecover: $Revision: 78.22.1.10 $ PATCH_10_20: main.o utilities.o files.o io.o volhead ers.o hpux_rel.o rmt.o vdi.o 01/05/23 /sbin/frecover: $Revision: 78.22.1.10 $ PATCH-PHCO_18644 for 10.20; for 10.30, 11.x compatib ility libc.a_ID@@/main/r10dav/libc_dav/libc_ dav_cpe/9 /ux/core/libs/libc/archive_pa1/libc.a_ID Jul 8 1999 15:44:31 PATCH_10_20: main.o utilities.o files.o io.o volhead ers.o hpux_rel.o rmt.o vdi.o 01/05/23 /usr/share/man/man1m.Z/fbackup.1m: None /usr/share/man/man1m.Z/frecover.1m: None cksum(1) Output: 3976780561 13720 /usr/lib/nls/msg/C/fbackup.cat 1717646248 77824 /usr/sbin/fbackup 723916642 16384 /usr/sbin/fbackuprdr 2023072917 73728 /usr/sbin/fbackupwrtr 155023914 9686 /usr/lib/nls/msg/C/frecover.cat 3146094178 106496 /usr/sbin/frecover 3869291265 335872 /sbin/frecover 1278687625 13620 /usr/share/man/man1m.Z/fbackup.1m 4244624383 8429 /usr/share/man/man1m.Z/frecover.1m Patch Conflicts: None Patch Dependencies: s700: 10.20: PHKL_22285 PHKL_23258 s800: 10.20: PHKL_22286 PHKL_23259 Hardware Dependencies: None Other Dependencies: None Supersedes: PHCO_9188 PHCO_9228 PHCO_13839 PHCO_14176 PHCO_16031 PHCO_17865 PHCO_18135 PHCO_21263 Equivalent Patches: PHCO_23854: s700: 11.00 s800: 11.00 Patch Package Size: 710 KBytes Installation Instructions: Please review all instructions and the Hewlett-Packard SupportLine User Guide or your Hewlett-Packard support terms and conditions for precautions, scope of license, restrictions, and, limitation of liability and warranties, before installing this patch. ------------------------------------------------------------ 1. Back up your system before installing a patch. 2. Login as root. 3. Copy the patch to the /tmp directory. 4. Move to the /tmp directory and unshar the patch: cd /tmp sh PHCO_23861 5a. For a standalone system, run swinstall to install the patch: swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHCO_23861.depot By default swinstall will archive the original software in /var/adm/sw/patch/PHCO_23861. If you do not wish to retain a copy of the original software, you can create an empty file named /var/adm/sw/patch/PATCH_NOSAVE. WARNING: If this file exists when a patch is installed, the patch cannot be deinstalled. Please be careful when using this feature. It is recommended that you move the PHCO_23861.text file to /var/adm/sw/patch for future reference. To put this patch on a magnetic tape and install from the tape drive, use the command: dd if=/tmp/PHCO_23861.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: None