RTC Backup and Restore
Hi
I am looking at the production backup and restore procedures for RTC 3.0.1 with WAS 7 and Oracle.
http://publib.boulder.ibm.com/infocenter/clmhelp/v3r0m1/topic/com.ibm.jazz.repository.web.admin.doc/topics/t_jfs_backup.html
Basically we need to backup:
1. JazzInstallDir/server/conf/jts
2. run the backupConfig script for WAS
3. Backup Oracle.
Am I missing anything?
The following link only provide steps for DB2, is there a procedure for Oracle 11g?
http://publib.boulder.ibm.com/infocenter/clmhelp/v3r0m1/topic/com.ibm.jazz.repository.web.admin.doc/topics/t_backup_commercial_db.html
Thanks
Jirong
I am looking at the production backup and restore procedures for RTC 3.0.1 with WAS 7 and Oracle.
http://publib.boulder.ibm.com/infocenter/clmhelp/v3r0m1/topic/com.ibm.jazz.repository.web.admin.doc/topics/t_jfs_backup.html
Basically we need to backup:
1. JazzInstallDir/server/conf/jts
2. run the backupConfig script for WAS
3. Backup Oracle.
Am I missing anything?
The following link only provide steps for DB2, is there a procedure for Oracle 11g?
http://publib.boulder.ibm.com/infocenter/clmhelp/v3r0m1/topic/com.ibm.jazz.repository.web.admin.doc/topics/t_backup_commercial_db.html
Thanks
Jirong
5 answers
We are on windows, we are backing up the server, which includes the WAS config and the RTC config.
However, we are not so concerned with the server, as we have a DR server which we would switch to, in our case, we would reinstall the app to the primary server if required.
The DB (MSSQL), is a hot backup, we don't shutdown anything, this way RTC is online at all times. We don't have to worry about locking users out (geographically in many countries), or locking out jobs from buildforge.
According to the docs, you should also backup you index locations (in our case they are on a NAS share), however, we don't do this. It was too difficult to syncrhonise the backup of the DB with the NAS share (since they are managed by different groups in our organisation). The indices are easy to recreate with a few simple commands, so in the event of a restore, we restore the DB and recreate the indices. We've tested this and confirmed with IBM support that this is a valid approach.
However, we are not so concerned with the server, as we have a DR server which we would switch to, in our case, we would reinstall the app to the primary server if required.
The DB (MSSQL), is a hot backup, we don't shutdown anything, this way RTC is online at all times. We don't have to worry about locking users out (geographically in many countries), or locking out jobs from buildforge.
According to the docs, you should also backup you index locations (in our case they are on a NAS share), however, we don't do this. It was too difficult to syncrhonise the backup of the DB with the NAS share (since they are managed by different groups in our organisation). The indices are easy to recreate with a few simple commands, so in the event of a restore, we restore the DB and recreate the indices. We've tested this and confirmed with IBM support that this is a valid approach.
Thanks for your reply.
As I know so far, our ITS is backup all files on the server. In this case, for WAS server, is this ITS backup sufficient? Do we have to "run the backupConfig script for WebSphere Application Server" in addition to our ITS backup?
I am going to ask DBA to backup our Oracle DB anyway. Just need to figure our if we need to do anything other than ITS file level backup on our WAS server.
There is something I don't quite understand is: do I have to backup the files in WAS server? Assume I know all the settings I did during the installation such as LDAP info. Let's say the WAS server is gone. Can I just reinstall RTC(JTS/CCM) on a new server and connect it to the existing database, by re-run the setup Wizard?
Jirong
As I know so far, our ITS is backup all files on the server. In this case, for WAS server, is this ITS backup sufficient? Do we have to "run the backupConfig script for WebSphere Application Server" in addition to our ITS backup?
I am going to ask DBA to backup our Oracle DB anyway. Just need to figure our if we need to do anything other than ITS file level backup on our WAS server.
There is something I don't quite understand is: do I have to backup the files in WAS server? Assume I know all the settings I did during the installation such as LDAP info. Let's say the WAS server is gone. Can I just reinstall RTC(JTS/CCM) on a new server and connect it to the existing database, by re-run the setup Wizard?
Jirong
Hi
Quick question, I have two servers, one for Jazz/WAS and another Oracle DB.
1. If DB server crashes, then I rebuild this DB server, restore the databases. Will it work automatically with the old Jazz server, or shall I do anything else?
2. If the Jazz server crashes, then I reinstall RTC on it, restore all config files. Will it work automatically with the old DB server, or shall I do anything else? If I don't have the backup of all config files, how can I connect to the DB server, re-run the setup wizard?
Or I have to restore both servers with the backup from the same day?
Thanks
Jirong
Quick question, I have two servers, one for Jazz/WAS and another Oracle DB.
1. If DB server crashes, then I rebuild this DB server, restore the databases. Will it work automatically with the old Jazz server, or shall I do anything else?
2. If the Jazz server crashes, then I reinstall RTC on it, restore all config files. Will it work automatically with the old DB server, or shall I do anything else? If I don't have the backup of all config files, how can I connect to the DB server, re-run the setup wizard?
Or I have to restore both servers with the backup from the same day?
Thanks
Jirong
1. That should work. As I said earlier, you'll need to rebuild the indices after restoring the db.
2. Yes, you can rerun the setup. This is our approach.
The only thing that is important is the application URI. I believe this cannot change.
As I said earlier, we developed our backup/restore approach as described above, since we did not want to follow the documented approach. We tested it, and got IBM support to confirm it's validity.
If you have any concerns, you should do the same, and get IBM to give it's approval, since they will be the ones supporting you in the event of restore problems.
2. Yes, you can rerun the setup. This is our approach.
The only thing that is important is the application URI. I believe this cannot change.
As I said earlier, we developed our backup/restore approach as described above, since we did not want to follow the documented approach. We tested it, and got IBM support to confirm it's validity.
If you have any concerns, you should do the same, and get IBM to give it's approval, since they will be the ones supporting you in the event of restore problems.