SDP-435
Open
Provide a mechanism for backing up and recovering any and all readonly/partitioned client data.
The offline database can be used to recover the production database (this contains journaled data) but the readonly/partitioned clients are overlooked. A database failure in the SDP environment does not currently provide the means to recover these partitioned/readonly clients.
The offline database can be used to recover the production database (this contains journaled data) but the readonly/partitioned clients are overlooked. A database failure in the SDP environment does not currently provide the means to recover these partitioned/readonly clients.
- Status
- Open
- Project
- perforce-software-sdp
- Severity
- A
- Reported By
- Adam Morriss
- Reported Date
- Modified By
- C. Thomas Tyler
- Modified Date
- Owned By
- amo
- Dev Notes
- This was filed as a bug, but I have re-classified it as a Feature.
See comments in the job for a discussion on this issue. A fair
question is rasied about P4D behvaior, as well as reasons for the
current P4D behaviour. In any case, the issue here is not an SDP
bug. - Component
- core-unix
- Type
- Feature