Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FR] Specify Bacula jobid in confi #717

Closed
hazcod opened this issue Nov 26, 2015 · 6 comments
Closed

[FR] Specify Bacula jobid in confi #717

hazcod opened this issue Nov 26, 2015 · 6 comments
Labels
enhancement Adaptions and new features needs sponsorship This issue will not get solved on a voluntary base by ReaR upstream. support / question

Comments

@hazcod
Copy link
Contributor

hazcod commented Nov 26, 2015

Currently, the config allows us to specify the volume on beforehand but not the jobid.
(this is possible too in bootstrap.txt of bextract)

It would be good if we could specify the JobId too in the configuration file, so an almost-automatic disaster recovery CD can be built.

@hazcod hazcod changed the title [FR] Specify Bacula JobId in config [FR] Specify Bacula jobid in confi Nov 26, 2015
@gdha
Copy link
Member

gdha commented Nov 26, 2015

@hazcod Dag and Jeroen wrote the Bacula integration, but they are not active currently within the rear project. So, no clue who could assist you with the feature request?

@gdha
Copy link
Member

gdha commented Feb 19, 2016

@hazcod Could you explain with an example?

@hazcod
Copy link
Contributor Author

hazcod commented Feb 19, 2016

@gdha As far as I know, when booting the recovery CD for bacula, you need to select the jobid. If we could include that in our config too, users could just insert the CD and it would recover automatically.
( no user-driven decisions needed )

Jobids here are ids of the backup jobs done by bacula, e.g.:
001 today at 12:00
002 today at 13:00
003 todat at 14:00

So if I want to generate a disaster recovery ISO for the latest backup, I would just fill in the last known JobId (003) in the config file and generate the ISO.

@gdha gdha added the enhancement Adaptions and new features label Feb 19, 2016
@gdha
Copy link
Member

gdha commented Feb 19, 2016

@hazcod sounds indeed interesting to keep. Are you able to prepare a pull request for this?

@hazcod
Copy link
Contributor Author

hazcod commented Feb 19, 2016

Not at the moment as i'm currently not using rear in my situation, I'm afraid

@jsmeix jsmeix added the needs sponsorship This issue will not get solved on a voluntary base by ReaR upstream. label Sep 28, 2016
@jsmeix
Copy link
Member

jsmeix commented Sep 28, 2016

I neither use Bacula nor Bareos but according to what I read in
#997
there is meanwhile support for a variable
named BAREOS_RESTORE_JOB
which seems to be support for a Bareos job ID.

According to
https://www.bareos.org/en/
"Bareos is a ... fork of the backup project from bacula.org"
which indicates that support for a Bacula job ID
could be implemented in a similar way.

But #717 (comment)
indicates that at least for now this will not be implemented
so that I close this issue now.

If needed it could be reopened but preferably
a new issue based on a current rear version
should be submitted.

@jsmeix jsmeix closed this as completed Sep 28, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Adaptions and new features needs sponsorship This issue will not get solved on a voluntary base by ReaR upstream. support / question
Projects
None yet
Development

No branches or pull requests

3 participants