Delta chat id backup? [small archive without past messages]

[paraglider]

I need the ability to recover the account/profile following a complete loss of all hardware devices I own. What do I need to back up - preferably as an encrypted .tar archive squirreled somewhere on the net - in order to reinstate the account/profile on a replacement device(s)? Please note I am only interested in the ability to recover the account/profile, NOT the past message content or list of correspondents.

TIA

[WofWca]

All you need is a backup from Settings → Chats → Export Backup. It also contains your messages and contacts.
You’ll have to care for encryption yourself though.

[ian]

You can use the export backup feature already implemented.

If you find the file too large to handle, you need to prune the zip manually. You can remove past messages, xdc state updates, attachments, but not your avatar and then vacuum the database file with a few SQL commands.

[WofWca]

@ian

If you find the file too large to handle, you need to prune the zip manually.

This doesn’t have to be manual. One may add another device and then delete older messages with Settings → Chats → Delete old messages from device. Then export the backup.

[ian]

Well, the shortest interval here in my client is After 1 hour. While this may seem good enough for all practical purposes, am I supposed to wait 1 hour for it to clear up fully for the above use case?

Does DC execute full vacuuming before each export? Past experience showed that an sql dump and then recreation of the database usually resulted in a smaller database overall.

[Low]

@ian

Well, the shortest interval here in my client is After 1 hour. While this may seem good enough for all practical purposes, am I supposed to wait 1 hour for it to clear up fully for the above use case?

Your client automatically does a backup for you every hour? That would be nice. I guess it’s like whatsapp integrating with google drive for you.

[ian]

No, we were talking about the deletion interval of past messages. I.e., so the backup file won’t be that large. I actually take daily backups of my profiles like so:

Daily exporting of all of your messages in a compact textual archive

#!/bin/sh get_fingerprint() { cat << EOF | select fingerprint from keypairs join public_keys on keypairs.public_key == public_keys.public_key order by is_default desc limit 1 ; EOF sqlite3 -csv -batch "$1" } get_messages() { local PRINT readonly PRINT="`get_fingerprint "$DB"`" cat << EOF | .separator "&&" select '${PRINT}' as profile, m.chat_id as chat_id, m.id as m_id, datetime(m.timestamp, 'unixepoch') as date, replace(replace(replace(replace(replace( case when instr(concat(…

To also retain your connections, you would need to dump a different set of tables, such as bobstate, broadcast_secrets, chats, chats_contacts, config, contacts, keypairs, public_keys and maybe more. It’s usually easier the other way around: copy the database file, delete the blobs, messages and caches and vacuum so you won’t leave out anything important. Could still be done with a few lines of shell script, but I think it would be easier to install DC on a separate device (or a bot) with reduced message retention timeout in multi-device mode so it keeps syncing your ID from your main device as long as it’s online.

[Low]

Yeah, we need to make this more simple for people. Thank you for explaining it though!