Backups/nl

Miraheze heeft interne en externe procedures omtrent back-ups. Kritische toepassingen worden automatisch geback-upt naar een externe server (deze server is onder het beheer van Miraheze, maar wordt gehost door een andere provider en ander land ten opzichte van onze normale servers). Deze 'interne' back-ups bestaan uit volledige 'database dumps', welke weer bestaan uit onder andere gebruikersinformatie, artikelen en CheckUser-informatie. Deze back-ups kunnen alleen worden ingezien door de systeembeheerders zodat deze ze kunnen gebruiken om de website zo snel mogelijk online te krijgen in het geval van problemen.

As such, Miraheze has a total of three types of backups which are taken. On top of this, users may generate their own backups, quickly and conveniently on demand using our DataDump tool.

Backup types
Miraheze takes three types of backups to ensure as much resiliency as possible.


 * Internal backups are backups kept on hand which the Site Reliability Engineering team can use to quickly bring the entire site up in the event of a catastrophic failure. These backups include full database dumps, which include user account information and CheckUser information. See the schedule below for more information.
 * External backups are automatic backups kept on servers controlled by us but on a different host and in a different country. This is done to ensure that a failure on one host or in the power grid of one country, etc., doesn't cause extended downtime or data loss to our users. These types of backups include critical parts of our infrastructure such as the databases of all wikis, private Git repository data, Phabricator configurations, and much more. See the schedule below for more information.
 * Public backups are XML backups which we upload every month to archive.org of all public wikis. We do this to make sure we have a reliable backup of all wikis on an external site along with to ensure users have peace of mind by seeing a backup that is readily available for usage by us/them.

General backup schedules
Up to date as of 12 January, 2023

Miraheze automatically runs the following backups for disaster recovery purposes:


 * Internal/External


 * De volgende gegevens worden elke zondag volledig geback-upt:
 * Onze interne git repository (puppet1)
 * Hierin worden wachtwoorden en private keys opgeslagen
 * Ganglia (misc2)
 * ACME (mw1)
 * Hierin staan onze private keys en certificaten van wiki's die gebruik maken van SSL-certificaten uitgegeven door Let's Encrypt
 * De volgende gegevens worden op de eerste zondag van de maand volledig ge-backupt. Op de derde zondag van de maand worden veranderingen (dus tussen de eerste en derde zondag van de maand) ge-backupt:
 * Databases van alle wiki's (bevat o.a. gebruikersinformatie, artikelen, logboeken, etc.)
 * Zgn. 'static' content (afbeeldingen, XML dumps)
 * Phabricator static (afbeeldingen en documenten opgeslagen door onze bugtracker)


 * Not currently ran: Static images for all wikis


 * Public
 * Monthly: All public wikis; XML dumps uploaded to archive.org

Manual backups
On top of our internal, external, and public backups, users may generate their own using different ways.

 Back-ups van wiki's

Naast deze back-ups, welke privacygevoelige informatie bevatten, kunnen systeembeheerders op aanvraag XML-dumps beschikbaar stellen (via onze sites of e-mail, zowel voor openbare als privéwiki's). Deze back-ups bestaan uit artikelen en logboeken, en kunnen probleemloos worden geïmporteerd op elke wiki die de MediaWiki draait.

To use DataDump, go to Special:DataDump on your wiki and select what backup you want. Once you submit your request, your backups will be generated. Depending on the size of the wiki, it may take from a few seconds up to a few hours to generate a database dump.

DataDump API
DataDump offers an API module which lets users use DataDump via the command line. As of yet, there are no scripts that make use of this.

Wikiteam dumpgenerator
While we strongly recommend using DataDump as it's the most convenient, you may also generate a database dump using less interactive command-line scripts. We do not recommend any in particular nor do we endorse any. However, one of these such well-known scripts is the Mediawiki Client Tools' Mediawiki Scraper Python 3 script, based on the original WikiTeam Python 2.7 script.

User account information will not be preserved. The XML dump can include full or only most recent page history. The images dump will contain all file types with associated descriptions. The siteinfo.json file will contain information about wiki features such as the installed extensions and skins.

 Zie ook
 * Bacula (former backup system)