Just another thing about Delta Migrator that's bugging me. We've had some problems with it and produced a document to BMC about some of the issues (look to the Communities page where I'll be posting some "Tips and Tricks" that are not documented in the official BMC Docs about Delta Migrator).
So one of the things that they came back with is they are saying that we need to run Delta Migrator BEFORE we make any customizations to our Destination server (like overlays). Well, what if you added 40 new fields to various forms in the source environment? If we don't overlay those forms and add those fields, they would not come over in the Delta Migrator tool. I sort of understand what they are saying that things might not map correctly, but then how do we get those fields migrated over? Things that I'm still working on with BMC. Have others that have experience with Delta Migrator tool move their customizations over first and THEN migrate data like us? Thanks! Lisa -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Misi Mladoniczky Sent: Wednesday, May 20, 2015 8:37 AM To: [email protected] Subject: Re: Delta Data Migration Tool vs RRRChive Hi, RRR|Chive does not know anything about differences in application versions. It moved data readily between AR System Servers of different versions. What exactly do you mean by "attributes"? If fields from one form has been split up into different forms, or vice versa, it might be difficult to do an efficient migration of that data using RRR|Chive. If you have added/removed a field or two, or change the field id, you can define field-mappings, and skip-fields-lists, or just ask it to work on COMMON fields. You can easily build logic to enrich/split data in the source/target environment with filters: source-server-filter: Execute On = Get Entry, Run If: ($CLIENT-TYPE$ = 6666) target-server-filter: Execute On = Merge Entry, Run If: ($CLIENT-TYPE$ = 6666) Best Regards - Misi, RRR AB, http://rrr.se > Misi, > > How does RRR|Chive handle moving from 7.6.04 SP5 to 8.1 SP2 and Attributes? > > Lisa > > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:[email protected]] On Behalf Of Misi Mladoniczky > Sent: Tuesday, May 19, 2015 4:02 PM > To: [email protected] > Subject: Re: Delta Data Migration Tool vs RRRChive > > Hi, > > The API version is not really an issue. There are no new data types in > 8.1.2, so there is no issue. > > These are some differences: > 1. RRR|Chive does not need a starting date, it will compare the modify > date on all records very efficiently, and move the delta only 2. > RRR|Chive only uses the Request ID as key 3. RRR|Chive can delete > records that has been deleted in the source 4. RRR|Chive can overwrite > records that has been updated manually in the target server, and for > example revert changes made during a test session > > Best Regards - Misi, RRR AB, http://www.rrr.se (ARSList MVP > 2011) > > Ask the Remedy Licensing Experts (Best R.O.I. Award at WWRUG10/11/12/13): > * 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, >> >> We are trying to configure the DDMT - and having trouble with the >> syntax for the config files. We were able to see differences, but not >> migrate successfully. >> >> We just want to migrate People data from one server to the next. We >> checked the RRRChive web page which shows this works for API 7.6.4. >> We are on 8.1.2. >> >> Which tool works better and is straightforward? >> >> _____________________________________________________________________ >> _ _________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org >> "Where the Answers Are, and have been for 20 years" >> > > ______________________________________________________________________ > _________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > "Where the Answers Are, and have been for 20 years" > > > ______________________________________________________________________ > _________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > "Where the Answers Are, and have been for 20 years" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
