Just out of curiosity, how do you handle a situations like these using any 
other system?

 

Ø  A table in 7.1 has a field which has a NULL value consistently.  In 8.1 the 
same field exists in the same table BUT must have a proper value in it for the 
GUI to work.  There is Active Link workflow that relies on this field having a 
value.  Indeed the value can be set with a single manually concocted SQL Update 
statement after the migration but it is only one example.

Ø  The Release module did not exist in 7.1.  Instead there were Changes of type 
Release.  How do you migrate that with anything other than Meta-Update?  And 
it’s tasks into activities?

Ø  How do you migrate a running Clarify help desk into a running ITSM – imagine 
different companies users, groups, statuses, etc all.  We did this with 
Meta-Update over a weekend.  The Clarify analysts were working on their tickets 
Friday and continued to work on their same tickets Monday – but on ITSM.  All 
in under 2 man-months (including analysis of the Clarify db structures).

Ø  How do you correct the CMDB Classes of a badly migrated system.  All CIs 
were computer systems but had proper CTI information.  These were worked a year 
so they had contracts, tickets, changes etc associated as well as CI 
relationships.  A single Meta-Update script developed in 2 days read a search 
and replace Excel sheet specifying what CTI Class to transfer to what CTI Class 
and replicated the CIs in the correct class with the changed or not CTIs.  
Humans checked a few records and the same script was run to delete the original 
CIs.  The ITSM Admins ran the script.  Problem solved in 4 days.

Ø  How do you do proper tree based archiving with checking of associations (an 
archivable incident related to a non-archivable change should not be archived)? 
 Meta-Update does this  – all with no forms or fields mentioned in the script.  
The ITSM structure is defined in the Archiving configuration file making it 
easy to add your own customised forms.  It even builds the Archive forms for 
you.

 

Yes.  The API is slow compared to SQL.  And Meta-Update is no doubt slower that 
other API tools (it takes the value set from Remedy and keeps it in a unified 
type internally and the converts it back when needed, and has masses of logging 
and auditing code).  

 

But it offers you the flexibility to set those fields as needed and migrate 
things like Change record to Release records.  Millions of records have been 
moved through it – albeit slowly J  

 

Cheers

Ben

 


Ben Chernys
Senior Software Architect
logoSthInc-sm  

Canada / Deutschland
Mobile:      +49 171 380 2329    GMT + 1 + [ DST ]
Email:        <mailto:Ben.Chernys_AT_softwaretoolhouse.com> 
Ben.Chernys_AT_softwaretoolhouse.com
Web:          <http://www.softwaretoolhouse.com/> www.softwaretoolhouse.com

We are a BMC Technology Alliance Partner

 

 

Check out Software Tool House's free Diary Editor and our  Freebies Section for 
ITSM Forms and Fields spreadsheet.

Meta-Update, our premium ARS Data tool, lets you automate your imports, 
migrations, in no time at all, without programming, without staging forms, 
without merge workflow. 

 

Meta-Archive does ITSM Archiving your way: with your forms and your 
multi-tenant rules, treating each root request as the tree of data and forms 
that it is it is.

 

Pre ITSM 7.6.04?  Clarify?  Roll your own?  No problem!

You can keep your valuable data!


 <http://www.softwaretoolhouse.com/> http://www.softwaretoolhouse.com/  

 

 

 

 

 

 

From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORG] On Behalf Of Charlie Lotridge
Sent: October-07-14 17:53
To: arslist@ARSLIST.ORG
Subject: Re: RRR|Chive vs. DDM

 

** 

Hi Lyndsay,

 

A bit over a year ago I architected & implemented the data migration for my 
client at the time, which involved an upgrade from 7.1 to 8.1, and a migration 
of the data from Oracle to SQL Server.  Like you, we only wanted to migrate a 
subset of the data and leave a whole bunch of garbage behind.

 

This custom solution had a Remedy based control and configuration application 
along with a .NET executable. The control & config app was used pretty simply 
to describe which forms we were interested in migrating along with connection 
and authentication info. The exe then used this info to affect the data 
transfer.

 

Unlike other Remedy based data migration tools out there, this solution did NOT 
transfer the data through the Remedy servers, but instead used the ARS data 
dictionary info about each of the required forms to dynamically construct SQL 
statements which affected the data transfers through a database link between 
the legacy and new DBs (e.g. SELECT INTO and UPDATE FROM type statements).  It 
was very fast.

 

If you don't find another solution and are interested, I'd be happy to provide 
more details about how this thing worked.

 

-charlie

 

On Tue, Oct 7, 2014 at 7:42 AM, Ben Chernys <ben.cher...@softwaretoolhouse.com> 
wrote:

** 

There is also Meta-Update <http://www.softwaretoolhouse.com/>  and specifically 
the ITSM 7.1 Migration Package 
<http://www.softwaretoolhouse.com/product/PkgMigItsm/index.html>  of scripts 
which allows you to change your companies, organization, people, support 
structure, product catalogue – and even Changes of type Release into Releases – 
along the way.

 

No it is not free but the costs are small compared to the efforts saved.

 

Contact me off list for more details or trials.

 

Cheers

 


Ben Chernys
Senior Software Architect
logoSthInc-sm  

Canada / Deutschland
Mobile:      +49 171 380 2329 <tel:%2B49%20171%20380%202329>     GMT + 1 + [ 
DST ]
Email:       Ben.Chernys_AT_softwaretoolhouse.com
Web:          <http://www.softwaretoolhouse.com/> www.softwaretoolhouse.com

We are a BMC Technology Alliance Partner

 

 

Check out Software Tool House's free Diary Editor and our  Freebies Section for 
ITSM Forms and Fields spreadsheet.

Meta-Update, our premium ARS Data tool, lets you automate your imports, 
migrations, in no time at all, without programming, without staging forms, 
without merge workflow. 

 

Meta-Archive does ITSM Archiving your way: with your forms and your 
multi-tenant rules, treating each root request as the tree of data and forms 
that it is it is.

 

Pre ITSM 7.6.04?  Clarify?  Roll your own?  No problem!

You can keep your valuable data!


 <http://www.softwaretoolhouse.com/> http://www.softwaretoolhouse.com/  

 

 

 

 

 

From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORG] On Behalf Of Lyndsay Reese
Sent: October-07-14 15:51
To: arslist@ARSLIST.ORG
Subject: RRR|Chive vs. DDM

 

** 

Hello arslisters,

I am in need of a good data migration tool to get all of our current ARS/ITSM 
7.5 production data over to our new ARS/ITSM 8.1.01 fresh install server, with 
moderate customizations (we were not interested in copying our full prod db to 
the new server and then upgrading it, as it has had its own issues in the past 
with prior installs and upgrades and customizations). Therefore, the servers 
are not identical. The new server is built, customized, and UAT tested. We do 
have a development server where we took a db copy of prod, upgraded it to 
8.1.01 (to match versions with the new server) and now we need to migrate the 
data. I've never used RRR|Chive or DDM. Is one better than the other for this 
type of migration?

 

Thanks in advance for any thoughts/opinions/suggestions.

 

Lyndsay

_ARSlist: "Where the Answers Are" and have been for 20 years_ 

No virus found in this message.
Checked by AVG - www.avg.com
Version: 2013.0.3485 / Virus Database: 4031/8340 - Release Date: 10/07/14

_ARSlist: "Where the Answers Are" and have been for 20 years_

 

_ARSlist: "Where the Answers Are" and have been for 20 years_ 

No virus found in this message.
Checked by AVG - www.avg.com
Version: 2013.0.3485 / Virus Database: 4031/8343 - Release Date: 10/07/14


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

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to