Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!gatech!hubcap!ncrcae!ncr-sd!hp-sdd!hplabs!sdcrdcf!trwrb!scgvaxd!ashtate!unisol!haral
From: haral@unisol.UUCP (Haral Tsitsivas)
Newsgroups: comp.unix.questions
Subject: Dump and Cpio for backups
Message-ID: <279@unisol.UUCP>
Date: Thu, 25-Jun-87 04:01:43 EDT
Article-I.D.: unisol.279
Posted: Thu Jun 25 04:01:43 1987
Date-Received: Sat, 27-Jun-87 02:05:44 EDT
References: <1007@killer.UUCP>
Reply-To: haral@unisol.UUCP (Haral Tsitsivas)
Organization: UniSolutions Associates, Culver City, CA
Lines: 22
Keywords: dump, cpio, /etc/dumpdates


In article <1007@killer.UUCP>  jfh@killer.UUCP (John Haugh) writes:
>We recently had to backup a file system over Ethernet using cpio and when
>dump(1)ing the system today, dump wanted to backup everything.  I realize
>that this is because I told cpio to reset the access times on the files
>after saving them.  Now for the questions.

Ahemm....  There is no dump(1) but there is a dump(8).  Actually, there is a
dump(1) under System V but the manual entry says "dump selected parts of an
object file" which does not seem to backup a filesystem.  Dump(8) does not
look at your last access time... It looks at the last modification time and
the date of your last backup as defined in the file /etc/dumpdates.  From
the manual again: "Dump copies to magnetic tape all files changed after a
certain date in the filesystem".  "Files changed" does not refer to access
times.  If you want to reset dump's idea of the last backup time (presumably
to the time of a backup done with cpio) edit the file /etc/dumpdates by hand
and modify the last dump date.

--Haral Tsitsivas
  UniSolutions Associates
  ...!seismo!scgvaxd!ashtate!unisol!haral
  (213) 641-6739