VMware Knowledge Base Weekly Digest |
Easiest Way to identify the Raid card and SCSI card.
On Raid card the ch-0, ch-1 will be there in port.
on SCSI card it will be ch-A, ch-B
Red Hat Enterprise Linux Advanced Platform
Virtualization Support in Red Hat Enterprise Linux
A guest instance in Red Hat Enterprise Linux 5 Virtualization can be run in one of two different modes: Para-Virtualized (PV) and Fully-Virtualized (FV).
The Para-Virtualized mode provides high performance but requires a Xen-enabled version of the guest operating system.
The Fully-Virtualized mode allows unmodified guest operating systems to be run, but requires the hardware to provide Virtualization enablement (Intel-VT or AMD-V).
Red Hat generally supports different versions of Enterprise Linux as a guest as well as a well-defined list of third party operating systems. Please refer to the virtualization support matrix2 for details on the supported combinations of host and guest operating systems and architectures.
Red Hat also provides a set of optimized "para-virtualized" drivers for fully virtualized guests, that will directly talk to the hypervisor instead of emulated hardware. These drivers require the host operating system to run Enterprise Linux version 5.1 or later. The virtualization support matrix2 provides detailed information about the available PV driver support.
For supported third-party operating systems listed in the virtualization support matrix2, Red Hat will provide commercially reasonable efforts to isolate problems customers encounter and provide solutions for defects in the Red Hat Enterprise Linux Virtualization environment. However, Red Hat is not able to provide any support for the third party operating system itself.
If the problem falls into the domain of the third-party OS, Red Hat will request that the customer contact the OS vendor directly or Red Hat will engage with the vendor on behalf of the customer for further investigation. Please note that a support contract with any third-party OS vendor will be required for continued support.
If the problem falls into the domain of the Red Hat Enterprise Linux Virtualization environment, Red Hat will continue to provide support in accordance with the defined Service Level Agreement associated with the Red Hat Enterprise Linux subscription.
Red Hat will also provide para-virtualized drivers for a selected sub-set of the supported third-party guest operating systems.
1. Please note that running in a virtualized environment may be subject to the third party operating systems license agreement.
2. Please see chart below for details.
Legend
PV Para-Virtualized: Guest kernel optimized for virtualization.
FV Fully-Virtualized: Unmodified guest kernel, requires virtualization hardware support.
Optimized Supported and PV or optimized PV drivers provided.
Supported Supported but no optimized PV drivers provided.
Unsupported Not supported and may not work
N/A Not a valid combination.
Tech Preview Technically possible, but not yet supported.
Red Hat Enterprise Linux 5.2 Virtualization Guest Matrix
Kernel & Processor Architecture
Guest Operating System Enterprise Linux 5
x86-64 Enterprise Linux 5
x86-32 (PAE) Enterprise Linux 5
IA64
Supported Enterprise Linux Combinations
Red Hat Enterprise Linux 3 x86-64 FV Optimized N/A N/A
Red Hat Enterprise Linux 3 x86-32 FV Optimized Optimized N/A
Red Hat Enterprise Linux 3 IA64 FV N/A N/A N/A
Red Hat Enterprise Linux 4 x86-64 PV Optimized N/A N/A
Red Hat Enterprise Linux 4 x86-64 FV Optimized N/A N/A
Red Hat Enterprise Linux 4 x86-32 PV Tech Preview1 Optimized N/A
Red Hat Enterprise Linux 4 x86-32 FV Optimized Optimized N/A
Red Hat Enterprise Linux 4 IA64 PV N/A N/A N/A
Red Hat Enterprise Linux 4 IA64 FV N/A N/A Supported
Red Hat Enterprise Linux 5 x86-64 PV Optimized N/A N/A
Red Hat Enterprise Linux 5 x86-64 FV Optimized N/A N/A
Red Hat Enterprise Linux 5 x86-32 PV Tech Preview1 Optimized N/A
Red Hat Enterprise Linux 5 x86-32 FV Optimized Optimized N/A
Red Hat Enterprise Linux 5 IA64 PV N/A N/A Optimized
Red Hat Enterprise Linux 5 IA64 FV N/A N/A Supported
Supported 3rd Party Operating Systems
Windows Server 2000 32-Bit Supported2 Supported2 N/A
Windows Server 2000 64-Bit Unsupported3 N/A N/A
Windows Server 2000 IA64 N/A N/A Supported
Windows Server 2003 32-Bit Supported2 Supported2 N/A
Windows Server 2003 64-Bit Unsupported3 N/A N/A
Windows Server 2003 IA64 N/A N/A Supported
Windows XP 32-Bit Supported2 Supported2 N/A
Windows XP 64-Bit Unsupported3 N/A N/A
Windows Vista 32-Bit Supported2 Supported2 N/A
Windows Vista 64-Bit Supported2 N/A N/A
1. Support for para-virtualized x86-32 guests on a x86-64 host environment is planned to be fully supported in a later update to Enterprise Linux 5.
2. Red Hat is actively working on optimized PV drivers for Windows guests. These drivers will lead to a significant improvement in the performance of Windows guests and move the support level to "Optimized." Red Hat will announce details on the availability at a later point in time.
3. 64-Bit Windows guests have not been tested and considered lower priority than 32-Bit guests due to a lack of visible adoption. Red Hat plans to add support at a later point in time.
This article describes how dependencies in Microsoft Cluster Server (MSCS) resou...
This article describes how dependencies in Microsoft Cluster Server (MSCS) resources are used.
The basic unit of failover in MSCS is the group. The group is the set of tasks o...
The basic unit of failover in MSCS is the group. The group is the set of tasks or items that must all be on the same node of the cluster for a particular objective to be accomplished. Each group can be on only one node in the cluster at a time, but different groups can be owned by different nodes. Each group contains one or more resources. A resource is a process or data item that is managed and watched by the cluster service of the node on which the group resides. If a resource fails, the cluster service will first attempt to restart the resource, but, if that is unsuccessful, the cluster service will move the group to another node if one is available.
As stated above, the group should contain all resources that must be on the same node for processing to occur. In that sense, the resources of the group are interdependent. More pragmatically, often one resource must be online before another resource can configure itself and start correctly. The second resource is said to "depend" on the other. The Cluster Administrator allows you to designate one resource as depending on another. If this is done, the Cluster service will not start the resource until the one it depends upon is started. If a resource fails, the resources that depend on it will be taken offline, and, if it restarts, the resources will be returned to an online state.
Many of the resource types that ship with MSCS have requirements for dependencies. The only resource types that do not usually depend on another resource are the Physical Disk, and IP Address. The Network Name resource must depend upon an IP address so that it can register the name and address pair with WINS. The other resources have similar requirements.
The cluster service will start resources in the order of their dependencies. In the above example, a typical group going online would start the Disk and IP Address resources first, because they have no dependencies. The Network Name resource would be started next, and after that starts, the File Share resource would start, because both the Disk and Network Name resources are online.
Note that it is not possible to have resources in different groups depend on one another. Because different groups can reside on different nodes, there is no way to guarantee that the dependencies can be satisfied.
You can also define dependencies where none are required to satisfy logical dependencies that you create. For instance, you may not want your Internet Information Server (IIS) virtual web page describing the
Running a backup in Linux
To execute a simple backup using TAR in Linux, enter the following command at the prompt:
tar -cvf /dev/st0 /home<enter>
(home is used as an example of a directory.)
For more information on the different switches for TAR, enter the following command at the prompt:
man tar<enter>
Other useful tape related commands in Linux:
General keyboard shortcuts
Dialog box keyboard shortcuts
If you press SHIFT+F8 in extended selection list boxes, you enable extended selection mode. In this mode, you can use an arrow key to move a cursor without changing the selection. You can press CTRL+SPACEBAR or SHIFT+SPACEBAR to adjust the selection. To cancel extended selection mode, press SHIFT+F8 again. Extended selection mode cancels itself when you move the focus to another control.
Microsoft natural keyboard shortcuts
Accessibility keyboard shortcuts
Windows Explorer keyboard shortcuts
Shortcut keys for Character Map
After you double-click a character on the grid of characters, you can move through the grid by using the keyboard shortcuts:
Microsoft Management Console (MMC) main window keyboard shortcuts
MMC console window keyboard shortcuts
Remote desktop connection navigation
Microsoft Internet Explorer navigation
· e-learning again on subject Exchange Server 2010 be the first one to learn about it. Invest sometimes on the material to be the first mover in exchange server 2010. The following is useful link to help you and it is free.
| Introduction |
|
|
| This one-hour clinic describes Exchange Server 2010 features, deployment scenarios, and development platform options. It also contains descriptions of tools used for managing Exchange Server 2010. · Exchange Server 2010 features · Deployment scenarios · Business-to-business support · Storage, compliance, and development platform enhancements · How RBAC works · Management tools such as EMC, PowerShell, and ECP Users completing this collection should have three or more years of experience working with previous versions of Exchange Server, including the implementation of Exchange Server 2007. They should be familiar with Active Directory, Exchange messaging, and SharePoint and fundamentals of Microsoft Office 2003, Microsoft Office 2007, Windows Server 2003, and Windows Server 2008. It is beneficial if they have experience with a Windows or command-line scripting language. |
|
|
| Objectives |
|
|
| At the end of the course, students will be able to: · Explain the operational flexibility features of Exchange Server 2010 |
From: Kelvin Chow
Sent: Friday, May 08, 2009 8:10 AM
To: Undisclosed recipients
Subject: Microsoft Proactive Information: Exchange Server 2010
Get ahead of the learning curve and explore the training and product information on Exchange Server 2010.
Collection 6899: Exploring Features of Exchange Server 2010
https://www.microsoftelearning.com/eLearning/offerDetail.aspx?offerPriceId=249671
Product Overview
http://www.microsoft.com/exchange/2010/en/us/overview.aspx
Beta information:
http://www.microsoft.com/exchange/2010/en/us/try-it.aspx
Kelvin Chow
Technical Account Manager | Microsoft Services
Subscribe to
Comments [Atom]