Déjà Dup

Log files- Warnings , summary, etc

Asked by Jean-Francois Ouellette

I am using Deja Dup on my home network on 3 workstation that all backup to a server.

It works over samba shares and scheduled for daily backups.

Everything works great, but I would like to know if there are log files created, either by Deja dup or Duplicty after each runs?

I searched my files to try and find some but to no avail. Also researching the web returned very little information about log files and Duplicity other than command line switches and homemade bash scripts that create their own logs.

I need those for reviews in case somethiog goes wrong and backup jobs fail for some reasons. For now the only way I have to find out if daily backups are done is to mount the share and look at the time and date of the recent backup archives.

Thanks in advance an also many more thanks for your great program.

Question information

Language:
English Edit question
Status:
Solved
For:
Déjà Dup Edit question
Assignee:
No assignee Edit question
Solved by:
Michael Terry
Solved:
Last query:
Last reply:

This question was reopened

Revision history for this message
Michael Terry (mterry) said : 		#1

You can run Deja Dup with the environment variable DEJA_DUP_DEBUG=1 and it will spew lots of information (verbose output of duplicity). Since I'm assuming you have them set up to automatically backup, you'll need to set the variable in a way that effects the whole session so that deja-dup-monitor picks it up.

Revision history for this message
Jean-Francois Ouellette (jeanf-ouellette) said : 		#2

Thank you . That clears it up.

Revision history for this message
Jean-Francois Ouellette (jeanf-ouellette) said : 		#3

What scheduling system does Deja Dup use. I don 't see it in cron as far as I can tell?

Revision history for this message
Michael Terry (mterry) said : 		#4

I just added a scheduling section to the pretty bare 'behind the scenes' wiki documentation.

See http://live.gnome.org/DejaDup/HowItWorks#Scheduling

Revision history for this message
Jean-Francois Ouellette (jeanf-ouellette) said : 		#5

Thanks for the the info.

Revision history for this message
Jean-Francois Ouellette (jeanf-ouellette) said : 		#6

Sorry for being annoyingly persistent but I would like to write a little bash script to run deja-dup with the DEJA_DUP_DEBUG=1option and redirect the output to a cutom log file that would be emailed to me on a daily basis.

For that I need to know that if I run deja-dup from the command line it will use the backup profile I created in the "preferences" section of the GUI.

I don't really see any other way of telling deja-dup what to backup anyhow.

If this is the case, I would then setup my backup source and target using the GUI and then not use the schedule option. Instead I would put my own script in CRON to be run whenever I want and create a log file.

It's eihter that or you'll tell me your next version will have a new tick box that says : "create log file" ;-) , Hahahaha! In which case I would be very happy.

Revision history for this message
Best Michael Terry (mterry) said : 		#7

Hmm. Well, deja-dup run from the command line will use your settings from the UI (it stores them in gconf like other GNOME apps) if you run it in a command line as part of your user session. But... cron doesn't run as part of your user session. So I don't believe it will work right without X.

Revision history for this message
Jean-Francois Ouellette (jeanf-ouellette) said : 		#8

Ok thanks a lot for your input. Very informative. All I need then is scheduling utility in userspace and my little project is going to work.

Revision history for this message
step21 (step22) said : 		#9

Should DEJA_DUP_DEBUG=1 still work, or where does it put its output?