I’m using the Deja Dup GUI. I’m mostly a Linux newbie beginner so if the answer involves lots of complicated command lines without context, I may not be able to follow (unless it’s fully step by step with no steps left out and with clear instructions).
I tried the DEBUG=1 option but could not determine if and where the log was saved.
If the best answer is “use xyz backup app instead” that’s fine. As long as the alternate backup app has a GUI and automatically creates a log of each backup job. And it can make incremental backups.
I was unable to find the webpage that gave the details. All I remember is it said run “deja_dup_DEBUG=1”. When I run the command it works but doesn’t give any info. Also the page didn’t say where the files are stored.
The DEBUG option probably won’t be any more user friendly but it will be more informative to say the least. So here’s what you need to do. Keep in mind this will create very VERY verbose output.
In a terminal type: DEJA_DUP_DEBUG=1
This will create a variable and set it’s value to 1. It is not an environment variable yet.
If you type: echo $DEJA_DUP_DEBUG
It should output the value 1
Now type: export DEJA_DUP_DEBUG
This takes your variable, which so far is only available to the current terminal, and makes it an environment variable so that it is persistent even if you close the terminal.
Type: printenv DEJA_DUP_DEBUG
This will print the value of an environment variable if it exists. This should output the value 1. This just confirms that you’ve done all the steps so far correctly.
Run deja-dup from the terminal, but redirect the output to a file. deja-dup >> /tmp/somefile.txt
By default, programs will print output to the terminal. If you want the output in a file, just redirect it with >> followed by the location and file name. Keep in mind >> will overwrite an existing file. If you want to add the output to an already existing file use a single >.
Now you won’t see any output in the terminal but you will have a text file when the backup is complete. This file will be many thousands, perhaps millions, of lines as it prints out literally everything it is doing.
NOTE: Don’t direct the output to a file that is in the path that deja-dup is backing up. I accidentally did this while testing this out lol.
I’m looking more closely at the .manifest file created by Deja Dup when it runs. I think it has enough info to serve as a good summary of backup jobs. So I think that will resolve the issue. Could you mark this as resolved? Thanks again for your help on this. Especially thanks for letting me know about .cache/manifest file.