I finally think that everything is after all ok.
The initial table I sent:
Level Type Pri Name Volume
=
IncrementalBackup10 vm25-linux Full-0031
IncrementalBackup10
On 12.05.2020 11:34, 'DUCARROZ Birgit' via bareos-users wrote:
2) I thought that incremental level is writing into
incremental-Volume, full level is writing into full-Volume etc. But it
is not. Why?
Depends how your job is configured.
You might just use Pool directive to specify a pool
Gonna guess here, but I think you need to use the name of the
database, rather than a filename?
Another thing is the database in "full" recovery mode?
Ah I see the database name "test", so I would check recovery mode
On 5/8/2020 5:41 AM, Mixer Pack
LS,
I’m running Bareos 19.2.7 on Ubuntu 18.04 with the Rados Storage Backend
My device configuration looks like this:
Device {
Name = RadosDevice
Archive Device = "Rados Device"
Device Options =
I still don't understand why it's not working correctly :-/
Should I change in jobdefs/vm25-linux.conf
Level = Full into Level = Incremental
And also Pool = Full into Pool = Incremental
?
JobDefs {
Name = "vm25-linux"
Type = Backup
Level = Full
Client = vm25-linux
FileSet =
I'm a bit confused about what follows.
1) I wonder why in the GUI sometimes I am able to see under "Storages"
my volumes and sometimes not which is actually the case (see
print-screen). I would like to see the infos of my volumes, but actually
no chance via the GUI.
2) I thought that
Hello,
Since friday my bareos stopped sending emails (it sends reporting that it
wasn't send).
By troubleshooting I noticed the sender address is a bit awkward -
bar...@srvtsprdbos.domain.com
I havent done anything in bareos in last week that could do this error or
something like that
I've create the PR https://github.com/bareos/bareos/pull/516 which will fix
this issue.
Regarding MySQL: Changing the PluginName column to longblob should be no
problem, as for PostgreSQL this column is TEXT,
so I don't expect any length problem. Please also consider migration to
PostgreSQL,
