I would use each in a different situation. RRRChive: I would use when I have two identical systems that I'm migrating data between (prod->dev for example)
DDM: Useful for doing the migration from version X to version X+1....it contains all of the mappings to move data between versions when doing staged upgrades. On Wed, Apr 19, 2017 at 6:38 AM, Murnane, Phil <phil.murn...@windward.com> wrote: > ** > > We've used DDM and RRR|Chive successfully on various projects. Misi's > tool is scriptable and very fast compared to DDM. DDM can schedule code > and data migrations. Generally both require the Last-Modified date/time > field to be accurate. Overall, I'd personally recommend RRR|Chive. > > > HTH, > > --Phil > ------------------------------ > *From:* Action Request System discussion list(ARSList) < > arslist@ARSLIST.ORG> on behalf of Nicosia, Ryan J. CTR USSOCOM HQ < > ryan.nicosia....@socom.mil> > *Sent:* Wednesday, April 19, 2017 8:14 AM > *To:* arslist@ARSLIST.ORG > *Subject:* Re: [Non-DoD Source] Re: need input about data migration after > Upgrade > > I have to disagree. We used DDM with great success but it does require > admin freeze on all deletion activities of your production environment. > That said, there are ways to get around that as well but purging the form > in question on your target server and telling DDM to just pull everything > over. > > Once you get to the point where you are running DDM every few days, the > errors are easy to identify and clean up and you can re-run a specific > package as needed. > > Ryan > > -----Original Message----- > From: Action Request System discussion list(ARSList) [ > mailto:arslist@ARSLIST.ORG <arslist@ARSLIST.ORG>] On Behalf Of Mohamed > Kamruzzaman > Sent: Wednesday, April 19, 2017 5:50 AM > To: arslist@ARSLIST.ORG > Subject: [Non-DoD Source] Re: need input about data migration after Upgrade > > Hi Amit, > > Agree with Vinod, you may want to look at alternate solution considering > you are looking at migrating and cleaning your data. You will want to > migrate over foundation, configuration and transactional data onto ITSM 9.x > . This is an ideal time to clean up data, remapping Prod cats and Op Cats > etc. and potentially archive some of the tickets that you no longer need. > > We use our Customer Move Tool (more info [CAUTION] > http://www.alderstone.com/cmt) for the migration from previous ITSM > versions to the latest, as we can migrate all modules data or a reduced set > (including transformation and cleaning of data), depending on your > requirements. In general we've been able to move entire data set within a > day ensuring a smooth migration. Please let me know if you would like to > talk about this in more detail or have any specific questions. > > Regards, > Mohamed > > Mohamed Kamruzzaman. Alderstone.com +962776723269 <+962%207%207672%203269> > | mohamed.kamruzza...@alderstone.com | Skype: mkamruzzaman | LinkedIn: > Mohamed-Kamruzzaman > > ____________________________________________________________ > ___________________ > UNSUBSCRIBE or access ARSlist Archives at [CAUTION] 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" > _ARSlist: "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"
