If you're making changes ( in my case very small ones ) to dtl files and in other ways actively hacking on OTRS, you would be well served to just check your entire otrs tree into a cvs repository or similar. I've been as a rule trying to hack *around* otrs using php, but I have made small additions to .dtl files and it's very useful to have source control on this sort of thing. It makes upgrades much less of a hassle... JeffG Marshall28 wrote:
ignore my last response. I got it figured out. thanks
IT Department @ Admin -Jesse
-----Original Message----- From: otrs-bounces@otrs.org [mailto:otrs-bounces@otrs.org]On Behalf Of Tyler Hepworth Sent: Thursday, June 10, 2004 12:02 PM To: User questions and discussions about OTRS. Subject: RE: [otrs] Properly Backing up OTRS
Marshall28 wrote:
If I'm going to backup all of otrs so that I can restore in case of hard drive failure, should I just copy the /opt/otrs directory as well as do a "mysqldump --all-databases" to save the entire otrs database? I'm also curious where all the tickets are stored? Are these tickets all in the mysql database?
Take a look /opt/otrs/scripts/backup.sh. It will backup the DB and all of the critical system files needed. If you make changes to .dtl files or things in other locations, then you would want to dump additional directories, but the backup.sh should be enough to get you started.
Hth,
Tyler Hepworth
_______________________________________________ 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 Support oder Consulting für Ihr OTRS System? => http://www.otrs.de/
_______________________________________________ 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 Support oder Consulting für Ihr OTRS System? => http://www.otrs.de/