Disaster Recovery (DR) Setup
As part of our comprehensive Disaster Recovery plan, we have implemented the following measures to ensure data integrity and quick recovery in case of any unforeseen issues:
- Main Teamforge Directories:
The critical directories, including /opt/collabnet/teamforge/var, var/scm/svnroot, and var/scm/gerrit/gitroot, are mounted on an NS (Network Storage) mount. This setup safeguards our data in the event of any local drive issues, as all crucial information resides in the secure NS mount.
- VM Snapshots:
We take daily snapshots of the entire TeamForge server. These snapshots capture the server's state at specific points in time, allowing us to revert to a previous snapshot in case of emergencies or data loss. This provides an added layer of protection and flexibility during recovery operations.
- Parallel Teamforge DR Server:
With the AWS service in place, we have set up a parallel TeamForge Disaster Recovery (DR) server. This setup ensures that our server data is replicated in real-time, maintaining two identical copies simultaneously. One copy represents the current Production environment, while the other serves as the DR environment. If there are any issues with the Production environment, we can quickly switch to the DR server. Currently, this switching process is a manual operation.
P.S: Post-AWS Migration Enhancement:
We introduced the DR feature after migrating to AWS from Rackspace. This enhancement has significantly improved our Disaster Recovery capabilities and strengthened our data resilience.
As a part of our DR strategy, we maintain an additional data copy in AWS for every second change in the DR environment. Moreover, we take separate VM snapshots daily to ensure comprehensive data backup.
By implementing these measures, we are well-prepared to handle any unexpected events and ensure the continuity and security of our data.
This documentation serves as a reference for our Disaster Recovery plan and provides transparency on our data protection practices.