I saw that issue come up & thought someone was fixing it. I thought the export/import was more for migrating config trees from one release to another rather than backup, but I see how being able to do this with the content is a good thing.
I've dabbled with using ANT to zip up backups, but since it was slow and sometimes ran out of memory was advised to use shell scripting. That was a little slow too until I switched to having it gzip the files. I have it create separate gzip files for public docroot, repositories, & templates, and author docroot, repositories, & templates. Should a problem arise, I suspect it would be in the repository, so would be able to restore just that. Have never had to though. Now that persistence is based on Berkley DB, maybe this wouldn't work anymore. -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] Sent: Thursday, December 15, 2005 10:19 AM To: [email protected] Subject: Re: [magnolia-user] Is 2.1.3 stable enough for commercial use? Greetings, On Dec 15, 2005, at 11:11 AM, (Robert Van Overmeiren) wrote: > Is anyone using Magnolia 2.1.3 in a commercial production setting yet, > or is it still to buggy for that? Yes, I am building commercial production sites for users with Magnolia 2.1.3. The biggest problem I have with that, as far as I know, all versions of Magnolia, is that content authors can very easily break my backup procedure by simply pasting in some content from Word or whatever. Magnolia's export feature cannot handle these "invalid XML" characters and before you know it you have 7 days of empty backups. If you use Magnolia's export feature for backups then you have to monitor the process. When things go bad, you have to find the page that caused the problem, locate the weird character (It probably shows up as a square box in your browser) and replace it. In some situations with many content authors I can see how this would be impossible, in which case you would need to devise an alternative backup strategy or fix the bug. - Tom ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ---------------------------------------------------------------- ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ----------------------------------------------------------------
