#31786: move dictyotum off moly -------------------------------------------------+------------------------- Reporter: anarcat | Owner: anarcat Type: task | Status: | needs_review Priority: Medium | Milestone: Component: Internal Services/Tor Sysadmin Team | Version: Severity: Normal | Resolution: Keywords: | Actual Points: Parent ID: #29974 | Points: Reviewer: | Sponsor: -------------------------------------------------+------------------------- Changes (by anarcat):
* status: assigned => needs_review Comment: the procedure I actually followed is documented in "Restore the directory server" in: https://help.torproject.org/tsa/howto/backup/#index5h2 Specifically, I have: 1. shutdown postgres on both servers 2. redid a BASE backup 3. restored the base backup on the new server 4. changed the bacula user password in postgres 5. started the director (it was actually not stopped, but that didn't seem to matter) 6. re-enabled and ran puppet on the director, holding a lock on the scheduler 7. switched over a few nodes (perdulce at first, then pauli and alberti) and ran backup jobs on them 8. switched over *all* nodes, and ran puppet everywhere 9. ran puppet on the storage and new director servers 10. released the lock on the scheduler I ran another backup job on crm-int-01 because it seems like an important server to backup, and might run more manual jobs on different servers like this, but not all, so we know the scheduler works. Once all backups return to normal, I guess it will be time to decom dictyotum! -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/31786#comment:6> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs