Search the FAQ Archives

3 - A - B - C - D - E - F - G - H - I - J - K - L - M
N - O - P - Q - R - S - T - U - V - W - X - Y - Z
faqs.org - Internet FAQ Archives

comp.sys.hp.hpux FAQ
Section - 5.2.3 Why do cpio/tar/dump/pax all backup to tape painfully slowly?

( Single Page )
[ Usenet FAQs | Web FAQs | Documents | RFC Index | Business Photos and Profiles ]


Top Document: comp.sys.hp.hpux FAQ
Previous Document: 5.2.2 How can I use dump with a DDS tape?
Next Document: 5.2.4 What CD burning software is available?
See reader questions & answers on this topic! - Help others by sharing your knowledge
Added: 04/17/01

cpio/tar = VERY VERY OLD - never designed for DDS or DLT[TM]

fbackup/ftio = designed for Gb backups and modern tape drives

However, the default for fbackup is 1/2" magtapes, which almost no one
uses anymore.  ALWAYS use a config file for fbackup with at least these
options:

  blocksperrecord     256
  records             32
  checkpointfreq      1024
  readerprocesses     6
  maxretries          5
  retrylimit          5000000
  maxvoluses          200
  filesperfsm         2000

Check the manpage for fbackup for other parameters, including what to do
when you run out of tape (the chgvol parameter).

You need huge block sizes for modern tapes.  Try ftio (block size limited
only by hardware), pax (block sizes up to 32k), tar (which is 10k, by
design) or cpio -B which changes from 512 to 5k (but still too small).

cpio, tar, dump, pax and similar utils can NEVER backup large files and
are single processes whereas fbackup can read from 6 different files at
the same time.

Note, the large record size (blocksperrecord), checkpointfreq, and
filesperfsm also contribute to tape overhead.

User Contributions:

Comment about this article, ask questions, or add new information about this topic:

CAPTCHA




Top Document: comp.sys.hp.hpux FAQ
Previous Document: 5.2.2 How can I use dump with a DDS tape?
Next Document: 5.2.4 What CD burning software is available?

Single Page

[ Usenet FAQs | Web FAQs | Documents | RFC Index ]

Send corrections/additions to the FAQ Maintainer:
hpux.faq@gmail.com





Last Update March 27 2014 @ 02:11 PM