Hey Amar, Thanks for sending the Journal log. It will definitely help in debugging this. Assuming that you started using Tarsnap GUI on the 18th here's what I see happening:
1. You added Job "weekly tarsnap backup"; 2. You started a backup for said Job at 00-57-08 and then another which failed with: [18/08/17 1:04 AM] Backup Job_weekly tarsnap backup_2017-08-18_01-04-30 failed: tarsnap: Transaction already in progress Which is correct since you can't run multiple create/delete operations with tarsnap, these two operations are mutually-exclussive. 3. You exited the app and ran it again, while the first backup ran in the background still. You tried a manual backup again which failed for the same reason. 4. You started a new session when you woke up, I see 8:40 AM. You queued a dropbox on-demand backup which started running immediately. I see no backup finished for the initial backup at 2017-08-18_00-57-08 which I assume you killed the process either by system shutdown or otherwise. 5. Then you followed with more actions which failed with: [18/08/17 1:35 PM] Backup Job_weekly tarsnap backup_2017-08-18_10-03-42 failed: tarsnap: Error looking up v1-0-0-server.tarsnap.com: nodename nor servname provided, or not known These are network issues, check your firewall if you have one or could have been just a temporary network problem on your side. I see you had better success with creating archives and jobs later on between 21-22. Can you confirm that you have those backups showing up in the GUI? Thank you, Shinnok > On Aug 24, 2017, at 6:46 PM, [email protected] wrote: > > Hey, > >> Apart from what Graham said, did you expand the Journal log (clicking the >> bottom status bar or CMD+j) or took a peek at the Console Log in Help tab >> next day? Sending screenshots of the UI, especially the top part, doesn't >> really provide enough info for us to help you. What about desktop > > My point of screenshot was - I didn't see any archives where I could see > data usage on tarsnap.con. That's all. > > Yes, I am attaching journal log with this mail. > >> notifications, can you check your macOS system notification area and see >> if you got any errors during the backup process, or if the back was >> started in the first place (assuming you didn't clear it)? > > I didn't clear any notifications but there are none from beyond 2 days. > >> >> Also did you enable Save Console Log in Settings -> Application ? That > > No, I didn't know. I didn't know it existed. I have enabled it now but > obviously it shall not help with the issue now. > >> will definitely help in trouble shooting problems like this in the near >> future, including for scheduled backups. The setting is not enabled by >> default for privacy concerns mostly and *maybe* disk usage to some extent, >> since the plain-text log can get quite big with heavy usage of operations >> like list archives and contents. Maybe we should start a discussion in >> regards to that, meaning should we enable it by default? > > I think it will be a good idea with some checks and balances. > >> >> Thank you for trying Tarsnap GUI out, > > Thank you for trying to make Tarsnap more accessible to non true geeks :) > > -- > Amar<journal.log>
