Hi,
Thanks for your detailed answer, I read all of it :-)
To make it short ...
I never thought about using more than one configuration, thanks for pointing
this out, it would need more space, but nowadays diskspace is cheap.
Lsync sounds nice too, I have one or two offsite locations I may use for
syncing. But the warning to not use it productive scares me a little bit.
Sparse bundles as far as I know don't exist in linux . As far as I know you
could use an hfs+ volume within linux, but normally there is no real reason
to do this for a linuxuser (if he doesn't want to share a partition between
Mac and a Linux box)
I have a list of some backup programs I try to go trough and test, I hope on
weekend I have some time to start my backup.
If I have any further questions I'll post again.
Thanks again for your answer!
Greetings from Austria,
Harald
-Ursprüngliche Nachricht-
Von: lbackup-discussion-boun...@lists.connect.homeunix.com
[mailto:lbackup-discussion-boun...@lists.connect.homeunix.com] Im
Auftrag von henri
Gesendet: Dienstag, 18. Jänner 2011 11:43
An: lbackup-discussion@lists.connect.homeunix.com
Betreff: Re: [lbackup-discussion] Some beginner questions (OS backup
rotation)
This reply is quite long. As such a very brief summary is provided at the
start.
However, I would recommend that if you are going to use LBackup that you
read the entire email so that (hopefully) the advantages and disadvantages
are clear.
Summarized version :
- LBackup will work on Ubuntu.
- Do not move any snapshots. Instead copy or archive them (compression is
optional)
- No example script is included with LBackup yet.
- If you develop one please contribute it back to the project.
- LPrune is an LBackup component. It is still under development.
- If you are interested in assisting with development let me know.
- LSync is a solution which may be closer to what you are looking for?
- LBackup supports chained backups (for sending data off-site).
- LBackup supports multi-destination very well for the kind of scenario
you
provided.
- If you have problems then please let me know.
- If a Mac OS X system as the backup server is a then :
- You gain access to sparse bundles which allow quick snap shooting of
the
backup set.
Extended version :
Has someone tested it on Ubuntu LTS 10.04? A lot of your documentation
deals with Mac Os and some rare pages also with debian, which is near to
ubuntu, so I hope the best.
LBackup has been tested with Ubuntu LTS 10.04. However, it has only been
tested with the Ubuntu system being a backup client not as a server. It is
very likely that this particular version of Ubuntu will work as a backup
server
just fine, although to my knowledge lbackup it has not yet been tested
with
this specific version of Ubuntu in this configuration.
LBackup works on a variety of Ubuntu versions and I have not seen the .deb
installer for lbackup fail on a Ubuntu system to date. If something goes
wrong then please reply to this message and in the mean time refer to the
instructions for installing lbackup from source :
http://www.lbackup.org/source
Another technical question: I want to have a set of snapshots like
rsnapshot does 1 daily snapshot, some weekly snapshots, for older data
only some montly snapshots, yearly snapshots
Is there a way to
accomplish
this,
Yes, the easiest way is to have three backup configurations each with a
different schedule and number of backups. For example, one backup config
for daily, weekly, month and yearly.
The advantage of this approach which at first seems counter intuitive, is
that
you are able to have multiple backup sets for backup configuration being
stored on different physical media, which may be separated geographically
(eg. The data in different physical locations).
In essence, this approach allows you to keep the daily backups on-site and
the monthly backups off-site. Basically, LBackup has the ability to deal
with a
number of different backup policy requirements. This allows you to comply
(in some cases more easily) with your organizations backup policy.
It is possible to configure backups to DAS every 40 min, every week, every
month and every year. Yet, each of these sets could go to different media
for
additional redundancy. It is also possible to decide on physical proximity
to
your backups based upon the frequency of the backup. For instance, if you
have a high speed network to a different building close by or on the other
side of the city you could perform frequent backups via this network. Then
if
your link to another country is slower then these backups could be
automatically mirrored off site via a the internet at less frequent
intervals.
In addition, when the monthly backup is running (which could be a lot of
data) the backups each 40 min will still carry
