Hi Maurits,
please can you give me the location of that branch if it is public?
I wrote an rsync based incremental backup of the blobstorage using
hardlinks to safe space but keep the whole tree per backup.
It is not published yet because I need to rework it for the case, the
destination is on a different drive or server and (specially for me) a
solution if the local backup is synced with a mirror. In this case it
is important to recreate the links at the destination as links too,
which is not solved yet.
I send you my code directly via mail due to some time limitation.
There is no license on the code by me. Feel free to use this as
inspiration.
Armin
Am 24.08.2011 um 12:24 schrieb Maurits van Rees:
Op 23-08-11 19:42, Karl Johan Kleist schreef:
Dear Plone fellows,
I've checked in a small enhancement of
collective.recipe.backup:repozorunner.py
(http://dev.plone.org/collective/changeset/243743) as to handle
filestorage
files that reside in their own directory. This is the default
behavior when
using collective.recipe.filestorage.
Who knows the e-mail addresses of the maintainers Reinout van Rees
and
Maurits van Rees? I guess I should notify them, and if they approve
they
might even release a new version.
Hi, that would be me. :) You can mail maurits at vanrees.org or use
the contact form on my website http://maurits.vanrees.org
But you've got my attention now via this mailing list and I noticed
the changes in the collective mailing list. I will have a look at
it. Can you try adding a test for this?
I am now busy on a branch to add blobstorage backup and restore
support though, so I am focusing on that first.
Thanks,
#!/bin/sh
#blobstoragesnapshot
VERSION="0.1.3"
echo "blobstoragesnapshot Version "$VERSION
echo "rsync based Plone blobstorage timemachine companion for repozo"
#20110226_19-35-31 by Armin Carl Stross-Radschinski, [email protected]
#a rsync based Plone blobstorage timemachine companion for repozo
#Using rsync to make hardlinked snapshots of your blobstorage
#based on
#http://blog.interlinked.org/tutorials/rsync_time_machine.html
#
#Description
#Every snapshot is a full copy of the state of the blobstorage
#make sure your blobstorage is backuped AFTER the run of repozo AND
#no packing of the database has taken place until the
blobstoragesnapshot
#is finished.
#Usually no file in the blobstorage is deleted until a pack is initiated
#keeping the prerequisite for a undo.
#Take care!
#ToDo
#take timestamp, source and destination via parameter to match repozo
backups
#initiated by backup recipe
#
#History
#rev 0.1.3 20110226_20-10-59 by acsr
# date format changed to match the repozo timestamp
#rev 0.1.2 20110226_19-30-00 by acsr
# initial test on Ubuntu, destination directory creation added
#rev 0.1.1 20110226_19-41-36 by acsr
# first release working without ssh
date=`date "+%Y-%m-%d-%H-%M-%S"`
HOME="/home/goa/instances/everweb/var/blobstorage/"
DEST="/home/goa/instances/everweb/var/backupsblobstorage/"
# --exclude-from=$HOME .rsync/exclude \
mkdir -p $DEST
rsync -azP \
--delete \
--delete-excluded \
--link-dest=$DEST"current" \
$HOME $DEST"incomplete_blobstorage-$date"
mv $DEST"incomplete_blobstorage-$date" $DEST"blobstorage-$date"
rm -f $DEST"current"
ln -s $DEST"blobstorage-$date" $DEST"current"
#from the comments (to be tested)
#how to restore data from the backup
#this will be the simplest restore option. If you want to restore the
whole thing, you could do:
# rsync -aP /path/to/backup/folder/ /path/to/restore
#endblobstoragesnapshot
--
Armin Carl Stroß-Radschinski, Dipl. Designer
acsr industrialdesign, Landgrafenstraße 32, 53842 Troisdorf, Germany
Telefon +49 (0) 22 41 / 94 69 94, FAX +49 (0) 22 41 / 94 69 96
eMail [email protected] - http://www.acsr.de
UST. ID Nr: DE154092803 (EU VAT ID)
_______________________________________________
Product-Developers mailing list
[email protected]
https://lists.plone.org/mailman/listinfo/plone-product-developers
