Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #5087 > unrolled thread
| Started by | James Mills <prologic@shortcircuit.net.au> |
|---|---|
| First post | 2011-05-11 09:57 +1000 |
| Last post | 2011-05-11 08:45 +0200 |
| Articles | 2 — 2 participants |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Python backup programs? James Mills <prologic@shortcircuit.net.au> - 2011-05-11 09:57 +1000
Re: Python backup programs? Laurent Claessens <moky.math@gmail.com> - 2011-05-11 08:45 +0200
| From | James Mills <prologic@shortcircuit.net.au> |
|---|---|
| Date | 2011-05-11 09:57 +1000 |
| Subject | Re: Python backup programs? |
| Message-ID | <mailman.1389.1305071897.9059.python-list@python.org> |
On Wed, May 11, 2011 at 9:00 AM, Dan Stromberg <drsalists@gmail.com> wrote: > > What are your favorite backup programs written, in whole or in part, in > Python? > > What do you like about them? Dislike about them? > > Are there any features you wish your backup program had, whether in Python > or not? Recently I wrote a simple backup system for a client using a mixture of Python and Bash using rsync, ssh and pptp. (Not packaged well enough to show source though) It works very well and does the job. cheers James -- -- James Mills -- -- "Problems are solved by method"
[toc] | [next] | [standalone]
| From | Laurent Claessens <moky.math@gmail.com> |
|---|---|
| Date | 2011-05-11 08:45 +0200 |
| Message-ID | <iqdbas$r66$1@news.univ-fcomte.fr> |
| In reply to | #5087 |
Le 11/05/2011 01:57, James Mills a écrit :
> On Wed, May 11, 2011 at 9:00 AM, Dan Stromberg<drsalists@gmail.com>
wrote:
>>
>> What are your favorite backup programs written, in whole or in part, in
>> Python?
My favorite one is the one I wrote myself for myself ;)
The point I like :
1. the backup is a simple copy. I can retrieve it without any specific
programs.
2. if a file changed, before to be copied, the backup file is moved to a
specific repertory
whose name is the date and hour. So if I destroy a file and backup
the destroyed one, the old
non-destroyed one is still available.
3. Since the program is anyway performing a long os.walk operation, in
the same time, it performs `git commit`
in the directories that need it.
4. My program is command-line only. Works fine in tty
Points that are of no importance (very personal and adapted to my
specific case !) :
1. time. One backup takes between 10 minutes and one hour. I don't
really care.
2. space. Since my backup is a copy (and copy of copies), my backup
directory takes ~150Go
while my home is about 25 Go.
Hope it answer your question.
Have a nice day
Laurent
[toc] | [prev] | [standalone]
Back to top | Article view | comp.lang.python
csiph-web