Showing posts with label server. Show all posts
Showing posts with label server. Show all posts

Friday, February 6, 2009

Installing Windows Hyper-V Server 2008

How to install Microsoft Hyper-V Server 2008 and use the HVConfig command line configuration tool.

Microsoft Hyper-V Server (HVS) 2008 is a hypervisor solution that is based on Windows Server 2008 and Hyper-V. Unlike Windows Server 2008 which supports the installation of many different roles, Microsoft Hyper-V Server 2008 is standalone virtualization software that does not support any additional roles.

The installation of Microsoft Hyper-V Server 2008 will be very familiar to those of you who have installed a Windows Server 2008 edition because it uses a similar wizard-driven installation. Here are the steps you must follow to install Microsoft Hyper-V Server 2008.

Friday, January 30, 2009

Predeployment I/O Best Practices: SQL Server Best Practices Article

The I/O system is important to the performance of SQL Server. When configuring a new server for SQL Server or when adding or modifying the disk configuration of an existing system, it is good practice to determine the capacity of the I/O subsystem prior to deploying SQL Server. This white paper discusses validating and determining the capacity of an I/O subsystem.

CoreConfigurator - use a graphic interface to configure Windows Server 2008 Core edition!

Smart-X has published a new version, 1.2.0.2 of their tool, CoreConfigurator - use a graphic interface to configure Windows Server 2008 Core edition!

CoreConfigurator is free for personal use and free for non commercial use.




Active Directory on separate volumes?

I have seen numerous discussions with people on the benefits and drawbacks of putting Active Directory files and folders on a separate volume or even on several separate volumes. Time to makes some things clear!

Transitioning your Active Directory to Windows Server 2008

You might be running Windows Server 2003 and Windows Server 2003 R2 Domain Controllers at the moment and you're looking to replace these servers with Windows Server 2008 Domain Controllers to utilize the new features of Windows Server 2008. You might also be looking to replace your aging Windows Server 2003 and Windows Server 2003 R2 Domain Controllers with spanking new Windows Server 2008 Domain Controllers, while keeping your Active Directory running smoothly.

This post intends to help you with this transition in a structured, balanced and thorough way.

Exchange Servers in Hardware Virtualization Environments

Microsoft Support Policies and Recommendations for Exchange Servers in Hardware Virtualization Environments

This Technet page provides the Microsoft support policies for running currently supported versions of Microsoft Exchange Server in production in a hardware virtualization environment.

Wednesday, January 28, 2009

Creating OS VHDs from Windows Server 2008 R2 OS media

A tutorial about the procedure of getting the setup image of Windows Server 2008 R2 into a VHD.

http://www.ravichaganti.com/blog/?p=314

And the follow up, Enabling a captured VHD to boot in a Hyper-V Virtual Machine.

Tuesday, January 27, 2009

How do Cluster Shared Volumes work in Windows Server 2008 R2?

I have found today the description of the new Cluster Shared Volumes that will be availabe in Windows Server 2008 R2, a feature designed for Hyper-V 2.0, to remove the need for 1 LUN per VM:

http://windowsitpro.com/article/articleid/100867/q-how-do-cluster-shared-volumes-work-in-windows-server-2008-r2.html

You need to register/login to see the answer.

Monday, January 26, 2009

Auto notification for failover of a server and restart of SQL Server services

Learn how you can monitor the SQL Server instances for failover of a cluster or a restart.

http://www.mssqltips.com/tip.asp?tip=1663

Friday, January 23, 2009

Hyper-V Server 2008 Local Management scripts / UI

A very nice addition to the configuration script integrated in Hyper-V Server, HVS2008 UI is a CodePlex developed script that helps you manage a Hyper-V Server host.

http://www.codeplex.com/HVS2008UI

Is developed by Ravikanth Chaganti's and his blog can be found here.

IIS 7.0 Configuration Reference - online library

The IIS development team has put together a brand new technical reference on IIS 7.0 configuration.
This vast library comprehensively details all IIS 7.0 configuration settings in Windows Server 2008, including configuration collections, elements, and attributes. You can sort the configuration settings alphabetically to easily find what you are looking for or by browsing the schema structure. Each configuration topic provides sections such as an overview, examples of how to configure the configuration, setup instructions, configuration details, and code and script samples – including AppCmd.exe, C# .NET, Visual Basic .NET, JavaScript, and VBScript.
This is the only online reference you’ll need for IIS configuration, so check out the comprehensive documentation at http://www.iis.net/ConfigReference today!

Wednesday, January 21, 2009

Hyper-V 2.0: Live Migration setup on Windows Server 2008 R2 (beta 1)

Now that Windows Server 2008 R2 beta 1 is available, I decided to give it a spin. The installation of the Hyper-V role and the Failover Cluster feature is very similar to the current version and is not discussed in this article. This article does not discuss best practices. It merely illustrates the setup process that enables you to live migrate virtual machines with Hyper-V 2.0.

http://blog.baeke.info/blog/_archives/2009/1/14/4057251.html

Tuesday, January 20, 2009

Planning virtualization of servers with Hyper-V, part 2

The part 2 of this kind of tutorial talks about creating the list of applications that need to be virtualized. Part 1 is available here:

Step 2: Create the List of Applications
Before designing and implementing the infrastructure, determine which applications the infrastructure needs to support. This information will be used in later steps to determine resource requirements and, ultimately, to design the physical host infrastructure.

Determine Application Compatibility

The first step in deciding which applications to virtualize is to consider the specific technical requirements for the application or operating system and map that against any constraints in the virtualization technology. Factors include:
  • Processor architecture requirements.
  • The number of required processors.
  • Memory requirements.
  • Graphics adapter requirements.
  • Special hardware requirements.
Windows Server 2008 Hyper-V has the following constraints and limitations:
  • Is available with Windows Server 2008.
  • Requires specialized hardware chipset (Intel VT or AMD-V).
  • No access to USB devices or hardware such as Host Bus Adapters (HBAs).

Document the List of Applications

Most organizations run multiple operating systems, applications, and services that IT may consider moving to a virtual environment. To ensure that no important considerations are overlooked, a spreadsheet or table should be created that lists the applications, whether they are compatible with virtualization, and whether it is appropriate to virtualize them. Such a job aid could also include additional notes, requirements, and concerns. Filling out such a table can provide a very helpful structure to the process of planning for virtualization.

In the next article, i will cover the step 3, Determine Resource Requirements.

Planning virtualization of servers with Hyper-V, part 1

For a succesful implementation of virtualization of your existing servers you need to plan your moves carefuly. To keep things short, these are the steps you need to take:

  1. Determine the Virtualization Scope
  2. Create the List of Applications
  3. Determine Resource Requirements
  4. Select the Backup Approach for Each Application
  5. Applying Fault Tolerance
  6. Summarize and Analyze the Application Requirements
  7. Select a Form Factor for the Hosts
  8. Map Guests to Hosts
  9. Determine the Host Backup Approach
  10. Design Fault Tolerance
  11. Design the Storage Infrastructure
  12. Design the Network Infrastructure

Starting with step 1, determining the virtualization scope, you have a few options:

  1. Enterprise Deployment - this option involves deployment of virtualization technology to the entire organization, including corporate data centers.
  2. Hub Deployment - this option involves deployment of virtualization technology to one or more hub locations. Hubs are physical locations where there are concentrations of users, computers, and/or network connectivity. Resources within the hub may be provided to additional satellite locations.
  3. Satellite Deployment - this option involves deployment of virtualization technology to one or more satellite locations. Satellite locations are smaller than enterprise or hub environments and often have limited network connectivity to the rest of the environment because of bandwidth constraints.

In part 2, i will examine the next step, creating the list of applications that need to be virtualized.

Things to know before you build an OpenFiler SAN

These are some important tips that you may want to know before you go and choose the hardware that will run the OpenFiler software, if you do not want OpenFiler to be just a play toy:

  1. Do not run OpenFiler on a desktop PC.
  2. If you must use a desktop PC, use only Intel hardware (CPU, mainboard and network cards). Leave away any system that has nVidia, ATI, VIA or AMD hardware. The network cards can also be from Broadcom. Do not use network cards from Realtek, Marvell or others, put them on your usual desktops, not in your SAN.
  3. Choose only "jumbo frames" enabled network cards from Intel/Broadcom. Search also for "teaming" or LACP or 802.3ad capable network cards. Do not forget that the switch also needs to know about these features.
  4. Check all the chosen hardware against the RedHat HCL - https://hardware.redhat.com/. Do not use the hardware if is not on the RHEL HCL.
  5. Do not use the latest and greatest of hardware, go for at least a year old hardware before the current kernel.
  6. If you decide to buy some server (new or used), choose a server from a big server vendor: Dell, IBM, HP, Fujitsu-Siemens, Supermicro and others.
  7. Do not use the RAID features implemented in chipset or add-on cards, expose every disk to the OpenFiler and use the software RAID implemented in OpenFiler. Buy simple add-on card for adding drives to the OpenFiler box, without RAID. If you do not find cards without RAID, disable the onboard RAID features.
  8. For SCSI, use Adaptec, LSI Logic or AMI controllers. For SATA, use Silicon Image, Marvell or Intel AHCI controllers. Avoid JMicron and the likes.
  9. Do not use USB or FireWire attached disk drives to use them as the main storage! Use them only for backup. Using OpenFiler on USB and FireWire disks will eventually result in tears.
  10. Try to use SCSI/SAS disks. If you use SATA disks, use Seagate ES, Western Digital Enterprise/Raptor or Hitachi drives. If you must go with other brands/models, search for NCQ enabled drives.
  11. Size your power supply carefully, SATA drives are particularly sensitive to voltage drops on the 12v rail. Choose a high quality and powerful PSU.
  12. If you value your data, you must use a UPS on your OpenFiler system.
  13. For the file system, use XFS. XFS is extremely resilient to faults, dirty shutdowns and other maladies that can cause data corruption.
  14. Install Openfiler on a RAID1 set of drives, if one drive will fail your SAN will continue to work.

Keep in mind that OpenFiler is designed to store information. Sometimes very important information. Reliability is therefore the most important aspect of using OpenFiler, unless you don't mind losing data.

Make your own (free) NAS or SAN

If you want to build your own cheap NAS or SAN, there are available a couple of software packages that can transform a regular PC into a full fledged NAS or SAN (or both).

This is a list of the free NAS or SAN software that i found:

  1. FreeNAS - http://www.freenas.org/
  2. OpenFiler - http://www.openfiler.com/
  3. unRAID - http://lime-technology.com/
  4. ClarkConnect - http://www.clarkconnect.com/

There are others, of course, but these are the most prominent packages i have found after a few days of searching and reading on the net. And there are free.

The most advanced is OpenFiler, which is based on rPath Linux. In the past CentOS was used. Some people regret the transition to rPath.