Hi Christoph
how did you "increase the number of volumes in the Pool definition" ?
Did you just edit the pool configuration file and do a reload ?
Or did you use the `add` command to add new volumes directly ?
https://docs.bareos.org/TasksAndConcepts/BareosConsole.html#console-commands
>>> This command is used to add Volumes to an existing Pool. That is,
it creates the Volume name in the catalog and inserts into the Pool in
the catalog, but does not attempt to access the physical Volume. Once
added, Bareos expects that Volume to exist and to be labeled.
Are you sure that the message was printed _after_ you added new volumes
to the pool ? Maybe this message was printed first and you only added
new volumes afterwards ?
Could you provide the full job log ?
Kind Regards
Sebastian Sura
Am 18.12.24 um 11:42 schrieb Christoph Haas:
While running a backup I realized that the pool had too few volumes
(on disk). So I increased the number of volumes in the Pool
definition, went to the bconsole and reloaded.
However that instantly lead to this error:
18-Dec 11:37 bareos-sd JobId 3605: Warning: stored/mount.cc:246 Open
device "DiskVmwareStorage9" (/srv/stor2/bareos/vmware) Volume
"VmwareIncr-2346" failed: ERR=stored/dev.cc:597 Could not open:
/srv/stor2/bareos/vmware/VmwareIncr-2346, ERR=No such file or directory
There is indeed no such file. The most recent files are:
-rw-r----- 1 bareos bareos 10736369887 Dez 18 03:21 VmwareIncr-2339
-rw-r----- 1 bareos bareos 10736369871 Dez 18 03:21 VmwareIncr-2331
-rw-r----- 1 bareos bareos 10736369879 Dez 18 03:21 VmwareIncr-2338
-rw-r----- 1 bareos bareos 10736369887 Dez 18 03:22 VmwareIncr-2337
-rw-r----- 1 bareos bareos 10736369887 Dez 18 03:23 VmwareIncr-2341
-rw-r----- 1 bareos bareos 10736369887 Dez 18 03:23 VmwareIncr-2340
-rw-r----- 1 bareos bareos 10736369887 Dez 18 03:24 VmwareIncr-2343
-rw-r----- 1 bareos bareos 10736369887 Dez 18 03:27 VmwareIncr-2342
My Pool definition:
Pool {
Name = VmwareIncr
Pool Type = Backup
Recycle = yes # Bareos can automatically
recycle Volumes
AutoPrune = yes # Prune expired volumes
Volume Retention = 10 days # How long should the
Incremental Backups be kept?
Maximum Volume Bytes = 10G # Limit Volume size to
something reasonable
Maximum Volumes = 400 # Limit number of Volumes in Pool
Label Format = "VmwareIncr-" # Volumes will be labeled
"Incremental-<volume-id>"
Recycle Oldest Volume = yes
}
The only way I can solve that is cancelling all active jobs (cancel
all yes) and restarting them.
I'm on Bareos 23.1.1 on Debian 12. Has anyone else seen this? What am
I doing wrong?
Cheers
Christoph
--
You received this message because you are subscribed to the Google
Groups "bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/bareos-users/aa0dcfd4-a51e-4019-b1a5-1f8b48dd137an%40googlegroups.com
<https://groups.google.com/d/msgid/bareos-users/aa0dcfd4-a51e-4019-b1a5-1f8b48dd137an%40googlegroups.com?utm_medium=email&utm_source=footer>.
--
Sebastian [email protected]
Bareos GmbH & Co. KG Phone: +49 221 630693-0
https://www.bareos.com
Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
Komplementär: Bareos Verwaltungs-GmbH
Geschäftsführer: Stephan Dühr, Jörg Steffens, Philipp Storz
--
You received this message because you are subscribed to the Google Groups
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/bareos-users/80908c31-8013-4973-9258-a89bc76e149d%40bareos.com.
