Re: Development environment refresh with Production - Guidlines
Does your environment have cmdb data in it? Date: Thu, 23 Dec 2010 08:27:23 +0530 From: vaibhavsing...@hcl.com Subject: Development environment refresh with Production - Guidlines To: arslist@ARSLIST.ORG ** Hi All, We are going to perform DB refresh of Development environment from our Production Remedy Box. We already have managed about the code that is not yet in Production. Can anyone suggest some common config changes that are required after this kind of refresh? Regards, Vaibhav ::DISCLAIMER:: --- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any mail and attachments please check them for viruses and defect. --- _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
Re: Development environment refresh with Production - Guidlines
Vaibhav: The most common way I've seen to copy a production server to development is by either database backup/restore (for MS SQL) or expdp/impdp (for Oracle). Just backup/export from the production server database and restore/import to the development server database. You might have to update the development server ar.cfg (or ar.conf on *nix) and modify the database related lines. I think BMC's knowledgebase has a couple articles about how to do this. HTH, --Phil From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Vaibhav Singhal Sent: Wednesday, December 22, 2010 21:57 To: arslist@ARSLIST.ORG Subject: Development environment refresh with Production - Guidlines ** Hi All, We are going to perform DB refresh of Development environment from our Production Remedy Box. We already have managed about the code that is not yet in Production. Can anyone suggest some common config changes that are required after this kind of refresh? Regards, Vaibhav ::DISCLAIMER:: --- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any mail and attachments please check them for viruses and defect. --- _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
Re: Development environment refresh with Production - Guidlines
Hi, So you have stored away the def-changes that you need to save. If you do a DB-copy, all definitions and data will be moved. If your system has been correctly set up, there should be very few server references in the databases. Here are two places to look out for is: 1. AR System Email Mailbox Configuration, as you will probably have separate mail accounts for dev and prod 2. The report server config in AR System User Preferences If you do not need to copy the definitions, but only the data, you may want to try RRR|Chive: https://www.rrr.se/cgi/rrrchive/main Best Regards - Misi, RRR AB, http://www.rrr.se Products from RRR Scandinavia (Best R.O.I. Award at WWRUG10): * RRR|License - Not enough Remedy licenses? Save money by optimizing. * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs. Find these products, and many free tools and utilities, at http://rrr.se. > ** Hi All, We are going to perform DB refresh of Development > environment from our Production Remedy Box. We already have managed about > the code that is not yet in Production. Can anyone suggest some common > config changes that are required after this kind of refresh? Regards, > Vaibhav > ::DISCLAIMER:: > > --- > > The contents of this e-mail and any attachment(s) are confidential and > intended for the named recipient(s) only. > It shall not attach any liability on the originator or HCL or its > affiliates. Any views or opinions presented in > this email are solely those of the author and may not necessarily reflect > the opinions of HCL or its affiliates. > Any form of reproduction, dissemination, copying, disclosure, > modification, distribution and / or publication of > this message without the prior written consent of the author of this > e-mail is strictly prohibited. If you have > received this email in error please delete it and notify the sender > immediately. Before opening any mail and > attachments please check them for viruses and defect. > > > --- > _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
Development environment refresh with Production - Guidlines
** Hi All, We are going to perform DB refresh of Development environment from our Production Remedy Box. We already have managed about the code that is not yet in Production. Can anyone suggest some common config changes that are required after this kind of refresh? Regards, Vaibhav ::DISCLAIMER:: --- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any mail and attachments please check them for viruses and defect. --- _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_
