Stopping all Veeam activities

KB ID: 2991
Product: Veeam Backup & Replication | 9.5 | 10 | 11
Published: 2019-08-26
Last Modified: 2021-12-08
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please try again later.

Challenge

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

 

Solution

The steps below will explain how to do the following:

  • Stop all Jobs and Restore operations
  • Disable all Jobs
  • Stop all Veeam related services
  • (Optional) Stop the Veeam Database
  1. Confirm that no jobs or recovery sessions are running:
    User-added image

  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:
    User-added image

  3. Stop all services that begin with the word "Veeam":
    User-added image
    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):
    User-added image

  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

      User-added image

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

      User-added image

    3. Take the database Offline:
      User-added image

  7. After performing the steps above you can be sure that all Veeam activities are stopped.
Reverse the above steps to get everything back into a running state. Remember, the SQL Database must be available for some of the key Veeam services to start.

More Information

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

To stop all Veeam named services:

Get-Service Veeam* | Stop-Service
To start all Veeam named services:
Get-Service Veeam* | Start-Service
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.