Automatic Retry & Start

[uxmax]

Hello,

I schedule a few Veeam Proxy Server to reboot ona daily basis and
iam looking for an option to auto retry or start jobs aber a system reboot ?
I could not find anthing related within the gui.
I believe the only option is to confige a windows bash script to execute a ps script ?

Thanks

[Tobias_Elfstrom]

Why would you want to restart or start job when you reboot a proxy? Or do you want to restart job that has failed due to the proxy reboot?

[foggy]

Marcus, you could set your proxy servers reboots to occur at different time, that will allow you to rely on Veeam B&R built-in automatic job retries, since the overall job will continue to be executed on other proxies and only the failed tasks will be retried later.

[uxmax]

Why would you want to restart or start job when you reboot a proxy? Or do you want to restart job that has failed due to the proxy reboot?

Hi Tobias, i only want to make sure that all backups jobs continue / resume the backup job after a system reboot.

Actually we have to to that manually for each proxy server and each with 5-10 Jobs.

Marcus, you could set your proxy servers reboots to occur at different time, that will allow you to rely on Veeam B&R built-in automatic job retries, since the overall job will continue to be executed on other proxies and only the failed tasks will be retried later.

Hi Alex,

do you mean the built-in automatic job retries options which you can configure per job ?
Automatic Retry: 1) times of retry 2) time to wait (10 Min atm)

It seems that all jobs are not running after a reboot.

Thanks, marcus

[foggy]

Yes, I'm talking about these settings.

Do you have backup proxy selection set to automatic in your jobs? Do you reboot all proxy servers simultaneously?

[uxmax]

Some have automatic settings, some are binded to a specific IP. I dont need to reboot all servers at the same time but i have to reboot the Veeam Server's as well (where all Jobs are configured).

[foggy]

but i have to reboot the Veeam Server's as well (where all Jobs are configured).

That explains. Rebooting the backup server during jobs execution is not considered the best practice (affects Veeam database as well). Can you carry those events over in time somehow?

[Tobias_Elfstrom]

Ah.
In case you cant get around your reboot window of the backup server I suggest you handle thos cases with a simple powershell script along the lines of this:

Code: Select all

Add-PSSnapin VMware.VimAutomation.Core 
$Jobs = Get-VBRJob
foreach ($Job in $Jobs){
            if (($Job.GetLastResult()) -eq "Failed") {
                if ($Job.JobType -eq "Backup") {
                    Start-VBRJob -job $job -RetryBackup -RunAsync
                }
            }

[Vitaliy S.]

I would strongly suggest to find a way NOT to reboot your backup management server during job runs, as it can affect the consistency of Veeam configuration database.

[veremin]

Also, if I were to stick with the "script" scenario, I’d modify the proposed script a little bit, so that, it would restart only backup jobs that failed within last 24 hours:

Code: Select all

Asnp VeeamPssnapin
$Jobs = Get-VBRJob | where {($_.jobtype -eq "Backup") -and (((Get-Date) - ($_.info.ScheduleOptions.LatestRun)).totalhours -le "24")}
foreach ($Job in $Jobs)
{
            if (($Job.GetLastResult()) -eq "Failed") {
                if ($Job.JobType -eq "Backup") {
                    Start-VBRJob -job $job -RetryBackup -RunAsync
                }
            }
}

Nevertheless, the preferable way is to not restart Veeam management server during backup/replication activities.

Thanks.

[uxmax]

I would strongly suggest to find a way NOT to reboot your backup management server during job runs, as it can affect the consistency of Veeam configuration database.

Good point!

So what about stopping all jobs, rebooting the vm and to retry the jobs?

[Vitaliy S.]

Yes, that would be a better idea. Out of curiosity, why do you need to reboot your servers every day? What about rebooting this server as a post-backup job script which will be specified in the configuration of your last job? As an alternative, you can use this solution to check the status of your jobs, and once all jobs are complete trigger the reboot script.