ZINFI IT Infrastructure

www.zinfi.
com
IT Infrastructure Overview
Ext.prc.002.01 | 02.04.2019
UCM 10.x
ZINFI Confidential & Proprietary

Shared Under NDA
1 | © 2019 ZINFI Technologies Inc. All Rights Reserved. ZINFI Confidential & Proprietary Document - Shared under NDA.
www.zinfi.com
Contents
Section 1: Database Type & Scalability............................................................ 3
1.1 Capabilities of Database Infrastructure .................................................................. 3
1.2 Enterprise-Class Scalability ................................................................................... 4
1.3 Scale out (Horizontal Scaling) of Database Environment ....................................... 4
1.4 Scale up (Vertical Scaling) of Database Environment ............................................ 5
Section 2: Hardware Scalability, Software Scalability & DR ........................... 5
2.1 Initial IIS Web Application Server Hardware Configuration ..................................... 6
2.2 Initial Database Server Hardware Configuration .................................................... 6
2.3 Hardware Global Load Balancer ............................................................................ 6
2.4 DNS Auto Failover ................................................................................................. 7
2.5 Monitoring .............................................................................................................. 7
2.6 Monitoring and Data Collection for Performance Management .............................. 7
2.7 Monitoring and Data Collection .............................................................................. 8
2.8 Disaster Recovery and Backup .............................................................................. 8
Section 3: Location & Security of Data Center .............................................. 12
Data Center Design ................................................................................................................................ 13
3.1 Data Center Security at a glance ......................................................................... 13
3.2 Specification of Data Center Space ..................................................................... 13
3.3 Layer 1: Physical & Operational Security ............................................................. 14
Physical and operational security is the foundation of Security Layer. ................................................... 14
3.4 Layer 2: Network Security .................................................................................... 14
3.5 Layers 3 – 5: System, Application & Data Security............................................... 15
www.zinfi.com
Section 1: Database Type & Scalability
ZINFI uses Relational Database Management System (RDBMS) of Microsoft SQL Server 2012 Enterprise
Edition in Cluster mode (2 physical Servers) running under Windows Server 2012 R2 Data Center Edition
Operating System to structure and process data at the backend.
1.1 Capabilities of Database Infrastructure
 Our Database Server has high-end Database query performance which can be boosted on demand by 10-100x
with xVelocity in-memory column store index for data warehousing.
 More consistent performance is provided on demand for concurrent and mixed workloads by defining
resource usage with Resource Governor.
 We monitor specific events and capture server events for near real-time diagnosis using SQL Server
Profiler.
 We visualize resource utilization with multi-server management to proactively make changes before
trouble arises.
 We collect data from T-SQL queries and bundle it into a collection set for analysis using the
Performance Data Collector.
 I/O intensive workloads are accelerated by cutting the growing volumes of data approximately 50-60%
with high-grade compression capabilities.
www.zinfi.com
1.2 Enterprise-Class Scalability
Continuous performance Monitoring will be done in order to assess the scaling opportunities.
The following diagram (Figure: 1) explains the variables involved in our Performance & Scalability Model:
Figure 1
1.3 Scale out (Horizontal Scaling) of Database Environment
 The Database Server capabilities can grow beyond the constraints of any deployment environment
with Hybrid IT opportunities across Traditional Server as well as Cloud Server.
 We can expand data warehouses with database features like Remote Blob Storage and partitioned
tables that scale to 15,000 partitions.
 We can scale out heavily accessed databases while maintaining consistency with Peer-to-Peer
Replication.
 The Database Servers can leverage Service Broker to build more highly scalable, service-oriented
solutions.
www.zinfi.com
1.4 Scale up (Vertical Scaling) of Database Environment
Current Servers are configured with 8 x 64-bit logical processors and 64 GB of RAM. Based on the usage, the
current servers are barely loaded. We can further improve scalability and performance of future workloads and
consolidation scenarios with up to 320 logical processors and 4 TB of memory.
Section 2: Hardware Scalability, Software

Scalability & DR
The following diagram (Figure: 2) describes the scalability and disaster recovery (DR) model of our hosting
environment:
Figure 2
www.zinfi.com
The following specification represents our Server configurations:
2.1 Initial IIS Web Application Server Hardware Configuration
Intel Xeon Quad core CPU 64 bit 16 GB of DDR3 RAM

SATA HDD Array of 500GB with RAID 1 controller (basic protection from HDD failure)
2.2 Initial Database Server Hardware Configuration
Dual Intel Xeon Quad core CPU 64 bit 64 GB of DDR3 RAM

Hot Swappable SATA HDD Array of 4TB with RAID 5 controller (protected from HDD failure)
2.3 Hardware Global Load Balancer
Load Balancing: Our enterprise-class load balancing solution utilizes industry -standard techniques to balance
traffic among two or more servers, even between geographically diverse Data Centers. It can be instantly
activated and ready to configure, and Servers can be added to or removed from the balancing pool on-demand
with no downtime.
Our dedicated servers can be upgraded to hex-core, and even GPU-powered Servers. They can all be
deployed in real time.
If a distributed architecture is required, the global private network used lets us deploy cloud servers in
Singapore and dedicated servers in San Jose and communicate between them as if they were in the same
rack, with no back-end network charges or additional connectivity products to buy.
The Flex Images server deployment system provides image capture and deployment for dedicated, just like
virtualized cloud servers, unified across both technologies. Build on cloud, move to dedicated servers and
back again as our needs evolve, or leverage features like real-time cloning and image-based backup with our
physical servers.
www.zinfi.com
2.4 DNS Auto Failover
By directing your traffic at the DNS level, we have the power and flexibility to maximize uptime and be available
to our customers 24/7. This is especially important for customer sites that have people browsing and using the
services round the clock. Every minute of downtime means loss of revenue, something that no one wants.
With automatic re-routing capabilities, our web users will never know if there was an issue, because they will
never experience a delay or dropped request.
Auto rollback works when the target server appears to be back online or available, our system will automatically
restore its DNS entry to its original IP address. Manual Rollback process is also performed when we need to
verify the availability and integrity of data and services.
2.5 Monitoring
ZINFI has automatic real time monitoring enabled by NMS software which sends Email on reaching the
predefined threshold of malfunction and also emergency SMS Service is enabled on critical issues.
2.6 Monitoring and Data Collection for Performance Management
The following list of performance counters is considered a base set of counters when we monitor the resource
usage on the RDS workload. Log the performance counters to a local, raw (blg) performance counter log. It is
less expensive to collect all instances (‘*’ wide character) and then extract particular instances while post-
processing by using Relog.exe:
\Cache\*
\IPv4\*
\LogicalDisk(*)\*
\Memory\*
\Network Interface(*)\*
\Paging File(*)\*
\PhysicalDisk(*)\*
\Print Queue(*)\*
\Process(*)\*
\Processor Information(*)\*
\Synchronization(*)\*
\System\*
\TCPv4\*
www.zinfi.com
Note: If applicable, we also add the \IPv6\* and \TCPv6\* objects and the parameter related to current
connections.
Additional measures are taken for performance tuning of Operating System and Database Server.
2.7 Monitoring and Data Collection
The following list of performance counters is considered a base set of counters when you monitor the resource
usage:
\Terminal Service Gateway\*

\RPC/HTTP Proxy\*
\RPC/HTTP Proxy Per Server\*
\Web Service\*
\W3SVC_W3WP\*
\IPv4\*
\Memory\*
\Network Interface(*)\*
\Process(*)\*
\Processor Information(*)\*
\Synchronization(*)\*
\System\*
\TCPv4\*
Note: If applicable, add the “\IPv6\*” and “\TCPv6\*” objects.
2.8 Disaster Recovery and Backup

The pictorial representation (Figure: 2.8) of our Data Center DR structure is as follows:
Figure 3
www.zinfi.com
There is no such significant down time from Disaster as all data are synced and backed up in almost real time
to other offshore Data Center in the Europe.
Local Incremental, Differential and Full backup are scheduled to back up the Server Data to external storage
network as an additional security measure. The below mentioned table has a brief detail of Backup Type and
Schedule of running the backup.
Backup Type Schedule
Incremental Daily, every 6 hours
Full Weekly, Sunday mid night
Differential Weekly, Thursday mid night
Global load balancing between our geographically diverse Data Center facilities keeps traffic evenly distributed
for optimized performance and availability.
In the event of Server failure in one location, loads can be automatically shifted to the other functioning
systems.
ZINFI’s test management methodology provides a clear and concise approach that focuses on detecting
defects early through quality checks while identifying, quantifying, and mitigating risk. An integral part of the
agile methodology, business driven test management assesses project/product risks to increase visibility and
improve decision making. We use our in-house testing tools that we have developed as the foundation for test
management processes.
www.zinfi.com
The following is a brief overview of our QA and Test Plans:
1. Initiate and Plan: QA is involved early in the SDLC to contribute to the overall project charter from a QA
strategy perspective and to support the project from a testing perspective. Early
involvement of the QA Lead reduces the knowledge transfer effort for the other stake holders.
2. Requirements Analysis Phase: The Requirement Analysis Phase incorporates the Planning and Control
phases when creating functional requirements. This provides the basis for a manageable and high quality
testing process. The value of the development planning, the expected quality of the test object, organization
of the various tasks and the availability of staff, infrastructure and time are factors that are taken into account
in determining the test estimation and approach.
3. Design Phase: The Design Phase aligns to the Preparation Phase of the test management process. The
first activity during this phase is knowledge acquisition of the Test Team. Once the first version of the
specification is ready with an adequate level of quality, the actual preparation activities begin. This phase
consists of detailed review of the specification and other documentation that serve as the starting point for
testing (Static Testing).
4. Build Phase: The Build Phase is aligned to the Specification Phase of the Test Management. In this phase,
the test cases are specified and the accompanying test infrastructure is realized. A test case consists of a
description of the input, the process to be executed, and a prediction of the expected output. In parallel to the
test design, the test infrastructure is constructed. Developers conduct unit tests during this phase and unit
tests are reviewed and verified by the QA Team.
5. Test Phase: The Verification Phase starts as soon as the first testable components of the software product
are available and align to Execution Phase. When (parts of) the software product, the infrastructure and the
test database are available, the first pre-tests are executed to check whether the main functions of the object
can be tested. As soon as the pre-tests have been completed successfully, test execution can start using the
test scripts to validate the functionality. If there is a difference between the test result and the expected result,
it indicates a software product or specification defect, a defect in the test infrastructure, or an invalid test case.
www.zinfi.com
Key Deliverables Quality Checks Action Plan
Test Execution Report Integration test Execute the tests
at different
Defect Status Report System test
levels, log and
Execution and Defect Metrics Regression test
track defects to
Phase End Test Summary Performance test closure, capture
Report Automation (if applicable) relevant metrics
Process Compliance Report
Test Phase Activities
6. Deployment Phase: The Deployment Phase map to the Test Management Completion Phase and
support period, which occur after the completion of test execution.
Our PMs do a round of UAT, i.e. the testing process and the quality of the product are evaluated in front of the
customer. Quantities of statistics are used to improve the future planning and optimization of the testing
processes, development processes, and the quality of the system.
By adapting to the process described above, the following additional advantages are anticipated, potentially
reducing the testing cost:
 Prevention and discovery of defects at an early stage

 Test execution is the only activity on the critical path of the testing lifecycle
 The test process is comprehensible, manageable and business driven.
www.zinfi.com
Section 3: Location & Security of Data Center
ZINFI is using shared Data Center space of a renowned Service Provider (IBM Softlayer). Location of our
Primary Data Center is at Dallas in USA and a similar auto failover setup is running in multiple country locations
to comply with data privacy laws, along with performance requirements.
The following Figure (Figure: 4) shows Global Locations of Data Centers:
Figure 4
Additionally, our Data Center is self-certified with the U.S. Department of Commerce’s U.S.-European Union
(EU) Safe Harbor framework, verifying that the Data Center meets the EU’s adequacy standard for data and
privacy protection.
www.zinfi.com
Data Center Design
The following figure (Figure: 5) shows our Data Center Infrastructure Design pattern:
Figure 5
3.1 Data Center Security at a glance
 SSAE16 (SOC1) Compliant Data Center Infrastructure.

 24/7 physical security and monitoring of Data Centers and Network Operations Centers.
 Integrated server hardening using Hardware and Software both mechanisms.
 Regular full-system virus scanning and systems patching.
 We perform regular security profile review and mitigate the risks.
3.2 Specification of Data Center Space
 UPS battery backup units

 Diesel generator with on-site fuel storage Water chillers
 Redundant Liebert HVAC units
 Pre-action dry pipe fire suppression
 Proximity security badge access
 Digital security video surveillance
www.zinfi.com
3.3 Layer 1: Physical & Operational Security
Physical and operational security is the foundation of Security Layer.
 Data Center and Server Room Measures

 Data Centers located only in facilities with controlled access and 24-hour security
 No server room doors are public-facing
 Server rooms are staffed 24/7
 Un-marked entry and exit doors
 Digital security video surveillance
 Biometric security systems
 Server room access strictly limited to employees.
Operational Measures
 Engineers and technicians trained on internal industry standard policies and procedures and audited
yearly.
 Geographic redundancy for all core systems for disaster recovery and business continuity.
 2-factor authentication for Customer Portal access adds greater server security.
 All data removed from re-provisioned machines with drive wipe software approved by the
Department of Defense.
3.4 Layer 2: Network Security
Network-Within-a-Network Infrastructure
 Public Network handles public traffic to hosted websites or online resources

 Private Network allows for true out-of-band management through a distinct stand-alone third carrier
over SSL, PPTP or IPSEC VPN gateways.
 Data Center to Data Center Network provides secure connectivity between servers hosted in separate
locations.
www.zinfi.com
3.5 Layers 3 – 5: System, Application & Data Security
McAfee® Virus Scan and Host Intrusion Servers: These systems combine anti-virus, anti-spyware, firewall,
and intrusion prevention technologies to stop and remove malicious software from your infrastructure.
RescueLayer®: Boot failed servers into a RAM-disk recovery kernel with the failed server’s regular IP
addresses, giving it full access to private and public networks, NAS and backend service network servers, a
wide range of tools and disk recovery utilities, on-board file systems, and locally attached storage.
Network IDS/IPS Protection: Through partnerships with leading hardware and software vendors, a complete
array of intrusion protection and assessment options at both the network and host level.
Nessus® Vulnerability Assessment and Reporting: Providing the world leader in active scanners, featuring
high speed discovery, configuration auditing, asset profiling, sensitive data discovery, and vulnerability
analysis of security posture.

ZINFI IT Infrastructure

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

ZINFI IT Infrastructure

Caricato da

Copyright:

Formati disponibili

www.zinfi.

ZINFI Confidential & Proprietary

Section 1: Database Type & Scalability

1.1 Capabilities of Database Infrastructure

1.2 Enterprise-Class Scalability

1.3 Scale out (Horizontal Scaling) of Database Environment

1.4 Scale up (Vertical Scaling) of Database Environment

Section 2: Hardware Scalability, Software

The following specification represents our Server configurations:

2.1 Initial IIS Web Application Server Hardware Configuration

Intel Xeon Quad core CPU 64 bit 16 GB of DDR3 RAM

2.2 Initial Database Server Hardware Configuration

Dual Intel Xeon Quad core CPU 64 bit 64 GB of DDR3 RAM

2.3 Hardware Global Load Balancer

2.4 DNS Auto Failover

2.6 Monitoring and Data Collection for Performance Management

2.7 Monitoring and Data Collection

\Terminal Service Gateway\*

Note: If applicable, add the “\IPv6\*” and “\TCPv6\*” objects.

2.8 Disaster Recovery and Backup

Backup Type Schedule

Incremental Daily, every 6 hours

Full Weekly, Sunday mid night

Differential Weekly, Thursday mid night

The following is a brief overview of our QA and Test Plans:

Key Deliverables Quality Checks Action Plan

Test Execution Report Integration test Execute the tests

Report Automation (if applicable) relevant metrics

Process Compliance Report

Test Phase Activities

 Prevention and discovery of defects at an early stage

Section 3: Location & Security of Data Center

The following Figure (Figure: 4) shows Global Locations of Data Centers:

Data Center Design

3.1 Data Center Security at a glance

 SSAE16 (SOC1) Compliant Data Center Infrastructure.

3.2 Specification of Data Center Space

 UPS battery backup units

3.3 Layer 1: Physical & Operational Security

Physical and operational security is the foundation of Security Layer.

 Data Center and Server Room Measures

3.4 Layer 2: Network Security

 Public Network handles public traffic to hosted websites or online resources

3.5 Layers 3 – 5: System, Application & Data Security

Potrebbero piacerti anche

Note: If applicable, add the “\IPv6\” and “\TCPv6\” objects.