Recovery steps after ALM corruption

ALM is HP's software development life cycle software, the full name is Application Lifecycle Management, its use of B/s structure, from requirements, business models to test cases and defect management should also have to meet the general software enterprise development of the product and project management , powerful and easy to use.

I am in the company use of ALM using Microsoft SQL Server as its database, has been used well, but in Saturday, where the office in Friday without notice of temporary power outage for several hours, although there are ups, but the outage time is too long lead to ALM and SQL Server (both deployed on the same machine) or shut down due to a power outage. When this Monday morning to work only to find the shutdown, start the machine still found unable to use, later found that the corresponding database is in suspect state.

After finding the data, it is hard to do a good job of the database (see the MS SQL Server 2008 database in suspect case processing), but ALM is still unusable, the main performance is to create a defect prompt error after login, the execution of the test case also prompts the same error, as shown in.

Looking for information again, but did not find the relevant information, and finally had to replace the machine to reinstall SQL Server and ALM, this time I put SQL Server and ALM separately installed in different machines.

After that, in the original ALM with the administrator account into the site management, the previous project was exported successfully, the exported file name extension. qcp.

Finally, new projects are created in the new ALM and the way the projects are exported before they are imported, I find that the previous database is also imported into the process, that is, the data of the database is not dedicated to processing.

After the import is complete, I found the Cup: unable to log in.

Because the information is not found, we have to try to solve the problem: To verify the imported project, as shown in. The result of the verification is that a problem was found, and then the project was repaired and the repair was successful, but still unable to log in,

Then tell yourself to be calm, carefully check their own operation process: found that the original ALM is a SP2 version, And the new ALM is the 11.0 version, and then to the newly installed ALM SP2, after the installation of the login and execute test case test, found that there is no problem, it is very gratifying ah.

Summary of lessons Learned:

1. The ALM database needs to be backed up so that it can be restored at the time of the problem, in a way that is backed up once per day and incrementally in a daily manner. If you've backed up before, it won't be so much trouble. In addition to spit slot under Microsoft's SQL Server database, really too fragile, power outages such common things caused the database to hang up, and at that time no one to the ALM and SQL Server operation, the database actually prompted the log file is incomplete.

The 2.ALM itself is cumbersome to back up, and if there is a problem, you can take the pilot out project and then reinstall ALM and import the project, but remember to keep the same version as the previous Alm.

Recovery steps after ALM corruption