Hi all, we're running fedora in "leader/follower" configuration so the ingest phase is going on the leader node and followers are in read only mode. Fedora datastores are on local FSs and all the VMs access a shared FS for the journals. We're using a load balancer in order to distribute API-A calls to the nodes. Given this configuration i would like to perform scheduled hot backups of a follower without stopping fedora or changing the LB configuration.
We think we have to suspend the journaling on a follower node in order to perform a safe backup on it. What do you think? We could not find a way to "suspend" the RMI journaling without a fedora restart. Can you confirm this? Given this configuration and these constraints, IF we find a way to "suspend" the journaling (ie using the FS transport), do you think it would be safe to perform a hot backup of a follower node even if it is running (=readonly access)? We're wondering about open files or similar problems. Thank you in advance, all the best, Matteo ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ Fedora-commons-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fedora-commons-users
