Hi

When a new version of ALM is released, it is necessary to upgrade all projects created in ALM to be compatible with the new version of the product.

The answer is yes,  from any source you can gather the details of the projects :

The quesiton will be if your 2 app servers are in cluster or are a separated instances? if they are in cluster , they share the same site admin database,  where the information about the project databases and repositories  is stored. If they are different instances,  you need to run different times the ALM robot wizard and point it to each server.

Cordially

The ALM Robot does connect to source ALM (e.g. ALM 11.52) and to destination ALM (e.g.) in order to automate the upgrade process. The Robot automates all steps but the database schema transfer from the source database to the new one, including repository copying.

---

wrote:

... The Robot automates all steps but the database schema transfer from the source database to the new one, including repository copying.

---

I would just like to emphasize and enhance slighty what goldroy wrote.  The Robot automates all steps EXCEPT the database schema transfer and restoration from the source database to the new one and does NOT include copying the repository from the old location to the new location. 

Those four steps (backup database, transfer to new database server, restore database, and the copying of the repository must all be done by the user, manually, and before you start the Robot.

Craig

Let me clarify. The Robot does the following operations:

Mass Undo checkout for VC enabled projects

Copies repository

Restores the project to the target ALM instance

Runs the verify Repair upgrade

Restores project status

Manual steps:

Backup database

Transfer to new database server

Restore database

BTW, a very good reason for using the Robot would be that it runs a comprehensive validation check on your environment and ALM instance, which eventually reflects the system readiness for the upgrade.