Hi everyone,
I am using Bacula 5.0.0 on Centos 5.4 64bit.
When I issue 'status storage=XYZ', where XYZ is a storage device managed by
StorageDaemonA , what I get is information about all storage devices defined
for StorageDaemonA. Is this how it's supposed to be ?
For example, below is the
I am using Bacula 5.0.0 on Centos 5.4 64bit.
When I issue 'status storage=XYZ', where XYZ is a storage device managed by
StorageDaemonA , what I get is information about all storage devices defined
for StorageDaemonA. Is this how it's supposed to be ?
This is how it is supposed to be. I mean
Sven Hartge schrieb:
Ralf Gross wrote:
Bob Hetzel schrieb:
My suggestion is to try upgrading your server to 3.0.2. You won't need to
upgrade all your FD's. Since I went through that, the things that used to
hang bacula in my environment (at exactly the same place you describe) are
Ralf Gross wrote:
Bob Hetzel schrieb:
My suggestion is to try upgrading your server to 3.0.2. You won't need to
upgrade all your FD's. Since I went through that, the things that used to
hang bacula in my environment (at exactly the same place you describe) are
fixed.
3.0.2 is not yet
Hi,
I'm stuck at the 'status storage' output, or better at a mount command.
I started a Verify job and had to mount a volume into a drive (ULTRIUM-TD4-D3)
because the drive was umounted at that time. Nothing exciting I thought
mtx-changer scrip log:
20090820-08:42:37 Parms: /dev/Neo4100
Ralf,
My suggestion is to try upgrading your server to 3.0.2. You won't need to
upgrade all your FD's. Since I went through that, the things that used to
hang bacula in my environment (at exactly the same place you describe) are
fixed.
Bob
From: Ralf Gross ralf-li...@ralfgross.de
Hi,
Bob Hetzel schrieb:
My suggestion is to try upgrading your server to 3.0.2. You won't need to
upgrade all your FD's. Since I went through that, the things that used to
hang bacula in my environment (at exactly the same place you describe) are
fixed.
3.0.2 is not yet available in
Hello,
Linux 2.6.x
bacula 2.2.5 patched from sourceforge
I have checked the documentation, but can not find any reference to this.
It appears a status storage is showing the wrong pool. I have never had
this before.
I have just retired some old Media (purge and delete) and added some new
On 11/2/07, GDS.Marshall [EMAIL PROTECTED] wrote:
Hello,
Linux 2.6.x
bacula 2.2.5 patched from sourceforge
I have checked the documentation, but can not find any reference to this.
It appears a status storage is showing the wrong pool. I have never had
this before.
I have seen this
OK. Some progress!
I can telnet and ping OK. Everyone can ping each other via hostnames and
IPs. Now I run the console with /usr/bin/bconsole -d200 every time to
get verbose output.
I then tried changing my config files to use IP addresses instead of
FQDNs. No luck there though.
Your
OS: Ubuntu Linux 6.06
Bacula version: 1.36.3
Tape changer: Quantum Superloader 3, LTO Ultrium 3
Changer passes btape autochanger test.
status storage gives me an error:
Automatically selected Storage: LTO-3
Connecting to Storage daemon LTO-3 at lasbmms1w03.bmmad.internal:9103
Failed to connect to
Simple question...
Did you restart the SD daemon after modifying your SD file to use the
LTO device instead of the HDD?
Erich
On Mar 15, 2007, at 6:22 PM, Mike Toscano wrote:
OS: Ubuntu Linux 6.06
Bacula version: 1.36.3
Tape changer: Quantum Superloader 3, LTO Ultrium 3
Changer passes
Sure did. I restarted them all.
Thanks for the reply!
Mike
On Thu, 15 Mar 2007 20:49:53 -0500, Erich Prinz [EMAIL PROTECTED]
said:
Simple question...
Did you restart the SD daemon after modifying your SD file to use the
LTO device instead of the HDD?
Erich
On Mar 15, 2007,
[ Sorry for reposting so soon, but this is time-sensitive and it
seems to have flown under the list radar ]
We've migrated a working bacula installation and changer to a new
server, but bacula seems unable to connect to the storage unit. All
of the configuration files were moved intact,
On Fri, 15 Dec 2006 10:36:06 -0500, Jason Dixon said:
We've migrated a working bacula installation and changer to a new
server, but bacula seems unable to connect to the storage unit. All
of the configuration files were moved intact, with the exception of
changing the director name
On Fri, 15 Dec 2006, Jason Dixon wrote:
All
of the configuration files were moved intact, with the exception of
changing the director name and the scsi device.
Ownerships/permissions of the device(s) ?
I am able to see the
changer and drives via dmesg, proc and mtx, but it simply times out
On Dec 15, 2006, at 10:58 AM, [EMAIL PROTECTED] wrote:
On Fri, Dec 15, 2006 at 10:36:06AM -0500, Jason Dixon wrote:
We've migrated a working bacula installation and changer to a new
server, but bacula seems unable to connect to the storage unit. All
of the configuration files were moved
On Friday 15 December 2006 19:24, Jason Dixon wrote:
On Dec 15, 2006, at 10:58 AM, [EMAIL PROTECTED] wrote:
On Fri, Dec 15, 2006 at 10:36:06AM -0500, Jason Dixon wrote:
We've migrated a working bacula installation and changer to a new
server, but bacula seems unable to connect to the
Hi!
I've just upgraded from 1.38.0 to 1.38.5.
So far everything works fine, I was able to run a successful incremental
backup.
However, the status dir command in the bacula console doesn't show the
correct pool any more:
snipp!
*status storage
On Thu, 09 Feb 2006 13:46:42 +0100, Alexander Bergolth [EMAIL
PROTECTED] said:
Hi!
I've just upgraded from 1.38.0 to 1.38.5.
So far everything works fine, I was able to run a successful incremental
backup.
However, the status dir command in the bacula console doesn't show the
20 matches
Mail list logo
