Little more info…
I have migrated\updated rt3 database to a fresh install of rt4.2.8. So I
can bounce back and forth between rt3 database and rt4 database with
$DatabaseName in RT_SiteConfig.pm.
rt4 database has “RT::Extension::Assets” plugin working however the
tables (rtxassets, rtxassets_id_seq, rtxcatalogs, rtxcatalogs_id_seq)
aren’t populated due to this being a fresh database.
old rt3 build\database on the other hand had "RTx::AssetTracker"
installed so it has the following tables\sequences that rt4 does not
(at_assets, at_assets_id_seq, at_ips, at_ips_id_seq, at_ports,
at_ports_id_seq, at_types, at_types_id_seq)
Installing AT3.0 has given me some issues with both rt3 and rt4
database. It appears it’s no longer supportd after rt4.0.0. We were
hoping you guys could shed some light on this for us. How can we migrate
our old Asset Tracker data into rt4 database or maybe get rt3 database
fully functional on 4.2.8.
ITS System Administrator
Bard College at Simon’s Rock
84 Alford Road
Great Barrington, MA 01230
(413) 528-7428 (voice)
(413) 528-7405 (fax)
firstname.lastname@example.orgOn 10/13/2014 4:29 PM, charlie derr wrote:
We’ve been using RT for several years and have a lot of data inside our old instance
(which is running RT 3.8.4 with the Asset Tracker module). My colleague Will has
done some good work with spinning up a new version (and with the help of the list
getting it integrated with our LDAP) which is running 4.2.8. Both the new and the
old are running off of postgres underneath.
Does anyone have any advice about how we can most efficiently migrate over our custom
asset types and asset information into the new version?
thanks so much in advance,