**
I can add my vote for rrrchive as well. During our drawn out upgrade to 7.6.04, it ran from PROD to UPGRADE all day and night (using Windows batch files) keeping everything in sync until we were ready to go live. Then all we did was shut everyone out of PROD, run the sync one more time, and point the network to the new servers (there were a few minor updates to some forms with server references but it was relatively smooth).

We still use it even now to continuously update our archive/reporting server through Windows batch files and scheduling.

Can't say enough good things about it.

Thanks, Misi.

On Jan 15, 2014, at 08:35 AM, Chad Wilhelm <[email protected]> wrote:

We use RRR Chive.  We synced millions of records with no problems so far.

 

https://www.rrr.se/cgi/index?pg=chive

 

Thank You,

Chad Wilhelm
CareTech Solutions
Office: (248) 823-0177

<image001.gif>


Helping extraordinary peopledo extraordinary things

Best in KLAS

Partial IT Outsourcing 2012

Extensive IT Outsourcing
2008, 2009, 2010 and 2011

Best in KLAS Awards:
Software & Services

www.KLASresearch.com

 

<image002.jpg>

­­­­­

 

 

 

 

From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Dale Jones
Sent: Wednesday, January 15, 2014 12:00 AM
To: [email protected]
Subject: Re: Migration of Foundation and Historical Data ITSM 7.6 to ITSM 8 - Using Spoon

 

**

Brad,

You have multiple options to move data, I would first like to ask a couple questions.
Transactional Data - Number of INC, CHG, SRM, PBM, Task.  Just ballpark 100K or > million. Volume per month 50K, 100K or >million
Number of open tickets INC, CHG, SRM, PBM, Task

I have leveraged ARX exports and imports for most of my customers transactional data migrations to 8.1 (1 initial move then multiple Delta moves up to Go Live weekend.  Added a handful of cleanup filters and an escalation or two to trigger cleanup.  The main cleanup is on open records that need to modified and will trip validation filter errors.  Also have added an exclusion to some existing validation filters  (ie 'Submit Date' > "01/01/14")   (Go Live date 01/01/14 example)

 

Dale Jones

DCS

Raleigh, NC

919-523-6034


From: Action Request System discussion list(ARSList) [[email protected]] on behalf of BradRemedy [[email protected]]
Sent: Tuesday, January 14, 2014 11:22 PM
To: [email protected]
Subject: Migration of Foundation and Historical Data ITSM 7.6 to ITSM 8 - Using Spoon

**

Hi All

 

Hope everyone is well.

 

We are busy with our upgrade to ITSM 8 and have setup a completely new environment which will host the Version 8 applications. We are currently running Remedy 7.6 P003 with ITSM 7.6 and SRM 7.6.

 

The new environment has been setup and configured and is working perfectly and we now come to the task of migrating the data from ITSM 7.6 to the new ITSM 8 environment. For now, we are focusing on the foundation data as that is the most important part and I was wondering how everyone who has done this upgrade has managed to move their data over.

 

I was looking at using the spreadsheets, however it is alot of admin work and with any data updates or changes on our currently live 7.6 environment, we would need to make sure that we apply those updates to the version 8 environment.

 

Ideally, we would like a automated solution / scripted solution that we can run which would update the data and keep the new environment in sync.

 

It was suggested by another developer that we look at possibly using the Atrium Integration Spoon application to do this data migration and that we create a transformation job which we can re-run etc.

 

Has anyone done this before? If not, would you please share how your company / project was able to migrate their data?

 

Any assistance would be greatly appreciated.

 

Thanks

Brad

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

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

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

Reply via email to