We will generate on es2002 (and maybe somewhere else) an offline copy of es2 and es3 content (es1 is already at es2003 and es2004) as a one-time copy, in case of a huge disaster. This will unblock pending maintenance work and server until a proper solution is in place for proper automatic incremental backups.
Description
Description
Event Timeline
Comment Actions
Change 423949 had a related patch set uploaded (by Jcrespo; owner: Jcrespo):
[operations/mediawiki-config@master] mariadb: Depool es2015 for maintenance
Comment Actions
Change 423949 merged by jenkins-bot:
[operations/mediawiki-config@master] mariadb: Depool es2015 for maintenance
Comment Actions
@ayounsi We are performing this 5.4TB backup by saturating the es2015 and es2002 host links, it will take 12 hours.
Comment Actions
Change 424227 had a related patch set uploaded (by Jcrespo; owner: Jcrespo):
[operations/mediawiki-config@master] mariadb: Repool es2015, depool es2019
Comment Actions
Change 424227 merged by jenkins-bot:
[operations/mediawiki-config@master] mariadb: Repool es2015, depool es2019
Comment Actions
Mentioned in SAL (#wikimedia-operations) [2018-04-05T08:30:20Z] <jynus> starting backup of es2019, it may create lag T153440
Comment Actions
es1 is in es2003/es2003 as a binary copy.
es2 and es3 is in es2002 as logical copies.
Comment Actions
Change 424745 had a related patch set uploaded (by Jcrespo; owner: Jcrespo):
[operations/mediawiki-config@master] mariadb: Repool es2019 after maintenance
Comment Actions
Change 424745 merged by jenkins-bot:
[operations/mediawiki-config@master] mariadb: Repool es2019 after maintenance