Backing up Jazz server

That set of files would cover most things, but two things it would not
cover are (1) the fulltext lucene index and (2) license keys you have
installed through the web UI. Rather than pick and choose from the
server directory, I would just back up the entire server directory.

Backing up JazzInstallDir/repotools should not be needed, but rarely
changes so it wouldn't hurt if it was.

If your site is internet accessible, and presumably always online, then
how do you plan on taking backups of the live filesystem? Perhaps the
simple approach of just copying the files would work, but I'm concerned
about files that Derby would be holding open or modifying in the
server/repositoryDB directory.

ignace wrote:

Hello

I got a question about backing up all data of a jazz server.
I would like to setup backing up service because my jazz server will
be accessible from the internet. So you never know.

I read on the information center when u wanna migrate from tomcat to
websphere to backup:
* The fileJazzInstallDir/server/teamserver.properties.
* The files JazzInstallDir/server/log4j.properties.
* The file JazzInstallDir/server/tomcat/webapps/jazz.war.
* The default repository database in the
directoryJazzInstallDirserver/repositoryDB.
* The repository tools in the directory JazzInstallDir/repotools.

Would this backup all my server?
user account, projects, repository, properties en so on.

thanks anyway
Ignace

The server definitely needs to be stopped when backing up the derby db. We strongly recommend regular backups of the database as it is a free open source db. Additional suggestions are covered in the following technote, in the section "Backing up your Database and other Essential Data":
https://jazz.net/learn/LearnItem.jsp?href=content/tech-notes/jazz-team-server-0_6-deployment-guide/index.html

If you desire to perform "online" backups with a live server running, you should consider using a supported commercial database like DB2 or Oracle. Our jazz.net administrator has started a draft technote that discusses online backups, attached to the following work item:
technote - Configuring IBM DB2 V9.5 for Online backups for RTC Server (58695)

Lastly, note that backing up the full lucene index, aka the "workitemindex" folder, is optional, as it can be recreated using the repotools command after the database is restored.

Ritchie Schacher
Jazz Repository Team

"Matt Lavin" <matt_lavin> wrote in message news:g6th6v$j6s$1@localhost.localdomain...

That set of files would cover most things, but two things it would not
cover are (1) the fulltext lucene index and (2) license keys you have
installed through the web UI. Rather than pick and choose from the
server directory, I would just back up the entire server directory.

Backing up JazzInstallDir/repotools should not be needed, but rarely
changes so it wouldn't hurt if it was.

If your site is internet accessible, and presumably always online, then
how do you plan on taking backups of the live filesystem? Perhaps the
simple approach of just copying the files would work, but I'm concerned
about files that Derby would be holding open or modifying in the
server/repositoryDB directory.

ignace wrote:
Hello

I got a question about backing up all data of a jazz server.
I would like to setup backing up service because my jazz server will
be accessible from the internet. So you never know.

I read on the information center when u wanna migrate from tomcat to
websphere to backup:
* The fileJazzInstallDir/server/teamserver.properties.
* The files JazzInstallDir/server/log4j.properties.
* The file JazzInstallDir/server/tomcat/webapps/jazz.war.
* The default repository database in the
directoryJazzInstallDirserver/repositoryDB.
* The repository tools in the directory JazzInstallDir/repotools.

Would this backup all my server?
user account, projects, repository, properties en so on.

thanks anyway
Ignace