Veeam: Jobs Stuck In Stopping State

2 minute read

Description:

I haven’t had this happen to backup jobs, but replications have done this a couple times. Essentially, you want to reboot a replication server but you need to stop the replications on the VBR server first and you get stuck at a screen that shows your jobs are stuck in a stopping state for over 10 minutes. Use the following steps to actually get the jobs to stop.

veeam-stuck-in-a-stopping-state

To Resolve:

  1. Stop all services that start with “veeam”.

  2. Open the Windows Task Manager and kill all Veeam.Backup.Manager and VeeamAgent.exe processes.

  3. Restart the services that were stopped in step 1.

  4. Remove snapshots from VM(s) that part of the stuck jobs. (If they have not been already removed).

  5. If the previous steps didn’t work, we need to alter the MySQL database the Veeam uses. To backup the MySQL database:

    • Using SQL Server Management Studio:

      • Open Microsoft SQL Server Management Studio (May need to be installed separately)
      • Connect to the “ServerName\Instance” of the server that has the DB you want backed up.
      • Expand the Databases tab to get to the DB you want to back up.
      • Right click the desired DB –> Tasks –> Back Up…
      • Set “Backup Type” to “Full”
      • Go through the rest of the General and Options tab information to set the options to what you want.
      • Click OK to start the Backup process.
    • Using sqlcmd (preferred):

      • Check the name of the SQL instance and Veeam database in the Windows registry:
      • HKLM\Software\VeeaM\Veeam Backup and Replication\SqlServerName
      • HKLM\Software\VeeaM\Veeam Backup and Replication\SqlInstanceName
      • HKLM\Software\VeeaM\Veeam Backup and Replication\SqlDatabaseName
      • Open Windows Command prompt and connect to SQL instance:
      • SQLCMD -S SERVER\VEEAMSQL2008R2
      • syntax is SQLCMD -S (SqlServerName)\SqlInstanceName
      • Note: In case you have SQL server authentication enabled you may define username using -U parameter
      • Back up the Veeam database:
      • BACKUP DATABASE VeeamBackup TO DISK = ‘f:\db-backup\veeamdb.bak’
      • GO
      • Syntax is:
      • BACKUP DATABASE SqlDatabaseName TO DISK = ‘C:\VeeamDB.bak’
      • GO
  6. In a new notepad document, copy/paste the following query:

    UPDATE [Backup.Model.JobSessions]  
    SET [state] = '-1'  
    WHERE [state] != '-1'
    
    • Save the script as *.sql file (e.g. script.sql) to local disk.
    • Make sure that no jobs are running.
    • Open an admin command prompt and run the following command:
    • sqlcmd -S SERVER\VEEAMSQL2008R2 -d VeeamBackup -i C:\Scripts\sql-query.sql -o C:\Scripts\sqlresetresults.txt
    • Syntax is:
    • sqlcmd -S SqlServerName\SqlInstanceName -d SqlDatabaseName -i PATHTOSCRIPT\script.sql -o c:\resetresult.txt
    • Using: HKLM\Software\VeeaM\Veeam Backup and Replication\SqlServerName
    • Using: HKLM\Software\VeeaM\Veeam Backup and Replication\SqlInstanceName
    • Using: HKLM\Software\VeeaM\Veeam Backup and Replication\SqlDatabaseName
    • If the script needs to be applied to EM database, please use:
    • Using: HKLM\Software\VeeaM\Veeam Backup Reporting\SqlServerName
    • Using: HKLM\Software\VeeaM\Veeam Backup Reporting\SqlInstanceName
    • Using: HKLM\Software\VeeaM\Veeam Backup Reporting\SqlDatabaseName
  7. Start all the Veeam services, should be good to go!

References:

https://www.veeam.com/kb1727