On Monday, 19 June 2017 8:30:46 AM AEST Arjen Lentz via luv-main wrote:
> >time when we have 2 separate instances of Drupal and I don't want
> >anyone to
> >make changes to the old one that get lost.
>
> Re the backend MySQL storage, you make the new MySQL instance a slave of the
> old one. That
>time when we have 2 separate instances of Drupal and I don't want
>anyone to
>make changes to the old one that get lost.
Re the backend MySQL storage, you make the new MySQL instance a slave of the
old one. That way nothing can get lost.
We've find this many times with large systems. No
New hardware has been purchased for the system that hosts the LUV VM. The old
server is a i7-920, 8G of RAM, and 2*750G SATA disks. The "new" server is a
i7-930, 48G of RAM, 2*250G SATA SSD, and 2*2TB SATA disks. I put new in
quotes because it's not new hardware, it's hardware someone else
On 12/01/16 15:11, Russell Coker via luv-main wrote:
> When running at VPAC the watchdog table in the Drupal database took up 20G of
> disk space and as it was in the ibdata1 file there was no good option for
> freeing the space even after deleting most rows. As part of the migration to
>
Russell Coker via luv-main writes:
> Unfortunately we have some DNS issues. I've got a simple TCP proxy in place
> for the web server but that doesn't work so well for email as it breaks lots
> of anti-spam checks. I will use a proxy for the mail server if we don't have
As mentioned in a previous message (which many people on the list probably
didn't get) I've just moved the LUV server to a VM in Germany courtesy of Paul
Menzel who pays the rent on the physical hardware.
We had a few problems along the way with DNS records not updating when I
wanted them to
As previously discussed VPAC no longer officially exists and out hosting there
is going to disappear.
I have migrated the LUV server to a virtual maching in Germany on the Hetzner
network. This gives us plenty of storage, fast Internet access, IPv6, and
it's free (courtesy of a German Linux