Where are em client files stored?

Hello,

I am aware that this question has been posted often, but I’m not completely
clear as to the answer.

I am using eM Client v 7.1.30794.0 on a Windows 10 PC.
I have registered with a file sync service, to maintain a continuous copy
in the “cloud” of my most important files, not the whole hard drive, as that
would be far too large.  This is for backup only.

I want all my eM Client emails and contacts to be among the files sync’d.
I am not sure where they are saved; there are two possibilities, as follows
(I am “Ken” on my PC):

“C:\Users\Ken\AppData\Roaming\eM Client”
“C:\Users\Ken\AppData\Local\eM Client”

Should I designate one or both of these folders for sync?
Or is my eM Client stuff kept somewhere else?

Thanks for your help,   Ken.

The database is at “C:\Users\Ken\AppData\Roaming\eM Client”. This folder contains everything including email, contacts, events, settings, rules, signatures etc. But you will not get a reliable copy if eM Client is running when it makes a sync. It has to do with the way that the SQLite files are opened. If you ever tried to restore from that synced copy, you would get a database error the same as if you did not close the application properly. Though there usually is no problem once the database check has been run, it is not foolproof.

One reliable method is to sync the backup directory, where you have a daily backup running. The backups are run whether eM Client is running or closed. Another way to ensure continuous synced data is if you are using IMAP protocol that includes your calendar and contacts. That way your local data is always synced with a server in real time. IMAP does not sync settings and other items like signatures and rules, but as these don’t change that often, a daily or weekly backup is usually a safe option for those.

“C:\Users\Ken\AppData\Local\eM Client”  has one useful folder and that is the avatar cache. This folder is not included in the backup, so I would not worry about it. Usually on a restore where this folder is manually copied, it is ignored and new avatars are downloaded anyway.

Thank you Gary for comprehensive reply.
The backup directory sounds like a good option – I presume you are referring to a constantly running eM Client backup?  Can you tell me where it is located?

Menu > Tools > Settings > General > Backup. You can set the location of the backup.

I don’t think a constantly running backup would work. Really if you are using IMAP, and regularly backup so you have a copy of your settings etc., there is very little risk of losing anything. I don’t use IMAP on my primary account, so my mail is stored locally. I backup daily using eM Client’s automatic backup, and have a script that copies that backup to another location after it is completed. My retention policy on the POP server is 2 days, so even if I lose yesterday’s backup, I can still get those emails back. I think that is as safe as can be.

Apologies, misunderstanding on my part as to how these things work.
I have now set a daily backup to a folder that will be sync’d.
EM Client does not say at what time of day it happens, but I guess when I look tomorrow the backup file will have appeared.  Am i correct to assume this backup will allow complete recovery of all my eM Client stuff?

It is not possible to set a specific time of the backup in eM Client, but if you have set it for daily it will run at the same time every day, starting from when you set it. However, you can change the time and frequency in Windows Task Scheduler.

In Windows 10, click the start button and type Task. Select Task Scheduler from the results.

Navigate down to eM Client Database Backup and you can change the settings under Triggers.

Yes, the backup will allow complete recovery, including emails, contacts, events, tasks, signatures and templates, rules, categories, accounts, license information . . . everything!

Apologies for delay in replying.
That answers all my questions – everything saved in the backup file.
Many thanks for your help.
I think that completes this posting thread.