incremental backup
in [Slackware]
|
Prev: libgtk-x11 (slackware 12)
Next: Dell desktops
From: Helmut Hullen on 29 Mar 2010 14:09 Hallo, Vwaju, Du meintest am 29.03.10: > I'm running 13.0 on my workstation, and making a backup plan > (following some hints in Running Linux (O'Reilly)). > For daily incremental backups, I tested the following command: .... What about "rsnapshot"? You don't need to reinvent the wheel ... http://rsnapshot.org <http://helmut.hullen.de/filebox/Linux/slackware/ap/rsnapshot-1.3.1-i486-10hln.tgz> Viele Gruesse Helmut "Ubuntu" - an African word, meaning "Slackware is too hard for me".
From: Charles Polisher on 30 Mar 2010 19:05 On 2010-03-29, Vwaju <slack(a)rcn.com> wrote: > For daily incremental backups, I tested the following command: > > # output full path for all files modified in the last 24 hours > > find / -mtime -1 \! -type d -print > /tmp/filelist.daily > > To my surprise, this command output the names of over 40,000 files! > (This, on a day when I did almost nothing on the system!) > > Almost half of the filenames output are from the /proc file system > > most of the othes are, variously under the following directories > > /etc > /usr/share/mime > /dev/char > /dev/.udev > /sys/devices/virtual > /sys/devices/LNXSYTM > /sys/devices/pci0000:00 > /sys/dev/char > /sys/bus > /sys/class > /sys/kernel > /sys/module > > I'm guessing that I don't really want all of this in a daily > incremental backup. What would a reasonable policy be? Vwaju, The -xdev switch on the find command will solve your problem. It will prevent descending into other file systems, such as /proc. Best regards, -- Charles
From: Eef Hartman on 31 Mar 2010 05:53
Vwaju <slack(a)rcn.com> wrote: > I'm running 13.0 on my workstation, and making a backup plan > (following some hints in Running Linux (O'Reilly)). > > For daily incremental backups, I tested the following command: > > # output full path for all files modified in the last 24 hours > > find / -mtime -1 \! -type d -print > /tmp/filelist.daily Put at least a -xdev (do NOT cross devices) in that find to exclude the pseudo file systems /dev, /proc and/or /sys If you have any _real_ other filesystems mounted, like /home, you will have to add them to the list of directories (although I mostly do them in separate backups, that is: I've got backup's for / (root fs), /opt (optional software), /home etc. > I'm guessing that I don't really want all of this in a daily > incremental backup. What would a reasonable policy be? Apart from logfiles, / doesn't change hard, so doesn't have to be backup'ed too often, just make one after you really change things, the same goes for most "system" file systems, you KNOW when things have been changed there so when to make backup's OF them. The files normally to backup are your own ones, like /home or wherever you stored your own files. For me that is my music library (/music), my video library (/video) and my home dir (/home), all of which are separate file systems. -- ******************************************************************* ** Eef Hartman, Delft University of Technology, dept. SSC/ICT ** ** e-mail: E.J.M.Hartman(a)tudelft.nl - phone: +31-15-278 82525 ** ******************************************************************* |