Feature Request: One Time Schedule

[shaun.binkley]

Scenario:
Backup job fails because technician Bob migrated a VMware virtual machine and didn't remember to update the Veeam backup job. The next morning, technician Clive sees the failure and reactively changes the backup job to the virtual machines new location. However, Clive can't re-run the backup job during the day as it is a critical machine. The schedule is set to backup the virtual machine once a week, the next being in 6 days. Technician Clive can change the schedule so that the backup runs tonight, the next day he will have to change it back to the old schedule. Alternatively, Clive can stay up late that night and manually retry the job.

Clive's life could be made easier if there was a 'One-time schedule' option or similar in the Veeam Backup and Replication console. That way, Clive doesn't have to modify the existing schedule and change it back after the backup completes. Clive can just ask the backup job to run that evening too.

Great product, keep up the good work

Shaun

[Dima P.]

Hello shaun.binkley.

You can perform quick backup of desired virtual machine. It's even possible to script one time quick backup via PowerShell via Start-VBRQuickBackup. Will that work for your case? Thanks.

[shaun.binkley]

That's very cool that you can run a quick backup of a virtual machine and it automatically adds it to the bakup chain of it's existing job!

Yeah, ultimately it would work in our case, we could probably create a powershell command and schedule it to run at a later time. It's not quite as slick as having a button on a right click menu though.

[veremin]

Be aware that quick backup won't help, if backup job previously hasn't processed this VM at least once; which seems to be the case. Thanks.

[nezzer]

Hey!

Maybe Mr Clive should try to create his jobs with vmtags instead. They should follow a migrated VM. Using automatic backup proxy should allocate the correct proxy even after migration and wollah backup is taken.

[veremin]

I think usage of dynamic containers such as resource pool, folder or tag won't necessarily help here. Even if VM were migrated to a different job automatically, you would still need to wait 6 days before the next job cycle (as is in OP's example). Thanks.

[Ollo]

For our company, a onetime fullbackup after adding the vm to a job is not a "nice to have" feature, it is a "must have" one. We can't do an active full for a job with 200 VMs includes daytimes.

After changing to Veeam, I still wondering why this doesn't work. In other backup solutions it is "standard".
Please discuss this with the development.

Thanks

[Dima P.]

Hi Ollo.

Thank you for sharing your thoughts. Should it be controlled process or you would like full backup to be created automatically after you assign VM to a backup job?

[Gostev]

For our company, a onetime fullbackup after adding the vm to a job is not a "nice to have" feature, it is a "must have" one. We can't do an active full for a job with 200 VMs includes daytimes.

When you add the VM to a job, it's first backup will be an active full backup regardless, so I am not sure what are we missing here?

[Ollo]

p.e. we have a job, that only runs one times per month.
In this case, we have to wait 30days before the first backup runs.

Or you have a deloyment of a VM. The last step is a fullbackup, because this is point where you can recover to.
Now, we have to tell the requester to wait until tomorrow to begin to work on the VM, because we have no restore point. The job only runs onetimes at night.

It is not possible that you change the routine "Quick backup" to check if it is a new VM or an old? new=fullbackup, old=incremental