Risk Management

Disaster Recovery Plan

The disaster recovery plan addresses the following areas:

1.  Hardware or software failures, data loss during development work

1. A dedicated system administrator is responsible for hardware, software, or data failures.
   SysAdmin restores data from backups that are stored outside of the office. SysAdmin is also responsible for synchronizing information between the offices
2. DataArt maintains 3 server sets:
   1. Development and demo servers at the St. Petersburg office
   2. Demo servers at the New York office
   3. Demo servers at an independent provider in St. Petersburg (Metrocom).

   When required, development or demo sites are quickly transferred to one of the backup servers.

3. No development is performed on developers' workstations. All project information (including documentation and code) is on development servers that are covered by a continuous backup routine.

2.   General office building problems (fire or other)

1. Every member of the development team has a computer at home equipped with dial-in Internet connectivity, which shall be used in case of any general office problems.

2. External server platforms are used to restore the team development environment from the backup.

3.   Internet connectivity problems

1. In St. Petersburg, there are two independent channels. Should one of them go down, dynamic routing transfers all traffic to the other one. If both lines are down, the office has dial-up connectivity for critical tasks.
2. In New York, Sprint support is used to resolve office connectivity issues. In the event the link is down during office hours, NYC staff uses dial-up access.

4.   Staff migration

1. DataArt maintains long-term contracts with employees. This ensures that we have minimal staff turnover. As a rule, a person finishes all his tasks and shares his knowledge with others before leaving the company.
2. In each project, a senior manager supervises the process. He is always up to date with project requirements and status. In the event a team member gets sick or unexpectedly leaves the company, he initiates replacement and knowledge- sharing processes.