Change Details

**Scheduled for 2019-09-29 11:30:00 UTC** https://docs.google.com/document/d/1rHFMeuxQ6qOaLumsENYhkkf7sNo6PNav63az71Ii0Tg/edit The steps are in this exact order. [x] fixing that TODO Jaime mentioned in order to have the iptables hole opened [Alex is doing this] [x] Move archive pool files into backup1001/2001 so they are not lost even if helium/heze go down. (Production rolls over, so it would be less problematic, as long there is some backup?) DONE. [x] Test a full backup/restore cycle on a new remote host towards backup1001 to validate new setup [Jaime did this] [] Change helium to an sd role of the new director backup1001 (or if for some reason that is not possible, to an easily revertable noop role). Start with either an upgraded current bacula db “bacula” (and a backup generated) or on an upgraded copy of it “bacula9”. [] update references to helium all over puppet * Prepared: https://gerrit.wikimedia.org/r/c/operations/puppet/+/544665 [] check newly backup1001/2001 backups run as expected and they can be recovered [] Make sure we can recover from backup1001 helium/heze pools. Keep helium heze around for 3 months so new backups got to backup1001/2001, but old can be recovered from [] Reattach locally to backup1001(/2001) the helium archive files moved on step 2

**Scheduled for 2019-09-29 11:30:00 UTC** https://docs.google.com/document/d/1rHFMeuxQ6qOaLumsENYhkkf7sNo6PNav63az71Ii0Tg/edit The steps are in this exact order. [x] fixing that TODO Jaime mentioned in order to have the iptables hole opened [Alex is doing this] [x] Move archive pool files into backup1001/2001 so they are not lost even if helium/heze go down. (Production rolls over, so it would be less problematic, as long there is some backup?) DONE. [x] Test a full backup/restore cycle on a new remote host towards backup1001 to validate new setup [Jaime did this] [x] Change helium to an sd role of the new director backup1001 (or if for some reason that is not possible, to an easily revertable noop role). Start with either an upgraded current bacula db “bacula” (and a backup generated) or on an upgraded copy of it “bacula9”. * Prepared: https://gerrit.wikimedia.org/r/c/operations/puppet/+/544665 [] update references to helium all over puppet [] check newly backup1001/2001 backups run as expected and they can be recovered [] Make sure we can recover from backup1001 helium/heze pools. Keep helium heze around for 3 months so new backups got to backup1001/2001, but old can be recovered from [] Reattach locally to backup1001(/2001) the helium archive files moved on step 2

**Scheduled for 2019-09-29 11:30:00 UTC** https://docs.google.com/document/d/1rHFMeuxQ6qOaLumsENYhkkf7sNo6PNav63az71Ii0Tg/edit The steps are in this exact order. [x] fixing that TODO Jaime mentioned in order to have the iptables hole opened [Alex is doing this] [x] Move archive pool files into backup1001/2001 so they are not lost even if helium/heze go down. (Production rolls over, so it would be less problematic, as long there is some backup?) DONE. [x] Test a full backup/restore cycle on a new remote host towards backup1001 to validate new setup [Jaime did this] [x] Change helium to an sd role of the new director backup1001 (or if for some reason that is not possible, to an easily revertable noop role). Start with either an upgraded current bacula db “bacula” (and a backup generated) or on an upgraded copy of it “bacula9”. [] update references to helium all over puppet * Prepared: https://gerrit.wikimedia.org/r/c/operations/puppet/+/544665 [] update references to helium all over puppet [] check newly backup1001/2001 backups run as expected and they can be recovered [] Make sure we can recover from backup1001 helium/heze pools. Keep helium heze around for 3 months so new backups got to backup1001/2001, but old can be recovered from [] Reattach locally to backup1001(/2001) the helium archive files moved on step 2