Stopping all Veeam activities

This KB outlines the proper step-by-step way to stop all Veeam activities in your infrastructure.

 

On occasion it may be required to stop all Veeam-related processes, for example, during an upgrade or when applying a hotfix. 

Before you begin:

1. Confirm that no jobs or recovery sessions are running:


2. (Optional) 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":


4. Ensure that services are not running before proceeding (Press F5 to refresh the view status):

5. Repeat steps 3-4 for all the Veeam Proxies and Repositories.

6. (Optional) If you would like to disable Veeam Database, please do the following:

          6.1  Open regedit, go to HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication\
and find values of the following keys:

SqlDatabaseName (default VeeamBackup)

SqlInstanceName

SqlServerName


You can use Microsoft SQL Server Management Studio to connect to the instance on the found SQL server where VeeamBackup database is located.

In this example, the instance name is VEEAM and the database name is default.

6.2 Take the database Offline: 

7. After performing the steps above you can be sure that all Veeam activities are stopped. Now you can perform hotfix or update installation or any other kind of measures required by a Support Engineer.

Bring Veeam Services back online

1. Start the services in the following order: Repository servers -> Proxy servers -> Veeam Server.
2. Re-enable the jobs you disabled previously:


3. Once the jobs are re-enabled, your Veeam Server will be ready to resume operations.

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

Get-Service | Where-Object {$_.DisplayName.StartsWith("Veeam")} | Stop-Service
Get-Service | Where-Object {$_.DisplayName.StartsWith("Veeam")} | Start-Service

Once the shell prompt returns control, all Veeam Services should be started.