On 14.03.2011 17:27, Anne-Marie Scheidegger wrote:
What do you use for nightly backups? pros? cons? Any input is appreciated!
Hi Anne-Marie,
we have 2 backup actions, each night.
1) Virtual Machine snapshot: Webapp + DB Server
- pros: easy to implement, often is configured out-of-the-box in VM
appliances; extreme quick to perform: few minutes!; hot-backup, no
shutdown needed; quick to recover: just power up a new virtual machine!
- cons: you have to virtualize your infrastructure; you need quite big
file repositories, backup files are huge; sys-admin rights, privileges
and knowledge needed
2) We have developed a custom backup job. We use a scheduled command and
the packager module. We define the packages we want to be backupped and
the command job runs at 4.00: it looks into package definitions, runs
the package command for each definition and saves the output (zip) file
into a backup directory.
- pros: easy to configure; application-scope; we backup only what we
need; few and small files for each backup; quick solution: 10 minutes
for about 20 sites; we save website, dms and custom configurations. No
jars (they are on our SVN/Maven repo), no scripts, no markup.. only
content and config; each file can be used for a quick recovery: imagine
for instance a customer that delete a page and want it back. You open
another magnolia (maybe a trial not-productive EE on your laptop), you
upload the package (.mgnl), extract it, export the page and take it back
on production. 10 minutes for a surgical recovery!
- cons: is not enough for a full backup, you need to have the webapp
backupped too..
In my experience, the first option is the most affordable / secure /
stable solution.
The second is the best for punctual and surgical recovery operations.
HTH!
Matteo
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
