Ghosting would help I guess, you would only have to re-apply your dev licenses to the machine, and of course, check your ar.conf file for the database name etc.
There would be one other benefit in ghosting; the dev environment will be completely the same again as the production environment.
One other gotcha: please make sure that if you have the e-mail engine installed on dev as well to prevent it from sending messages by pointing it to a non-existing SMTP server or by setting the email engine service to "Manual" and stopping it. You would not be the first sending out notifications for tickets that have been long solved...
Re-installing would also work I guess. What you could do is to opt for "overwrite db", and after the install has finished, stop arserver, restore a copy of the production db on the dev serverand start arserver.
--
Michiel
On 7/31/06, Kathy Morris <[EMAIL PROTECTED]> wrote:
**__20060125_______________________This posting was submitted with HTML in it___Our system doesn't seem to be recovering too well after the group duplications. I tried arreload, arcache, upgrade, restoring the backup of the database. The application still hangs since the admin imported multiple groups.Our technical team wants to ghost production and turn this to the development server. We have CMDB, Mid Tier, Change Mgmt., Help Desk on both servers. I didn't think ghosting would be a better option than reinstalling. Is ghosting Prod the better solution?
__20060125_______________________This posting was submitted with HTML in it___
