Home
Join

10 Replies

  • Hi, considered what you have shared. It’s like you are already setup the key items to handle Veeam Backup Jobs except the Replication portion.

    You can approach the Veeam Backup Server recovery by:
    1. Backup the Veeam Server offsite (copy) then restore it. Then simply review the configurations only.
    2. Setup a new VM and then restore the configuration file that you have backed up. Using the process https://helpcenter.veeam.com/docs/backup/hyperv/vbr_config.html?ver=110

    Spice (2) flagReport
    1 found this helpful thumb_up thumb_down
  • we have a similar set up here.  for our main ESXi host we have a replica job to another ESXi host.  Interested to see what other are doing in this situation.  

    Spice (1) flagReport
    Was this post helpful? thumb_up thumb_down
  • Bill_Chz wrote:

    Hi, considered what you have shared. It’s like you are already setup the key items to handle Veeam Backup Jobs except the Replication portion.

    You can approach the Veeam Backup Server recovery by:
    1. Backup the Veeam Server offsite (copy) then restore it. Then simply review the configurations only.
    2. Setup a new VM and then restore the configuration file that you have backed up. Using the process https://helpcenter.veeam.com/docs/backup/hyperv/vbr_config.html?ver=110

    Thanks.. with only 1 Veeam server orchestrating the backup jobs I don't see how I would restore the offsite backup of the server without a second Veeam server. Maybe just a setup VM on a different host that can have Veeam installed then restore the config in the event the primary Veeam server is dead. 

    jim.mcneil wrote:

    we have a similar set up here.  for our main ESXi host we have a replica job to another ESXi host.  Interested to see what other are doing in this situation.  

    I need to get replication done. I am curious if the Veeam server is down; does Veeam need to be restored before anything can be done with the replicas? 

    Spice (1) flagReport
    Was this post helpful? thumb_up thumb_down
  • The replica sits on the target host in a shutdown state with the NIC disconnected.  You can bring it up at will for testing, etc., and in the case of an outage all you need to do is start it and attach the NIC.  No need for Veeam to bring it up.

    Spice (4) flagReport
    2 found this helpful thumb_up thumb_down
  • Da_Schmoo wrote:

    The replica sits on the target host in a shutdown state with the NIC disconnected.  You can bring it up at will for testing, etc., and in the case of an outage all you need to do is start it and attach the NIC.  No need for Veeam to bring it up.

    Thanks!

    Spice (1) flagReport
    Was this post helpful? thumb_up thumb_down
  • " Maybe just a setup VM on a different host that can have Veeam installed then restore the config in the event the primary Veeam server is dead. " Yes, you can have an idle Veeam Server that you can simply restore the configuration file and then link your repositories to initiate restores.

    Spice (1) flagReport
    1 found this helpful thumb_up thumb_down
  • Just have an offline clone of your existing Veeam B&R machine sitting somewhere and call it a day. I have it lying around on my work laptop as Hyper-V virtual machine so I can quickly power it up to restore the primary one 😎 You can use your favorite V2V converter https://www.vmwareblog.org/v2v-converters-overview/ to convert your VMware virtual machine to Hyper-V if you want to follow this route.
    Spice (2) flagReport
    Was this post helpful? thumb_up thumb_down
  • Supaplex wrote:

    Just have an offline clone of your existing Veeam B&R machine sitting somewhere and call it a day. I have it lying around on my work laptop as Hyper-V virtual machine so I can quickly power it up to restore the primary one 😎 You can use your favorite V2V converter https://www.vmwareblog.org/v2v-converters-overview/ to convert your VMware virtual machine to Hyper-V if you want to follow this route.

    I risked the snapshot stun for 1 replica and put it on the other host. Then copied the replica to remote site host for extra insurance - Same concept though. 

    Spice (1) flagReport
    Was this post helpful? thumb_up thumb_down
  • networks_jj wrote:

    Same concept though. 

    Totally. Just make sure you are using a local database that was cloned too and not the same external one. I missed that part once back in the days and crippled the whole backup configuration.

    Spice (1) flagReport
    Was this post helpful? thumb_up thumb_down
  • Da_Schmoo wrote:

    The replica sits on the target host in a shutdown state with the NIC disconnected.  You can bring it up at will for testing, etc., and in the case of an outage all you need to do is start it and attach the NIC.  No need for Veeam to bring it up.

    But be carefull with this workaround. When you get the backup server back online, you need to configure the started replicas active with a later permanent failover. Otherwise, you delete the active VM when you delete all replicas that are no longer in use. We once very successfully deleted about two-thirds of our infrastructure with this. That was a really hard test for our backup and our nerves. But all went well ;-)

    Bye Tom

    Was this post helpful? thumb_up thumb_down

Read these next...