Backing up the TrackStudio database...

Discuss problems installing or using TrackStudio.

Backing up the TrackStudio database...

Postby larsf » Thu Oct 09, 2003 7:22 pm

I feel like an idiot asking this question...

but - how do I actually back up the TrackStudio database? Do I copy the entire trackstudio directory tree, or just a few database files?

Can I safely make a backup with the server up and running or do I have to take down the service before I make the backup?

Running demo version using hyperSonic SQL.
larsf
 
Posts: 200
Joined: Thu Aug 28, 2003 6:32 pm

Re: Backing up the TrackStudio database...

Postby admin » Thu Oct 09, 2003 8:14 pm

larsf wrote:I feel like an idiot asking this question...

but - how do I actually back up the TrackStudio database? Do I copy the entire trackstudio directory tree, or just a few database files?

Can I safely make a backup with the server up and running or do I have to take down the service before I make the backup?

Running demo version using hyperSonic SQL.


This is more smart question you can expect :-)

We does not implement nothing like "automatic backup" because it should be done very carefully and generally we can't guarantee results. For example, we should use right isolation level and backup all database within one transaction. For some DBMS this is OK, for other this can lock all tables and make application unavailable for users.

Generally, you should use backup utility that offer your database vendor. Some of them (such as ORACLE) can implement "hot backup" (backup without database shutdown and interrupring user activity), some other can require database shutdown before backup.

ORACLE, DB2, MS SQL, PostgreSQL offer database backup utility. For Firebird and HSQL you should stop application and database server and copy files manually.

PS. HSQL performs very bad on large database. For example, database with 5000 tasks need about 30 minutes to start and large amount of memory. In 2.8 we offer database<->XML transfer, I suggest use it to transfer data to Firebird or PostgreSQL after we release 2.8
Maxim Kramarenko (mailto: maximkr@trackstudio.com)
TrackStudio - Hierarchical Bug & Issue Tracking Software
http://www.trackstudio.com
admin
Site Admin
 
Posts: 7452
Joined: Thu Jan 01, 1970 3:00 am
Location: Smolensk, Russia

Re: Backing up the TrackStudio database...

Postby larsf » Fri Oct 10, 2003 10:39 am

admin wrote:This is more smart question you can expect :-)


Thanks, mate :oops:

admin wrote:ORACLE, DB2, MS SQL, PostgreSQL offer database backup utility. For Firebird and HSQL you should stop application and database server and copy files manually.

PS. HSQL performs very bad on large database. For example, database with 5000 tasks need about 30 minutes to start and large amount of memory. In 2.8 we offer database<->XML transfer, I suggest use it to transfer data to Firebird or PostgreSQL after we release 2.8


OK, I see that starting out with HSQL was a mistake. How do I actually identiy the HSQL database files for backup?

I don't want to go to Oracle, DB2 or MSSQL, so I will look at the two you mentioned.

I am surprised that you don't support mySQL as well? We are using that quite a bit...
larsf
 
Posts: 200
Joined: Thu Aug 28, 2003 6:32 pm

Re: Backing up the TrackStudio database...

Postby admin » Fri Oct 10, 2003 10:52 am

larsf wrote:OK, I see that starting out with HSQL was a mistake. How do I actually identiy the HSQL database files for backup?


You should stop HSQL and backup test.properties, test.log and test.script. You can notice that HSQL does not store database in binary form - only last-seesion-changes (.log) and full SQL script (.script).

larsf wrote:I don't want to go to Oracle, DB2 or MSSQL, so I will look at the two you mentioned.


If you use Windows I suggest you Firebird - its opensource implementation of InterBase, quite quality product. PostgreSQL has no native Windows support, only via cygwin.

larsf wrote:I am surprised that you don't support mySQL as well? We are using that quite a bit...


This is painful question, search this forum.
In 2.5 we was implement such support, but drop it in 2.7. TrackStudio
need referential integrity support, but MySQL even with InnoDB has
very buggy/non-standard implementation. I think that we return to this
question when MySQL will be more stable and more compatible with other
databases.
Maxim Kramarenko (mailto: maximkr@trackstudio.com)
TrackStudio - Hierarchical Bug & Issue Tracking Software
http://www.trackstudio.com
admin
Site Admin
 
Posts: 7452
Joined: Thu Jan 01, 1970 3:00 am
Location: Smolensk, Russia


Return to TrackStudio Support

Who is online

Users browsing this forum: No registered users and 1 guest