v5 - SureBackup and Distributed Switches in vSphere 4.1?

[johanb2b]

I cannot create a virtual lab in our enviroment and found this in the release notes about it:

"Virtual lab may not be configured correctly when production network is connected to DVS (distributed virtual switch) on ESX(i) host virtual lab is created on. It is recommended to use ESX host with standard virtual switch until this issue is resolved in future update."

Is there a way to work around this? We do not want to change to regular vswitches.

When can we expect this to work?

/Johan

[Gostev]

We are planning to address this in future updates to version 5. This issue was reported too late in the release cycle unfortunately, and QC did not allow implementing the required fixes because this would require major retest and required release date would be misseed. Meanwhile, as a temporary workaround I suggest that you can use separate (even standalone) ESX host for your virtual labs.

[flakpyro]

Having the same problem here, luckily we have a test lab esx sever that is using plain old vSwitches, however when i try and run the verification job there i am given the error:

Code: Select all

10/21/2010 11:59:34 AM          Publishing
10/21/2010 11:59:35 AM          Updating configuration
10/21/2010 12:00:15 PM          Registering
10/21/2010 12:00:16 PM Fail     Configuring networks
10/21/2010 12:00:16 PM Fail     
                                Cannot retrieve VM networks for vm-30531.
10/21/2010 12:00:24 PM          Unregistering
10/21/2010 12:00:26 PM          Cleaning up redo logs
10/21/2010 12:00:26 PM          Unpublishing
10/21/2010 12:00:26 PM          Task finished

Is this because the VM is assigned a dvPortGroup on the production cluster while no such thing exists on our test lab with normal vSwitches? When i watch the ESX console i see the VM is published but no network adapters are ever assigned.

Everything else is working great, indexed searching, same great backup speed, just having issues with the new SureBackup.

[Gostev]

No, all should be fine in this setup. VNICs on VMs are assigned to virtual networks, not to switches. Please send full log files from Help > Support information to support@veeam.com, they provide much more extensive information, and our technical staff should be able to say what is missing here.

[flakpyro]

Support ticket in and logs sent

[sunshineknox]

We are using dvswitches. Could I just create a standard switch with a vm network for the virtual lab and still be able to keep my VMs on the dvswitches?

[Gostev]

Hello, actually Veeam Backup & Replication 5.0.1 added support of DVS (check out release notes for new features), so workarounds are no longer required.

[sunshineknox]

I'm running 5.0.1. I will open a support case, because it is not working for me.

[Gostev]

What exactly is not working for you?

[sunshineknox]

I had to take my dvswitch out of the folder it was in. Veeam is unable to work correctly when the dvswitch is in a folder. Veeam said they would address the problem. For the time being make sure the dvswitch is not in a folder.

[Gostev]

Thanks for the update!

[Berniebgf]

[merged into existing discussion]

Veeam B&R 5.0.2 - Release Notes.

Quote:
"Virtual lab may not be configured correctly when production network is connected to
DVS (distributed virtual switch) on ESX(i) host virtual lab is created on. It is
recommended to use ESX host with standard virtual switch until this issue is resolved
in future update"

Any timeline on when the update will be available to resolve this limitation?

Bernie.

[Vitaliy S.]

Hello Bernie, you are looking at the list of issues resolved in version 5.0.1. Thanks!