
My Laptop's Hard Disk croaked yesterday. The device is less than a year old but it decided to destroy itself. No idea why. So backup early and often people. You will be thankful one day. I'm glad I have _any_ backup at all. Even if it is 3 or more months old. Regards

Actually now just looking at the backup archive date it is only just over 2 months old. Still even loosing two months of data is annoying. Regards Oliver Jones wrote:
My Laptop's Hard Disk croaked yesterday. The device is less than a year old but it decided to destroy itself. No idea why. So backup early and often people. You will be thankful one day. I'm glad I have _any_ backup at all. Even if it is 3 or more months old.
Regards
_______________________________________________ wlug mailing list | wlug(a)list.waikato.ac.nz Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug

On Wed, Sep 28, 2005 at 01:07:29AM +1000, Oliver Jones wrote:
My Laptop's Hard Disk croaked yesterday. The device is less than a year old but it decided to destroy itself. No idea why. So backup early and often people. You will be thankful one day. I'm glad I have _any_ backup at all. Even if it is 3 or more months old.
Backups are one of those things you keep telling yourself you should really do at some point... For people who have their own LAN at home, maybe just a desktop and a server, I recommend using 'rsync' to make a copy of any important directories across the network. If you are at all familiar with 'scp', then rsync is very similar to use, but has the advantage that it won't re-copy over any files that already exist unless they have changed. Actually getting around to writing a quick backup script also helps you think about which data on your computer is worth keeping "forever". For me it turned out that the only really critical stuff I'd want to keep is my digital photos. The /etc directory is useful too, although I could recreate similar config files myself. I wouldn't be able to recreate my photos. If you have a LAN, but don't know how to use command-line tools like scp/rsync, you can browse across your network in gnome by opening a location such as "ssh://servername/home/username". If you don't have a LAN, write stuff to CDs. See the wiki page http://www.wlug.org.nz/BackupNotes for more links/ideas and (as always) feel free to add to the page if you have questions or contributions. John

John R. McPherson wrote:
If you don't have a LAN, write stuff to CDs.
If you're going to take this option, make sure you get good CDs, or back up often. I have a few CDs which are not even 5 years old and can no longer be read. They have been kept in their cases in my drawer virtually their entire lives, have not been abused in any way, but will mount with only two files on them called "???????? ????". Fortunately they weren't important, because I back up more frequently than once every couple of years :) I'd also like to ask the LUG about pendrives. I back up primarily to a 1 GB Legend USB pendrive, which is convenient for obvious reasons. Does anyone have any horror stories about pendrives dying? I also back up to a laptop on my network (maybe I'm a bit paranoid), but I like being able to take my backup with me wherever I go. You know, in case I come home and find the house on fire... Regards, Bnonn

I'd also like to ask the LUG about pendrives. I back up primarily to a 1 GB Legend USB pendrive, which is convenient for obvious reasons. Does anyone have any horror stories about pendrives dying? I also back up to a laptop on my network (maybe I'm a bit paranoid), but I like being able to take my backup with me wherever I go. You know, in case I come home and find the house on fire...
I've not heard of any horror stories. Of course, pen drives are easy to lose / stand on / etc, so you shouldn't rely on them as your only method of backup. But as another backup, along with backing up to your lan, it is a good solution.

I'd also like to ask the LUG about pendrives. I back up primarily to a 1 GB Legend USB pendrive, which is convenient for obvious reasons. Does anyone have any horror stories about pendrives dying? I also back up to a laptop on my network (maybe I'm a bit paranoid), but I like being able to take my backup with me wherever I go. You know, in case I come home and find the house on fire...
Principle thing I've heard about pen drives is the data getting corrupted but this is at the time of writing to them not later so as long as you check the data is OK it should be fine - I recommend removing and then testing on another computer for critical data.

Principle thing I've heard about pen drives is the data getting corrupted but this is at the time of writing to them not later so as long as you check the data is OK it should be fine - I recommend removing and then testing on another computer for critical data.
This primarily happens if you don't cleanly unmount the volume. Never unplug a USB mass storage device from a machine if you have just written to it, unless you unmount it cleanly (by running 'unmount /path/to/mountpoint' in a shell, right clicking on it and pressing 'eject' in nautilus or similar, or using Windows' unmount removable device option). Basically, you can't guarantee that writes have been committed to disk when the copy command completes. Disk cache and so on mean that there's still quite a bit going on. You can run 'sync' a few times on the command line to check that all pending writes have been written. This was especially bad on USB1.x devices. USB2, having significantly faster throughput available, isn't as bad, but it can still happen.

This primarily happens if you don't cleanly unmount the volume. Never unplug a USB mass storage device from a machine if you have just written to it, unless you unmount it cleanly (by running 'unmount /path/to/mountpoint' in a shell, right clicking on it and pressing 'eject' in nautilus or similar, or using Windows' unmount removable device option).
Yes I agree. I have had corruption once though even when I did do this... but I should have said you should always unmount also. Ian

John R. McPherson wrote:
Actually getting around to writing a quick backup script also helps you think about which data on your computer is worth keeping "forever". For me it turned out that the only really critical stuff I'd want to keep is my digital photos. The /etc directory is useful too, although I could recreate similar config files myself. I wouldn't be able to recreate my photos. For reference (hopefully someone can use it for that purpose) here is my rsync backup script:
---------------------- #!/bin/sh export RSYNC='/usr/local/bin/rsync -a -z -u -v -4 --delete-after' # Back up currently installed packages information (FreeBSD) # If I need to rebuild the box, I like to know what was on it :) /usr/sbin/pkg_info > /etc/pkg_info # Back up WWW Data ${RSYNC} /www/usr/* /rsync/www # Back up MAIL Data ${RSYNC} /home/vpopmail/* /rsync/mail # Back up rsync realted scripts, because I hate having to recreate them! ${RSYNC} /root/bin/* /rsync/bin # Back up SubVersioN Data ${RSYNC} /pub/svn/* /rsync/svn # Back up configuration files ${RSYNC} /etc/* /rsync/etc ${RSYNC} /usr/local/etc/* /rsync/usr.local.etc <<EOF

A workmate told me about a tool today called rdiff-backup (part of Fedora Extras) that uses the rsync protocol to do differential backups. Sounds cool. I'm going to do a little experimentation. Basically so I can do backups of my remote server over my DSL link (and reverse, backup my important local files to my remote server). Regards Drew Broadley wrote:
John R. McPherson wrote:
Actually getting around to writing a quick backup script also helps you think about which data on your computer is worth keeping "forever". For me it turned out that the only really critical stuff I'd want to keep is my digital photos. The /etc directory is useful too, although I could recreate similar config files myself. I wouldn't be able to recreate my photos.
For reference (hopefully someone can use it for that purpose) here is my rsync backup script:
---------------------- #!/bin/sh
export RSYNC='/usr/local/bin/rsync -a -z -u -v -4 --delete-after'
# Back up currently installed packages information (FreeBSD) # If I need to rebuild the box, I like to know what was on it :) /usr/sbin/pkg_info > /etc/pkg_info
# Back up WWW Data ${RSYNC} /www/usr/* /rsync/www
# Back up MAIL Data ${RSYNC} /home/vpopmail/* /rsync/mail
# Back up rsync realted scripts, because I hate having to recreate them! ${RSYNC} /root/bin/* /rsync/bin
# Back up SubVersioN Data ${RSYNC} /pub/svn/* /rsync/svn
# Back up configuration files ${RSYNC} /etc/* /rsync/etc ${RSYNC} /usr/local/etc/* /rsync/usr.local.etc
<<EOF
_______________________________________________ wlug mailing list | wlug(a)list.waikato.ac.nz Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug

See the wiki page http://www.wlug.org.nz/BackupNotes for more links/ideas and (as always) feel free to add to the page if you have questions or contributions.
I've documented rsync on this page for those interested and given a quick example of how to make copies using this tunelled over ssh. Ian
participants (6)
-
Bnonn
-
Daniel Lawson
-
Drew Broadley
-
Ian McDonald
-
John R. McPherson
-
Oliver Jones