flyinweb's blog

VMware vCenter Converter导入计算机时出错，对话框内容如下：

---------------------------
VMware vCenter Converter
---------------------------
出现错误。此错误的原因可能由网络连接故障所致。
向导将立即关闭。
请检查网络连接并重试。
---------------------------
确定  
---------------------------

解决办法：

重启以下服务：

　　市场上各种VMware工具中，有一来自TriLead公司叫做VM Explorer的工具，他们提供了完整产品的免费版本，我喜欢免费的VMware工具，所以测试了它。VM Explorer也叫做VMX，它能做开发虚拟环境以外的更多事情。事实上，专业版本的VMX可以替换VMware Consolidated Backup（VCB），帮助运行VMware ESX的小型企业。

　　VMX有一个图形用户界面和作业调度程序，能够直接复制到NAS或SAN，并且提供像任务历史、备份完成邮件、虚拟机子机恢复、SSH及访问虚拟机的远程桌面协议、克隆和快照管理，这些都是VCB不提供的功能。对于喜欢尝试新免费VMware工具的管理者来说，VMX本身是一个非常有用的备份和管理工具。

For clustering the Cluster resource name must have full access to the Virtual Cluster Names so when failover takes place DNS entries can be updated.

However if you used a underscore _ a big NO! NO! with NetBIOS and DNS names. Solution: wipe and start over.
If you used a dash -, an exceptable NetBIOS name, your still screwed and got this error. BUG in Windows 2008 R2. You can add the name manualy to the DNS, but it will not be automatic.

Following errors were recorded in event logs when it registrations fails:

场景1：

Cluster network name resource 'SQL Network Name (VirutalClusterName)' failed registration of one or more associated DNS name(s) for the following reason:
DNS signature failed to verify.

Ensure that the network adapters associated with dependent IP address resources are configured with at least one accessible DNS server
In DNS Management (dnsmgmt.msc):

1. Find the VirtualClusterName that is failing to register.
2. Right-Click Properties.
3. Select Security Tab.
4. Click Add.
5. Click Object Types.
6. Check off "Computers"; uncheck other options selected.
7. Enter in the name of the cluster (a.k.a Cluster Name Object (CNO)).
8. Click Check Names; Verify that the entry has been found.
9. Click OK.
10. Give the CNO FULL Control over this record.
11. Click OK.

场景2：

群集网络名称资源“群集名称”注册一个或多个相关联的 DNS 名称失败。原因如下:
DNS 服务器失败。

请确保与从属 IP 地址相关联的网络适配器已配置为至少可以访问一个 DNS 服务器。

相关资源：

Windows Server 2008 Troubleshooting: Event ID 1196 — Microsoft-Windows-FailoverClustering

DNS Registration with the Network Name Resource

The Hyper-V best practice in traditional production environments is that any physical network interface used by guest virtual machines is dedicated and isolated to guest only traffic and not shared with the management operating system (host). This recommendation was made for several reasons – security is the primary reason since virtual machines are considered less trusted than the management partition isolating the network traffic reduces the risk that a malicious guest could take advantage of a remote security exploit to take over the physical machine. Following this practice also reduces the risk of a guest virtual machine saturating the network preventing the server administrator from being able to log onto the physical machine and take appropriate action. In Server 2008 (Hyper-V V1) you accomplished this by unbinding TCP (as well as any other network protocol) on the virtual adapter exposed by Hyper-V – in Server 2008 R2 we have added a new feature which be default does not create the virtual adapter on the management partition (of course there’s an option to have it the old way). In addition this functionality was pushed into the Add Roles Wizard when you create your first virtual network. Here’s some screen captures to illustrate.

I was recently asked about how to change the IP address of an Exchange 2007 cluster. Here is the information that I shared:

[Window Title]
错误

[Main Instruction]
检查目标节点上的虚拟机兼容性时出错

[Content]
虚拟机“Win08R2Web”与目标节点“node140.zzyddc.com”不兼容。
Hyper-V 检测到:
虚拟机“Win08R2Web”与物理计算机“NODE140”不兼容。(虚拟机 ID B577EECE-FCFE-4DF6-AE30-3C1D64EA471D)

虚拟机“Win08R2Web”当前正在使用 Intel 处理器，但物理计算机“NODE140”具有的处理器为 未知。如果虚拟机和物理计算机的处理器来自不同的供应商，则无法将正在运行或已保存的虚拟机迁移到物理计算机。但如果关闭了该虚拟机，则可以将其移动到此节点。(虚拟机 ID B577EECE-FCFE-4DF6-AE30-3C1D64EA471D)

[确定]

While initiating a live migration of a running virtual machine under Hyper-V R2 the error message below is displayed:
 
“there was an error checking for virtual machine compatibility on the target node
 The virtual machine <name> is not compatible with the target node <nodename>. Hyper-V has detected that: The virtual machine <name> is not compatible with physical computer <servername>. The virtual machine <name> is currently using an Intel processor, but physical computer <servername> has an Unknown processor.
 
Solution: make sure Intel Virtualization Technology & Execute Disable Bit (or AMD equivalent) are both enabled on the target Hyper-V server.

What is a Microsoft Failover Cluster Virtual Adapter anyway?

A question often asked is, "What is the Microsoft Cluster Virtual Adapter and what can I do with it?" The typical, and correct answer, is to leave it alone and let it just work for you. While that answer satisfies most, others may want just a little more by way of an explanation, so hopefully, this blog will provide that.

The networking model in Windows Server 2008 Failover Clustering was rewritten to accommodate new functionality which included being able to obtain IP addresses from DHCP servers and being able to locate Cluster nodes on separate, routed subnets. Additionally, communications went from being UDP Broadcast transmissions to UDP Unicast with a smattering of TCP connections thrown in for good measure. What this all adds up to is more reliable and robust communication connectivity within the Cluster, no matter where the Cluster nodes were located. It no longer matters if Cluster nodes are located in the same physical rack in the same datacenter or in a server rack in a server room in a remote datacenter located at the end of an OC3 WAN connection. This now makes the Cluster more tolerant of single points of failure, e.g. Network Interface Card (NIC) card (and hence the new driver name 'Network Fault-Tolerant or NetFT.sys). The only real minimum requirement is multiple (at least two), redundant communication paths between all nodes in the Cluster. This way, the Cluster network driver (NETFT.SYS) could build a complete routing structure to provide the redundant communication connectivity the Cluster would need to keep applications and services highly available.

Live migration is probably the most important technology that Microsoft has added to Hyper-V in Windows Server 2008 R2. It enables virtual machines (VMs) to be moved between Hyper-V hosts with no downtime. Using live migration, you can migrate all VMs off the Hyper-V host that needs maintenance, then migrate them back when the maintenance is done. In addition, live migration enables you to respond to high resource utilization periods by moving VMs to hosts with greater capacities, thereby enabling the VM to provide end users with high levels of performance even during busy periods.

      Live migrations can be manually initiated, or if you have System Center Virtual Machine Manager 2008 R2 and System Center Operations Manager 2007, you can run automated live migrations in response to workload. You need to complete quite a few steps to set up two systems for live migration, and I’ll guide you through the process. First, I’ll explain how live migration works. Then I’ll cover some of the hardware and software prerequisites that must be in place. Finally, I’ll walk you through the important points of the Hyper-V and Failover Clustering configuration that must be performed to enable live migration.