RRC v3.0.1 back up procedure: Just confirming.
Delete this post Edit/Delete this post
PostPosted: Wed, 22 Feb 2012 @ 619: Subject: RRC v 3.0.1. Back UP: with Derby & Tomcat
As per infocenter --
http://publib.boulder.ibm.com/infocenter/clmhelp/v3r0m1/index.jsp?topic=%2Fcom.ibm.rational.rrm.help.doc%2Ftopics%2Ft_create_snapshots.html
Topic: Backing up and restoring the Derby database under section::
Administering > Administering the Jazz Team Server
we need to backup only
<JazzInstallDir>\server\conf\jts\derby\repositoryDB.
Wanted to be sure, if any thing else (like some properties files or any other settings files) also need to be backed up.
Thanks for your help.
Shiv
PostPosted: Wed, 22 Feb 2012 @ 619: Subject: RRC v 3.0.1. Back UP: with Derby & Tomcat
As per infocenter --
http://publib.boulder.ibm.com/infocenter/clmhelp/v3r0m1/index.jsp?topic=%2Fcom.ibm.rational.rrm.help.doc%2Ftopics%2Ft_create_snapshots.html
Topic: Backing up and restoring the Derby database under section::
Administering > Administering the Jazz Team Server
we need to backup only
<JazzInstallDir>\server\conf\jts\derby\repositoryDB.
Wanted to be sure, if any thing else (like some properties files or any other settings files) also need to be backed up.
Thanks for your help.
Shiv
2 answers
In the event you do need to restore from a backup, you will benefit from backing up the server/conf folder that contains the config and index files. This will come in especially handy in the event you need to restore the backup on another server.
Just note that if you do have to restore on another server, you must maintain the same public URI you used previously (whether the server has the same host name, a DNS entry, proxy server, virtual host, etc...).
Also note that if you currently have or plan on having more than 10 users, you'll need to move to an enterprise DBMS rather than using Derby. Hope it helps,
Just note that if you do have to restore on another server, you must maintain the same public URI you used previously (whether the server has the same host name, a DNS entry, proxy server, virtual host, etc...).
Also note that if you currently have or plan on having more than 10 users, you'll need to move to an enterprise DBMS rather than using Derby. Hope it helps,