Here is why I do not think it is a network issue, but I will have a look. I can backup the newly created machine and restore it's backup. For example, I issue:
root@lamp:/usr/lib/tklbam# tklbam-backup
And it is successful
--------------[ Backup Statistics ]--------------
StartTime 1287499188.11 (Tue Oct 19 14:39:48 2010)
EndTime 1287499188.49 (Tue Oct 19 14:39:48 2010)
ElapsedTime 0.38 (0.38 seconds)
SourceFiles 256
SourceFileSize 1883983 (1.80 MB)
NewFiles 89
NewFileSize 361048 (353 KB)
DeletedFiles 0
ChangedFiles 58
ChangedFileSize 513727 (502 KB)
ChangedDeltaSize 0 (0 bytes)
DeltaEntries 147
RawDeltaSize 3389 (3.31 KB)
TotalDestinationSizeChange 5082 (4.96 KB)
Errors 0
-------------------------------------------------
Then I issue the restore:
root@lamp:/usr/lib/tklbam# tklbam-restore 2
Restoring duplicity archive from s3://s3.amazonaws.com/tklbam-opmdspw7ttxuu6za
Local and Remote metadata are synchronized, no sync needed.
Here is why I do not think it
Here is why I do not think it is a network issue, but I will have a look. I can backup the newly created machine and restore it's backup. For example, I issue:
root@lamp:/usr/lib/tklbam# tklbam-backup
And it is successful