1. It saves one big inscrutable .db file rather than individual messages in some compatible format or other.
2. It doesn't seem to play nice with laptop suspend. If I'm going to run it as a scheduled task then it needs to not get confused if I shut my laptop lid in the middle of a run.
3. It could be clearer about the correct workflow for continual incremental backups. It sounds like you probably want to do one full backup, continual partial backups and then occasionally a full backup in case your labels have changed. I don't like choices.
1. Gmvault doesn't save all your emails in a .db file. It creates a db directory which contains sub directories containing your emails in eml format. So it is using a standard email format and allow users to access individual emails.
2. I have already closed my laptop and reopen it and Gmvault restarted from where it stopped (tried on windows). Still there might be a problem so please report it following the instructions here: http://gmvault.org/report_pb.html.
3. Regarding the workflow, the recommended mode is to do a full backup and then daily do a quick backup. The quick backup is an incremental backup that only check emails for the last two months. It takes only 2 to 3 minutes normally.
Thanks for replying. I'm going to check again. I must have been doing something wrong. I'll contact you by a more appropriate means when I've figured out what.
1. It saves one big inscrutable .db file rather than individual messages in some compatible format or other.
2. It doesn't seem to play nice with laptop suspend. If I'm going to run it as a scheduled task then it needs to not get confused if I shut my laptop lid in the middle of a run.
3. It could be clearer about the correct workflow for continual incremental backups. It sounds like you probably want to do one full backup, continual partial backups and then occasionally a full backup in case your labels have changed. I don't like choices.