older mantis 1.1.7 going to 2.8.0, platform retired

[SunnyMantis]

Hi, we do need mantis, precisely, the data from the mantis, however, the platform mantis 1.1.7 sitting on is going to retire (windows server 2003) . It should be retired long time ago actually.
I want to know what would be the proper way to retire the data as platform we cannot control any longer.

[rkarmann]

Hi,

I would say... try a DUMP ? Or upgrade if possible

[SunnyMantis]

we consider 'upgrade', but run into some troubles as 1.1.7 very old, some platform not supported. we are seeking for a successful case from a mantis lower than 1.1.8 , upgraded to current version, perhaps, which is ideal for us.

[rkarmann]

Yes, in fact you might get issues with Mantis database schema. If you can try it on a localhost, then run on a test server, guess you will be able to migrate...

[SunnyMantis]

agree with you!

our mantis 1.1.7 for production use actually, I cannot touch, but the database dump sql can be imported into 2.8.0 structure, or cannot ?
As you said, some schema changed on database level, I don't think that would be a simple task just import sql (whole 1.1.7 data) into current running 2.8.0 database.

The questions I always have and no solution so far yet -
just based on a dump sql file from 1.1.7, can we achieve the goal to have a higher version of mantis running on data from 1.1.7 dump ?
if we use import on DB level, table by table ?
should we adjust anything or run some tasks to make sure we are fitting into a higher level schema ?

after all, we are changing the interface to 2.8.0; while data 'migrated' from 1.1.7;
testing site 2.8.0 running as expected, and we can have full access.

[atrol]

but the database dump sql can be imported into 2.8.0 structure, or cannot ?
As you said, some schema changed on database level, I don't think that would be a simple task just import sql (whole 1.1.7 data) into current running 2.8.0 database.

Didn't I tell you how to do that? viewtopic.php?f=3&t=25226&p=64240#p64166

[SunnyMantis]

what we have had is a sql file from 1.1.7 and a site running 2.8.0 , what we need :
step by step based on what we have to see whether we can see data from 1.1.7 in 2.8.0.

[rkarmann]

In case you just need to retrieve bug datas from your old Mantis, is it possible to export/import bug in XML in your 1.1 version ? See this thread

Not sure this will work for you but let's try

[SunnyMantis]

yes!
but
XML feature not in v1.1.7 unfortunately, we only see PRINT REPORTS, CSV EXPORT when viewing issues.
XML feature okay in 2.8.0 we can see like
Viewing Issues (0 - 0 / 0) [ Print Reports ] [ CSV Export ] [ Excel Export ] [ XML Export ]

the situation here :
sql file will be available, but not every one knows how to access, so we need an interface (v2.8.0) or any version can be loaded onto current platform our IT supported;
sql file will be used for a data migration into jira, but that's in another plan.

[rkarmann]

Ok I see. Well I have upgraded 1.2.14 > 2.9 a few weeks earlier, and faced just one difficulty, wich has been solved by fetching this forum ( schema[185] or something like that).

-> Create a Virtual Machine and install PHP 5.5 or > (with MySQL 5.5)
-> Dump your Mantis Database and import the SQL file in your new VM's database
-> (Make several copies so you won't have to import each time it might fail)
-> When your DB is ready, copy latest MantisBugTracker realease on your new server
-> Follow installation process
-> Make sure to type the right DB name (your old mantis's db name, if not renamed)
-> Mantis will process to the installation (you might encounter many errors but nothing that you can't find on the web )

[SunnyMantis]

I will see how it goes on my end to follow your steps. Thank you very much!

[SunnyMantis]

forum link schema[185] where should I go , please ?

[rkarmann]

See this post from atrol.

[SunnyMantis]

Hi,
Good news: data from 1.1.7 imported into 2.8.0 without problem. site can be launched, but
Bad news: although we have 2.8.0 site, login error still.

[rkarmann]

What kind of login error?