# The form data below was edited by super-tom_tyler # Perforce Workshop Jobs # # Job: The job name. 'new' generates a sequenced job number. # Status: Job status; [open/closed/suspended]. Required # Project: The project this job is for. Required. # Severity: [A/B/C] (A is highest) Required. # ReportedBy The user who created the job. Can be changed. # ReportedDate: The date the job was created. Automatic. # ModifiedBy: The user who last modified this job. Automatic. # ModifiedDate: The date this job was last modified. Automatic. # OwnedBy: The owner, responsible for doing the job. Optional. # Description: Description of the job. Required. # DevNotes: Developer's comments. Optional. # Type: Type of job; [Bug/Feature]. Required. Job: SDP-30 Status: closed Project: perforce-software-sdp Severity: B ReportedBy: ttyler ReportedDate: 2017/04/02 17:24:05 ModifiedBy: super-tom_tyler ModifiedDate: 2017/04/02 17:24:06 OwnedBy: ttyler Description: Enhanced offline_db 'stale data' check in weekly backup script. Add a check to verify that the offline_db is current (based on the journal counter) before doing the database swap in the weekly backup script. This addresses a scenario where a calamity of errors could cause the offline_db to be stale before the weekly backup script is run. A safety feature already in the SDP ensures that the offline_db is not incomplete, e.g. in the process of being written, as could occur if there were a sudden power off during checkpoint recovery. The improved check in this job will also verify that the data is current. DevNotes: This job, SDP-30, was originally named job000427. Type: Feature