Thanks Stephan, another question I don't know if you can answer too,
regarding on the ovirt plugin limitation "Error '%s' already have
snapshosts. This is not supported\n", do you know what rationale that
aren't support snapshot existent.
On Tuesday, May 12, 2020 at 10:36:24 PM UTC+8,
Just saw an issue:
Error updating Volume records: ERR=cats/sql_update.cc:444 Update failed:
affected_rows=0 for UPDATE Media SET
ActionOnPurge=0,Recycle=1,VolRetention=31536000,VolUseDuration=0,MaxVolJobs=0,MaxVolFiles=0,MaxVolBytes=0,RecyclePoolId=0,MinBlocksize=0,MaxBlocksize=0
WHERE
Did you try
bconsole
* relabel
?
--
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 bareos-users+unsubscr...@googlegroups.com.
To view this discussion on the web
On 06.06.20 at 15:26 wrote Kirill Iliashenko:
> Hello,
> Did you managed to solve the problem? Because i have the same one.
It seams, there is still a problem with the underlying sslpsk and Python 3.
Using Python 2.7 it works without problems. I hope, there will be a fix
for sslpsk soon.
On 09.06.20 at 14:58 wrote 'birgit.ducarroz' via bareos-users:
> Did you try
> bconsole
> * relabel
>
> ?
>
Relabel will only work on empty/purged volumes. By relabeling a tape,
data will be lost.
AFAIK it is only possible to append data to a physical tape, not
rewriting parts of it.
--
Jörg
All,
I honestly don't know what I'm doing wrong here. Every month the director
clogs up and every single client wants me to mount an append volume. Below
is a link to a google docs with my configs. IPs and passwords have been
obfuscated. I appreciate any guidance you can provide.
LS,
As far as I can see the bareos-storage-droplet package is only available for
old openSUSE versions and CentOS 7 an OS that released 6 years ago.
Are there any plans for making this plugin available for CentOS 8 or even
better Ubuntu 18.04 / 20.04?
Met vriendelijke groet / With kind
On 09.06.2020 18:16, Jörg Steffens wrote:
On 09.06.20 at 14:58 wrote 'birgit.ducarroz' via bareos-users:
Did you try
bconsole
* relabel
?
Relabel will only work on empty/purged volumes. By relabeling a tape,
data will be lost.
AFAIK it is only possible to append data to a physical tape, not
Hi there.
I'm wondering whether there is a reasonable way to prevent bareos from
scheduling jobs from same client in quick succession.
Here's what I mean. We have a bareos setup with a single tape drive. The
jobs are scheduled daily with Inc/Diff/Full schedule. If we fail to
change tape as
On 09/06/2020 11:24, Spadajspadaj wrote:
Hi there.
I'm wondering whether there is a reasonable way to prevent bareos from
scheduling jobs from same client in quick succession.
Here's what I mean. We have a bareos setup with a single tape drive. The
jobs are scheduled daily with
On 09.06.2020 11:30, Andrei Brezan wrote:
On 09/06/2020 11:24, Spadajspadaj wrote:
Hi there.
I'm wondering whether there is a reasonable way to prevent bareos
from scheduling jobs from same client in quick succession.
Here's what I mean. We have a bareos setup with a single tape drive.
11 matches
Mail list logo
