Since we've got SQL backups as well, I'd say every 3 months for XML would be reasonable
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jan 24 2024
May 19 2023
Dec 27 2022
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
root@puppet141:~/private# /usr/local/bin/miraheze-backup backup private Starting backup of 'private' for date 2022-12-27... Completed! This took 8.501368522644043s root@puppet141:~/private# /usr/local/bin/miraheze-backup backup sslkeys Starting backup of 'sslkeys' for date 2022-12-27... Completed! This took 7.49277400970459s
Nov 25 2022
Given recent events, a work around solution will be worked on and released this weekend hopefully.
Jun 25 2022
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.
Feb 14 2022
Started work on this using a python handler for interacting with OVH's PCA via swift.
Feb 7 2022
Upping to normal as we are looking to decom bacula in the very near future.
Dec 26 2021
Dec 22 2021
Nov 28 2021
Nov 17 2021
Jul 19 2021
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
Jun 7 2020
WikiLirik sözcüleri eleştirisel pozitif-negatif düşünce karşılaştırma
PyschoLyricWiki Attack Groups
Ben ötesi psikoloji
Aug 12 2018
Jan 8 2018
*list jobs Automatically selected Catalog: Catalog Using Catalog "Catalog" +-------+--------------------+---------------------+------+-------+----------+-- -----------+-----------+ | JobId | Name | StartTime | Type | Level | JobFiles | J obBytes | JobStatus | +-------+--------------------+---------------------+------+-------+----------+-- -----------+-----------+ | 4 | BackupPhabStatic | 0 | B | F | 0 | 0 | C | | 5 | BackupPrivateGit | 0 | B | F | 0 | 0 | C | | 1 | BackupDatabasesDB2 | 2018-01-07 00:05:04 | B | F | 1026938 | 6 169770958 | T | | 2 | BackupDatabasesDB3 | 2018-01-07 01:35:16 | B | F | 24530 | 2 7755498714 | T | | 3 | BackupStatic | 2018-01-07 03:28:28 | B | F | 0 | 0 | R | +-------+--------------------+---------------------+------+-------+----------+-- -----------+-----------+
Jan 6 2018
@John Could you maybe be around later today (as I don't want anything to go wrong when dealing with backups)?
Jan 5 2018
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)
Dec 17 2017
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!
Dec 11 2017
I think it's alright if we add another 250GB of space to bacula1. @labster can you approve?
Dec 6 2017
For perspective, the last backup of static.miraheze.org is from July.
Dec 4 2017
Nov 29 2017
High priority and no progress for nearly a month?
Nov 5 2017
Well nfs1 is definitely not being backed up.
db* is getting backed up as far as icinga and bacula are happy.
Oct 6 2017
SPF reinstalled Bacula so everything should be back to normal when the next run is scheduled.
Oct 3 2017
Jul 10 2017
Jul 9 2017
Jun 27 2016
Jun 26 2016
May 9 2016
May 5 2016
Apr 18 2016
This was just for the daemon (as the title states).