Randy,
Even though you mentioned mirroring (or rather, using Fedora's Journaling
Module) is not in the cards for your repo, that would probably be have been my
preferred route, where you have a follow server with which you have a little
more freedom to perform a consistent backup.
However, since that's what you specifically didn't ask for, I'd use an XACML
policy to disable writes to the repo:
https://wiki.duraspace.org/pages/viewpage.action?pageId=30221092
-Eddie
--
Edwin Shin
MediaShelf
On Feb 8, 2013, at 2:15 PM, Randy Fischer <r...@ufl.edu> wrote:
> We're trying to plan out a medium-to-largish fedora installation, ~30 TB, and
> I have questions on folks' experience with backup and maintenance procedures.
>
> As I understand it, the best procedure is to take fedora offline (a mirrored
> fedora is probably not in the cards for this size installation).
>
> Is it relatively straight-forward to set Fedora and Islandora into a
> read-only mode so that data/object store and database (ri, solr and the
> relational db) can be backed up, while the site is still accessible?
>
> We also like to schedule rotating fscks on the partitions, so we expect to
> have this occur pretty frequently.
>
> We're planning on using the akubra lowlevel store, with top level storage
> directories (0,1,2...d,e,f) mapped to 2TB or larger partitions.
>
> RedHat 6.x, 64bit server btw.
>
> Alternative configurations, success stories (horror stories) all appreciated.
>
> -Randy Fischer
------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
Fedora-commons-users mailing list
Fedora-commons-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fedora-commons-users
