• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Veeam Backup & Replication

I just found out that Veeam does not work with vSphere 5 and a ESXi 4.1 host just yet, I get that datastore inactive error. I sent in a support ticket to get the download link for the patch.

Does anyone have this patch they could give me? Why don't they just let you download it? I assume they want people to migrate to Veaam version 6?
 
AMD_Gamer said:
I am confused how the replication failover works with networking, say you are replicating a web server how does the outside world get to it once you do the failover to the replica at a different site?

bump.

My remote site uses a different IP subnet so what happens when the replica powers on?
Click to expand...

bump
 
If you are replicating to the same site (same subnet). You don't have to do anything. I have some customers that have two ESX hosts and replicate the VM's between them.

If it's being replicated to a remote site with a VPN connection or something. Once you turn the replicated VM on, you will need to adjust the NAT statement on your firewall.
 
jenuster said:
If you are replicating to the same site (same subnet). You don't have to do anything. I have some customers that have two ESX hosts and replicate the VM's between them.

If it's being replicated to a remote site with a VPN connection or something. Once you turn the replicated VM on, you will need to adjust the NAT statement on your firewall.
Click to expand...

But the remote site uses a different IP subnet.
 
marty9876 said:
Veeam v6 should re-ip things
Click to expand...

So how would you route traffic destined for that VM to the remote site? lets say you are running a web server on the VM and want to the outside world to access it like normal? We have a site-to-site from the main location to the remote location setup.
 
AMD_Gamer said:
So how would you route traffic destined for that VM to the remote site? lets say you are running a web server on the VM and want to the outside world to access it like normal? We have a site-to-site from the main location to the remote location setup.
Click to expand...

This gets over my head. Assuming these are different networks/WAN locations with different sets of routable IP's I think you need to use BGP routing or something like that. I tried to do this once and was told I needed a class A set of routable IP's. I didn't have that at the time... ;)

DNS weighting and stuff don't really work for this, unlike MX records and weighting.
 
AMD_Gamer said:
So how would you route traffic destined for that VM to the remote site? lets say you are running a web server on the VM and want to the outside world to access it like normal? We have a site-to-site from the main location to the remote location setup.
Click to expand...

What would you have to do if you moved a physical box between sites?

Do the same thing. :)

(hint: I know jack-all about networking, but I expect it has to do with changing the external / edge routing tables or the like, so that traffic gets routed to the right subnet internally from outside. Or whatever).
 
lopoetve said:
What would you have to do if you moved a physical box between sites?

Do the same thing. :)

(hint: I know jack-all about networking, but I expect it has to do with changing the external / edge routing tables or the like, so that traffic gets routed to the right subnet internally from outside. Or whatever).
Click to expand...

Extended VLANs + HSRP + MPLS :> worrying w/ the networking at the server level is nuts. Changing it isn't that bad, but its all the apps and uderlying dependencies in a complicated environment. Not worth it to me.
 
It's really not worth it. What I usually do for mail servers for example is create a secondary MX record and create a 1 to 1 NAT with the firewall at your remote site. So when you turn the VM on in case of a disaster you still have mail flow.
 
So i would create a static route for the new IP from the failed site across the VPN to the remote site? What happens if the site is destroyed in a nuclear blast and not just the VN/server .:p How would i get people from the internet to go to the new site? I assume it would have to be done with DNS?
 
What happens if the ESXi host you are running Veeam on or vCenter goes down, how do you fire back up the replication or perform a restore?
 
jenuster said:
Setup VEEAM on a physical server.
Click to expand...

Is that the best practice? Right now we have Veeam on the same VM as vCenter and it seems to work fine other than CPU usage spike during jobs.

I suppose that putting it on its own server would be best.

What about doing a replication of the VM you are running Veeam on?
 
Never tried it but I assume it won't work. I would move the VEEAM server to a physical box since it is best practice.
 
AMD_Gamer said:
Is that the best practice?
Click to expand...
The question really should be; What makes the most sense to you?
It's already been addressed on page 1 that running Veeam as a VM in the environment it is protecting is a bad idea. That fact really hasn't changed.

Veeam can't back itself up.

You could just use SQL Management Studio to back up the Veeam SQL database and then you'd have to reinstall Veeam and point it to the database. Ideally you'd have another Veeam install that backs up your production Veeam server only using application image awareness.
 
You must log in or register to reply here.
Back
Top