I think my issues is DriveA is not reading the labels created by DriveB. Is
there a way to test driveA further? I tried btape test and it was able to
read/write to a tape without any issue.
--
You received this message because you are subscribed to the Google Groups
"bareos-users" group.
To
I might have my own answer, partitioning, each with its own control path?
Unless something better?
On 3/26/2018 2:16 PM, David Lawley wrote:
Revisiting Bareos, been about a year. Thought I would have better luck
this time but seems I have hit the same road block.
Anyway to work around the
Hi Konax,
what about labelling a new volume manual on bconsole?
I think there should be a similar message at the log?
Regards
Stefan
Am 26.03.2018 um 10:27 schrieb garbag...@gmail.com:
> Hello
>
> I have a little question of beginner.
>
> My backups on disk were blocked (backup is waiting or
Revisiting Bareos, been about a year. Thought I would have better luck
this time but seems I have hit the same road block.
Anyway to work around the control path on the ML6000? Another card maybe.
Seems that the control path takes over and does not seem to allow me
access to the second
Arjen -
You said "After removing a client from the Director", I am assuming al you did
was remove the client configuration from the file system. To remove the data
for the client you should use console...
purge -> jobs -> . That will remove remove all of the
data from the catalog. Now the
On 26.03.2018 at 12:59 wrote Minaa:
> i configerd bareos to backup my data on S3 i did as this link
>
> https://github.com/bareos/bareos/blob/master/README.droplet
>
> but when i run the job i get this error mes after fail
>
> " 26-Mar 07:36 bareos-dir JobId 4: Warning: bsock_tcp.c:128 Could
Hi Daniel,
some of your questions have be discussed before. Please see
https://groups.google.com/forum/#!topic/bareos-users/42J_PuE6J34 and
https://groups.google.com/forum/#!topic/bareos-users/t4Ko2RIRjEc.
The issue you report is properly related to the network heartbeat.
Please refer to
I stumbled on that some changers don't update slots on operations so it's
possible that the index may be incorrect? I tried "update slots scan" but chose
drive 1 and now it looks like all of the tapes do not have labels::
Volume "" wanted on "DRV1A" (/dev/st1) is in use by device "DRV1B"
I have a backup job that is backing up S3 objects to tape and I am trying to
backup a 10TB bucket to a set of tapes. I have all of my tapes labeled and
assigned to a Tapes pool. After some time the tape fills up and it looks like
bareos is trying to span the job to another tap but it seems that
Turns out my t50e had an issue and the controller was replaced. It now seems to
be loading and unloading properly. I have another issue now but i'm going to
make a separate thread about that.
--
You received this message because you are subscribed to the Google Groups
"bareos-users" group.
Hello,
I have been using bareos for backups in the company for some time. Currently,
the backups are triggered at night. Since some colleagues turn off their
computers at night, I use the following settings:
MaxFullInterval = 1 months
MaxDiffInterval = 1 weeks
Reschedule On Error = yes
Hi List,
using BareOS 16.2.4 on CentOS 7.
After removing a client from the Director, it still shows up every now
and then in certain bconsole queries, for instance "list jobs last"
shows jobs from clients that were removed in 2016. The executable
bareos-dbcheck doesn't seem to help here.
btw 46.101.9.86 is the server that has data on it need to be backup
--
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.
i configerd bareos to backup my data on S3 i did as this link
https://github.com/bareos/bareos/blob/master/README.droplet
but when i run the job i get this error mes after fail
" 26-Mar 07:36 bareos-dir JobId 4: Warning: bsock_tcp.c:128 Could not connect
to Storage daemon on
Hello
I have a little question of beginner.
My backups on disk were blocked (backup is waiting or status is "Running" )
because the storage space was full. OK it's normal.
I freed some space for my "backups to resume.
But after freeing up disk space, all my backups were always blocked with
W dniu piątek, 23 marca 2018 17:25:36 UTC+1 użytkownik Jörg Steffens napisał:
> On 23.03.2018 at 09:06 wrote Mateusz Ostrzyżek:
> > Hi,
> >
> > I have a question,
> >
> > Is there any possibility to make backups monthly and by that i mean 30 days
> > from previous backups.
> >
> > I know there
16 matches
Mail list logo