I’d like an option in the settings for an automatic backup / export.
Usually apps that have this would allow you choose a frequency and location for your backup / export.
I would use this feature to backup my data every day to my hard drive in case.
Manual backup / export.
Maybe self-hosting?
Moved to the API subcategory as I think this should be possible with the API. Let me know if you want it to be moved back.
No votes here though. 
I voted @Filip !
I really want an auto-backup system.
Especially when we will be able to install Anytype on a server. That will be a must have.
I have the feeling that hosting your own backup node is the autobackup you are asking for. Of couse, you should host at least two backup nodes on a remote location, so you have the 321 backup strategy:
The backup nodes will also host the version control, so I don’t see any other reason for having an auto-export feature? It of course depends on how the selfhosting will take form (docker container, or something else) but I think you can do some file level, container level, or full VM level backups?
If you can easily set up a backup node on your desktop, then this would be a decent alternative. We’ll need to wait for all the details first.
With that in mind, an auto-backup / auto-export feature would still be useful for people who are less tech savvy.
This topic just reminded me that there’s one problem with the self-hosting solution, and that is if you somehow get locked out of Anytype, your data is gone. Your backup node can’t help you with that.
That’s the reason why this feature is still useful.
Good point! It does require your backups to be unencrypted, or at least decryptable with another Anytype instance or tool.
I followed the post that @Filip posted about here. In addition to providing a backup in the event someone was locked out of anytype, it could also be used as a “bridge” to use other tools to process/develop/publish or otherwise utilize their data.
The export data folder could also be encrypted using other methods.
I agree that backup nodes are a better option for backups, but there are many questions about how anytype will implement it. I am hoping that it will be accessible to people who are not very tech savvy. Some sort of desktop installation would be great. Questions regarding how backup nodes will be implemented does make me wonder if it would be better to have autobackup/export as a part of anytype core application rather than something that is done through the api. I guess the application already has export. This is about auto/ scheduled backups.
I wonder why the backup needs to be unencrypted.
When one wants to import the backup it could be possible to enter the previous key. The anytype app would be needed to decrypt and import it into a new instance. This then could be exported unancrypted if wanted.
In light of recent events 
, I’m really hoping that the team prioritizes this feature more. There should definitely be some kind of automated backup so that we can make sure our data is safe.
This is what currently stopping me from using Anytype as my main PKM system.
This would be a huge feature, if you use something like Obsidian, there are so many sync/backup plugins that you can integrate with. Personally I would like to see a way in which I could sync my notes with a private git repo or similar. Direct integration would be ideal, but file based backup would be fine too, I could just build something off the back of it.
I am considering switching to obsidian due to the lack of a backup feature as it’s restricting me from utilising my notes in other ways.
I just found myself doing a “backup” manually before updating the app.
With multiple spaces, it gets a bit tedious to export one-by-one.
So, yes, add the option to create a full backup. And better yet, add the option for a full backup as part of future updates.
I would love to be able to auto export a filtered set of pages to a git repo or local folder.
This way I could use AnyType as a place to write blogs or documentation and push it as markdown to a repo with a ci/cd pipeline to create the site with tooling like MKDocs / hugo / pelican.
I would like an option to be run via command line, so I can setup an automated export of all my Anytype data in markdown for backup reasons. This should also include files.
Adding a parameter like “–export-all” with different options like for “markdown” or other export formats.
Would be even better if I could give it the same directory and Anytype would check for every file if it is already there and just writing new/changed ones.
Backing up the data folder of Anytype isn’t the same thing here, as there is no real way right now to import this back in. Also, in a case where everything goes really wrong, I would like to have all my stuff in a format I can read without Anytype.
Many users complain about programme crashes.
We are all very dependent on our data and it would be reassuring to be able to access our data by other means in an emergency.
Anytype stores the data encrypted - that’s general fine, but in an emergency also a a major hurdle.
@sturdily suggests in this thread a solution:
He suggests an external tool which works independent from the Anytype app.
This tool encrypts our data after entering the correct passphrase.
The main idea is that we have access then to our data by using a suitable other app. So the encrypted file format should be a usual one, nothing special.
If Anytype does not start for unknown reasons and if there is no time to wait for an update or another solution, then there should be a “Plan B”!
We are too dependent on having access to our data at all times to simply accept a failure of the app!
Off course we could make exports every day or so. But to be honest, who does it?
But even if every user would do it: what’s to do then with all these no longer encrypted data?
We want to encrypt only if needed.
I suggest one additional step:
Seemingly in most cases does it help to reinstall the app after an emergency has happen.
So I suggest that the described independent app could not only encrypt our data, but also doing the reinstallation of the main app in an automated way.
Not each user is a “computer pro”. Some of us would be overwhelmed to do it ourselves when the nerves are tense because of the disaster.
I therefore think that this additional feature to reinstall the app would increase the perceived security even further.
But our main concern is the ability to decrypt our data.
Thanks @Code-Jack ! I have to admit I am not great at long texts explaining all the details! Voted!
Yeah, an external, static, portable binary, that hopefully would never be needed, but a saviour in the cases that it would, and be the answer to the fears about not using .md files.
Since it happened today, where I made a blunder in anytype, so I just cloned the anytype-ts git repo, patched source, built app, run app on profile, fixed blunder, then reverted to latest beta and all good, I feel attacked 
( just kidding, I understand what you mean, no issue taken )
Hmm, now I’m no longer sure about my chosen word “freak”. Does it sound somehow attacking in English?
In German we also use this word, but for us it has a positive meaning.
It means for us, that someone is really really good in something, because he is obsessed by the topic.
We call someone a “Computer-Freak” if he’s able to do seemingly everything on it.
Most users aren’t such “freaks”; they need support for all kinds of little problems, but especially in an emergency.