How to install and configure a dynamic data center test environment

In the previous article, I introduced an overview of the hardware environment and software environment for building a dynamic data center test environment. I did not mention how to install and configure the software environment (System Center Enterprise, in this article, we will solve these problems.

Review:

Cloud computing is not accessible? Three major impacts of private cloud on IT architecture

Build a hardware and software environment for the Dynamic Data Center test environment

First, let's recall the features that need to be included in the System Center Enterprise suite:

1. System Center Virtual Machine manager 2008 R2: vmm provides a scalable Virtual Machine management mechanism. It can be integrated with Operations Manager to dynamically optimize the performance and resources of virtual machines.

2. System Center Operations Manager 2007 R2: it can be used to monitor hardware, network, and software usage. R2 is further enhanced and expanded to monitor Linux-based systems and applications.

3. System Center Configuration Manager 2007 R2: Provides software distribution, patch updates, configuration management, operating system deployment, software and hardware asset management, remote assistance, and other functions.

4. systems Center Data Protection Manager 2010: provides short-term or long-term backup and recovery for physical and virtual hosts, as well as granular backup and recovery for other Microsoft products, such as exchange.

Systems Center Virtual Machine manager 2008 r2

To install Virtual Machine manager 2008 R2, check the following prerequisites and steps:

1) Capacity Planning: before deploying hyper-V and vmm, make relevant planning solutions based on your needs. For details, refer to the relevant materials on technet. The link is as follows:

Http://technet.microsoft.com/en-us/library/cc793146.aspx

2) Evaluate the current deployment environment and determine whether the prerequisites for vmm deployment are met. The links to relevant documents are as follows:

Http://technet.microsoft.com/en-us/systemcenter/vmm/default.aspx

3) provides a physical or virtual server based on Windows Server 2008 R2 for vmm 2008 installation.

4) install components and services required before vmm deployment, including those on which any SQL Server 2005 SP3 (or later) depends. For more information, see the link to the pre-installed vmm 2008 R2 on technet:

Http://technet.microsoft.com/en-us/library/cc764289.aspx

5) for more information about how to install vmm 2008 R2, refer to the related documents on technet as follows:

Http://technet.microsoft.com/en-us/library/cc793149.aspx

Task after installation in vmm 2008:

After installing vmm 2008 R2, you need to perform the following configuration tasks:

1) first, you can refer to the related documents in the DDC toolkit, including:

"Deploying hyper-V and scvmm 2008 best practices.pptx", and "system center Virtual Machine manager 2008-advanced features360.pptx ".

2) Make sure that the console of vmm 2008 R2 can be started.

3) create one or more server groups as needed.

4) Add the created Cluster to the current host.

5) Make sure that the standby node of the cluster is visible on the host.

6) Create and configure the database server. Add any required vhd and ISO images to the library.

7) create a hardware/software template.

8) Set/configure High Availability options for virtual machines.

9) enable PRO integration and configure other related integration options. For detailed steps, see "system center Virtual Machine manager advanced integration350.pptx" in the DDC toolkit ".

10) If you need to integrate with the VMware ESX Server, you need to add an ESX host or cluster to the vmm group.

　　Systems Center Operations Manager 2007 r2

Install and configure Operations Manager 2007 r2

To install om 2007r2 In the DDC lab environment, follow these steps:

1) In this DDC experiment environment, we only deploy the solution based on a single server and a single management group. For details about other deployment schemes, refer to the links to the relevant deployment schemes on technet as follows:

Http://technet.microsoft.com/en-us/library/bb432145.aspx

The architecture of a single server and a single management group is shown in 1.

▲Figure 1 architecture of a single management group

2) Capacity Planning: before deploying operations manager 2007 R2, make relevant planning solutions based on your own needs. For details, refer to the links on technet as follows:

Http://technet.microsoft.com/en-us/library/dd887701.aspx

3) analyze the current deployment requirements. links to relevant planning and design documents are as follows:

Http://technet.microsoft.com/en-us/library/dd789005.aspx

4) evaluate the current deployment environment and determine whether the prerequisite for the deployment of Operations Manager 2007 R2 is met. The links to relevant information are as follows:

Http://technet.microsoft.com/en-us/library/bb432131.aspx

5) provides a physical or virtual server based on Windows Server 2008 R2 for installing om 2007 R2.

Install components and services required before the deployment of Om 2007 R2, including any components on which SQL Server 2005 SP3 (or later) and SQL reporting services depend.

Operations Manager 2007 R2 after installation:

You have installed a business manager and perform the following steps:

1) links to the configuration operations of Operations Manager 2007 R2 are as follows:

Http://technet.microsoft.com/en-us/library/cc540365.aspx

2) install and deploy the Operations Manager 2007 R2 agent client to each computer to be managed.

3) import and install the management packages related to Operations Manager 2007 R2. You can link to the management package directory site:

Http://pinpoint.microsoft.com/en-US/systemcenter/managementpackcatalog

Query the list of management packages available for download, and select the corresponding management package for download. The following are recommended management packages:

A) Windows Server 2008 (Windows Server)

B) hyper-V

C) DPM 2007.

D) Configuration Manager 2007

E) Operations Manager Management pack

F) SQL Server

G) Internet Information Services (IIS) Manager

4) install the corresponding components on the servers of vmm 2008 R2 and OM 2007 R2 to ensure that the pro function is enabled.

5) established computer and device monitoring.

6) set the corresponding alarms and tasks.

7) create a view.

8) if needed, we can also customize the management package.

Systems Center Configuration Manager 2007 r2

Install configuration manger 2007 R2:

1) before installing and deploying configuration manger, make relevant planning solutions based on your own needs. If necessary, go to technet and refer to the following link for relevant materials:

Http://technet.microsoft.com/en-us/library/bb735860.aspx

2) evaluate the current deployment environment and determine whether the prerequisite for configuration manger deployment is met. The relevant information links are as follows:

Http://technet.microsoft.com/en-us/library/bb694113.aspx

3) provides a physical or virtual server based on Windows Server 2008 R2 for SCCM installation.

4) install the components and services required before configuration manger deployment, including any security updates, service packs, SQL Server 2005 SP3 (or later), and the components on which it depends. For more information, see the related documentation for the pre-Installation of configuration manger 2007 R2 on technet. The link is as follows:

Http://technet.microsoft.com/en-us/library/bb680397.aspx

In addition, to install configuration manger 2007 R2, we must first install configuration manger 2007 SP1 or SP2, and then apply the update of R2.

5) in this DDC experiment environment, we use a single site and single server deployment solution. For more information about this solution, see the link to the relevant documentation on technet as follows:

Http://technet.microsoft.com/en-us/library/bb680961.aspx

Tasks after Configuration Manager 2007 R2 is installed:

1) first, make sure that the Site Server of Configuration Manager has been correctly installed. Run the Configuration Manager 2007 R2 console to check the status of the Site Server.

2) For more information, see Configuration Manager single site configuration tasks on technet. Generally, we recommend the following configuration tasks:

A. Specify the Configuration Management Boundary

B. Configure the default Management points on the site

C. Configure the site system

D. Configure the required site system role. The role is as follows:

I. configmgr Site Server

Ii. configmgr Site System

Iii. configmgr management point

Iv. configmgr Software Update point

V. configmgr reporting point

Vi. configmgr distribution point

E. Configure the status report and SQL Server reporting of Site-related components.

3) Check whether Configuration Manager functions are normal

4) Create and modify a set.

5) Deploy the Configuration Manager Client:

A. Configure the management point.

B. Determine the server locator point if necessary.

C. Configure fallback status point and reporting point.

D. Install the configmgr client.

E. Configure the client proxy.

6) configure the operating system deployment function ..

7) configure the software distribution function.

8) configure the patch distribution function.

System Center Data Protection Manager 2010

Systems Center Data Protection Manager (DPM) 2010 is a component in the Systems Center product suite. It can provide unified protection functions for Windows servers, such as SQL Server, exchange, Sharepoint, virtual machines, and file servers. It can also protect desktop clients and laptops Based on Windows operating systems. DPM 2010 not only provides disk and tape-based protection, but also supports backup and recovery using storage in the cloud. Enhanced hyper-V Protection in DPM 2010, including protection for host machines and virtual machines.

Install system center Data Protection Manager 2010:

1) before installing and deploying Data Protection Manager, make relevant planning solutions based on your own needs. If necessary, you can go to technet to refer to the following links for relevant materials:

Http://technet.microsoft.com/en-us/library/ff399135.aspx

2) evaluate the current deployment environment and determine whether the prerequisites for Data Protection Manager deployment are met. Related Information on technet is as follows:

Http://technet.microsoft.com/en-us/library/ff399554.aspx

3) provides a physical or virtual server based on Windows Server 2008 R2 for installing DPM.

4) install the components and services required before Data Protection Manager deployment, including any security updates, service packs, SQL Server 2008 SP1 (or later), and the components on which it depends. For more information, see the link to the documentation for pre-installing Data Protection Manager 2010 on technet as follows:

Http://technet.microsoft.com/en-us/library/ff399515.aspx

5) in this DDC experiment environment, we use a single server and a local database deployment solution. For more information about this solution, see related documents on technet.

Tasks after DPM 2010 installation are completed:

1) First, ensure that the Data Protection Manager 2010 server has been correctly installed. Run the DPM console to check whether the status and functions of the Site Server are normal.

2) You can refer to the links to related documents on technet as follows:

Http://technet.microsoft.com/en-us/library/ff399138.aspx

Complete the subsequent configuration.

3) use the DPM console to add an additional disk (which can be a disk array) for the storage pool. You can also configure the tape library if needed.

4) create a DPM protection group to protect each storage group.

5) Deploy the DPM client proxy to protect each server and client that requires backup and recovery.

6) collect the servers and clients installed with agents, create protection groups for them, and customize the content and scheduled tasks to be protected.

Summary

So far, all the systems center components required by DDC have been installed. Most of the deployment of the DDC toolkit is based on code writing and debugging, and the content and steps are too complex, therefore, I will not repeat it too much here, but the reference documents here are all in E, which is not very convenient to chew on.

 

[It168 special draft]