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 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.

Hello, we already have the solution for this case. Details according to support.We understand that: DATABASE MAINTENANCE.· They have already performed controlled tests, disabling jobs and services, and uninstalling Sophos.· After restarting the server and waiting for the execution window, the jobs still do not start automatically, although they can be run manually (albeit slowly).· CPU, RAM, and disk resources show no evidence of bottlenecks during execution.Comments and Next Steps· Manual vs. Automatic Operation· The fact that the jobs run manually but do not start by schedule suggests a possible issue with the Veeam scheduling service or internal communication between services.So far, everything's working fine. Thanks for your help. See you later.

Att. F

· It may be related to the database, but also to components such as Veeam Backup Service or Veeam Backup Scheduler. (It is possible that the failure of these services that we saw in the Windows logs is related)

Slow execution, despite not detecting resource saturation, could be due to internal locks, pending sessions in the database, or even corruption in the indexes/tables that manage jobs and sessions. Abnormal shutdowns may have caused this corruption.

· It is important to review both the Veeam logs and the database status after restarts.· Uninstall Sophos· It is positive that Sophos has been uninstalled to rule out interference, but if the behavior persists, the focus should shift to the Veeam infrastructure and its database.· Recommended action: Database validation and maintenance· Even if the database allows access, there may be fragmentation, locks, or orphaned records that affect scheduling and performance.· We recommend running the official Veeam SQL maintenance script for the database, which helps to reindex and clean up old sessions:

1. Identify the SQL Instance and Database· Typically, the database is named VeeamBackup and is located on the local SQL Server instance of the Veeam server.2. Pre-Backup· Before making any changes, perform a full backup of the VeeamBackup database from SQL Server Management Studio (SSMS) or your usual method.3. Run the Maintenance Script· Veeam recommends running a maintenance script that:· Rebuilds fragmented indexes.· Updates statistics.· Cleans up old sessions and logs.· You can use the following official Veeam script, running it in SSMS connected to the VeeamBackup database:

USE VeeamBackup

GO

-- Reconstrucción de índices en todas las tablas

EXEC sp_MSforeachtable 'ALTER INDEX ALL ON ? REBUILD WITH (FILLFACTOR = 80, SORT_IN_TEMPDB = ON, STATISTICS_NORECOMPUTE = OFF)'

-- Actualización de estadísticas

EXEC sp_updatestats

-- Limpieza de sesiones antiguas (opcional, solo si se detectan muchas sesiones históricas)

DELETE FROM fSessions] WHERE Lcreation_time] < DATEADD(month, -6, GETDATE())

4. Restart Veeam Services After Maintenance· Once maintenance is complete, restart Veeam services to ensure they take effect.5. Monitor Behavior· Observe if the console's responsiveness and the execution of scheduled and manual jobs improve.· Review Veeam Scheduler and Related Services· Ensure the Veeam Backup Service and other services are running and configured in "Automatic" mode at the backup time.· Check the Windows Event Viewer and Veeam logs for any errors or warnings related to the scheduler.

Thank you for the update ​@Fvinas . Odd behavior...never heard of that issue before. Some jobs do run on schedule though, correct? If so..I would think the issue is not with the server-wide service, but just Job specific.

Sorry, coolsport00 -I didn't express myself well. What I mentioned above from support is that the database is very busy, and we needed to perform maintenance according to this query. This is why it wasn't responding to requests; the database is very saturated. The errors mentioned, both related to services and slowness, were caused by this.

Ah, ok. I understand now...thank you for sharing the resolution from Support ​@Fvinas .