[bareos-users] When should Consolidate run? After the catalog backup?

2021-12-29 Thread wizh...@gmail.com
I would guess that consolidation should run after the catalog backup when 
all else is done.

Does this make sense or should it happen before?

-- 
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/399d57e2-f0c4-4cc2-ab7f-5e04fab6ac87n%40googlegroups.com.


[bareos-users] Re: Community packages repository for version 22

2023-05-09 Thread wizh...@gmail.com
Ran into this too.

"Designed for testing and home environments "  and  "not for production" 
are unfortunate. Home use is not considered production I guess, we need to 
avoid it for any real backup use at all now.

Sounds like they are on the same path as bacula, which is why I switched to 
bareos in the first place.

On Tuesday, May 9, 2023 at 2:51:53 a.m. UTC-4 Willem Basson wrote:

> I think we are both out of luck. 
> https://www.bareos.com/bareos-release-policy/ explains the what the 
> community repos will have from now on.
>
> On Monday, May 8, 2023 at 8:21:11 PM UTC+2 Willem Basson wrote:
>
>> Some clarity about the future of the community repos will actually be 
>> very much appreciated.
>> release/21 recently disappeared, and we had to switch to 
>> https://download.bareos.org/release-old-deleteme/21/Debian_11
>> Turns out that was short lived, and release-old-deleteme was... you 
>> guessed it. Deleted.
>> If we aren't ready for bareos version 22, is our only viable option to 
>> build debian packages ourselves?
>>
>> On Wednesday, March 15, 2023 at 10:38:24 AM UTC+2 Łukasz Szczepanik wrote:
>>
>>> Hi,
>>>
>>> From Bareos 22 version something has changed with packages repository 
>>> location for community repo. The newest community version  points to 
>>> "current" location instead of "release/22" like for subscription repository.
>>>
>>> I see a problem with this approach. My Bareos config is fully managed by 
>>> Puppet. If I point repository path to "current" my Bareos config could be 
>>> upgraded automatically without my knowledge if Bareos will release new 
>>> version eg. 23. I want to avoid such situation.
>>>
>>> Is there any chance that Bareos 22 version and next ones will be located 
>>> in 'release/'  in community repo ?
>>>
>>> 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/092efe97-c81c-4329-8d30-7261155ab05dn%40googlegroups.com.


[bareos-users] Restore catalog from bootstrap

2023-09-22 Thread wizh...@gmail.com
I have followed the documentation and cannot get past the restore command 
requiring a jobid

The docs state

" After re-initializing the database, you should be able to run Bareos. If 
you now try to use the restore command, it will not work because the 
database will be empty. However, you can manually run a restore job and 
specify your bootstrap file. You do so by entering the run command in the 
console and selecting the restore job. If you are using the default Bareos 
Director configuration, this Job will be named RestoreFiles. Most likely it 
will prompt you with something such as:"

So o run in bconsole

run

then selec 14 for RestoreFiles

It then requires a jobid to continue but there are non yet in the database 
as I am trying to get the catalog using a bootstrap file.

What am I missing?





-- 
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/80215214-5214-45dd-998e-946a417eee44n%40googlegroups.com.


[bareos-users] bareos-sd device count usage

2023-09-26 Thread wizh...@gmail.com
I see the sd now has a "Count" parameter that looks handy for multiple 
devices.

in the director I see no similar way to specify these devices except to 
list out manually like in the example

https://docs.bareos.org/TasksAndConcepts/VolumeManagement.html#example-use-four-storage-devices-pointing-to-the-same-directory

Would be nice if the sd config a a similar directive to not have to list 
all the auto generated devices.

Perhaps I am missing something and it already does?

-- 
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/c7358d8a-25f6-4b23-9871-b32b538efec5n%40googlegroups.com.


[bareos-users] Re: bareos-sd device count usage

2023-09-27 Thread wizh...@gmail.com
I saw the autochanger, but that does not allow for parallel jobs correct?

Currently to have parallel jobs you have to define multiple devices and 
specify them all in both the sd and dir.

using count simplifies the sd config, but the director with needs each 
listed.

On Wednesday, September 27, 2023 at 4:55:39 a.m. UTC-4 Bruno Friedmann 
(bruno-at-bareos) wrote:

> The trick is to use a virtual autochanger for those kind of device, so 
> only the changer is declared on the director.
>
> If you want to get inspired, you can have a look at the following PR which 
> will propose to introduce this 
> https://github.com/bareos/bareos/pull/1467
>
>
> Le mardi 26 septembre 2023 à 15:25:48 UTC+2, wizh...@gmail.com a écrit :
>
>> I see the sd now has a "Count" parameter that looks handy for multiple 
>> devices.
>>
>> in the director I see no similar way to specify these devices except to 
>> list out manually like in the example
>>
>>
>> https://docs.bareos.org/TasksAndConcepts/VolumeManagement.html#example-use-four-storage-devices-pointing-to-the-same-directory
>>
>> Would be nice if the sd config a a similar directive to not have to list 
>> all the auto generated devices.
>>
>> Perhaps I am missing something and it already does?
>
>

-- 
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/cc6ba5a7-4da1-4c7e-88a3-73a2b73cbc42n%40googlegroups.com.


[bareos-users] Re: bareos-sd device count usage

2023-09-27 Thread wizh...@gmail.com
I believe you are saying what i was saying.

With X number of devices in an autochanger then up to X number of jobs can 
run at the same time.  Perfect.

On Wednesday, September 27, 2023 at 9:43:42 a.m. UTC-4 Bruno Friedmann 
(bruno-at-bareos) wrote:

> Well not really, I've implemented that with 4 devices in my autochanger 
> which mean I can run 4 concurrents writes job or 2 read / 2 write for 
> copy/AI etc.
> and I have one storage definition on my director.
> Of course that mean I will write 4 distinct volumes at the same time. and 
> not 4 jobs on a volume. 
> Le mercredi 27 septembre 2023 à 14:49:28 UTC+2, wizh...@gmail.com a 
> écrit :
>
>> I saw the autochanger, but that does not allow for parallel jobs correct?
>>
>> Currently to have parallel jobs you have to define multiple devices and 
>> specify them all in both the sd and dir.
>>
>> using count simplifies the sd config, but the director with needs each 
>> listed.
>>
>> On Wednesday, September 27, 2023 at 4:55:39 a.m. UTC-4 Bruno Friedmann 
>> (bruno-at-bareos) wrote:
>>
>>> The trick is to use a virtual autochanger for those kind of device, so 
>>> only the changer is declared on the director.
>>>
>>> If you want to get inspired, you can have a look at the following PR 
>>> which will propose to introduce this 
>>> https://github.com/bareos/bareos/pull/1467
>>>
>>>
>>> Le mardi 26 septembre 2023 à 15:25:48 UTC+2, wizh...@gmail.com a écrit :
>>>
>>>> I see the sd now has a "Count" parameter that looks handy for multiple 
>>>> devices.
>>>>
>>>> in the director I see no similar way to specify these devices except to 
>>>> list out manually like in the example
>>>>
>>>>
>>>> https://docs.bareos.org/TasksAndConcepts/VolumeManagement.html#example-use-four-storage-devices-pointing-to-the-same-directory
>>>>
>>>> Would be nice if the sd config a a similar directive to not have to 
>>>> list all the auto generated devices.
>>>>
>>>> Perhaps I am missing something and it already does?
>>>
>>>

-- 
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/3f5dfd5d-08fb-4d52-9751-361177de869bn%40googlegroups.com.


[bareos-users] Re: bareos-sd device count usage

2023-09-28 Thread wizh...@gmail.com
Thank you for clarifying, this is a welcome configuration simplification.

On Thursday, September 28, 2023 at 5:41:27 a.m. UTC-4 Maksim Pratasevich 
wrote:

> *storage daemon*
>
> *1. Create device config*
>
> Device {
>   Name = device-sd
>   Media Type = File
>   Archive Device = /srv/backup/device
>   Count = 4
>   Label Media = yes
>   AutomaticMount = yes
>   RemovableMedia = no
>   AlwaysOpen = no
>   RandomAccess = yes
>   Maximum Concurrent Jobs = 1
> }
>
> 2. create autochanger config
>
> Autochanger {
>   Name =  autochanger-ac
>   Device = device-sd *## YOUR DEVICE HERE*
>   Changer Device = /dev/null
>   Changer Command = ""
> }
>
> director config
> 3. create storage config
>
> Storage {
>   Name = storage-st
>   Address = ...
>   Password = ...
>   Device = autochanger-ac* ##autochanger here*
>   Auto changer = yes
>   Media Type = File
>   Maximum Concurrent Jobs = 4
> }
>
> 4. and finally create job configs
>
> Job {
>   Name = job1-jb
> ...
>   Storage  =  storage-st *##storage here*
> ... 
> }
>
> Job {
>   Name = job2-jb
> ...
>   Storage  =  storage-st  *##storage here*
> ...
> }
>
> I have 30 jobs set up like this, 4 running simultaneously
> среда, 27 сентября 2023 г. в 15:46:46 UTC+2, wizh...@gmail.com: 
>
>> I believe you are saying what i was saying.
>>
>> With X number of devices in an autochanger then up to X number of jobs 
>> can run at the same time.  Perfect.
>>
>> On Wednesday, September 27, 2023 at 9:43:42 a.m. UTC-4 Bruno Friedmann 
>> (bruno-at-bareos) wrote:
>>
>>> Well not really, I've implemented that with 4 devices in my autochanger 
>>> which mean I can run 4 concurrents writes job or 2 read / 2 write for 
>>> copy/AI etc.
>>> and I have one storage definition on my director.
>>> Of course that mean I will write 4 distinct volumes at the same time. 
>>> and not 4 jobs on a volume. 
>>> Le mercredi 27 septembre 2023 à 14:49:28 UTC+2, wizh...@gmail.com a 
>>> écrit :
>>>
>>>> I saw the autochanger, but that does not allow for parallel jobs 
>>>> correct?
>>>>
>>>> Currently to have parallel jobs you have to define multiple devices and 
>>>> specify them all in both the sd and dir.
>>>>
>>>> using count simplifies the sd config, but the director with needs each 
>>>> listed.
>>>>
>>>> On Wednesday, September 27, 2023 at 4:55:39 a.m. UTC-4 Bruno Friedmann 
>>>> (bruno-at-bareos) wrote:
>>>>
>>>>> The trick is to use a virtual autochanger for those kind of device, so 
>>>>> only the changer is declared on the director.
>>>>>
>>>>> If you want to get inspired, you can have a look at the following PR 
>>>>> which will propose to introduce this 
>>>>> https://github.com/bareos/bareos/pull/1467
>>>>>
>>>>>
>>>>> Le mardi 26 septembre 2023 à 15:25:48 UTC+2, wizh...@gmail.com a 
>>>>> écrit :
>>>>>
>>>>>> I see the sd now has a "Count" parameter that looks handy for 
>>>>>> multiple devices.
>>>>>>
>>>>>> in the director I see no similar way to specify these devices except 
>>>>>> to list out manually like in the example
>>>>>>
>>>>>>
>>>>>> https://docs.bareos.org/TasksAndConcepts/VolumeManagement.html#example-use-four-storage-devices-pointing-to-the-same-directory
>>>>>>
>>>>>> Would be nice if the sd config a a similar directive to not have to 
>>>>>> list all the auto generated devices.
>>>>>>
>>>>>> Perhaps I am missing something and it already does?
>>>>>
>>>>>

-- 
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/b95bfe2c-b8d3-4bb1-b128-34108ec8c38fn%40googlegroups.com.


Re: [bareos-users] bextract failing trying to restore catalog

2025-01-22 Thread wizh...@gmail.com
Correct I am using encryption.  If you cannot use bextract on encrypted 
volumes how are you supose to recover them?

I have tried this for example

bscan -v -b /tmp/bootstrap.bsr -m -s FileStorage-0001

I get error that it cannot update the media record., but it inserts the 
files an job.  I can't restore in my tests from that as it complains there 
is not volume

bscan: stored/butil.cc:305-0 Using device: "FileStorage-0001" for reading.
22-Jan 13:31 bscan JobId 0: Ready to read from volume "Full-0001" on device 
"FileStorage-0001" (/var/lib/bareos/storage/file).
bscan: stored/bscan.cc:322-0 Using Database: bareos, User: bareos
22-Jan 13:31 bscan JobId 0: Forward spacing Volume "Full-0001" to 
file:block 0:163006.
bscan: stored/bscan.cc:601-0 SOS_LABEL: Found Job record for JobId: 1
bscan: stored/bscan.cc:1173-0 Fileset "Catalog" already exists.
bscan: stored/bscan.cc:1289-0 Updated Job termination record for JobId=1 
Level=Full TermStat=T
22-Jan 13:31 bscan JobId 0: End of Volume at file 0 on device 
"FileStorage-0001" (/var/lib/bareos/storage/file), Volume "Full-0001"
bscan (0): stored/bscan.cc:363-0 == JobId=0 
bscan: stored/bscan.cc:1101-0 Could not update media record. ERR=
22-Jan 13:31 bscan JobId 0: End of all volumes.
bscan: stored/bscan.cc:1101-0 Could not update media record. ERR=
bscan: stored/bscan.cc:735-0 End of all Volumes. VolFiles=0 VolBlocks=0 
VolBytes=162,902
Records added or updated in the catalog:
  0 Media
  0 Pool
  1 Job
121 File
  0 RestoreObject
22-Jan 13:31 bscan JobId 0: Releasing device "FileStorage-0001" 
(/var/lib/bareos/storage/file).



Unable to get Job Volume Parameters. ERR=cats/sql_get.cc:408 No volumes 
found for JobId=1 Unable to construct a valid BootStrapRecord. Cannot 
continue.

On Wednesday, January 22, 2025 at 1:25:37 a.m. UTC-5 Sebastian Sura wrote:

> Hello wizhippo,
>
> Is it possible that you backed up your data with encryption turned on ? 
> `stream=32` is supposed to be `STREAM_ENCRYPTED_FILE_COMPRESSED_DATA`.
> I think bextract does not currently support extracting encrypted data.  
> Feel free to open an issue about it here: 
> https://github.com/bareos/bareos/issues
>
> Best Regards
> Sebastian Sura
> Am 21.01.25 um 23:14 schrieb wizh...@gmail.com:
>
> I run the following
>
> bextract -b ~/bootstrap.bsr FileStorage-0001 /tmp/
>
> I get theses errors and the sql file is empty
>
> bextract: stored/butil.cc:305-0 Using device: "FileStorage-0001" for 
> reading.
> 21-Jan 22:12 bextract JobId 0: Ready to read from volume "Full-0002" on 
> device "FileStorage-0001" (/var/lib/bareos/storage/file).
> 21-Jan 22:12 bextract JobId 0: Forward spacing Volume "Full-0002" to 
> file:block 0:208.
> bextract JobId 0: -rw-r--r--   1 bareos   bareos  18565666 2025-01-21 
> 22:07:00  /tmp//var/lib/bareos/bareos.sql
> 21-Jan 22:12 bextract JobId 0: Error: Unknown stream=32 ignored. This 
> shouldn't happen!
> 21-Jan 22:12 bextract JobId 0: Error: Unknown stream=32 ignored. This 
> shouldn't happen!
> 21-Jan 22:12 bextract JobId 0: Error: Unknown stream=32 ignored. This 
> shouldn't happen!
> 21-Jan 22:12 bextract JobId 0: Error: Unknown stream=32 ignored. This 
> shouldn't happen!
> 21-Jan 22:12 bextract JobId 0: Error: Unknown stream=32 ignored. This 
> shouldn't happen!
>
> Any ideas why that would be?
>
> Using bareos-dir Version: 24.0.1~pre19.3e3a7a6a2 (08 January 2025) Ubuntu 
> 24.04.1 LTS -- 
> 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 visit 
> https://groups.google.com/d/msgid/bareos-users/3983e9b0-e8b9-4a89-807e-0dc6c61730a8n%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/bareos-users/3983e9b0-e8b9-4a89-807e-0dc6c61730a8n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
> -- 
>  Sebastian Sura  sebasti...@bareos.com
>  Bareos GmbH & Co. KGPhone: +49 221 630693-0
>  https://www.bareos.com
>  Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
>  Komplementär: Bareos Verwaltungs-GmbH
>  Geschäftsführer: Stephan Dühr, Jörg Steffens, Philipp Storz
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to bareos-users+unsubscr...@googlegroups.com.
To view this discussion visit 
https://groups.google.com/d/msgid/bareos-users/0318f5f8-c7b0-48e6-bbd5-8312925aa216n%40googlegroups.com.


[bareos-users] Bareos restore catalog instructions missing bootstrap menu?

2025-01-22 Thread wizh...@gmail.com
If trying to restore according 
to https://docs.bareos.org/Appendix/Troubleshooting.html#section-restorecatalog 
note the RestoreFiles job does not give the option to specify a boostrap 
file.  You can add top the config a Bootstrap = /tmp/restore.bsr or create 
another job config to do this.

Was there are some point a menu option to do so?

-- 
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 visit 
https://groups.google.com/d/msgid/bareos-users/206f8655-456b-4a09-8dd4-b629c9251f7fn%40googlegroups.com.


[bareos-users] bextract failing trying to restore catalog

2025-01-21 Thread wizh...@gmail.com
I run the following

bextract -b ~/bootstrap.bsr FileStorage-0001 /tmp/

I get theses errors and the sql file is empty

bextract: stored/butil.cc:305-0 Using device: "FileStorage-0001" for 
reading.
21-Jan 22:12 bextract JobId 0: Ready to read from volume "Full-0002" on 
device "FileStorage-0001" (/var/lib/bareos/storage/file).
21-Jan 22:12 bextract JobId 0: Forward spacing Volume "Full-0002" to 
file:block 0:208.
bextract JobId 0: -rw-r--r--   1 bareos   bareos  18565666 2025-01-21 
22:07:00  /tmp//var/lib/bareos/bareos.sql
21-Jan 22:12 bextract JobId 0: Error: Unknown stream=32 ignored. This 
shouldn't happen!
21-Jan 22:12 bextract JobId 0: Error: Unknown stream=32 ignored. This 
shouldn't happen!
21-Jan 22:12 bextract JobId 0: Error: Unknown stream=32 ignored. This 
shouldn't happen!
21-Jan 22:12 bextract JobId 0: Error: Unknown stream=32 ignored. This 
shouldn't happen!
21-Jan 22:12 bextract JobId 0: Error: Unknown stream=32 ignored. This 
shouldn't happen!

Any ideas why that would be?

Using bareos-dir Version: 24.0.1~pre19.3e3a7a6a2 (08 January 2025) Ubuntu 
24.04.1 LTS

-- 
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 visit 
https://groups.google.com/d/msgid/bareos-users/3983e9b0-e8b9-4a89-807e-0dc6c61730a8n%40googlegroups.com.


[bareos-users] bsmtp strips first newline?

2025-03-11 Thread wizh...@gmail.com
Given the following file

# 10-Mar-2025 22:44:02 - BackupCatalog.2025-03-10_21.10.00_20 - Full
Volume="Full-0387"
MediaType="File"
VolSessionId=196
VolSessionTime=1740423781
VolAddr=211-615837750
FileIndex=1-124

If you pipe it to bsmtp the first newline is strip in the email body 
resulting in

# 10-Mar-2025 22:44:02 - BackupCatalog.2025-03-10_21.10.00_20 - Full 
Volume="Full-0387"
MediaType="File"
VolSessionId=196
VolSessionTime=1740423781
VolAddr=211-615837750
FileIndex=1-124

Is this expected? Seams odd to modify the input at all.

I have a script that uses tee to send the bootstrap to both a file and 
bsmtp and they contents do not match. 

I can manually correct if I ever need the emailed bootstrap but it feels 
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 visit 
https://groups.google.com/d/msgid/bareos-users/bf9c6037-165a-4e5d-9277-f877409b9adfn%40googlegroups.com.