Use Case: Database corruption
We have 100 RTC projects using Source Control on an Oracle database.
If the database gets corrupt (for what ever reason) all 100 projects will be impacted while we go to tape to recover the database.
In ClearCase if a database gets corrupted only the corrupt VOB needs to be recovered (and does not impact other VOBs).
Has anyone considered this use case?
If the database gets corrupt (for what ever reason) all 100 projects will be impacted while we go to tape to recover the database.
In ClearCase if a database gets corrupted only the corrupt VOB needs to be recovered (and does not impact other VOBs).
Has anyone considered this use case?
3 answers
We have 100 RTC projects using Source Control on an Oracle database.
If the database gets corrupt (for what ever reason) all 100 projects will be impacted while we go to tape to recover the database.
In ClearCase if a database gets corrupted only the corrupt VOB needs to be recovered (and does not impact other VOBs).
Has anyone considered this use case?
Yes, and it's rather frightening, but the alternative is 100 databases and 100 separate repositories.
Yep but 100 RTC instances would not be maintainable...
We are thinking about using a script to export source and house it is another source repository (git maybe) as a safety net.
Just thought I put the question out there to stimulate debate.
Oracle "Flashback" is another option available to us.
We are thinking about using a script to export source and house it is another source repository (git maybe) as a safety net.
Just thought I put the question out there to stimulate debate.
Oracle "Flashback" is another option available to us.