Re: CMDB dev to production
This document explain what you need to do: BMC Atrium CMDB 7.6.04 Administrator's Guide Chapter 5 Migrating BMC Atrium Core data -- J 2011/2/26 John Doe : > ** > Hi all, > > I am in the process of trying to figure out how to migrate the CI's in our > dev CMDB to production. We have appoximately 100,000. > > Our production CMDB is an exact copy of our dev CMDB minus our actual CI's. > We are just trying to migrate all of our CI's from the dev CDM to the > production CDM. > > I have given thought to AIE (using it to connect to an external database) or > using BMC Migrator. Essentially, we would be transferring CI's from one 7.6 > remedy system(dev) to another like remedy 7.6 system(prod). SQL Server 08 > on Windows. > > We are currently utilizing other modules in production system with active > users. > > Any ideas? > > Thank you > > _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: CMDB dev to production
The best way to achieve this is to export the CI's into a CSV. Then use AIE to bring them from excel into production. Tim -Original Message- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of John Doe Sent: Saturday, February 26, 2011 9:47 AM To: arslist@ARSLIST.ORG Subject: CMDB dev to production ** Hi all, I am in the process of trying to figure out how to migrate the CI's in our dev CMDB to production. We have appoximately 100,000. Our production CMDB is an exact copy of our dev CMDB minus our actual CI's. We are just trying to migrate all of our CI's from the dev CDM to the production CDM. I have given thought to AIE (using it to connect to an external database) or using BMC Migrator. Essentially, we would be transferring CI's from one 7.6 remedy system(dev) to another like remedy 7.6 system(prod). SQL Server 08 on Windows. We are currently utilizing other modules in production system with active users. Any ideas? Thank you _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: CMDB dev to production
You could try exporting and importing the CI’s using cmdbdriver but the files get very big very quickly which may defeat the import. You could also try rrrChive to copy CI’s and then relationship CI’s across the servers. If your CI’s have other non-CMDB relationships such as Asset Management relationships to support groups then you may need to copy these over as well. From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of John Doe Sent: 26 February 2011 23:44 To: arslist@ARSLIST.ORG Subject: Re: CMDB dev to production ** >From my original post "I have given thought to AIE (using it to connect to an external database) or using BMC Migrator. Essentially, we would be transferring CI's from one 7.6 remedy system(dev) to another like remedy 7.6 system(prod). SQL Server 08 on Windows." Even if we were on oracle, the impdp/expdp commands in oracle would overright our current production system when importing. We have an operating production system with production users. _ From: Joe Martin D'Souza To: arslist@ARSLIST.ORG Sent: Sat, February 26, 2011 11:06:40 AM Subject: Re: CMDB dev to production ** If you are on Oracle, you could use the Oracle imp and exp tools to selectively export and import data. This should work even given the unique nature of relationships in CMDB since you say that your production environment matches your development environment. You may need to manually set your next ID’s if you choose this method. Joe From: John Doe <mailto:hornetl...@yahoo.com> Sent: Saturday, February 26, 2011 11:46 AM Newsgroups: public.remedy.arsystem.general To: arslist@ARSLIST.ORG Subject: CMDB dev to production ** Hi all, I am in the process of trying to figure out how to migrate the CI's in our dev CMDB to production. We have appoximately 100,000. Our production CMDB is an exact copy of our dev CMDB minus our actual CI's. We are just trying to migrate all of our CI's from the dev CDM to the production CDM. I have given thought to AIE (using it to connect to an external database) or using BMC Migrator. Essentially, we would be transferring CI's from one 7.6 remedy system(dev) to another like remedy 7.6 system(prod). SQL Server 08 on Windows. We are currently utilizing other modules in production system with active users. Any ideas? Thank you _attend WWRUG11 www.wwrug.com <http://www.wwrug.com/> ARSlist: "Where the Answers Are"_ _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: CMDB dev to production
>From my original post "I have given thought to AIE (using it to connect to an external database) or using BMC Migrator. Essentially, we would be transferring CI's from one 7.6 remedy system(dev) to another like remedy 7.6 system(prod). SQL Server 08 on Windows." Even if we were on oracle, the impdp/expdp commands in oracle would overright our current production system when importing. We have an operating production system with production users. From: Joe Martin D'Souza To: arslist@ARSLIST.ORG Sent: Sat, February 26, 2011 11:06:40 AM Subject: Re: CMDB dev to production ** If you are on Oracle, you could use the Oracle imp and exp tools to selectively export and import data. This should work even given the unique nature of relationships in CMDB since you say that your production environment matches your development environment. You may need to manually set your next ID’s if you choose this method. Joe From: John Doe Sent: Saturday, February 26, 2011 11:46 AM Newsgroups: public.remedy.arsystem.general To: arslist@ARSLIST.ORG Subject: CMDB dev to production ** Hi all, I am in the process of trying to figure out how to migrate the CI's in our dev CMDB to production. We have appoximately 100,000. Our production CMDB is an exact copy of our dev CMDB minus our actual CI's. We are just trying to migrate all of our CI's from the dev CDM to the production CDM. I have given thought to AIE (using it to connect to an external database) or using BMC Migrator. Essentially, we would be transferring CI's from one 7.6 remedy system(dev) to another like remedy 7.6 system(prod). SQL Server 08 on Windows. We are currently utilizing other modules in production system with active users. Any ideas? Thank you_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: CMDB dev to production
If you are on Oracle, you could use the Oracle imp and exp tools to selectively export and import data. This should work even given the unique nature of relationships in CMDB since you say that your production environment matches your development environment. You may need to manually set your next ID’s if you choose this method. Joe From: John Doe Sent: Saturday, February 26, 2011 11:46 AM Newsgroups: public.remedy.arsystem.general To: arslist@ARSLIST.ORG Subject: CMDB dev to production ** Hi all, I am in the process of trying to figure out how to migrate the CI's in our dev CMDB to production. We have appoximately 100,000. Our production CMDB is an exact copy of our dev CMDB minus our actual CI's. We are just trying to migrate all of our CI's from the dev CDM to the production CDM. I have given thought to AIE (using it to connect to an external database) or using BMC Migrator. Essentially, we would be transferring CI's from one 7.6 remedy system(dev) to another like remedy 7.6 system(prod). SQL Server 08 on Windows. We are currently utilizing other modules in production system with active users. Any ideas? Thank you ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
