Hi Nils That's great to know.
Thanks, Anne On Mar 14, 2011, at 6:07 PM, Nils Breunese wrote: > I just wanted to mention that it's pretty easy to switch a table from MyISAM > to InnoDB (even on a live setup, though we shut down each Magnolia instance > one by one for this conversion) using the following SQL statement: > > ALTER TABLE tablename ENGINE = InnoDB; > > We did this a while ago ourselves, maybe the shell script we used to convert > all tables is helpful to you, so I attached it. (The script takes a list of > database names to process. If your MySQL server requires auth, you'll need to > add the -u and -p options to the mysql commands in the script yourself.) > You'll also want to set "default-storage-engine = InnoDB" in your MySQL > server configuration to make sure future tables are also created using the > InnoDB engine. > > Nils. > ________________________________________ > Van: [email protected] [[email protected]] > namens Anne-Marie Scheidegger [[email protected]] > Verzonden: maandag 14 maart 2011 17:27 > Aan: Magnolia User-List > Onderwerp: [magnolia-user] Nightly backups > > Hi all > > I know the topic has been discussed here and described on the Wiki, but > somehow I'm missing the overview. So here is my first attempt and I'd be > happy to include any corrections and comments and post the whole thing as > "Backup - the overview" on the Wiki: > > (What I'm trying to figure out is: What's the best backup tool for our > nightly backups. We have been using the Export servlet, but it uses a lot of > memory and/or fails on our bigger repositories. We use the Community Edition > 4.4.2 with MySQL, some with single-site, some with multi-site setup. The > hardware servers are being backed up, too. But we don't want to restore the > entire server, if for example a customer goofed and deleted their website > repository.) > > 1. Backup with Backup module > - pro: works without shutting down (= hot backup), even when using > externalBlobs=true > - contra: full backups only > - contra: Enterprise Edition only > Is this the same backup method as "Backup with Packager" mentioned, > for example by Matteo Pelucco (Tinext) on mailing list on Apr 30, 2010 (Re: > Single WebSite Backup)? > > 2. Backup with Export servlet > see: > http://wiki.magnolia-cms.com/display/WIKI/Repository+backup+and+restore > - pro: works without shutting down (= hot backup), even when using > externalBlobs=true > - pro: granular backups > we can create an xml file for each customer and their website, > dms, data, etc. > example: > website.site1.xml, dms.site1.xml > website.site2.xml, dms.site2.xml, > data.site2.xml > etc. > - pro: easy to use because anybody with access to AdminCentral can > restore > - contra: doesn't work so well on large repositories (uses too much > memory or doesn't work at all) > > 3. Backup with Tools > toolsv4_1.jsp > see: http://wiki.magnolia-cms.com/display/WIKI/Backup+and+restore > - pro: ? > - contra: ? > > 4. Backup with JSP Scripts > runThread.jsp > backup.jsp > see > http://wiki.magnolia-cms.com/display/WIKI/Backup+and+Restore+JSP+Scripts > - pro: ? > - contra: comments don't make me think that this is meant to be used > for nightly backups > > 5. Backup of database or filesystem > for example: mysqldump > see for example: > http://dev.mysql.com/doc/refman/5.5/en/mysqldump.htmlhttp://www.thegeekstuff.com/2008/09/backup-and-restore-mysql-database-using-mysqldump/ > Is there a howto for hot backup of mysqldump and magnolia? I have only > found this comment by Jan Haderka 17.12.2010: > make sure that the DB is transactional ( in case of MySQL it > means that you need to use InnoDB instead of MyISAM) > (To find out which you use, log onto database on command line > and type "show table status;". We have MyISAM. Should have done this research > before setting up the latest Magnolia...) > - pro: easy on the memory? > - contra: doesn't work when using externalBlobs=true > > What do you use for nightly backups? pros? cons? Any input is appreciated! > > Thanks, > Anne > > > > > > > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- > > ------------------------------------------------------------------------ > VPRO www.vpro.nl > ------------------------------------------------------------------------ > > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- > > This part of mail contained an attachment with prohibited file name: > > MIME type: application/octet-stream > File name: alter_tables_to_innodb.sh > File size: 542 B > > > The attachment was removed by Kerio Connect 7.1.3 > at mail.magnolia-cms.com. > ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
