Skip to main content
  • EN

I am working on a Veeam DR doc. I would like to be able to bring up the DR environment in a controlled manner to the point of only enabling the jobs I want to enable.  I know it can be easily done by simply right clicking and disabling the jobs or by PowerShell script. My concern is jobs kicking off as soon as the DR instance is up and not being able to disable them before they start failing. Because before anything we need to validate the environment, proxies, repositories, etc.  Simply failing over the prod system will mean ALL the services and processes will start when the system boots. The feedback I received from support is to stop the Veeam Backup Service.  However, from what I understand I do not have the ability to disable jobs while the Veeam Backup Service is offline. Is there a scheduler service that can be stopped? Ideally, at least for the DR test, we would like to keep jobs from running yet be able to restore systems.

While an actual failover is something that should occur automatically, there are a number of steps/validations that need to happen before backups are resumed.

So the DR steps would be (Ideally):

  1. Fail over VBR and VDB servers.
  2. Verify access to VBR and VDB servers.
  3. Stop Veeam Backup Service (or any other that will still permit the succeeding steps.)
  4. Disable ALL configured enabled/scheduled jobs. Assuming that it is possible.
  5. Add Veeam Proxy Server(s).
  6. Add Veeam Repositories.
  7. Enable needed services to execute restores ONLY. Assuming that whatever services that are enabled WILL NOT kick off backup jobs.
    1. IF the services that are enabled will also control backup jobs, Disable ALL jobs.

I welcome your input.

What do you mean by “Veeam DR”? Are you referring to how to recover your Veeam server in the event of corruption or something? Or, are you referring to DR recovery of your backed up VMs?

The DR scenario is the primary VBR & VDB systems are down and a disaster has been called and we are failing over to the alt site. Presently, we are using Zerto to replicate VMs, including the VBR & VDB systems.

I am with Shane on this one regarding clarity of what you are trying to do - a VBR failover or just VM failovers?  The response you will receive in this thread will be much different depending on the answer to that question because each has their own processes and caveats.

The DR scenario is the primary VBR & VDB systems are down and a disaster has been called and we are failing over to the alt site. Presently, we are using Zerto to replicate VMs, including the VBR & VDB systems.

Then to test this I would recommend to disable all jobs and then allow Zerto to replicate the VMs over.  Then bring them up on the DR side for testing - this way nothing runs when the services start on VBR.

Well, I’m not familiar with Zerto, so specific step-by-step I can’t provide. The “cleanest” way would be to run Config backups of your Veeam DB and place them at a DR site. Have a Windows VM already built up at your DR site with the version of Veeam you have installed on your Prod VBR server. In the event your Prod VBR server goes down, perform a DB Migration per the User Guide:

https://helpcenter.veeam.com/docs/backup/vsphere/vbr_config_restore.html?ver=120

If your Prod VBR is still on, you’ll need to power it down. You don’t need to add Proxies/Repos as the DB restore does all that for you.

Also, are you running your Veeam server AT the DR site? that is best practice to not have to fail it over in the event of a disaster. 

Comment


Terms & Conditions