Stopping all Veeam activities

1. Confirm that no jobs or recovery sessions are running:
   
   
   
2. We recommend disabling scheduled jobs which can start in the middle of disabling Veeam activities to exclude any interference with the further steps below:
   
   
   
3. Stop all services that begin with the word "Veeam":
   
   There may be more services starting with the word Veeam than are shown here.
   
   
4. Ensure that services are not running before proceeding (Press F5 to refresh the view status):
   
   
   
5. Repeat steps 3 and 4 for all the Veeam Proxies and Repositories.
   
   
6. (Optional) If you would like to disable Veeam Database, please do the following.
   
   Note:  Do not take the database offline when upgrading Veeam Backup & Replication as the upgrade installer will attempt to start the services after the upgrade. If the SQL Database is offline, the services cannot start, and the upgrade will likely fail.
   
   
   1. Locate information about which SQL Instance and Database being used by Veeam Backup & Replication
      
      Open Regedit, go to HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication\
      
      and find values of the following values:
      
      SqlDatabaseName (default VeeamBackup)
      SqlInstanceName
      SqlServerName
      
      
      
      
   2. You can use Microsoft SQL Server Management Studio to connect to the instance on the found SQL server where the VeeamBackup database is located.
      
      In this example, the instance name is VEEAM, and the database name is the default (VeeamBackup).
      
      
      
      
   3. Take the database Offline:
      
      
      
7. After performing the steps above you can be sure that all Veeam activities are stopped.

You can automate the stopping/starting of the Veeam Services with the following PowerShell commands.

To stop all Veeam named services: