Comprehensive data protection for all workloads
Post Reply
AlexWeit
Influencer
Posts: 18
Liked: never
Joined: Apr 04, 2018 9:49 am
Full Name: Alexander Weit
Contact:

Backup without Job

Post by AlexWeit »

Hi,

is it planned to decouple the VMs from the jobs? In the event of an error, the entire job chain must always be regenerated.

BR
Alex
HannesK
Product Manager
Posts: 14322
Liked: 2890 times
Joined: Sep 01, 2014 11:46 am
Full Name: Hannes Kasparick
Location: Austria
Contact:

Re: Backup without Job

Post by HannesK »

Hello,
can you maybe explain what kind of "error" you mean and why you need to regenerate the chain (case numbers?)

I'm also not sure what you mean with "decouple". I mean, a Veeam backup file is completely standalone. Even without the full product, you can extract data with the extract tool. No VBR, no job, no database is needed for that.

Best regards,
Hannes
foggy
Veeam Software
Posts: 21073
Liked: 2115 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Backup without Job

Post by foggy »

Hi Alex, aren't you looking for something like the Quick Backup?
AlexWeit
Influencer
Posts: 18
Liked: never
Joined: Apr 04, 2018 9:49 am
Full Name: Alexander Weit
Contact:

Re: Backup without Job

Post by AlexWeit »

Hi Hannes,

Case #04455752

I mean it will be better if i can backup via policy an not via job. If i have a corrupt job, i must rebuild the Retention for all VMs.

BR
Alex
foggy
Veeam Software
Posts: 21073
Liked: 2115 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Backup without Job

Post by foggy »

What do you mean by a corrupt job?
AlexWeit
Influencer
Posts: 18
Liked: never
Joined: Apr 04, 2018 9:49 am
Full Name: Alexander Weit
Contact:

Re: Backup without Job

Post by AlexWeit »

We have Primary Jobs in Forewer-Forward-Increment-Mode. We migrated the VBR to a new server and previously canceled BC jobs that were not fast enough. The BC jobs had increments with the status incomplete and were only noticed after 30 days because the savepoints with the status were not merged into the full.
foggy
Veeam Software
Posts: 21073
Liked: 2115 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Backup without Job

Post by foggy »

I believe you could map the new job to the existing backups and continue the chain normally. Incomplete restore points would be finally merged and deleted according to retention (unless there's some sort of an issue).
AlexWeit
Influencer
Posts: 18
Liked: never
Joined: Apr 04, 2018 9:49 am
Full Name: Alexander Weit
Contact:

Re: Backup without Job

Post by AlexWeit »

Hi the idea with a new Job and mapping fails like the original-Job:
Failed to merge full backup file Error: Agent: Failed to process method {Transform.Patch}: There is an item with the specified name and another type.
Failed to generate points Error: Agent: Failed to process method {Transform.Patch}: There is an item with the specified name and another type.

I have a Retention with 30 days. In that Jobs we have some VMs (not all) where the Full is from 06.09. and the increment with state "Incomplete" from 07.09.... the chain grow and grow.
We stopped six BC Jobs and generade a new chains (with more than 60TB).

BR Alex
foggy
Veeam Software
Posts: 21073
Liked: 2115 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Backup without Job

Post by foggy »

Have you asked our engineers to take a closer look at this behavior? I would do so even though you've already started the new chains.
Post Reply

Who is online

Users browsing this forum: Bing [Bot] and 121 guests