[ale] Rasberry Pi Backup Rebuild

JD jdp at algoloma.com
Fri Nov 7 06:02:57 EST 2014


Trust, but validate.

I use rdiff-backup and have a script that runs daily to show the completion
status (start/end times and amount of data backed up) of all backup jobs.
Additionally, each backup job outputs the run status ... but I ignore those
(delete them) unless there is an issue.

Happiness is seeing something like this for every machine:

=== Backing up  lubuntu ===
StartTime 1415343786.00 (Fri Nov  7 02:03:06 2014)
EndTime 1415343974.65 (Fri Nov  7 02:06:14 2014)
ElapsedTime 188.65 (3 minutes 8.65 seconds)
TotalDestinationSizeChange 23088828 (22.0 MB)


=== Backing up  xen41 ===
StartTime 1415346615.00 (Fri Nov  7 02:50:15 2014)
EndTime 1415346661.60 (Fri Nov  7 02:51:01 2014)
ElapsedTime 46.60 (46.60 seconds)
TotalDestinationSizeChange 2147492 (2.05 MB)



On 11/06/2014 09:38 PM, Jonathan Meek wrote:
> Hey everyone,
> 
> I have a Raspberry Pi that I was using as a backup solution for my stuff.
> Recently, the Pi somehow quit booting into OS.
> 
> Literally, didn't realize my backups were not happening until I went to wipe the
> computer and double-checked the backup to see what my latest backups were before
> wiping the system :)
> 
> I was using deja-dup to point to the Pi over the network using SSH to do my
> backups. Deja-dup just said it completed the job but never indicated it couldn't
> contact the host.
> 
> So my question is how do I move forward in using this RPi as a backup solution
> but avoid a repeat of this 'near-miss' I just had.
> 
> EXTRA INFO: I am using the same SD card just re-formatted, the card itself
> seemed fine but for some reason lost the boot partition from one of the config
> files.
> 


More information about the Ale mailing list