Pros and Cons to Windows 2003 Clustering and Load Balancing:

You could now be asking yourself, which is better to implement, Windows clustering or load balancing hosting? To give you a quick rundown of the high-level pros and cons to each technology, consider the following. With Windows cluster hosting, you depend on the actual clustered nodes to make a decision about the state of the network and what to do in a failure. If Node A in a cluster senses a problem with Node B (Node B is down), then Node A comes online. This is done with heartbeat traffic, which is a way for Node A to know that Node B is no longer available and it must come online to take over the traffic. With load balancing, a single device (a network client) sends traffic to any available node in the load-balanced group of nodes. Load balancing uses heartbeat traffic as well but, in this case, when a node comes offline, the “load” is recalculated among the remaining nodes in the group. Also, with clustering (not load balancing), you’re normally tied down or restricted to a small number of participating nodes. For example, if you want to implement a clustered solution with Windows 2003 Advanced Server, you might use a two-node cluster. With load balancing, you can implement up to 32 nodes and, if you use a third-party utility, you can scale way beyond that number. You can even mix up the operating system (OS) platforms, if needed, to include Sun Solaris or any other system you might be running your services on. Finally, you have the option to set up tiered access to services and to mix both architectures (clustering and load balancing hosting) together. You can set up the first tier of access to your web servers as load balanced and the last tier of access as your clustered SQL databases.

With eukhost we have expertise for any feature as per your hosting requirement. We can also setup Windows Dedicated Cluster hosting along with Plesk control panel, this is something that only eUKhost can provide.

This would only happen if the Cluster services has been installed before installing and configuring MSDTC Service. Hence it is highly recommended that you first install and configure MSDTC and then configure the Windows Cluster Service.

Event ID: 4097
Description:
MS DTC started with the following settings: Security Configuration (OFF = 0 and ON = 1): Network Administration of Transactions = 1, Network Clients = 0, Distributed Transactions using Native MSDTC Protocol = 1, Transaction Internet Protocol (TIP) = 0, XA Transactions = 1.

OR

Event ID: 4395
Description:
MSDTC detected that MSDTC related information in the local registry is different from that in the shared cluster registry. Error Specifics: d:ntcomcom1xdtcsharedmtxclumtxclusetuphelper.cpp:541, CmdLine: C:WINNTSystem32msdtc.exe, Pid: 796
Data:
0000: 05 40 00 80 .@.?

OR

Event ID: 4384
Description:
MS DTC was unable to start because the installation was not configured to run on a cluster. Please run comclust.exe and restart MS DTC. Error Specifics: d:ntcomcom1xdtcsharedmtxclumtxclusetuphelper.cpp:668, CmdLine: C:WINNTSystem32msdtc.exe, Pid: 796

OR

Event ID : 7024
Source : Service Control Manager
Description: The MSDTC service terminated with service specific error 3221229584.

Initially you should try and run the command below and check if it solves the problem:

msdtc -resetlog

If that does not help then follow the fix below:

1. Delete the DTC resource
2. Delete MSDTC folder from the quorum disk.

On Node 1:

– Stop the Cluster Service

– Remove Enable network DTC  Service with the command below:

msdtc -uninstall

Make sure to check the Success in the Event logs.

– Verify that the following registry key has been removed as well.. if not then remove it manually.

HKEY_CLASSES_ROOTCID
HKEY_LOCAL_MACHINESOFTWAREMicrosoftMSDTC
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesMSDTC

– Reboot the Server

– After the Server is back online reinstall Enable network DTC Service with the command below:

msdtc -install

Now create the DTC resource on Node 1 and it should come online.

Now on Node 2

– Stop the Cluster Services.

– Evict Node 2 from the Cluster

– Remove Enable network DTC  Service with the command below:

msdtc -uninstall

Make sure to check the Success in the Event logs.

– Verify that the registry key has been removed as well.. if not then remove it manually.

– Reboot

– Reinstall Enable network DTC Service with the command below:

msdtc -install

– Verify that the Service has now Started and also registry keys created.

– Rejoin the node back into the cluster.

Software Requirements

•    Microsoft Windows Server 2003 Enterprise Edition or Windows Server 2003 Datacenter Edition installed on all dedicated servers in the cluster.
•    A name resolution method such as Domain Name System (DNS), DNS dynamic update protocol, Windows Internet Name Service (WINS), HOSTS, and so on.

•    An existing domain model.
•    All nodes must be members of the same domain.
•    A domain-level account that is a member of the local administrators group on each node. A dedicated account is recommended.

Hardware Requirements

•    Clustering hardware must be on the cluster service Hardware Compatibility List (HCL). To find the latest version of the cluster service HCL, go to the Windows Hardware Compatibility List at http://www.microsoft.com/hcl/, and then search for cluster. The entire solution must be certified on the HCL, not just the individual components.

•    Two mass storage device controllers—Small Computer System Interface (SCSI) or Fibre Channel. A local system disk for the operating system (OS) to be installed on one controller. A separate peripheral component interconnect (PCI) storage controller for the shared disks.
•    Two PCI network adapters on each node in the cluster.
•    Storage cables to attach the shared storage device to all computers. Refer to the manufacturers instructions for configuring storage devices..
•    All hardware should be identical, slot for slot, card for card, BIOS, firmware revisions, and so on, for all nodes. This makes configuration easier and eliminates compatibility problems.

Network Requirements

•    A unique NetBIOS name.
•    Static IP addresses for all network interfaces on each node.
•    Access to a domain controller. If the cluster service is unable to authenticate the user account used to start the service, it could cause the cluster to fail. It is recommended that you have a domain controller on the same local area network (LAN) as the cluster is on to ensure availability.
•    Each node must have at least two network adapters—one for connection to the client public network and the other for the node-to-node private cluster network. A dedicated private network adapter is required for HCL certification.
•    All nodes must have two physically independent LANs or virtual LANs for public and private communication.
•    If you are using fault-tolerant network cards or network adapter teaming, verify that you are using the most recent firmware and drivers. Check with your network adapter manufacturer for cluster compatibility.

Shared Disk Requirements:

•    An HCL-approved external disk storage unit connected to all computers. This will be used as the clustered shared disk. Some type of a hardware redundant array of independent disks (RAID) is recommended.
•    All shared disks, including the quorum disk, must be physically attached to a shared bus.
•    Shared disks must be on a different controller then the one used by the system drive.
•    Creating multiple logical drives at the hardware level in the RAID configuration is recommended rather than using a single logical disk that is then divided into multiple partitions at the operating system level. This is different from the configuration commonly used for stand-alone servers. However, it enables you to have multiple disk resources and to do Active/Active configurations and manual load balancing across the nodes in the cluster.
•    A dedicated disk with a minimum size of 50 megabytes (MB) to use as the quorum device. A partition of at least 500 MB is recommended for optimal NTFS file system performance.
•    Verify that disks attached to the shared bus can be seen from all nodes. This can be checked at the host adapter setup level. Refer to the manufacturer’s documentation for adapter-specific instructions.
•    SCSI devices must be assigned unique SCSI identification numbers and properly terminated according to the manufacturer’s instructions.
•    All shared disks must be configured as basic disks.
•    Software fault tolerance is not natively supported on cluster shared disks.
•    All shared disks must be configured as master boot record (MBR) disks on systems running the 64-bit versions of Windows Server 2003.
•    All partitions on the clustered disks must be formatted as NTFS.
•    Hardware fault-tolerant RAID configurations are recommended for all disks.
•    A minimum of two logical shared drives is recommended.

So here we go:

On your local machine, [AND NOT THE SERVER]:
Goto START >> Run >> and Type:
notepad "C:WINDOWSsystem32driversetchosts"
And hit Enter

If you get file does not exist error then create hosts file in notepad “C:WINDOWSsystem32driversetc” folder.

At the end of the file you will have:

127.0.0.1 localhost

Just add your domain with the IP you want to point to, and it will look like, this will be also applicable if you have create a new hosts file:

127.0.0.1 localhost
192.168.1.52 mywebhostingblog.net
192.168.1.52 www.mywebhostingblog.net

Save the file and exit.

Now ping the domain on the computer you have made changes on and it will point to the IP address defined. You can now browse your site without the site preview and you will have to the content of the server you are moving to. Just remove the entries from the hosts file to point your domain back it was.

Wasn’t that Simple..!!!

After installing a SQL Server failover cluster, the node hosting the SQL Server resource uses the Service Control Manager to check every 5 seconds whether the SQL Server service appears to be running. This “LooksAlive” check does not impact the performance of the system, but also does not do a thorough check; the check will succeed if the service appears to be running even though it might not be operational. Because the LooksAlive check does not do a thorough check, a deeper check must be done periodically; this “IsAlive” check runs every 60 seconds.

The IsAlive check runs a SELECT @@SERVERNAME Transact-SQL query against SQL Server to determine whether the server can respond to requests. Although a reply to the IsAlive query confirms that the SQL Server service is available for requests, it does not guarantee that all user databases are available, or that the user databases are operating within necessary performance/response-time requirements.

If the IsAlive query fails, the IsAlive health check is retried five times and then it attempts to reconnect to the instance of SQL Server. If all five retries fail, the SQL Server resource fails. Depending on the failover threshold configuration of the SQL Server resource, the failover cluster will attempt to either restart the resource on the same node or it will fail over to another available node. The IsAlive query tolerates a few errors, but ultimately it fails if its threshold is exceeded.

During failover of the SQL Server instance, SQL Server resources start up on the new node. Windows clustering starts the SQL Server service for that instance on the new node and SQL Server goes through the recovery process to start the databases. After the service is started and the master database is online, the SQL Server resource is considered to be up. Now the user databases will go through the normal recovery process, which means that any completed transactions in the transaction log are rolled forward (the Redo phase), and any incomplete transactions are rolled back (the Undo phase). In SQL Server 2005 Enterprise Edition, each user database will be available to the user once the Redo phase completes; for the other editions, as with all previous versions, each user database is unavailable until the Undo phase completes. The length of the recovery process depends on how much activity must be rolled forward or rolled back upon startup. The ‘recovery interval’ sp_configure option of the server can be set to a low number to avoid longer Redo recovery times and to speed up the failover process. The Undo recovery time can be reduced by using shorter transactions so that any uncommitted transactions do not have much to roll back.

Whenever you plug a USB drive in your system (which you think is infected by virus), do not open it -  Do not click ‘OK’ !
click on ‘Cancel’. Now open Command Prompt by typing ‘cmd‘ in run box.
Type dir /w/a and press enter.
Above command will display list of files in pen drive. Check in the list if the files are not

* Heap41a
* New Folder.exe
* Autorun.inf
* svchost.exe
* Ravmon.exe
* or any other exe file which may be suspicious.

If any of the above files are present in the list, then your USB drive is infected. To remove these files, type the following command in command prompt
attrib -r -a -s -h *.* and press enter.
This will remove from files  Read Only, Archive, System and Hidden attributes .

The files which you will now be looking on are the junk files (viruses) and can be deleted using  del command. Delete all those files which you find suspicious. To be on a safer side, just scan again your  USB Pen drive using a anti virus to check whether it is free of virus or not.

Windows Server 2003 provides improved alternatives to CDONTS. To make CDONTS
functioning on a Windows Server 2003-based computer, use one of the following

solution:

1. Obtain CDONTS.DLL and put it into %systemroot%\system32 folder
(C:\Windows\system32 by default).

2. Register the CDONTS.DLL component on your server using the following command:

regsvr32 “%systemroot%\system32\cdonts.dll”

For example:

C:\WINDOWS\system32>regsvr32.exe cdonts.dll

3. After you have registered your CDONTS.DLL component you need to check whether
your SMTP service is running. Go to Administrative tools > IIS and expand your local
machine. If SMTP service is listed then it is installed, else  it’s necessary to
install this service. To install SMTP perform the following operation:
Go to Control Panel > Add/Remove Programs > Add/Remove Windows Components >
Application Server > IIS > Mark SMTP service > Click OK.

4. Change the port number for SMTP service. Default port is 25. Use 25 only if you
don’t have another SMTP service running. If another SMTP service is already running
on your server you should switch IIS SMTP port to another, for example to 26. You
can do through IIS management console:
Control Panel > IIS > expand `local computer` > SMTP > Properties > General tab >
click on Advanced button > Edit.

5. Configure SMTP service. The main things are to set a valid full-qualified domain
name for SMTP service:
Control Panel > IIS > expand `local computer` > SMTP > Properties > Delivery tab >
click on Advanced button

6. Configure Security for SMTP service. It’s necessary to grant permissions to
IIS_WPG standard IIS Worker Process Group.

Control Panel > IIS > expand `local computer` > SMTP > Properties > Security tab >
click on Add button > Cick Object types… button > Mark Groups item > click OK >
Add IIS_WPG as object name to add > Click OK.

7. Additional setting:

Choose Authentication and tick Anonymous Access and Integrated Windows
Authentication. Click OK, then click CONNECTION. Configure RELAY settings as you
wish. Click the DELIVERY tab then click ADVANCED.

8. Stop SMTP service of IIS and start it again. Now IIS SMTP service as configured
and ready to work.