flyinweb's blog

简介： IBM® Cloud 的新特性支持应用程序开发人员和架构师消除应用程序中的单点故障。本文将提供关于那些特性的一个详细指南，其中包括关于 IBM Cloud 采用的一种方法（添加虚拟 IP 地址支持）的讨论，如何准备您的云实例以利用这个特性，如何设置一个高可用网站，以及如何测试该网站。

IBM® Smart Business Development and Test on the IBM Cloud 是一个动态提供且可伸缩的弹性环境，能够向企业客户提供他们开发、测试和托管应用程序所需的全部资源。它包含一个 web 门户，用于配置和管理云资源；一些 IBM 产品的软件映像，用于迅速开始开发和测试工作；以及一些 API，用于允许用户以编程方式控制云资源和软件。自从 IBM Cloud 问世以来，IBM 团队就一直致力于添加提供额外灵活性和弹性的新特性。

Proxmox VE 是一个基于Debian Etch (x86_64) 版本的虚拟环境；它提供了一个可运行OpenVZ和KVM虚拟机的开源虚拟化平台。同时，其拥有一个强大的基于web界面的控制面板（这个控制面板包含了一个web化的图形控制终端，你可以通过这个终端，连接并使用虚拟机。 使用Proxmox VE，你甚至可以通过控制面板创建虚拟主机集群，并且在远程的主机上创建和控制虚拟机。Proxmox VE，同时也支持把一个运行的虚拟机从一个主机中镜像到另一个。这个教程将向你展示如何使用Proxmox VE控制KVM和OpenVZ虚拟机，和怎样通过Proxmox VE创建一个小的计算机云。

我不能保证这篇文章对你完全有效。

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.