From: Dan S. <da...@sh...> - 2007-09-07 11:17:26
|
Hello, I'm from OpenChange, the native-protocols Exchange replacement project at http://openchange.org. We have been thinking about backup, and are developing MAPI-level backup tools (a small advance on what we have already developed.) The basic assumption is that backups of mailboxes, public folders (ie, all the other stuff such as calendars) and groups of the above are important to many users. With full permissions and metadata. Do you have user demand for this sort of thing? We have written a summary of MAPI issues from a backup implementor's perspective at http://wiki.openchange.org/index.php/OpenChangeForMAPIStoreBackup . You'll find there details of commandline facilities proposed, and clearly this will show you how to use libmapi to achive similar things (only better, since you're backup experts.) We have Perl bindings and are GPL2+ like BackupPC. Feedback wanted! There's the openchange-devel mailing list, the wiki, and irc. We want to push our backup client soon, but want to be sure the design is approximately right as well. We had a discussion with the Bacula people today which had some interesting Backup points but quickly became a problem of license incompatibility. Intro message from me, with MAPI definitions for backup people: http://mailman.openchange.org/pipermail/devel/2007-September/000347.html Arno Lehmann on aspects of backing up Exchange: http://sourceforge.net/mailarchive/forum.php?thread_name=46E12E01.2090201%40its-lehmann.de&forum_name=bacula-devel Regards, -- Dan Shearer da...@sh... |
From: Dan S. <da...@sh...> - 2007-09-11 20:39:02
|
Hello, I'm from OpenChange, the native-protocols Exchange replacement project at http://openchange.org. OpenChange provides client and server facilities, and right now we're concentrating on the client library, libmapi. libmapi can access Exchange in the same way, and a bit more, that Outlook can. libmapi has many uses, from mail and groupware clients to VOIP integration to, yes, backup :-) A preliminary and sample backup tool for MAPI has just hit svn. Some background for this can be found on the wiki[1] and in a thread on the -devel mailing list[2]. We have thought about the problems from the point of view of MAPI, but of course we are not backup experts. We are looking for developers who understand backup well to try OpenChange and tell us what you think needs to be changed. We're heading for a first major release in a few months and really need feedback. Some definitions relevant to OpenChange: * MAPI Store. That's Microsoft Exchange. We have a prototype server and after our client is released we'll be making sure that we are also a MAPI store. * MAPI Client. That's either OpenChange libmapi (and the commandline client that ships with OpenChange, openchangeclient), Outlook, or some of the third-party groupware applications that use the same Microsoft MAPI library as Outlook. libmapi works like Exchange. * libmapipfadmin. Like libmapi, only it adds administrative functions. This may be of some use to a backup suite. * openchangemapidump. The cause for this posting :-) libmapi is GPL. There's the openchange-devel mailing list, the wiki, and irc. Feel free to drop in! Regards, -- Dan Shearer da...@sh... [1] http://wiki.openchange.org/index.php/OpenChangeForMAPIStoreBackup [2] http://mailman.openchange.org/pipermail/devel/2007-September/000364.html |
From: Dan S. <da...@sh...> - 2007-09-12 12:52:18
|
On Wed, Sep 12, 2007 at 06:08:39AM +0930, Dan Shearer wrote: > Hello, And that was just spam the second time. Sorry everyone. I got confused in the middle of the night :-) Dan |