Backup data suddenly decreased, and the reduced backup data recovery was abnormal, causing the website to be unable to interact normally. Fortunately, historical data could be found in the Amazon S3 storage bucket, otherwise the loss would be immeasurable.
סיכום מבוסס בינה מלאכותית
用户sober报告在升级到3.3.0.beta2-dev版本后,备份数据量减少且无法正常恢复,导致网站交互异常。尽管通过亚马逊S3存储桶找回了历史数据,避免了更大损失,但备份问题依然存在。用户使用了两容器架构(data.yml和web_only.yml),并启用了AI插件,怀疑数据库升级和容器重建是导致问题的原因。JammyDodger建议检查备份设置,并将问题转至#installation讨论。pfaffman推测可能是资产被移至S3导致本地备份不完整,或因未完成恢复过程。用户进一步询问如何确保备份可用,以及如何避免数据库升级引发的问题。Firepup650解释dev标签是版本系统新变化,实际稳定性并无差异,用户担心dev版本不稳定,但希望升级到beta2而非beta2-dev。sober JammyDodger pfaffman Firepup650
Were there any settings changes in that timeframe that could have had an affect on whether uploads were included in your backups?
Did you change to a two-container set-up at that point, or were you always using it?
It’s always been used like this, what are the possible causes?
I tried restore my latest backup a couple days ago and upload on my dash was refused I felt for a second that my backup is gone so I try one more uploading on FTP and guess what? restored! but this happened idem and I would to know the reason.
I’m afraid I’m more familiar with the standard install and I’m not sure if the two-container setup has any quirks that may be relevant here.
Let me slide this over to #installation and see if we can get some more experienced eyes on it.
(@pfaffman
)
Previously, I used the standard installation. However, the standard installation has a problem: every time I modify app.yml, my website cannot be accessed normally. If I use data.yml or web_only.yml, I can modify web_only.yml without affecting website access. Does the standard installation have a similar function, and how is it used specifically?
No. The only difference is that a rebuild rebuilds just the rails and nginx part. The database and redis stay the same. Those change rarely, so they don’t need to be rebuilt. It works just the same. You understand that just fine. (The only complication is when there is a postgres or redis update, which is on the order of once a year, though there were some database updates that happened due to requirements of the AI plugin. So if you weren’t using the AI plugin you’d be just fine, but if you were, you’d get confusing database errors if you didn’t also rebuild the data container.)
My guess is that they moved assets to s3 and so the local uploads aren’t included. This is consistent with them saying that they were able to restore stuff from s3. Or maybe they deleted some posts that had uploads so those uploads weren’t included in subsequent backups.
Also, it sounded a bit like they did a restore and didn’t wait for it to finish completely.
We did use an AI plug-in. What should we pay attention to so that the backup data can be used? How should we deal with this kind of problem?
We did use an AI plug-in. What should we pay attention to so that the backup data can be used? How should we deal with this kind of problem
Does it mean that as long as data.yml is not rebuilt, there is no problem, or is it necessary to use app.yml, or does this kind of problem exist in both the data.yml web_only plan and the app.yml plan?
The problem is that when I backed up, the container built by data.yml was not supported, and the database was upgraded. If the data.yml rebuild is upgraded, there will be no problem even if you do a major database upgrade, and then there is no problem with the backup and restore it. How can I know that your database has been greatly modified
@sober, as a process note, it’s much easier for those reading along/wanting to help out if you include an English translation in your posts. Could you please edit one in. ![]()
I now understand that the problem was a big upgrade of the database that caused backup problems
What? well I’ll wait for a confirmation cause idk if will broken something here.
I only want to upgrade beta2, not beta2-dev, because I am afraid that dev is unstable, and the recent data backup cannot be restored normally, which almost causes data loss. I used the early backup for backup, but the data was still lost for a period of time
They’re not, that’s just a recent change to the versioning system. Technically, you’re not even supposed to see the -dev labels.


