Since we've got SQL backups as well, I'd say every 3 months for XML would be reasonable

Backup schedules defined:

• Private - weekly
• SSL Keys - weekly
• SQL - fortnightly
• mediawiki-xml - MediaWiki (SRE) - can someone propose a time frame for XML dumps please? - 3 monthly?
• Phabricator Static - fortnightly

Given recent events, a work around solution will be worked on and released this weekend hopefully.

Being able to run and support effective backups is looking like we need to reduce existing infrastructure strain. So this is unfortunately blocked on bigger projects in the next few months.

Started work on this using a python handler for interacting with OVH's PCA via swift.

Upping to normal as we are looking to decom bacula in the very near future.

I've now managed to restart bacula2 via the RamNode interface and it appears to be working fine. Closing this task now as it was clearly RNs fault and there's nothing further to be done. I've asked them if they can give us any indication of what happened.

RamNode also can't get it to restart. It's now waiting on one of their team to look further.

I've tried to restart it from the Cloud interface on RN to no avail. Ticket filed.

Looking at RamNode

WikiLirik sözcüleri eleştirisel pozitif-negatif düşünce karşılaştırma
PyschoLyricWiki Attack Groups
Ben ötesi psikoloji

@John Could you maybe be around later today (as I don't want anything to go wrong when dealing with backups)?

Not really besides set it up as a puppet client and make sure it works.

After I click the "reinstall" button, do I need to do anything else manually on bacula1?

Labster has granted me access to Backupsy, I will reinstall tomorrow (before the new cycle)

Also check all sizes and they should be about 20-30GB less than the usable disk space

I can’t recommend. Probably double the currents if needed. Check what icings reports sizes as and if there’s enough space, leave them.

@John Could you maybe recommend what sizes should be changed to what? Or maybe make a PR for it? Since I'm not too sure about how much space to give to what.

It should really be installed and left to run to its own schedule. The sizes of each volume has to be changed in configuration as well

Looks like this is done.

Just control panel.

@John ^

And paid the upgrade cost (looks like we get to keep the discount).

Opened a ticket for an upgrade.

Yes, we obviously need to add more space to backups. I'm just hoping that the 40% coupon still applies to the upgrade!

I think it's alright if we add another 250GB of space to bacula1. @labster can you approve?

For perspective, the last backup of static.miraheze.org is from July.

@Southparkfan ^

High priority and no progress for nearly a month?

Well nfs1 is definitely not being backed up.

db* is getting backed up as far as icinga and bacula are happy.