All, Having had my first database corruption with Bacula, which I don't feel too bad about after 11 months on a medium sized site (compared to Veritas!) I have now discovered dbcheck and its limitations.
I understand that dbcheck on a big database with millons and millions or rows like mine is going to take a long time. However, having the database locked for days on end is not really workable. So I thought I would start a discussion on possible workaround methods: 1. Per Client/Job Catalogues Clearly this would be quite inefficient but I can deal with suspending the backups of a single system or single job for a while. Also the dbcheck should be much quicker since it operates on a much smaller number of files. In my case I have a MySQL server dedicated to being a Bacula catalogue server and it has plenty of disc space so this might be a serious option for me, if not in general. Other than increasing the complexity of the installation somewhat and placing more work on the MySQL server, would there be other issues with this sort of setup? 2. Replicated MySQL Catalogue Server With a replicated server I could dbcheck against the slave while suspending the replication. Of course the master and slave would then be increasingly out of sync and I would still need to shutdown the master to fix problems encountered. Other ideas? comments? Thanks, Dominic ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
