We have a test environment that we would like to refresh with production. I've tried doing a MySql DB export and re-import, but not so good. To many OS dependencies in the DB contents.
I'm thinking there is a minimal set of tables that can be exported/imported to accomplish what I'm looking for, but wanted to know if anyone else has already worked through this one.
We're running 3.0.5 with ITSM. We need the setup/config items of customers/groups/agents/etc. as well as the ticket data/history and ITMS host information.
Has anyone else already worked through this process, or (hopefully) does a utility already exist?
Refresh of Test Env Data
Moderator: crythias
-
- Znuny ninja
- Posts: 1029
- Joined: 13 Apr 2009, 12:26
- Znuny Version: 6.0.13
- Real Name: Wolfgang Fürtbauer
- Company: PBS Logitek GmbH
- Location: Pinsdorf
Re: Refresh of Test Env Data
hm - that's exactly what I'm doing for my test environment, admitting that I have similar production and test environmentWe have a test environment that we would like to refresh with production. I've tried doing a MySql DB export and re-import, but not so good. To many OS dependencies in the DB contents.
only thing to change in my case: email-account for retrieving mails inteded to go to OTRS
Produktiv:
OTRS 6.0.13/ ITSM 6.0.13
OS: SUSE Linux (SLES 12, Leap), MySql 5.5.x, 5.6.x
Windows 2012 AD Integration (agents and customers), Nagios integration (incidents, CMDB), Survey, TimeAccounting
OTRS 6.0.13/ ITSM 6.0.13
OS: SUSE Linux (SLES 12, Leap), MySql 5.5.x, 5.6.x
Windows 2012 AD Integration (agents and customers), Nagios integration (incidents, CMDB), Survey, TimeAccounting
-
- Znuny newbie
- Posts: 2
- Joined: 02 Jun 2011, 03:27
- Znuny Version: 3.0.5
- Real Name: Rick Siner
- Company: Open Systems Technologies
Re: Refresh of Test Env Data
Thanks Wolfgangf,
I think the issue we're having is due to some differences in application modules and/or their location(s). The test OS environment was built quite a bit earlier than the prod, and it looks like the locations for some of the modules have a different path (wasn't involved in the OS setup) and/or different ones between the two environments.
If you're successfully doing a dump/load of the DB environment for a refresh, then I'm assuming you're also refreshing all application modules from prod to test too then?
If that's the case, and the way it needs to work, then looks like I may have to do some layout corrections as well as think through how applications module differences will affect.....
Thanks....
I think the issue we're having is due to some differences in application modules and/or their location(s). The test OS environment was built quite a bit earlier than the prod, and it looks like the locations for some of the modules have a different path (wasn't involved in the OS setup) and/or different ones between the two environments.
If you're successfully doing a dump/load of the DB environment for a refresh, then I'm assuming you're also refreshing all application modules from prod to test too then?
If that's the case, and the way it needs to work, then looks like I may have to do some layout corrections as well as think through how applications module differences will affect.....
Thanks....
-
- Znuny ninja
- Posts: 1029
- Joined: 13 Apr 2009, 12:26
- Znuny Version: 6.0.13
- Real Name: Wolfgang Fürtbauer
- Company: PBS Logitek GmbH
- Location: Pinsdorf
Re: Refresh of Test Env Data
Hi,
I'm doing it differently:
before I bring a new version into production, everything is installed and tested on the test system
if test are OK, same on production system
so both of them have to be more or less identical
BR
I'm doing it differently:
before I bring a new version into production, everything is installed and tested on the test system
if test are OK, same on production system
so both of them have to be more or less identical
BR
Produktiv:
OTRS 6.0.13/ ITSM 6.0.13
OS: SUSE Linux (SLES 12, Leap), MySql 5.5.x, 5.6.x
Windows 2012 AD Integration (agents and customers), Nagios integration (incidents, CMDB), Survey, TimeAccounting
OTRS 6.0.13/ ITSM 6.0.13
OS: SUSE Linux (SLES 12, Leap), MySql 5.5.x, 5.6.x
Windows 2012 AD Integration (agents and customers), Nagios integration (incidents, CMDB), Survey, TimeAccounting