Hi Brian,

I’ve not tried the Deployment Tool but if you’re looking for a comprehensive 
easy to use migrator tool with a friendly UI, take a look at ITSMBridge.  It 
includes a difference report to compare servers, pre-built templates to migrate 
selected ITSM applications (foundation and/or transaction data) and options to 
migrate between different AR/ITSM versions or from external SM platforms like 
Service Now to BMC Remedy.

HTH
Mark




> On 13 Feb 2017, at 23:00, arslist automatic digest system 
> <[email protected]> wrote:
> 
> There is 1 message totaling 560 lines in this issue.
> 
> Topics of the day:
> 
>  1. Migrator Tool
> 
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> "Where the Answers Are, and have been for 20 years"
> 
> ----------------------------------------------------------------------
> 
> Date:    Mon, 13 Feb 2017 13:19:15 +0000
> From:    Brian Pancia <[email protected]>
> Subject: Re: Migrator Tool
> 
> Misi,
> 
> 
> I've been playing around with your tools and as always they are pretty 
> awesome.  There's a new tool in ARS 9.1 called AR System Deployment 
> Management that looks pretty promising.  Messing around with Migrator was 
> painful just like I remembered.  It looks like the deployment tool will end 
> up replacing Migrator.  Another toy to add to the tool box.  I'm sure there 
> are a few kinks that need to be worked out of the deployment tool, but I'll 
> give it a go to see how it works.  I'm curious to see anyone else's 
> experience with the deployment tool.
> 
> 
> Thanks again,
> 
> 
> Brian
> 
> 
> 
> ________________________________
> From: Brian Pancia
> Sent: Friday, February 10, 2017 8:14 AM
> To: [email protected]
> Subject: Re: Migrator Tool
> 
> 
> Awesome.  New toys to play with.  I'll have to play with different scenarios 
> depending on the source and destination servers.  I'm thinking monthly syncs 
> to dev and weekly syncs to test for code.  I may do weekly data syncs to both 
> environments.  In theory Prod and Test should be locked down, preventing 
> development directly from there, but that's a different beast to tackle.  I 
> guess RRRDefDiff will be a good way for me to tell if updates are being made 
> to Prod or Test without going through Dev>Test>Prod sequence.  Batching that 
> process out may be interesting to see if developers aren't following the 
> proper process.  For a COOP environment I'm thinking using SQL replication is 
> probably the best bet.  With replication I can do near real time updates.
> 
> Brian
> ________________________________
> From: Action Request System discussion list(ARSList) <[email protected]> on 
> behalf of Misi Mladoniczky <[email protected]>
> Sent: Thursday, February 9, 2017 1:37 PM
> To: [email protected]
> Subject: Re: Migrator Tool
> 
> **
> Hi,
> 
> Why not try a combination of RRR|ExportDef, RRR|DefDiff, RRR|ImportDef and 
> RRR|DeleteObject.
> 
> The important one is RRR|DefDiff, mening that you can use other tools to 
> export/import definitions and delete surplus objects.
> 
> https://rrr.se/cgi/tools/main?tool=rrrDefDiff
> 
> RRR|DefDiff<https://rrr.se/cgi/tools/main?tool=rrrDefDiff>
> rrr.se
> RRR|DefDiff updated 2015-06-16 Finds differences between two def-files
> 
> 
> 
> https://rrr.se/cgi/tools/main?tool=rrrExportDef
> 
> RRR|ExportDef<https://rrr.se/cgi/tools/main?tool=rrrExportDef>
> rrr.se
> RRR|ExportDef updated 2012-11-23 Exports definition files from your server
> 
> 
> 
> https://rrr.se/cgi/tools/main?tool=rrrImportDef
> 
> RRR|ImportDef<https://rrr.se/cgi/tools/main?tool=rrrImportDef>
> rrr.se
> usage: rrrimportdef [ -l error.log ] [ -e error.def ] [ -verbose ] [ -silent 
> ] server tcpport user password import.def usage: rrrimportdef -help
> 
> 
> 
> https://rrr.se/cgi/tools/main?tool=rrrDeleteObject
> 
> Best Regards - Misi, RRR AB, http://www.rrr.se (ARSList MVP 2011)
> 
> RRR|Home<http://www.rrr.se/>
> www.rrr.se
> RRR|Log Fix specific performance problems or work proactively with 
> performance by using RRR|Log. It will help you make sense of the information 
> in the Remedy log ...
> 
> 
> 
> 
> 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
> 
> RRR|Home<http://rrr.se/>
> rrr.se
> RRR|Log Fix specific performance problems or work proactively with 
> performance by using RRR|Log. It will help you make sense of the information 
> in the Remedy log ...
> 
> 
> 
> 
> 
> February 9, 2017 5:52 PM, "Brian Pancia" 
> <[email protected]<mailto:%22Brian%20Pancia%22%20<[email protected]>>> 
> wrote:
> 
> I'm blowing off the dust on BMC Migrator. It has been years since I've messed 
> with it. I've used it in the past to migrate small amounts of code from dev 
> to test to production. What I'm looking at now is using it as a sync tool 
> between the environments for code only. I've usually just done a database 
> backup and restore in the past and for small code migrations I just 
> export/import .def files. There are definitely pros/cons to all these 
> methods. My plan now is to use RRRChive to migrate data updates and BMC 
> Migrator to do code migration. This will give me much more control then a 
> simple database backup and restore. Is anyone currently taking this approach 
> between dev/test/prod. We're using MS SQL 2012 on the backend, which I'll use 
> database replication between prod and coop.
> 
> Brian
> 
> DISCLAIMER: The information contained in this e-mail and its attachments 
> contain confidential information belonging to the sender, which is legally 
> privileged. The information is intended only for the use of the recipient(s) 
> named above. If you are not the intended recipient, you are notified that any 
> disclosure, copying, distribution or action in reliance upon the contents of 
> the information transmitted is strictly prohibited. If you have received this 
> information in error, please delete it immediately. _ARSlist: "Where the 
> Answers Are" and have been for 20 years_
> _ARSlist: "Where the Answers Are" and have been for 20 years_
> DISCLAIMER: The information contained in this e-mail and its attachments 
> contain confidential information belonging to the sender, which is legally 
> privileged. The information is intended only for the use of the recipient(s) 
> named above. If you are not the intended recipient, you are notified that any 
> disclosure, copying, distribution or action in reliance upon the contents of 
> the information transmitted is strictly prohibited. If you have received this 
> information in error, please delete it immediately.
> 
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> "Where the Answers Are, and have been for 20 years"
> 
> ------------------------------
> 
> End of arslist Digest - 12 Feb 2017 to 13 Feb 2017 (#2017-38)
> *************************************************************


_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Reply via email to