To create a test/development CA Service Desk Manager Advanced Availability environment, some customers have asked if they can simply clone their virtual machines from production.
This document will provide the steps to do this. However, it is important to note that this is not something that Broadcom Support will be able to provide support for as it would be outside the scope of support to troubleshoot the cloning process, or any problems that arise from cloning an environment using third party applications.
The steps provided here are applicable to an environment running CA Service Desk Manager ONLY and not for an environment where other CA Service Management applications are installed (for example CA Service Catalog). The steps provided are based on the notion that all servers, including the database server hosting the MDB, will be cloned.
CA Service Desk Manager All Versions running CA Service Desk Manager ONLY in Advanced Availability mode
Microsoft SQL Server MDB
- Repository upload servlet path(s)
- Maileater Mailboxes - ensure that there are no mailboxes configured that are in use by the production environment
- any servers that may be listed in any of the Options Manager options which could point to an application in the production environment (EEM, CABI, CA PAM, etc.)
You may want to blank out email addresses on all contact records so that false notifications do not go out for existing tickets/tasks. You can do this by running the following SQL statement:
update ca_contact set email_address=NULL
It is recommended to run through a full set of use cases to test the cloned CA SDM environment and ensure that it is working properly.