Debian has a number of packages enabling remote (over the network) backup: backupPC, backupninja, backup-manager, dirvish, duplicity, luckybackup, rdiff-backup, and some others.

In my setup I wanted backups to be initiated by the external backup server (as opposed to internal, production server initiated backup). Also, I was going to backup linux server to another linux box. Thus, it would be preferable to have support for rsync on both boxes and hardlinks on the backup box. I needed backup to be run regularly, I didn’t need any kind of GUI, and I would prefer to keep a bunch of older backups around (in case the most recent backup is of a compromised system, for example). Also, having an incremental backup of SQL databases was yet another requirement.

A few tools more or less matched my requirements: backupPC, duplicity, rdiff-backup, and dirvish.

backupPC, judging from its description and a few tutorial articles, is a cool piece of software. I think I might use it next time. But this time I really had no need for over-SMB backups (intended for Windows boxes), and no need for a nice administrative web-interface to backupPC. If not these extra features (which I don’t currently need) I’d go for backupPC. Here’s a guide for Ubuntu.

Duplicity claims to still be in beta, thus I haven’t given it a try. rdiff-backup seemed a bit too simple (and with no ready templates to get working regular backups faster), so I skipped that one as well.

Dirvish really caught my attention, partially thanks to a good and relatively short quick-start tutorial. That tutorial also mentions automysqlbackup – a nice, almost no-configuration tool to take regular dumps of MySQL databases. In combination, these two now regularly backup up my whole server to another linux box.

I would definitely recommend using dirvish+automysqlbackup for remote/off-site backup needs. However, other solutions might be as good or better for your use case.

For about 2 weeks now, I am every day alerted of the suspicious behavior of some computer/server from the Google’s IP range:

Dec 5 05:39:33 mx suhosin[3701]: ALERT – tried to register forbidden variable ‘_REQUEST[option]‘ through GET variables (attacker ’66.249.71.20′, file ‘html/index.php’)
Dec 5 05:39:33 mx suhosin[3701]: ALERT – tried to register forbidden variable ‘_REQUEST[Itemid]‘ through GET variables (attacker ’66.249.71.20′, file ‘html/index.php’)
Dec 5 05:39:33 mx suhosin[3701]: ALERT – tried to register forbidden variable ‘GLOBALS’ through GET variables (attacker ’66.249.71.20′, file ‘html/index.php’)
Dec 5 05:39:33 mx suhosin[3701]: ALERT – ASCII-NUL chars not allowed within request variables – dropped variable ‘mosConfig_absolute_path’ (attacker ’66.249.71.20′, file ‘html/index.php’)
Dec 5 05:39:42 mx suhosin[3701]: ALERT – tried to register forbidden variable ‘_REQUEST[option]‘ through GET variables (attacker ’66.249.71.20′, file ‘html/index.php’)
Dec 5 05:39:42 mx suhosin[3701]: ALERT – tried to register forbidden variable ‘_REQUEST[Itemid]‘ through GET variables (attacker ’66.249.71.20′, file ‘html/index.php’)
Dec 5 05:39:42 mx suhosin[3701]: ALERT – tried to register forbidden variable ‘GLOBALS’ through GET variables (attacker ’66.249.71.20′, file ‘html/index.php’)
Dec 5 05:39:42 mx suhosin[3701]: ALERT – ASCII-NUL chars not allowed within request variables – dropped variable ‘mosConfig_absolute_path’ (attacker ’66.249.71.20′, file ‘html/index.php’)

These requests repeat up to several hundred times per hour, with periods of no or very little malicious requests.

Here’s WHOIS information about 66.249.71.20:

OrgName: Google Inc.
OrgID: GOGL
…
NetRange: 66.249.64.0 – 66.249.95.255
CIDR: 66.249.64.0/19
NetName: GOOGLE
NetHandle: NET-66-249-64-0-1
Parent: NET-66-0-0-0-0

Does Google attack you, too?

These attacks initially started from a different Google IP – 66.249.71.2; I wrote to abuse at google, and got an automated response with the ticket number (in the hundreds of millions range). A week after that, requests started flowing from IP 66.249.71.20. I am not inferring “evil Google abuse department” here, just that there was no response, and the problem shifted to a different IP from the Google’s IP range.

Update: I decided just to ignore this class of problems.

“Evil?” image by copyblogger.com.

• SysCP
• Domain Technologie Control, DTC
• Virtualmin (also Webmin, Usermin)
• ISPConfig
• RavenCore (no longer developed)
• GNUPanel

SysCP: looks good to me (though demo isn’t functional), has customer billing module. Unsure as to where it is used, but most probably sponsors are also the users of SysCP. Majority of support forums are in German.

DTC: has no demo, only some screenshots. Has a set of packages for Debian lenny (which is a huge plus for maintenance and future upgrades). DTC is being developed by GPLHost, and is also used by GPLHost – so this is a live (used) distribution. Seems quite feature-rich.

Virtualmin claims to be the “world’s most powerful and flexible web server control panel”. Virtualmin offers 4 means to control it: Web, mobile device, command line, and remote API. There are both screenshots and demo. Has both GPL and Professional versions. GPL version has a number of limitations, comparing to Pro version. From what I’ve read about Webmin (all three – Virtualmin, Webmin, Usermin – are just different “layers” of server control), it is a framework with a number of “interface scripts”, which allow to control various services. As such, it is easily extendible, but is not monolithic – in the sense of module inter-dependencies and action triggers.

RavenCore was a promising CP.

GNUPanel is a year-old control panel, but has a news item on the front page (dated August, 17) promising new, completely rewritten release somewhere in October. By the feature list, looks promising. However, I need the panel right now, and even in October, that will be quite a rough release, not really used/tested anywhere, so not a good option as well. But GNUPanel is a panel to check in half a year for progress.

As the final choice, I had ISPConfig (which seems to be the best by people’s comments), and which is also quite widely used, and is easy to install onto Debian (at least the Perfect setup: Debian Etch says so), and DTC. I discarded Virtualmin (for the poor functionality of the GPLed version), RavenCore (for the lack of current descriptions and non-functioning demo), GNUPanel (which just isn’t ready yet), and SysCP (because ISPConfig seems better ).

As DTC has Debian packages (and will be easier to maintain/upgrade), I decided to try it first. I already have it installed (that’s easy, esp. if you first read the DTC Debian Express Setup). Later I might post my impressions from using DTC.

Update: DTC is indeed easy and pleasant to use. I had problems allowing FTP and SSH access using MySQL authorization, but at least FTP was an easy one to fix (SSH access with MySQL authorization is still unconfigured, but that’s a low priority for me). There is a minor concern about the files and directory permissions setup, but thanks to chrooted environment that is only minor concern. Use of a single Apache installation for hosting admin and serving user sites might be a sub-optimal decision, but it works. Traffic and disk space accounting are plain superb! Server memory use for the dtc-toaster installation is troublesome, but for a powerful RAM-my server that is not a problem (I now have about 800-900MiB RAM occupied, but that includes the XCache’s cache, quite big MySQL cache, and loads of Apache and PHP modules).

But I’m still willing to try other control panels. As I expected, GNUPanel hasn’t released anything yet; Ravencore‘s online demo is still unfunctional; ISPConfig has recently released RC (and their demo is working as it should and as it used to); SysCP is also up and running fast. If my little hosting service starts pouring in some cash, then I’ll try SysCP on my second server – to compare it with DTC, and choose one of them for further support/extension/localization.

Finally, just a useful resource if you need a shiny name for your brand-new 2.0-beta project: anagram server.

First thing to think about: at least they did transfer all my emails to the new account.

Second: hey, they had given up their own email interface! Are they leaving the web-portal market of Ukraine? Was the part of their team (which later formed MI6) too important to handle their exodus with no consequences? Is that just a desire to give customers “better” interface and not invest anything into development?

I hope this won’t be a trend, for every service to have Google behind their servers. Or even just behind the name, to avoid extra complexity of having a server.

Finally, I think I’ll get used. But it was only yesterday, that I read the Google anti-utopia, where Big Brother’s name is (evidently) Google, and it’s webcams and microphones and search history define each person’s future AND guilt. Scary…

And I wonder which will be the next service of bigmir.net, “outsourced” like their email.

int main () {
unsigned int i;

for (i = 0; i < 2 ; i++ ) { i = 0; } return 0; } [/c] compiled it and executed several times on the GoDaddy shared hosting server. I did observe the program running for the maximum of 20 seconds of CPU time, not a second more. Please note, that 20 seconds of CPU time can be much more of “real” time, if the script isn’t using 100% of CPU, which often the case for shared hosting. Thus if you have in your php.ini max_execution_time set to, say, 60 seconds, your php script may actually execute as long as one minute; but I’m pretty sure that if your script has lots of CPU-intensive procedures, then as soon as it uses 20 seconds of CPU time, it will be terminated (however, this statement still needs checking – anyone?). To verify, I also created a cron job with the same file. It ran for 30 seconds CPU time. Strangely, this behaviour is not documented anywhere. This limit may also explain a number of other problems, if you have heavy web-applications: they just might be killed before they are finished, causing errors. I do understand the reason for this limitation, and am sure similar limitations exist in other shared hosting environments. The only important thing here is that this limit should have been documented and even put upfront somewhere in the hosting plans descriptions. I also wonder if the limit is the same for all godaddy shared hosting plans, or if it differs. 20 seconds when executed from PHP, and 30 seconds when executed as a cron job were observed on the Deluxe Linux Hosting plan. Extensions, additions and comments are welcome.