This table contains all the backup folders defined in the client.ĬREATE TABLE mountpoints(jwc_id INTEGER PRIMARY KEY ASC AUTOINCREMENT,jwc_name,jwc_path,jwc_device,jwc_description,jwc_status,jwc_location,jwc_type,jwc_ip,jwc_suspended )
#JOTTACLOUD LOGIN FULL#
‘pattern’ allows for simple pattern matching (*) for the full local path of a file or folder to exclude from backup.
‘mountpoint’ is set to ‘-1’, and I find no possible use for it to match an entry in the ‘mountpoints’ table. From the client settings, it is possible to include hidden files and folders.ĬREATE TABLE excludes(id INTEGER PRIMARY KEY, mountpoint INTEGER, pattern VARCHAR(1024)) This also includes the system and hidden files and folders that are not backed up. The ‘backup_schedule_copy’ table contains the schedule before making changes through the client.Īll files and folders that are excluded by the backup. My guess about the ‘mountpoint’ column (which is set to “-1” by the schedule settings in the client) is that it refers to the ‘mountpoints’ table, so theoretically it should be possible to create separate schedules for every one of the mountpoints by directly entering them into the database… If the schedule is set to any of the multi-day variants (“weekends”,”weekdays”,”everyday”) there will be multiple entries in the database, one for each day: By modifying the database it looks like they prepared to allow for different backup time settings every day (I don’t know if it works).ĬREATE TABLE backup_schedule(id INTEGER PRIMARY KEY, mountpoint INTEGER, start_day TEXT, start_hour INTEGER, start_minute INTEGER, end_day TEXT, end_hour INTEGER, end_minute INTEGER) Īll self-explanatory except “mountpoint”, which is set to “-1” when I create a schedule. The backup schedule in settings seems to be a very simplified one. Tables: backup_schedule The backup schedule (Schedule tab in settings) backup_schedule_copy Backup copy of the backup schedule excludes Files and folders excluded from backup excludes_copy Internal backup copy of the excludes table mountpoints All backup folders set in the client Never change anything without having a backup, and never change anything while the client is running.
#JOTTACLOUD LOGIN MANUAL#
This is the only table I have made manual changes to (I made the listed folder name in the GUI more obvious on some entries). This database file was last changed almost a year before I stopped the client. The use of it is for me unknown (as the table is empty in my db). jobs.dbĬontains only one table ‘jobs’ defined asĬREATE TABLE jobs (id integer primary key autoincrement, status integer, uri, name, path, databasepath, files integer, bytes integer ) It’s an 24 character alphanumeric string. Jwc_shareid is in the form of jwc_uuid given above, jwc_owner is probably some secret string about my user (at Jotta) that I’m not supposed to share. Mostly self-explanatory, except for the two fields I’m unable to explain 🙂 It was empty in my current copy of the database, but it should be more or less like jwt_files (used only temporarily).ĬREATE TABLE jwt_shares (jwc_id INTEGER PRIMARY KEY ASC AUTOINCREMENT, jwc_shareid, jwc_localpath, jwc_remotepath, jwc_owner, jwc_members ) Open the client interface, go to settings, then under the “General” tab, you will find a button that opens the log file location:Ī window with the location ‘C:\Users\’ on most files jwc_revision 0, 1 or 11 on all my files jwc_folderid id (jwc_id from jwt_folders) of containing folder jwc_newpath New local name of a file renamed because of an upload errorĬREATE TABLE jwt_queuedfiles (jwc_id INTEGER PRIMARY KEY ASC AUTOINCREMENT, jwc_remotepath, jwc_remotesize INTEGER, jwc_localpath, jwc_localsize INTEGER, jwc_relativepath, jwc_created INTEGER, jwc_modified INTEGER, jwc_status, jwc_checksum, jwc_revision INTEGER, jwc_queueid, jwc_type, jwc_hash, jwc_folderid)
#JOTTACLOUD LOGIN WINDOWS#
This method works for finding the location on the windows version: The path to the database files and the path formats within the databases will differ for the client for other OSes. This documentation is for the windows version of the client. I dug into the sqlite databases used by the JottaCloud client (and branded ones like Elgiganten) and found something that can be useful for other diggers…
0 kommentar(er)
