Tuesday, April 19, 2016
Features of NLB
Features in Network Load Balancing
NLB includes the following features:
Scalability
Scalability is the measure of how well a computer, service, or application can grow to meet increasing performance demands. For NLB clusters, scalability is the ability to incrementally add one or more systems to an existing cluster when the overall load of the cluster exceeds its capabilities. To support scalability,
NLB can do the following:
Balance load requests across the NLB cluster for individual TCP/IP services.
Support up to 32 computers in a single cluster.
Balance multiple server load requests (from either the same client or from several clients) across multiple hosts in the cluster.
Support the ability to add hosts to the NLB cluster as the load goes up, without bringing the cluster down.
Support the ability to remove hosts from the cluster when the load goes down.
Enable high performance and low overhead through fully pipelined implementation. Pipelining allows requests to be sent to the NLB cluster without waiting for response to the previously sent one.
High-availability :
A highly available system reliably provides an acceptable level of service with minimal downtime. To provide high availability, NLB includes built-in features that can automatically:
Detect and recover from a cluster host that fails or goes offline.
Balance the network load when hosts are added or removed.
Recover and redistribute the workload within ten seconds.
Manageability :
NLB provides the following manageability features:
You can manage and configure multiple NLB clusters and the cluster hosts from a single computer by using NLB Manager.
You can specify the load balancing behavior for a single IP port or group of ports by using port management rules.
You can define different port rules for each Web site. If you use the same set of load-balanced servers for multiple applications or Web sites, port rules are based on the destination virtual IP address (using virtual clusters).
You can direct all client requests to a single host by using optional, single-host rules. NLB routes client requests to a particular host that is running specific applications.
You can block undesired network access to certain IP ports.
You can enable Internet Group Management Protocol (IGMP) support on the cluster hosts to control switch flooding (when operating in multicast mode).
You can remotely start, stop, and control NLB actions from any networked computer that is running Windows by using shell commands or scripts.
You can view the Windows event log to check NLB events. NLB logs all actions and cluster changes in the event log.
Ease-of-use
NLB provides many features that make it convenient to use:
NLB is installed as a standard Windows networking driver component.
NLB requires no hardware changes to enable and run.
NLB Manager enables you to create new NLB clusters.
NLB Manager enables you to configure and manage multiple clusters and all of the cluster's hosts from a single remote or local computer.
NLB lets clients access the cluster by using a single, logical Internet name and virtual IP address—known as the cluster IP address (it retains individual names for each computer). NLB allows multiple virtual IP addresses for multihomed servers.
Note
In the case of virtual clusters, the servers do not need to be multihomed to have multiple virtual IP addresses.
NLB can be bound to multiple network adapters, which allows you to configure multiple independent clusters on each host. Support for multiple network adapters differs from virtual clusters in that virtual clusters allow you to configure multiple clusters on a single network adapter.
You do not have to modify server applications to run in an NLB cluster.
If a cluster host fails and then is subsequently brought back online, NLB can be configured to automatically add that host to the cluster. The added host will then be able to start handling new server requests from clients.
You can take computers offline for preventive maintenance without disturbing cluster operations on the other hosts.
NLB includes the following features:
Scalability
Scalability is the measure of how well a computer, service, or application can grow to meet increasing performance demands. For NLB clusters, scalability is the ability to incrementally add one or more systems to an existing cluster when the overall load of the cluster exceeds its capabilities. To support scalability,
NLB can do the following:
Balance load requests across the NLB cluster for individual TCP/IP services.
Support up to 32 computers in a single cluster.
Balance multiple server load requests (from either the same client or from several clients) across multiple hosts in the cluster.
Support the ability to add hosts to the NLB cluster as the load goes up, without bringing the cluster down.
Support the ability to remove hosts from the cluster when the load goes down.
Enable high performance and low overhead through fully pipelined implementation. Pipelining allows requests to be sent to the NLB cluster without waiting for response to the previously sent one.
High-availability :
A highly available system reliably provides an acceptable level of service with minimal downtime. To provide high availability, NLB includes built-in features that can automatically:
Detect and recover from a cluster host that fails or goes offline.
Balance the network load when hosts are added or removed.
Recover and redistribute the workload within ten seconds.
Manageability :
NLB provides the following manageability features:
You can manage and configure multiple NLB clusters and the cluster hosts from a single computer by using NLB Manager.
You can specify the load balancing behavior for a single IP port or group of ports by using port management rules.
You can define different port rules for each Web site. If you use the same set of load-balanced servers for multiple applications or Web sites, port rules are based on the destination virtual IP address (using virtual clusters).
You can direct all client requests to a single host by using optional, single-host rules. NLB routes client requests to a particular host that is running specific applications.
You can block undesired network access to certain IP ports.
You can enable Internet Group Management Protocol (IGMP) support on the cluster hosts to control switch flooding (when operating in multicast mode).
You can remotely start, stop, and control NLB actions from any networked computer that is running Windows by using shell commands or scripts.
You can view the Windows event log to check NLB events. NLB logs all actions and cluster changes in the event log.
Ease-of-use
NLB provides many features that make it convenient to use:
NLB is installed as a standard Windows networking driver component.
NLB requires no hardware changes to enable and run.
NLB Manager enables you to create new NLB clusters.
NLB Manager enables you to configure and manage multiple clusters and all of the cluster's hosts from a single remote or local computer.
NLB lets clients access the cluster by using a single, logical Internet name and virtual IP address—known as the cluster IP address (it retains individual names for each computer). NLB allows multiple virtual IP addresses for multihomed servers.
Note
In the case of virtual clusters, the servers do not need to be multihomed to have multiple virtual IP addresses.
NLB can be bound to multiple network adapters, which allows you to configure multiple independent clusters on each host. Support for multiple network adapters differs from virtual clusters in that virtual clusters allow you to configure multiple clusters on a single network adapter.
You do not have to modify server applications to run in an NLB cluster.
If a cluster host fails and then is subsequently brought back online, NLB can be configured to automatically add that host to the cluster. The added host will then be able to start handling new server requests from clients.
You can take computers offline for preventive maintenance without disturbing cluster operations on the other hosts.
What is Network Load Balancing ?
The Network Load Balancing (NLB) feature in Windows Server 2008 R2 enhances the availability and scalability of Internet server applications such as those used on Web, FTP, firewall, proxy, virtual private network (VPN), and other mission-critical servers. A single computer running Windows Server 2008 R2 provides a limited level of server reliability and scalable performance. However, by combining the resources of two or more computers running one of the products in Windows Server 2008 R2 into a single virtual cluster, NLB can deliver the reliability and performance that Web servers and other mission-critical servers need.
The diagram above depicts two connected Network Load Balancing clusters. The first cluster consists of two hosts and the second cluster consists of four hosts. This is one example of how you can use NLB.
Each host runs a separate copy of the desired server applications (such as applications for Web, FTP, and Telnet servers). NLB distributes incoming client requests across the hosts in the cluster. The load weight to be handled by each host can be configured as necessary. You can also add hosts dynamically to the cluster to handle increased load. In addition, NLB can direct all traffic to a designated single host, which is called the default host.
NLB allows all of the computers in the cluster to be addressed by the same set of cluster IP addresses, and it maintains a set of unique, dedicated IP addresses for each host. For load-balanced applications, when a host fails or goes offline, the load is automatically redistributed among the computers that are still operating. When a computer fails or goes offline unexpectedly, active connections to the failed or offline server are lost. However, if you bring a host down intentionally, you can use the drainstop command to service all active connections prior to bringing the computer offline. In any case, when it is ready, the offline computer can transparently rejoin the cluster and regain its share of the workload, which allows the other computers in the cluster to handle less traffic.
The hosts in an NLB cluster exchange heartbeat messages to maintain consistent data about the cluster’s membership. By default, when a host fails to send heartbeat messages within five seconds, it has failed. When a host has failed, the remaining hosts in the cluster converge and do the following:
- Establish which hosts are still active members of the cluster.
- Elect the host with the highest priority as the new default host.
- Ensure that all new client requests are handled by the surviving hosts.
During a convergence, the surviving hosts look for consistent heartbeats. If the host that failed to send heartbeats begins to provides heartbeats consistently, it rejoins the cluster in the course of the convergence. When a new host attempts to join the cluster, it sends heartbeat messages that also trigger a convergence. After all cluster hosts agree on the current cluster membership, the client load is redistributed to the remaining hosts, and the convergence completes.
Convergence generally takes only a few seconds, so interruption in client service by the cluster is minimal. During convergence, hosts that are still active continue handling client requests without affecting existing connections. Convergence ends when all hosts report a consistent view of the cluster membership and distribution map for several heartbeat periods.
Upload multiple photos is missing - SharePoint 2010
Situation : I Was not able to find a option to upload multiple photos and documents the option was missing in upload dialog box
Resolution:
Normally Upload Multiple Files is missing when you don't have any local Office clients installed.
You need to check on the below
1. The 32 bit version of Internet Explorer.
2. Office 2003 /Office 2007 / Office 2010 / Office 2013 or newer on the client
3. Client integration will need to be enabled for the web app.
4. The STSUpld.UploadCtl IE add-in must be enabled.
Note : Does not work with other browsers or 64 bit IE
There is an ActiveX control that is used to support multiple file uploading - that ActiveX control is installed with office.
Once you install any of the client (i.e. any office version ) then your issue will be resolved.
Resolution:
Normally Upload Multiple Files is missing when you don't have any local Office clients installed.
You need to check on the below
1. The 32 bit version of Internet Explorer.
2. Office 2003 /Office 2007 / Office 2010 / Office 2013 or newer on the client
3. Client integration will need to be enabled for the web app.
4. The STSUpld.UploadCtl IE add-in must be enabled.
There is an ActiveX control that is used to support multiple file uploading - that ActiveX control is installed with office.
Once you install any of the client (i.e. any office version ) then your issue will be resolved.
Tuesday, March 29, 2016
Sharepoint 2013 Latest Updates
| SharePoint 2013 | |||
|
Build
Number
|
Build Name | Component | Information Link |
| 15.0.4128.1014 | Beta | SharePoint Foundation 2013 | |
| 15.0.4128.1014 | Beta | SharePoint Server 2013 | |
| 15.0.4128.1014 | Beta | Project Server 2013 | |
| | | | |
| 15.0.4420.1017 | RTM | SharePoint Foundation 2013 | |
| 15.0.4420.1017 | RTM | SharePoint Server 2013 | |
| 15.0.4420.1017 | RTM | Project Server 2013 | |
| | | | |
| 15.0.4433.1506 | December 2012 Hotfix | SharePoint Server 2013 | KB2752058 |
| 15.0.4433.1506 | December 2012 Hotfix | SharePoint Server 2013 (coreserver) | KB2752001 |
| | | | |
| 15.0.4481.1005 | March 2013 Public Update | SharePoint Foundation 2013 | KB2768000 |
| 15.0.4481.1005 | March 2013 Public Update | SharePoint Server 2013 | KB2767999 |
| 15.0.4481.1005 | March 2013 Public Update | Project Server 2013 | KB2768001 |
| | | | |
| 15.0.4505.1002 | April 2013 CU | SharePoint Foundation 2013 | KB2751999 |
| 15.0.4505.1005 | April 2013 CU | SharePoint Server 2013 | KB2726992 |
| 15.0.4505.1005 | April 2013 CU | Project Server 2013 | KB775426 |
| | | | |
| 15.0.4517.1003 | June 2013 CU | SharePoint Foundation 2013 | KB2817346 |
| 15.0.4517.1005 | June 2013 CU | SharePoint Server 2013 | KB2817414 |
| | June 2013 CU | Project Server 2013 | KB2817415 |
| | | | |
| 15.0.4535.1000 | August 2013 CU | SharePoint Foundation 2013 | KB2817517 |
| | August 2013 CU | SharePoint Server 2013 | KB2817616 |
| | August 2013 CU | Project Server 2013 | KB2817615 |
| | | | |
| 15.0.4551.1001 | October 2013 CU | SharePoint Foundation 2013 | KB2825674 |
| 15.0.4551.1005 | October 2013 CU | SharePoint Server 2013 | KB2825647 |
| | October 2013 CU | Project Server 2013 | |
| | | | |
| 15.0.4551.1508 | December 2013 CU | SharePoint Foundation 2013 | KB2849961 |
| 15.0.4551.1511 | | SharePoint Server 2013 | KB2850024 |
| 15.0.4551.1508 | | Project Server 2013 | KB2837668 |
| | | | |
| 15.0.4569.1000* | Service Pack 1 | SharePoint Foundation 2013 | KB2817439 |
| | | SharePoint Server 2013 | KB2817429 |
| | | Project Server 2013 | KB2817434 |
| | | | |
| 15.0.4571.1502* | Service Pack 1 Mark 2 | SharePoint Foundation 2013 | KB2880551 |
| | SharePoint Server 2013 | KB2880552 | |
| | Project Server 2013 | KB2880553 | |
| | | | |
| 15.0.4605.1000 | April 2014 CU | SharePoint Foundation 2013 | KB2863892 |
| | | SharePoint Server 2013 | KB2878240 |
| | | Project Server 2013 | KB2880484 |
| | | | |
| 15.0.4615.1001 | MS14-022 | SharePoint Foundation 2013 | KB2952166 |
| | | SharePoint Server 2013 | KB2952166 |
| | | Project Server 2013 | KB2952166 |
| | | | |
| 15.0.4617.1000 | June 2014 CU | SharePoint Foundation 2013 | KB2881063 |
| | | SharePoint Server 2013 | KB2881061 |
| | | Project Server 2013 | KB2881062 |
| | | | |
| 15.0.4631.1001 | July 2014 CU | SharePoint Foundation 2013 | KB2882999 |
| | | SharePoint Server 2013 | KB2882989 |
| | | Project Server 2013 | KB2882990 |
| | | | |
| 15.0.4641.1001 | August 2014 CU | SharePoint Foundation 2013 | KB2883081 |
| | | SharePoint Server 2013 (1/5) | KB2760213 |
| | | SharePoint Server 2013 (2/5) | KB2880559 |
| | | SharePoint Server 2013 (3/5) | KB2883078 |
| | | SharePoint Server 2013 (4/5) | KB2883085 |
| | | SharePoint Server 2013 (5/5) | KB2883086 |
| | | Project Server 2013 | KB2883083 |
| | | | |
| 15.0.4649.1001 | September 2014 CU | SharePoint Foundation 2013 | KB2883087 |
| | | SharePoint Server 2013 | KB2883068 |
| | | Project Server 2013 | KB2883072 |
| | | | |
| 15.0.4659.1001 | October 2014 CU | SharePoint Foundation 2013 | KB2889946 |
| | | SharePoint Server 2013 (1/3) | KB2899469 |
| | | SharePoint Server 2013 (2/3) | KB2880962 |
| | | SharePoint Server 2013 (3/3) | KB2880485 |
| | | Documentum Connector | KB2752098 |
| | | Project Server 2013 | KB2889959 |
| | | | |
| 15.0.4667.1000 | November 2014 CU | SharePoint Foundation 2013 | KB2899468 |
| | | SharePoint Server 2013 | KB2889944 |
| | | Project Server 2013 | KB2889949 |
| | | | |
| 15.0.4675.1000 | December 2014 CU | SharePoint Foundation 2013 | KB2910945 |
| | | SharePoint Server 2013 | KB2910938 |
| | | Project Server 2013 | KB2910911 |
| | | | |
| 15.0.4693.1001 | February 2015 CU | SharePoint Foundation 2013 | KB2920801 |
| | | SharePoint Server 2013 | KB2920804 |
| | | Project Server 2013 | KB2920796 |
| | | | |
| 15.0.4701.1001 | March 2015 CU | SharePoint Foundation 2013 | KB2956159 |
| | | SharePoint Server 2013 | KB2956166 |
| | | Project Server 2013 | KB2956162 |
| | | | |
| 15.0.4711.1000 | April 2015 CU | SharePoint Foundation 2013 | KB2965261 |
| | | SharePoint Server 2013 | KB2965266 |
| | | Project Server 2013 | KB2965263 |
| | | | |
| 15.0.4719.1002 | May 2015 CU | SharePoint Foundation 2013 | |
| | | SharePoint Server 2013 | KB3039780 |
| | | Project Server 2013 | KB3039753 |
| | | | |
| 15.0.4727.1001 | June 2015 CU | SharePoint Foundation 2013 | KB3054864 |
| | | SharePoint Server 2013 | KB3054866 |
| | | Project Server 2013 | KB3054865 |
| | | | |
| 15.0.4737.1001 | July 2015 CU | SharePoint Foundation 2013 | |
| | | SharePoint Server 2013 | |
| | | Project Server 2013 | |
| | | | |
| 15.0.4745.1001 | August 2015 CU | SharePoint Foundation 2013 | KB3055004 |
| | | SharePoint Server 2013 | |
| | | Project Server 2013 | |
| | | | |
| 15.0.4753.1000 | September 2015 CU |
SharePoint Foundation 2013
|
KB2975894 |
| | | SharePoint Server 2013 | |
| | | Project Server 2013 | |
| | | | |
| 15.0.4763.1000 | October 2015 CU | SharePoint Foundation 2013 | KB3085488 |
| | | SharePoint Server 2013 | KB3085492 |
| | | Project Server 2013 | KB3085489 |
| | | | |
| 15.0.4771.1000 | November 2015 CU | SharePoint Foundation 2013 | KB3101368 |
| | | SharePoint Server 2013 | KB3101373 |
| | | Project Server 2013 | KB3101369 |
| | | | |
| 15.0.4779.1000 | December 2015 CU | SharePoint Foundation 2013 | KB3114339 |
| | | SharePoint Server 2013 | KB3114345 |
| | | Project Server 2013 | KB3114341 |
| | | | |
| 15.0.4787.1000 | January 2016 CU | SharePoint Foundation 2013 | KB3114492 |
| | | SharePoint Server 2013 | KB3114497 |
| | | Project Server 2013 | KB3114493 |
| | | | |
| 15.0.4797.1000 | February 2016 CU | SharePoint Foundation 2013 | KB3114722 |
| | | SharePoint Server 2013 | KB3114726 |
| | | Project Server 2013 | KB3114723 |
| | | | |
| 15.0.4805.1000 | March 2016 CU | SharePoint Foundation 2013 | KB3114822 |
| | | SharePoint Server 2013 | KB3114827 |
| | | Project Server 2013 | KB3114823 |
Friday, February 28, 2014
Workflow History Purge After 60 days
Hi Readers ,
Today i came across a department in the organisation which wants all the old workflow history for Audit purpose .
By default the workflow history gets purged after 60 days . For the same there is a Timer job which runs .
You could also disable the automatic cleanup of workflow history by the following steps:
1. From Central Administration, click the Operations tab on the top navigation bar.
2. On the Operations page, in the Global Configuration section, click Timer job definitions.
3. On the Timer Job Definitions page, click Workflow Auto Cleanup to edit the appropriate timer job.
4. On the Edit Timer Job page, click Disable and then click OK to disable the Workflow Auto Cleanup feature.
Reference :
Disable automatic cleanup of workflow history (SharePoint Server 2007)
Disable preservation of workflow history (SharePoint Server 2010)
check this too
Huge MOSS Workflow Issue… What is Microsoft Thinking!!!!
Today i came across a department in the organisation which wants all the old workflow history for Audit purpose .
By default the workflow history gets purged after 60 days . For the same there is a Timer job which runs .
You could also disable the automatic cleanup of workflow history by the following steps:
1. From Central Administration, click the Operations tab on the top navigation bar.
2. On the Operations page, in the Global Configuration section, click Timer job definitions.
3. On the Timer Job Definitions page, click Workflow Auto Cleanup to edit the appropriate timer job.
4. On the Edit Timer Job page, click Disable and then click OK to disable the Workflow Auto Cleanup feature.
Reference :
Disable automatic cleanup of workflow history (SharePoint Server 2007)
Disable preservation of workflow history (SharePoint Server 2010)
check this too
Huge MOSS Workflow Issue… What is Microsoft Thinking!!!!
Subscribe to:
Posts (Atom)