Windows Network Load Balancing Dedicated Servers
Network Load Balancer or Clusters that were included in Windows Server OS enabled TCP/IP-based services such as follows:
- Web Services
- Terminal Services
- Virtual Private Networking
- Streaming Media
It basically didn’t require any Hardware Support and distributed IP traffic across cluster hosts which ensures detecting host failures and re-distributes traffic to hosts. It provides control and upgrade from Windows NT 4.0 OS. It delivered high performance and fail-over protection in comparison with other load-balancers.
Financial Transactions, Database access, corporate connections and other functions required more reliability which was offered in Windows NLB. Cluster enabled different servers to manage and operate as a single server increasing availability and management.
Windows 2000 Advanced Server and Data Center Server OS includes cluster technology which also provides fail-over for applications and databases. In terms with NLB, traffic is distributed among multi-node clusters.
Advantages of Network Load balancing servers:
> Network Load Balancer Servers are Scalable based upon the activity it hosts. It always adds more no. of servers when we speak of traffic increase.
> Network Load Balancer Server improves reliability of servers. It detects failure of servers and distributes traffic among servers without interrupting any service.
> It distributes traffic based upon the client’s / Users request.
> In comparison, it’s much better than Round Robin Solutions
> 100% Network Uptime
> Centralized access to all cluster servers
> Cost effective when compared to hardware load-balancing techniques
Installation and Management of Network Load-balancing Dedicated Web Servers:
Network Load Balancer is automatically installed and enabled on the Windows Server 2003 and 2008 Operating System. It’s compatible with Ethernet and network adapters, it doesn’t require any hardware. In a NLB, customer is assigned a IP address which is seen as Virtual IP address which all cluster host respond to. Network Load Balancer load-balances only incoming traffic from all IPs. While configuration of NLB, it’s important that there should be a dedicated IP address, primary IPs and Virtual IP’s in order to enable host TCP/IP to respond to IP addresses. Dedicated IP address is entered first and then virtual IP addresses. Services such as PPTP Server does not allow outgoing connections from a different IP address and cannot be used by dedicated IP.
In a cluster, each host is assigned in range of 1 to 32 where lower no. refers to priority. The default host handles all client traffic for virtual IP addresses. Normally, in this case, if the default host fails, the next priority takes place. Network Load Balancer also customized port rules for range of server ports. It can select either Multiple-host or second hosting load balancing policies. With Multiple-host load balancing, incoming request are distributed among all cluster hosts and load percentage can be specified. In this case, it directs all traffic to most priority server. Rules specified at Ports can block different network access. WHen we speak of port rule multiple-host NLB, one of them is selected in affinity mode and Network Load Balancer client’s traffic from on IP addresses on multiple-cluster hosts. It reduces the load on the servers and increases the response time.
In order to manage client sessions, single-client affinity mode balances network traffic from client’s IP on a single cluster host. Network Load Balancer is configured with single port rule covers all port with multiple-host balancing and single client affinity. It is used for applications.
Network Load Balancer also has remote control program which allows administrators to check status of clusters from cluster host. Network Load Balancer for port rules can be enabled or disabled. New traffic can be blocked on host while TCP connections to complete removing host from cluster. Cluster host can disable remote control.
Applications do not need to be modified for load balancing. It does not directly monitor applications. Network Load Balancer provides application mechanism to monitor cluster. Servers can be removed from the clusters for maintenance without interference with other cluster servers. It also allows custom hardware of software upgrades.
Network Load Balancer scales the performance of server based program. It distributes request among different servers in a cluster. With NLB, each IP packet is received by each host. Cluster host responds to different client requests even multiple request from a single client. Load percentage can be handled with each cluster server and can be set as required depending upon the activity. In case one cluster host fails, the traffic and is re-distributed among other cluster host.
Network Load Balancer uses are fully distributed software architecture. A copy of Network Load Balancer driver runs on each cluster host. Drivers check for all incoming network traffic for cluster IP address. On each cluster host, they act as filter between network adapter drive and TCP/IP stack allowing portion of incoming network traffic. Incoming client request are partitioned and load-balanced among cluster host. Network Load Balancer runs as network driver which is below higher-level application protocol such as HTTP and FTP.
Network Load Balancer can also run as drive between TCP/IP protocol and network adapter drivers within Windows protocol. It maximizes throughput by broadcasting subnet to deliver incoming network traffic to cluster host and removers requirement to route incoming packers to individual cluster host. Filtering packets that are not required can be easily be removed than routed packages, it delivers higher Network Load Balancer throughput than any other solution. As network and speed improve, it improves accordingly and reduces dependencies on hardware. It’s availability in fail-over is another advantage.
Network Load Balancer takes advantage of subnet / switch hub to deliver network traffic to cluster host. It increases the load on switches by accessing additional port bandwidth. However, this is not the concern in many applications. Client-side network switch connections are faster than server-side connection. During packet receiving, Network Load Balancer implements delivery of incoming packages to TCP/IP and receiving other packets by Network adapter driver. It means it will speed up all the processes and reduces latency. In many cases, it removes packet data in memory.
Network Load Balancer uses layer-two broadcast or multi-cast to distribute incoming traffic to cluster host. Network Load Balancer re-assigns MAC address of network adapter for which it is enabled. And cluster host assigned the same MAC address. Incoming traffic received by cluster host and Network Load Balancer driver for filtering. MAC address is taken from cluster IP address in the Network Load Balancer properties.
Cluster host that is attached to switch, it might create MAC address conflict due to layer-two switches to see unique MAC address on all switch ports. In order to avoid these problems, Network Load Balancer modifies MAC address for outgoing packages. This prevents switch from learning the cluster’s MAC address and incoming packets for cluster are delivered to all switch ports. Cluster host connected to hub, Network Load Balancer masking for MAC address in Unicast disables to avoid flooding upstream switches. This is done by setting Network Load Balancer registry parameters MaskSourceMAC to 0.
Network Load Balancer unicast mode has a disadvantage of communication disabling between cluster hosts through cluster adapters. Outgoing packets for cluster host are sent to sender’s MAC address, packages are looped within sender by network stack and they do not reach the wire.
Communication between cluster hosts and host outside the cluster is never affected by NLB’s unicast mode. Traffic for all static IP address are received by cluster host due to the same MAC address. Network Load Balancer doesn’t load balance traffic for the IP address, Network Load Balancer deliver the traffic to TCP/IP on host.
With other cluster host, Load balancing Servers checks it’s traffic as load balanced traffic and deliver to TCP/IP. Network Load Balancing also has another mode by distributing incoming traffic to cluster hosts which is called multi-cast mode. Network Load Balancer – Unicast also increases switch flooding by delivering incoming network traffic to cluster hosts, however this is not the case with multi-cast mode. Network Load balancing have Address Resolution Protocol which is required for the cluster’s main IP and virtual IP address resolving to cluster multi-cast MAC address. Network Load Balancing does not include management of incoming IP traffic other than TCP traffic, UDP traffic, Generic routing encapsulation traffic for each port.
Exchange Servers started in 1993 and outgrown since then. It was built in XENIX which is a version of Linux Operating System licensed by Microsoft from AT&T in the 70’s. to exchange server in April 1993.
The users were around 500 in Exchange server in Jan 1995 which then increased to 32000 in 1996. It was then migrated to beta version and the next version was brought in the market.
The Exchange Server 4.0 was released in 1996 and officially sold to public and was to upgrae Microsoft Mail 3.5. It was utilized by 400 client server mails with one database and 500 directories. Following release version was 5.0 which was released in 1997 introduces Administrator console integrated to SMTP-based networks. It also had an add-on feature known as Intenet Mail connecter which could directly communicate with server.
Exchange Server 5.5 was then released in 1997 which came in two versions, Standard and Enterprise. There were many differences in storage limit, mail transport connectors and had the ability of cluster servers.
Exchange Server 2000 edition was released in 2000 which many improvements and it’s limitations were reduced compared to Exchange Server 5.5. It supported more than one cluster and increased it’s supported database. Instant messaging support was also includes and the version includes Microsoft Acive directory which was unavailable in the previous version. The era was then supported by Exchange Server 2007 which was released in 2003. It was supported on Windows 2000 Server and Windows Server 2003. This allowed easy upgration from one operating sytem to another. This was mainly used by major organizations which could not afford downtime caused due to dedicated server migrations.
It main feature includes disaster recovery which allowed administrators to bring servers online faster by sending / receiving emails and recovering them from backups. It also provided anti-virus and anti-spam.
This was introduced in two versions such as standard and enterprise. The standard version allowed 75GB of database storage whereas Enterprise edition allowed 16TB and 4 storage group with 5 databases per group. However, it was only compatible with 32 bit version and not install on 64-bit windows server 2003.
The lastest version is Exchange Server 2007 which was in the beta version in 2006. It can run on 32-bit or 64-bit version of Windows Dedicated Servers. The performance has been improved with this version when compared to Exchange Server 2003.
Exchange server 2007 also introduces features such as voice-mail, filter options, web service support, Outlook Web Access new interface.
BODHost.com supports Exchange Dedicated Server Setup
At the time of request to the DNS Server in order to resolve domain names, it provides different cnames in one order. It redirects the request to servers which are in groups. The BIND feature of DNS resolveing the domain to the server, the request are sent to the same server.
In case of Multiple CNames, when there are four dedicated web servers clusters configured with a IP address, adding them to the DNS with A names. The srv can be set as per our selectionand should meet up the next option.
srv1 IN A xx.xx.xx.1
srv2 IN A xx.xx.xx.2
srv3 IN A xx.xx.xx.3
srv4 IN A xx.xx.xx.4
Add cnames to resolve www.domain.com to one of servers such as
IN CNAME srv2.domain.com.
IN CNAME srv3.domain.com.
IN CNAME srv4.domain.com.
DNS Dedicated Server will then resolve to www.domain.com. The request is sent over group of servers.
Also, the request that is sent to the domain without www should be forwarded to www.domain.com. In order to avoid cname error, we need to do the following :
options {
multiple-cnames yes;
};
In case of Multiple A records for one domain is thus not appropriate DNS server for BIND 9. We use the following :
www.domain.com. 60 IN A xx.xx.xx.1
www.domain.com. 60 IN A xx.xx.xx.2
www.domain.com. 60 IN A xx.xx.xx.3
www.domain.com. 60 IN A xx.xx.xx.4
In this case, if any DNS load balancing dedicated dedicated server, it will have no idea if the server is down. It does not check the port of the dedicated server. IP can be cached by nameserver, the request cannot be sent to load balancing DNS server.
Round Robin DNS load balancing does have many drawbacks but can removed by using Perl scripts.
By using the below steps you can easily install Apache on a Dedicated server :-
http://httpd.apache.org/download.cgi
#cd /usr/local/src
#wget http://mirrors.24-7-solutions.net/pub/apache/httpd/httpd-2.2.8.tar.gz
#tar -xzvf httpd-2.2.8.tar.gz
#cd httpd-2.2.8.tar.gz
#./configure –prefix=/usr/local/apache
# make /compile
# make install /install
#cp /usr/local/apache/bin/apachectl /etc/initr.d/
#service httpd stop
#service httpd start
#httpd –v
These are the points you should remember before transferring a data from one dedicated server to another:-
1)First thing you should remember to give notice to your visitors and users that your website will be down during a specified period of time for planned migration. Ideally, this time should be in the middle of the night (to most of your visitors), to minimize the inconvenience to clients.
2)Prepare DNS for the move:You should make sure that all your DNS records are set to something like an hour. This should be done 48 hours before your move. By doing this will ensure that when you move the website and switch the IP address in the DNS records, people will get to the new location quickly. If you want to double-check the website before it comes back up, add in a new “A” record that already points to the new server’s IP address.
3)Take inventory:You should make a list of all things which you wants to move.Does your web server have a special setup for your website? Do you have any cron jobs running that you will need to set up on the new server? If someone else developed your website and you are not sure about this step, ask them.
4)Put your website on “hold”: Create a small page that just has your website logo and something to the effect of “Sorry. We are moving to a new server. We will be back in couple of hour or so on.” Put this page in place of your web directory and make sure NO pages on your website can be accessed. Keeping people out of any page will result in no loss of data.
5)Set up Email, cron :If your email goes through an account on your server or you have any cron jobs or additional setup to do on the new server, do it now.
7)Once everything is set up bring your website back. To do this, simply swap the IP address in the DNS to the new server’s IP and you should see your website come up pretty quickly.
8)After a day or so, change the TTL in your DNS records back to what it was before . If you forget to do this and leave the TTL at 1 hour, it can create an unnecessary burden on your DNS server.
If everything goes well, you should be able to move a data-driven website or blog with very minimal downtime and with no major problems.
Dedicated Server Migration is one of the most important process and should be done carefully.
> It containes packages for ditribution by SPRMS. It is not invludes in Red Hat. It is the part of core distribution.
> CentOS contains apt RPMS. However, it has issues with distros that utilize multiple libraries.
> centOSplus is also included which are contribution from centOS developers and Users.
> contrib are contribution from users.
> docs which includes manuals and releases of notes
> Added Functionality to the Core distribution
> ISO’s for download from centOS mirror websites
> Updates that released through centOS
centOS is a very user-friendly and interactive Operating System and known to fease very easily. centOS dedicated servers are known to integrate with many control panel such as cPanel.
Bodhost VPS Hosting packages can host game servers depending upon the configuration of the game and resources it will utilize.
If in case you would like to host a high-configuration game. You may host them on a dedicated server which can be renowned as Game Dedicated Servers. We also provide SC Interface Game Control Panel which will allow you to host more than 40 latest games, voice servers and many more.
Any configuration plan along with $30.00 additional will allow you manage your own Game Dedicated Server. If you have any questions, please contact our sales department now.
What is POP3 server?
The POP3 stands for Post Office Protocol 3. POP3 provides a simple, standardized way for users to access mailboxes and download messages to their computers.POP3 is the standard protocol which is used to receive emails. The name of your incoming mail server is needed in order for IncrediMail to give you access to your incoming emails.Usually, the server’s name includes your Internet Service Provider (ISP’s) name in the following format: ‘mail.yourISPname.com’.When you use the POP3 protocol all your eMail messages will be downloaded from the mail server to your local computer.You have a choice to leave copies of your eMails on the server as well.
What is SMTP server?
SMTP stands for Simple Mail Transfer Protocol.SMTP is protocol which is used by the Mail Transfer Agent (MTA) to deliver your eMail to the recipient’s mail server. The name of your outgoing mail server is needed in order for IncrediMail to send your emails.Usually, the server’s name includes your Internet Service Provider (ISP’s) name in the following format: ‘mail.yourISPname.com’.An important feature of SMTP is its capability to relay mail across transport service environments.A transport service provides an interprocess communication environment (IPCE). An IPCE can cover one network, several networks or a subset of a network. More specifically, mail can be relayed between hosts on different transport systems by a host on both transport systems.
Note: The incoming and outgoing server names are usually the same.
E-commerce Server
Internet has changed the way of business. At the touch of a button, consumers can now purchase goods and services from anywhere in the world. There are no geographical barriers to Internet trading. Businesses are increasingly recognising and harnessing the power of the Internet, satisfying the needs of a growing, demanding customer base.
E-Commerce Servers have become one of the most important need of the Internet to have emerged in the recent times. Ecommerce( Electronic commerce) involves carrying out business over the Internet with the help of computers, which are linked to each other forming a network. To be specific ecommerce would be buying and selling of goods and services and transfer of funds through digital communications.
These are the major benefit’s of E-commerce :
1) E-commerce expand’s your global Reach:
The major benefit of E-commerce is the ability to acquire customers across the country and around the world.
2) It expand Customer Base
E-commerce expands customer by providing your customers another purchase channel, your business can attract and retain customers that may have never purchased from you.
3) E-commerce increases the Visibility:
Consumers are increasingly searching for information on the internet prior to making a purchase. You can make your business available to them.
4) It provides customers valuable information about your business
It makes easy to find contact information, store hours, product information, and answers to common questions all add to creating a positive customer experience.
5) E-commerce is always Open For Business
Yes,this E-commerce enables your customers to purchase your products at anytime when you are asleep.
6) E-commerce build’s Customer Loyality
E-commerce’s technology can provide the means to create an effective, automated customer retention program.
7) Collection of customer Data
E-commerce by the very nature of the transactions, automatically collects valuable customer data and relates purchases to that customer. You can use this information to increase future sales from your customers.
It Reduces the cost of Marketing and Advertising
This Internet marketing can be highly targeted to your specific customer; it is more effective and provides a higher return on investment than traditional media advertising.
9) One more important benefit of Ecommerce server is that it is the cheapest means of doing business
10) The benefit of making a business ‘E-commerce enabled’, is that it helps reduce the delivery time, cost of labour and the cost incurred in the following areas:
a) Preparation of documents.
b) Correction and Error Detection
c) Mail preparation
d) Reconciliation
e) Data entry
f) Telephone calling
g) Overtime
h) Supervision expenses
11) E-commerce Provides customers Value
a) Customers can login and view their order history and order status
*Enhanced user experience leads to repeat business and it increased referrals
*Total Customer Service cost is decreased when client can check their own status
b) Ecommerce solution allows for ‘Temporary’ Shopping Carts – allowing people to shop & then sign-up
* By allowing them to Shop First, they become more committed to the sale – higher conversion rate
c) Ecommerce server solution has powerful Advanced Search features – allowing items to be found by varied critieria
* It enhanced user experience leads to repeat business & increase the referrals
* Search features also decreases the costs (no phone calls) and customer frustration
The server has a aim to operate in the following Operating Systems -
a) Unix-like systems
b) Microsoft Windows
c) Novell NetWare
d) Mac OS X
e) And many more
Initially when apache was released and created by Robert McCool, it was the only option for Sun Java Web Server. Since 1996, it has been one of the most popular HTTP server on the internet. It has been managed by open community of developers under Apache Software Foundation.
It also introduced a API which was much more flexible featuring better cache and proxy modules.