I would recommend that anyone having trouble with Migrator 7.0.x have a look at 7.1. I have moved a fair amount of workflow and data back and forth between 7.1 ITSM servers with it, and I find it vastly improved over all previous versions. I moved a number of customized forms and workflow objects between 7.0.01.003 and 7.1 with it last month, and did not detect any errors, but I may not have audited the results as exhaustively as Rick has. I was usually satisfied when a subsequent object comparison showed no differences. Note that I was usually running it on either a 2gb RAM Vista or 1gb RAM XP client, and on both it was dramatically faster than previous versions, but one caveat; I still have to use the 5.1.2 migrator on production, so almost anything is better than that. I don't believe that you will experience problems using the 7.1 migrator between 7.0.x servers, although I never tested a 7.0 to 7.0 migration, usually 7.0 to 7.1 or 7.1 to 7.0. You may have problems with using the 7.0 migrator against a 7.1 server because of the change in license storage - I did - but who would want to? When I migrate objects, admittedly I usually turn off all of the Required Object options - a cautious habit from the past - and move everything manually, so I have not done any large-scale migrations of a major change and all of the related objects. A good acid-test in the near future might be to install ITSM patch 006 on one server, and migrate all of the differences to another, but that might be a little bit too extreme (and miss the file system changes). I might try it to move ALL of my customizations to the fresh 7.1 ITSM server I will be building out for production late this month, after backing up the clean database of course, but hopefully _after_ patch 006 comes out.
Christopher Strauss, Ph.D. Remedy Database Administrator University of North Texas Computing Center http://remedy.unt.edu/ _____ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Rick Cook Sent: Monday, September 10, 2007 6:44 PM To: [email protected] Subject: Re: Problem with Migrator ** The pattern is that it can't be trusted to do what it's supposed to do - move Remedy code and/or data from one server to another, and move ALL of it exactly - the first time it's told - so that a subsequent difference report of what it was just told to move doesn't show any appreciable differences that can't be explained by the migration masking we configure. It's like a lazy teenager that only does things halfway and has to be watched like a hawk - except that threatening Migrator doesn't work - I've tried. :-\ Rick On 9/10/07, Joe D'Souza <[EMAIL PROTECTED]> wrote: ** So what happens when you use it, it just randomly skips some permissions or is there some sort of a pattern? Joe -----Original Message----- From: Action Request System discussion list(ARSList) [mailto: [email protected] <mailto:[email protected]> ]On Behalf Of Rick Cook Sent: Monday, September 10, 2007 7:28 PM To: [email protected] Subject: Re: Problem with Migrator ** Yes, it is true. Everybody but Migrator seems to have that concept well in hand... Rick On 9/10/07, Joe D'Souza <[EMAIL PROTECTED] > wrote: ** Doesn't General Access have the same ID irrespective? I thought that when these application groups are created they get created with the same ID across any server.. Is that not true? Joe -----Original Message----- From: Action Request System discussion _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
