Thank you for working so hard to get the data back up. Today I received the mail with the archive.
This has me thinking: why bother at all? I do have all this data on my own devices. I would not be bothered by an empty space and having Nextcloud Desktop upload all 300Gb again. So, although I appreciate the effort and I understand that you are obviously morally obliged to get it all back up, please consider the other option, to capitulate.
If users would have the choice of reuploading instead of waiting, could that make life easier for all of us?
Hello, not everyone is in your situation. I backuped my photos from my phone and have no other copies. Iād appreciate a working Nextcloud with my old data again and donāt care how long it will take. But I am sure others were using the cloud in a more timely manner and would have needed a working cloud months ago. Please letās stop proposing individual solutions and let them work to restore their services.
I get your point, but it should be up to the user to decide if they want to go through with the restoration, and not up to the service
Murena should keep trying to offer a solution to all itās users, as they have been doing.
Itās good that some of us donāt need the lost data, but that shouldnāt discourage murena from fixing the servers.
Hi,
Is it possible to get a delay on the overall processing of emails? Even estimated? Unfortunately, I really need my data, and a little visibility on the deadlines would be really welcome.
The emails have started, and? When should they finish, as some like me have probably not received anything, it would allow us to wait more serenely.
Do we have an update on when the full service will be restored? I would like to make two accounts for my daughters but Iāve been waiting a couple months now.
Iāve got my email for my backup archive file, and Iām now over the point of getting angry about it.
In short: There is a lot of data loss. It may vary from user to user, but in my case, the backup is far older and was made months before the outage.
The backup was made on 2024-06-18! The outage started at 6th October. Thatās a difference of ~15 weeks. 15 weeks where all new/modified data is lost.
Iām downloading it and veryfing and posting it here, if the above info turns out wrong.
No problem for me as I have multiple backups as you should have, too, or at least you have learned your lesson with this outage; but itās a thing you should be aware of that you might loose data in varying degree, even if you get your link.
Please correct me, but I suspect the following:
There were no regular and sheduled backups, as nobody would intentionally configure backup cycles of ~3 months
Something went wrong with the shelduled backup jobs (out of disk space, etc.) and nobody cared/fixed it for 3 months
This is no backup but recovered data from a cluster storage node, and there may have not been a proper backup at all.
It would be very nice to give an explanation as I think this situation is still getting uglier for Murena. I wouldnāt be so dissapointed if there would be better communication about the possibility of data loss.
Edit:
The date of the backup is correct, I checked the automatically uploaded photos from my phone, and the last one was around beginning of June. So 15 weeks of data is missing.
The team is working on restoring the file system which when complete would give users access to all the data. This is for cases where there is a difference in the backup data and the data in the filesystem. The backup restored is from June as you correctly mentioned.
Thanks for specifiying there is a chance for all data to be restored.
May I ask, whatās the technical reason for having only this old backups at the time of the outage. In my understanding this canāt be intentionally.
Edit:
In other words: Now it makes sense to me that murena is putting so much effort and time into restoring the cluster instead of nuking and paving the cluster and to deploy the backup asap to get a running eDrive service again. Thatās not happening with 15 weeks old backups I assume. Someone could describe that as standing with the back to the wall.
I would really like to know what led to this; if this was deliberate, negligent or something else.
Iām not bitter and donāt want to make a fuss about it, but I highly recommend Murena to make a really good post mortem about the whole incident and what led to it, because your customer base and the people donating to the project are mostly here because they value their data, and just from the pure outcome of having no service for a month and than no access to the own data after 3 months with an even older backup, tells the story of Murena not caring as much about users data as advertised (unless someone gives an explanation and takes responsibility).
Iām just saying that Iām invested with around 1500ā¬ into murena (3 phones, 3 years of eDrive subscribtion), and I wonāt propably buy the tablet or another phone as Iām not convinced about the future of Murena. I would gladly put my trust and money into Murena again, but Iām missing an authentic explanation.
Today I received an email to say my archived files available and the password is in my e passwords folder. The sad joke is I wanted to use my phone, only to be told the default browser /e/OS comes with (modified Chromium) is outdated! How bad is this! The alternatives are Firefox which Google has itās claws in, Vivaldi written by the author of Opera that got sold off to Chinese consortium, or Tor, no guarantee of security there either. The only secure browser is un-Googled Chrome - so why is that not available?
The download of the ZIP file does not work; the following error message appears each time: āfilename.zip.part could not be saved because the source file could not be read.ā
Yes, I have tried both. I have since found out that my WLAN repeater is causing the network problem. When I placed my computer right next to my internet router, I was able to download the file.
While the outage has, undeniably, been very disruptive, it didnāt make it to the top 10 of big outages. Admittedly, they donāt have a category for length of time.
Itās now Friday, the last update was on the 20th, and I would still like to know why the provided backup archive is 15 weeks older than the date of the outage. Come on, COMMUNICATE, please. Tell us why you do stuff the way you do. Tell us why you prefer restoring the cluster files over having eDrive operating asap without the user data. Just anything what explains having nothing usefull to show for after 3 months.
