Disaster Recovery

1. Disaster Recovery
• Describes how Performix deals with potential disasters.
• Code and Data protection strategy
• We have UPS system with 8 hrs backup when all the system is up & all users logged in.
• We have 2 different internet providers to handle the connectivity issues. All ISP lines are up & running at any
given point. In case of any failure situations, the router automatically connects the other line to Network,
keeping the network availability un-interrupted.
• Scope spans to 2 Servers, all the servers on Network are exposed through VPN. The user ID & password
required for network from outside the organization, thereby assuring un-interrupted work at any given point
of time. This formation helps in situation when the office facility is in-accessible due to any disasters.
• We use Bit Bucket as Version control system, where the source code repository is maintained. This allows
distributed software development process & at any given point in time all the users work on the updated
code, thereby elimination the data redundancy or working on OLD code situation.
• All the data backup (Testing Database) happens on a daily basis on Local machines and this backup is then
moved to the external hard drives. At present, we keep backups on the server as well as on network storage
hard drive
• As part of RPO process, we take backup of databases daily. Hence the estimated data loss is of 24 hours i.e.
RPO = 24. The RTO required for this is estimated to 24 hours or 1 day.