Posts by bytesplit

Achtung: der Artikel bei Golem sagt konkret eher "BIS ZU 30 mal schneller..." lol

ich habe mein MySQL durch Percona ersetzt. Maria ginge auch noch. imscp interessiert das nicht wirklich, was genau da als Datenbank hinten ansteht. Da auch MemSQL binary-compatible sein soll, kannste ja mal testen. Aber solange die DB nicht über 1GB Größe hat, sehe ich keine Veranlassung hier was zu tun.

Bedenke ebenso, dass alle Apps auf Kunden-Websites ebenfalls damit laufen müssen (Wordpress, Contao, Typo3 oder whatever SQL backend nutzt). Schau lieber ob optimierung an MySQL settings noch was bringt, dann memcache für die Websites. Dann könntest Du noch die SQL-Queries selbst überprüfen und ggf. optimieren.

Das I-MSCP panel könnte man übrigens auch mal auf hiphop kompilieren und schauen ob dass dann viel schneller tut...

Hi,

first, I totally agree with Joximu. The previous backup must be deleted when only after the new one had be created successfully. Think of a power outage or so, where the new backup is not being dumped out. Then we are left with nothing.

Okay, for the full view... I'd like to partition it into the different work areas of the system:
Server hardware:
- use backup software + RAID + UPS or whatever, but this is absolutely out of the scope of the software. Think of service updates (e.g. MySQL) which break some startup script. Should i-mscp daemon monitor this and allow for recovery? To me an absolute no.

Control panel:
- this resides in the i-mscp database. We have transactions to keep the thing clean. Either dump the db before every change (impractical) or keep daily backups for 14 days (enough for my needs).

Servers (the machines running postfix, dovecot, apache, ...):
- we have that /etc/imscp directory where working configs are generated based on the database changes. So these could be moved/copied before every change. I don't know if the system generates ALL/every configs after any change or if it recognizes individual changes (e.g. mailbox added -> update postfix/dovecot or courier only). I would like to have review possibility in a folder structure based on changes made:
2011-12-13/19-21/(configs from that date)
2012-01-04/12-07/(configs from that date)

then it would be very easy to review changes to the server configuration. When were they made? What changed? Perhaps a log from manager could also be a good idea. Like a changelog:
Administrator altered mailusers -> generating new configs for services postfix, dovecot
Reseller 'horst' altered domains -> generating new configs for apache2, awstats

This to me is very important with multiple admins hacking the server(s). Also think of the m in i-mscp, multiple servers. A hell hard thing to monitor, especially when something breaks. I want a quick way to return to last known good state.

Last point, the users:
- x number daily backups. Select based on hosting plan, databases, sites, mailboxes. Selectable daily, weekly, monthly. This can create lots of traffic (tar 3000 users every night) for the hosts and lots of webspace to waste (keep 30 copies of 1 website is 30 times the space).
- a default for me is to backup the sites/databases only. Once daily, I guess it's what has been talked about in this thread here initially. Train the users to make backups between changes and all is good.
- When the customer is allowed to have multiple backup steps, then account this into his quota.
- I'm curious, can customers already run a restore from the web panel? Perhaps this could be useful.
- I do not make individual email backups. Most users still have POP boxes and download everything. I do nightly backups of /var/mail and can restore individual boxes via shell on demand, but that has never been the case in the last years.

Okay, I hope I haven't bloated this thread to much with my reply.

that's indeed very cool. And absolutely makes sense btw...

Can anybody enlighten me on this? How is this better now?

I'm still on ispCP, but upgraded my MySQL with InnoDB support in preparations of the crossgrade. Memory usage grew from 8 MB to 32 MB. InnoDB default was even way much highter...

So, yeah Inno allows transactions and more reliable writes to the tables. Is i-mscp already making use of this in the admin panel? Or are we at the cosmetical level just yet?

Just wondering. My setup is running on a VPS and I'm trying to quench out every mem of RAM I can...

SpamAssassin on my setup was pretty simple. I have it running via Amavisd. The main issue thus is how and where to save the settings for ham whitelist/spam blacklist.

Amavis can only handle a global SA list as it calls it identically for all users. I've implemented it that way now. Learning is done through internal emails for ham and spam which are written to maildir folders using sieve. Cron then feeds sa-learn.

Works but amavis and clamd eat 200 MB RAM... not that optimal.

The alternative would be using SpamAssassin alone with a MySQL db. Then users would tag their spam/ham in Roundcube webmail plugin. I think that's not that comfortable but well, time will bring an answer.

I personally think clamsmtp and dspam could be a decent alternative.

How is the plan for i-mscp?

Just as an info, I changed my values to read like this:

AFAIK *:bytes would only accept a byte value.

Btw: I also added an UNIQUE INDEX on mail_users.mail_addr, so that the MySQL can perform the user lookup faster. Perhaps this can be incorporated into the MySQL setup db.