Changes between Version 3 and Version 4 of red-mosh-reorganization


Ignore:
Timestamp:
Jul 9, 2018, 9:59:24 AM (4 months ago)
Author:
https://id.mayfirst.org/jamie
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • red-mosh-reorganization

    v3 v4  
    2121
    2222We will also setup several MySQL proxies (that will respond via round robin DNS to mysql.mayfirst.org). Each proxy will properly route the database request to the proper back end host, so members will all simply configure their web apps to use the host mysql.mayfirst.org.
     23
     24== Phase one: backup chages ==
     25
     26Our current backup strategy places an enormous disk i/o strain on our servers. While this strain is mostly confined to off hours (for US and Mexico members), it often continues for some servers past 10 or 11 am America/New_York time, thus contributing to the disk i/o strain during our peak time.
     27
     28The problem is that we run ''both'' an onsite rdiff-backup with 10 days of increments saved followed immediately by an rsync off-site backup. That means all files on all servers are ready twice.
     29
     30We could signficantly reduce this load by instead running an rsync backup to our onsite backup server, then running an incremental backup from the onsite backup server to the offsite server during the day (and perhaps switching from rdiff-backup to borg-backup to see if we get better performance (see [ticket/12677#comment:15]).
    2331
    2432== Phase one: File system re-organization ==