Regarding #1. I'm using rsync more for populating default content in another instance then backups. Our host handles the primary file system backup on the remote server. I still don't like the idea of "url fetched backups", especially since 2.x doesn't support root calls. How can this method possibly scale without human intervention?
If you did switch to a database repository, backups should be even easier, as you'd be able to handle most, if not all, of this outside of Magnolia. -----Original Message----- From: user-list@magnolia.info [mailto:[EMAIL PROTECTED] Sent: 23 August 2006 17:04 To: user-list@magnolia.info Subject: Re: [magnolia-user] Getting Backups Going Hi Ben, Thanks for the comment. As much as I like rsync, I'd been avoiding file-system approaches for a couple of reasons: 1. According to the note at <http://www.magnolia.info/wiki/Wiki.jsp?page=BackupServlet>, copying files on a live repository has the potential to generate corrupt backups. 2. The file system approach ties you to JCR implementations that store their data in the file system. If we decide to switch over to using Jackrabbit/MySQL or CRX or something else in the future, the servlet method will still work. We're likely to be going pretty high-volume with our Magnolia installation over time, so having the option to switch to a higher-performance repository implementation is important to us. Sean On 8/23/06 10:35 AM, "Ben Brock" <user-list@magnolia.info> wrote: > I'm joining this discussion a bit late, but I'm working on the same so > I thought I'd chime in. I'm having a lot of luck using rsync. You > might consider trying it as an alternative. It seems to be working > flawlessly so far. > > The following command will copy the website content from one server to > another: > > rsync --verbose --progress --stats --compress -e ssh --recursive > --times --perms --links --delete > [EMAIL PROTECTED]:/path_to_tomcat/webapps/magnoliaAuthor/repositor > ie > s/website* > [EMAIL PROTECTED]:/path_to_tomcat/webapps/magnoliaAuthor/repo > si > tories/ ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ---------------------------------------------------------------- ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ----------------------------------------------------------------
