Windows Server 2012：服务器虚拟化实战指南

WS2012

需积分: 10 22 浏览量更新于2024-07-25 收藏 9.45MB PDF 举报

身份认证购VIP最低享 7 折!

30元优惠券

在本篇关于Windows Server 2012的服务器虚拟化手册中，作者探讨了如何通过这款强大的操作系统提升IT专业人士在数据中心管理方面的效率和灵活性。Windows Server 2012引入了Hyper-V技术，这是一种革命性的改变，使得组织能够更轻易地利用虚拟化的优势，最大化服务器硬件投资的价值。传统的数据中心设计通常包含物理服务器，每个服务器专为单一工作负载而生，一旦工作负载变化，如退役或升级，服务器可能面临闲置或废弃的问题。 Hyper-V的引入使得一台物理服务器可以同时运行多个独立的虚拟机，支持包括Microsoft Windows、Linux等在内的多种操作系统并行运行，这极大地提高了资源利用率。Windows Server 2012在此基础上增加了更多功能，提升了可扩展性和内置的可靠性机制。本篇文章将重点关注以下几点： 1. **服务器角色整合**：通过Hyper-V，IT专业人员可以将多个服务器角色整合到单个虚拟机上，比如Web服务器、数据库服务器、应用程序服务器等，从而节省硬件成本，简化管理和维护。 2. **灵活性与效率**：通过虚拟化，IT团队能够根据需求快速部署或迁移虚拟机，实现按需分配资源，提高整体运营效率。 3. **跨平台支持**：支持多种操作系统，增强了数据中心的兼容性和选择性，有助于降低软件许可成本。 4. **可靠性增强**：Windows Server 2012提供了备份和恢复机制，以及高级的故障转移和高可用性功能，确保在出现问题时能迅速恢复服务。 5. **管理工具**：文章可能会介绍Windows Server 2012提供的管理工具，如Hyper-V Manager和PowerShell，这些工具可以帮助管理员轻松监控、配置和维护虚拟环境。 6. **数据中心转型指南**：对于已经建立的传统数据中心，本文会给出如何逐步迁移到基于Hyper-V的虚拟化环境的实用建议，以减少过渡期的复杂性和风险。 Windows Server 2012通过Hyper-V技术，为数据中心带来了更高的效率、更低的成本和更好的可扩展性，是现代IT基础设施管理的重要组成部分。通过阅读这篇MVA虚拟学院的手册，读者可以深入了解如何充分利用这些功能，优化现有资源，提升数据中心的整体性能和竞争力。

资源详情

资源推荐

With the evolution of storage systems, and the ever-increasing reliance on virtualized enterprise

workloads, the VHD format of Windows Server needed to also evolve. The new format is better

suited to address the current and future requirements for running enterprise-class workloads,

specifically:

• Where the size of the VHD is larger then 2,040 GB.

• To reliably protect against issues for dynamic and differencing disks during power failures.

• To prevent performance degradation issues on the new, large-sector physical disks.

Hyper-V in Windows Server 2012 contains an update to the VHD format, called VHDX, that has

much larger capacity and additional resiliency. VHDX supports up to 64 terabytes of storage. It

also provides additional protection from corruption from power failures by logging updates to

the VHDX metadata structures and prevents performance degradation on large-sector physical

disks by optimizing structure alignment.

Technical description

The VHDX format’s principal new features are:

8/29/2012

Page 13

• Support for virtual hard disk storage capacity of up to 64 terabytes.

• Protection against corruption during power failures by logging updates to the VHDX

metadata structures. The format contains an internal log that is used to capture updates to

the metadata of the virtual hard disk file before being written to its final location. In case of

a power failure, if the write to the final destination is corrupted, then it is played back from

the log to promote consistency of the virtual hard disk file.

• Optimal structure alignment of the virtual hard disk format to suit large sector disks. If

unaligned I/Os are issued to these disks, an associated performance penalty is caused by

the Read-Modify-Write cycles that are required to satisfy these I/Os. The structures in the

format are aligned to help ensure that are no unaligned I/Os exist.

The VHDX format also provides the following features:

• Larger block sizes for dynamic and differential disks, which lets these disks attune to the

needs of the workload.

• A 4-KB logical sector virtual disk that results in increased performance when applications

and workloads that are designed for 4-KB sectors use it.

• The ability to store custom metadata about the file that you might want to record, such as

operating system version or patches applied.

• Efficiency (called trim) in representing data, which results in smaller files and lets the

underlying physical storage device reclaim unused space. (Trim requires pass-through or

SCSI disks and trim-compatible hardware.)

The figure illustrates the VHDX hard disk format.

As you can see in the preceding figure, most of the structures are large allocations and are MB

aligned. This alleviates the alignment issue that is associated with virtual hard disks. The different

regions of the VHDX format are as follows:

• Header region. The header region is the first region of the file and identifies the location

of the other structures, including the log, block allocation table (BAT), and metadata region.

The header region contains two headers, only one of which is active at a time, to increase

resiliency to corruptions.

• Intent log. The intent log is a circular ring buffer. Changes to the VHDX metastructures are

written to the log before they are written to the final location. If corruption occurs during a

power failure while an update is being written to the actual location, on the subsequent

open, the change is applied again from the log, and the VHDX file is brought back to a

consistent state. The log does not track changes to the payload blocks, so it does not

protect data contained within them.

• Data region. The BAT contains entries that point to both the user data blocks and sector

bitmap block locations within the VHDX file. This is an important difference from the VHD

format because sector bitmaps are aggregated into their own blocks instead of being

appended in front of each payload block.

• Metadata region. The metadata region contains a table that points to both user-defined

metadata and virtual hard disk file metadata such as block size, physical sector size, and

logical sector size.

Hyper-V in Windows Server 2012 also introduces support that lets VHDX files be more efficient

when they represent that data within it.

Because the VHDX files can be large, based on the workload they are supporting, the space they

consume can grow quickly. Currently, when applications delete content within a virtual hard disk,

the Windows storage stack in both the guest operating system and the Hyper-V host have

limitations that prevent this information from being communicated to the virtual hard disk and

the physical storage device.

This contains the Hyper-V storage stack from optimizing the space used and prevents the

underlying storage device from reclaiming the space previously occupied by the deleted data.

In Windows Server 2012, Hyper-V now supports unmap notifications, which lets VHDX files be

more efficient in representing that data within it. This results in smaller files size, which lets the

underlying physical storage device reclaim unused space.

Benefits

VHDX, which is designed to handle current and future workloads, has a much larger storage

capacity than the earlier formats and addresses the technological demands of evolving

enterprises. The VDHX performance-enhancing features make it easier to handle large workloads,

protect data better during power outages, and optimize structure alignments of dynamic and

剩余119页未读，继续阅读

myluobin

粉丝: 0
资源: 6

Windows Server 2012：服务器虚拟化实战指南

WS2012服务器虚拟化

WS2012超越虚拟化

ws:127.0.0.1:8888/ 与ws:127.0.0.1:8888 有区别吗

WebSocketClient.js:13 WebSocket connection to 'ws://192.168.3.250:8080/ws' failed:

WebSocketClient.js:13 WebSocket connection to 'ws://localhost:8080/ws' failed: Invalid frame header

WebSocketClient.js:13 WebSocket connection to 'ws://192.168.1.8:8080/ws' failed:

CreateWindow每个参数的所有值

WebSocket connection to 'wss://10.72.192.117:8000/ws' failed:

用中文回答，为什么报这个错WebSocketClient.js:13 WebSocket connection to 'ws://172.28.128.53:8080/ws' failed:

窗口样式的属性值有哪些

WebSocketClient.js:13 WebSocket connection to 'ws://10.131.43.118:8080/ws' failed:

WebSocket connection to 'ws://192.168.2.128:8080/ws' failed:

WebSocketClient.js:13 WebSocket connection to 'ws://192.168.8.36:8080/ws' failed:

WebSocketClient.js:13 WebSocket connection to 'ws://192.168.202.64:8080/ws' failed:

WebSocket connection to 'ws://192.168.202.64:8080/ws' failed:

WebSocketClient.js:13 WebSocket connection to 'ws://192.168.3.57:8080/ws' failed:

WebSocket connection to 'ws://192.168.2.220:8080/ws' failed: WebSocketClient @ WebSocketClient.js:13

WebSocketClient.js:16 WebSocket connection to 'ws://192.168.0.5:8080/ws' failed:

WebSocketClient.js:13 WebSocket connection to 'ws://10.65.37.218:8080/ws' failed:

WebSocketClient.js:13 WebSocket connection to 'ws://localhost:3000/ws' failed: Invalid frame header

最新资源