I have to recover a complete CA and I would recommend you to backup all.
1. database 2. openca-var 3. openca-etc 4. openca-lib 5. htdocs 6. cgi-bin 7. openca perl modules 8. openca binaries (bin and sbin)
Please don't think that it is an easy task to recover OpenCA if you don't have the original source or binary packages after a complete crash. If there are working packages of OpenCA in a distribution then you can remove openca-lib, openca perl modules and openca binaries from this list but you must run configure_etc.sh after such a recovery.
Hello,
well, I don't use any distribution package; I installed OpenCA from sources. But I don't have 'configure_etc.sh' in my openca src tree ( I think it's included in openca 0.9.2, and I use 0.9.1.3 ).
Anyway, why should I save directories such as openca-lib, cgi-bins, perl modules and binaries? Are they written in everyday operations (like certificate issuing), maybe with temporary files? Can't I assume them to be somehow more 'static' than database and openca-var?
What about 2 backup levels: a big one, including openca-lib, perl modules, binaries and so on, to be run for example once every some months, and a normal backup (an 'everyday' backup), saving only database, var and ldap?
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Openca-Users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/openca-users
