|
Ede,
Vielen dank! My German is _very_ rusty,
unfortunately.
I think your script is an excellent helper/tool for
the already great duplicity. I will probably leverage it to help me in my
backup plans.
However, the intent of #4, below, was "what needs
to be protected/otherwise-backed-up in order to recover files backed-up by
duplicity"? For example, what happens if the linux server I am backing-up
is completely destroyed (say by a natural disaster)? I no longer have that
host, nor any local files to it (PGP Keys, duplicity software, etc.). What
should I export/copy/backup elsewhere so that I can recover my duplicity
backups? Export the PGP keys? The private ones? The public
ones? The passphrase? What else???
Thanks again for your kind reply!
-AJ
----- Original Message -----
Sent: Monday, March 03, 2008 11:11
AM
Subject: ftplicity 1.3b to be released -
Re: [Duplicity-talk] Newbie questions...
Hello AJ,
regarding comment number 4 .. you can use a
wrapper like ftplicity
(simplified user frontend for duplicity ftp
backups) to make the process
a little bit more straight forward. Btw. I am
finishing a new release of
ftplicity right now and will put it on
sourceforge. A list of changes
and the location will be send top this list
then.
Regards Ede
--
> First off, this seems like a great
utility. Great work, guys!
>
> A couple of questions to make
sure I'm using it correctly and efficiently, if I may?
>
> 1) Do I
assume that duplicity will keep all files, regardless of "age", unless I
periodically clean-them-up with the "remove-older-than"
option?
>
> 2) WRT backup strategy then, if I choose to create a
new full-backup every couple of weeks, I understand that I then use
"remove-all-but-n-full" to remove old full backup-sets AND any old
incrementals that were based upon them, right?
>
> 3) Is there any
way to make the initial d/l of the signatures file(s) more efficient? If
I use archive-dir, and keep a copy of signatures locally, will this eliminate
that initial requirement to d/l the signatures from the target server (and
make the process more efficient)?
>
> 4) A "Newbie Guide to Backup
and Restore with Duplicity" would be great to avoid pitfalls. I think I
need to understand what is required on the SOURCE-side to restore, should I
lose the local server running the duplicity utility. For example, what
keys and passphrases need to be backed-up so I could image a minimal linux
host in an emergency and recover the data from the target
host?
>
> Thanks again for all the hard work. It looks like
it's shaping-up to be a great, great utility!
>
>
-AJ
>
>
>
>
------------------------------------------------------------------------
>
>
_______________________________________________
> Duplicity-talk mailing
list
> address@hidden
>
http://lists.nongnu.org/mailman/listinfo/duplicity-talk
>
--
public class WhoDidIt{ // A comment. I love comments
private static Person sender;
public static void main
(String[] foo){
sender = new Person();
sender.setName(new String[]{"Edgar", "Soldin"});
Address address
= new Address();
address.setStreet("Stadtweg 119");
address.setZip(39116);
address.setCity("Magdeburg");
address.setCountry("Germany");
sender.setAddress(address);
sender.setMobilePhone("
+49(0)171-2782880 ");
sender.setWebSiteUrl(" http://www.soldin.de ");
sender.setEmail(" address@hidden
");
sender.setPGPPublicKey(" http://www.soldin.de/edgar_soldin.asc
");
sender.setGender(true);
System.out.println(sender.toString());
}
}
|