Been using Bacula for a few years now and have always been experiencing the same problems. I am using 1.38.1.
1) Tape Error
Why does a tape get the Error status when there is a database problem? So what if the database died, the tape is still good and should still be usable for the next job.
2) Failure to recognize tape
The tape is loaded in the drive, but the console is reporting that a job is waiting for a mount request instead of just proceeding to use the tape. I issue the mount command which results in a message asking me to mount the volume. Huh? Thought I just did that. I issue the unmount command which places the tape back in the loader and then I use the mtx command to load the same tape back into the drive. After verifying with mt and btape can use the tape and read the label I then issue the mount command again. Sometimes the tape is recognized, other times I have to erase the tape and start over. The tapes are also in variable mode.
I have experienced both of these problems with different versions of Bacula as well as different tape devices including LTO-2 and VXA-2 devices with autochangers. I have also tried different hardware platforms from 32-bit single CPU systems to 64-bit 8-CPU systems. As I said, I have been using this software for a few years now, but my latest implementation is running for a Fortune 500 client and they are thinking about getting rid of the system for some commercial solution :(
If anybody else has run in to these issues and done something to prevent them from occurring, then please let me know.
Thanks.
1) Tape Error
Why does a tape get the Error status when there is a database problem? So what if the database died, the tape is still good and should still be usable for the next job.
2) Failure to recognize tape
The tape is loaded in the drive, but the console is reporting that a job is waiting for a mount request instead of just proceeding to use the tape. I issue the mount command which results in a message asking me to mount the volume. Huh? Thought I just did that. I issue the unmount command which places the tape back in the loader and then I use the mtx command to load the same tape back into the drive. After verifying with mt and btape can use the tape and read the label I then issue the mount command again. Sometimes the tape is recognized, other times I have to erase the tape and start over. The tapes are also in variable mode.
I have experienced both of these problems with different versions of Bacula as well as different tape devices including LTO-2 and VXA-2 devices with autochangers. I have also tried different hardware platforms from 32-bit single CPU systems to 64-bit 8-CPU systems. As I said, I have been using this software for a few years now, but my latest implementation is running for a Fortune 500 client and they are thinking about getting rid of the system for some commercial solution :(
If anybody else has run in to these issues and done something to prevent them from occurring, then please let me know.
Thanks.
------------------------------------------------------------------------- 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
