Database Migration from IVMS Rich to Pro version

Modified on Thu, 25 May, 2017 at 11:22 AM

STEP 1: Configure the database IP in ‘vmsserverconfiguration.xml’ file. Then execute ‘run.cmd’ under ‘V_Smart-DB-Migrator’ package.

Figure 1(a)

Figure 1(b)

Figure 1(c)

Figure 1(d)

NOTE: Change the existing IP (as highlighted in below figure) to 127.0.0.1

Figure 1(e)

STEP 2: Open ‘Mysql-Workbench’/’Mysql -Query-Browser’ and make ‘product_atom_64’ schema as a default schema.

Figure 2(a)

STEP 3: Drop older STORED PROCEDURES.

Figure 3(a)

STEP 4: Import new procedures stepwise, which are placed under ‘V-Smart-DB-Migrator/Procedure’ folder.

[NOTE: Must select ‘product_atom_64’ schema as a default schema]

Now import procedure stepwise:

1. First import ‘markEventClips.sql’, execute it and run the procedure.

2. Execute ‘markScheduleAndMotionClip.sql’ and run the procedure.

3. Execute ‘proc_delete_channel.sql’ and run the procedure.

4. Execute ‘updateChannelParam.sql’ and run the procedure.

5. Execute ‘createVideoClip.sql’ and run the procedure.

Now your database is ready to run IVMS PRO VERSION 1.0.3.0.
But you are not able to play or see previous recordings clips.
To do this first, we have to run new version of IVMS software and secondly we have to register VMS with DB, and media servers with VMS.

After this we will get a MEDIA SERVER ID. This ID helps us to recover our previous database.

[MEDIA SERVER ID will create under ‘vtpl_cnf\vtpl.conf’ folder]

Figure 4(a)

Figure 4(b)

1. Import ‘insertVAclip.sql’ and replace existing MEDIA SERVER ID with original ‘vtpl.ms.serverId’.

2. After changing existing MEDIA SERVER ID, Execute and run the procedure.

[NOTE: Before the execution of procedure make sure that we have been successfully replace the fake MEDIA SERVER ID with original MEDIA SERVER ID]

3. Import ‘transferVClipRecordings.sql’ and again replace existing MEDIA SERVER ID with original ‘vtpl.ms.serverId’.

4. After changing existing MEDIA SERVER ID, Execute and run the procedure.

[NOTE: Before the execution of procedure make sure that we have been successfully replace the fake MEDIA SERVER ID with original MEDIA SERVER ID]

Figure 4(c)