We have new DS20Es with Tru64 v5.1 (patch kit 2) and intend using "cpio" for our backups (as we are doing in the existing NCR hosts). However, I have noticed a strange difference. On the NCR Unix, I use "cpio -ocvB -O{tape drive} >{output file} 2>{error file}" to copy to tape and the "error file" holds the number of blocks. After this, I read back the tape with "cpio -itv -I{tape drive} >{output file} 2>{error file}" and the "error file" again holds the number of blocks; thus making the job of checking scheduled backup (done off-office hrs in our case) logs quite easy.
On the Tru64, the whole process works with cpio needing "-itvB" to read back. However, I have noticed that the error file during copying contains NOTHING and the blocks are APPENDED to the output file. Also, on read back, both the output and error files are NOT written DURING the read back process (as in the case of our NCR system) but AFTER reading the entire backup.
Any idea whether this is how cpio functions in Tru64 or am I missing out on some parameter?
Harihar K
(Network Manager)
Received on Wed Jul 25 2001 - 05:37:11 NZST