KB ID: 1891
Products: Veeam Backup & Replication
Last Modified: 2014-06-05
New Features and Enhancements
VMware Virtual SAN (VSAN)
- In addition to adding basic support (as provided by other vendors), the intelligent load-balancing engine was enhanced to account for VSAN specifics. As the result, for each VM the job will pick backup proxy running on VSAN cluster node with most of the virtual disks’ data available locally. This significantly reduces backup traffic on VSAN cluster network, resulting in minimum possible impact on production environment from backup activities.
Microsoft SQL Server 2014
- Added support for Microsoft SQL Server 2014 both as the protected guest workload (including application-aware processing functionality), and the back-end database for backup and Enterprise Manager servers.
License key auto update
- Added automated license key update option to the License Information dialog. With auto-update enabled, the product will check Veeam licensing server periodically for an updated license key, and download and install the key automatically as soon as it becomes available. This feature is particularly useful to the Service Providers and subscription-based customers, and it removes the need to download and install the license key manually each time when the license extension is purchased.
In my test environment I configured tree Hyper-V 2012R2 servers nested on vSphere 5.5, the configuration was very easy, here some details:
1. Deploy a Windows 2012R2 server, use GuestOS Windows 2012 (64-bit)
2. Upgrade hardware level to version 10
3. Remove the virtual machine from the vCenter inventory
4. Download and edit the .vmx file, add the following lines:
vhv.enable = “TRUE”
hypervisor.cpuid.v0 = “FALSE”
mce.enable = “TRUE”
5. Upload and re-add the .vmx file to the vCenter inventory
6. Edit the virtual machine hardware > CPU > Hardware virtualization> select: Expose hardware assisted virtualization to the guest OS
*Note: you need to upgrade to HW level 10, otherwise the hardware virtualization tab is grayed out.
7. Power on the virtual machine
8. Now you are able to select the Hyper-V role, finish the setup
The backend storage volume corresponding to the datastore has been removed and the datastore appears as Inactive, when I want to remove (via vSphere Client connected to vCenter server) the NFS datastore I receive this error message:
Unmounting the datastore in vCenter Server fails with the error:
‘Call “HostDatastoreSystem.RemoveDatastore” form object “datastoreSystem-28″ on vCenter Server “xxxx” failed. CannotRemove datastore ‘datastore_name’ because Storage I/O control is enabled on it. Correct it and re-try the operation
To resolve this issue, log in directly to each ESXi host that has access to the inactive datastore and manually remove it.
- Connect to the vSphere ESXi host using SSH
- Run this command to list the mounted datastores:
esxcli storage nfs list
- Run this command to unmount the NFS datastore:
esxcli storage nfs remove –v datastorename
The inactive NFS datastore has been removed
Note: if your datastore display name have some spaces, please use quotes
More information: VMware
Start Profile Wizard after you have entered Maintenance Mode
- Select: Create Profile from existing host
- Select host (in maintenance mode)
- Profile details: Reset root password
- Finish the host profile creation
On the left pane select your new host profile and right-click and select edit profile:
- Select: Root password reset > Security configuration > SSH authorized key for root user
Note: check or deselect specific host profile configurations to enable or disable them. A disabled configuration will not be applied when applying the host profile and hosts will not be checked for compliance with that configuration
Now click OK and we’ll start attaching the host of which we want to reset the password. Click ‘Attach Host/Cluster’ and select the right host, click Attach and then OK.
Voila, the root account of the host has been reconfigured and you should be able to log in again. Now the only thing left is to detach the host from the profile.
Today I installed a new vCenter 5.5 server in a environment without a domain and DNS server. During the deployment of vCenter Single Sign On I received this error message:
Error 29101 Could not connect to vCenter Single Sign On. Make sure that the Lookup Service URL points correctly to the vCenter Single Sign On instance you installed. If vCenter Sign On is installed with an IP address, make sure the IP address is specified in the URL.
Select: “Use FQDN instead of IP address to configure vCenter Single Sign-On”
Last week I upgraded a vCenter Server from version 5.1 to 5.5, I also added a 4th hosts to the cluster, so I need to upgrade the host license keys. But after upgrade I couldn’t remove the license files in vCenter Licensing section:
To connect to the ADAM database:
- Log in to the vCenter Server.
- To open ADSI Edit, click Start > Run, type adsiedit.msc, and press Enter.
- Right-click ADSI Edit and click Connect to.
- In the Connection point section, click Select or type a Distinguished Name or Naming Context.
- Enter dc=virtualcenter, dc=vmware, dc=int
- In the Computer section, click Select or type a domain or server: (Server | Domain [:port]).
- Enter localhost
- Click OK.
- Drill down to DC=virtualcenter,DC=vmware,DC=int, OU=Licensing, OU=LicenseEntities.You see the CN="license key" containers.
- Right-click the container that shows the the serial number of the key that is negative within the vCenter Server Licensing page.
- Click Delete.
When you restart he vSphere client and navigate to the Licensing page the old license keys are removed and you can re-assign license keys to the hosts
More information: VMware
Last week I upgraded VMware vCenter server from version 5.0 to 5.5 Update 1c, during installation of vCenter Single Sign-On 5.5 I received this warning message:
Service ‘VMware Kdc Service’ (VMwareKdcService) failed to start. Verify that you have sufficient privileges to start system services
The service account which I´m using for the upgrade is Domain Administrator, I tied to start the service manually but the service won’t start. The Windows Event log was clean, but in the vmkdcd.log file (located at: C:\ProgramData\VMware\CIS\logs\vmkdcd) I found this error logs:
20140812092452.000:t@0:TRACE: Vmkdcd: stop
20140812092458.000:t@0:TRACE: VmKdcSrvOpenServicePortTcp called…
20140812092458.000:t@0:TRACE: dwError=87 errno=17
20140812092458.000:t@0:TRACE: VmKdcSrvOpenServicePortTcp done.
20140812092458.000:t@0:TRACE: ERROR: vmkdc VmKdcInit failed (87)
20140812092458.000:t@0:TRACE: Vmkdcd: stop
20140812092503.000:t@0:TRACE: VmKdcSrvOpenServicePortTcp called…
20140812092503.000:t@0:TRACE: dwError=87 errno=17
20140812092503.000:t@0:TRACE: VmKdcSrvOpenServicePortTcp done.
20140812092503.000:t@0:TRACE: ERROR: vmkdc VmKdcInit failed (87)
20140812092503.000:t@0:TRACE: Vmkdcd: stop
To resolve this issue, ensure port 88 is available for use by the VMware Kdc Service:
- Use netstat from an elevated command prompt on the Windows host system to confirm port 88 is not in use. For more information on using the netstat command, see Determining if a port is in use (1003971).
- If another application is using port 88, reconfigure or disable the application to open port 88 for use with the VMware Kdc Service.
In my case VMware Converter Standalone Server was running and configured at port 88, I removed the installation and restarted the Single Sign-On setup.
More information: VMware
Last week I upgraded for a customer VMware vCenter server to from version 5.0 to 5.5 Update 1c, here some details:
This release resolves the following issues related to vCloud Automation Center:
Attempts to perform vCloud Automation Center tenant administration operation fail with an error
When you attempt to perform any vCloud Automation Center tenant administration operations such as removing an administrator from the default tenant (vsphere.local), the operation fails with a System Exception error.
Attempts to log in to vCloud Automation Center fail if the SAMAccountName contains extra trailing spaces
When you attempt to log in to vCloud Automation Center, the login attempt fails if the SAMAccountName attribute contains extra spaces trailing at the end of the name.
Attempts to log in to vCloud Automation Center fail if the password contains the colon (:) character
While attempting to log in to vCloud Automation Center, if you use a password that contains the colon (:) character, the login attempt fails.
Attempts to use the Windows Session Authentication feature might fail
When you log in to vCloud Automation Center by using Windows Session Authentication on browsers such as Internet Explorer, Google Chrome, and Mozilla Firefox might fail due to an error in the VMware Client Integration Plug-in. An error message similar to the following is displayed:
Windows Session Authentication login has failed as a result of an error caused by the VMware Client Integration Plugin
Attempts to log in to vCloud Automation Center fail if a custom UPN suffix is configured in the alias field for AD over LDAP
When you attempt to log in to the vCloud Automation Center where the custom UPN suffix is configured in the alias field for Active Directory (AD) over Lightweight Directory Access Protocol (LDAP), the login attempt fails.
This issue is resolved in this release.
Attempts to log in to vCloud Automation Center using vSphere Single Sign-On 5.5.0b might fail with an error
If you specify the Global Catalog (GC) port in the AD over LDAP Identity Provider’s (IDP) connection string, attempts to log in to vCloud Automation Center using vSphere Single Sign-On 5.5.0b might fail with an error message similar to the following:
Error received by LDAP client: com.vmware.identity.interop.ldap.WinLdapClientLibrary, error code: 10
You can also see log messages similar to the following in the vmware-sts-idmd.log file:
2014-04-09 14:18:16,564 ERROR [ServerUtils] Exception
LDAP error '
The vCenter Server 5.5 Update 1c can be downloaded here and the release notes can be found here.