We are beginning evaluation of veeam for our enterprise. Have a scenario I need a definitive answer on. I can follow up with any information I may need to add.
In a scenario where vCenter and all points are down. We get to a place where network is back up, esx hosts are back up, san is back up, but vCenter is completely hosed.
Making the assumption that my database is functioning, and I want to restore my vCenter from a known good Veeam backup using Instant Recovery, will having all Distributed Switches allow this to be possible via instant recovery? I know i can just point to an esxi host instead of vcenter for Instant recovery, but am curious about the DVS portion. Let me nkow if i can provide more detail. We do not currently own Veeam but are beginning the evaluation for our company.
Please note again, this would be an all DVS infrastructure, no vswitch. Let me know if i can provide more detail if my question is unclear about Instant Recovery being able to get our vcenter back online. I do realize that if vcenter is down i do need to point Instant Recovery directly to an online esxi host. But does that work with an all DVS infrastructure? Thanks.
-
- Lurker
- Posts: 1
- Liked: never
- Joined: May 30, 2013 12:55 pm
- Full Name: Dave Withers
-
- VeeaMVP
- Posts: 6166
- Liked: 1971 times
- Joined: Jul 26, 2009 3:39 pm
- Full Name: Luca Dell'Oca
- Location: Varese, Italy
- Contact:
Re: esxi vcenter DVS all points down - instant recovery?
The problem you are referring to is well known, and usually refers to the "invalid backing" of the vm network while it's beeing powered on.
At customers with a 100% VDS design like yours, I always used a quick trick: create the management port group (the one where you connect vCenter, its DB VM, and all other VM you need to manage the environment) and configure it with ephemeral binding. In this way it does not need vCenter to connect a virtual network, since there is no binding.
I can't find right now the docs, but I recall this problem has been fixed in later 5.0 patches, and maybe is no more a problem in 5.1, need to better check.
Luca.
At customers with a 100% VDS design like yours, I always used a quick trick: create the management port group (the one where you connect vCenter, its DB VM, and all other VM you need to manage the environment) and configure it with ephemeral binding. In this way it does not need vCenter to connect a virtual network, since there is no binding.
I can't find right now the docs, but I recall this problem has been fixed in later 5.0 patches, and maybe is no more a problem in 5.1, need to better check.
Luca.
Luca Dell'Oca
Principal EMEA Cloud Architect @ Veeam Software
@dellock6
https://www.virtualtothecore.com/
vExpert 2011 -> 2022
Veeam VMCE #1
Principal EMEA Cloud Architect @ Veeam Software
@dellock6
https://www.virtualtothecore.com/
vExpert 2011 -> 2022
Veeam VMCE #1
Who is online
Users browsing this forum: Bing [Bot], Google [Bot], Semrush [Bot] and 55 guests