Deploy OTRS configuration from test environment to production environment
Hi everyone! I'm using OTRS 4.0.11. Because of some company policies, I need to set up to environments, one for testing and another for production (operational). The problem is: How to export the required configuration data from test env. and deploy it into production env? I know I could copy and paste the ZZZAuto.pm file, but is that enough? Is there any database configuration data I should also take care? If so, how? I know I could use the provided backup.pl script, but I don't want to backup/restore all the data, only the configuration data. Is there any way to do so? Thanks in advance, Samuel
Hello, The way we have done that before is: on app: tar --exclude=var/article --exclude=var/tmp -cvpzf ../otrs_app.tar.gz * on db: mysqldump -u root -p otrs > otrs_db.sql And then restore both on your new environment, previous installation of the product so all software requirements are already met. On 12 August 2015 at 14:53, Samuel Diniz Casimiro < samuel.casimiro@camara.leg.br> wrote:
Hi everyone!
I’m using OTRS 4.0.11.
Because of some company policies, I need to set up to environments, one for testing and another for production (operational).
The problem is: How to export the required configuration data from test env. and deploy it into production env?
I know I could copy and paste the ZZZAuto.pm file, but is that enough? Is there any database configuration data I should also take care? If so, how?
I know I could use the provided backup.pl script, but I don’t want to backup/restore all the data, only the configuration data. Is there any way to do so?
Thanks in advance,
Samuel
--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
Have you checked out the /opt/otrs/scripts/backup.pl and /opt/otrs/scripts/ restore.pl scripts? These are both described at https://otrs.github.io/doc/manual/admin/stable/en/html/backup-and-restore.ht... . When performing restore from the generated backup files, I usually find that it's necessary to drop/create the mysql otrs database. Otherwise, the restore will complain that the database already exists. On the production environment, generate a backup: sudo /opt/otrs/scripts/backup.pl -d /path/to/backup/folder On the test environment: 1. Copy the backup from the production system. 2. Drop/create the otrs database. WARNING: make sure you're on the dev environment. mysql -e "drop database otrs;" mysql -e "create database otrs;" 3. Restore the backup. /opt/otrs/scripts/restore.pl -b /path/to/backup/folder/YYY-MM-DD_hh-mm/ -d /opt/otrs/ 4. Verify the DB. su - otrs -c '$HOME/bin/otrs.CheckDB.pl' 5. Re-configure the otrs cron jobs. /opt/otrs/bin/Cron.sh restart otrs 6. To disable otrs user cron jobs, for testing or to avoid colliding with an existing production instance, disable the otrs crontab with '/opt/otrs/bin/Cron.sh stop otrs'. 7. Start the Scheduler. su - otrs -c '$HOME/bin/otrs.Scheduler.pl -a start' Hope this helps. Jay On Wed, Aug 12, 2015 at 1:00 PM, Leonardo Certuche < leonardo.certuche@itconsultores.com.co> wrote:
Hello,
The way we have done that before is:
on app: tar --exclude=var/article --exclude=var/tmp -cvpzf ../otrs_app.tar.gz *
on db: mysqldump -u root -p otrs > otrs_db.sql
And then restore both on your new environment, previous installation of the product so all software requirements are already met.
On 12 August 2015 at 14:53, Samuel Diniz Casimiro < samuel.casimiro@camara.leg.br> wrote:
Hi everyone!
I’m using OTRS 4.0.11.
Because of some company policies, I need to set up to environments, one for testing and another for production (operational).
The problem is: How to export the required configuration data from test env. and deploy it into production env?
I know I could copy and paste the ZZZAuto.pm file, but is that enough? Is there any database configuration data I should also take care? If so, how?
I know I could use the provided backup.pl script, but I don’t want to backup/restore all the data, only the configuration data. Is there any way to do so?
Thanks in advance,
Samuel
--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
oops.. i missed the last part of your question. sorry.
can u just export/import the configuration directly from the UI?
Jay
On Wed, Aug 12, 2015 at 1:23 PM, Jay
Have you checked out the /opt/otrs/scripts/backup.pl and /opt/otrs/scripts/restore.pl scripts? These are both described at https://otrs.github.io/doc/manual/admin/stable/en/html/backup-and-restore.ht... .
When performing restore from the generated backup files, I usually find that it's necessary to drop/create the mysql otrs database. Otherwise, the restore will complain that the database already exists.
On the production environment, generate a backup: sudo /opt/otrs/scripts/backup.pl -d /path/to/backup/folder
On the test environment: 1. Copy the backup from the production system. 2. Drop/create the otrs database. WARNING: make sure you're on the dev environment. mysql -e "drop database otrs;" mysql -e "create database otrs;" 3. Restore the backup. /opt/otrs/scripts/restore.pl -b /path/to/backup/folder/YYY-MM-DD_hh-mm/ -d /opt/otrs/ 4. Verify the DB. su - otrs -c '$HOME/bin/otrs.CheckDB.pl' 5. Re-configure the otrs cron jobs. /opt/otrs/bin/Cron.sh restart otrs 6. To disable otrs user cron jobs, for testing or to avoid colliding with an existing production instance, disable the otrs crontab with '/opt/otrs/bin/Cron.sh stop otrs'. 7. Start the Scheduler. su - otrs -c '$HOME/bin/otrs.Scheduler.pl -a start'
Hope this helps.
Jay
On Wed, Aug 12, 2015 at 1:00 PM, Leonardo Certuche < leonardo.certuche@itconsultores.com.co> wrote:
Hello,
The way we have done that before is:
on app: tar --exclude=var/article --exclude=var/tmp -cvpzf ../otrs_app.tar.gz *
on db: mysqldump -u root -p otrs > otrs_db.sql
And then restore both on your new environment, previous installation of the product so all software requirements are already met.
On 12 August 2015 at 14:53, Samuel Diniz Casimiro < samuel.casimiro@camara.leg.br> wrote:
Hi everyone!
I’m using OTRS 4.0.11.
Because of some company policies, I need to set up to environments, one for testing and another for production (operational).
The problem is: How to export the required configuration data from test env. and deploy it into production env?
I know I could copy and paste the ZZZAuto.pm file, but is that enough? Is there any database configuration data I should also take care? If so, how?
I know I could use the provided backup.pl script, but I don’t want to backup/restore all the data, only the configuration data. Is there any way to do so?
Thanks in advance,
Samuel
--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
participants (3)
-
Jay -
Leonardo Certuche -
Samuel Diniz Casimiro