@prefix dcterms: <http://purl.org/dc/terms/> .
@prefix edu: <https://knobit.org/def/> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix schema: <https://schema.org/> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .

<https://knobit.org/id/task/dso-migration-cutover/C1> a edu:Question ;
    rdfs:label "C1 (3 points)"@en ;
    dcterms:license <https://creativecommons.org/licenses/by/4.0/> ;
    owl:sameAs <https://bitbucket.org/reffa/ontology/id/task/dso-migration-cutover/C1> ;
    schema:hasPart <https://knobit.org/id/register/data-storage-operations#SO-550>,
        <https://knobit.org/id/register/data-storage-operations#SO-551>,
        <https://knobit.org/id/register/data-storage-operations#SO-552> ;
    schema:identifier "C1" ;
    schema:position 1 ;
    schema:text "Rollback after real postings, 1 each. (a) Wave W1's rollback restores legacy from the Friday 20:00 backup and is called possible until Sunday 23:59, but the new core posts card payments, transfers and standing orders from Saturday 06:00: the answer says a restore after 06:00 would erase real customer postings, so the rollback cannot work as written. (b) A way back that works: the point of no return set at Saturday 06:00 (the first customer posting) with rollback by repointing channels to the unchanged legacy until then; or a reverse migration of every posting made on the new core, saying how it is done and reconciled. (c) W1's go/no-go decision at Saturday 10:00 falls after the first posting: moved before Saturday 06:00 (or, with a reverse migration in (b), before the later point of no return that reverse migration sets, stated)."@en .

edu:Question rdfs:label "Question"@en,
        "Küsimus"@et .

<https://knobit.org/id/register/data-storage-operations#SO-550> rdfs:label "dso-migration-cutover C1a: W1 rollback by restore after the new core posts real transactions"@en .

<https://knobit.org/id/register/data-storage-operations#SO-551> rdfs:label "dso-migration-cutover C1b: a way back that works - point of no return at the first posting, or a reverse migration"@en .

<https://knobit.org/id/register/data-storage-operations#SO-552> rdfs:label "dso-migration-cutover C1c: go/no-go decision moved before the point of no return"@en .