Skip to main content

 

I have some jobs that aren't running automatically. Nothing unusual has happened. We just checked the proxies. We have VMware and general proxies. We assigned both, and nothing. Any help would be appreciated. I'll wait before opening a support case. 

 

If you are referring to the <Not scheduled> ones they will not run automatically as those are manual - you need to schedule them like the other jobs.


Hi ​@Fvinas -

Are your jobs configured to run automatically? Never heard of that behavior. Verify in the Job settings based on the link below:

https://helpcenter.veeam.com/docs/backup/vsphere/backup_job_schedule_vm.html?ver=120

Best.


I'm not referring to unscheduled tasks, but to active tasks, which, as shown, haven't been running for a day or two. I've restarted the services and even updated the OS, then restarted several times, and the tasks still aren't running automatically.

 


I have tried changing the proxy settings and it doesn't work either,

 

 


Hi ​@Fvinas 

as Microsoft teaches have you tried restartng VBR Server? 

So… jokes aside (but not really)… Your informations are very poor to understand your issue. So please get more details about your environment and check in “Backup Infrastructure” - Backup Proxies if there are some of it in Offline mode. 

 


if the proxies are online.
As for the proxies, I had them as VMware Proxies and I set them to General so I wouldn't see the other type. At the same time, as I said, I've already tried several methods.

 


That happened to me a number of years ago.  I’m afraid I don’t recall the exact resolution, but have you tried manually kicking off one of the jobs that was supposed to run but didn’t?  Also try editing the schedule of one of the jobs so that it get resaved.  Finally, have you tried creating a new job with a schedule and see if that one runs?


If I changed several tasks at the time of execution and it didn't work either, the strange thing is if you look at the image I have several tasks that do execute and others don't.
 

 


and I have also run it manually, even though when I run it manually I break the backup chain

Running a backup manually shouldn’t break the chain, it just adds an additional point.  Have you restarted the proxy servers?  Checked disk space on the VBR and proxies?  Is it a local DB or a separate server?  Have you confirmed that the DB is online when the jobs should run?


Yes, equally, I've checked everything, the space, the database on the same server is online. I've restarted the proxies.

You haven’t answered about what happens when you create a new job.  Also try cloning one of the existing jobs to see if the clone runs.


Welp ​@Fvinas ..at this point, it’s best you reach out to Veeam Support. As you do, you can maybe look at the Backup Job logs at: C:\ProgramData\Veeam\Backup & Replication\<job-name>.log and see if anything in there shows.

Keep us posted what Support says.

Best.


Yes also, I made a new job and it didn't run either.

 I'll wait before opening a support case. 

 

I wouldn’t recommend waiting. You can submit a case first, and while you wait for an official response from Veeam support, someone might come up with an answer here.


Check if any Veeam services are in stopped status or failing to run. If you have a service account to run those services, perhaps the account’s password expired or got changed. 


 


 


all services run this way.

 


How is your Tape Infrastructure? Looks like Backup_Plazafs001_FS is backup to tape job. Another job is supposed to run after that. Is the Backup_Plazafs001_FS job still running? Sometimes Veeam needs new tapes added to the tape library, tape drive starts cleaning etc., and it waits for your action.


Perdon por la demor. no mis trabajos de cinta estan bien, lo que succede es que las tareas no se ejecutan automaticamente. acutalmente tengo un caso con veeam, y no hemos llegado a nada aun.


Comment