Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!hplabs!hpcc05!hpgva1!hpuamsa!franks From: franks@hpuamsa.neth.hp.com (Frank Slootweg CRC) Newsgroups: comp.sys.hp Subject: Re: Do NOT use ftio or cpio for backups Message-ID: <28510054@hpuamsa.neth.hp.com> Date: 11 Jun 91 15:49:59 GMT References: Organization: HP-Sales Office-The Netherlands Lines: 41 Just some quick notes : problem #1: memory usage by ftio and cpio I don't think that cpio uses shared memory. It uses normal (i.e. virtual) memory. As long as you have enough virtual memory there is no problem. problem #2: multiply linked files with inodes >64k For ftio : I *think* you are right (SR# 1650147959). Can investigate if needed. For cpio : This was fixed with some clever algorithms in 6.5 (300) and 7.0 (800). The tape format is still compatible. Are you sure you have a new and stock (and HP :-)) cpio? At some release (can find out number if needed) there was some problem with getting the wrong cpio. If I remember correctly a "what" on the wrong cpio said something like "update version". Customers were informed at the time about this wrong version and how to get a good one. problem #3: can not (re)set the change-of-inode time You are right. This is a fundamental one. Any backup utility can only be as good as the OS on which it runs. In this respect UNIX (not just HP-UX) is just not good. > in the HP manuals, they list 4 different ways of doing backups. the > first two are cpio and ftio. i cant believe that with such > fundamental problems with cpio/ftio that they would even suggest using > them. the other two methods that they suggest are dd and fbackup. Can you please be specific (i.e. which manual, edition and page)? The 7.0 HP-UX System Administration Tasks manual for the Series 300 (you said 7.05, so I assume 300/400) recommends (on page 11-5) to use "fbackup". Hope this helps somewhat. If you want me to investigate then mail me and I will see what I can do. Frank Slootweg, HP, Dutch Customer Response Center.