Feature Request: Job Bundle

[Poweruser]

Whats a Job Bundle?

Its a group of jobs, which belong together.
So you can setup jobs and run them standalone OR you can just run the bundle (manual or by schedule).

A bundle can be: Normal job + tape job
or: normal job + veeam db backup job + tape job for all

also bundles should make it easier to define which data is written to a tape.
so if you setup the tape job you should be able to mark by checkbox which other jobs should be written to tape.

[PTide]

<...>OR you can just run the bundle

Could you provide some use cases when doing so would be beneficial compared to the current approach, please?

so if you setup the tape job you should be able to mark by checkbox which other jobs should be written to tape

I'm not quite sure that I get the idea, but I guess that is achievable with the current Tape job design.

Thanks

[Poweruser]

I got one hyper-v job to repo
one for above repo to tape
and one for file (config backup) to tape
and one for config backup to repo

i cant make them be execute from one start time. i need to setup 1 for config 1 for file to tape 1 for hyper-v to repo and i set repo to tape after hyper-v to repo.
thats a bit confusing.

would be easier if i have a job batch, where i can add many jobs.
tell them in which order or which one can be executed parallel.
like a critical project path.
then it is executed until done.

especially this batch of jobs checks, that all data prepared in the jobs before may be writte in one session to the tape.

also config backup is not well included.

another problem is, that its confusing to keep all the times in mind.
so it would be easier to "group" them
so adding some jobs works a bit, but not that nice, also the starting time is not defined by a criticial path or after all previous jobs has been done.
just by the default 3 hour timeout or a start time.

[PTide]

I cant make them be execute from one start time. i need to setup 1 for config 1 for file to tape 1 for hyper-v to repo and i set repo to tape after hyper-v to repo.
thats a bit confusing.

Do you run your config backup job as often as you run your backup and tape jobs?

Regarding backup and tape jobs - you can chain them so they start one after another. Anyway you cannot run them in parallel as the tape job will still have to wait until the source job is finished. That is, bundling won't change that.

Thanks

[Poweruser]

Yes is run them the same time or prefer to run them after the job so i got the whole state. it does not cost time so why not keep it up2date?
I can chain hyper-v job and next the first tape job. but i cant chain the second tape job for file2tape config backup nor cant i chain the config backup creation process.
veeam allows me to chain only 2 jobs together. :(