Category: vCenter [en]

Posted on

vSphere 6.7 U1 and Veeam Backup 9.5 U3a

Failed Backup Jobs after Update to vSphere 6.7 U1

On October 16th 2018 vSphere 6.7 Update 1 became available. An update we’ve been desperately waiting for. Finally vSphere-Client (HTML5) has become fully functional. Until that some tasks had to be done with the infamous flash client.

Unfortunately problems emerged soon after users updated their clusters to vSphere 6.7 U1 in combination with Veeam Backup jobs.

Workaround

VMware and Veeam worked hard to identify the root cause of the problem. It turned out that there was a change in the vSphere API which caused communication issues with Veeam Backup.

Latest API version is 6.7.1, but this one seems to be incompatible with Veeam Backup 9.5 U3a. According to Veeam sources, the issue will be settled with the soon to come Veeam Backup Update 4.

For all of those who have already updated their clusters to vSphere 6.7 U1 there’s a workaround. You need to enter a registry key to force Veeam Backup using the older API 6.7.

Warning! This solution is not recommended by Veeam Support. If you’re not yet on vSphere 6.7 U1 and you’re using Veeam Backup, you better wait until release of Veeam Backup 9.5 Update 4. Do not upgrade. Read this passage again!

The workaround outlined below has to be reverted as soon as Veeam 9.5 Update 4 is available.

HKLM\SOFTWARE\Veeam\Veeam Backup and Replication

You need to add a multi-string-value (REG_MULTI_SZ). Enter the Value below:

6.7.1 = 6.7

This registry key forces Veeam Backup to use API 6.7, but might lead to other yet unknown problems. But it enables to run your Veeam Backup jobs again.

Posted on

NSX-Manager Permissions and Groups

Using vSphere-Client 6.7 to synchronize NSX-Manager with Active Directory

Once you’ve deployed NSX-Manager to a vSphere 6.7 cluster, you may have noticed an error  on the dashboard.

“No NSX Managers available. Verify current user has role assigned on NSX Manager.”

Assuming you have configured vCenter connections correctly, there’s a simple explanation for the error (KB2080740).

Usually initial setup of NSX-Manager is done by the default SSO User administrator@vsphere.local. If you log into vCenter using that user, there will be no error on the dashboard. The point is that NSX-Manager has its own permissions and roles which are not coupled to vCenter permissions. That means a user with administrator rights in vCenter does not automatically get administrator rights in NSX-Manager. Without any permissions that user can’t even see NSX-Manager. Continue reading “NSX-Manager Permissions and Groups”

Posted on

Joining VCSA to Active Directory

Joining Active Directory with vCenter Server Appliance (VCSA) has been simplified with every generation of VCSA.

I will show the workflow how to connect a VCSA 6.7 to an Active Directory source. The process differs a little, depending whether you’re using the HTML5-Client or the Web-Client (Flash).

Requirements

  • VCSA hostname has to be FQDN and may not be an IP address.
  • You need to login with a member of systemconfiguration admins, which administrator@vsphere.local is by default.

Workflow

The workflow is divided into three steps

  • Join VCSA to ADS
  • Reboot
  • Add ADS as identity source

Continue reading “Joining VCSA to Active Directory”

Posted on

vCenter Appliance Migration Upgrade

Relink VM MoRef IDs to Veeam Backup Restore-Points

In this post I will show how to use Veeam Migration Utility in cases when you have to migrate a whole cluster to a new vCenter, but you can’t afford to cut existing backup chains.

The Good

Upgrading a vCenter Server Appliance (VCSA) has become a commodity in recent times. All you have to do is to run an upgrade wizard and point to the old VCSA. Thanks to VMware developers it’s one of these “Next-Next-Finish” deployments. At the end you’ll have an upgraded vCenter with same settings, name, IP, and (if you like) historic data.  This is great! I can remember vCenter on Windows upgrades that were a PITA.

The Bad

In some rare (but ugly) occasions you simply can’t use the wizard and you have to migrate your hosts to a completely new VCSA without data migration. You’ll have to rebuild every setting, datacenter, cluster, folder, pool, group, rule, etc from scratch to match your old environment. Continue reading “vCenter Appliance Migration Upgrade”

Pages: 1 2