> So, we are currently pallning to go for rsync (includingresourceIndex) > + DB export on leader/DB import on DR, to get the DR up-to-date. > > Does this make sense ? > What's your opinion about the whole architecture ? > Ideas/comments/suggestions/criticisms welcomed...
Back when I was with the NSDL, we found journaling to be much easier: https://wiki.duraspace.org/display/FEDORA35/Journaling Some problems with Rsync and database dumps: - resourceIndex file might be corrupt if a write occurs during transfer, or if all data hasn't yet been sync'd to disk - Database and filesystem objects can theoretically be out of sync if a write occurs during either db dump or file rsync Journaling has some advantages: - Follower is only slightly behind leader - Journal files are written and queued even if follower is slow or turned off - Follower can be taken offline at any time for safe snapshot backup in a guaranteed consistent state. -- Follower will simply "catch up" when turned back on - Journal files (if kept around for a period of time) are very helpful for disaster recovery or investigation of problems, as they contain all data for an ingest or modify. We used RMI transport, with listener daemons on each follower, which would write journal files to a directory that is readable by the follower Fedora instance. -Aaron ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Fedora-commons-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fedora-commons-users
