Hi,
During the last few days, MySQL database replication has
been activated between suda and ariel. suda is master,
ariel is slave. To do this, a downtime of suda was needed.
If there are writes to a MySQL slave, the replication will
break. In that case the replication has to be set up again
from scratch.
To avoid downtime in that case, we're currently setting up
a second slave. This slave is not going to be used for
any queries. If the first slave fails, a copy of the
second slave can be made without taking down the master.
The latest database dump has been generated from ariel,
without any problems. During the copying of the data files
from suda to ariel, ariel served an old DB copy, without
any problems.
The second slave will be set up on zwinger and will most
likely only replicate once per day in off-peak hours.
To have enough disk space available, log files are
currently being moved to yongle and yongle will be
used to compute access statistics from the squid logs.
As soon as the second slave is working, ariel will be
used for service.
Regards,
JeLuF