Problems after restoring to different host
I'd like to create a second copy of our live database.
We have a nightly backup that is done using repotools.
I have tried restoring from that and I've also tried restoring from an offline db2 backup of our database the result is the same: after the restoration we can no longer save user accounts in the ccm server (jts accounts seem ok) and we can no longer save dashboards; you can edit, save and refresh as much as you like, once you navigate away from the dashboard, when you go back it will have reset itself to it's original state.
Approximate method for preparing the destination host and restoring is :
Install fresh copy of RTC
Install DB2 if not already installed, create 2 databases: JTS and JAZZ
Restore the databases
db2 RESTORE DATABASE JTS FROM C:\DB2BACK
db2 RESTORE DATABASE RTC_LIVE from C:\DB2Back TAKEN AT 20110210100740 INTO JAZZ
Update the teamserver.properties files to match the db2 databases
Reset the Lock Ids
repotools-jts.bat -resetRepoLockId
repotools-jazz.bat -resetRepoLockId
Start The Server
Log into jazz/admin and remove the friend
Log into jts/admin and remove the registered application
Run Setup...
This procedure works apart from the two items I mention above and any others I haven't found yet.
Also, I have confirmed that we do not have either of these problems in the originating repository.
Anyone have any suggestions?
Many Thanks,
Robin
We have a nightly backup that is done using repotools.
I have tried restoring from that and I've also tried restoring from an offline db2 backup of our database the result is the same: after the restoration we can no longer save user accounts in the ccm server (jts accounts seem ok) and we can no longer save dashboards; you can edit, save and refresh as much as you like, once you navigate away from the dashboard, when you go back it will have reset itself to it's original state.
Approximate method for preparing the destination host and restoring is :
Install fresh copy of RTC
Install DB2 if not already installed, create 2 databases: JTS and JAZZ
Restore the databases
db2 RESTORE DATABASE JTS FROM C:\DB2BACK
db2 RESTORE DATABASE RTC_LIVE from C:\DB2Back TAKEN AT 20110210100740 INTO JAZZ
Update the teamserver.properties files to match the db2 databases
Reset the Lock Ids
repotools-jts.bat -resetRepoLockId
repotools-jazz.bat -resetRepoLockId
Start The Server
Log into jazz/admin and remove the friend
Log into jts/admin and remove the registered application
Run Setup...
This procedure works apart from the two items I mention above and any others I haven't found yet.
Also, I have confirmed that we do not have either of these problems in the originating repository.
Anyone have any suggestions?
Many Thanks,
Robin
3 answers
Hi Robin,
This is not officially supported yet. Here's a work item to track this:
https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/150638
As for the dashboard not saving, I would recommend shutting down the JTS and running repotools-jts -reindex then restarting. Note that the dashboards from your old server will not be available after such a move, but they should at least save properly if you want to rebuild them manually. I've created WI https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/153145 to add manual steps for restoring the dashboards after public URI change.
This is not officially supported yet. Here's a work item to track this:
https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/150638
As for the dashboard not saving, I would recommend shutting down the JTS and running repotools-jts -reindex then restarting. Note that the dashboards from your old server will not be available after such a move, but they should at least save properly if you want to rebuild them manually. I've created WI https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/153145 to add manual steps for restoring the dashboards after public URI change.