[bareos-users] LabelMedia = no;

2021-09-05 Thread 'Frank Cherry' via bareos-users 
Hi there,

in my storage device configuration
/etc/bareos/bareos-sd.d/device/TapeStorage.conf
I have set LabelMedia = no;
But yesterday the first tape was full an then:


20
2021-09-04 11:51:11
bareos-dir JobId 491: Created new Volume "CRFull-0050" in catalog.

19
2021-09-04 11:51:10
bareos-sd JobId 491: End of medium on Volume "CRFull-001" 
Bytes=6,087,968,665,600 Blocks=27,424,830 at 04-Sep-2021 11:51. 

Is there anything else a config which overwrite this setting?
Bareos v20.0.1

Thanks Frank

-- 
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/e294242a-7812-4d30-9acb-c2d8d125506an%40googlegroups.com.

[bareos-users] backup from gluster fs

2021-05-20 Thread 'Frank Cherry' via bareos-users 

Hi there,
what is the criteria for the Bareos FD to take a file to a differeantial or 
incremental backup against the prev. full backup ?

Example:

[op1@storage1 ~]# stat 
/mnt/glusterfs/piler/store/00/588/00/45/40005885d683233125cc00df2ff10045.m
  File: 
„/mnt/glusterfs/piler/store/00/588/00/45/40005885d683233125cc00df2ff10045.m“
  Size: 3912Blocks: 8  IO Block: 131072 reguläre Datei
Device: 17h/23d Inode: 10930643060122436912  Links: 1
Access: (0777/-rwxrwxrwx)  Uid: (  500/backup_master)   Gid: (  
500/backup_master)
*Access: 2021-05-21 08:31:13.545365435 +0200*
*Modify: 2017-01-23 11:10:01.744076268 +0100*
*Change: 2021-05-21 08:31:13.568365427 +0200*

Is it Modify or Change ? I think, it is change because glusterfs 
permanently updates the meta data of the files and so it's impossible to 
back up ONLY modified files.

Is there a strategy for backing up GlusterFS volumes (FUSE mount) or can I 
change the criteria of the FD to backup only modified files?

Thanks, Frank

-- 
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/75f6707b-8297-4cf6-82c4-52d142809ea2n%40googlegroups.com.

[bareos-users] Re: Whitepaper tape speed optimation

2021-05-02 Thread 'Frank Cherry' via bareos-users 
Yes thanks, I have taken out the information from Google cache. But on both 
sources, the diagrams are not available.

atb, Frank

d.san...@gmail.com schrieb am Samstag, 1. Mai 2021 um 16:00:12 UTC+2:

> I seem to get the same error. But I found a snapshot of the page on 
> archive.org. Hope it helps.
>
>
> https://web.archive.org/web/20201028133014/https://www.bareos.com/en/Whitepapers/articles/Speed_Tuning_of_Tape_Drives.html
>
> -Dmitri
> On Tuesday, April 20, 2021 at 10:05:36 AM UTC+3 Frank Cherry wrote:
>
>> Hi there,
>> can anyone mail me please the Whitepaper for Tape speed optimation:
>>
>> https://www.bareos.com/en/Whitepapers/articles/Speed_Tuning_of_Tape_Drives.html
>>
>> the page brings a 404 error an the diagrams are not visible in google 
>> cache.
>>
>> Thanks, Frank
>>
>

-- 
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/a7fe4e72-b252-439d-b2d7-d8af3d97a609n%40googlegroups.com.

[bareos-users] Restore Bug: wrong pool selected by Bareos

2021-04-28 Thread 'Frank Cherry' via bareos-users 

Scenario:
Restore a dir from a full backup job.

>From the log:





*bareos-sd JobId 256: Please mount read Volume "Audio-001" for: Job: 
RestoreFiles.2021-04-28_14.18.25_49 Storage: "LTO7-Tape-Drive" (/dev/nst0) 
Pool: Incremental Media type: LTO-7 *

Problem, the Volume "Audio-001" is not or was never a member of the 
"Incremental" pool.


**list volumes pool=IncrementalNo results to list.*

But this is correct now:

*list volumes pool=AudioBackup
+-++---+-+---+--+--+-+--+---+---+-+-+
| mediaid | volumename | volstatus | enabled | volbytes  | volfiles 
| volretention | recycle | slot | inchanger | mediatype | 
lastwritten | storage |
+-++---+-+---+--+--+-+--+---+---+-+-+
|  45 | Audio-001  | Append|   1 | 1,325,144,182,784 |   67 
|  946,080,000 |   0 |0 | 0 | LTO-7 | 2021-04-26 
16:09:42 | Tape|
+-++---+-+---+--+--+-+--+---+---+-+-+

You can see, Audio-001 is a member of AudioBackup pool.

The job was started with an empty LTO drive. Get also the Email message:
*28-Apr 14:18 bareos-sd JobId 256: Please mount read Volume "Audio-001" 
for: Job: RestoreFiles.2021-04-28_14.18.25_49 Storage: "LTO7-Tape-Drive" 
(/dev/nst0) Pool: Incremental Media type: LTO-7* 

I have cenceled the job and insert the Audio-001 tape, the start the 
restore job again. Now it takes the right volume:

*bareos-sd JobId 257: Ready to read from volume "Audio-001" on device 
"LTO7-Tape-Drive" (/dev/nst0). *

Is this a bug or have I do a mount after interting the right tape?
But if I wouldn't know, to which pool / volume the required restoring files 
are belogngs, this would be a nightmare to find the right tape, when it 
shows me the wrong name of the pool.

Thanks for an hints, Frank

-- 
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/6e99b12e-9472-4900-993e-a753876fce40n%40googlegroups.com.

Re: [bareos-users] LTO-7 tape lost capacity during recycling

2021-04-25 Thread 'Frank Cherry' via bareos-users 
Problem solved:

st 9:0:0:0: [st0] Add. Sense: Warning - specified temperature exceeded 

gaves me the hint: After checking the server and watching the fans with a 
endoscopic camera and closed cover inside the rack:

After starting the test, the speed of the fans goes up, but with increasing 
of the temperature, they lowered the speed instead of spooling up more.
Checking the the controller shows some damaged capacitors. After replacing 
the caps and simulating hot air with a hairdryer, the speed of the fans is 
now linear to the increasing temperature. The test is now running well and 
stable with a thruput of arounf 280 MB/s

Thanks and all the best, Frank



Frank Cherry schrieb am Sonntag, 25. April 2021 um 17:10:14 UTC+2:

> There are some kernel messages too:
>
> [ 6882.814479] btape   D0  6770   5665 0x0320
> [ 6882.814484] Call Trace:
> [ 6882.814493]  __schedule+0x2e6/0x700
> [ 6882.814497]  schedule+0x33/0xa0
> [ 6882.814500]  schedule_timeout+0x205/0x330
> [ 6882.814504]  ? __blk_mq_delay_run_hw_queue+0x14a/0x160
> [ 6882.814508]  ? blk_mq_run_hw_queue+0x90/0x120
> [ 6882.814510]  wait_for_completion+0xb7/0x140
> [ 6882.814515]  ? wake_up_q+0x80/0x80
> [ 6882.814522]  st_do_scsi.constprop.31+0x371/0x410 [st]
> [ 6882.814527]  st_write+0x328/0xd80 [st]
> [ 6882.814532]  ? common_file_perm+0x5e/0x140
> [ 6882.814536]  __vfs_write+0x1b/0x40
> [ 6882.814538]  vfs_write+0xab/0x1b0
> [ 6882.814541]  ksys_write+0x61/0xe0
> [ 6882.814544]  __x64_sys_write+0x1a/0x20
> [ 6882.814547]  do_syscall_64+0x57/0x190
> [ 6882.814551]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
> [ 6882.814554] RIP: 0033:0x7fb4698e0815
> [ 6882.814561] Code: Bad RIP value.
> [ 6882.814562] RSP: 002b:7ffec86872d8 EFLAGS: 0246 ORIG_RAX: 
> 0001
> [ 6882.814565] RAX: ffda RBX: 01989f90 RCX: 
> 7fb4698e0815
> [ 6882.814566] RDX: 0008 RSI: 0199b528 RDI: 
> 0003
> [ 6882.814568] RBP: 0199b528 R08: 7ffec8687268 R09: 
> 7ffec8687260
> [ 6882.814569] R10: 608535d1 R11: 0246 R12: 
> 0008
> [ 6882.814570] R13:  R14: 7fb46abbaae0 R15: 
> 0008
> [ 6900.114207] st 9:0:0:0: [st0] Sense Key : Not Ready [current] 
> [ 6900.114212] st 9:0:0:0: [st0] Add. Sense: Warning - specified 
> temperature exceeded
> [ 6900.177340] st 9:0:0:0: [st0] Sense Key : Not Ready [current] 
> [ 6900.177343] st 9:0:0:0: [st0] Add. Sense: Warning - specified 
> temperature exceeded
>
> Frank Cherry schrieb am Samstag, 24. April 2021 um 18:13:37 UTC+2:
>
>> The test with an other tape ends: 
>>
>> have placed an other tape into drive, rewind and start the fill test:
>>
>> [root@bareos ~]# mt -f /dev/st0 rewind
>> [root@bareos ~]# btape /dev/nst0
>> Tape block granularity is 1024 bytes.
>> btape: stored/butil.cc:293-0 Using device: "/dev/nst0" for writing.
>> btape: stored/btape.cc:481-0 open device "LTO7-Tape-Drive" (/dev/nst0): OK
>>
>> *fill
>>
>> This command simulates Bareos writing to a tape.
>> It requires either one or two blank tapes, which it
>> will label and write.
>>
>> If you have an autochanger configured, it will use
>> the tapes that are in slots 1 and 2, otherwise, you will
>> be prompted to insert the tapes when necessary.
>>
>> It will print a status approximately
>> every 322 MB, and write an EOF every 20.00 G.  If you have
>> selected the simple test option, after writing the first tape
>> it will rewind it and re-read the last block written.
>>
>> If you have selected the multiple tape test, when the first tape
>> fills, it will ask for a second, and after writing a few more
>> blocks, it will stop.  Then it will begin re-reading the
>> two tapes.
>>
>> This may take a long time -- hours! ...
>>
>> Do you want to run the simplified test (s) with one tape
>> or the complete multiple tape (m) test: (s/m) s
>> Simple test (single tape) selected.
>> btape: stored/btape.cc:3000-0 Autochanger returned: 0
>> Mount blank Volume on device "LTO7-Tape-Drive" (/dev/nst0) and press 
>> return when ready:
>> btape: stored/btape.cc:3006-0
>> Wrote Volume label for volume "TestVolume1".
>> Wrote Start of Session label.
>> 15:28:50 Begin writing Bareos records to tape ...
>> Wrote block=5000, file,blk=1,5000 VolBytes=2,621,440,000 rate=262.1 MB/s
>>
>> Wrote block=1, file,blk=1,1 VolBytes=5,242,880,000 rate=275.9 MB/s
>> Wrote block=15000, file,blk=1,15000 VolBytes=7,864,320,000 rate=280.8 MB/s
>> Wrote block=2, file,blk=1,2 VolBytes=10,485,760,000 rate=291.2 
>> MB/s
>>
>> Wrote block=25000, file,blk=1,25000 VolBytes=13,107,200,000 rate=291.2 
>> MB/s
>> Wrote block=3, file,blk=1,3 VolBytes=15,728,640,000 rate=296.7 
>> MB/s
>>
>> Wrote block=35000, file,blk=1,35000 VolBytes=18,350,080,000 rate=295.9 
>> MB/s
>> Wrote block=4, file,blk=2,1854 VolBytes=20,971,520,000 rate=275.9 MB/s
>> Wrote block=45000, file,blk=2,6854 VolBytes=23,592,960,000 rate=280.8 MB/s
>> Wrote bl

Re: [bareos-users] LTO-7 tape lost capacity during recycling

2021-04-25 Thread 'Frank Cherry' via bareos-users 
There are some kernel messages too:

[ 6882.814479] btape   D0  6770   5665 0x0320
[ 6882.814484] Call Trace:
[ 6882.814493]  __schedule+0x2e6/0x700
[ 6882.814497]  schedule+0x33/0xa0
[ 6882.814500]  schedule_timeout+0x205/0x330
[ 6882.814504]  ? __blk_mq_delay_run_hw_queue+0x14a/0x160
[ 6882.814508]  ? blk_mq_run_hw_queue+0x90/0x120
[ 6882.814510]  wait_for_completion+0xb7/0x140
[ 6882.814515]  ? wake_up_q+0x80/0x80
[ 6882.814522]  st_do_scsi.constprop.31+0x371/0x410 [st]
[ 6882.814527]  st_write+0x328/0xd80 [st]
[ 6882.814532]  ? common_file_perm+0x5e/0x140
[ 6882.814536]  __vfs_write+0x1b/0x40
[ 6882.814538]  vfs_write+0xab/0x1b0
[ 6882.814541]  ksys_write+0x61/0xe0
[ 6882.814544]  __x64_sys_write+0x1a/0x20
[ 6882.814547]  do_syscall_64+0x57/0x190
[ 6882.814551]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 6882.814554] RIP: 0033:0x7fb4698e0815
[ 6882.814561] Code: Bad RIP value.
[ 6882.814562] RSP: 002b:7ffec86872d8 EFLAGS: 0246 ORIG_RAX: 
0001
[ 6882.814565] RAX: ffda RBX: 01989f90 RCX: 
7fb4698e0815
[ 6882.814566] RDX: 0008 RSI: 0199b528 RDI: 
0003
[ 6882.814568] RBP: 0199b528 R08: 7ffec8687268 R09: 
7ffec8687260
[ 6882.814569] R10: 608535d1 R11: 0246 R12: 
0008
[ 6882.814570] R13:  R14: 7fb46abbaae0 R15: 
0008
[ 6900.114207] st 9:0:0:0: [st0] Sense Key : Not Ready [current] 
[ 6900.114212] st 9:0:0:0: [st0] Add. Sense: Warning - specified 
temperature exceeded
[ 6900.177340] st 9:0:0:0: [st0] Sense Key : Not Ready [current] 
[ 6900.177343] st 9:0:0:0: [st0] Add. Sense: Warning - specified 
temperature exceeded

Frank Cherry schrieb am Samstag, 24. April 2021 um 18:13:37 UTC+2:

> The test with an other tape ends: 
>
> have placed an other tape into drive, rewind and start the fill test:
>
> [root@bareos ~]# mt -f /dev/st0 rewind
> [root@bareos ~]# btape /dev/nst0
> Tape block granularity is 1024 bytes.
> btape: stored/butil.cc:293-0 Using device: "/dev/nst0" for writing.
> btape: stored/btape.cc:481-0 open device "LTO7-Tape-Drive" (/dev/nst0): OK
>
> *fill
>
> This command simulates Bareos writing to a tape.
> It requires either one or two blank tapes, which it
> will label and write.
>
> If you have an autochanger configured, it will use
> the tapes that are in slots 1 and 2, otherwise, you will
> be prompted to insert the tapes when necessary.
>
> It will print a status approximately
> every 322 MB, and write an EOF every 20.00 G.  If you have
> selected the simple test option, after writing the first tape
> it will rewind it and re-read the last block written.
>
> If you have selected the multiple tape test, when the first tape
> fills, it will ask for a second, and after writing a few more
> blocks, it will stop.  Then it will begin re-reading the
> two tapes.
>
> This may take a long time -- hours! ...
>
> Do you want to run the simplified test (s) with one tape
> or the complete multiple tape (m) test: (s/m) s
> Simple test (single tape) selected.
> btape: stored/btape.cc:3000-0 Autochanger returned: 0
> Mount blank Volume on device "LTO7-Tape-Drive" (/dev/nst0) and press 
> return when ready:
> btape: stored/btape.cc:3006-0
> Wrote Volume label for volume "TestVolume1".
> Wrote Start of Session label.
> 15:28:50 Begin writing Bareos records to tape ...
> Wrote block=5000, file,blk=1,5000 VolBytes=2,621,440,000 rate=262.1 MB/s
>
> Wrote block=1, file,blk=1,1 VolBytes=5,242,880,000 rate=275.9 MB/s
> Wrote block=15000, file,blk=1,15000 VolBytes=7,864,320,000 rate=280.8 MB/s
> Wrote block=2, file,blk=1,2 VolBytes=10,485,760,000 rate=291.2 MB/s
>
> Wrote block=25000, file,blk=1,25000 VolBytes=13,107,200,000 rate=291.2 MB/s
> Wrote block=3, file,blk=1,3 VolBytes=15,728,640,000 rate=296.7 MB/s
>
> Wrote block=35000, file,blk=1,35000 VolBytes=18,350,080,000 rate=295.9 MB/s
> Wrote block=4, file,blk=2,1854 VolBytes=20,971,520,000 rate=275.9 MB/s
> Wrote block=45000, file,blk=2,6854 VolBytes=23,592,960,000 rate=280.8 MB/s
> Wrote block=5, file,blk=2,11854 VolBytes=26,214,400,000 rate=281.8 MB/s
> Wrote block=55000, file,blk=2,16854 VolBytes=28,835,840,000 rate=285.5 MB/s
>
> Wrote block=6, file,blk=2,21854 VolBytes=31,457,280,000 rate=285.9 MB/s
> Wrote block=65000, file,blk=2,26854 VolBytes=34,078,720,000 rate=288.8 MB/s
>
> Wrote block=7, file,blk=2,31854 VolBytes=36,700,160,000 rate=288.9 MB/s
> Wrote block=75000, file,blk=2,36854 VolBytes=39,321,600,000 rate=289.1 MB/s
> Wrote block=8, file,blk=3,3708 VolBytes=41,943,040,000 rate=281.4 MB/s
> Wrote block=85000, file,blk=3,8708 VolBytes=44,564,480,000 rate=282.0 MB/s
> Wrote block=9, file,blk=3,13708 VolBytes=47,185,920,000 rate=284.2 MB/s
>
> Wrote block=95000, file,blk=3,18708 VolBytes=49,807,360,000 rate=284.6 MB/s
> Wrote block=10, file,blk=3,23708 VolBytes=52,428,800,000 rate=284.9 
> MB/s
> Wrote block=105000, file,blk=3,2870

Re: [bareos-users] LTO-7 tape lost capacity during recycling

2021-04-24 Thread 'Frank Cherry' via bareos-users 
The test with an other tape ends: 

have placed an other tape into drive, rewind and start the fill test:

[root@bareos ~]# mt -f /dev/st0 rewind
[root@bareos ~]# btape /dev/nst0
Tape block granularity is 1024 bytes.
btape: stored/butil.cc:293-0 Using device: "/dev/nst0" for writing.
btape: stored/btape.cc:481-0 open device "LTO7-Tape-Drive" (/dev/nst0): OK
*fill

This command simulates Bareos writing to a tape.
It requires either one or two blank tapes, which it
will label and write.

If you have an autochanger configured, it will use
the tapes that are in slots 1 and 2, otherwise, you will
be prompted to insert the tapes when necessary.

It will print a status approximately
every 322 MB, and write an EOF every 20.00 G.  If you have
selected the simple test option, after writing the first tape
it will rewind it and re-read the last block written.

If you have selected the multiple tape test, when the first tape
fills, it will ask for a second, and after writing a few more
blocks, it will stop.  Then it will begin re-reading the
two tapes.

This may take a long time -- hours! ...

Do you want to run the simplified test (s) with one tape
or the complete multiple tape (m) test: (s/m) s
Simple test (single tape) selected.
btape: stored/btape.cc:3000-0 Autochanger returned: 0
Mount blank Volume on device "LTO7-Tape-Drive" (/dev/nst0) and press return 
when ready:
btape: stored/btape.cc:3006-0
Wrote Volume label for volume "TestVolume1".
Wrote Start of Session label.
15:28:50 Begin writing Bareos records to tape ...
Wrote block=5000, file,blk=1,5000 VolBytes=2,621,440,000 rate=262.1 MB/s
Wrote block=1, file,blk=1,1 VolBytes=5,242,880,000 rate=275.9 MB/s
Wrote block=15000, file,blk=1,15000 VolBytes=7,864,320,000 rate=280.8 MB/s
Wrote block=2, file,blk=1,2 VolBytes=10,485,760,000 rate=291.2 MB/s
Wrote block=25000, file,blk=1,25000 VolBytes=13,107,200,000 rate=291.2 MB/s
Wrote block=3, file,blk=1,3 VolBytes=15,728,640,000 rate=296.7 MB/s
Wrote block=35000, file,blk=1,35000 VolBytes=18,350,080,000 rate=295.9 MB/s
Wrote block=4, file,blk=2,1854 VolBytes=20,971,520,000 rate=275.9 MB/s
Wrote block=45000, file,blk=2,6854 VolBytes=23,592,960,000 rate=280.8 MB/s
Wrote block=5, file,blk=2,11854 VolBytes=26,214,400,000 rate=281.8 MB/s
Wrote block=55000, file,blk=2,16854 VolBytes=28,835,840,000 rate=285.5 MB/s
Wrote block=6, file,blk=2,21854 VolBytes=31,457,280,000 rate=285.9 MB/s
Wrote block=65000, file,blk=2,26854 VolBytes=34,078,720,000 rate=288.8 MB/s
Wrote block=7, file,blk=2,31854 VolBytes=36,700,160,000 rate=288.9 MB/s
Wrote block=75000, file,blk=2,36854 VolBytes=39,321,600,000 rate=289.1 MB/s
Wrote block=8, file,blk=3,3708 VolBytes=41,943,040,000 rate=281.4 MB/s
Wrote block=85000, file,blk=3,8708 VolBytes=44,564,480,000 rate=282.0 MB/s
Wrote block=9, file,blk=3,13708 VolBytes=47,185,920,000 rate=284.2 MB/s
Wrote block=95000, file,blk=3,18708 VolBytes=49,807,360,000 rate=284.6 MB/s
Wrote block=10, file,blk=3,23708 VolBytes=52,428,800,000 rate=284.9 MB/s
Wrote block=105000, file,blk=3,28708 VolBytes=55,050,240,000 rate=285.2 MB/s
Wrote block=11, file,blk=3,33708 VolBytes=57,671,680,000 rate=282.7 MB/s
Wrote block=115000, file,blk=4,562 VolBytes=60,293,120,000 rate=281.7 MB/s
Wrote block=12, file,blk=4,5562 VolBytes=62,914,560,000 rate=278.3 MB/s
Wrote block=125000, file,blk=4,10562 VolBytes=65,536,000,000 rate=278.8 MB/s
Wrote block=13, file,blk=4,15562 VolBytes=68,157,440,000 rate=279.3 MB/s
Wrote block=135000, file,blk=4,20562 VolBytes=70,778,880,000 rate=280.8 MB/s
Wrote block=14, file,blk=4,25562 VolBytes=73,400,320,000 rate=281.2 MB/s
Wrote block=145000, file,blk=4,30562 VolBytes=76,021,760,000 rate=282.6 MB/s
Wrote block=15, file,blk=4,35562 VolBytes=78,643,200,000 rate=282.8 MB/s
Wrote block=155000, file,blk=5,2416 VolBytes=81,264,640,000 rate=279.2 MB/s
Wrote block=16, file,blk=5,7416 VolBytes=83,886,080,000 rate=279.6 MB/s
Wrote block=165000, file,blk=5,12416 VolBytes=86,507,520,000 rate=279.9 MB/s
Wrote block=17, file,blk=5,17416 VolBytes=89,128,960,000 rate=281.1 MB/s
Wrote block=175000, file,blk=5,22416 VolBytes=91,750,400,000 rate=281.4 MB/s
Wrote block=18, file,blk=5,27416 VolBytes=94,371,840,000 rate=282.5 MB/s
Wrote block=185000, file,blk=5,32416 VolBytes=96,993,280,000 rate=282.7 MB/s
Wrote block=19, file,blk=5,37416 VolBytes=99,614,720,000 rate=282.9 MB/s
Wrote block=195000, file,blk=6,4270 VolBytes=102,236,160,000 rate=280.0 MB/s
Wrote block=20, file,blk=6,9270 VolBytes=104,857,600,000 rate=280.3 MB/s
Wrote block=205000, file,blk=6,14270 VolBytes=107,479,040,000 rate=281.3 
MB/s
Wrote block=21, file,blk=6,19270 VolBytes=110,100,480,000 rate=281.5 
MB/s
Wrote block=215000, file,blk=6,24270 VolBytes=112,721,920,000 rate=280.4 
MB/s
Wrote block=22, file,blk=6,29270 VolBytes=115,343,360,000 rate=280.6 
MB/s
Wrote block=225000, file,blk=6,34270 VolBytes=117,964,800,000 rate=280.8 
MB/s
Wrote block=23,

Re: [bareos-users] LTO-7 tape lost capacity during recycling

2021-04-24 Thread 'Frank Cherry' via bareos-users 
ead test  
> dd if=/backup_spool/testfile of=/dev/null bs=1M count=204800
> 204800+0 Datensätze ein
> 204800+0 Datensätze aus
> 214748364800 bytes (215 GB, 200 GiB) copied, 625,029 s, 344 MB/s
>
> My conclusion: I can read up to 344 MB/s from the spooling directory.
>
> Tape test 1 with 512k Blocks using btape:
> *speed file_size=3 skip_raw
>
> btape: stored/btape.cc:1048-0 Test with zero data and bareos block 
> structure.
> btape: stored/btape.cc:938-0 Begin writing 3 files of 3.221 GB with blocks 
> of 524288 bytes.
> 
> btape: stored/btape.cc:600-0 Wrote 1 EOF to "LTO7-Tape-Drive" (/dev/nst0)
> btape: stored/btape.cc:416-0 Volume bytes=3.221 GB. Write rate = 292.8 MB/s
> 
> btape: stored/btape.cc:600-0 Wrote 1 EOF to "LTO7-Tape-Drive" (/dev/nst0)
> btape: stored/btape.cc:416-0 Volume bytes=3.221 GB. Write rate = 322.1 MB/s
> 
> btape: stored/btape.cc:600-0 Wrote 1 EOF to "LTO7-Tape-Drive" (/dev/nst0)
> btape: stored/btape.cc:416-0 Volume bytes=3.221 GB. Write rate = 322.1 MB/s
> btape: stored/btape.cc:392-0 Total Volume bytes=9.663 GB. Total Write rate 
> = 311.7 MB/s
>
> btape: stored/btape.cc:1060-0 Test with random data, should give the 
> minimum throughput.
> btape: stored/btape.cc:938-0 Begin writing 3 files of 3.221 GB with blocks 
> of 524288 bytes.
> +
> btape: stored/btape.cc:600-0 Wrote 1 EOF to "LTO7-Tape-Drive" (/dev/nst0)
> btape: stored/btape.cc:416-0 Volume bytes=3.221 GB. Write rate = 94.74 MB/s
> 
> btape: stored/btape.cc:600-0 Wrote 1 EOF to "LTO7-Tape-Drive" (/dev/nst0)
> btape: stored/btape.cc:416-0 Volume bytes=3.221 GB. Write rate = 94.74 MB/s
> 
> btape: stored/btape.cc:600-0 Wrote 1 EOF to "LTO7-Tape-Drive" (/dev/nst0)
> btape: stored/btape.cc:416-0 Volume bytes=3.221 GB. Write rate = 94.74 MB/s
> btape: stored/btape.cc:392-0 Total Volume bytes=9.663 GB. Total Write rate 
> = 94.74 MB/s
>
> Are the random data to low ?
> the Quantum LTO-7 HH drive is connectet to a Microsemi 1100-4i SAS HBA.
>
> Mainboard: ASUSTeK ROG STRIX B450-F 
> CPU: AMD Ryzen 3 3200G 
>
> Have now start a fill test:
>
> [root@bareos ~]# mt -f /dev/st0 rewind
> [root@bareos ~]# mt -f /dev/st0 status
> SCSI 2 tape drive:
> File number=0, block number=0, partition=0.
> Tape block size 0 bytes. Density code 0x5c (no translation).
> Soft error count since last status=0
> General status bits on (4101):
>  BOT ONLINE IM_REP_EN
>
> btape /dev/nst0
> *fill
>
> This command simulates Bareos writing to a tape.
> It requires either one or two blank tapes, which it
> will label and write.
>
> If you have an autochanger configured, it will use
> the tapes that are in slots 1 and 2, otherwise, you will
> be prompted to insert the tapes when necessary.
>
> It will print a status approximately
> every 322 MB, and write an EOF every 20.00 G.  If you have
> selected the simple test option, after writing the first tape
> it will rewind it and re-read the last block written.
>
> If you have selected the multiple tape test, when the first tape
> fills, it will ask for a second, and after writing a few more
> blocks, it will stop.  Then it will begin re-reading the
> two tapes.
>
> This may take a long time -- hours! ...
>
> Do you want to run the simplified test (s) with one tape
> or the complete multiple tape (m) test: (s/m) s
> Simple test (single tape) selected.
> btape: stored/btape.cc:3000-0 Autochanger returned: 0
> Mount blank Volume on device "LTO7-Tape-Drive" (/dev/nst0) and press 
> return when ready:
> btape: stored/btape.cc:3006-0
> Wrote Volume label for volume "TestVolume1".
> Wrote Start of Session label.
> 12:46:12 Begin writing Bareos records to tape ...
> Wrote block=5000, file,blk=1,5000 VolBytes=2,621,440,000 rate=238.3 MB/s
> Wrote block=1, file,blk=1,1 VolBytes=5,242,880,000 rate=275.9 MB/s
> .
>
> will report the result in some hours 
>
> Thanks for helping me.
>
>
>
>
>
> Christian Svensson schrieb am Samstag, 24. April 2021 um 11:13:07 UTC+2:
>
>> Hi, 
>>
>> New on this forum, and new on tape in general - but I think I might be 
>> able to help here. 
>>
>> On Sat, Apr 24, 2021 at 9:29 AM 'Frank Cherry' via bareos-users 
>>  wrote: 
>> > 
>> > Bareos declares fully erased LTO-7 after 628 GB as full. Details here: 
>> > https://bugs.bareos.org/view.php?id=1341 
>>
>> I know that Bacula at least assumes the volume/tape is full if it 
>> receives an uncorrectable error from the drive. 
>> That seems to be the case here:

Re: [bareos-users] LTO-7 tape lost capacity during recycling

2021-04-24 Thread 'Frank Cherry' via bareos-users 
Thanks Christian,

I use the spooling feature for the backups to tape. 
The spooling directory ( /backup_spool/ ) is a hardware RAID-0 (stripe) 
mount of two SATA harddisks.
Have done a test:

 write test  
dd if=/dev/zero of=/backup_spool/testfile bs=1M count=204800 
conv=fdatasync,notrunc
204800+0 Datensätze ein
204800+0 Datensätze aus
214748364800 bytes (215 GB, 200 GiB) copied, 596,839 s, 360 MB/s

 read test  
dd if=/backup_spool/testfile of=/dev/null bs=1M count=204800
204800+0 Datensätze ein
204800+0 Datensätze aus
214748364800 bytes (215 GB, 200 GiB) copied, 625,029 s, 344 MB/s

My conclusion: I can read up to 344 MB/s from the spooling directory.

Tape test 1 with 512k Blocks using btape:
*speed file_size=3 skip_raw

btape: stored/btape.cc:1048-0 Test with zero data and bareos block 
structure.
btape: stored/btape.cc:938-0 Begin writing 3 files of 3.221 GB with blocks 
of 524288 bytes.

btape: stored/btape.cc:600-0 Wrote 1 EOF to "LTO7-Tape-Drive" (/dev/nst0)
btape: stored/btape.cc:416-0 Volume bytes=3.221 GB. Write rate = 292.8 MB/s

btape: stored/btape.cc:600-0 Wrote 1 EOF to "LTO7-Tape-Drive" (/dev/nst0)
btape: stored/btape.cc:416-0 Volume bytes=3.221 GB. Write rate = 322.1 MB/s

btape: stored/btape.cc:600-0 Wrote 1 EOF to "LTO7-Tape-Drive" (/dev/nst0)
btape: stored/btape.cc:416-0 Volume bytes=3.221 GB. Write rate = 322.1 MB/s
btape: stored/btape.cc:392-0 Total Volume bytes=9.663 GB. Total Write rate 
= 311.7 MB/s

btape: stored/btape.cc:1060-0 Test with random data, should give the 
minimum throughput.
btape: stored/btape.cc:938-0 Begin writing 3 files of 3.221 GB with blocks 
of 524288 bytes.
+
btape: stored/btape.cc:600-0 Wrote 1 EOF to "LTO7-Tape-Drive" (/dev/nst0)
btape: stored/btape.cc:416-0 Volume bytes=3.221 GB. Write rate = 94.74 MB/s

btape: stored/btape.cc:600-0 Wrote 1 EOF to "LTO7-Tape-Drive" (/dev/nst0)
btape: stored/btape.cc:416-0 Volume bytes=3.221 GB. Write rate = 94.74 MB/s

btape: stored/btape.cc:600-0 Wrote 1 EOF to "LTO7-Tape-Drive" (/dev/nst0)
btape: stored/btape.cc:416-0 Volume bytes=3.221 GB. Write rate = 94.74 MB/s
btape: stored/btape.cc:392-0 Total Volume bytes=9.663 GB. Total Write rate 
= 94.74 MB/s

Are the random data to low ?
the Quantum LTO-7 HH drive is connectet to a Microsemi 1100-4i SAS HBA.

Mainboard: ASUSTeK ROG STRIX B450-F 
CPU: AMD Ryzen 3 3200G 

Have now start a fill test:

[root@bareos ~]# mt -f /dev/st0 rewind
[root@bareos ~]# mt -f /dev/st0 status
SCSI 2 tape drive:
File number=0, block number=0, partition=0.
Tape block size 0 bytes. Density code 0x5c (no translation).
Soft error count since last status=0
General status bits on (4101):
 BOT ONLINE IM_REP_EN

btape /dev/nst0
*fill

This command simulates Bareos writing to a tape.
It requires either one or two blank tapes, which it
will label and write.

If you have an autochanger configured, it will use
the tapes that are in slots 1 and 2, otherwise, you will
be prompted to insert the tapes when necessary.

It will print a status approximately
every 322 MB, and write an EOF every 20.00 G.  If you have
selected the simple test option, after writing the first tape
it will rewind it and re-read the last block written.

If you have selected the multiple tape test, when the first tape
fills, it will ask for a second, and after writing a few more
blocks, it will stop.  Then it will begin re-reading the
two tapes.

This may take a long time -- hours! ...

Do you want to run the simplified test (s) with one tape
or the complete multiple tape (m) test: (s/m) s
Simple test (single tape) selected.
btape: stored/btape.cc:3000-0 Autochanger returned: 0
Mount blank Volume on device "LTO7-Tape-Drive" (/dev/nst0) and press return 
when ready:
btape: stored/btape.cc:3006-0
Wrote Volume label for volume "TestVolume1".
Wrote Start of Session label.
12:46:12 Begin writing Bareos records to tape ...
Wrote block=5000, file,blk=1,5000 VolBytes=2,621,440,000 rate=238.3 MB/s
Wrote block=1, file,blk=1,1 VolBytes=5,242,880,000 rate=275.9 MB/s
.

will report the result in some hours 

Thanks for helping me.





Christian Svensson schrieb am Samstag, 24. April 2021 um 11:13:07 UTC+2:

> Hi,
>
> New on this forum, and new on tape in general - but I think I might be
> able to help here.
>
> On Sat, Apr 24, 2021 at 9:29 AM 'Frank Cherry' via bareos-users
>  wrote:
> >
> > Bareos declares fully erased LTO-7 after 628 GB as full. Details here:
> > https://bugs.bareos.org/view.php?id=1341
>
> I know that Bacula at least assumes the volume/tape is full if it
> receives an uncorrectable error from the drive.
> That seems to be the case here:
> 22-Apr 17:01 bareos-sd JobId 246: Error: stored/block.cc:803 Write
> error at 29:11710 on device "LTO7-Tape-Drive" (/dev/nst0).
&

[bareos-users] LTO-7 tape lost capacity during recycling

2021-04-24 Thread 'Frank Cherry' via bareos-users 
Bareos declares fully erased LTO-7 after 628 GB as full. Details here:
https://bugs.bareos.org/view.php?id=1341

Anyone a idea please?

Thanks Frank

-- 
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/1be5e19c-c4ef-4295-b785-ad373ce50328n%40googlegroups.com.

[bareos-users] Whitepaper tape speed optimation

2021-04-20 Thread 'Frank Cherry' via bareos-users 
Hi there,
can anyone mail me please the Whitepaper for Tape speed optimation:
https://www.bareos.com/en/Whitepapers/articles/Speed_Tuning_of_Tape_Drives.html

the page brings a 404 error an the diagrams are not visible in google cache.

Thanks, Frank

-- 
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/339405ed-c773-4939-8e78-03d3bb9fa49en%40googlegroups.com.

Re: [bareos-users] LTO-7 Question about capacity

2021-04-06 Thread 'Frank Cherry' via bareos-users 
Thanks Wolfgang,
I have also read some SAS datasheets of HDD's and 300 MB/s are whishes. So 
RAID or SSD like you wrote are the solutions.
My plan is now to buy excatly the same HDD for spooling and setup a 
softraid 0 (stripe set).
There should be theroretically 2x180 MB/s = 360 possible, because there is 
only one file which is used when spooling for the backup job is enabled.

Frank



wd schrieb am Dienstag, 6. April 2021 um 13:23:19 UTC+2:

> Dear Frank,
>
> In message <8a1afda1-c38f-4411...@googlegroups.com> you wrote:
> >
> > Okay, checking the datasheet of the HDD, the max. cont. data rate is 180 
> > MB/s, that's the bottle neck.
> > I will replace it with a SAS HDD, plugged directly to the HBA.
>
> Are you sure this will be sufficient?
>
> I see for example: "HP SAS 15K SFF Hard drives offer sustained
> performance of 260 MB/s to 175 MB/s (outer to inner diameter)."
>
> this would still be too slow. Either you set up a RAID array, or
> you go for SSD for spool data.
>
> > Wolfgang, can you explain please the context between start-stop mode and 
> > the serious 
> > degradation of capacity?
>
> Sorry, I don;t have any reliable data here. Modern LTO drives can do
> "speed matching" (i. e. slow down tape motion for slower incoming
> data rates), but only within certain limits. Just listen to your
> drive when running a backup - you can hear easily when it's runnin
> slower, and when it stops completely.
>
> I don't have any documents / specs that allow to estimate the impact
> on total storage capacity, sorry.
>
>
> Best regards,
>
> Wolfgang Denk
>
> -- 
> DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> Phone: (+49)-8142-66989-10 <+49%208142%206698910> Fax: (+49)-8142-66989-80 
> <+49%208142%206698980> Email: w...@denx.de
> I can't say I've ever been lost, but I was bewildered once for three
> days. - Daniel Boone (Attributed)
>

-- 
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/014cb4c5-a760-4bc4-a691-94ed9027838en%40googlegroups.com.

Re: [bareos-users] LTO-7 Question about capacity

2021-04-06 Thread &#x27;Frank Cherry&#x27; via bareos-users 
Okay, checking the datasheet of the HDD, the max. cont. data rate is 180 
MB/s, that's the bottle neck.
I will replace it with a SAS HDD, plugged directly to the HBA.

Wolfgang, can you explain please the context between start-stop mode and 
the serious 
degradation of capacity?

Thanks, Frank

Frank Cherry schrieb am Dienstag, 6. April 2021 um 11:30:35 UTC+2:

> My storage daemon hardware:
>
> Microsemi Adaptec HBA 1100 4i - Speicher-Controller - 4 Sender/Kanal - 
> SATA 6Gb/s / SAS 12Gb/s Low Profile - 1.2 GBps
> Quantum LTO-7 HH - Bandlaufwerk - LTO Ultrium (6 TB / 15 TB) - Ultrium 7 - 
> SAS-2 - intern
> A separate Seagate IronWolf NAS HDD 4TB, SATA 6Gb/s (ST4000VN008) is used 
> for spooling partition only.
>
> The SATA HDD is plugged on the main board's SATA Port. 300 MB/s = 2,4 
> Gb/s, so the 6 Gb/s should be OK.
> Taking a look to the last job: Despooling elapsed time = 03:13:27, 
> Transfer rate = 99.29 M Bytes/second 
>
> Maybe a solution to plug the HDD directly to the SAS controller?
>
> Thanks for help Wolfgang,
> Frank
> wd schrieb am Dienstag, 6. April 2021 um 11:06:09 UTC+2:
>
>> Dear Frank,
>>
>> In message <9d042448-250b-467a...@googlegroups.com> you wrote:
>> >
>> > I use Ultrium 7 tapes with 6 / 15 TB storage capacity. So I do expect a 
>> > minimum of 6 TB in worst case (without compression).
>> ...
>> > When I now calclulate the present 2.55 TB + 1,2 TB in queue = 3,75 TB, 
>> less 
>> > than 6 TB for LTO-7
>>
>> The spec for LTO 7 gives a sustained data rate of 300 MB/s. Check
>> if your storage daemon can feed the drive with such a rate;
>> otherwise the drive will run in start-stop mode which is slow, causes
>> increased wear on the drive and the tapes, and results in a serious
>> degradation of capacity - as you are seeing here.
>>
>>
>> Best regards,
>>
>> Wolfgang Denk
>>
>> -- 
>> DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
>> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
>> Phone: (+49)-8142-66989-10 <+49%208142%206698910> Fax: 
>> (+49)-8142-66989-80 <+49%208142%206698980> Email: w...@denx.de
>> Living on Earth may be expensive, but it includes an annual free trip
>> around the Sun.
>>
>

-- 
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/8a1afda1-c38f-4411-afb3-e642f41e9932n%40googlegroups.com.

Re: [bareos-users] LTO-7 Question about capacity

2021-04-06 Thread &#x27;Frank Cherry&#x27; via bareos-users 
My storage daemon hardware:

Microsemi Adaptec HBA 1100 4i - Speicher-Controller - 4 Sender/Kanal - SATA 
6Gb/s / SAS 12Gb/s Low Profile - 1.2 GBps
Quantum LTO-7 HH - Bandlaufwerk - LTO Ultrium (6 TB / 15 TB) - Ultrium 7 - 
SAS-2 - intern
A separate Seagate IronWolf NAS HDD 4TB, SATA 6Gb/s (ST4000VN008) is used 
for spooling partition only.

The SATA HDD is plugged on the main board's SATA Port. 300 MB/s = 2,4 Gb/s, 
so the 6 Gb/s should be OK.
Taking a look to the last job: Despooling elapsed time = 03:13:27, Transfer 
rate = 99.29 M Bytes/second 

Maybe a solution to plug the HDD directly to the SAS controller?

Thanks for help Wolfgang,
Frank
wd schrieb am Dienstag, 6. April 2021 um 11:06:09 UTC+2:

> Dear Frank,
>
> In message <9d042448-250b-467a...@googlegroups.com> you wrote:
> >
> > I use Ultrium 7 tapes with 6 / 15 TB storage capacity. So I do expect a 
> > minimum of 6 TB in worst case (without compression).
> ...
> > When I now calclulate the present 2.55 TB + 1,2 TB in queue = 3,75 TB, 
> less 
> > than 6 TB for LTO-7
>
> The spec for LTO 7 gives a sustained data rate of 300 MB/s. Check
> if your storage daemon can feed the drive with such a rate;
> otherwise the drive will run in start-stop mode which is slow, causes
> increased wear on the drive and the tapes, and results in a serious
> degradation of capacity - as you are seeing here.
>
>
> Best regards,
>
> Wolfgang Denk
>
> -- 
> DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> Phone: (+49)-8142-66989-10 <+49%208142%206698910> Fax: (+49)-8142-66989-80 
> <+49%208142%206698980> Email: w...@denx.de
> Living on Earth may be expensive, but it includes an annual free trip
> around the Sun.
>

-- 
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/b35f044f-ec9b-4fe9-b338-f7ac822e3c4cn%40googlegroups.com.

[bareos-users] LTO-7 Question about capacity

2021-04-06 Thread &#x27;Frank Cherry&#x27; via bareos-users 

Hi There,

I use Ultrium 7 tapes with 6 / 15 TB storage capacity. So I do expect a 
minimum of 6 TB in worst case (without compression).

Now a tape was marked as full. There are two jobs with 1.15 and 1.4 TB = 
2.55 TB.
A running job wants to despool 1,198,389,602,186 bytes.
During despooling, end of medium was reached:
End of medium on Volume "CRFull-0012" Bytes=3,314,676,943,872 
and Bareos asks for a new volume in this pool to append.

When I now calclulate the present 2.55 TB + 1,2 TB in queue = 3,75 TB, less 
than 6 TB for LTO-7

Has anyone an explantation for this please? The tape was new.
At the moment, a new tape was add to the pool and the backup continuous.

Thaks for helping, Frank

-- 
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/9d042448-250b-467a-8090-fd1a1fd6d890n%40googlegroups.com.

[bareos-users] Re: Maximum PostgreSQL Version

2021-03-25 Thread &#x27;Frank Cherry&#x27; via bareos-users 
FYI only, I had running Bareos 19 with PgSQL 12.5 on CentOS 8

mstir...@plusline.net schrieb am Mittwoch, 24. März 2021 um 14:46:51 UTC+1:

>
> Hello, 
> I have a rather simple question. I could not find anything in the release 
> notes. 
> What is the maximum PostgreSQL version I can use with Bareos 19? 
> Thank you. 

-- 
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/495211b4-265c-4ca7-8dc2-433845cd3872n%40googlegroups.com.

[bareos-users] appending a backup

2021-03-24 Thread &#x27;Frank Cherry&#x27; via bareos-users 

Helleo there,
this scenario:
I have a directory, where image files (jpg) are being. This files should 
stored in a tape. Then the files of the directory will be deleted after the 
backup was finished successful. The backup is done a a full backup job. Now 
new files are placing into the directory. The a nes full backup job  will 
started. 

So fa so good.

But if I want now to restore a file, I would have to know on which job it 
was stored.
I have tried tried to set in the GUI the restoring parameters 
"Merge all client filesets" and 
" Merge all related jobs to last full backup of selected backup job "

But the file I'm looking for was not found in the File selection list on 
the right side.

The I have slect the backup job and klicked on the restore icon. Now the 
required file for restore was found.

Is my backup strategy wrong by using full backup from the same client with 
the same file set? Or is there a bug with the merging of backups?

Thanks and best regards,
Frank

-- 
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/bb367ca9-603e-44a8-a34f-486ab1917d1cn%40googlegroups.com.

[bareos-users] Compatibility question

2021-03-17 Thread &#x27;Frank Cherry&#x27; via bareos-users 

Hi there,
On my backup system I've run Bareos v20 (Director and Storage Daemin) but I 
have a system with CentOS 6, there is running Bareos with V19 (File 
Director). I have tested it successful. 
Are there any pages which shows the version compatibility?
As I read between the lines in 
https://docs.bareos.org/Appendix/BackwardCompatibility.html
the backward compatibility to a lower version of a FD should be ever 
possible - right?

Thanks and all the best,
Frank

-- 
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/481485cc-9dd3-4f13-927c-53bdcd35984en%40googlegroups.com.

[bareos-users] Re: Jobdefs and job

2021-01-25 Thread &#x27;Frank Cherry&#x27; via bareos-users 
OK, solution found myself. It comes from the JobDefs, the last 3 lines:

" Incremental Backup Pool Type:

The Incremental Backup Pool specifies a Pool to be used for Incremental 
backups.* It will override any Pool (Dir->Job) 
 
specification during an Incremental backup.*
"
The last night was too long  
Frank Cherry schrieb am Dienstag, 26. Januar 2021 um 07:51:21 UTC+1:

>
> Hi there,
>
> Why did bareos want's the volume "... Director wanted Volume 
> "Incremental-0027". "
> from the Incremental Pool and not from the " CRInc- " Pool like configured 
> in the job?
> I thought, parameters in the job overwrites parameters in jobdefs?
>
> Here are my configs:
>
> JobDefs {
>   Name = "DefaultJob"
>   Type = Backup
>   Level = Incremental
>   Client = bareos-fd
>   FileSet = "SelfTest" # selftest 
> fileset(#13)
>   Schedule = "WeeklyCycle"
>   Storage = File
>   Messages = Standard
>   Pool = Incremental
>   Priority = 10
>   Write Bootstrap = "/var/lib/bareos/%c.bsr"
>   Full Backup Pool = Full  # write Full Backups into 
> "Full" Pool (#05)
>   Differential Backup Pool = Differential  # write Diff Backups into 
> "Differential" Pool (#08)
>   Incremental Backup Pool = Incremental# write Incr Backups into 
> "Incremental" Pool  (#11)
> }
>
> Job {
>   Name = "BackupStorage1Data"
>   JobDefs = "DefaultJob"
>   Client = "Storage1"
>   Pool = CR-Inc-Pool
>   Type = Backup
>   Storage = Tape
>   Spool Data = yes
>   Schedule = "CR-WeeklyCycle"
>   FileSet = "Storage1Data"
>   
> Run Script {
> Console = ".bvfs_update jobid=%i"
> RunsWhen = After
> RunsOnClient = No
>   }
>   RunBeforeJob = "/etc/bareos/load_tape.sh"
>   RunAfterJob  = "/etc/bareos/eject_tape.sh"
> }
>

-- 
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/a94576b8-f983-43ee-b149-e36b0f340da0n%40googlegroups.com.

[bareos-users] Jobdefs and job

2021-01-25 Thread &#x27;Frank Cherry&#x27; via bareos-users 

Hi there,

Why did bareos want's the volume "... Director wanted Volume 
"Incremental-0027". "
from the Incremental Pool and not from the " CRInc- " Pool like configured 
in the job?
I thought, parameters in the job overwrites parameters in jobdefs?

Here are my configs:

JobDefs {
  Name = "DefaultJob"
  Type = Backup
  Level = Incremental
  Client = bareos-fd
  FileSet = "SelfTest" # selftest 
fileset(#13)
  Schedule = "WeeklyCycle"
  Storage = File
  Messages = Standard
  Pool = Incremental
  Priority = 10
  Write Bootstrap = "/var/lib/bareos/%c.bsr"
  Full Backup Pool = Full  # write Full Backups into "Full" 
Pool (#05)
  Differential Backup Pool = Differential  # write Diff Backups into 
"Differential" Pool (#08)
  Incremental Backup Pool = Incremental# write Incr Backups into 
"Incremental" Pool  (#11)
}

Job {
  Name = "BackupStorage1Data"
  JobDefs = "DefaultJob"
  Client = "Storage1"
  Pool = CR-Inc-Pool
  Type = Backup
  Storage = Tape
  Spool Data = yes
  Schedule = "CR-WeeklyCycle"
  FileSet = "Storage1Data"
  
Run Script {
Console = ".bvfs_update jobid=%i"
RunsWhen = After
RunsOnClient = No
  }
  RunBeforeJob = "/etc/bareos/load_tape.sh"
  RunAfterJob  = "/etc/bareos/eject_tape.sh"
}

-- 
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/17b7d8b0-85cb-4da9-9754-dc64158745b7n%40googlegroups.com.

[bareos-users] Re: Very Newbie Linux Full Backup Size

2021-01-25 Thread &#x27;Frank Cherry&#x27; via bareos-users 
What's the output of "du -sch", executed at the VM's root: "/"

ric...@rogersuk.me.uk schrieb am Montag, 25. Januar 2021 um 09:32:29 UTC+1:

> Hi,
> I've just started looking into this app for backing up my Linux and 
> FreeBSD boxes.
> I've started by backing up one server, which is a pretty small one.
> However, the first full backup is huge (584GB).
> The server is an ESXi 6.5 VM with only a 200GB drive assigned.
> Obviously there is something I've configured wrong, so any advice 
> gratefully appreciated.
> This is what's listed in Bareos:
> [image: Bareos-Linux-Client.png]
> This is the client's file system:
> [image: Bareos-Linux-Client-Files-System.png]
> This the the FileSet:
>
> FileSet {
>   Name = "LinuxAll"
>   Description = "Backup all regular filesystems, determined by filesystem 
> type."
>   Include {
> Options {
>   Signature = MD5 # calculate md5 checksum per file
>   One FS = No # change into other filessytems
>   FS Type = btrfs
>   FS Type = ext2  # filesystems of given types will be backed up
>   FS Type = ext3  # others will be ignored
>   FS Type = ext4
>   FS Type = reiserfs
>   FS Type = jfs
>   FS Type = xfs
>   FS Type = zfs
> }
> File = /
>   }
>   # Things that usually have to be excluded
>   # You have to exclude /var/lib/bareos/storage
>   # on your bareos server
>   Exclude {
> File = /var/lib/bareos
> File = /var/lib/bareos/storage
> File = /proc
> File = /tmp
> File = /var/tmp
> File = /.journal
> File = /.fsck
>   }
> }
>
>
> JobDef:
>   GNU nano 4.8
>  /etc/bareos/bareos-dir.d/jobdefs/LinuxJob.conf
> JobDefs {
>   Name = "LinuxJob"
>   Type = Backup
>   Level = Incremental
>   Client = bareos-fd
>   FileSet = "LinuxAll"
>   Schedule = "WeeklyCycle"
>   Storage = File
>   Messages = Standard
>   Pool = Incremental
>   Priority = 10
>   Write Bootstrap = "/var/lib/bareos/%c.bsr"
>   Full Backup Pool = Full  # write Full Backups into 
> "Full" Pool (#05)
>   Differential Backup Pool = Differential  # write Diff Backups into 
> "Differential" Pool (#08)
>   Incremental Backup Pool = Incremental# write Incr Backups into 
> "Incremental" Pool  (#11)
> }
>
> Dir Config for Client:
> Job {
>   Name = "svrwebutil01"
>   Client = svrwebutil01-fd
>   JobDefs = "LinuxJob"
> }
>
>
> Client {
>   Name = svrwebutil01-fd
>   Address = svrwebutil01# the name has to be resolvable through DNS
>   Password = "REMOVED" # password for FileDaemon which has to be 
> the same like the password in the director ressource of the bareos-fd.conf 
> on the backup c>
>   File Retention = 30 days# 30 days
>   Job Retention = 6 months# six months
>   AutoPrune = yes  # Prune expired Jobs/Files
> }
>
> Thanks,
> Richie
>
>

-- 
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/ac84897e-2390-4e0e-9ddf-2238cb76b31an%40googlegroups.com.

Re: [bareos-users] LTO tape question

2021-01-14 Thread &#x27;Frank Cherry&#x27; via bareos-users 
Additional observation:

I insert the required tape into the drive
-> the drive loads the tape

I start incremential backup job
-> the drive is moving the tape to end of data 

Spooling datas starts
-> after some time, the drive rewinds the tape back to the cardridge 
*(is there a drive idle and can I configure it?)*

Spooling is finished
-> the drive is moving the tape to end of data 
-> despooling starts.

Any ideas to set the idle time of a tape drive?

Thanks and all the best, Frank
birgit.ducarroz schrieb am Mittwoch, 13. Januar 2021 um 13:38:36 UTC+1:

> Hi,
>
> I don't know what I saw :-/ but I see you already have AlwaysOpen = no
>
> and /dev/nst0 normally is also okay. At the moment I am stumped as to 
> what else it could be.
> Hoping someone else could help you.
>
> Regards,
> Birgit
>
> On 13/01/21 13:09, DUCARROZ Birgit wrote:
> > Hi,
> > 
> > Yes, try to set AlwaysOpen = no
> > 
> > Regards,
> > Birgit
> > 
> > On 13/01/21 07:37, 'Frank Cherry' via bareos-users wrote:
> >> Hi there,
> >> when I have a tape for daily incremental beackups, is there a way to 
> >> configure, that the tape
> >> not rewinds to the BOT after finish the incremental backup?
> >>
> >> In SD, the tape is set as device:
> >>
> >> Device {
> >> Name = LTO7-Tape-Drive
> >> Drive Index = 0
> >> Media Type = LTO-7
> >> Archive Device = /dev/nst0
> >> LabelMedia = yes;
> >> AutomaticMount = yes;
> >> RemovableMedia = yes;
> >> AlwaysOpen = no;
> >> RandomAccess = no;
> >> Spool Directory = /backup_spool/spool
> >> Maximum Concurrent Jobs = 1
> >> Maximum FileSize = 20GB
> >> }
> >>
> >> Thanks, Frank
> >>
> >> -- 
> >> 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...@googlegroups.com 
> >> <mailto:bareos-users...@googlegroups.com>.
> >> To view this discussion on the web visit 
> >> 
> https://groups.google.com/d/msgid/bareos-users/8f037b70-a943-4ea6-8855-5708902455e3n%40googlegroups.com
>  
> >> <
> https://groups.google.com/d/msgid/bareos-users/8f037b70-a943-4ea6-8855-5708902455e3n%40googlegroups.com?utm_medium=email&utm_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/55000830-fd74-424c-938d-fb7749e9f246n%40googlegroups.com.

[bareos-users] LTO tape question

2021-01-12 Thread &#x27;Frank Cherry&#x27; via bareos-users 
Hi there,
when I have a tape for daily incremental beackups, is there a way to 
configure, that the tape 
not rewinds to the BOT after finish the incremental backup?

In SD, the tape is set as device:

Device {
Name = LTO7-Tape-Drive
Drive Index = 0
Media Type = LTO-7
Archive Device = /dev/nst0
LabelMedia = yes;
AutomaticMount = yes;
RemovableMedia = yes;
AlwaysOpen = no;
RandomAccess = no;
Spool Directory = /backup_spool/spool
Maximum Concurrent Jobs = 1
Maximum FileSize = 20GB
}

Thanks, Frank

-- 
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/8f037b70-a943-4ea6-8855-5708902455e3n%40googlegroups.com.

[bareos-users] testting tape speed with btape

2021-01-11 Thread &#x27;Frank Cherry&#x27; via bareos-users 

Hi there,

when using:





*btape /dev/nst0Tape block granularity is 1024 bytes.btape: 
stored/butil.cc:290-0 Using device: "/dev/nst0" for writing.btape: 
stored/btape.cc:485-0 open device "LTO7-Tape-Drive" (/dev/nst0): OK*speed 
file_size=3 skip_raw*

the test ist done with* writing 3 files of 3.221 GB with blocks of 64512 
bytes*

How can I test other block sizes or which config file I have to use with 
the -c option when btape is started? 

Thanks, Frank

-- 
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/9f4e6ddd-a90e-4ae6-80a2-7c181d64208cn%40googlegroups.com.

[bareos-users] longtime archive

2021-01-10 Thread &#x27;Frank Cherry&#x27; via bareos-users 

Hi there,
I have PDF files on a folder. They should be moved on a tape for 
archiveing. If this is successful done. the source files will be delete. 
Then after some time, new files are in the source folder and should be 
moved to the tape  and so on. The tape should be a fast recovery solution 
for us. If it's not useable -we can get the files from the client. So this 
solution is only a faster way for us.

My plan is to define a pool like this:

Pool {
  Name = Archive
  Pool Type = Backup
  Recycle = no   # Bareos can automatically recycle 
Volumes
  AutoPrune = no# Prune expired volumes
  Volume Retention = 20 years # How long should the Full Backups be 
kept? (#06)
  Maximum Volumes = 100   # Limit number of Volumes in Pool
  Label Format = "Archive-"  # Volumes will be labeled 
"Full-"
}

The job will be done manually as a full backup type. 
So I'm right, that every new job will append on the tape until it's full 
and then the next empty tape will used by using auto-labeling?

When using auto-labeling, it defines a new volume by taking the prefix from 
the Label Format, defined at the Pool settings followed by counting up - 
 4 digits.
In SD the device is defined with LabelMedia = yes;
Would it be possible to do manually label a tape, then add it to the pool 
for using if needed?

thank, Frank

-- 
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/f268e7dd-23a4-4e3f-a471-eccf3d75a1b1n%40googlegroups.com.

[bareos-users] Re: Graphing Backup Usage

2021-01-07 Thread &#x27;Frank Cherry&#x27; via bareos-users 
I'm interested in too.

bols@gmail.com schrieb am Mittwoch, 6. Januar 2021 um 03:14:22 UTC+1:

> This page from the Bareos docs describing the always-incremental backup 
> scheme have some really nice graphs:
>
> https://docs.bareos.org/TasksAndConcepts/AlwaysIncrementalBackupScheme.html
>
> Are the scripts/programs that generated these graphs available?  How can I 
> generate a similar set of graphs for my own pools?
>
> Thanks,
> Schwab
>
>

-- 
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/0417201a-fb88-4f76-826f-d9d0473400b9n%40googlegroups.com.

[bareos-users] autoloader recommendation

2021-01-07 Thread &#x27;Frank Cherry&#x27; via bareos-users 
Hi there,
which LTO-7 autoloader are supported by Bareos?
Any recommendations there?

Thanks, Frank

-- 
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/0434eb2e-e86d-4910-887c-0ba823ac378bn%40googlegroups.com.

[bareos-users] Schedule question

2021-01-07 Thread &#x27;Frank Cherry&#x27; via bareos-users 

Hi there,
this is my schedule set:

Schedule {
  Name = "CR-WeeklyCycle"
  Run = Level=Full 1st sun at 7:00
  Run = Level=Differential 2nd-5th sun at 7:00
  Run = Level=Incremental mon-sat at 7:00
}

The backup is stored on a LTO tape, changed manually - no autoloader.

Looking on the schedule, a tape of the increment pool is insert on Saturday 
morining.
When now a differential or full backup is started, it checks first if the 
right tape is insert.
So I have do by manpower, that the right tape is available before the 
backup starts.

All backup jobs like inc, diff and full have spooling active.
Is there a way, that the nackups starts, and spools also if the wring tape 
is insert and after changing to the right tape, the despooling process 
starts or must I split it each backup in two jobs: copy to hdd and then to 
tape?

Thanks for any useful hints, Frank

-- 
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/7000fa15-2e2c-4224-9602-bf1f94437a85n%40googlegroups.com.

[bareos-users] LTO 7 tape with 9,87 GB marked as full:

2021-01-05 Thread &#x27;Frank Cherry&#x27; via bareos-users 

Hello there,

I use a LTO 7 ultrium tape (6 / 15 TB). On the tape "CRInc-0013"are two 
jobs with 9.87 GB used space.
Bareos marked it as full:
Why? 
Tape related logs from the 1st job:
bareos-sd JobId 33: Labeled new Volume "CRInc-0013" on device 
"LTO7-Tape-Drive" (/dev/tape). 
bareos-sd JobId 33: Wrote label to prelabeled Volume "CRInc-0013" on device 
"LTO7-Tape-Drive" (/dev/tape) 
bareos-sd JobId 33: Committing spooled data to Volume "CRInc-0013". 
Despooling 9,873,485,603 bytes 

the 2nd job:
bareos-sd JobId 38: Volume "CRInc-0013" previously written, moving to end 
of data. 
bareos-sd JobId 38: Ready to append to end of Volume "CRInc-0013" at file=1 
bareos-sd JobId 38: Committing spooled data to Volume "CRInc-0013". 
Despooling 3,399,163,731 bytes 
bareos-sd JobId 38: Error: Error writing final EOF to tape. This Volume may 
not be readable.
backends/generic_tape_device.cc:402 ioctl MTWEOF error on "LTO7-Tape-Drive" 
(/dev/tape). ERR=Input/output error. 
bareos-sd JobId 38: End of medium on Volume "CRInc-0013" 
Bytes=9,871,755,264 Blocks=153,021 at 05-Jan-2021 08:26 
bareos-sd JobId 38: Please mount append Volume "CRInc-0015" or label a new 
one for:
Job: BackupStorage1Data.2021-01-05_06.51.59_02
Storage: "LTO7-Tape-Drive" (/dev/tape)
Pool: CR-Inc-Pool
Media type: LTO-7 

Then the incrementiell backup was finished on a new tape.

The tape CRInc-0013 was manually recycled by doing this bash commands:

mt -f /dev/st0 rewind
mt -f /dev/st0 weof
mt -f /dev/st0 rewind
mt -f /dev/st0 status

status BOT = Begin of Tape was displayed finally.

Any ideas pleas?
Thanks, Frank

-- 
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/7a108ea2-f91e-4ce3-9bbb-5eca07d6e10bn%40googlegroups.com.

[bareos-users] feature request: Web-UI

2020-12-29 Thread &#x27;Frank Cherry&#x27; via bareos-users 
in configuration.ini :
Config possibility for scheduler preview time, default is 7 days

A possibility to send an email on user defined times with a scheduler 
preview, maybe also with a *.ical file for adding it to calendar.

-- 
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/070ff4d6-e716-4d1f-9895-db9dd12ba675n%40googlegroups.com.

[bareos-users] Message: send email => improper command pipelining after RCPT

2020-12-29 Thread &#x27;Frank Cherry&#x27; via bareos-users 
Hello there,

I have set up the message resource like following:

Messages {
  Name = Standard
  mailcommand = "bsmtp -h localhost -f \"%r\"
  -s \"Bareos: %t %e of %c %l\" %r"
  operatorcommand = "bsmtp -h localhost -f \"%r\"
  -s \"Bareos: Intervention needed for %j\" %r"
  mail = x...@yyy.de = all, !skipped
  operator = x...@yyy.de = mount
  console = all, !skipped, !saved, !audit
  append = "/var/log/bareos/bareos.log" = all, !skipped, !saved, !audit
  catalog = all, !skipped, !saved, !audit
}

My mailserver bounces the mail:

improper command pipelining after RCPT from unknown[192.168.130.211]: >\r\n 

looks like that the rest of e email adress ">" is left, but there are no <> 
tags are used in my config. From where did it come from?

Thanks and all the best, Frank



-- 
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/4fd88c3e-2a17-4200-a2c9-9c846c1d9644n%40googlegroups.com.

[bareos-users] pool question

2020-12-27 Thread &#x27;Frank Cherry&#x27; via bareos-users 

Hello there,

I have running a Proxmox cluster which backups the VMs and CTs daily on a 
disk array with a history of 30 days.
The only changing data inside the virtual machines are error logs 
(unimportant if restore case) and configurations (important).
Configuration changes are done 1 to 3 times per month. Important user data 
are stored outside. So important for backup is the VM with it's config as a 
working unit.

My plan is to set up a job without scheduler for each VM - so I have it run 
manually when I have made config changes on a VM or had run an update on 
it. It should be for each job a full backup - the compressed backup file of 
a CT has around 3 GB.
The backup should be store on two different tapes (LTO-7)
So calculated in append mode, with 6000 GB space on tape, I would have 
space for up to 2000 full backups per tape.

Is there a way to do it within a pool definition, e.g. make a copy on a 2nd 
volume or the other way for me would be:

1. Making a spooling job to local disk
2. followed by a copy job to tape volume
3. followed by a move job to 2nd tape volume

When using the last scenario, can I label both volumes identically and it 
would be no matter which tape I use in the case of restoring?

I do own a single tape drive only, no autoloader. So manually work is 
needed.

Thanks, all the best, Frank

-- 
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/6bd90c53-9331-466d-a324-5c8a2265c2afn%40googlegroups.com.

[bareos-users] space management on tape

2020-12-26 Thread &#x27;Frank Cherry&#x27; via bareos-users 

Hi there,
a question how Bareos managed space on tape:
Hypothetc:

On a LTO tape are stored in this order 3 jobs:
1: 3 TB
2: 2 TB
3: 1 TB

Job 1 is deleted.
Now a new job is queued, the spooling file has a size of 2 TB.

Will now the SD despool it 
a) on position 4 of the tape (append) [this is what I think]
or
b) replace position1 because the is availabe space

So, thinking about fragmentation would be one part of a backup strategy 
when working with tapes.

Thanks and all the best, Frank


-- 
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/b5b7f195-056e-4391-99f0-6de9b0b87129n%40googlegroups.com.

[bareos-users] reusing tapes

2020-12-26 Thread &#x27;Frank Cherry&#x27; via bareos-users 

Hello there,

I have done a lot of test with writing to LTO tape. Now I want to set the 
tapes back to a clean state, like new. I have found this in the web:

Insert the tape into drive.
   
mt -f ${DRIVE} rewind 
mt -f ${DRIVE} weof
mt -f ${DRIVE} rewind

Now the tape should be ready for usage, the SD will label it automatically 
when requested. This is then needed when starting with a new catalog when 
I'm cleared about my future backup strategies. There will also flow in all 
the valuable pointers from all the people here, helping me to understand 
this great powerfulg software. Thanks a lot. Great community here.

Do you have any objections?
Thanks and all the best, Frank

-- 
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/9ad0a549-ff49-418a-8b55-98fd71a59c10n%40googlegroups.com.

Re: [bareos-users] Maximum Volume Bytes for Ultrium LTO-7 tape

2020-12-25 Thread &#x27;Frank Cherry&#x27; via bareos-users 
Thanks for the information, I will play with some test backups and see, 
also install sg_utils and check.

Thanks a lot, Frank

bro...@mlds-networks.com schrieb am Freitag, 25. Dezember 2020 um 19:18:08 
UTC+1:

> Found the command it’s
>
> sg_logs -a 
> sg_logs -a /dev/sg5
>
> 
> Data compression page (LTO-5 specific) [0x32]
> Read compression ratio x100: 109
> Write compression ratio x100: 100
>
>
> You can see I’m not compressing at all because I’m doing client side 
> compression (backing up over home networks)
>
> You can also compare the bareos volume size to 
>
> Tape capacity page (LTO-5 and LTO-6 specific) [0x31]
> Main partition remaining capacity (in MiB): 46592
> Alternate partition remaining capacity (in MiB): 0
> Main partition maximum capacity (in MiB): 800226
> Alternate partition maximum capacity (in MiB): 0
>
> Which is the native capacity, if your volume is larger than your actual 
> consumed your compression is working.
>
> Brock Palen
> bro...@mlds-networks.com
> www.mlds-networks.com
> Websites, Linux, Hosting, Joomla, Consulting
>
>
>
> > On Dec 25, 2020, at 12:58 PM, Brock Palen  
> wrote:
> > 
> > Also compression look up the mt commands. But most are on by default. 
> Only encryption is anything you need to mess with in bareos. Again if doing 
> client compression you won’t see much if any on the tape side. If your not 
> you should see it. 
> > 
> > You can verify how much compression your getting two ways. One is the 
> volume size bareos reports being larger than the 6T native size. 
> > 
> > The other is look at the sg_* commands. One will read ann the drive and 
> currently loaded tape data. One will tell you compression ratio read / 
> written for the tape. 
> > 
> > Sent from my iPhone
> > Brock Palen
> > 989-277-6075 <(989)%20277-6075>
> > 
> >> On Dec 25, 2020, at 12:53 PM, Brock Palen  
> wrote:
> >> 
> >> I wouldn’t bother. Modern LTO drives (any made in lay 10 years) auto 
> detect end of volume. I do t use this setting at all with my two drives and 
> it auto sorts it out. 
> >> 
> >> This is important because the 15T quoted assumes compression of a given 
> ratio. That can very drastically. If you use client side compression you 
> won’t see any compression at all. Similar if most your data are video and 
> doesn’t compress well. If it’s all text emails you will get more than 
> listed. 
> >> 
> >> Let the drive auto detect and it will work the best. I think this is 
> one of the things you can test with the btape command. Highly recommend you 
> run all the tests in btape abd make sure they pass. 
> >> 
> >> I only use max volume size with disk volumes.
> >> 
> >> Sent from my iPhone
> >> Brock Palen
> >> 989-277-6075 <(989)%20277-6075>
> >> 
> >>> On Dec 25, 2020, at 12:38 PM, 'Frank Cherry' via bareos-users <
> bareos...@googlegroups.com> wrote:
> >>> 
> >>> 
> >>> Hello there,
> >>> 
> >>> I'm storing on Ultrium 7 LTO tapes with a single drive unit. 
> >>> It is right, to set in the pool config the 
> >>> 
> >>> Maximum Volume Bytes = 15000G # Limit Volume size to something 
> reasonable
> >>> 
> >>> to 15000G ? The tape is specified with 6 / 15 TB (uncompressed / 
> compressed)
> >>> 
> >>> Is the tape drive works as default with compression? How can I check 
> it and can I define it on the SD config?
> >>> 
> >>> Thanks, Frank
> >>> 
> >>> -- 
> >>> 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...@googlegroups.com.
> >>> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/bareos-users/f7fef681-396f-47dc-8a76-6a28547e7caan%40googlegroups.com
> .
>
>

-- 
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/22f744b7-dd1e-43ba-850e-cb4c287d81c7n%40googlegroups.com.

[bareos-users] Maximum Volume Bytes for Ultrium LTO-7 tape

2020-12-25 Thread &#x27;Frank Cherry&#x27; via bareos-users 
Hello there,

I'm storing on Ultrium 7 LTO tapes with a single drive unit. 
It is right, to set in the pool config the   

Maximum Volume Bytes = 15000G  # Limit Volume size to something 
reasonable

to 15000G ? The tape is specified with 6 / 15 TB (uncompressed / compressed)

Is the tape drive works as default with compression? How can I check it and 
can I define it on the SD config?

Thanks, Frank

-- 
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/f7fef681-396f-47dc-8a76-6a28547e7caan%40googlegroups.com.

[bareos-users] Execute script in FileSet

2020-12-25 Thread &#x27;Frank Cherry&#x27; via bareos-users 
Hello there,
my goal is, to backup only files, created of today.

This is my FileSet:

FileSet {
  Name = "Storage1PVE"
  Description = "PVE backups from GlusterFS"
  Include {
Options {
  Signature = MD5 # calculate md5 checksum per file
  Compression = LZ4
  noatime = yes
}
File = "|sh -c 'find /mnt/glusterfs/pve_dump/dump/ -type f -mtime -1 
-name \"*.zst\"'"
  }
}

When I execute it on the client, I get display the right files.
But when I start a job in Bareos, I get:

bareos-dir JobId 13: Fatal error: Error running program: sh -c 'find 
/mnt/glusterfs/pve_dump/dump/ -type f -mtime -1 -name "*.zst"'. ERR=Child 
exited with code 1 

Followed the instructions on: 
https://docs.bareos.org/Configuration/Director.html#fileset-include

What I'm doing wrong?

-- 
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/c5806bea-9612-4e96-8bf9-9c5a2251f845n%40googlegroups.com.

Re: [bareos-users] some newbie questions

2020-12-23 Thread &#x27;Frank Cherry&#x27; via bareos-users 
Thanks, have insert it into my configs and start a test but this was 
terminated by an error. Here is the lof of the job:


2020-12-23 16:32:25
storage1-fd JobId 9: Fatal error: lib/bsock_tcp.cc:131 Unable to connect to 
Storage daemon on 127.0.0.1:9103. ERR=Verbindungsaufbau abgelehnt

2020-12-23 16:32:25
storage1-fd JobId 9: Fatal error: Failed to connect to Storage daemon: 
127.0.0.1:9103

2020-12-23 16:32:25
bareos-dir JobId 9: Fatal error: Bad response to Storage command: wanted 
2000 OK storage
, got 2902 Bad storage


2020-12-23 16:32:25
bareos-dir JobId 9: Error: Bareos bareos-dir 19.2.7 (16Apr20):
Build OS: Linux-3.10.0-1062.18.1.el7.x86_64 redhat Red Hat Enterprise Linux 
release 8.1 (Ootpa)
JobId: 9
Job: BackupStorage1.2020-12-23_16.02.22_04
Backup Level: Full
Client: "Storage1" 19.2.7 (16Apr20) 
Linux-3.10.0-1062.18.1.el7.x86_64,redhat,CentOS release 6.10 (Final)
FileSet: "Storage1Data" 2020-12-23 14:53:23
Pool: "Full" (From command line)
Catalog: "MyCatalog" (From Client resource)
Storage: "Tape" (From Job resource)
Scheduled time: 23-Dec-2020 16:02:22
Start time: 23-Dec-2020 16:02:24
End time: 23-Dec-2020 16:32:25
Elapsed time: 30 mins 1 sec
Priority: 10
FD Files Written: 0
SD Files Written: 0
FD Bytes Written: 0 (0 B)
SD Bytes Written: 0 (0 B)
Rate: 0.0 KB/s
Software Compression: None
VSS: no
Encryption: no
Accurate: no
Volume name(s): 
Volume Session Id: 1
Volume Session Time: 1608735731
Last Volume Bytes: 0 (0 B)
Non-fatal FD errors: 2
SD Errors: 0
FD termination status: Fatal Error
SD termination status: Waiting on FD
Bareos binary info: bareos.org build: Get official binaries and vendor 
support on bareos.com
Termination: *** Backup Error ***


2020-12-23 16:28:25
storage1-fd JobId 9: Warning: lib/bsock_tcp.cc:125 Could not connect to 
Storage daemon on 127.0.0.1:9103. ERR=Verbindungsaufbau abgelehnt
Retrying ...

2020-12-23 16:23:15
storage1-fd JobId 9: Warning: lib/bsock_tcp.cc:125 Could not connect to 
Storage daemon on 127.0.0.1:9103. ERR=Verbindungsaufbau abgelehnt
Retrying ...

2020-12-23 16:18:05
storage1-fd JobId 9: Warning: lib/bsock_tcp.cc:125 Could not connect to 
Storage daemon on 127.0.0.1:9103. ERR=Verbindungsaufbau abgelehnt
Retrying ...

2020-12-23 16:12:55
storage1-fd JobId 9: Warning: lib/bsock_tcp.cc:125 Could not connect to 
Storage daemon on 127.0.0.1:9103. ERR=Verbindungsaufbau abgelehnt
Retrying ...

2020-12-23 16:07:45
storage1-fd JobId 9: Warning: lib/bsock_tcp.cc:125 Could not connect to 
Storage daemon on 127.0.0.1:9103. ERR=Verbindungsaufbau abgelehnt
Retrying ...

2020-12-23 16:02:35
storage1-fd JobId 9: Warning: lib/bsock_tcp.cc:125 Could not connect to 
Storage daemon on 127.0.0.1:9103. ERR=Verbindungsaufbau abgelehnt
Retrying ...

2020-12-23 16:02:24
bareos-dir JobId 9: Start Backup JobId 9, 
Job=BackupStorage1.2020-12-23_16.02.22_04

2020-12-23 16:02:24
bareos-dir JobId 9: Connected Storage daemon at 127.0.0.1:9103, encryption: 
TLS_CHACHA20_POLY1305_SHA256

2020-12-23 16:02:24
bareos-dir JobId 9: Using Device "LTO7-Tape-Drive" to write.

2020-12-23 16:02:24
bareos-dir JobId 9: Probing client protocol... (result will be saved until 
config reload)

2020-12-23 16:02:24
bareos-dir JobId 9: Connected Client: Storage1 at 192.168.130.170:9102, 
encryption: PSK-AES256-CBC-SHA

2020-12-23 16:02:24
bareos-dir JobId 9: Handshake: Immediate TLS 
2020-12-23 16:02:24
bareos-dir JobId 9: Encryption: PSK-AES256-CBC-SHA

--

Explanation: Client is Storage1 => 192.168.130.170 only FD is running there:
# ps ax | grep bareos
32321 ?Ssl0:00 /usr/sbin/bareos-fd -g bareos

# netstat -tulpn | grep bareos
tcp0  0 0.0.0.0:91020.0.0.0:*   
LISTEN  32321/bareos-fd

>From this client, I can connect to the Backup-Server 192.168.130.211 with 
DIR and SD running on it:

# telnet 192.168.130.211 9101
Trying 192.168.130.211...
Connected to 192.168.130.211.
Escape character is '^]'.
x
▒Connection closed by foreign host.

]# telnet 192.168.130.211 9103
Trying 192.168.130.211...
Connected to 192.168.130.211.
Escape character is '^]'.
x
▒Connection closed by foreign host.

During the backup, I have read this status infos:

Client Details:
Connecting to Client Storage1 at 192.168.130.170:9102
 Handshake: Immediate TLS, Encryption: PSK-AES256-CBC-SHA

storage1-fd Version: 19.2.7 (16 April 2020)  
Linux-3.10.0-1062.18.1.el7.x86_64 redhat CentOS release 6.10 (Final)
Daemon started 23-Dez-20 15:46. Jobs: run=0 running=0, bareos.org build 
binary
 Sizeof: boffset_t=8 size_t=8 debug=0 trace=0 bwlimit=0kB/s

Running Jobs:
JobId 9 Job BackupStorage1.2020-12-23_16.02.22_04 is running.
Full System or Console Job started: 23-Dez-20 16:02
Files=0 Bytes=0 Bytes/sec=0 Errors=0
Bwlimit=0
Files Examined=0
SDSocket closed.
bareos-dir (director) connected at: 23-Dez-20 16:19

Director:
Running Jobs:
Console connected at 23-Dec-20 16:19
 JobId Level   Name

[bareos-users] Re: storage tape device, SD didn't start

2020-12-23 Thread &#x27;Frank Cherry&#x27; via bareos-users 
Problem solved: "bareos-storage-tape" was not installed automaticly, after 
done it manually the SD starts.



Frank Cherry schrieb am Mittwoch, 23. Dezember 2020 um 10:25:33 UTC+1:

> Hello there,
>
> I try to set up a single tape device, I can write an read from commandline 
> and also get the status:
>
> mt -f /dev/tape status
> SCSI 2 tape drive:
> File number=0, block number=0, partition=0.
> Tape block size 0 bytes. Density code 0x5c (no translation).
> Soft error count since last status=0
> General status bits on (4101):
>  BOT ONLINE IM_REP_EN
>
> When I use in SD a device config with:
> Archive Device = /dev/tape
>
> the SD didn't start
> But using e.g. a disk path:
> Archive Device = /backup_spool/spool
>
> SD starts up.
>
> have also tried:
> Archive Device = /dev/st0
> Archive Device = /dev/nst0
>
> Bareos V 19.2.7.-2
>
> What's going wrong?
>
>
>

-- 
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/6110bafc-c04b-4f25-8996-0f9467bf4a65n%40googlegroups.com.

[bareos-users] storage tape device, SD didn't start

2020-12-23 Thread &#x27;Frank Cherry&#x27; via bareos-users 
Hello there,

I try to set up a single tape device, I can write an read from commandline 
and also get the status:

mt -f /dev/tape status
SCSI 2 tape drive:
File number=0, block number=0, partition=0.
Tape block size 0 bytes. Density code 0x5c (no translation).
Soft error count since last status=0
General status bits on (4101):
 BOT ONLINE IM_REP_EN

When I use in SD a device config with:
Archive Device = /dev/tape

the SD didn't start
But using e.g. a disk path:
Archive Device = /backup_spool/spool

SD starts up.

have also tried:
Archive Device = /dev/st0
Archive Device = /dev/nst0

Bareos V 19.2.7.-2

What's going wrong?


-- 
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/c913988a-96da-4742-960b-c2cb7d16b393n%40googlegroups.com.

[bareos-users] setting up tape device

2020-12-23 Thread &#x27;Frank Cherry&#x27; via bareos-users 
Hi there,

with the additional file, placed here:
 /etc/bareos/bareos-sd.de/device/TapeStorage.conf

Device {
Name = LTO7-Tape-Drive
Drive Index = 0
Media Type = Tape
Archive Device = /dev/st0
LabelMedia = yes;
AutomaticMount = yes;
RemovableMedia = yes;
AlwaysOpen = no;
RandomAccess = no;
Spool Directory = /backup_spool/spool
Maximum Concurrent Jobs = 1
}

I can't start the SD. Systemd shows:

# systemctl status bareos-sd.service
● bareos-sd.service - Bareos Storage Daemon service
   Loaded: loaded (/usr/lib/systemd/system/bareos-sd.service; enabled; 
vendor preset: disabled)
   Active: failed (Result: exit-code) since Wed 2020-12-23 09:20:53 CET; 
8min ago
 Docs: man:bareos-sd(8)
  Process: 23805 ExecStart=/usr/sbin/bareos-sd (code=exited, 
status=0/SUCCESS)
 Main PID: 23806 (code=exited, status=1/FAILURE)

bareos-sd.service: Service RestartSec=100ms expired, scheduling restart.
bareos-sd.service: Scheduled restart job, restart counter is at 5.
Stopped Bareos Storage Daemon service.
bareos-sd.service: Start request repeated too quickly.
bareos-sd.service: Failed with result 'exit-code'.
Failed to start Bareos Storage Daemon service.

What I'm doing wrong for setting up a single LTO drive?

Thanks, all the best, Frank

-- 
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/d77b662e-035b-4f86-bf68-cfcf5aa0431an%40googlegroups.com.

[bareos-users] Error of SD, trying to use a single tape drive

2020-12-23 Thread &#x27;Frank Cherry&#x27; via bareos-users 

Hello there,
I would like to use a single tape drive. Config:

/etc/bareos/bareos-sd.d/storage/tape-sd.conf:
Storage {
Name = Tape
Device = LTO7-Tape-Drive
Maximum Concurrent Jobs = 1
Media Type = Tape
Autochanger = no
}

/etc/bareos/bareos-sd.d/device/TapeStorage:
Device {
Name = LTO7-Tape-Drive
Drive Index = 0
Media Type = Tape
Archive Device = /dev/st0
LabelMedia = yes;
AutomaticMount = yes;
RemovableMedia = yes;
AlwaysOpen = no;
RandomAccess = no;
Spool Directory = /backup_spool/spool
Maximum Concurrent Jobs = 1
}

Staarting SD, I get the error:

bareos-sd[13632]: bareos-sd: ERROR TERMINATION at 
lib/parse_conf_state_machine.cc:158
bareos-sd[13632]: Config error: Keyword "Device" not permitted in this 
resource.
bareos-sd[13632]: Perhaps you left the trailing brace off of the previous 
resource.
bareos-sd[13632]: : line 6, col 7 of file 
/etc/bareos/bareos-sd.d/storage/tape-sd.conf
bareos-sd[13632]: Device = LTO7-Tape-Drive

Bareos Version 19.2.7-2

What I doing wrong please?
Thanks for any help,
Frank

-- 
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/4089a039-e4da-4b79-b4c0-832153724433n%40googlegroups.com.

[bareos-users] some newbie questions

2020-12-22 Thread &#x27;Frank Cherry&#x27; via bareos-users 

Hello there,
I'm Frank, changing from Bacula to Bareos because didn't get it running.

Now Bareos is working well after installation, the test backup and restore 
of /usr/sbin was successful with "file" as storage on a dedicated hard disk.

Now my goal is the following scenario:

1. using the Quantum Ultrium LTO-7 tape drive:
- I can read an write to tape, using the devices /dev/st0 or /dev/nst0 or 
/tape
Have add in /etc/bareos/bareos-sd/device a file with this content:

Device {
  Name = TapeStorage
  Media Type = LTO-7
  Archive Device = /dev/st0
  LabelMedia = no;   # lets Bareos label unlabeled media
  Random Access = no;
  AutomaticMount = yes;   # when device opened, read it
  RemovableMedia = yes;
  AlwaysOpen = yes;
  Description = "LTO 7 Tape."
}

With this file, bareos SD daemon won't start.
What's wrong?

2. My backup plan is, to collect the data from several servers by NFS / 
GulsterFS connection, store it on a dedicated local disk on the Bareos 
server and than stream it to the tape inside the bareos server too. Can 
anyone give me please some hints, which configuration steps I have to do 
for this scenario? 

Thans for any help, Frank

-- 
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/e53797d1-7bbd-48a5-a1bc-debb6991450fn%40googlegroups.com.