Loomio
Fri 8 Jan 2016 1:18PM

Backup and restore

PS Pavithran S Public Seen by 266

The last I heard about backup and restore hasnt been given much interest. Any reason for that?
https://github.com/diaspora/diaspora/issues/5343 has some progress.

CS

Comrade Senya Fri 8 Jan 2016 2:27PM

I hope I can participate in it in a while, after some present jobs are done.

JR

Jason Robinson Fri 8 Jan 2016 9:20PM

The latest automatic back up / restore spec proposal includes the import parts in this issue. Would be fancy to get more comments on it, split it into smaller chunks and dump a lot of bounty money on the issues - maybe get something to happen :)

Anyone wanting to give their insight, please check the proposal and comment in issue #908 . If no comments are received after some time I could just create a proposal to accept the proposal as a guideline for development.

Please don't start working on any import thingy before at least considering that proposal ;)

PS

Pavithran S Sat 9 Jan 2016 1:50PM

Its a very detailed proposal. Isn't there a simple way like mysql dump to csv/json and import csv/json ? Pod to pod communication sounds very complex.

JR

Jason Robinson Sat 9 Jan 2016 6:45PM

Dumping database would not work for ordinary users very well - and certainly would not work in the situation where the pod just disappears. And, importing raw SQL dumps into other pods would probably not be a very nice thing to do :)

Regarding JSON, yes we already allow exporting data. The proposal details how this data could be to not only restore the data to a new pod (profile, etc), but also migrate the identity, and thus take control of previously shared posts etc.

PS

Pavithran S Sat 9 Jan 2016 8:59PM

Regarding JSON, yes we already allow exporting data.

Yes now we need an import function but your proposal looks too big and lot of stuff needs to be implemented. Agreed its the optimal way to go forward.

but also migrate the identity, and thus take control of previously shared posts etc.

Can't we have something just for exporting all the posts and its comments which are imported back under new account. " Taking Control" sounds complex.

JR

Jason Robinson Sat 9 Jan 2016 9:02PM

Can’t we have something just for exporting all the posts and its comments which are imported back under new account. “ Taking Control” sounds complex.

That would create duplicates and there would be no interaction possibility. No comments to the old ones would arrive to your new identity, for example.

Sure, you can have (almost) anything (sane) - just find a coder to do it :) The issue has been there for a while waiting for someone to grab it. This proposal aims to solve the disappearing pod problem and clean migration. That doesn't stop anyone doing partial or full imports before a "proper" migrate solution is done.

SVB

Steffen van Bergerem Sat 9 Jan 2016 9:04PM

Can’t we have something just for exporting all the posts and its comments which are imported back under new account. “ Taking Control” sounds complex.

So you would like to share all your previous posts again from your new profile?

CS

Comrade Senya Fri 22 Jan 2016 2:33PM

So we have User and Person models. On migration we must create a new user but do we preserve the same Person model which was known for that person? I suppose we should.

CS

Comrade Senya Fri 22 Jan 2016 2:39PM

Profile data export package contains also posts and comments which can be ignored during the restore process.

I don't think posts and comments can be ignored. It is possible that the new pod doesn't contain some posts (especially private). I believe it must not be dropped and we should fetch them on restore also.

CS

Comrade Senya Fri 22 Jan 2016 2:42PM

https://wiki.diasporafoundation.org/Account_Backup_And_Restore#Backup_delivery_message

"backup" is signed and encrypted using the user private key

Where do we store signature? Don't we have to have a separate field in the schema for that?

Load More