invalid-file

List of issues that are fixed

Issue 1

Issue 2

Issue 3

• You migrate a virtual machine from a Virtual Server host.
• Multiple virtual machines share the same parent virtual hard disk file.

Issue 4

Issue 5

Issue 6

iSCSI 초기자 설정
iscsicli QAddTargetPortal <Portal IP Address>
iscsicli ListTargets
iscsicli QloginTarget <target_iqn>
iscsicli PersistentLoginTarget <target_iqn> T * * * * * * * * * * * * * * * 0
iscsicli ListPersistentTargets
iscsicli ReportTargetMappings

모든 Vendor 허용 설정 후  자동으로 재부팅
mpclaim -r -i -a ""

Processor

1.      32 논리 프로세서 코어 지원

2.      SLAT(Second Level Address Translation)

-       가상 주소와 실제 주소 변환에 대한 overhead 감소

-       Hypervisor의 CPU Time과 각 가상 머신의 메모리 사용량 절약

3.      CPU Core Parking

-       유휴 상태의 CPU를 Sleep 상태로 전환해 전원 절약

Networking

1.      Jumbo frame

-       물리적인 NIC이 지원하는 경우 9014byte 크기의 frame 지원

-       전체적인 네트워크 성능 향상, CPU overhead 감소

2.      TCP Chimney

-       Network processing 작업을 NIC(H/W)에서 하도록 해 성능 향상

3.      VMQ(Virtual Machine Queue)

-       물리적인 컴퓨터의 NIC이 DMA를 이용해 패킷을 VM의 메모리로 직접 전달하도록 해 I/O 성능 향상

CSV(Cluster Shared Volumes)

-       CSV는 장애 조치 클러스터링 기능의 일부로 다수의 Windows 서버가 SAN 저장소를 하나의 일관된 이름 공간으로 접근할 수 있게 해준다. 클러스터 구성에서 저장소 설정을 간편하게 만들어주며 라이브 마이그레이션의 속도를 향상시킨다.

Live Migration

-       Windows Server 2008 R2에 추가된 기능 중 가장 핵심적인 기능

요구 사항

ž   지원 운영체제

-       Windows Server 2008 R2 x64 Enterprise Edition

-       Windows Server 2008 R2 x64 Datacenter Edition

-       Hyper-V Server 2008 R2

ž   모든 물리적인 호스트에 Failover Clustering이 구성되어 있어야 한다.

ž   Failover Clustering은 클러스터당 최대 16 노드까지 지원한다.
(두 클러스터 노드에서 한번에 한 개의 라이브 마이그레이션 세션만 가능하다.)

ž   라이브 마이그레이션을 위한 전용 네트웍이 구성되어 있어야 한다.
(많은 양의 메모리 페이지를 전송하기 위해 1 Gigabit의 전용 이더넷이 권장된다.)

ž   물리적인 호스트는 같은 제조사의 프로세서를 사용해야 한다. (Intel / AMD)

ž   물리적인 호스트는 동일한 서브넷으로 구성되어야 한다.

ž   물리적인 호스트는 공유 저장소에 접근할 수 있어야 한다.
(공유 저장소는 CSV가 권장된다.)

Live Migration 과정

①     Live Migration Setup

ž   원본 호스트와 대상 호스트 간에 데이터 이동을 위한 TCP 세션 생성

ž   대상 호스트에 빈 VM이 생성되고 메모리 할당

②     메모리 페이지 전송

ž   대상 호스트에 할당된 메모리로 원본 VM의 Working Set 전송 시작
(메모리의 페이지 크기는 4 Kbyte)

ž   전송 중 원본 VM에서 변경되는 메모리 페이지에 대한 추적

ž   메모리 추적으로 변경된 메모리에 대해 수 차례 전송 수행

③     메모리 페이지 전송 완료

ž   대상 호스트로 남아 있는 변경된 메모리 페이지를 복사하고 VM의 레지스터와 디바이스의 상태 전송
(이 과정에서 원본과 대상 호스트의 네트웍 속도가 매우 중요한 요인이 된다. 변경된 페이지와 VM의 Working Set을 전송하는 시간에 따라 라이브 마이그레이션의 완료 시간이 결정된다.)

ž   대상 호스트로 VM의 Working Set 전송이 완벽하게 완료되면, 즉 VM의 Working Set과 대상 호스트의 그것과 완전히 일치하면 다음 과정 진행

ž   라이브 마이그레이션은 이 과정 이전 어디서든 취소가 가능하다.

④     저장소 핸들 이동

ž   VM에 대한 저장소(VHD 파일 또는 Pass-through 디스크)의 조작(Control) 권한이 대상 호스트로 이동

⑤     대상 호스트에서 VM Online

윈도우 서버 2008에 SCOM 2007 설치

1. hoxfix 설치
Administration Console
- KB951327

RMS, Management Server, Gateway Server, Agent
- KB952664
- KB953290
- KB951116

2. Reporting Services 설치 시 필요한 구성 요소 SSRS Reporting Service
Servermanagercmd -i Web-server Web-Http-Redirect Web-Asp-Net Web-Windows-Auth Web-Metabase Web-WMI Web-Lgcy-Scripting Web-Lgcy-Mgmt-Console

3. SQL Server 설치
- Database Engine
- Reporting Services
- Workstation components, Books Online and development tools

4. Management Server 설치 시 필요한 구성 요소
Servermanagercmd -i Powershell NET-Framework-Core

5. 관리 서버 설치

6. KB954049 설치 

SCVMM 2008 설치 후 Hyper-V 호스트를 등록하면 Need Attention 경고와 함께 Upgrade available로 나타나는 경우 해당 Hyper-V 호스트에 다음 업데이트를 적용하면 해결된다.

KB956589 - KO EN
KB956774 - KO EN

Windows6.0-KB956589-x64-EN.msu

Windows6.0-KB956589-x64-KO.msu

Windows6.0-KB956774-x64-EN.msu

Windows6.0-KB956774-x64-KO.msu

Supported Server Operating Systems

Microsoft Windows Server 2008 x64 (VMs configured with 1, 2 or 4 virtual processors)
Windows Server 2008 Standard
Windows Server 2008 Enterprise
Windows Server 2008 Datacenter
Windows HPC Server 2008
Windows Web Server 2008
Windows Server 2008 Standard without Hyper-V
Windows Server 2008 Enterprise without Hyper-V
Windows Server 2008 Datacenter without Hyper-V

Microsoft Windows Server 2008 x86 (VMs configured with 1, 2 or 4 virtual processors)
Windows Server 2008 Standard (x86 Edition)
Windows Server 2008 Enterprise (x86 Edition)
Windows Server 2008 Datacenter (x86 Edition)
Windows Web Server 2008 (x86 Edition)
Windows Server 2008 Standard without Hyper-V (x86 Edition)
Windows Server 2008 Enterprise without Hyper-V (x86 Edition)
Windows Server 2008 Datacenter without Hyper-V (x86 Edition)

Microsoft Windows Server 2003 x86 (VMs configured with 1 or 2 virtual processors)
Windows Server 2003 R2 Standard x86 Edition with Service Pack 2
Wndows Server 2003 R2 Enterprise x86 Edition with Service Pack 2
Windows Server 2003 R2 Datacenter x86 Edition with Service Pack 2
Windows Server 2003 Standard x86 Edition with Service Pack 2
Windows Server 2003 Enterprise x86 Edition with Service Pack 2
Windows Server 2003 Datacenter x86 Edition with Service Pack 2
Windows Server 2003 Web Edition with Service Pack 2

Microsoft Windows Server 2003 x64 (VMs configured with 1 or 2 virtual processors)
Windows Server 2003 R2 Standard x64 Edition with Service Pack 2
Windows Server 2003 R2 Enterprise x64 Edition with Service Pack 2
Windows Server 2003 R2 Datacenter x64 Edition with Service Pack 2
Windows Server 2003 Standard x64 Edition with Service Pack 2
Windows Server 2003 Enterprise x64 Edition with Service Pack 2
Windows Server 2003 Datacenter x64 Edition with Service Pack 2

Microsoft Windows 2000 Server (VMs configured with 1 virtual processor)
Windows 2000 Server with Service Pack 4
Windows 2000 Advanced Server with Service Pack 4

Linux Distributions (VMs configured with 1 virtual processor)
Suse Linux Enterprise Server 10 with Service Pack 2 x86 Edition
Suse Linux Enterprise Server 10 with Service Pack 2 x64 Edition
Suse Linux Enterprise Server 10 with Service Pack 1 x86 Edition
Suse Linux Enterprise Server 10 with Service Pack 1 x64 Edition


Supported Client Operating Systems

Microsoft Windows Vista x86 (VMs configured with 1 or 2 virtual processors)
Windows Vista Business x86 with Service Pack 1
Windows Vista Enterprise x86 with Service Pack 1
Windows Vista Ultimate x86 with Service Pack 1

Microsoft Windows Vista x64 (VMs configured with 1 or 2 virtual processors)
Windows Vista Business x64 with Service Pack 1
Windows Vista Enterprise x64 with Service Pack 1
Windows Vista Ultimate x64 with Service Pack 1

Windows XP Professional x86 with SP3 (VMs configured with 1 or 2 virtual processors)

Windows XP Professional x86 with SP2 (VMs configured with 1 virtual processor)

Microsoft Windows XP Professional x64 with SP2 (VMs configured with 1 or 2 virtual processors)

How to Configure/Setup RMS on a Windows 2008 Cluster
1. On each RMS cluster node, ensure that the domain Operations Manager Administrators security group has been added to the local administrators group and that the Cluster service account is a member of the domain Operations Manager Administrators security group.
Note: Having the Cluster service account in the Operations Manager Administrators group is necessary for creating the clustered configuration of RMS.
2. Ensure that each cluster node meets the prerequisites for the Management Server and User Interface components:
- .NET Framework version 3.0 components (Add it from the Features Wizard)
3. Add the SDK and Config service accounts to the Local Administrators group on each node of the RMS cluster.
4. Log on to the cluster node that will be the primary owning node for the RMS with administrative rights.

Cluster preparation
1. In Failover Cluster Management, right click ‘Services and Applications’ and select ‘Configure a Service or Application’.
2. Click next and select ‘Other Server’.
3. Click next and enter the network name for the clustered RMS
4. Click next and select an available storage for cluster group and click next through remainder of wizard.

Install the RMS on the First Node
1. Log on to the cluster node that will be the primary owning node for the RMS with administrative rights
2. Ensure that the RMS cluster group is owned by the node that you are logged onto Proceed with the regular installation wizard
3. On the Completing the System Center Operations Manager 2007 Setup Wizard page, clear the Start the Console checkbox and ensure that the Backup Encryption Key checkbox is selected, then click Finish. The Encryption Key Backup or Restore Wizard will now launch.
Important: Even though the Operations Console has been installed, do not launch the console at this point.
Note If setup fails, it provides you with a value to search on and a link to open the setup log.
4. On the Introduction page of the Encryption Key Backup or Restore Wizard click Next.
5. On the Backup or Restore page select Backup the Encryption Key radio button and click Next.
6. On the Provide a Location page specify a valid path and filename for the encryption key and click Next.
Important: It is critical that the location provided for backing up the encryption key be accessible by all nodes in the cluster.
7. On the Provide a Password page, enter a password to secure the encryption key backup file and click Next to start the backup process.
8. You should now see the Secure Storage Backup Complete page, click Finish.

Install the Secondary Management Servers
In this procedure you will install secondary management servers on all other nodes in the cluster. These servers are secondary Management Servers until this process is complete, at which time they will be able to host the Root Management Server.
1. Log on to each remaining cluster node with the Operations Manager Administrator account.
2. Follow the Install RMS procedures to install the Management Server and User Interface components on each of the other nodes in the Management Group.

Prepare the RMS Cluster Resources
1. In Failover Cluster Management, Right click the RMS server name under ‘Services and Applications’ and select ‘Add a resource -> 4-Generic Service’.
2. From list of services select ‘OpsMgr Health Service’ and click ‘next’ through rest of wizard.
3. Right click newly created resource, choose Properties and enable ‘Use Network Name for computer name’ and add dependencies for the shared disk and network name.
4. Repeat steps 2 and 3 for Config Service and SDK Service.

Create the Virtual RMS
1. Log on to each secondary Management Server computer with an account that is a member of the Administrators group.
2. At a command prompt on each secondary Management Server, type cd <path to Operations Manager installation directory> and then press ENTER.
3. To restore the key to each secondary Management Server, type the following, where <fileshare> is a share accessible by all cluster nodes:
SecureStorageBackup.exe Restore \\<fileshare>\<filename>.bin
Note: You must provide the same password that you entered to encrypt the file on the RMS node.
4. On the SQL server that hosts the OperationsManager database, open the SQL Server Management Studio tool, open the Databases folder and select the OperationsManager database. Right-click to open the context sensitive menu and select Tasks, Back Up to initiate a backup. On the Back Up Database - OperationsManager page, ensure that the Backup type value is set to Full, give the Backup set an appropriate name, and set the Backup set will expire value to a date in the distant future. In the Destination box, for the Back up to value, select Disk and add an appropriate disk location to hold the backup, if one is not already present, and then click OK.
Important: When you run the ManagementServerConfigTool to create the RMS cluster, you are advised to back up the OperationsManager database because irrecoverable damage can be done by creating the RMS cluster.
Note: The OperationsManager database should already be running in the Full Recovery model. For more information, see SQL Server 2005 Books Online.
5. On the RMS server, open a command prompt, type cd <path to Operations Manager installation directory> and then press ENTER.
6. To instantiate the RMS cluster group as a cluster, type the following, where G is the disk resource that is allocated to the cluster group that is being used to create this virtual Root Management Server and where <VirtualServerNetbiosName> is the network name resource allocated to the same cluster group:
ManagementServerConfigTool.exe InstallCluster /vs:<VirtualServerNetbiosName> /Disk:G
The value you enter for <VirtualServerNetbiosName> must be the value that appears in the Name text box located in the Parameters tab of the Properties dialog box for the network name resource.
If InstallCluster runs successfully, the InstallCluster action will return ‘InstallCluster performed successfully’
Note: ManagmentServerConfigTool.exe InstallCluster will install the RMS as a clustered service on every available node in the cluster.
7. In the Cluster Administrator, right click the RMSClusterGroup to open the context menu and select Bring Online. This will bring all the RMSClusterGroup services online.