[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 emai

[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

[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 ma

[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-

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

2023-09-27 Thread wizh...@gmail.com
se 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

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

2023-09-27 Thread wizh...@gmail.com
; 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 th

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

2023-09-28 Thread wizh...@gmail.com
b { > 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. >

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

2025-01-22 Thread wizh...@gmail.com
`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: &

[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

[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" (

[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 #