Single Window Systems
In the OIC Member States
79
Business Continuity / Disaster Recovery
There is no business continuity plan to guarantee the continuation of services and no backup
site (mirror, hot or cold recovery site) that would enable TULPAR to recover the system
efficiently from any type disruption. The TULPAR is implementing disk-to-disk backup (mirror
copy) policy. This is also critical issue, since only two instances can be used for recovery of data
and services. The best practice is to apply backup tape as an additional backup instance - disk to
disk to tape backup concept.
IT Infrastructure
The TULPAR IT architecture consists of infrastructural components of a particular type. The
implemented infrastructural model is divided into three layers according to the application
burdens performed by the component types of each layer. These layers are:
 Presentation layer: Includes component types such as web based user interface and
process components hosted by Web Server, Microsoft® Internet Information Services
(IIS) allocated in demilitarized zone (DMZ);
 Business layer: Includes component types such as business processes and single
service interface, which manage the processes and rules. The business components are
hosted by Microsoft® Internet Information Services (IIS) as Application Server. The SW
application layer consist of Customer Relationship Management (CRM), SharePoint
Server and complicated hard coded core SW application that is difficult to maintain and
further develop;
 Data layer: Includes component types such as single data layer and Microsoft ® SQL
Server 2008 EE data tools components and Web services, encapsulating the
complexities of distributing data across SW.
The TULPAR IT architecture is not designed to avoid the loss of service (downtime) whether
planned or unplanned. This is due to lack of High Availability (HA) approach (the percentage of
the agreed service timeframe for which the component or service is available). The current ICT
Infrastructure is not providing the hardware / software clustering and virtualization services in
which the SW will effectively provide the required level of service. The virtualization is used
only for SW test and development environment.
The SW Infrastructure is setup on dedicated hardware, which dramatically increases the cost to
expand the Infrastructure. The future plan is to combine the server clustering (N+1 spare node
failover) and virtualization services in order to utilize the maximum of the hardware resources.
Centralized / Common Data Layer
The TULPAR operational data resides on a single database repository (MS SQL Server 2008).
This represents a high risk in case of non-responsive or locked database thus is downgrading
the performance and efficiencies in SW operations. As well, there is a no separation of
operational and archive data (written off and expired certificates and licenses). The process of