sjau has finally found the solution: http://www.howtoforge.com/ftp-backups-with-duplicity-ftplicity-debian-etch#comment-4324
Saw the solution--damn, empty directory caused this: Traceback (most recent call last): File "/usr/bin/duplicity", line 373, in ? if __name__ == "__main__": main() File "/usr/bin/duplicity", line 349, in main globals.archive_dir).set_values() File "/usr/lib/python2.4/site-packages/duplicity/collections.py", line 406, in set_values backend_filename_list = self.backend.list() File "/usr/lib/python2.4/site-packages/duplicity/backends.py", line 365, in list try: return self.error_wrap('nlst') File "/usr/lib/python2.4/site-packages/duplicity/backends.py", line 335, in error_wrap except ftplib.all_errors, e: raise BackendException(e) duplicity.backends.BackendException: 226 Transfer complete. I just drug a txt file off my desktop into the directory and it ran. Thought it was going to be ok, but... Traceback (most recent call last): File "/usr/bin/duplicity", line 373, in ? if __name__ == "__main__": main() File "/usr/bin/duplicity", line 366, in main if not sig_chain: full_backup(col_stats) File "/usr/bin/duplicity", line 142, in full_backup bytes_written = write_multivol("full", tarblock_iter, globals.backend) File "/usr/bin/duplicity", line 89, in write_multivol backend.put(tdp, dest_filename) File "/usr/lib/python2.4/site-packages/duplicity/backends.py", line 349, in pu t self.error_wrap('storbinary', "STOR "+remote_filename, source_file) File "/usr/lib/python2.4/site-packages/duplicity/backends.py", line 335, in er ror_wrap except ftplib.all_errors, e: raise BackendException(e) duplicity.backends.BackendException: 421 No Transfer Timeout (300 seconds): clos ing control connection. ---------------- Anyone know what's causing this one?
guys, believe me, I have tried to solve this forever. for me the empty directory was not the problem. curiously, right now, I was trying the whole thing again with the latest versions of boths programs, will psot again if it works.
For some reason it's working ok for me now--I don't know what caused the second error, but I'm not having it now. I just use pico to create a small file in the empty destination directory. I have a 2nd drive on my server, so I located how to backup the whole drive to that if it's called disk2, for example: duplicity --exclude /proc --exclude /disk2 / file:///disk2/server2bkup http://www.nongnu.org/duplicity/duplicity.1.html Btw, I just used apt-get install duplicity Update: I couldn't get the full drive backup to work yet--it runs for a few hours then errors out.
right, that was exactly my problem. basically I just followed this guide: http://www.howtoforge.com/ftp-backups-with-duplicity-ftplicity-debian-etch-p2 again, but used the newest versions from here: http://sourceforge.net/projects/ftplicity and http://duplicity.nongnu.org/ made sure I removed all old versions, then read the changes as the ftplicity syntax has slightly changed to include profiles and now everything is running smoothly as it should. btw. take care to install all prerequisites of duplicity.
