RE: Data Migration after upgrade from 2 disparate ITSM instances

2018-07-03 Thread Manoharan, Karthik 
Thanks a lot JD Hood.

Regards,
Karthik.

From: ARSList [mailto:arslist-boun...@arslist.org] On Behalf Of JD Hood
Sent: Tuesday, July 03, 2018 5:34 PM
To: ARSList
Subject: Re: Data Migration after upgrade from 2 disparate ITSM instances

Hi Karthik,

I've used the DDM as a data pump before. It was not designed for that, but it 
will do the job if given enough time. It's just *extremely* slow.

If all you are moving is foundation data, then instead of DDM, you might want 
to consider exporting the foundation data into the data loader spreadsheets 
(found in v9 under "Data Management" in the application menu).

The tabs of the worksheets will lead you to the forms that hold the data you 
need to export.

Once you get the data in excel, it would be trivial to sort/filter out any 
duplicates.

Then you would just create the data loader jobs and let it do its thing.

The hardest part is making sure all the data entered (particularly any data 
that is a number) are formatted as TEXT values in excel. If it's not TEXT, it 
could import as an integer or some number format and you will see (for 
instance) phone numbers like 888.0-555.0-1234.0, instead of 888-555-1234.

I find dealing with data errors is much easier with the data loader too, since 
it imports the data first to a load sheet for data validation. Once in those 
load sheets, you can use modify all or purpose-built workflow to bulk fix any 
errors.

Good luck with whatever you decide to do!
-JDHood


On Tue, Jul 3, 2018 at 12:26 AM, Manoharan, Karthik 
mailto:karthik.manoha...@cgi.com>> wrote:
Hello Listers,

Currently there are 2 different ITSM environments A and B running on different 
version 7.6 and 8.1.
I’m planning to setup a single ITSM instance 9.1 by installing a standalone 
ITSM instance and migrating foundation data from 2 disparate ITSM instances 
(A+B).
I’ve explored BMC Delta Data Migrator and found that we could use it to migrate 
from instance A.
Let's assume I've migrated from instance A. The problem arises when performing 
migration from the second instance B.

There are would be lot of duplicate records(which might not be actually 
duplicate but from instance A)
DDM would identify matching unique index values and may have different Request 
ID/ Instance ID values from instance A.
This would involve lot of manual activity to validate and delete in case of 
duplicates, but most of the cases we would like to retain records from both 
servers.

Could you please help with any suggestions for any other tool for data 
migration or any different approach for the same.

Thanks in advance.

Regards,
Karthik.

--
ARSList mailing list
ARSList@arslist.org<mailto:ARSList@arslist.org>
https://mailman.rrr.se/cgi/listinfo/arslist<https://urldefense.proofpoint.com/v2/url?u=https-3A__mailman.rrr.se_cgi_listinfo_arslist=DwMFaQ=H50I6Bh8SW87d_bXfZP_8g=vtTp6THS8v_3NkXkX7OYKsYNrKXbAYcsNz87iHKVu88=eC-yzIrpuTXCPkO1mo_C-ql-03857q-SdlgTPhYKB0c=G6b4whbMUim7XQ0awlhULtzNK82O6VlasuGSdET7Ruc=>

-- 
ARSList mailing list
ARSList@arslist.org
https://mailman.rrr.se/cgi/listinfo/arslist

RE: Data Migration after upgrade from 2 disparate ITSM instances

2018-07-03 Thread Ben Chernys 
Hi Karthik,

 

With Meta-Update request ids can be changed and dependent records will reflect 
the newly assigned request ids where needed.  So can instance ids but that 
“should” not be needed.  In addition support groups can be merged from the two 
systems or renamed as needed.

 

Please speak to us off-list if you want any further information.

 

 


Cheers,

Ben Chernys
Senior Software Architect
  

Canada / Deutschland
Mobile:+49 171 380 2329   GMT - 7 + [ DST ]

Mobile +1 403  554 0887
Email: 
ben.cher...@softwaretoolhouse.com
Web:   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 a complete tree and checking associatuions.  
Archive output to different servers, HTML pages with links to attachments or 
archive forms.

 

  Meta-Databot is 
an automated, extensible BMC Data Wizard.  It reads a file of data changes and 
sports an Undo feature.

 

Pre ITSM 9.1.04?  Clarify?  HP? Roll your own?  No problem!  You can keep your 
valuable data!


  http://www.softwaretoolhouse.com/  

 

 

 

 

 

From: ARSList  On Behalf Of karthik manoharan
Sent: July-02-18 10:21 PM
To: arslist@arslist.org
Subject: Data Migration after upgrade from 2 disparate ITSM instances

 

Hello Listers,

Currently there are 2 different ITSM environments A and B running on different 
version 7.6 and 8.1.

I’m planning to setup a single ITSM instance 9.1 by installing a standalone 
ITSM instance and migrating foundation data from 2 disparate ITSM instances 
(A+B).

 

I’ve explored BMC Delta Data Migrator and found that we could use the same to 
migrate from instance A.

Let's assume I've migrated from instance A. The problem arises when performing 
migration from the second instance B. There are would be lot of duplicate 
records(which might not be actually duplicate but from instance A)

DDM would identify matching unique index values and may have different Request 
ID/ Instance ID values from instance A.

This would involve lot of manual activity to validate and delete in case of 
duplicates, but most of the cases we would like to retain records from both 
servers.

Is there any suggestions for any other tool for data migration or any different 
approaches for the same.

Regards,

Karthik.

 

-- 
ARSList mailing list
ARSList@arslist.org
https://mailman.rrr.se/cgi/listinfo/arslist

Re: Data Migration after upgrade from 2 disparate ITSM instances

2018-07-03 Thread JD Hood 
Hi Karthik,

I've used the DDM as a data pump before. It was not designed for that, but
it will do the job if given enough time. It's just *extremely* slow.

If all you are moving is foundation data, then instead of DDM, you might
want to consider exporting the foundation data into the data loader
spreadsheets (found in v9 under "Data Management" in the application menu).

The tabs of the worksheets will lead you to the forms that hold the data
you need to export.

Once you get the data in excel, it would be trivial to sort/filter out any
duplicates.

Then you would just create the data loader jobs and let it do its thing.

The hardest part is making sure all the data entered (particularly any data
that is a number) are formatted as TEXT values in excel. If it's not TEXT,
it could import as an integer or some number format and you will see (for
instance) phone numbers like 888.0-555.0-1234.0, instead of 888-555-1234.

I find dealing with data errors is much easier with the data loader too,
since it imports the data first to a load sheet for data validation. Once
in those load sheets, you can use modify all or purpose-built workflow to
bulk fix any errors.

Good luck with whatever you decide to do!
-JDHood


On Tue, Jul 3, 2018 at 12:26 AM, Manoharan, Karthik <
karthik.manoha...@cgi.com> wrote:

> Hello Listers,
>
>
>
> Currently there are 2 different ITSM environments A and B running on
> different version 7.6 and 8.1.
>
> I’m planning to setup a single ITSM instance 9.1 by installing a
> standalone ITSM instance and migrating foundation data from 2 disparate
> ITSM instances (A+B).
>
> I’ve explored BMC Delta Data Migrator and found that we could use it to
> migrate from instance A.
>
> Let's assume I've migrated from instance A. The problem arises when
> performing migration from the second instance B.
>
>
>
> There are would be lot of duplicate records(which might not be actually
> duplicate but from instance A)
>
> DDM would identify matching unique index values and may have different
> Request ID/ Instance ID values from instance A.
>
> This would involve lot of manual activity to validate and delete in case
> of duplicates, but most of the cases we would like to retain records from
> both servers.
>
>
>
> Could you please help with any suggestions for any other tool for data
> migration or any different approach for the same.
>
>
>
> Thanks in advance.
>
>
>
> Regards,
>
> Karthik.
>
> --
> ARSList mailing list
> ARSList@arslist.org
> https://mailman.rrr.se/cgi/listinfo/arslist
>
>
-- 
ARSList mailing list
ARSList@arslist.org
https://mailman.rrr.se/cgi/listinfo/arslist

Re: Data Migration after upgrade from 2 disparate ITSM instances

2018-07-03 Thread Mark Herring 
Hi Karthik,

Yes you can use ITSM Bridge to do this;

When migrating from Instance B, define the primary key for each form mapping in 
the form mapping definition.  Then you can control the behaviour as follows:

If the target record exists on your new instance and you don’t want to 
over-write, set the option to skip.
If the target record exists and you want to update it with values from instance 
B, set the option to Update.
If the target record exists but you want to create another copy - use the 
assignment mapping to prefix or suffix the primary key field to make the target 
record unique.

Hope that helps

Mark Herring

itsmbridge.com



















> On 3 Jul 2018, at 11:00, arslist-requ...@arslist.org wrote:
> 
> Send ARSList mailing list submissions to
>   arslist@arslist.org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
>   https://mailman.rrr.se/cgi/listinfo/arslist
> or, via email, send a message with subject or body 'help' to
>   arslist-requ...@arslist.org
> 
> You can reach the person managing the list at
>   arslist-ow...@arslist.org
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of ARSList digest..."
> 
> 
> Today's Topics:
> 
>   1. RE: Renaming Business Service Names (Ben Chernys)
>   2. Data Migration after upgrade from 2 disparate ITSM instances
>  (karthik manoharan)
>   3. Data Migration after upgrade from 2 disparate ITSM instances
>  (Manoharan, Karthik)
> 
> 
> --
> 
> Message: 1
> Date: Mon, 2 Jul 2018 09:12:31 -0600
> From: "Ben Chernys" 
> To: "'ARSList'" 
> Subject: RE: Renaming Business Service Names
> Message-ID: <55cbd01d41217$1ad37340$507a59c0$@softwaretoolhouse.com>
> Content-Type: text/plain; charset="us-ascii"
> 
> Meta-Databot works like the BMC Data Wizard but is automated and extensible.
> It processes spreadsheets of changes.  
> 
> 
> 
> Putting up a new Data admin config is as easy as adding a new sheet to the
> configuration Excel file.
> 
> 
> 
> Meta-Databot is free with Meta-Update and we would put up the new
> configuration sheet for you.
> 
> 
> 
> 
> 
> 
> Cheers,
> 
> Ben Chernys
> Senior Software Architect
> 
> 
> Canada / Deutschland
> Mobile:+49 171 380 2329   GMT - 7 + [ DST ]
> 
> Mobile +1 403  554 0887
> Email:
> ben.cher...@softwaretoolhouse.com
> Web:   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 a complete tree and checking associatuions.
> Archive output to different servers, HTML pages with links to attachments or
> archive forms.
> 
> 
> 
>  Meta-Databot
> is an automated, extensible BMC Data Wizard.  It reads a file of data
> changes and sports an Undo feature.
> 
> 
> 
> Pre ITSM 9.1.04?  Clarify?  HP? Roll your own?  No problem!  You can keep
> your valuable data!
> 
> 
>  http://www.softwaretoolhouse.com/  
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> From: ARSList  On Behalf Of
> gurupra...@trimeg.co.uk
> Sent: June-29-18 9:47 AM
> To: arslist@arslist.org
> Subject: Renaming Business Service Names
> 
> 
> 
> Hi Guys,
> 
> Is there any easy way of renaming the business service CI in ITSM and its
> related transactional references in the system ie. Incident, change etc ?
> 
> 
> 
> Regards,
> 
> Guru
> 
> -- next part --
> An HTML attachment was scrubbed...
> URL: 
> 
> -- next part --
> A non-text attachment was scrubbed...
> Name: image003.jpg
> Type: image/jpeg
> Size: 2441 bytes
> Desc: not available
> URL: 
> 
> 
> --
> 
> Message: 2
> Date: Tue, 3 Jul 2018 09:51:08 +0530
> From: karthik manoharan 
> To: arslist@arslist.org
> Subject: Data Migration after upgrade from 2 disparate ITSM instances
> Message-ID:
>   
> Content-Type: text/plain; charset="utf-8"
> 
> Hello Listers,
> 
> Currently there are 2 different ITSM environments A and B running on
> different version 7.6 and 8.1.
> 
> I?m planning to setup a single ITSM instance 9.1 by installing a standalone
> ITSM

Re: Data Migration after upgrade from 2 disparate ITSM instances

2018-07-03 Thread Mohamed Kamruzzaman 
Hi Karthik,

This is something Alderstone CMT 
 can definitely help with 
and we have done this for a number of customers. Please see some details around 
consolidation for your reference below:


What is Consolidation?
Consolidation is the process of merging one or more BMC Remedy ITSM systems 
together. All users and integrations of the old Remedy systems will use the new 
consolidated Remedy system.

This process is technically complex and logistically challenging. However, a 
successful consolidation can result in significant cost savings and operational 
benefits. Examples of the reasons that businesses may choose to perform a 
consolidation include;
 
Reducing the number of multi-tenant BMC Remedy ITSM Systems
Customers who manage ITSM as a service on multi-tenant BMC Remedy ITSM systems, 
often have more than one multi- tenant system for various reasons including 
geographical performance or legal constraints. Reductions in hardware and 
software costs and/or improved operational efficiency can be realised by 
merging multi-tenant environments together to create fewer multi-tenant 
environments.
Typical approaches may be to;
Move Company(s) from an existing multi-tenant ITSM Remedy system into an 
existing, in-use multi-tenant system.
Move Company(s) from two or more multi-tenant ITSM Remedy systems into a new, 
clean Remedy system.
Any consolidation operation will cause some level of disruption for the 
customers of a multi-tenant system. If the benefit of
the disruption of a typical consolidation activity and accrues solely to the 
operator of the multi-tenant platform this can cause customer relationship 
issues. Combining the consolidation of multi-tenant systems with an ITSM 
application upgrade can offer clear business benefit to the customer, therefore 
this is a common component of these types of consolidations.
 
Moving an customer from an on-premise ITSM Remedy System into an existing 
multi-tenant system
Onboarding a customer from an existing on-premise Remedy system into a 
multi-tenancy system managed by a different company is effectively a 
consolidation of the two Remedy environments. Multi-tenant BMC Remedy ITSM 
systems typically have a high level of control around the shared application 
data. On-premise customers usually make free use of the shared data 
configuration in ITSM. Onboarding a customer into a multi-tenant system usually 
involves analysis and transformation of the data to ensure there is no impact 
to existing customers.
 
Merging two businesses using BMC Remedy ITSM
When two companies, or business units within the same company, merge their 
operations, significant reductions in costs
can be achieved by consolidation of the Remedy ITSM systems. This operation is 
likely to involve high levels of data transformation as the use of Remedy ITSM 
in the two businesses is likely to have a number of differences with no shared 
data discipline in either system.
 
Technical Challenges
Historically, the major challenge for the consolidation of Remedy systems has 
been the data migration component. The three principal data migration 
challenges when performing consolidation are;
 
Poor Performance
The Remedy API, used by all legacy tools, is not engineered for data migration. 
It can take several, resource-intensive weeks to migrate all data in a Remedy 
application. This is of particular concern for consolidation into an live 
Production Remedy system where a large volume of data needs to be moved during 
a  short cutover window.
 
Unique Identifier Clashes
Application unique Identifiers such as Request IDs, Group IDs and Ticket 
Numbers are only unique within a single Remedy system. Merging data without 
reconciling these unique keys seriously compromises data integrity and security 
and impacts the viability of the core Remedy application.
For example
Two different Companies in two different systems may have been assigned the 
same Group ID. If they are merged without transforming the Group IDs throughout 
all data in the application then they would be able to see each others data.
Incident Tickets will be overwritten as they were assigned the same Request ID 
in two different systems.
 
Lack of control
Legacy data migration tools do not provide the capabilities for identifying, 
migrating or transforming related sets of Remedy data. Even with the investment 
of significant development effort, it is challenging to achieve the control 
necessary to support the complex data migration and transformation operations 
necessary for consolidation.
Data Transformation is a key component of Consolidation where often data such 
as Support Group and Company names or Categorisations have to realigned between 
two systems which requires very large scale data changes through configuration 
and ticket data need to be applied.
 
In short, Consolidation is technically very difficult and is not supported by 
legacy data migration tools.

Re: Data migration from 7.6.0 server to 7.6.4 server

2011-12-07 Thread Gmail 
Your best bet is DMT. DMT has been greatly enhancement in v7.6.4 over 7.6.
As for the order, the order is defined in each template.

Moe.

-Original Message-
From: Guillaume Rheault [mailto:guilla...@dcshq.com] 
Sent: Tuesday, December 06, 2011 7:45 PM
Subject: Re: Data migration from 7.6.0 server to 7.6.4 server

Hi Dan,

You probably already knows, but the only things that comes close is taking a
look at the ITSM Data Management tool, Data Load Console.
The Sequence in the table field denotes the order of the data loads

Guillaume


From: Action Request System discussion list(ARSList) [arslist@ARSLIST.ORG]
on behalf of Dan [daniel.b.pritch...@gmail.com]
Sent: Monday, November 28, 2011 10:29 AM
To: arslist@ARSLIST.ORG
Subject: Data migration from 7.6.0 server to 7.6.4 server

Is there documentation out there that shows the order to which we should
migrate our data over.  We have built a new server and want to
push all of our production data over so that we can roll it over.   I
have looked but cannot seem to find an order to which we should migrate.  We
are using Remedy Migrator to do the push.  I would use RRRChive from Misi
but we cannot put additional software on our systems.


___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12
www.wwrug12.com ARSList: Where the Answers Are


___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12
www.wwrug12.com ARSList: Where the Answers Are

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug12 www.wwrug12.com ARSList: Where the Answers Are

Re: Data migration from 7.6.0 server to 7.6.4 server

2011-12-06 Thread Guillaume Rheault 
Hi Dan,

You probably already knows, but the only things that comes close is taking a 
look at the ITSM Data Management tool, Data Load Console.
The Sequence in the table field denotes the order of the data loads

Guillaume


From: Action Request System discussion list(ARSList) [arslist@ARSLIST.ORG] on 
behalf of Dan [daniel.b.pritch...@gmail.com]
Sent: Monday, November 28, 2011 10:29 AM
To: arslist@ARSLIST.ORG
Subject: Data migration from 7.6.0 server to 7.6.4 server

Is there documentation out there that shows the order to which we
should migrate our data over.  We have built a new server and want to
push all of our production data over so that we can roll it over.   I
have looked but cannot seem to find an order to which we should
migrate.  We are using Remedy Migrator to do the push.  I would use
RRRChive from Misi but we cannot put additional software on our
systems.

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug12 www.wwrug12.com ARSList: Where the Answers Are

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug12 www.wwrug12.com ARSList: Where the Answers Are

Re: Data Migration

2008-04-22 Thread Misi Mladoniczky 
Hi,

Everything should be migrated.

The data is copied using the API, so the actual T/B/H tables are not
accessed directly by Migrator. Or so I would think...

You can also use our RRR|Chive to move the data. In this case, I
definitely know that all the data for each form is copied.

You can move all your data in a single pass of RRR|Chive.

RRR|Chive can also do incremental copying of your data. Anything
modified/deleted on the target server will be restored. Anything changed
on the source server will copied over. Just use the SYNCTOTARGET-mode
which is default if you use the online configurator.

https://www.rrr.se/cgi/rrrchive/main

Best Regards - Misi, RRR AB, http://www.rrr.se

Products from RRR Scandinavia:
* RRR|License - Not enough Remedy licenses? Save money by optimizing.
* RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs.
* RRR|Translator - Manage and automate your language translations.
Find these products, and many free tools and utilities, at http://rrr.se.

 While I think I know the answer to this I would like to be sure. When
 migrating data using Migrator is on the data from the T-tables migrated.
 I cannot find anything in the documentation that states whether data
 from B or H tables is or even can be migrated. I am thinking not. Thanks
 in advance for your help.



 Regards,



 Roger A. Nall
 Manager, OSSNMS Remedy
 T-Mobile, USA
 Desk: 813-348-2556
 Cell: 973-652-6723
 FAX: 813-348-2565
 sf49fanv AIM IM
 RogerNall Yahoo IM




 ___
 UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
 Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are

 --
 This message was scanned by ESVA and is believed to be clean.



___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are

Re: Data Migration

2008-04-22 Thread Nall, Roger 
Misi,

Thanks for getting back to me. While I am sure you are correct I am
wondering if anyone can confirm that indeed all data from the T, H, and
B tables is moved when using Migrator. This is a very important question
for me right now and I must be as sure as I can of the answer.

Thanks,

Roger A. Nall 
Manager, OSSNMS Remedy 
T-Mobile, USA 
Desk: 813-348-2556 
Cell: 973-652-6723 
FAX: 813-348-2565 
sf49fanv AIM IM 
RogerNall Yahoo IM 

-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Misi Mladoniczky
Sent: Tuesday, April 22, 2008 10:08 AM
To: arslist@ARSLIST.ORG
Subject: Re: Data Migration

Hi,

Everything should be migrated.

The data is copied using the API, so the actual T/B/H tables are not
accessed directly by Migrator. Or so I would think...

You can also use our RRR|Chive to move the data. In this case, I
definitely know that all the data for each form is copied.

You can move all your data in a single pass of RRR|Chive.

RRR|Chive can also do incremental copying of your data. Anything
modified/deleted on the target server will be restored. Anything changed
on the source server will copied over. Just use the SYNCTOTARGET-mode
which is default if you use the online configurator.

https://www.rrr.se/cgi/rrrchive/main

Best Regards - Misi, RRR AB, http://www.rrr.se

Products from RRR Scandinavia:
* RRR|License - Not enough Remedy licenses? Save money by optimizing.
* RRR|Log - Performance issues or elusive bugs? Analyze your Remedy
logs.
* RRR|Translator - Manage and automate your language translations.
Find these products, and many free tools and utilities, at
http://rrr.se.

 While I think I know the answer to this I would like to be sure. When
 migrating data using Migrator is on the data from the T-tables
migrated.
 I cannot find anything in the documentation that states whether data
 from B or H tables is or even can be migrated. I am thinking not.
Thanks
 in advance for your help.



 Regards,



 Roger A. Nall
 Manager, OSSNMS Remedy
 T-Mobile, USA
 Desk: 813-348-2556
 Cell: 973-652-6723
 FAX: 813-348-2565
 sf49fanv AIM IM
 RogerNall Yahoo IM






___
 UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
 Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are

 --
 This message was scanned by ESVA and is believed to be clean.




___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are

Re: Data Migration

2008-04-22 Thread Misi Mladoniczky 
Hi Roger,

I am 99.9 percent sure that everything is moved with Migrator.

Why not test it? Just copy a record with an attachment, then check to see
that both attachment and Status-History (Ctrl-H) is there.

Best Regards - Misi, RRR AB, http://rrr.se

 Misi,

 Thanks for getting back to me. While I am sure you are correct I am
 wondering if anyone can confirm that indeed all data from the T, H, and
 B tables is moved when using Migrator. This is a very important question
 for me right now and I must be as sure as I can of the answer.

 Thanks,

 Roger A. Nall
 Manager, OSSNMS Remedy
 T-Mobile, USA
 Desk: 813-348-2556
 Cell: 973-652-6723
 FAX: 813-348-2565
 sf49fanv AIM IM
 RogerNall Yahoo IM

 -Original Message-
 From: Action Request System discussion list(ARSList)
 [mailto:[EMAIL PROTECTED] On Behalf Of Misi Mladoniczky
 Sent: Tuesday, April 22, 2008 10:08 AM
 To: arslist@ARSLIST.ORG
 Subject: Re: Data Migration

 Hi,

 Everything should be migrated.

 The data is copied using the API, so the actual T/B/H tables are not
 accessed directly by Migrator. Or so I would think...

 You can also use our RRR|Chive to move the data. In this case, I
 definitely know that all the data for each form is copied.

 You can move all your data in a single pass of RRR|Chive.

 RRR|Chive can also do incremental copying of your data. Anything
 modified/deleted on the target server will be restored. Anything changed
 on the source server will copied over. Just use the SYNCTOTARGET-mode
 which is default if you use the online configurator.

 https://www.rrr.se/cgi/rrrchive/main

 Best Regards - Misi, RRR AB, http://www.rrr.se

 Products from RRR Scandinavia:
 * RRR|License - Not enough Remedy licenses? Save money by optimizing.
 * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy
 logs.
 * RRR|Translator - Manage and automate your language translations.
 Find these products, and many free tools and utilities, at
 http://rrr.se.

 While I think I know the answer to this I would like to be sure. When
 migrating data using Migrator is on the data from the T-tables
 migrated.
 I cannot find anything in the documentation that states whether data
 from B or H tables is or even can be migrated. I am thinking not.
 Thanks
 in advance for your help.



 Regards,



 Roger A. Nall
 Manager, OSSNMS Remedy
 T-Mobile, USA
 Desk: 813-348-2556
 Cell: 973-652-6723
 FAX: 813-348-2565
 sf49fanv AIM IM
 RogerNall Yahoo IM





 
 ___
 UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
 Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are

 --
 This message was scanned by ESVA and is believed to be clean.



 
 ___
 UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
 Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are

 ___
 UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
 Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are

 --
 This message was scanned by ESVA and is believed to be clean.



___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are

Re: Data Migration

2008-04-22 Thread LJ Longwing 
You could setup a simple form with an attachment on it, create a record and
add the attachment, then migrate that record to the other server and see if
it made it over there with the status historyI seriously doubt it won't,
I mean...the migration tool sucks in several aspects, but it usually 'works
as advertised' for the most part...and only migrating information from T
would not be working as advertised 

-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Nall, Roger
Sent: Tuesday, April 22, 2008 10:35 AM
To: arslist@ARSLIST.ORG
Subject: Re: Data Migration

Misi,

Thanks for getting back to me. While I am sure you are correct I am
wondering if anyone can confirm that indeed all data from the T, H, and B
tables is moved when using Migrator. This is a very important question for
me right now and I must be as sure as I can of the answer.

Thanks,

Roger A. Nall
Manager, OSSNMS Remedy
T-Mobile, USA
Desk: 813-348-2556
Cell: 973-652-6723
FAX: 813-348-2565
sf49fanv AIM IM
RogerNall Yahoo IM 

-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Misi Mladoniczky
Sent: Tuesday, April 22, 2008 10:08 AM
To: arslist@ARSLIST.ORG
Subject: Re: Data Migration

Hi,

Everything should be migrated.

The data is copied using the API, so the actual T/B/H tables are not
accessed directly by Migrator. Or so I would think...

You can also use our RRR|Chive to move the data. In this case, I definitely
know that all the data for each form is copied.

You can move all your data in a single pass of RRR|Chive.

RRR|Chive can also do incremental copying of your data. Anything
modified/deleted on the target server will be restored. Anything changed on
the source server will copied over. Just use the SYNCTOTARGET-mode which is
default if you use the online configurator.

https://www.rrr.se/cgi/rrrchive/main

Best Regards - Misi, RRR AB, http://www.rrr.se

Products from RRR Scandinavia:
* RRR|License - Not enough Remedy licenses? Save money by optimizing.
* RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs.
* RRR|Translator - Manage and automate your language translations.
Find these products, and many free tools and utilities, at http://rrr.se.

 While I think I know the answer to this I would like to be sure. When 
 migrating data using Migrator is on the data from the T-tables
migrated.
 I cannot find anything in the documentation that states whether data 
 from B or H tables is or even can be migrated. I am thinking not.
Thanks
 in advance for your help.



 Regards,



 Roger A. Nall
 Manager, OSSNMS Remedy
 T-Mobile, USA
 Desk: 813-348-2556
 Cell: 973-652-6723
 FAX: 813-348-2565
 sf49fanv AIM IM
 RogerNall Yahoo IM






___
 UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum 
 Sponsor: www.rmsportal.com ARSlist: Where the Answers Are

 --
 This message was scanned by ESVA and is believed to be clean.




___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:
www.rmsportal.com ARSlist: Where the Answers Are


___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:
www.rmsportal.com ARSlist: Where the Answers Are

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are

Re: Data Migration

2008-04-22 Thread Nall, Roger 
LJ and Misi,

You both make valid points. Like I said I could not find anything in the
documentation that would confirm or deny my understanding. Now that I
have sound examples I can move on.

Thanks again form the help.

Roger A. Nall 
Manager, OSSNMS Remedy 
T-Mobile, USA 
Desk: 813-348-2556 
Cell: 973-652-6723 
FAX: 813-348-2565 
sf49fanv AIM IM 
RogerNall Yahoo IM 
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of LJ Longwing
Sent: Tuesday, April 22, 2008 12:59 PM
To: arslist@ARSLIST.ORG
Subject: Re: Data Migration

You could setup a simple form with an attachment on it, create a record
and
add the attachment, then migrate that record to the other server and see
if
it made it over there with the status historyI seriously doubt it
won't,
I mean...the migration tool sucks in several aspects, but it usually
'works
as advertised' for the most part...and only migrating information from T
would not be working as advertised 

-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Nall, Roger
Sent: Tuesday, April 22, 2008 10:35 AM
To: arslist@ARSLIST.ORG
Subject: Re: Data Migration

Misi,

Thanks for getting back to me. While I am sure you are correct I am
wondering if anyone can confirm that indeed all data from the T, H, and
B
tables is moved when using Migrator. This is a very important question
for
me right now and I must be as sure as I can of the answer.

Thanks,

Roger A. Nall
Manager, OSSNMS Remedy
T-Mobile, USA
Desk: 813-348-2556
Cell: 973-652-6723
FAX: 813-348-2565
sf49fanv AIM IM
RogerNall Yahoo IM 

-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Misi Mladoniczky
Sent: Tuesday, April 22, 2008 10:08 AM
To: arslist@ARSLIST.ORG
Subject: Re: Data Migration

Hi,

Everything should be migrated.

The data is copied using the API, so the actual T/B/H tables are not
accessed directly by Migrator. Or so I would think...

You can also use our RRR|Chive to move the data. In this case, I
definitely
know that all the data for each form is copied.

You can move all your data in a single pass of RRR|Chive.

RRR|Chive can also do incremental copying of your data. Anything
modified/deleted on the target server will be restored. Anything changed
on
the source server will copied over. Just use the SYNCTOTARGET-mode which
is
default if you use the online configurator.

https://www.rrr.se/cgi/rrrchive/main

Best Regards - Misi, RRR AB, http://www.rrr.se

Products from RRR Scandinavia:
* RRR|License - Not enough Remedy licenses? Save money by optimizing.
* RRR|Log - Performance issues or elusive bugs? Analyze your Remedy
logs.
* RRR|Translator - Manage and automate your language translations.
Find these products, and many free tools and utilities, at
http://rrr.se.

 While I think I know the answer to this I would like to be sure. When 
 migrating data using Migrator is on the data from the T-tables
migrated.
 I cannot find anything in the documentation that states whether data 
 from B or H tables is or even can be migrated. I am thinking not.
Thanks
 in advance for your help.



 Regards,



 Roger A. Nall
 Manager, OSSNMS Remedy
 T-Mobile, USA
 Desk: 813-348-2556
 Cell: 973-652-6723
 FAX: 813-348-2565
 sf49fanv AIM IM
 RogerNall Yahoo IM






___
 UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum 
 Sponsor: www.rmsportal.com ARSlist: Where the Answers Are

 --
 This message was scanned by ESVA and is believed to be clean.




___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum
Sponsor:
www.rmsportal.com ARSlist: Where the Answers Are



___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum
Sponsor:
www.rmsportal.com ARSlist: Where the Answers Are


___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are

Re: Data Migration

2008-04-22 Thread Ben Chernys 
C'mon guys.  

It uses the API.  Simple as that.  Else, how would a Merge filter fire?
Note that the API allows you to turn off Merge filters on any run but the
Import tool does not offer this option. - Meta-Update does,

Confirm with a simple test running API and SQL logging (to the same file!)
on the arimport target server.  Then read the plethora of logging output for
your run.  Perhaps Misi's log reading program would help.

The internal (read: database) structure of the data is (mostly) not relevant
when using the API.

Cheers
Ben

Ben Chernys
Software Tool House Inc.

Canada / Deutschland / Germany
Mobile:  +49 162 175 0956   GMT + 1 + [ DST ]
Email:   mailto:[EMAIL PROTECTED]
Web: http://www.softwaretoolhouse.com

A free notepad for Diary fields:
http://www.softwaretoolhouse.com/downloads/DiaryFieldEditor.htm
Meta=Update, an ARS API scripting tool used for migrations, integrations,
imports, reports, extracts, batch jobs:
http://www.softwaretoolhouse.com/products/SthMupd
  


-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Nall, Roger
Sent: April 22, 2008 7:33 PM
To: arslist@ARSLIST.ORG
Subject: Re: Data Migration

LJ and Misi,

You both make valid points. Like I said I could not find anything in the
documentation that would confirm or deny my understanding. Now that I have
sound examples I can move on.

Thanks again form the help.

Roger A. Nall
Manager, OSSNMS Remedy
T-Mobile, USA
Desk: 813-348-2556
Cell: 973-652-6723
FAX: 813-348-2565
sf49fanv AIM IM
RogerNall Yahoo IM
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of LJ Longwing
Sent: Tuesday, April 22, 2008 12:59 PM
To: arslist@ARSLIST.ORG
Subject: Re: Data Migration

You could setup a simple form with an attachment on it, create a record and
add the attachment, then migrate that record to the other server and see if
it made it over there with the status historyI seriously doubt it won't,
I mean...the migration tool sucks in several aspects, but it usually 'works
as advertised' for the most part...and only migrating information from T
would not be working as advertised 

-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Nall, Roger
Sent: Tuesday, April 22, 2008 10:35 AM
To: arslist@ARSLIST.ORG
Subject: Re: Data Migration

Misi,

Thanks for getting back to me. While I am sure you are correct I am
wondering if anyone can confirm that indeed all data from the T, H, and B
tables is moved when using Migrator. This is a very important question for
me right now and I must be as sure as I can of the answer.

Thanks,

Roger A. Nall
Manager, OSSNMS Remedy
T-Mobile, USA
Desk: 813-348-2556
Cell: 973-652-6723
FAX: 813-348-2565
sf49fanv AIM IM
RogerNall Yahoo IM 

-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Misi Mladoniczky
Sent: Tuesday, April 22, 2008 10:08 AM
To: arslist@ARSLIST.ORG
Subject: Re: Data Migration

Hi,

Everything should be migrated.

The data is copied using the API, so the actual T/B/H tables are not
accessed directly by Migrator. Or so I would think...

You can also use our RRR|Chive to move the data. In this case, I definitely
know that all the data for each form is copied.

You can move all your data in a single pass of RRR|Chive.

RRR|Chive can also do incremental copying of your data. Anything
modified/deleted on the target server will be restored. Anything changed on
the source server will copied over. Just use the SYNCTOTARGET-mode which is
default if you use the online configurator.

https://www.rrr.se/cgi/rrrchive/main

Best Regards - Misi, RRR AB, http://www.rrr.se

Products from RRR Scandinavia:
* RRR|License - Not enough Remedy licenses? Save money by optimizing.
* RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs.
* RRR|Translator - Manage and automate your language translations.
Find these products, and many free tools and utilities, at http://rrr.se.

 While I think I know the answer to this I would like to be sure. When 
 migrating data using Migrator is on the data from the T-tables
migrated.
 I cannot find anything in the documentation that states whether data 
 from B or H tables is or even can be migrated. I am thinking not.
Thanks
 in advance for your help.



 Regards,



 Roger A. Nall
 Manager, OSSNMS Remedy
 T-Mobile, USA
 Desk: 813-348-2556
 Cell: 973-652-6723
 FAX: 813-348-2565
 sf49fanv AIM IM
 RogerNall Yahoo IM






___
 UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum
 Sponsor: www.rmsportal.com ARSlist: Where the Answers Are

 --
 This message was scanned by ESVA and is believed to be clean.




___
UNSUBSCRIBE

Re: Data Migration Using Migrator

2008-04-21 Thread Grooms, Frederick W 
You are correct in that the results only show you the number of records
(and form names) migrated, not the criteria used to select the records.
 
 
There are 2 ways to specify the data (Note: This is using Migrator
Version 7.0.00  - Patch 003 against Remedy 6.3.00 Patch 20 servers)
 
If I Right click on a form (on the source server) and choose Form Data
Only It will bring up a window where you pick your target server and
then pick the target form.  The next window that opens will give you a
place to select All Records or Search Selection.  With Search Selection
you put in your Advanced Query.
 
If you double click on the Source form and choose data you can put in
your advanced query there.  You then select the records to migrate and
right click on one of them to do the migration.
 
Personally I prefer to do the 1st option (right click on the form and
choose Form Data Only)
 
Fred
 




From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Nall, Roger
Sent: Monday, April 21, 2008 2:52 PM
To: arslist@ARSLIST.ORG
Subject: Data Migration Using Migrator



When migrating data from one system to another I am looking to see if
there is any report that will show the criteria used to get the list of
data. I do not see anything in the results file for data migrations only
object migrations. Can someone point me in the right direction?

 

Thanks,

 

Roger A. Nall 
Manager, OSSNMS Remedy 
T-Mobile, USA 
Desk: 813-348-2556 
Cell: 973-652-6723 
FAX: 813-348-2565 
sf49fanv AIM IM 
RogerNall Yahoo IM 

 


___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are

Re: Data Migration Using Migrator

2008-04-21 Thread Nall, Roger 
Fred,

 

I do it the same way. That is a bummer about not saving the criteria. We
just attempted an upgrade over the weekend. Data was migrated from the
old production to the new production but some of the data did not
migrate and we do not know why nor do we have a list of which records.
That was why we were hoping the criteria was saved.

 

Thanks, 

 

Roger A. Nall 
Manager, OSSNMS Remedy 
T-Mobile, USA 
Desk: 813-348-2556 
Cell: 973-652-6723 
FAX: 813-348-2565 
sf49fanv AIM IM 
RogerNall Yahoo IM 



From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Grooms, Frederick W
Sent: Monday, April 21, 2008 4:24 PM
To: arslist@ARSLIST.ORG
Subject: Re: Data Migration Using Migrator

 

You are correct in that the results only show you the number of records
(and form names) migrated, not the criteria used to select the records.

 

 

There are 2 ways to specify the data (Note: This is using Migrator
Version 7.0.00  - Patch 003 against Remedy 6.3.00 Patch 20 servers)

 

If I Right click on a form (on the source server) and choose Form Data
Only It will bring up a window where you pick your target server and
then pick the target form.  The next window that opens will give you a
place to select All Records or Search Selection.  With Search Selection
you put in your Advanced Query.

 

If you double click on the Source form and choose data you can put in
your advanced query there.  You then select the records to migrate and
right click on one of them to do the migration.

 

Personally I prefer to do the 1st option (right click on the form and
choose Form Data Only)

 

Fred

 

 



From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Nall, Roger
Sent: Monday, April 21, 2008 2:52 PM
To: arslist@ARSLIST.ORG
Subject: Data Migration Using Migrator

When migrating data from one system to another I am looking to see if
there is any report that will show the criteria used to get the list of
data. I do not see anything in the results file for data migrations only
object migrations. Can someone point me in the right direction?

 

Thanks,

 

Roger A. Nall 
Manager, OSSNMS Remedy 
T-Mobile, USA 
Desk: 813-348-2556 
Cell: 973-652-6723 
FAX: 813-348-2565 
sf49fanv AIM IM 
RogerNall Yahoo IM 

 

__Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are
html___

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are