Global Deployment in Data Centers
Prerika Agarwal1, Madhumala Kumari2
1 2
aga.prerika@gmail.com,
1,2
Student B-Tech IT Shobhit University,Meerut
Abstract- As data centres are becoming more and
more central in internet communications. Operation
and research communities are working on the
deployment of these data centres. In this paper, we
present a empirical study of global deployment in
data centres. Firstly we studied that data centres are
the facilities to house computer systems. We analyze
the replication and distribution strategy which helps
the data centres to increase the performance and
scalability. We also study WAN accelerators that are
used for optimize the packets over the global network
by using caching, compression, differencing, and
proprietary methods. We then find the aspects of
deploying data centres. We also included the
designing model of global data centres.
Keywords: WAN accelerators, Replication, Directory
proxy server, scalability, Multi-master, LDAP
1. Introduction
A data center can be defined as the facility used to
group computer systems and associated
components, such as any communication system
and storage system[2]. It is also known as Server
farm. It also includes backup power supplies,
redundant communication connections and security
devices.
In early ages, computer systems were complex to
operate and maintain. Wired Cables systems were
used to connect all the components. Security was
very important issue as computers were expensive.
However in 1990’s IT operations started to grow,
companies grew aware of the need to control IT
resources. With the advent of client-server
computing, micro computers (or severs) started
developing. The availability of inexpensive
networking equipment made to put the servers in a
specified room. Many companies started building
very large facilities, known as Internet data center
(IDCs). New technologies and practices eventually
migrated towards private data centers.
madhukumari30@gmail.com
IT operations are a crucial aspect of most
organizational operations. One of the concerns is
business continuity; companies depend upon their
information systems to run their operations. If there
would be no system, companies work may totally
halt. It is essential to provide a reliable
infrastructure for IT operations in order to
minimize risks. For the reason of security data
centers have to offer secured environment. A data
center must therefore keep high standards for
assuring the integrity and functionality of its hosted
computer environment. This is accomplished
through redundancy of both fiber optic cables and
power, which includes emergency backup power
generation.
1.1 Deploying Data Center
For deploying data center, five areas or aspects are
to be considered. These are the FCAPS of the
deployment of data centers[2].
Fault: This aspect looks at the status of the
components and whether they are performing
within set thresholds. It is event based. Broken
disks and dead processes are examples of events.
Configuration: This aspect manages the
configuration of the IT components. It tracks the
parameters and values of the IT components.
Preferably a history of configurations is maintained
so a bad change is backed-out easily.
Accounting: This aspect is an older concept that
stems from the mainframe world. It is the ability to
track usage of system resources and relate that to
business units and/or customers to enable billing.
An interesting side note is that, with the emerging
ASP business models, accounting has received
renewed interest.
Performance- This aspect manages the challenging
task of monitoring how fast or slow a system
responds and processes transactions. A key process
in this area is performance tuning and capacity
planning, where historical data is submitted for
analysis to discover trends or model anticipated
changes in the environment.
Security: This aspect manages the complete
infrastructure from an authentication, authorization
and access perspective. Security is very pervasive
and should be addressed early in the architecture.
Figure 1- Data Center
2 WAN Accelerators
WAN acceleration has been network equipment in
a geographically distributed deployment.
Especially WAN accelerator work with the design
of a device in the data centres with another device
in the branch office. It is also used for optimize the
packets over the global network by using caching,
compression, differencing, and proprietary
methods. There are some devices in WAN
accelerator that works to provide optimization for
Exchange and File Share traffic like Cisco, Citrix,
Packeteer, Certeon, F5, and Riverbed[6].
2.1 Offloading devices
WAN accelerator is the most important device in
the enterprise because it secures the information
transmitted over the internet where as bandwidth
and latency are not known. It also helps to control
over the branch office from one place to another.
Sometimes this performs as a slim devices or
simple servers that act as devices that likely
provide both load balancing and global distribution
can be had for a price.
In the global data centres, Caching and related
proprietary techniques, offloaded compression with
varying algorithms and warm ups and pre-fetching
are the important strategies that are beneficial for
the user experience. It also in the internet arena
there are global caching, network optimization
routing techniques for reducing dropped packets
and reducing latency are employed to ensure
optimum experience.
Even that it provides offloaded or delegated
authentication or a gateway for accessing
information adding a layer of security. This gives
the benefits of a firewall, load balancing, plus some
intelligence for offloading and caching.
2.2 Clients
Centralized deployments of SharePoint have
challenges with user experience. There are some
techniques for client that are often about pre-
fetching, background synchronization,
compression, add blockers, and image filters.
Client can easily be synchronized when online in
the background transparently. It still uses the WAN
to copy and/or download the files. If the clients
need to save the file up, then they again save it
locally and it is send back up to the server in the
background. The client software would then handle
any conflicts. Some clients handle this experience
better than others.
The Outlook 2007 experience is an example of a
client that could allow you to consume your
SharePoint blogs or lists offline by consuming the
RSS with RSS reader such as Outlook 2007. The
synchronization of the SharePoint document library
to Outlook could happen in the background, but the
upload wouldn’t. No caching or compression
algorithms are used in the case of outlook, but
Groove does have methods for taking SharePoint
files offline and it’s peer to peer mechanisms could
provide the files from another user on the LAN
rather than from a remote location .

2.3 Multi Farm Manageability and Reporting

WAN links the two main offices or disaster

recovery requirements with a multi master
requirement, replication comes up in deployments.
In a global deployment such as a regional or branch
office deployments, having multiple farms poses a
challenge of managing settings across the
thousands of sites across many farms.WAN Figure 3 – Global deployment
accelerator provide management tools designed for
making permissions management, effective user
rights, and settings and configuration easier.
3.1 Replication across Data Centers
2.4 Replication on Hardware or Byte-level
Replication is a set of technologies for copying and
Microsoft Cluster Services helps as a potential to
distributing data and database objects from one
eliminate the hardware. MSCS provides hardware
database to another and then synchronizing
based fault tolerance. Hardware vendors have
between databases to maintain consistency.
various methods for having redundant channels,
Replication enables geographic distribution of
redundant fibre, redundant disks, and various array
LDAP service. We can have identical copies of
configurations providing varying levels of fault
information on multiple servers[1].
tolerance. Software based failover solutions such
as SQL log shipping and SQL mirroring provide Directory Server enables multi-master replication
hardware fault tolerance. On the basis of replication configurations across geographical boundaries in
hardware or byte level replication makes it very multiple data centre deployments. The replication
easy to fail over and to synchronize environments protocol has complete asynchronous support; it also
between data centres. provides support for window, grouping mechanism.
Data transfer rate will be less than the available
When sense creates a clone or mirror of the
physical medium allows in terms of bandwidth. In
primary environment can create a secondary
the case the update volume between replicas is not
environment to fail over to then it is said to be
fitted into available bandwidth, the tuning does not
replication on byte level. This continuous
prevent replicas from diverging under heavy update
replication can provide a means for either
load. Replication delay and update performance are
automatic or manual failover.
dependent on modification rate, entry size, server
3. Designing a Global Deployment hardware, average latency and average bandwidth.
If there is slow replication, window size and group
In a global deployment access to directory services size parameters have to be adjusted. By avoiding
is required in more than one geographical location, peak network time, the usage can also be improved.
or data center. To optimize the bandwidth usage compression of
replication data is supported by directory server. At
the time of replication of data, security to ensure
data integrity and confidentiality is provided.

4. Grouping and window mechanism of

Replication
The mechanism of grouping and window is used to
optimize the flow of replication. Group mechanism
ensures the changes are sent in group. The group
size is the maximum number of data modifications
to be bundled in a single update message. If the
connection is appearing to be the bottleneck for
replication, group size can be increased.

The window size is the maximum number of

update message can be sent without immediate
acknowledgement from the consumer. The time
which the replicas spend waiting for updates can be
reduced by using appropriate window size. By
increasing window size, consumer’s replica can be
prevented from lagging behind.

4.1 Replication Compression

Replication compression streamlines replication
flow, which reduces the incidence of bottlenecks in
replication over a WAN. Replicated data
compression can increase replication performance,
when network has low bandwidth.
4.2 Factional Replication
Figure 4 - Multi-Master Replication
5. Directory Proxy Server
Directory proxy server is used, in the case when
centralized data model causes scalability and
performance issues, to distribute data and route
update requests.

A global topology might require restricting 5.1 Distribution Strategy

replication for security or compliance reasons.
Take the previous scenario, an enterprise has data
There is legal restriction that specific employee
centres in Germany and Japan and its headquarters
information cannot be copied or a specific site may
is in New York. All access to the data is all over
require details of their employees only. The
the WAN. The vast majority of the data that is
fractional replication feature enables only a subset
available to employees resides centrally in legacy
of the attributes that are present in an entry to be
RDBMS repositories in London.
replicated.

4.3 Replication Strategy

Let us take a scenario, in which a enterprise has

two data centres, one in Germany and the other in
Japan, separated by WAN. The total number of
hosts is 8. A 4-way fully connected multi-master
topology is deployed in each of the data centres.
The strategy includes: Master copies of data in both
data centres, Multi-master replication is used to
provide high availability and write-failover across
the deployment, Replication is scheduled so as to
work efficiently with optimized bandwidth, For the
better performance, client applications are directed
to local servers.

Figure 5 - Distributed Directory Infrastructure


The enterprise decides to a distributed data model
as scalability and performance problems have been
experienced by them. Deployment of an LDAP
directory also been decided, as it must be deployed
in a highly available, fault-tolerant infrastructure.
As the data is customer-based, the client
community must also update customer information
from time to time.
As the organisation decides to distribute the
directory infrastructure geographically, multiple
consumers are deployed in each location. Each of
these consumers is holding data of its location only.
Data for North and South American customers is
held in the New York consumers. Data for Asian
customers is held in the Japan consumers. Data for
Europe customers is held in the Germany
consumers.
Local directory servers increased scalability and
performance of directory server. Clients request are
processed locally and hence reduce network
overhead.
Locally deployed proxy servers route all requests to
the array of server holding local data. The instances
of Directory Proxy Server are configured to load
balance across the array of directory servers. This
load balancing provides automatic failover and
failback.
If the client request for any geographical location,
local server return a referral to proxy server.
Referral includes LDAP URL which points to
geographical proxy server instance. The local
proxy server processes the referral on behalf of the
local client. It then sends the search request to the
appropriate distributed instance of proxy server.
Server forwards the search request on to the
distributed Directory Server and receives the
appropriate response. This response is then
returned to the local client through the distributed
and the local instances of Directory Proxy Server.
Update requests are also satisfied initially by a
referral returned by the local Directory Server.
Directory Proxy Server follows the referral on
behalf of the local client. However, this time the
proxy forwards the update request to the supplier
directory server located in New York. The supplier
Directory Server applies the update to the supplier
database and sends a response back to the local
client through the local Directory Proxy Server.
Subsequently, the supplier Directory Server
propagates the update down to the appropriate
consumer Directory Server.
Conclusion
In this paper we have studied deployment model of
IT data centres globally. We found that these data
centres distribute information from one location to
another in a very efficient and secure manner.
These data centres increase the performance and
scalability of data distribution with the help of
directory proxy servers. We also give brief
introduction of WAN Accelerators that work with
the design of a device in the data centres with
another device in the branch office.
A key contribution of our work is to let other
understand the concept of Global deployment in IT
data centres. It tells how the data centres work for
data distribution to maintain databases of
companies and provide security to them.
References
1. Sun Java System Directory Server
http://docs.sun.com/app/docs/doc/820-2760
2. Sun BluePrints OnLine - May 2002 By
EdwardWustenhoff –Sun Professional Services
http://www.sun.com/blueprints/0502/816-4939-
10.pdf
3. Automating the Continuous Compliance Process in
the Decentralized Enterprise by Bill Niester –
Director, Public Sector Markets
http://scap.nist.gov/events/2009/itsac/presentations
4. Integration Competency Center Global
Implementation
http://www.informatica.com/INFA_Resources
5. Joel Oleson's Blog - SharePoint Land
http://blogs.msdn.com/joelo/archive/2008/01/17/glo
bal-sharepoint-deployment-partner-solutions.aspx
6. http://blogs.cisco.com/ciscoit/comments/cisco_intern
al_waas_implementation
7. Information on data centers