Share:|

Introduction

My Journey with Migrator tool was an interesting one.  Trying to learn about the Migrator tool thru documentation was somewhat limited.  Once I starting using the tool.  I've started run into problems that are found or not found in BMC sites. The goal of this blog is to save the newbie sometime on getting jump start on actually using the tool right off the bat without troubleshoot the tool itself.

 

I will divide things into section so that you don't have to read the whole blog to get started with migrator. I would recommend that you read the tuning section so that you don't run into issue or error with the tool.

 

Understanding Migrator

There are two tools within BMC Migrator.  There is the migrator itself and delta data migration tool.  These tool use Jet engine to create copy of the database being migrated and migrated from in the %temp% in most case.  I found that my log files are stored in the different location.  The location  found was %userfolder%/appdata/roaming/ar system for the migrator tool on windows system.  The log files for Delta Data Migration was stored in the working folder of Delta Data Migration tool.  These thing can be changed via registry on windows system.

 

-- This is where you edit most of the Migration tool settings

HKEY_CURRENT_USER\Software\Remedy

     

 

The software seems to have few issue that are well documented but, I see the information scatter around knowledgeable and communities.  I recommend reading the tuning section before starting your migration.

 

Enable Logging

If you run into issue with migrator, in most case you'll need detail logging.  In order to achive logging with the migrator tool start with the understanding of where the log is kept.  The log file kept:  C:\Users\%username%\AppData\Roaming\AR System\Remedy Migrator\backup\%servername%

 

Migrator is got it's beginning form AR platform thus you can use API log settings that work on the AR server.  In order for you to enable API logging you have to enable environment variable ARAPILOGGING=%loglevel%.  Log level value are 1 thru 88 far has I know.  The LOGLEVEL 88 isn't documented on BMC documents from what I could tell.

 

There are different way to enable logging with Migrator tool.  Enable server style logging.  By changing the value registry, you'll enable different type of logging.  I haven't found documentation on it.  You'll have to play with it.

[HKEY_CURRENT_USER\Software\Remedy\Remedy Migrator]

"LogLevel"=dword:00000006

"LogLayout"=dword:00000002

    

 

Understanding API Logging variable

 

Here is the documented log levels:  https://docs.bmc.com/docs/display/public/ars81/C+API+Client-side+ARAPILOGGING

 

ARAPILOGGING = 88 (shows you time stamp of the transaction)

 

 

Migrator Tuning

Here are knowledge article and communities discussion on Migrator tool.

 

I am firm believer in have two partition on servers.  One for the OS operation and second for the application.  Need to modify Configuration.xml setting delta work-dir to the correct install folder.  With migration there are lots of read and write to disk.  For example, when it cache the source server object.  It has read that information from the network and write it to disk.

 

Windows Registry Editor Version 5.00

 

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\inetinfo]

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\inetinfo\Parameters]

"ObjectCacheTTL"=dword:00000030

"MemCacheSize"=dword:00002048

"MaxCacheFileSize"=dword:00000256

"PoolThreadLimit"=dword:00000010

"ListenBackLog"=dword:00000250

"SynAttackProtect"=dword:00000000

"TcpTimedWaitDelay"=dword:0000001e

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server]

"DeleteTempDirsOnExit"=dword:00000000

"PerSessionTempDir"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Jet\4.0\Engines\Jet 4.0]

"MaxLocksPerFile"=dword:ffffffff

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Jet\4.0\Engines\Jet 3.x]

"MaxLocksPerFile"=dword:ffffffff

          

 

Thread Error 2004

 

1.  Enable logging

2.  Provided the logs to support and get the issue escalated

 

With my experience with this error, we found that there was "overlay schema migrator was not handling multiple field references correctly for while parsing object property"  and I had to apply a hotfix.  In addition, I had to install the latest version of Migrator.

 

How to migrate ITSM with Migrator During a Version Upgrade (This also address non-Unicode to Unicode migration)

 

1. build the AR Server

2. Use migrator to move data only on "AR System Licenses" form

3. Install CMDB

4. Atrium Integrator Server

5, Install ITSM

6. Install SRM

7. Process Designer

8. Install SLM

9. Apply available patches

10. Upgrade the mid-teir (optional or only required during version upgrade)

11. Extended CDM for custom attributes

12. Disable DSO

13. Disable Escalations

15. Disable Database Triggers (Ask the DBA to perform for ARSystem database)

16. Fix known DDM issue on production/source database with DDM fixes

17. Tune database for migration

18.  Turn off the following Recon Jobs:

        BMC Asset Management - Sandbox

        BMC Asset Management - Sandbox Bulk

        BMC Asset Management CI Data Load

19.    Disable Normalization Job if any at the destination server

20. Do a difference report on forms that was change %date%

21. Need to note the date that DDM was run:  9/29/15  (Need to run DDM more than 3 times)

22. Run migratorFindCustomForms.bat

23. Run Post Scripts for DDM