Offload

fgm - March 28, 2007 - 19:52

"Offload" allows sites to offload non-essential data, typically, those used for archiving, to an off-site repository, where they can be kept as needed for either compliance needs or more mundane statistical analysis, without having to maintain them on a production site where they add load to the main DB server.

It will expected to be mostly useful to larger sites. Prime targets for offloading are the accesslog, watchdog and (contrib) zeitgeist tables.

Structure

The project is in two parts:

  • a "front-office" server Drupal module, operating on the web server essentially as a "driver" to control access to the DB using the Drupal API and access control
  • a "back-office" client built as a traditional (non-Web) cross-platform UI (php-gtk) to manage the synchronization.

The client connects to its local back-office DB using local access, and indirectly to the remote Drupal DB via the module, over XML-RPC.

Prerequisites

  • Drupal site: 4.7.x with MySQL ≥ 4.x
  • Client UI:

For developers wishing to submit patches to offload, please read the OSInet coding standards for Drupal document.

Releases



 
 

Drupal is a registered trademark of Dries Buytaert.