1) What is DHCP? If primary DHCP failed wht role will work on Backend..?

Introduction
Small- and medium-sized networks often have a single DHCP server, which can become a single point of failure for
a large number of hosts on the network. When the DHCP server goes off-line, DHCP client hosts lose their
addresses and ability to communicate with the rest of the network. Since most desktop computers, and even some
servers, get their networking configuration via DHCP, such an outage can result in a lot of downtime.
If the network has a Unix infrastructure, theres a good chance that its using the Internet Systems Consortium
(ISC) DHCP server, which is widely available on Linux and BSD systems.
Starting with version 3.0, the ISC DHCP server offered failover capabilities that allow network administrators to
offer a more robust DHCP service. A failover setup requires a little care, but its fairly straightforward to
implement.
A simple starting point
Before getting to the failover setup, lets establish a simple baseline DHCP configuration with no frills.
#
# /etc/dhcpd.conf for simple network
#

authoritative;
ddns-update-style none;

subnet 192.168.200.0 netmask 255.255.255.0 {
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.200.255;
option routers 192.168.200.1;
option domain-name-servers 192.168.200.1;
pool {
max-lease-time 1800; # 30 minutes
range 192.168.200.100 192.168.200.254;
}
}
With this configuration, our server will act as the authoritative DHCP server on the 192.168.200.0 subnet, handing
out addresses from 192.168.200.100 to 192.168.200.254 to any host that asks for one.
The problem
Our configuration will work fine until the DHCP server goes off-line. The cause of its demise might be a hardware
failure, a power outage, or even an OS upgrade; it doesnt matter. Once its gone, all DHCP client hosts will lose
their network configurations within 30 minutes (our maximum lease time).
We could just bring another DHCP server online in its place, but the information about leases will be lost, possibly
forcing clients to acquire new addresses. In that situation, clients would have to break any existing network
connections. In some cases, local X sessions would also break. (If youre bored sometime, try changing the
hostname of your machine when running a live X desktop. The recovery process can be amusing.)
Alternatively, we could plan for a downtime by increasing lease times from 30 minutes to the better part of a day.
That would reducebut not completely removethe risk of any given client having its lease expire while the
server is off-line, but any newly arriving client wont get an address.
Configuring the primary
Once you identify the machine that will act as the secondary DHCP server (or the new primary, if youre going to
demote the old server), youll want to make sure the clocks on the two machines are in sync. Timestamps are very
important to dhcpd! After that, its time to configure it. Using the simple configuration above, well add the bits
necessary to upgrade it to serve as the primary in a failover situation:
The failover peer section that identifies the primary and secondary servers; in the
example below, its called dhcp-failover, but it can be any string that works for you.
The example identifies the two DHCP servers by address, but you can use DNS names
as well. In the past couple years, TCP ports 647 (primary) and 847 (peer) have
emerged as the standard bindings for DHCP failover. Its worth noting that as recently
as 2005, the dhcpd.conf(5) man page used ports 519 and 520 in its failover example,
but 647 and 847 look like good choices as of 2008.
The dhcpd.conf(5) man page says that the primary port and the peer port may be the
same number. Thats the configuration I deploy, using the port 647 for both the
primary and the peer.
The pool sections for which the failover pair is active; in our example, we have only
one pool section, so we add a reference to our failover peer set.
#
# /etc/dhcpd.conf for primary DHCP server
#

authoritative;
ddns-update-style none;

failover peer "dhcp-failover" {
primary; # declare this to be the primary server
address 192.168.200.2;
port 647;
peer address 192.168.200.3;
peer port 647;
max-response-delay 30;
max-unacked-updates 10;
load balance max seconds 3;
mclt 1800;
split 128;
}

subnet 192.168.200.0 netmask 255.255.255.0 {
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.200.255;
option routers 192.168.200.1;
option domain-name-servers 192.168.200.1;
pool {
failover peer "dhcp-failover";
max-lease-time 1800; # 30 minutes
range 192.168.200.100 192.168.200.254;
}
}
Configuring the secondary
For our simple network, the configuration for the secondary is quite similar to that of the primary. The only
significant differences are in the failover peer definition: theres a secondary declaration, the mclt and split
declarations are omitted, and the local and peer addresses are switched.
#
# /etc/dhcpd.conf for secondary DHCP server
#

authoritative;
ddns-update-style none;

failover peer "dhcp-failover" {
secondary; # declare this to be the secondary server
address 192.168.200.3;
port 647;
peer address 192.168.200.2;
peer port 647;
max-response-delay 30;
max-unacked-updates 10;
load balance max seconds 3;
}

subnet 192.168.200.0 netmask 255.255.255.0 {
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.200.255;
option routers 192.168.200.1;
option domain-name-servers 192.168.200.1;
pool {
failover peer "dhcp-failover";
max-lease-time 1800; # 30 minutes
range 192.168.200.100 192.168.200.254;
}
}
The folks at ISC note that the DHCP failover protocol is still under development, which makes it sort of a moving
target. As a result, they strongly suggest that the primary and secondary servers both be running the same version
of dhcpd.
SELinux notes
As noted, running dhcpd in failover mode involves opening a TCP port for communication with the peer server. The
SELinux policy distributed with CentOS 4 and 5 allows dhcpd to send packets over ports 647 and 847, but youll
need to tweak the policy if you want to use different ports.
The instructions below apply specifically to CentOS 4 (and, by extension, to Red Hat Enterprise Linux 4), though I
suspect that they would also work on Fedora Core 3 and 4.
1. Install the selinux-policy-targeted-sources rpm, if its not already on your system.
2. Open a command prompt in the /etc/selinux/targeted/src/policy directory.
3. Create or edit domains/misc/local.te using your editor of choice. Add a single line:
4. allow dhcpd_t port_t:tcp_socket name_bind;
5. Run make reload to install your modified policy.
What the logs will show
Once both servers are configured and working, the system logs will show when one goes offline. Heres what
shows up when the primary goes down:
Nov 6 19:50:51 secondary dhcpd: failover peer dhcp-failover: I move
from normal to communications-interrupted
When the primary comes back, the log will say (among other things)
Nov 6 19:51:37 secondary dhcpd: failover peer dhcp-failover: I move
from communications-interrupted to normal
The other main difference in the logs will be the presence of pool reports. In failover mode, dhcpd will try to
ensure that the primary and secondary servers each have a similar number of free dynamic leases for each pool
declared in the configuration file. As the servers work to keep that balance, theyll occasionally log their status.
Nov 6 20:27:09 secondary dhcpd: pool 98e82b8 192.168.200.0/24
total 155 free 38 backup 37 lts 0
In this case, 75 of the 155 of the addresses we declared eligible for dynamic assignment are still available. The
primary holds 38 in reserve, the secondary 37. As long as the values for free and backup differ by no more than
one, things are good. Should they vary by two or more (with a resulting non-zero lts), the pool addresses will be
juggled until balance is restored.
Now, the single point of failure is gone. So go hog wild: install those security patches on your DHCP server that
youd put off because you didnt want to lose leases!
2) What is DNS ? How many zones are there in DNS?
The Domain Name System is a hierarchical system for naming that is constructed on a distributed database
containing mappings of the DNS names of computers and other network resources to their IP addresses. DNS
allows computer users and administrators to use easy-to-remember names when locating Internet resources and
computers, such as "google.com," rather than a numerical IP address, such as "74.125.65.99." There are three
standard DNS zones

Standard Primary Zones
This is a zone that hosts a read and write copy of the DNS zone in which records are produced and
administered. Only one primary server per zone is allowed, and only this server loads and hosts the
master copy of the zone. In addition, this server is also the only one allowed to process dynamic updates
and zone changes. The primary server is generally located in a readily accessible location to allow
administration of the zone file.
Standard Secondary Zones
One or more servers can be used to store a read-only copy of the primary DNS zone. Information is
received from the primary through a zone transfer, which copies the zone file from the primary server to
the secondary server. These zone transfers can be full--meaning it transfers the complete zone contents
each time--or incremental--meaning it transfers only changed information since the last transfer.
Performing incremental transfers can reduce network traffic between servers. When creating a secondary
zone, you must provide the address of one or more master server from which you wish to copy the zones.
Reverse Lookup Zones
While most DNS queries are forward queries, which means requesting an IP address based on providing a
name, reverse lookup zones (also called in-addr.arpa domains ) allow determination of a hosts name by
providing its IP address. Network applications frequently use reverse lookup queries to verification
purposes, or to troubleshoot and monitor DNS functionality.
Stub Zones
DNS servers with Windows Server 2003 or Windows Server 2008 can also be configured as stub zones.
These servers maintain a copy of the zone that only contains records necessary to identify authoritative
DNS servers for its zone. Think of it as a pointer used to provide DNS resolution efficiency. Using the stub
zones list of name servers, a DNS server can resolve queries without querying the Internet or other
internal root servers.

What are DNS Records?
DNS records or Zone files are used for mapping URLs to an IPs. These records are located in the DNS server. It
connects your website with the outside world. When the URL is typed on the browser it is being forwarded to your
DNS servers and then get pointed to webservers. These webservers serve the website mentioned in the URL or the
Email server which handles the incoming email.
Types of DNS Records:
NS Record:
Name server All the servers that are listed in the NS record are stated as the authoritative name servers for a
particular domain.
MX Record:
MX record is considered as the Mail Exchange Record. This MX record states the location where the mail is being
sent. Apart from IP address MX records contains fully qualified domain names.
A Record:
A record is the Address Record. This assigns an IP address for a domain or a subdomain name. Usually A record will
be an IP address.
CNAME Record:
Canonical Name Record makes one domain name as an alias of another domain name. Usually the aliased domain
acquires all the subdomains and DNS record of the original domain. CNAME redirects request to another record.
CNAME will be fully qualified domain name.
TXT Record:
TXT Record allows inserting arbitrary text into a DNS record. These TEXT Record adds SPF records to a domain.
TIL Record :
TIL is nothing but Time to Live. This TIL value sets the tenure of information which will be good when a recursive
DNS server queries for your domain name information Usually the value is set in seconds.
SOA Record:
This State of Authority record specifies the DNS server that provides authoritative information about the domain
name, domain administrator email, domain serial number, along with several timers in relation to refreshing the
zone.
What is BitLocker? Why we need bit locked in Windows system ? If system crashed how you can retrieve that
data ?
Windows BitLocker Drive Encryption is a new security feature in Windows Vista and later that protects files on your
computer in the event that anyone tampers with the computer's startup process. BitLocker can leverage the
Trusted Platform Module (TPM) security hardware to guard data and system files in the Windows operating
system directory, and also protects early boot component integrity. Encrypting the entire Windows volume with
BitLocker can help prevent others from seeing your files, even if your computer is stolen or a hard disk removed. At
Indiana University, BitLocker may provide a useful tool for meeting the requirements for protecting confidential
data described in Protecting Data.
What does BitLocker not do?
BitLocker does not protect the computers contents while Windows is running. Again, BitLocker is built for offline
attacks, once the operating system is up and running. Windows 7 and Vista will protect your data from
unauthorized access. When 7 (and Vista) is up and running, unauthorized access can come in the form of:
1. A malicious user trying to log onto the local computer. Windows 7 (and Vista) can protect itself by
enforcing strict password policy and complexity. Please ensure that if your data is important enough to
encrypt, that you also require complex passwords and/or two factor authentication. Two factor
authentication takes the simple passwords or easy to guess passwords out of the equation so that they
are no longer a risk.
2. A malicious user connecting to the computer over the network to harvest data from the local computer. If
the user has access to your physical network, the malicious user can try to connect to your machine over
the network. Again, strict user permissions on the local machine and on your network as a whole, will
prevent malicious users from accessing your network.
Windows BitLocker Drive Encryption is a data protection feature available in Windows Vista Enterprise and
Windows Vista Ultimate for client computers and in Windows Server 2008. BitLocker provides enhanced
protection against data theft or exposure on computers that are lost or stolen, and more secure data deletion
when BitLocker-protected computers are decommissioned.
Data on a lost or stolen computer is vulnerable to unauthorized access, either by running a software attack tool
against it or by transferring the computer's hard disk to a different computer. BitLocker helps mitigate
unauthorized data access on lost or stolen computers by combining two major data-protection procedures:
Encrypting the entire Windows operating system volume on the hard disk. BitLocker encrypts all user files and
system files in the operating system volume, including the swap and hibernation files.
Encrypting multiple fixed volumes. Once the operating system volume has been encrypted, BitLocker can encrypt
other volumes. This feature requires a computer running Windows Vista Enterprise with Service Pack 1 (SP1),
Windows Vista Ultimate with SP1, or Windows Server 2008.
Checking the integrity of early boot components and boot configuration data. On computers that have a Trusted
Platform Module (TPM) version 1.2, BitLocker uses the enhanced security capabilities of the TPM to help ensure
that your data is accessible only if the computer's boot components appear unaltered and the encrypted disk is
located in the original computer.
Bitlocker works either using a TPM chip and/or a USB key. Now there are three methods of Recovery incase of a
disaster.
1.Recovery password
2.Recovery key file
3.Data Recovery Agent
The last one is by far the best method if you are part of Active Directory. It's pretty automatic. The second one is
the best method for all other cases IMO.
In the case of Bitlocker, recovery keys are called protectors and the Setup Wizards prompts you to make a copy of
the Recovery key.
How to use Bitlocker Data Recovery Agent to unlock Bitlocker Protected Drives
Data recovery agents are individuals whose public key infrastructure (PKI) certificates have been used to create a
BitLocker key protector, so those individuals can use their credentials to unlock BitLocker-protected drives. Data
recovery agents can be used to recover BitLocker-protected operating system drives, fixed data drives, and
removable data drives. However, when used to recover operating system drives, the operating system drive must
be mounted on another computer as a data drive for the data recovery agent to be able to unlock the drive. Data
recovery agents are added to the drive when it is encrypted and can be updated after encryption occurs.
Pre-requisites:
To use DRA for BitLocker, make sure the GPO for Unique ID is enabled.
To Configure the GPO,
1. Expand Computer Configuration, Administrative Templates, Windows Components, BitLocker Drive
Encryption.
Provide Unique Identifiers for your organization
Enable this Policy (see screenshot below).
For BitLocker Identification Field you can give your company name or any name.
Make sure BitLocker Identification Field and Allowed BitLocker Identification field are the same.

When do we use Bitlocker DRA?
In Windows 7, we introduced feature of Bitlocker DRA which can be used to unlock fixed data drives and
removable data drives.
Generally when we encrypt the USB flash Drives or fixed data drive, we give a password to unlock the drive. By
using a file based certificate we get an additional protector for the drive and we can use it to unlock the drive.
When you connect to a Windows 7 client machine and Open Control Panel > Bitlocker Drive Encryption, you will
see all your Data drives.
Open Certificate Manager on the client computer.
Expand Personal and click Certificates. Right Click on Certificates and Select All Tasks and then select Request New
certificate.

Under the Certificate Templates, select Bitlocker DRA certificate template.
If you do not have the bitlocker DRA template, you can copy the Key Recovery Agent template and then add
Bitlocker Drive Encryption and Bitlocker Drive Recovery Agent from the application policies.
NOTE: In case you do not see attributes listed under the Application polices, you should re-login to the domain
controller using a schema admin account and install the Bitlocker feature. The Bitlocker Drive Encryption and
Bitlocker Data Recovery Agent application policies will be listed upon installation of the bitlocker feature.


Install the certificate on the computer.

Export the Certificate.

Save the certificate to a location on your computer.


Now we can use a Group Policy to apply the certificate to all machines in the OU.

Open Group Policy Management Console and then add the bitlocker DRA.
Expand Computer Configuration > Windows Settings > Security Settings > Public Key Policies > Bitlocker Drive
Encryption.
Right click on Bitlocker Drive Encryption and then click Add Data Recovery Agent.
Note:
If a user wants to add additional Bitlocker DRA for his drive, he can add it by using the local security policies.
1. Open Group Policy Management Editor (gpedit.msc) on Windows 7 client machine.
2. Expand Computer Configuration > Windows Settings > Security Settings > Public Key Policies >
Bitlocker Drive Encryption.
3. Right click on Bitlocker Drive Encryption and then click Add Data Recovery Agent

Click Browse Folders and then select the exported certificate (.DER) file which we exported above.


After adding the DRA, go to windows 7 client machine.
After Adding the certificate, run gpupdate /force on the client machine.
On Windows 7 client machine, open an elevated command prompt and use the following commands:
To get the protectors, run:
C:\>manage-bde -protectors -get f:
BitLocker Drive Encryption: Configuration Tool version 6.1.7600
Copyright (C) Microsoft Corporation. All rights reserved.
Volume F: [New Volume]
All Key Protectors
Numerical Password:
ID: {FB4FF4B1-AAA3-4BB6-937E-80E7241CA2F2}
Password:
526108-505340-456258-529034-347050-022297-147796-530310
Password:
ID: {96C170CF-65AF-42A7-BEF8-0AD21667C02B}
Smart Card (Certificate Based):
ID: {7BBF31F5-DEBD-4C24-B76F-012855B4EF39}
Certificate Thumbprint:
09141e2c459016b5c51754503956c1d62efeee62
Data Recovery Agent (Certificate Based):
ID: {E1749014-6760-4501-9A48-58152A587279}
Certificate Thumbprint:
1e66a3476615d9a1e51f56aec49024bb34b8a688

To lock the drive, use:
C:>manage-bde -lock f:
BitLocker Drive Encryption: Configuration Tool version 6.1.7600
Copyright (C) Microsoft Corporation. All rights reserved.
Volume F: is now locked
To unlock the device, using the certificate thumbprint, use:
C:\>manage-bde -unlock f: -cert -ct 1e66a3476615d9a1e51f56aec49024bb34b8a688
BitLocker Drive Encryption: Configuration Tool version 6.1.7600
Copyright (C) Microsoft Corporation. All rights reserved.
The certificate successfully unlocked volume F:.
5) What is WDS ? What is the use of WDS?
Windows Deployment Services (WDS) enables you to deploy Windows operating systems over the network, which
means that you do not have to install each operating system directly from a CD or DVD.
Benefits of Windows Deployment Services
1. Allows network-based installation of Windows operating systems, which reduces the complexity and cost when
compared to manual installations.
2. Supports deploying images for mixed environments including Windows 7and Windows Server 2008 R2 through
Windows 8.1and Windows Server 2012 R2.
3. Uses standard Windows Setup technologies including Windows Preinstallation Environment (Windows PE), .wim
files, and image-based setup.
4. Transmits data and images by using multicast functionality.
5. Allows you to create images of a reference computer using the Image Capture Wizard, which is an alternative to
the ImageX tool.
6. Allows you to add driver packages to the server and configure them to be deployed to client computers along
with the install image.
6) What is MDT ? What is the use of MDT?
The Microsoft Deployment Toolkit (MDT) provides a unified collection of tools, processes, and guidance for
automating desktop and server deployments. In addition to reducing deployment time and standardizing desktop
and server images, MDT offers improved security and ongoing configuration management.
The Microsoft Deployment Toolkit is a product in the solution accelerator lineup. And how can it help network
administrators? In a word, automation. MDT 2010 provides one console with a complete toolset and
documentation that will help you deploy both Windows 7 and Windows Server 2008 release 2.

The latest release, MDT 2010 Update 1 includes Office 2010 and enhanced Windows 7 driver support. And if youre
in the camp that would like to provide your end user community with greater control and responsibility, the
Configuration Manager tool will allow you to give them the ability to initiate and customize their own
deployments. The wizard will walk them through the process step-by-step taking automation to another level.

MDT Systems Requirements
To use Microsoft Deployment Toolkit, youll need the following:

Windows Server 2008
Windows Deployment Services
Windows Automated Installation Kit for Windows 7
Windows 7 DVD/source
Microsoft Deployment Toolkit 2010
How Does MDT Work?
Most organizations will have a typical stable of software that they deploy. This could include the operating system,
hardware device drivers, software patches or updates, and of course, applications. With MDT, you add all of these
to the collection of available software or deployment packages.

The administrator decides which OS and other software should be included in each package, then includes
password and product key information. Users will use a custom image called the Windows PE image to boot up
(this can also be burned to a CD) and log into the network. They can then install packages from the MDT server.

How MDT is differ from WDS?
MDT is creating his boot images when you update the deployment share. From here you can either burn the
images to a CD or import them in WDS so client boot from network. If you want your clients to use OS images from
MDT you need to use MDT boot images.
If you want your clients to use OS images from WDS you need to import a boot image in WDS from the Win 7 or
2008 DVD. I recommend you always use MDT for deployment and keep the WDS server just so clients can boot
from the network.
Question: How Poweredge server is diffrent from other server?
More about the Dell PowerEdge R710:-
The Dell PowerEdge R710 is designed with organic growth and scalability in mind. Thanks to Dell's system
commonality, managing and upgrading the R710 is simple, allowing you to quickly react to changed business
circumstances. Logical component layout also makes for a straightforward installation and redeployment
process.
The Dell PowerEdge R710 is a 2U rack server that can support up to two quad- or six-core Intel Xeon 5500 and
5600 series processors, which are equipped with technology that adapts to your software in real time to process
more tasks simultaneously. 18 memory slots allow for a maximum of 288GB of memory, allowing the R710 to
support and memory-intensive task you can throw at it. The PowerEdge R710 can support up to eight SATA or
SAS hard drives, giving you up to 12TB of internal storage.
Additionally, the Dell PowerEdge R710 provides reduced power consumption and increased performance
capacity compared to previous generations. The Dell Management Console helps reduce manual processes,
meaning less time and money need to be spent keeping the lights on and more time can be used on thinking up
new ways to use this technology.
ServerMonkey offers the Dell PowerEdge R710 in a variety of options to suit your organizations' specific needs.
Since ServerMonkey offers complete hardware customization, you can configure your unit to meet your price
and processing specifications, or simply select a preconfigured unit from the list above.
Dell PowerEdge R710 Specs:
Form Factor: 2U Rack
Processors: Supports 2 quad or six-core Intel Xeon processors
Memory: Up to 288GB (18 DIMM slots)
Hard Drives: Supports eight 2.5" or six 3.5" drives
Cache: Up to 12MB
I/O Slots: 4 PCIe G2 slots + 1 storage slot
Maximum Internal Storage: Stores up to 12TB
Remote Management: iDRAC6 Enterprise (optional)
Question: What are the process your following? While upgrading the RAm in poweredge?
1. Place the computer power switch in the "off " position and disconnect the AC power cord.
2. Remove the computer top cover following the instructions in the model-specific owner manual.
3. Before touching any electronic components, make sure you first touch an unpainted, grounded metal object to
discharge any static electricity stored on your clothing or body.
4. Locate the memory expansion sockets on the computer motherboard. If all the sockets are full, remove smaller
capacity modules to allow room for higher capacity modules.
5. The ejector tabs shown in the illustration are used to remove a module. By pushing outward on the ejector tabs,
the module will pop-up from the socket and it can then be removed.
6. Handle your new module carefully; do not flex or bend the module. Always grasp the module by its edges.
7. For most installations, DDR modules can be installed in any available expansion slot. Other installations may
require the memory to be installed in a particular sequence based on the modules capacity. Check your owner
manual to determine the correct installation sequence for your configuration.
NOTICE: If you remove your original memory modules from the system during a memory upgrade, keep them
separate from any new memory modules that you may have, even if you purchased the new memory modules
from
Dell. Use only 533 MHz or 667 MHz DDR II FB-DIMMs.
The memory module sockets are divided into two equal branches (0 and 1). Each branch consists of two
channels:
Channel 0 and channel 1 are in branch 0.
Channel 2 and channel 3 are in branch 1.
Each channel consists of two DIMM sockets:
Channel 0 contains DIMM_1, DIMM_5.
Channel 1 contains DIMM _2, DIMM_6.
Channel 2 contains DIMM_3, DIMM_7.
Channel 3 contains DIMM _4, DIMM _8.
The first DIMM socket of each channel has white release tabs.
General Memory Module Installation Guidelines
To ensure optimal performance of your system, observe the following guidelines when configuring your
system memory.
Use only qualified Fully-Buffered DIMMs (FBDs). FBDs can be either single-ranked or dual-ranked.
FBDs marked with a 1R are single-ranked and modules marked with a 2R are dual-ranked.
A minimum of two identical FBDs must installed.
DIMM sockets must be populated by lowest number first.
FBDs must be installed in pairs of matched memory size, speed, and technology, and the total
number of FBDs in the configuration must total two, four, or eight. For best system performance, all
four, or eight FBDs should be identical memory size, speed, and technology.
Memory sparing and memory mirroring require eight FBDs, and all FBDs must be of identical
memory size, speed, and technology.
Memory sparing and memory mirroring cannot be implemented at the same time.

Question: What is Raid ? Types of Raid? How raid 5 is differ from raid 1?
Refer the Below Link
http://www.lascon.co.uk/hwd-raid.php






RAID Level 5 (Stripe with parity)




Question: Difference b/w 2008 & 2003?
1)2008 is combination of vista and windows 2003r2. Some new services are introduced in it
1. RODC one new domain controller introduced in it
[Read-only Domain controllers.]
2. WDS (windows deployment services) instead of RIS in 2003 server
3. shadow copy for each and every folders
4.boot sequence is changed
5.installation is 32 bit where as 2003 it is 16 as well as 32 bit, thats why installation of 2008 is faster
6.services are known as role in it
7. Group policy editor is a separate option in ads

2) The main difference between 2003 and 2008 is Virtualization, management.
2008 has more inbuilt components and updated third party drivers Microsoft introduces new feature with 2k8 that
is Hyper-V Windows Server 2008 introduces Hyper-V (V for Virtualization) but only on 64bit versions. More and
more companies are seeing this as a way of reducing hardware costs by running several 'virtual' servers on one
physical machine. If you like this exciting technology, make sure that you buy an edition of Windows Server 2008
that includes Hyper-V, then launch the Server Manger, add Roles.

3) In Windows Server 2008, Microsoft is introducing new features and technologies, some of which were not
available in Windows Server 2003 with Service Pack 1 (SP1), that will help to reduce the power consumption of
server and client operating systems, minimize environmental byproducts, and increase server efficiency.
Microsoft Windows Server 2008 has been designed with energy efficiency in mind, to provide customers with
ready and convenient access to a number of new power-saving features. It includes updated support for Advanced
Configuration and Power Interface (ACPI) processor power management (PPM) features, including support for
processor performance states (P-states) and processor idle sleep states on multiprocessor systems. These features
simplify power management in Windows Server 2008 (WS08) and can be managed easily across servers and clients
using Group Policies.
What is VM ware ? What the use of EXI Server?
VMware is a virtualization and cloud computing software provider for x86-compatible computers. VMware Inc. is a
subsidiary of EMC Corporation and has its headquarters in Palo Alto, California.
VMware virtualization is based on the ESX/ESXi bare metal hypervisor, supporting virtual machines. The term
"VMware" is often used in reference to specific VMware Inc. products such as VMware Workstation, VMware
View,VMware Horizon Application Manager and VMware vCloud Director.
VM, which stands for "Virtual Machine" (not to be confused with the broader term virtual machine), is a widely-
installed operating systemfor IBM-compatible computers and servers that can host other operating systems in
such a way that each operating system behaves as if it were installed on a self-contained computer with its own
set of programs and hardware resources.
Definition - What does VMware ESXi Server mean?
VMware ESXi Server is computer virtualization software developed by VMware Inc. The ESXi Server is an advanced,
smaller-footprint version of the VMware ESX Server, VMware's enterprise-level computer virtualization software
product. Implemented within the VMware Infrastructure, ESXi can be used to facilitate centralized management
for enterprise desktops and data center applications.
Techopedia explains VMware ESXi Server
VMware Inc. developed ESX and ESXi as bare metal embedded hypervisors, which means that they run directly on
server hardware and do not require the installation of an additional underlying operating system. This
virtualization software creates and runs its own kernel, which is run after a Linux kernel bootstraps the hardware.
The resulting service is a microkernel, which has three interfaces:
Hardware
Guest system
Console operating system (service console)
Some of the distinct features of VMware ESXi Server are:
The ESX architecture uses a service console for management tasks, including script execution and third-party
agent installation. ESXi does not have this service console, which significantly reduces the hypervisor code-
base footprint. By removing the service console, ESXi migrates the management functionality from a local
command line interface to remote management tools.
ESXi's application programming interface-based partner integration model removes the requirement to install
and control third-party management agents. This helps to automate routine tasks by using remote command
line scripting environments, which include vCLI or PowerCLI.
ESXi includes an ultra-thin architecture, which is not dependent on a general-purpose operating system;
however, it continues to deliver all the performance and functionality offered by VMware ESX. VMware ESXi is
highly reliable because its smaller code-base presents a lesser attack area with less code to patch.
Due to its thinner architecture, the installation happens in just 10 minutes, with the server booting up in two
to three minutes. Also, ESXi can be installed easily and booted even from a USB flash drive. ESXi Server is sold
as a built-in hypervisor, which eliminates the need to install the ESXi Server on the hard drive.
ESXi Server has a simple security profile configuration when compared to ESX Server.
ESXi uses a small direct console user interface instead of a full server console.
Because of its more compact size and reduced number of components, ESXi needs considerably fewer patches
when compared to ESX. This helps to shorten service windows and reduce security vulnerabilities
Question: Which tools are using monitoring VMware?
VMware Monitoring
VMware ESX Monitoring quickly and automatically.
Virtualization allows the rapid provisioning of systems LogicMonitor automates the monitoring of these systems,
reducing your workload.
Monitoring VMware ESX server or vSphere with LogicMonitors hosted solution is easy: all you need to do is enter
the Virtual Center or ESX server host name, and all information about your ESX infrastructure will be discovered.
LogicMonitor automatically discovers and monitors all:
ESX hosts
datastores
virtual machines
resource pools
hardware health
By using the VMware native API to query ESX performance counters, LogicMonitor provides a wealth of
performance data and intelligence, offering unmatched visibility into the VMware environment.
And because LogicMonitor can discover and monitor not only the VMware environment, but also the virtual
machines operating systems, the applications running on the VMs (such as IIS, MySQL, Apache, etc), and the
performance metrics of the storage arrays backing the datastores, LogicMonitor allows you to correlate
performance issues and bottlenecks no matter where in the infrastructure the root cause is.
Just a few of the critical VMware metrics we monitor:

VMware host metrics
Monitor VMware metrics for all your hosts and see at a glance critical graphs of memory usage, swap rate, CPU
load, disk latency and more. Predefined best practices alerts warn you of impending issues that can affect your
virtual machines, and provide recommendations without you having to be expert in VMware monitoring.

VMware virtual machine monitoring
Detect all your virtual machines, and monitor them all, automatically. Graph CPU load, network, memory usage,
VMkernel swap rates, ballooning, and more. Detailed statistics and alerts let you track down VM performance
issues, quickly and easily.
VMware virtual machine overview

When you want to head off performance issues, LogicMonitor will show you all your virtual machines at a glance,
and let you see how each is impacting Disk IO, Memory and CPU resources of the underlying ESX host. Know which
machines are slowing, and why
.

ESX and ESXi hardware monitoring
An ESXi host with many virtual machines becomes critically important. LogicMonitors VMware monitoring system
discovers and monitors the hardware supporting your ESX infrastructure, so you know of issues before they affect
your users. Is your power redundant? Or has one power supply failed, and a single failure will now take your host
down? With LogicMonitor, youll know.
Add in LogicMonitors powerful monitoring of Linux, Windows, and applications on the virtual machines and
youve got your VMware monitoring issues solved. Get away from silos of management tools. Get LogicMonitor.
Monitoring tools
Before you begin configuration of your vCenter Server and/or ESX/ESXi hosts, ensure that you already have your
monitoring software installed and configured. The monitoring software should be ready to receive SNMP traffic
before you begin the configuration on your vSphere hosts. There are many commercial and free products you can
use to accomplish this. Among the most popular are:
Dell OpenManage
HP Systems Insight Manager
IBM Tivoli
SolarWinds
VKernel vOPS Server Standard/Enterprise
Veeam ONE Monitoring
Zyrion
Fujitsu ServerView Suite