[Digikam-users] Best Way to Backup

[H. Jürgen Karbach]

Hello,

I‛m trying „bup‟ with „kup‟ as UI.
bup is git-based, can be automated and uses hardlinks to get small backup 
files. I‛ll see, if it matches it‛s promises.

Btw., how are you recording your work between the backups?
Is there a logging capability?
Good to know, which files are affected.
Better to know, which steps has been done to each file.

I am dreaming of a detailed record of all steps,
that will be work like a script or batch if needed. 
Yes, I know I‛m lazy. ;) (sorry, I like it convenient)
-- 
H. Jürgen Karbach

Am Freitag, 14. Februar 2014, 10:45:52 schrieb Simon Cropper:
> On 13/02/14 13:30, Henrique Santos Fernandes wrote:
> > Hello,
> > 
> > How is the best way to backup Digikam?
> > 
> > I mostly use image tags and its configured to apply to the image. But
> > for vídeos i guess it does not work.
> > 
> > I am also thinking of using digikam in mysql. If so the backup would be
> > only the database and pictures?
> > 
> > Thanks
> > 
> > []'sf.rique
> > Henrique Santos Fernandes
> > 
> > 
> > _______________________________________________
> > Digikam-users mailing list
> > Digikam-users at kde.org
> > https://mail.kde.org/mailman/listinfo/digikam-users
> 
> Henrique,
> 
> DigiKam works with albums, which are really just directories, when not
> using MySQL your database usually resides in the top album you identify.
> Personally I have one root album 'images' above my home, work and other
> albums.
> 
> I save my metadata to file (if JPG) but also XMP files (if NEF). If you
> have videos the metadata for these will be stored database but not on
> the file or in a XMP file.
> 
> In order to back up these files treat them like any other file. Backup
> the root directory with whatever backup system you currently use to save
> your electronic files. Ensure you keep several sets -- I have daily
> backups of my entire computer system, weekly+ad-hoc monthly backups and
> sets on different computers.
> 
> Remember that it might take you a few days or even a week to notice a
> file has gone missing or the database has become corrupt. The only way
> to recover from this situation is going back to a previous backup.
> 
> The method you use to backup is personal and usually dictated by your
> skill and experience. Recommendations for what program to use will
> result in many responses for a wide variety of applications. If you are
> on Linux, look into your repositories for suggestions and trial a few
> applications.
> 
> Personally I use rsync within a script... the actual command is...
> 
> rsync -rltvz --stats --delete --ignore-errors $FROM $TO