In today’s gp/bp an open door will be kicked in: take your backups offsite!
I was actually tempted to create a poll to see how many of you do not have proper backups, and how many of you do not take those backups offsite. It is a simple piece of advice and relatively simple to set up. Offsite in this case would ideally be physically offsite: to a different server in a different building in a different location. A start however is to take them to a different server. And don’t make the mistake of thinking a different VPS on the same physical server is good enough. True, that will protect you from operating system failure of the guest, but it will likely not protect you from hardware failure, or operating system failure on the host OS.

Also, take good care of how you are getting your backups offsite. A normal FTP connection might do the job, but it is hardly secure. Ideally, use SFTP or rsync over ssh to stream your backups …

Following a promotion at the registry. We will be offering .EU domain creations for €4 excl. VAT instead of €12 excl. VAT. This sale will last until August 31st and does not concern renewals or transfers.

Following a promotion at the registry. We will be offering .US domain creations for €4 excl. VAT instead of €12 excl. VAT. This sale will last until July 31st and does not concern renewals or transfers.

Summer has come and this has put us in the mood to make you happy...

So in this summer spirit, here are some things that we have come up with to please you:

• Have you not yet tried our cloud hosting service? If not to help you make your change, we are going to give you a free server this summer! Yes, from now until August 31st (and by request from this form) you can have a totally free server (equal to one free share). And like any Gandi hosting share, you can expand the power/performance instantly with no downtime by adding additional shares at your convenience
• Are you already a Gandi Hosting customer? If you feel like it is terribly unfair that you cannot benefit from this promo and are already getting ready to write a nasty comment in reply to this article: there is no need, since the price of fixed …

PHP 5.3 is released and after the release stress is over my mind is open for new ideas. While relaxing yesterday I thought about many things, among them was the Resultset iterator I recently discussed.

Now I wondered where to go next with this and had the idea that an individual Resultset is a child of the whole result and this might be wrapped in an Recursive Iterator. For doing so we don't implement the Iterator interface but RecursiveIterator. RecursiveIterator extends a typical Iterator with two methods: hasChildren() and getChildren(). But now we have a problem: The Iterator returned by getChildren() has to be a RecursiveIterator, too, which makes sense, in general. But I want to return a MySQLi Resultset which isn't recursive - so making this a RecursiveIterator is wrong. My solution now is to introduce yet another Iterator which goes by …

There are some bug reports on the auto-discovery protocol in MySQL Cluster.
The idea of the auto-discovery protocol is to fetch the .frm files for the NDB tables stored in the data dictionary of the data nodes, and put them in the data directory of the mysql server.

However, sometimes (not always, which makes it more difficult to reproduce and hence fix), the auto-discovery seems to make strange things (from this bug report):

After shuting down and restoring my cluster I get the following error.

090211  9:59:26 [Note] NDB: mismatch in frm for panel.gatewayquestions, discovering...
090211  9:59:26 [Note] NDB Binlog: DISCOVER TABLE Event: REPL$panel/gatewayquestions
090211  9:59:26 [Note] NDB Binlog: logging ./panel/gatewayquestions (UPDATED,USE_WRITE)

This is due to the files already being in the mysql data directory. After …

Some key differences for DBAs between Oracle and MySQL database servers include:Different tools used to manage and monitor database servers.Oracle architecture is process based, MySQL architecture is thread based.Different tools used for backup and recovery.Database specific SQL syntax.Database specific SQL functions.Different syntax for stored routines. MySQL has no packages.MySQL routines are

There are different ways for starting up and shutting down a MySQL server. A MySQL server when it starts up it starts up all the way. When a MySQL server shuts down it shuts down all the way. MySQL cannot startup and and shutdown at different levels the way an Oracle database server can.

Oracle DBAs understand the importance of defining guidelines and standards and using them in the configuration and management of database servers. Years ago the Optimal Configuration Architecture (OFA) developed a base set of guidelines and naming conventions for Oracle DBAs.I developed the MySQL Optimal Configuration Architecture (MOCA) modeled after OFA to give new MySQL DBAs a set of

Storage needs to be managed for any MySQL instance. A MySQL database server does not have the same flexibility as an Oracle database server in terms of how to lay out the data storage. It is important to learn the data storage defaults and options.