Hi, I thought I'd just put in a note that we have just done a successful upgrade to bacula 3.0 for a bacula system running 7 storage daemons with a total of ~70 TB data (all disk based, no tapes). Everything is running smoothly so far. The catalog in use is a mysql db totaling approximatly 110 GB. We did however skip the FileId -> BIGINT db update as we had to do that manually quite a while ago due to hitting the old limit in the catalog.
Also, the upgrade seems to have fixed a problem we have been seeing recently where certain windows clients were dropping the connection to the sd's during backup after a random amount of time. We were seeing repeated errors like: Error: ../../lib/bnet.c:439 Write error sending 12580 bytes to Storage daemon:x.x.x.x:9103: ERR=Input/output error Fatal error: append.c:259 Network error on data channel. ERR=Connection reset by peer Error: bsock.c:444 Read error from client:x.x.x.x:36643: ERR=Connection reset by peer The errors happened after random amounts of data, but was very repeatable for certain clients. tcpdump's of the errors showed the sd simply refusing to respond to the clients followed by an RST of the connection. Other simultaneous connections to the sd continued working without error. The clients are still running 2.x so they have not yet been upgraded. So, if anyone else is encountering similar problems, 3.0 seems to have solved it for us. A big thank you to all the developers that helped put together the 3.0 release. -- Simon Ekstrand ------------------------------------------------------------------------------ Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
