discourse s3 backup buckets no longer active #11683
Labels
No labels
announcement
anubis
authentication
aws
backlog
blocked
bodhi
ci
cloud
communishift
copr
database
day-to-day
dc-move
deprecated
dev
discourse
dns
downloads
easyfix
epel
firmitas
forgejo_migration
Gain
High
Gain
Low
Gain
Medium
gitlab
greenwave
hardware
help wanted
high-trouble
koji
koschei
lists
low-trouble
medium-trouble
mirrorlists
monitoring
Needs investigation
odcs
OpenShift
ops
outage
packager_workflow_blocker
pagure
permissions
Priority
Needs Review
Priority
Next Meeting
Priority
🔥 URGENT 🔥
Priority
Waiting on Assignee
Priority
Waiting on External
Priority
Waiting on Reporter
rabbitmq
release-monitoring
releng
request-for-resources
s390x
security
SMTP
sprint-0
sprint-1
src.fp.o
staging
unfreeze
waiverdb
websites-general
wiki
Backlog Status
Needs Review
Backlog Status
Ready
chore
documentation
points
01
points
02
points
03
points
05
points
08
points
13
Priority
High
Priority
Low
Priority
Medium
Sprint Status
Blocked
Sprint Status
Done
Sprint Status
In Progress
Sprint Status
Review
Sprint Status
To Do
Technical Debt
Work Item
Bug
Work Item
Epic
Work Item
Spike
Work Item
Task
Work Item
User Story
No milestone
No project
No assignees
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
infra/tickets#11683
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The S3-bucket-sync backups we have for Fedora Discussion are an exception Discourse's normal process, and as part of renewing our hosting contract this year, we've agreed to no longer require them.
The only thing missing from the regular backups is image and other file uploads. I am working on a script which will archive these via the API. In the meantime, the S3 sync is not happening.
Once this is ready, I'll want somewhere to run that (and to store the results). For now, there is no action needed, but be aware that these buckets are no longer updated.
Metadata Update from @phsmoura:
Metadata Update from @phsmoura:
Out of curiosity, what is the 'regular backups' ?
Metadata Update from @zlopez:
There is a timed job on the host itself that makes backup archives, and we can get these with the API.
But, yeah.
When I get a chance I will prototype this in Communishift.
[backlog refinement]
Any progress on this @mattdm?
[backlog refinement]
Any news here? Or perhaps this is something that someone else could take on (with initial info from you)?
@mattdm
I'm not sure if this is still needed? Does discourse do backups with uploads now?
The current help says: "Discourse backups include the full site database, which contains everything on the site: topics, posts, users, groups, settings, themes, etc. Depending on how the backup file is created, it may or may not include uploads. "
I can't seem to see the backup job, it might be at a different level...
I'll try and catch @mattdm and ask about this and clarify what the status is.
The current backups do not contain uploads/images. The linked upstream topic says "Warning: If your site is hosted by us and you would like to create a backup that includes uploads, contact the Discourse team before creating the backup."
I never did get very far on the promised S3-download script for alternate backups. I think it's probably still a good idea.
ok. I talked with our discourse contacts.
Currently:
If we want backups of our own, we can do that, but those don't have uploads included.
So, I guess we still need a way to download those uploads, or asking for disaster recovery backup copy if we desire to have uploads backed up ourselves instead of relying on them for them.