I have been backing up my servers with duply for years but now I noticed something strange: when running a full backup, the log entries about the pre/post script are missing. Coudl someoen else running duply please check if this is normal behavior? Is it just not shown in the logs or are pre/psot scritps ignored for full-backup? every Mon-Sat cron runs: /usr/bin/duply diladele backup and the log looks like this: Code: Start duply v1.5.5.5, time is 2014-07-26 18:00:01. Using profile '/root/.duply/diladele'. Using installed duplicity version 0.6.18, python 2.7.3, gpg 1.4.12 (Home: ~/.gnupg), awk 'GNU Awk 4.0.1', bash '4.2.37(1)-release (x86_64-pc-linux-gnu)'. Autoset found secret key of first GPG_KEY entry '27A8AEC1' for signing. Test - Encrypt to 27A8AEC1 & Sign with 27A8AEC1 (OK) Test - Decrypt (OK) Test - Compare (OK) Cleanup - Delete '/tmp/duply.765936.1406390402_*'(OK) [COLOR="Red"]--- Start running command PRE at 18:00:02.547 --- Running '/root/.duply/diladele/pre' - OK --- Finished state OK at 18:00:05.999 - Runtime 00:00:03.452 ---[/COLOR] --- Start running command BKP at 18:00:06.008 --- Import of duplicity.backends.giobackend Failed: No module named gio Reading globbing filelist /root/.duply/diladele/exclude Local and Remote metadata are synchronized, no sync needed. Last full backup date: Fri Jul 18 18:26:06 2014 Reuse configured PASSPHRASE as SIGN_PASSPHRASE --------------[ Backup Statistics ]-------------- StartTime 1406390460.92 (Sat Jul 26 18:01:00 2014) EndTime 1406390530.92 (Sat Jul 26 18:02:10 2014) ElapsedTime 70.00 (1 minute 10.00 seconds) SourceFiles 2 SourceFileSize 4604432384 (4.29 GB) NewFiles 0 NewFileSize 0 (0 bytes) DeletedFiles 0 ChangedFiles 1 ChangedFileSize 4604428288 (4.29 GB) ChangedDeltaSize 0 (0 bytes) DeltaEntries 1 RawDeltaSize 48304020 (46.1 MB) TotalDestinationSizeChange 5258563 (5.01 MB) Errors 0 ------------------------------------------------- --- Finished state OK at 18:34:38.303 - Runtime 00:34:32.295 --- [COLOR="red"]--- Start running command POST at 18:34:38.311 --- Running '/root/.duply/diladele/post' - OK --- Finished state OK at 18:34:44.547 - Runtime 00:00:06.235 ---[/COLOR] And every Sunday: /usr/bin/duply diladele full and the logs look like this: Code: Start duply v1.5.5.5, time is 2014-07-27 23:00:01. Using profile '/root/.duply/diladele'. Using installed duplicity version 0.6.18, python 2.7.3, gpg 1.4.12 (Home: ~/.gnupg), awk 'GNU Awk 4.0.1', bash '4.2.37(1)-release (x86_64-pc-linux-gnu)'. Autoset found secret key of first GPG_KEY entry '27A8AEC1' for signing. Test - Encrypt to 27A8AEC1 & Sign with 27A8AEC1 (OK) Test - Decrypt (OK) Test - Compare (OK) Cleanup - Delete '/tmp/duply.806269.1406494802_*'(OK) --- Start running command FULL at 23:00:03.077 --- Import of duplicity.backends.giobackend Failed: No module named gio Reading globbing filelist /root/.duply/diladele/exclude Local and Remote metadata are synchronized, no sync needed. Last full backup date: Fri Jul 18 18:26:06 2014 Reuse configured PASSPHRASE as SIGN_PASSPHRASE --------------[ Backup Statistics ]-------------- StartTime 1406494805.29 (Sun Jul 27 23:00:05 2014) EndTime 1406508712.21 (Mon Jul 28 02:51:52 2014) ElapsedTime 13906.91 (3 hours 51 minutes 46.91 seconds) SourceFiles 2 SourceFileSize 4648996864 (4.33 GB) NewFiles 2 NewFileSize 4648996864 (4.33 GB) DeletedFiles 0 ChangedFiles 0 ChangedFileSize 0 (0 bytes) ChangedDeltaSize 0 (0 bytes) DeltaEntries 2 RawDeltaSize 4648992768 (4.33 GB) TotalDestinationSizeChange 1674655632 (1.56 GB) Errors 0 ------------------------------------------------- --- Finished state OK at 03:29:50.194 - Runtime 04:29:47.116 ---
