We regularly backup/restore our project DB/Schema’s and corresponding project repository folders over to a disaster recovery server. Last week, we had an issue with a drive on our production server and since we had 2 copies of each project…the original one on the production server and a other backed-up one on the disaster recovery server, we pointed to it for our project’s DB/Schema and repositories.
While our project was pointing to the disaster recovery server, some work was done in the projects. When it came time to move back, we copied the project DB/Schema back to the production server and brought it online as a separate projects so both were available on the prod server. So we had, for example, Project_1 and Project_1_DR to indicate the one that came back from disaster recovery. The reason for this was due to corruption on the disaster recovery server and we wanted to preserve the originals just in case.
The issue came when we restored one of those projects. We accidentally pointed it to the original project's "repository"/file system rather than the repository we copied back from disaster recovery. So, we restored the project Project_1_DR (database) but pointed it to the file system for Project_1 (two projects pointing to the SAME repository folder). This project hasn't done any automation script work, but the users did create some manual tests while pointing to the disaster recovery project.
So, basically, the project’s repository/file system is a couple of weeks older than the one the project should be using.
We wanted to know, what are the potential impacts of this mistake?
Marked as spam
Please log in to participate..