Thanks Alex! @Venkat - the instructions that Alex provided the link for are specifically for offline reporting - not necessarily a dev/staging environment. The steps allow you to replicate certain tables and not others, which is ok for reporting, but wont allow you to configure a fully running replica of production. If the offline reporting meets your needs, then go with that for sure. If what you are looking for is to create a full blown replica of production, you would need to follow the manual steps as follows:
1. Follow the steps here to backup the db from prod and restore to staging environment: Move the CA MDB Database on Microsoft SQL Server - CA Service Management - 17.0 - CA Technologies Documentation
2. once you have restored the MDB from prod to staging, and you have restored the alcdb tables, and inactivated the records in the usp_servers table, you can copy over the following from prod and put them in place on staging:
- site\mods directory
- site\attachments directory (or other directory that you are storing attachments in)
3. run pdm_configure
4. go into WSP and then go into schema designer - make a dummy update to a table by adding an "X" to the description field on the right side for any object. For example, click on any table, then on the right side, put an "X" in the description field. Then click File > Save. Now remove that "X", and click File > Save and Publish.
5. stop CA SDM services
6. run pdm_publish
7. run pdm_configure again
8. log into SDM and add the additional servers and configurations for the staging environment
9. run configure on each server in that environment including the background
10. test out the system
That is the basic high level overview of the process.
Hope this helps,
Thanks,
Jon I.