[bareos-users] SAS tape library multi-host best practices

2023-06-01 Thread Kai Zimmer 

Hi,

i have an Overland/Tandberg NeoXL 40 tape library with a tape slot 
extension (40+40 slots) and two LTO-8 SAS drives attached to a bareos 
server. I think about attaching an existing second bareos server to it 
so that each server is connected to a single SAS drive. I know that the 
library supports partitioning of tape slots. Both servers would then 
have independent tape pools.


Do you think such a configuration is possible? Will bareos support it? 
Or would you prefer a different configuration?


Thanks in advance!

Best regards,
Kai

--
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 visit 
https://groups.google.com/d/msgid/bareos-users/c925f360-0ceb-a99b-bcec-3f56c8a16f13%40bbaw.de.

Re: [bareos-users] Any OS recommendations for Bareos server with NEOxl 40 tape storage?

2023-04-20 Thread Kai Zimmer 

Hi,

On 20.04.23 13:28, Evert Meulie wrote:
I know that many people have their own personal favorites when it 
comes to Linux flavours, but what would be considered the ultimate OS 
to host a BareOS server which needs to interact with a NEOxl 40 tape 
library?

Are there any flavours better than others? 邏


i also run a NEOxl 40 under Ubuntu Linux 20.4 LTS (focal), connected via 
SAS. I prefer Ubuntu because it supports newer hardware out of the box - 
but generally any other distro listed under 
http://download.bareos.org/current/ will do.


Best regards,

Kai

--
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 visit 
https://groups.google.com/d/msgid/bareos-users/7961b000-e50e-5dd5-f6fc-19bf5e89c6a5%40bbaw.de.

[bareos-users] endless archiving loop without fixed time schedule?

2023-03-17 Thread Kai Zimmer 

Hi,

i wonder if it is possible to define a schedule strategy in Bareos as an 
endless loop of jobs rather than executing jobs at a fixed time schedule?


I'd like to have a "full/incremental forever" forever archiving loop:

- doing a full backup/archiving of all clients first
- doing an incremental backup/archiving of all clients afterwards
- start over again

I think about having a tape pool with no recycling, no auto pruning and 
a retention period of 100 years, so the data is never overwritten by 
Bareos. Tape capacity and database growth are no problem.


Is such a endless loop without fixed time schedules possible (just 
running each job after the other)? If so, what would such a scheduler 
definition look like?


Any hints would be greatly appreciated.

Best regards,
Kai Zimmer



--
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 visit 
https://groups.google.com/d/msgid/bareos-users/fdf88621-fb33-2661-57be-47b6e5719f13%40bbaw.de.

Re: [bareos-users] Run Job not executed on Client

2022-06-10 Thread Kai Zimmer 
Thanks for the hint. That's what i tried in the first place, but without 
luck - my job just returned "Errors=1". So i tried to simplify.
So far i cannot tell whether i'm successful or not, it will take a while 
to test.


On 10.06.22 15:16, Spadajspadaj wrote:
If you want a dynamic list of files, why don't you use the dynamic 
list functionality? :-)


https://docs.bareos.org/Configuration/Director.html#id11


On 10.06.2022 12:34, Kai Zimmer wrote:

Hi again,

so my idea was to generate a file list to backup before the job 
starts to run. Bareos stopped the job because the file list didn't 
exist yet when the job was started. I probably interpreted 
"ClientRunBeforeJob" wrong or so.


Best regards,
Kai

On 10.06.22 11:30, Kai Zimmer wrote:

Hi,

i'm stuck trying to get a "run job" executed on a bareos client. I 
tried "Run Script", "ClientRunBeforeJob" and "Client Run Before Job" 
with the same result - no execution.

Bareos-dir (server) version 19.2.7-2 on Debian Bullseye
Bareos-fd (client) version 19.2.7.-2 on Ubuntu 20.04.1
The logfile (setdebug level=100 enabled) doesn't even mention 
"runscript".


The job definition looks like this:
Job {
  Name = "KiraDstarSources"
  JobDefs = "KiraDstarSourcesJob"
  Client = "kira-fd"
  Run Script {
 Command = "bash -c 'touch /tmp/bareos_dstar_sources.tmp'"
 Runs On Client = Yes
 Runs When = Before
  }
}

When i switch "Runs On Client" to "No" (so it runs on the 
serverside), the job is properly executed:

locutus-dir (50): dird/jobq.cc:907-0 Inc Job=KiraDstarSources rncj=1
locutus-dir (100): cats/sql_query.cc:131-437 called: bool 
BareosDb::SqlQuery(const char*, int) with query UPDATE Job SET 
JobStatus='R',Level='F',StartTime='2022-06-10 
11:02:01',ClientId=31,JobTDate=1654851721,PoolId=5,FileSetId=71 
WHERE JobId=437
locutus-dir (100): lib/runscript.cc:228-437 runscript: running a 
RunScript object type=124
locutus-dir (100): lib/runscript.cc:236-437 runscript: running 'bash 
-c 'touch /tmp/bareos_dstar_sources.tmp''...
locutus-dir (100): cats/sql_query.cc:131-437 called: bool 
BareosDb::SqlQuery(const char*, int) with query INSERT INTO Log 
(JobId, Time, LogText) VALUES (437,'2022-06-10 
11:02:01','locutus-dir JobId 437: shell command: run BeforeJob "bash 
-c ''touch /tmp/bareos_dstar_sources.tmp''"

')
locutus-dir (100): lib/runscript.cc:267-437 runscript OK

Any hints what might be the problem?

Best regards,
Kai







--
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 visit 
https://groups.google.com/d/msgid/bareos-users/edebbdfc-c021-9a66-0233-17fb93024f8b%40bbaw.de.

Re: [bareos-users] Run Job not executed on Client

2022-06-10 Thread Kai Zimmer 

Hi again,

so my idea was to generate a file list to backup before the job starts 
to run. Bareos stopped the job because the file list didn't exist yet 
when the job was started. I probably interpreted "ClientRunBeforeJob" 
wrong or so.


Best regards,
Kai

On 10.06.22 11:30, Kai Zimmer wrote:

Hi,

i'm stuck trying to get a "run job" executed on a bareos client. I 
tried "Run Script", "ClientRunBeforeJob" and "Client Run Before Job" 
with the same result - no execution.

Bareos-dir (server) version 19.2.7-2 on Debian Bullseye
Bareos-fd (client) version 19.2.7.-2 on Ubuntu 20.04.1
The logfile (setdebug level=100 enabled) doesn't even mention 
"runscript".


The job definition looks like this:
Job {
  Name = "KiraDstarSources"
  JobDefs = "KiraDstarSourcesJob"
  Client = "kira-fd"
  Run Script {
 Command = "bash -c 'touch /tmp/bareos_dstar_sources.tmp'"
 Runs On Client = Yes
 Runs When = Before
  }
}

When i switch "Runs On Client" to "No" (so it runs on the serverside), 
the job is properly executed:

locutus-dir (50): dird/jobq.cc:907-0 Inc Job=KiraDstarSources rncj=1
locutus-dir (100): cats/sql_query.cc:131-437 called: bool 
BareosDb::SqlQuery(const char*, int) with query UPDATE Job SET 
JobStatus='R',Level='F',StartTime='2022-06-10 
11:02:01',ClientId=31,JobTDate=1654851721,PoolId=5,FileSetId=71 WHERE 
JobId=437
locutus-dir (100): lib/runscript.cc:228-437 runscript: running a 
RunScript object type=124
locutus-dir (100): lib/runscript.cc:236-437 runscript: running 'bash 
-c 'touch /tmp/bareos_dstar_sources.tmp''...
locutus-dir (100): cats/sql_query.cc:131-437 called: bool 
BareosDb::SqlQuery(const char*, int) with query INSERT INTO Log 
(JobId, Time, LogText) VALUES (437,'2022-06-10 11:02:01','locutus-dir 
JobId 437: shell command: run BeforeJob "bash -c ''touch 
/tmp/bareos_dstar_sources.tmp''"

')
locutus-dir (100): lib/runscript.cc:267-437 runscript OK

Any hints what might be the problem?

Best regards,
Kai



--
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 visit 
https://groups.google.com/d/msgid/bareos-users/958dd4f6-7c58-7e7f-fb5e-0e9d2bc1febe%40bbaw.de.

[bareos-users] Run Job not executed on Client

2022-06-10 Thread Kai Zimmer 

Hi,

i'm stuck trying to get a "run job" executed on a bareos client. I tried 
"Run Script", "ClientRunBeforeJob" and "Client Run Before Job" with the 
same result - no execution.

Bareos-dir (server) version 19.2.7-2 on Debian Bullseye
Bareos-fd (client) version 19.2.7.-2 on Ubuntu 20.04.1
The logfile (setdebug level=100 enabled) doesn't even mention "runscript".

The job definition looks like this:
Job {
  Name = "KiraDstarSources"
  JobDefs = "KiraDstarSourcesJob"
  Client = "kira-fd"
  Run Script {
 Command = "bash -c 'touch /tmp/bareos_dstar_sources.tmp'"
 Runs On Client = Yes
 Runs When = Before
  }
}

When i switch "Runs On Client" to "No" (so it runs on the serverside), 
the job is properly executed:

locutus-dir (50): dird/jobq.cc:907-0 Inc Job=KiraDstarSources rncj=1
locutus-dir (100): cats/sql_query.cc:131-437 called: bool 
BareosDb::SqlQuery(const char*, int) with query UPDATE Job SET 
JobStatus='R',Level='F',StartTime='2022-06-10 
11:02:01',ClientId=31,JobTDate=1654851721,PoolId=5,FileSetId=71 WHERE 
JobId=437
locutus-dir (100): lib/runscript.cc:228-437 runscript: running a 
RunScript object type=124
locutus-dir (100): lib/runscript.cc:236-437 runscript: running 'bash -c 
'touch /tmp/bareos_dstar_sources.tmp''...
locutus-dir (100): cats/sql_query.cc:131-437 called: bool 
BareosDb::SqlQuery(const char*, int) with query INSERT INTO Log (JobId, 
Time, LogText) VALUES (437,'2022-06-10 11:02:01','locutus-dir JobId 437: 
shell command: run BeforeJob "bash -c ''touch 
/tmp/bareos_dstar_sources.tmp''"

')
locutus-dir (100): lib/runscript.cc:267-437 runscript OK

Any hints what might be the problem?

Best regards,
Kai

--
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 visit 
https://groups.google.com/d/msgid/bareos-users/6caf0007-d701-8c48-99d1-06d76570622d%40bbaw.de.

Re: [bareos-users] Client-operated backup

2022-02-17 Thread Kai Zimmer 

Hi,

yes, you can have restricted accounts in bareos-webui. Last time i tried 
this i got stuck because at that time bareos-webui didn't support 
multiple catalogs (which would have been the most obvious way to 
implement restriction). But this issue has been addressed, see

https://docs.bareos.org/IntroductionAndTutorial/InstallingBareosWebui.html
"Can access multiple directors and catalogs"

Best,
Kai

On 14.02.22 11:34, Spadajspadaj wrote:

Hello there.

I'm wondering if there is any less-intrusive option for backing up 
"interminnently connected" hosts (like my wife's laptop :-)).


At first I had a static schedule which would backup the client every 
day at 9am or so.


That of course would make backups skipped if the laptop was not on at 
that precise time so I had to monitor that externally and sometimes 
spawn backup jobs manually. That was annoying.


Then I found the "Run On Incoming Connect Interval" option which made 
my life much easier. Now if the "normal" backup job is skipped, the 
backup gets spawned as soon as my wife boots up the laptop. That makes 
it relatively well covered in terms of backup.


But it also makes the laptop unuseable (especialy in terms of 
videoconference solutions or other low-latency uses) for the first 
half hour or so after each bootup.


So the question is - is there any reasonable way to make the backups 
more client-controlled? So the backup job is not spawn immediately 
after the connection from fd to dir, but can be delayed by user or 
spawned directly by user when desired?


I probably could set up the bareos webui but could I limit my wife's 
permissions to just that single client? It would still not be a very 
elegant solution (the necessity to log in to "external" service is not 
very user-friendly) but it would be something.


Any other paths to explore?

I'm at 20.0.1 at the moment.



--
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 visit 
https://groups.google.com/d/msgid/bareos-users/baa3b114-4c58-fd0a-7d77-92e8ebb3a23a%40bbaw.de.

[bareos-users] Sizing 'Maximum Concurrent Jobs' parameter

2022-02-04 Thread Kai Zimmer 

Hi,

how do i correctly estimate the 'Maximum Concurrent Jobs' parameter?

Currently i use the following values, but i might probably use higher 
values?


bareos-dir.conf:  Maximum Concurrent Jobs = 4

bareos-fd.conf:  Maximum Concurrent Jobs = 20
bareos-sd.conf:  Maximum Concurrent Jobs = 20

I use data spooling for an LTO8 drive:

  Maximum File Size = 32G
  Maximum Spool Size = 10 # 10TB-enough to despool at least 
10 min to tape (216GB at 360MBps)

  Maximum Job Spool Size = 1 # 1TB

Best regards,
Kai



--
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 visit 
https://groups.google.com/d/msgid/bareos-users/1c925a21-a79b-f1d7-f820-651b9023a8ff%40bbaw.de.

Re: [bareos-users] I changed the database from MariaDB to PostgreSQL "Now the backups no longer work"

2021-11-05 Thread Kai Zimmer 

Hi Stefan,

instead of changing the backend i'd rather
- add another catalog in the bareos-dir configuration or
- convert the current database to postgres, and change the catalog 
configuration, there are scripts available from bareos for that (but can 
be quite time consuming)


Best regards,
Kai Zimmer


On 05.11.21 07:09, shar...@t-online.de wrote:

Hi there,
after changing the database backend from MariaDB to PostgreSQL, all 
backups fail with the following error message:

...
backupadmin
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit

05-Nov 03:45 bareos-dir JobId 0: Fatal error: cats/sql_create.cc:536 
cats/sql_create.cc:536 query SELECT ClientId,Uname FROM Client WHERE 
Name='bareos-fd' failed:

keine Verbindung mit dem Server

05-Nov 03:47 bareos-dir JobId 0: Error: cats/sql_create.cc:578 Create 
DB Client record INSERT INTO Client 
(Name,Uname,AutoPrune,FileRetention,JobRetention) VALUES 
('bareos-fd','',0,5184000,15552000) failed. ERR=keine Verbindung mit 
dem Server


05-Nov 03:48 bareos-dir JobId 0: Fatal error: Could not create Client 
record. ERR=Query failed: INSERT INTO Log (JobId, Time, LogText) 
VALUES (0,'2021-11-05 03:47:30','bareos-dir JobId 0: Error: 
cats/sql_create.cc:578 Create DB Client record INSERT INTO Client 
(Name,Uname,AutoPrune,FileRetention,JobRetention) VALUES 
(''bareos-fd'',,0,5184000,15552000) failed. ERR=keine Verbindung 
mit dem Server


'): ERR=keine Verbindung mit dem Server
...
Do you have a tip where I can look for the error?
Greetings from Stefan Harbich
--
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 
<mailto:bareos-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bareos-users/0e88fb24-b110-48ae-9468-ed927abea0b6n%40googlegroups.com 
<https://groups.google.com/d/msgid/bareos-users/0e88fb24-b110-48ae-9468-ed927abea0b6n%40googlegroups.com?utm_medium=email_source=footer>.



--
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 visit 
https://groups.google.com/d/msgid/bareos-users/4dcb76c3-e7c4-4b28-f2db-745823d50eae%40bbaw.de.

[bareos-users] mysqldump 128 GB limit ?

2020-06-11 Thread Kai Zimmer 

Hi,

in former times i used bareos with a mysql database backend. However it 
became too slow and i switched to a secondary postgres catalogue. I need 
to keep the mysql database as a history though.


Now i'm switching from Ubuntu 16.04 (mysql 5.7) to Ubuntu 20.04 (mysql 
8.0) and i'm unable to start the mysqld server because of incompatible 
data structures. I tried dumping the database on another Ubuntu 16.04 
machine, but the SQL-dump file is only about 128 gb in size, although 
the binary index files are > 200 GB in size.


Is there a known limit in mysqldump? I'm using ext4 file system which is 
capable of 16 Tb single file sizes.


Best,

Kai

--
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 visit 
https://groups.google.com/d/msgid/bareos-users/e4d46350-1e6c-859f-0830-421192ee1f3f%40bbaw.de.

[bareos-users] pause a job

2020-04-03 Thread Kai Zimmer 

Hi,

is it possible to pause a job to resume it later from the point where it 
left off?


E.g. a running job tells me it needs more tapes and waits for them. I 
exchange a bunch of tapes in my library and after i labeled the first of 
them, bareos immediately starts again so i can't label the rest of the 
tapes now. It would be nice if i could run a pause command, label all 
new tapes and resume the job again.


Best regards,

Kai

--
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 visit 
https://groups.google.com/d/msgid/bareos-users/fba500a3-4c60-c56d-e28a-3f67e7c087bd%40bbaw.de.

Re: [bareos-users] Fatal database error on restore with 18.2.

2020-03-13 Thread Kai Zimmer 

Hi,

i had the same problem and was able to fix it by upgrading to 19.2.6. 
There is also a bug ticket for bconsole crashes in 18.2.


Best regards,
Kai

On 12.03.2020 22:12, Marcus Wagner wrote:

Hello,

has someone an idea what causes this fatal database error? Any hint 
would be appreciated.


Thank you,
Marcus Wagner

-- Originalnachricht --
Von: "Marcus Wagner" >

An: bareos-users@googlegroups.com 
Gesendet: 28.02.2020 10:46:42
Betreff: [bareos-users] Fatal database error on restore with 18.2.

Hello Bareos Team,

I have a problem with a 18.2 director. When I start a bconsole, type 
"restore" and any other option like "9", the bconsole crashes and ends 
without any error message.


When I start the director in foreground and with debug 400, I get the 
following output:



mq-bareos01 (100): lib/bsock.cc:81-0 Construct BareosSocket
mq-bareos01 (100): include/jcr.h:320-0 Construct JobControlRecord
mq-bareos01 (100): lib/tls_openssl_private.cc:57-0 Construct 
TlsOpenSslPrivate
mq-bareos01 (100): lib/tls_openssl_private.cc:536-0 Set tcp 
filedescriptor: <6>

mq-bareos01 (100): lib/tls_openssl_private.cc:482-0 Set ca_certfile:    <>
mq-bareos01 (100): lib/tls_openssl_private.cc:488-0 Set ca_certdir:     <>
mq-bareos01 (100): lib/tls_openssl_private.cc:494-0 Set crlfile_:       <>
mq-bareos01 (100): lib/tls_openssl_private.cc:500-0 Set certfile_:      <>
mq-bareos01 (100): lib/tls_openssl_private.cc:506-0 Set keyfile_:       <>
mq-bareos01 (100): lib/tls_openssl_private.cc:518-0 Set pem_userdata 
to address: <0>

mq-bareos01 (100): lib/tls_openssl_private.cc:524-0 Set dhfile_:        <>
mq-bareos01 (100): lib/tls_openssl_private.cc:542-0 Set cipherlist:     <>
mq-bareos01 (100): lib/tls_openssl_private.cc:530-0 Set Verify Peer:  
  
mq-bareos01 (50): lib/tls_openssl.cc:100-0 Preparing TLS_PSK SERVER 
callback
mq-bareos01 (100): lib/tls_openssl_private.cc:401-0 psk_server_cb. 
identitiy: R_CONSOLE *UserAgent*.
mq-bareos01 (100): lib/tls_openssl_private.cc:426-0 psk_server_cb. 
result: 32.

mq-bareos01 (50): lib/bnet.cc:150-0 TLS server negotiation established.
mq-bareos01 (110): dird/socket_server.cc:109-0 Conn: Hello *UserAgent* 
calling version 18.2.5

mq-bareos01 (100): include/jcr.h:320-0 Construct JobControlRecord
mq-bareos01 (100): dird/storage.cc:157-0 write_storage_list=mq-bareos01
mq-bareos01 (100): dird/storage.cc:166-0 write_storage=mq-bareos01 
where=Job resource
mq-bareos01 (100): dird/job.cc:1519-0 JobId=0 created 
Job=-Console-.2020-02-28_10.45.52_03
mq-bareos01 (50): lib/cram_md5.cc:69-0 send: auth cram-md5 
<382897422.1582883152@mq-bareos01> ssl=1
mq-bareos01 (100): lib/cram_md5.cc:116-0 cram-get received: auth 
cram-md5 <710744962.1582883152@bconsole> ssl=1
mq-bareos01 (99): lib/cram_md5.cc:135-0 sending resp to challenge: 
pT5rHH+hw9+rG4k765/oyB
mq-bareos01 (10): dird/ua_audit.cc:146-0 : Console [default] from 
[127.0.0.1] cmdline restore

mq-bareos01 (100): dird/ua_db.cc:155-0 UA Open database
mq-bareos01 (100): cats/sql_pooling.cc:61-0 
DbSqlGetNonPooledConnection allocating 1 new non pooled database 
connection to database bareos, backend type postgresql
mq-bareos01 (100): cats/cats_backends.cc:81-0 db_init_database: Trying 
to find mapping of given interfacename postgresql to mapping 
interfacename dbi, partly_compare = true
mq-bareos01 (100): cats/cats_backends.cc:81-0 db_init_database: Trying 
to find mapping of given interfacename postgresql to mapping 
interfacename mysql, partly_compare = false
mq-bareos01 (100): cats/cats_backends.cc:81-0 db_init_database: Trying 
to find mapping of given interfacename postgresql to mapping 
interfacename postgresql, partly_compare = false

mq-bareos01 (100): cats/postgresql.cc:1255-0 db_init_database first time
mq-bareos01 (50): cats/postgresql.cc:247-0 pg_real_connect done
mq-bareos01 (50): cats/postgresql.cc:249-0 db_user=bareos 
db_name=bareos db_password=EpfEYTG5k3bS

mq-bareos01 (150): dird/ua_db.cc:188-0 DB bareos opened
mq-bareos01 (100): cats/sql_query.cc:96-0 called: void 
BareosDb::FillQueryVaList(PoolMem&, BareosDbQueryEnum::SQL_QUERY_ENUM, 
__va_list_tag*) with query name uar_del_temp (17)
mq-bareos01 (100): cats/sql_query.cc:102-0 called: void 
BareosDb::FillQueryVaList(PoolMem&, BareosDbQueryEnum::SQL_QUERY_ENUM, 
__va_list_tag*) query is now DROP TABLE temp
mq-bareos01 (100): cats/sql_query.cc:124-0 called: bool 
BareosDb::SqlQuery(const char*, int) with query DROP TABLE temp
mq-bareos01 (50): cats/postgresql.cc:687-0 Result status fatal: DROP 
TABLE temp
mq-bareos01 (10): cats/postgresql.cc:692-0 ERROR TERMINATION: Fatal 
database error

mq-bareos01: ERROR TERMINATION at cats/postgresql.cc:692
Fatal database error





I've had a look at the postgres database, there is no table "temp".


Can you give me a hint?


Thank you,
Marcus Wagner

--
You received this message because you are subscribed to the Google 
Groups "bareos-users" group.
To unsubscribe

Re: [bareos-users] Fatal database error on restore with 18.2.

2020-02-28 Thread Kai Zimmer 

Me too :-(

On 28.02.2020 10:46, Marcus Wagner wrote:
I have a problem with a 18.2 director. When I start a bconsole, type 
"restore" and any other option like "9", the bconsole crashes and ends 
without any error message.


--
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 visit 
https://groups.google.com/d/msgid/bareos-users/dfabe695-796f-d802-a0e8-368e11f4fcbe%40bbaw.de.

Re: [bareos-users] bconsole CRASH without error messages (bareos 18.2.5)

2020-01-13 Thread Kai Zimmer 

Hi again,

sorry for the wrong terminology. In fact bconsole doesn't 'exit', but it 
crashes. Any way to get more information about that?


Best,
Kai

On 07.01.2020 10:25, Kai Zimmer wrote:

Hi,

after upgrading bareos from 15.2.2.-37.1 to 18.2.5-147.2 (including 
postgres database) i'm doing some tests:


- restore of (old) backup data works successfully from bconsole

- doing new backups works successfully from bconsole

- when restoring new backups  with bconsole, bconsole exits without 
error message, after


"Building directory tree for JobId(s) 10,51,65,74 ..."

I tried 'setdebug level=200 trace=1 all' in bconsole, according to the 
trace file it looks like bareos found all relevant backup files in the 
index (took some hours), but also there i don't find any hint why 
bconsole exits:


...

kira-dir (150): dird/ua_tree.cc:229-0 Path=/home/ FI=258333 JobId=74
kira-dir (150): dird/ua_tree.cc:248-0 node=0x7f533d494050 JobId=74 
FileIndex=258333 Delta=0 node.delta=-1 LinkFI=0, fhinfo=0, fhnode=0

kira-dir (200): dird/scheduler.cc:331-0 enter find_runs()
kira-dir (200): dird/scheduler.cc:347-0 now = 5e14425c: h=9 m=0 md=6 
wd=2 wom=0 woy=2 yday=6
kira-dir (200): dird/scheduler.cc:367-0 nh = 5e14506c: h=10 m=0 md=6 
wd=2 wom=0 woy=2 yday=6

kira-dir (200): dird/scheduler.cc:450-0 Leave find_runs()
kira-dir (200): dird/scheduler.cc:331-0 enter find_runs()
kira-dir (200): dird/scheduler.cc:347-0 now = 5e144298: h=9 m=0 md=6 
wd=2 wom=0 woy=2 yday=6
kira-dir (200): dird/scheduler.cc:367-0 nh = 5e1450a8: h=10 m=0 md=6 
wd=2 wom=0 woy=2 yday=6

kira-dir (200): dird/scheduler.cc:450-0 Leave find_runs()
kira-dir (200): dird/stats.cc:149-0 statistics_thread: Doing work at 
1578386073
kira-dir (200): dird/stats.cc:153-0 statistics_thread: do nothing as 
no jobs are running

Pool   Maxsize  Maxused  Inuse
NoPool  256    2  0
NAME   9910   23 19
FNAME  3328  170    169
MSG   19818   82 80
EMSG   2299   22 18
BareosSocket  9910   10  9
RECORD  128    0  0

kira-dir (100): cats/sql_query.cc:140-0 called: bool 
BareosDb::SqlQuery(const char*, int (*)(void*, int, char**), void*) 
with query SELECT SUM(PurgedFiles) FROM Job WHERE JobId IN (10,51,65,74)

kira-dir (200): dird/scheduler.cc:331-0 enter find_runs()
kira-dir (200): dird/scheduler.cc:347-0 now = 5e1442d4: h=9 m=0 md=6 
wd=2 wom=0 woy=2 yday=6
kira-dir (200): dird/scheduler.cc:367-0 nh = 5e1450e4: h=10 m=0 md=6 
wd=2 wom=0 woy=2 yday=6

kira-dir (200): dird/scheduler.cc:450-0 Leave find_runs()

Any hints? What else could i check?

Best,

Kai



--
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 visit 
https://groups.google.com/d/msgid/bareos-users/d871d225-408d-bddc-8e39-c49c3f53b07d%40bbaw.de.

Re: [bareos-users] Re: use postgresql not mysql

2020-01-13 Thread Kai Zimmer 

On 10.01.2020 17:49, Andy Bird wrote:

is it possible to swith?
The easiest way is probably to add a second Catalog with the postgresql 
driver. After that you will be asked to choose the Catalog in bconsole.


Kai

--
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 visit 
https://groups.google.com/d/msgid/bareos-users/fa4f68f3-5c18-9299-7fc6-23c81b2545ba%40bbaw.de.

[bareos-users] bconsole exits without error messages (bareos 18.2.5)

2020-01-07 Thread Kai Zimmer 

Hi,

after upgrading bareos from 15.2.2.-37.1 to 18.2.5-147.2 (including 
postgres database) i'm doing some tests:


- restore of (old) backup data works successfully from bconsole

- doing new backups works successfully from bconsole

- when restoring new backups  with bconsole, bconsole exits without 
error message, after


"Building directory tree for JobId(s) 10,51,65,74 ..."

I tried 'setdebug level=200 trace=1 all' in bconsole, according to the 
trace file it looks like bareos found all relevant backup files in the 
index (took some hours), but also there i don't find any hint why 
bconsole exits:


...

kira-dir (150): dird/ua_tree.cc:229-0 Path=/home/ FI=258333 JobId=74
kira-dir (150): dird/ua_tree.cc:248-0 node=0x7f533d494050 JobId=74 
FileIndex=258333 Delta=0 node.delta=-1 LinkFI=0, fhinfo=0, fhnode=0

kira-dir (200): dird/scheduler.cc:331-0 enter find_runs()
kira-dir (200): dird/scheduler.cc:347-0 now = 5e14425c: h=9 m=0 md=6 
wd=2 wom=0 woy=2 yday=6
kira-dir (200): dird/scheduler.cc:367-0 nh = 5e14506c: h=10 m=0 md=6 
wd=2 wom=0 woy=2 yday=6

kira-dir (200): dird/scheduler.cc:450-0 Leave find_runs()
kira-dir (200): dird/scheduler.cc:331-0 enter find_runs()
kira-dir (200): dird/scheduler.cc:347-0 now = 5e144298: h=9 m=0 md=6 
wd=2 wom=0 woy=2 yday=6
kira-dir (200): dird/scheduler.cc:367-0 nh = 5e1450a8: h=10 m=0 md=6 
wd=2 wom=0 woy=2 yday=6

kira-dir (200): dird/scheduler.cc:450-0 Leave find_runs()
kira-dir (200): dird/stats.cc:149-0 statistics_thread: Doing work at 
1578386073
kira-dir (200): dird/stats.cc:153-0 statistics_thread: do nothing as no 
jobs are running

Pool   Maxsize  Maxused  Inuse
NoPool  256    2  0
NAME   9910   23 19
FNAME  3328  170    169
MSG   19818   82 80
EMSG   2299   22 18
BareosSocket  9910   10  9
RECORD  128    0  0

kira-dir (100): cats/sql_query.cc:140-0 called: bool 
BareosDb::SqlQuery(const char*, int (*)(void*, int, char**), void*) with 
query SELECT SUM(PurgedFiles) FROM Job WHERE JobId IN (10,51,65,74)

kira-dir (200): dird/scheduler.cc:331-0 enter find_runs()
kira-dir (200): dird/scheduler.cc:347-0 now = 5e1442d4: h=9 m=0 md=6 
wd=2 wom=0 woy=2 yday=6
kira-dir (200): dird/scheduler.cc:367-0 nh = 5e1450e4: h=10 m=0 md=6 
wd=2 wom=0 woy=2 yday=6

kira-dir (200): dird/scheduler.cc:450-0 Leave find_runs()

Any hints? What else could i check?

Best,

Kai

--
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 visit 
https://groups.google.com/d/msgid/bareos-users/619109a9-dc01-05fd-94b7-1ca908e4ee0f%40bbaw.de.

Re: [bareos-users] Re: update_bareos_tables progress

2019-10-29 Thread Kai Zimmer 

I have no table ' file name'. But for 'file' it says
bareos=# SELECT pg_size_pretty (pg_relation_size('file'));
 pg_size_pretty

 509 GB

Am 29.10.19 um 08:50 schrieb Nikolay:

What size is your DB ??? Tables "file" and "file name"???

четверг, 10 октября 2019 г., 19:38:44 UTC+3 пользователь Kai Zimmer 
написал:


Hi,

i'm trying to upgrade my bareos installation from 15.2.2.-37.1 to
17.2.4-9.1. Updating the postgres 9.3 tables under Debian 16.04
runs for
about 10 days already. I can see postgres is doing read and write
access
to temporary tables in the postgres directory (with fatrace) - and
there
is no other postgres database involved. I have plenty of free RAM and
disk space. Swap is slowly growing (about 3 GB now).

Is there any way to see how much progress update_bareos_tables script
has made?

Best,

Kai

--
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 
<mailto:bareos-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bareos-users/38bbb5c9-f910-43e6-a439-d3a164df9661%40googlegroups.com 
<https://groups.google.com/d/msgid/bareos-users/38bbb5c9-f910-43e6-a439-d3a164df9661%40googlegroups.com?utm_medium=email_source=footer>.



--
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 visit 
https://groups.google.com/d/msgid/bareos-users/f1f28bf0-8445-473f-d81e-c221c2f1e716%40bbaw.de.

Re: [bareos-users] Re: update_bareos_tables progress

2019-10-25 Thread Kai Zimmer 

Hi,

after two weeks i stopped/interrupted the script with Ctrl-Z. According 
to strace there were only lots of zeroes written in the last time. I'm 
trying to find out now if i can still restore files - than i'll decide 
wether to completely stop the process or let it run further...


Best,
Kai

Am 25.10.19 um 11:11 schrieb Nikolay:

Is your upgrade process over?

четверг, 10 октября 2019 г., 19:38:44 UTC+3 пользователь Kai Zimmer 
написал:


Hi,

i'm trying to upgrade my bareos installation from 15.2.2.-37.1 to
17.2.4-9.1. Updating the postgres 9.3 tables under Debian 16.04
runs for
about 10 days already. I can see postgres is doing read and write
access
to temporary tables in the postgres directory (with fatrace) - and
there
is no other postgres database involved. I have plenty of free RAM and
disk space. Swap is slowly growing (about 3 GB now).

Is there any way to see how much progress update_bareos_tables script
has made?

Best,

Kai

--
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 
<mailto:bareos-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bareos-users/6a133a51-64f9-428f-b1e1-0f2e5de6490a%40googlegroups.com 
<https://groups.google.com/d/msgid/bareos-users/6a133a51-64f9-428f-b1e1-0f2e5de6490a%40googlegroups.com?utm_medium=email_source=footer>.



--
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 visit 
https://groups.google.com/d/msgid/bareos-users/0729dd34-d34e-0a82-f3ae-04f8af6650b6%40bbaw.de.

[bareos-users] update_bareos_tables progress

2019-10-10 Thread Kai Zimmer 

Hi,

i'm trying to upgrade my bareos installation from 15.2.2.-37.1 to 
17.2.4-9.1. Updating the postgres 9.3 tables under Debian 16.04 runs for 
about 10 days already. I can see postgres is doing read and write access 
to temporary tables in the postgres directory (with fatrace) - and there 
is no other postgres database involved. I have plenty of free RAM and 
disk space. Swap is slowly growing (about 3 GB now).


Is there any way to see how much progress update_bareos_tables script 
has made?


Best,

Kai

--
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 visit 
https://groups.google.com/d/msgid/bareos-users/177492d4-ef4e-e659-e78e-2d8fd35b7ffb%40bbaw.de.

Re: [bareos-users] mysql error on restore of bareos catalog dump

2019-06-27 Thread Kai Zimmer 

Hi Steffen,

thanks for your comprehensive answer. I'll try it - beginning with mysql 
5.5.


Best regards,
Kai

Am 27.06.19 um 14:19 schrieb Steffen Knauf:

Hi Kai,

i migrate from bacula to bareos with an update from mysql 5.1 to 5.7
(140 GB mysql dump).

I decided to import the dump into the original (old) mysql Version and
then upgrade to the new mysql version (step by step). I'm not sure this
is the best solution, but it works for me. I hope i don't forget one
step:

1) create database bareos
2) import dump
3) Change bareos update scripts (/usr/lib/bareos/scripts/ddl/updates/)

Change from 256 to 255:

PRIMARY KEY (`ClientId`,`FileSetId`,`FileSystem`(255))
PRIMARY KEY (`JobId`,`FileIndex`,`EnvName`(255))

4) /usr/lib/bareos/scripts/./update_bareos_tables (it takes a lng
time)

5) /usr/lib/bareos/scripts/./grant_bareos_privileges

6) mysql update (with mysqlupgrade). Perhaps you need a mysqlcheck
--repair after that

7) Change defaults:

ALTER TABLE Job ALTER SchedTime set default NULL;
ALTER TABLE Job ALTER StartTime set default NULL;
ALTER TABLE Job ALTER EndTime set default NULL;
ALTER TABLE Job ALTER RealEndTime set default NULL;
ALTER TABLE Device ALTER CleaningDate set default NULL;
ALTER TABLE  JobHisto ALTER SchedTime set default NULL;
ALTER TABLE JobHisto ALTER StartTime set default NULL;
ALTER TABLE JobHisto ALTER EndTime set default NULL;
ALTER TABLE JobHisto ALTER RealEndTime set default NULL;
ALTER TABLE LocationLog ALTER Date set default NULL;
ALTER TABLE FileSet ALTER CreateTime set default NULL;
ALTER TABLE  Media ALTER FirstWritten set default NULL;
ALTER TABLE  Media ALTER LastWritten set default NULL;
ALTER TABLE  Media ALTER LabelDate set default NULL;
ALTER TABLE  Media ALTER InitialWrite set default NULL;
ALTER TABLE Log ALTER Time set default NULL;


greets

Steffen






Hi,

one of my disks crashed and now i need to recover a mysqldump of the
bareos table (catalog). When i try that i get the following error:

ERROR 1071 (42000) at line 115331: Specified key was too long; max
key
length is 255 bytes


It looks like this is the result of an update to mysql 5.7 (see also
https://bugs.bareos.org/view.php?id=705)

My system config:

Ubuntu 16.04

bareos 15.2.2-37.1

The dumpfile is about 112 GB (!) in size. It is a secondary catalog,
i.e. i have two catalogs integrated in my bareos-dir.conf file, my
current catalog works with postgresql. But i still need to have the
old
mysql catalog at hand.

I see that this bug has been fixed in bareos 17.2.4. But how do i
recover existing mysqldumps from older bareos/mysql versions? Is
there a
script available to fix the dump file? Or should i try to recover
the
dump in an older version of mysql first?

Best,

Kai



--
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 post to this group, send email to bareos-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bareos-users/a5293547-473b-398a-9715-33de4917bff7%40bbaw.de.
For more options, visit https://groups.google.com/d/optout.

[bareos-users] mysql error on restore of bareos catalog dump

2019-06-25 Thread Kai Zimmer 

Hi,

one of my disks crashed and now i need to recover a mysqldump of the 
bareos table (catalog). When i try that i get the following error:


ERROR 1071 (42000) at line 115331: Specified key was too long; max key 
length is 255 bytes



It looks like this is the result of an update to mysql 5.7 (see also 
https://bugs.bareos.org/view.php?id=705)


My system config:

Ubuntu 16.04

bareos 15.2.2-37.1

The dumpfile is about 112 GB (!) in size. It is a secondary catalog, 
i.e. i have two catalogs integrated in my bareos-dir.conf file, my 
current catalog works with postgresql. But i still need to have the old 
mysql catalog at hand.


I see that this bug has been fixed in bareos 17.2.4. But how do i 
recover existing mysqldumps from older bareos/mysql versions? Is there a 
script available to fix the dump file? Or should i try to recover the 
dump in an older version of mysql first?


Best,

Kai

--
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 post to this group, send email to bareos-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bareos-users/ec8927f5-7196-4a93-29fa-154249ddd09f%40bbaw.de.
For more options, visit https://groups.google.com/d/optout.

Re: [bareos-users] losing LTO3 tape capacity with bareos. But full tape length can be written with dd or btape speed

2018-08-22 Thread Kai Zimmer 

Hi Tim,

does the drive have a self test function in the firmware? If so, try it. 
If not, maybe there is a test software from the vendor available?


Best regards,
Kai

Am 22.08.2018 um 09:40 schrieb Tim Banchi:

Hi Stefan,

yes, I use newly purchased ones when the autoloader/drive requested it. I got 
clean requests when getting I/O errors with really bad tapes (which I then 
dumped right away). Otherwise there have been so far no cleaning requests 
(which is normal to my experience), and the status of the drive is OK. I also 
looked up regularly logged warnings/errors, and there is nothing (except the 
aforementioned I/O errors)



On Tuesday, August 21, 2018 at 10:38:26 PM UTC+2, Stefan Klatt wrote:

Hi Tim,

 


 only a idea... did you use cleaning tapes?

 


 Regards

 


 Stefan

 

 
Am 21.08.2018 um 15:46 schrieb Tim

   Banchi:

 
 
   Hello,


I'm using Bareos 17.2 with the following pool, and device configuration:

Pool {
   Name = tape_automated
   Pool Type = Backup
   Recycle = yes   # Bareos can automatically recycle 
Volumes
   AutoPrune = yes # Prune expired volumes
   #Recycle Oldest Volume = yes
   RecyclePool = Scratch
   Maximum Volume Bytes = 0
   Job Retention = 365 days
   Volume Retention = 4 weeks
   Volume Use Duration = 12 days
   Cleaning Prefix = "CLN"
   Catalog Files = yes
   Storage = delaunay_HP_G2_Autochanger #virtualfull test
#  Next Pool = tape_automated
}

Device {
   Name = "Ultrium920"
   Media Type = LTO
   Archive Device = /dev/st1
   Autochanger = yes
   LabelMedia = no
   AutomaticMount = yes
   AlwaysOpen = yes
   RemovableMedia = yes
   Maximum Spool Size = 50G
   Spool Directory = /var/lib/bareos/spool
   Maximum Block Size = 2097152
#  Maximum Block Size = 4194304
   Maximum Network Buffer Size = 32768
   Maximum File Size = 50G
   Alert Command = "/bin/bash -c '/usr/sbin/smartctl -H -l error %c'"
}

I'm closely monitoring tape performance (write speed + capacity marked as full 
by bareos), and all tapes are losing capacity, and write speed, in an almost 
linear way.

Over the period of roughly 8 months (I installed bareos early this year) and 3 
to 4 write cycles per tape (=every 2 months a tape is rewritten), I've lost on 
average 25% of the initial capacity per tape. E.g. some tapes started at 
~400GB, and are now somewhere at 300GB. some started at 160GB, and are now 
somewhere around 120GB.

Write-speed wise, I also lose speed: The fastest tapes (most often also the 
tapes which have the highest capacity) started out at 50MB/s, and are now 
somewhere at 42MB/s. The worst tapes are somewhere between 20MB/s, and are now 
at 16MB/s.

Because most of the tapes were second-hand (we got tape drive, controller, 
autoloader, and tapes as a gift, as our NGO doesn't have any money), I blamed 
the bad state of tapes (I verify volume to catalog after each job, I assume I'm 
still fine. Also there are no tape alerts).
But in the course of this year, I also introduced some brand new (never 
written) tapes. And they are also losing capacity, and write speed to the same 
amount.

Hardware compression, (software) encryption, and software compression is all ON 
since the very beginning (so no configuration change). And I don't think this 
can be relevant, because tapes are losing capacity over time, whether they 
started off at ~406GB (new) or 160GB (used, and initial bad condition). It also 
doesn't depend what I back up (everything is encrypted anyway, so compression 
shouldn't work at all at the drive's side).

I don't know the logic how bareos recognises that a tape is full, so I thought I give it 
a try to fill some tapes with zero/urandom to "realign" it. I could fully write 
to those tapes (=400GB). But bareos continued to only partly use them as before. I then 
tried to fill the tapes up with btape speed, but the same problem persists when using the 
tape again in bareos.

Tape backups typically have job logs like:

*Joblog*
Connecting to Director localhost:9101
1000 OK: pavlov-dir Version: 17.2.4 (21 Sep 2017)
Enter a period to cancel a command.
list joblog jobid=7665
Automatically selected Catalog: MyCatalog
Using Catalog "MyCatalog"
  2018-08-18 06:37:51 pavlov-dir JobId 7665: Start Backup JobId 7665, 
Job=edite_backup_automated.2018-08-18_05.30.00_34
  2018-08-18 06:37:52 pavlov-dir JobId 7665: Using Device "Ultrium920" to write.
  2018-08-18 06:37:53 delaunay-sd JobId 7665: 3307 Issuing autochanger "unload slot 
2, drive 0" command.
  2018-08-18 06:40:22 delaunay-sd JobId 7665: 3304 Issuing autochanger "load slot 1, 
drive 0" command.
  2018-08-18 06:41:06 delaunay-sd JobId 7665: 3305 Autochanger "load slot 1, drive 
0", status is OK.
  2018-08-18 06:41:15 delaunay-sd JobId 7665: Volume "XM2705L3" previously 
written, moving to end of data.
  2018-08-18 06:41:33 delaunay-sd JobId 7665: Ready to append to end of Volume 
"XM2705L3" at file=5.
  2018-08-18 06:41:33

Re: [bareos-users] Re: Trouble with LTO3

2018-01-12 Thread Kai Zimmer 

Problem solved! The storage definition was slightly wrong.

Am 12.01.2018 um 10:15 schrieb Kai Zimmer:

Hi listers,

the drive properly writes to tape using btape. But bconsole is unable 
to write to it - according to the debug output of bareos-sd the drive 
is used as readonly (mode=OPEN_READ_ONLY see below).

Any hints what the problem could be?

This is the drive definition used:

Device {
   Name = LTO3
   Media Type = LTO-3
   Archive Device = /dev/nst0
   AutomaticMount = yes;
   AlwaysOpen = yes;
   RemovableMedia = yes;
   RandomAccess = no;
   Maximum File Size = 4GB
}

Best,
Kai

Am 11.01.2018 um 11:52 schrieb Maciej Piasecki:
ii bareos 16.2.4-3+deb9u1 ii 
bareos-bat    16.2.4-3+deb9u1




Kaiu Simmer suggested

"
Looks like Bareos considers the tape (or the tape device) as 
readonly. I'm stuck here. It's best to send this output to the 
mailing list again, including your bareos version number. And mention 
the error codes directly in the the subject line like


"3999 Device "/dev/nst0" not found or could not be opened" vs 
"OPEN_READ_ONLY"


"

This debug from labeled operation

"
root@desk1:/home/Maciej# /usr/sbin/bareos-sd -f -d 150 -v
bareos-sd (100): parse_conf.c:151-0 config file = 
/etc/bareos/bareos-sd.conf

bareos-sd (100): lex.c:356-0 glob /etc/bareos/bareos-sd.conf: 1 files
bareos-sd (100): lex.c:250-0 open config file: 
/etc/bareos/bareos-sd.conf
bareos-sd (90): stored_conf.c:772-0 Inserting Director res: 
bareos-storage-mon

bareos-sd (90): stored_conf.c:772-0 Inserting Device res: LTO3
bareos-sd (100): lex.c:356-0 glob /etc/bareos/bareos-sd.conf: 1 files
bareos-sd (100): lex.c:250-0 open config file: 
/etc/bareos/bareos-sd.conf

bareos-storage-sd (100): jcr.c:141-0 read_last_jobs seek to 192
bareos-storage-sd (100): jcr.c:148-0 Read num_items=6
bareos-storage-sd (8): crypto_cache.c:55-0 Could not open crypto 
cache file. /var/lib/bareos/bareos-sd.9103.cryptoc ERR=Nie ma takiego 
pliku ani katalogu
bareos-storage-sd (10): socket_server.c:112-0 stored: listening on 
port 9103
bareos-storage-sd (100): bnet_server_tcp.c:170-0 Addresses 
host[ipv4;0.0.0.0;9103]
bareos-storage-sd (90): stored.c:651-0 calling init_dev 
/var/lib/bareos/storage
bareos-storage-sd (100): dev.c:394-0 init_dev: tape=0 
dev_name=/var/lib/bareos/storage
bareos-storage-sd (100): dev.c:396-0 dev=/var/lib/bareos/storage 
dev_max_bs=0 max_bs=0
bareos-storage-sd (10): stored.c:653-0 SD init done 
/var/lib/bareos/storage
bareos-storage-sd (100): block.c:127-0 created new block of blocksize 
64512 (dev->device->label_block_size) as dev->max_block_size is zero

bareos-storage-sd (90): stored.c:651-0 calling init_dev /dev/nst0
bareos-storage-sd (100): sd_backends.c:113-0 init_backend_dev: 
testing backend /usr/lib/bareos/backends/libbareossd-tape.so

bareos-storage-sd (100): dev.c:394-0 init_dev: tape=1 dev_name=/dev/nst0
bareos-storage-sd (100): dev.c:396-0 dev=/dev/nst0 dev_max_bs=0 max_bs=0
bareos-storage-sd (10): stored.c:653-0 SD init done /dev/nst0
bareos-storage-sd (100): block.c:127-0 created new block of blocksize 
64512 (dev->device->label_block_size) as dev->max_block_size is zero
bareos-storage-sd (20): stored.c:672-0 calling first_open_device 
"LTO3" (/dev/nst0)

bareos-storage-sd (120): device.c:266-0 start open_output_device()
bareos-storage-sd (129): device.c:285-0 Opening device.
bareos-storage-sd (100): dev.c:562-0 open dev: type=2 dev_name="LTO3" 
(/dev/nst0) vol= mode=OPEN_READ_ONLY
bareos-storage-sd (100): dev.c:581-0 call open_device 
mode=OPEN_READ_ONLY
bareos-storage-sd (100): generic_tape_device.c:49-0 Open dev: device 
is tape
bareos-storage-sd (100): generic_tape_device.c:60-0 Try open "LTO3" 
(/dev/nst0) mode=OPEN_READ_ONLY

bareos-storage-sd (100): generic_tape_device.c:88-0 Rewind after open
bareos-storage-sd (100): generic_tape_device.c:996-0 In 
set_os_device_parameters
bareos-storage-sd (100): generic_tape_device.c:1002-0 Set block size 
to zero

bareos-storage-sd (100): generic_tape_device.c:1018-0 MTSETDRVBUFFER
bareos-storage-sd (100): generic_tape_device.c:144-0 open dev: tape 4 
opened

bareos-storage-sd (100): dev.c:589-0 preserve=0xf88a8db6 fd=4
bareos-storage-sd (129): device.c:291-0 open dev "LTO3" (/dev/nst0) OK
bareos-storage-sd (100): dev.c:503-0 setting minblocksize to 64512, 
maxblocksize to label_block_size=64512, on device "LTO3" (/dev/nst0)
bareos-storage-sd (100): label.c:76-0 Enter read_volume_label res=0 
device="LTO3" (/dev/nst0) vol= dev_Vol=*NULL* max_blocksize=64512
bareos-storage-sd (130): label.c:140-0 Big if statement in 
read_volume_label
bareos-storage-sd (130): label.c:152-0 Could not unserialize Volume 
label: ERR=label.c:870 Expecting Volume Label, got FI=0 Stream=0 
len=64412


bareos-storage-sd (100): label.c:173-0 No volume label - bailing out
bareos-storage-sd (150): l

Re: [bareos-users] Re: Trouble with LTO3

2018-01-12 Thread Kai Zimmer 

Hi listers,

the drive properly writes to tape using btape. But bconsole is unable to 
write to it - according to the debug output of bareos-sd the drive is 
used as readonly (mode=OPEN_READ_ONLY see below).

Any hints what the problem could be?

This is the drive definition used:

Device {
   Name = LTO3
   Media Type = LTO-3
   Archive Device = /dev/nst0
   AutomaticMount = yes;
   AlwaysOpen = yes;
   RemovableMedia = yes;
   RandomAccess = no;
   Maximum File Size = 4GB
}

Best,
Kai

Am 11.01.2018 um 11:52 schrieb Maciej Piasecki:

ii  bareos16.2.4-3+deb9u1   
  ii  bareos-bat16.2.4-3+deb9u1



Kaiu Simmer suggested

"
Looks like Bareos considers the tape (or the tape device) as readonly. I'm 
stuck here. It's best to send this output to the mailing list again, including 
your bareos version number. And mention the error codes directly in the the 
subject line like

"3999 Device "/dev/nst0" not found or could not be opened" vs "OPEN_READ_ONLY"

"

This debug from labeled operation

"
root@desk1:/home/Maciej# /usr/sbin/bareos-sd -f -d 150 -v
bareos-sd (100): parse_conf.c:151-0 config file = /etc/bareos/bareos-sd.conf
bareos-sd (100): lex.c:356-0 glob /etc/bareos/bareos-sd.conf: 1 files
bareos-sd (100): lex.c:250-0 open config file: /etc/bareos/bareos-sd.conf
bareos-sd (90): stored_conf.c:772-0 Inserting Director res: bareos-storage-mon
bareos-sd (90): stored_conf.c:772-0 Inserting Device res: LTO3
bareos-sd (100): lex.c:356-0 glob /etc/bareos/bareos-sd.conf: 1 files
bareos-sd (100): lex.c:250-0 open config file: /etc/bareos/bareos-sd.conf
bareos-storage-sd (100): jcr.c:141-0 read_last_jobs seek to 192
bareos-storage-sd (100): jcr.c:148-0 Read num_items=6
bareos-storage-sd (8): crypto_cache.c:55-0 Could not open crypto cache file. 
/var/lib/bareos/bareos-sd.9103.cryptoc ERR=Nie ma takiego pliku ani katalogu
bareos-storage-sd (10): socket_server.c:112-0 stored: listening on port 9103
bareos-storage-sd (100): bnet_server_tcp.c:170-0 Addresses 
host[ipv4;0.0.0.0;9103]
bareos-storage-sd (90): stored.c:651-0 calling init_dev /var/lib/bareos/storage
bareos-storage-sd (100): dev.c:394-0 init_dev: tape=0 
dev_name=/var/lib/bareos/storage
bareos-storage-sd (100): dev.c:396-0 dev=/var/lib/bareos/storage dev_max_bs=0 
max_bs=0
bareos-storage-sd (10): stored.c:653-0 SD init done /var/lib/bareos/storage
bareos-storage-sd (100): block.c:127-0 created new block of blocksize 64512 
(dev->device->label_block_size) as dev->max_block_size is zero
bareos-storage-sd (90): stored.c:651-0 calling init_dev /dev/nst0
bareos-storage-sd (100): sd_backends.c:113-0 init_backend_dev: testing backend 
/usr/lib/bareos/backends/libbareossd-tape.so
bareos-storage-sd (100): dev.c:394-0 init_dev: tape=1 dev_name=/dev/nst0
bareos-storage-sd (100): dev.c:396-0 dev=/dev/nst0 dev_max_bs=0 max_bs=0
bareos-storage-sd (10): stored.c:653-0 SD init done /dev/nst0
bareos-storage-sd (100): block.c:127-0 created new block of blocksize 64512 
(dev->device->label_block_size) as dev->max_block_size is zero
bareos-storage-sd (20): stored.c:672-0 calling first_open_device "LTO3" 
(/dev/nst0)
bareos-storage-sd (120): device.c:266-0 start open_output_device()
bareos-storage-sd (129): device.c:285-0 Opening device.
bareos-storage-sd (100): dev.c:562-0 open dev: type=2 dev_name="LTO3" 
(/dev/nst0) vol= mode=OPEN_READ_ONLY
bareos-storage-sd (100): dev.c:581-0 call open_device mode=OPEN_READ_ONLY
bareos-storage-sd (100): generic_tape_device.c:49-0 Open dev: device is tape
bareos-storage-sd (100): generic_tape_device.c:60-0 Try open "LTO3" (/dev/nst0) 
mode=OPEN_READ_ONLY
bareos-storage-sd (100): generic_tape_device.c:88-0 Rewind after open
bareos-storage-sd (100): generic_tape_device.c:996-0 In set_os_device_parameters
bareos-storage-sd (100): generic_tape_device.c:1002-0 Set block size to zero
bareos-storage-sd (100): generic_tape_device.c:1018-0 MTSETDRVBUFFER
bareos-storage-sd (100): generic_tape_device.c:144-0 open dev: tape 4 opened
bareos-storage-sd (100): dev.c:589-0 preserve=0xf88a8db6 fd=4
bareos-storage-sd (129): device.c:291-0 open dev "LTO3" (/dev/nst0) OK
bareos-storage-sd (100): dev.c:503-0 setting minblocksize to 64512, maxblocksize to 
label_block_size=64512, on device "LTO3" (/dev/nst0)
bareos-storage-sd (100): label.c:76-0 Enter read_volume_label res=0 
device="LTO3" (/dev/nst0) vol= dev_Vol=*NULL* max_blocksize=64512
bareos-storage-sd (130): label.c:140-0 Big if statement in read_volume_label
bareos-storage-sd (130): label.c:152-0 Could not unserialize Volume label: 
ERR=label.c:870 Expecting Volume Label, got FI=0 Stream=0 len=64412

bareos-storage-sd (100): label.c:173-0 No volume label - bailing out
bareos-storage-sd (150): label.c:287-0 return 3
bareos-storage-sd (110): socket_server.c:79-0 Conn: Hello Director bareos-dir 
calling
bareos-storage-sd (110): socket_server.c:97-0 Got a DIR connection at 
11-sty-2018 11:13:53

Re: [bareos-users] Trouble with LTO3

2018-01-10 Thread Kai Zimmer 

Hi Maciej,

have you tried /dev/tape/by-id/scsi...-nst ?
This is a a single drive, not a library, right? Is this the first time 
you want to use it with Bareos?


Greetings from Berlin,
Kai

Am 10.01.2018 um 11:14 schrieb Maciej Piasecki:

I can't  writing in my Ultrim 960

"Bareos requires the nst devices so / dev / nst0 instead of / dev / st0. Shoe"

I tested all devices

"I'm not sure, if this solves the problem. You also get the btape test
program. Have you installed the bareos-storage-tape package?"


Of course
I testing configuration with dir (debian) and file
In email is attached config

from console...


root@desk1:/etc/amanda# less /etc/bareos/bareos-sd.conf
root@desk1:/etc/amanda# btape -v -c /etc/bareos/bareos-sd.conf LTO3
Tape block granularity is 1024 bytes.
btape: butil.c:274-0 Using device: "LTO3" for writing.
.
.

.
.
^C

root@desk1:/etc# ^C
root@desk1:/etc# ^C
root@desk1:/etc# ^C
root@desk1:/etc# ^C
root@desk1:/etc# ^C
root@desk1:/etc# btape -v -c /etc/bareos/bareos-sd.conf LTO3
Tape block granularity is 1024 bytes.
btape: butil.c:274-0 Using device: "LTO3" for writing.
^C
root@desk1:/etc#
root@desk1:/etc# dmesg |grep nst
[7.135053] xc2028 2-0061: creating new instance
root@desk1:/etc# dmesg |grep st0
[0.894625] scsi host0: ahci
[5.756608] st 6:0:3:0: Attached scsi tape st0
[5.756612] st 6:0:3:0: st0: try direct i/o: yes (alignment 512 B)
[6.252610] st 6:0:3:0: [st0] Block limits 1 - 16777215 bytes.
root@desk1:/etc#
root@desk1:/etc#



Scanning SCSI subsystem for new devices
Scanning host 0 for  SCSI target IDs  0 1 2 3 4 5 6 7, all LUNs
Scanning for device 0 0 0 0 ...
OLD: Host: scsi0 Channel: 00 Id: 00 Lun: 00
   Vendor: ATA  Model: KINGSTON SV300S3 Rev: BBF0
   Type:   Direct-AccessANSI SCSI revision: 05
Scanning host 1 for  SCSI target IDs  0 1 2 3 4 5 6 7, all LUNs
Scanning for device 1 0 0 0 ...
OLD: Host: scsi1 Channel: 00 Id: 00 Lun: 00
   Vendor: ATA  Model: WDC WD10EZRX-00A Rev: 1A01
   Type:   Direct-AccessANSI SCSI revision: 05
Scanning host 2 for  SCSI target IDs  0 1 2 3 4 5 6 7, all LUNs
Scanning host 3 for  SCSI target IDs  0 1 2 3 4 5 6 7, all LUNs
Scanning for device 3 0 0 0 ...
OLD: Host: scsi3 Channel: 00 Id: 00 Lun: 00
   Vendor: PIONEER  Model: BD-RW   BDR-207M Rev: 1.21
   Type:   CD-ROM   ANSI SCSI revision: 05
Scanning host 4 for  SCSI target IDs  0 1 2 3 4 5 6 7, all LUNs
Scanning host 5 for  SCSI target IDs  0 1 2 3 4 5 6 7, all LUNs
Scanning host 6 for  SCSI target IDs  0 1 2 3 4 5 6 7, all LUNs
Scanning for device 6 0 3 0 ...
OLD: Host: scsi6 Channel: 00 Id: 03 Lun: 00
   Vendor: HP   Model: Ultrium 3-SCSI   Rev: G66D
   Type:   Sequential-AccessANSI SCSI revision: 03


My SD config in file (for test - default in Debian config is directory from 
files)




-

#
# Default Bareos Storage Daemon Configuration file
#
#  For Bareos release 12.4.4 (12 June 2013) -- suse SUSE Linux Enterprise 
Server 11 (x86_64)
#
# You may need to change the name of your tape drive
#   on the "Archive Device" directive in the Device
#   resource.  If you change the Name and/or the
#   "Media Type" in the Device resource, please ensure
#   that dird.conf has corresponding changes.
#

Storage { # definition of myself
   Name = bareos-storage-sd
   Maximum Concurrent Jobs = 20

   # remove comment in next line to load plugins from specified directory
   # Plugin Directory = /usr/lib64/bareos/plugins
}

#
# List Directors who are permitted to contact Storage daemon
#
Director {
   Name = bareos-dir
   Password = "ZknJYcTKtHNuCCmc7c827hQVKWT5RKyEhw+tI7PTJ7nv"
}

#
# Restricted Director, used by tray-monitor to get the
#   status of the storage daemon
#
Director {
   Name = bareos-storage-mon
   Password = "ZknJYcTKtHNuCCmc7c827hQVKWT5RKyEhw+tI7PTJ7nv"
   Monitor = yes
}

#
# Note, for a list of additional Device templates please
#  see the directory /examples/devices
# Or follow the following link:
#  
http://bareos.svn.sourceforge.net/viewvc/bareos/trunk/bareos/examples/devices/
#

#
# Devices supported by this Storage daemon
# To connect, the Director's bareos-dir.conf must have the
#  same Name and MediaType.
#

Device {
   Name = FileStorage
   Media Type = File
   Archive Device = /var/lib/bareos/storage
   LabelMedia = yes;   # lets Bareos label unlabeled media
   Random Access = Yes;
   AutomaticMount = yes;   # when device opened, read it
   RemovableMedia = no;
   AlwaysOpen = no;
}

#
# An autochanger device with two drives
#
#Autochanger {
#  Name = Autochanger
#  Device = Drive-1
#  Device = Drive-2
#  Changer Command = "/usr/lib/bareos/scripts/mtx-changer %c %o %S %a %d"
#  Changer Device = /dev/sg0
#}

#Device {
#  Name = Drive-1  #
.
#Device {
#  Name = Drive-2  #
#  Drive Index = 1
#  Media Type = DLT-8000
...
#
# A

Re: [bareos-users] Server reboots on unmounting tape

2017-11-09 Thread Kai Zimmer 

Hi,

is the LTO drive the only device on the controller or do you have also 
disk drives attached to it? If so, try using a dedicated controller for 
the LTO drive.


Best,
Kai

Am 09.11.2017 um 15:43 schrieb Василий Потапов:


Hi guys
Installed Bareos on my new HP ProLiant DL360G9 with P441 controller and 
attached an HP LTO-5 SAS driver. Tried to use it, but got some strange issue. 
When, for example, I run btape speed test, it passes ok, but when I type 
'quit', my server reboots. The same issue I got, when I backed up some files to 
tape and tried to unmount and eject cassette. Does anybody got the same?



--
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 post to this group, send email to bareos-users@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [bareos-users] Work with Quantum Superloader 3?

2015-04-17 Thread Kai Zimmer 

Am 16.04.2015 um 18:58 schrieb Todd Blum:

Hello,

 I currently have an old version of Symantec Backup Exec working with a 
Quantum Superloader 3 tape library.

 If I switched to Bareos, would it be able to use the Superloader tape 
library?

 I see that I will need to run Bareos on a Linux or Univention Linux server.


Hi,

yes i have one here with LTO5 tape drive. It works fine under linux - no 
special drivers needed.

If you don't use barcodes, then you should disable the barcode reader.

Best regards,
Kai

--
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 post to this group, send email to bareos-users@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.