none
DFSR cancella file invece che aggiornarli RRS feed

  • Domanda

  • Ho un DFSR attivo fra due server W2016 e W2012 per mantenere sincronizzate due cartelle di disegni CAD

    A volte file che dovrebbero essere aggiornati vengono eliminati

    Nel file di log ho queste indicazionerelativamente al file XT0350011.idw che è uno dei file che sono spariti

    Primo file di log

    20210126 10:03:24.790 4332 DIRW  1986 DirWalkerTask::WalkImmediateChildren Validating:
    +    fid                             0x500000003BE90
    +    usn                             0x1d30a40ab0
    +    uidVisible                      1
    +    filtered                        0
    +    journalWrapped                  1
    +    slowRecoverCheck                0
    +    pendingTombstone                0
    +    internalUpdate                  0
    +    dirtyShutdownMismatch           0
    +    meetInstallUpdate               0
    +    meetReanimated                  0
    +    recUpdateTime                   20210112 01:56:50.285 GMT
    +    present                         1
    +    nameConflict                    0
    +    attributes                      0x21
    +    ghostedHeader                   0
    +    data                            0
    +    gvsn                            {1F48B6B6-7D67-4C07-9BBA-926C762D716A}-v1508537
    +    uid                             {1F48B6B6-7D67-4C07-9BBA-926C762D716A}-v1508536
    +    parent                          {FAF62CF0-C2D5-4F63-9236-0C466D26DD56}-v357609
    +    fence                           Default (3)
    +    clockDecrementedInDirtyShutdown 0
    +    clock                           20210112 01:56:50.269 GMT (0x1d6e88631330b21)
    +    createTime                      20191011 19:47:24.996 GMT
    +    csId                            {DABB4FF3-935B-4C7E-B3C8-4784F957D3B8}
    +    hash                            59648260-E48CF910-C7698D0C-4486D7BA
    +    similarity                      2825280A-0E0B333C-08013A31-131D320F
    +    name                            XT0350011.idw
    +      Against-----> name:XT0350011.idw fid:0x500000003BE90 usn:0x1d30a40ab0 parentFid:0x248000000056AC7 parentUid:{FAF62CF0-C2D5-4F63-9236-0C466D26DD56}-v357609 attributes:0x21
    20210126 10:03:24.790 4332 DIRW  2713 DirWalkerTask::Unmark LDB Updating ID Record:
    +    fid                             0x500000003BE90
    +    usn                             0x1d30a40ab0
    +    uidVisible                      1
    +    filtered                        0
    +    journalWrapped                  0
    +    slowRecoverCheck                0
    +    pendingTombstone                0
    +    internalUpdate                  0
    +    dirtyShutdownMismatch           0
    +    meetInstallUpdate               0
    +    meetReanimated                  0
    +    recUpdateTime                   20210112 01:56:50.285 GMT
    +    present                         1
    +    nameConflict                    0
    +    attributes                      0x21
    +    ghostedHeader                   0
    +    data                            0
    +    gvsn                            {1F48B6B6-7D67-4C07-9BBA-926C762D716A}-v1508537
    +    uid                             {1F48B6B6-7D67-4C07-9BBA-926C762D716A}-v1508536
    +    parent                          {FAF62CF0-C2D5-4F63-9236-0C466D26DD56}-v357609
    +    fence                           Default (3)
    +    clockDecrementedInDirtyShutdown 0
    +    clock                           20210112 01:56:50.269 GMT (0x1d6e88631330b21)
    +    createTime                      20191011 19:47:24.996 GMT
    +    csId                            {DABB4FF3-935B-4C7E-B3C8-4784F957D3B8}
    +    hash                            59648260-E48CF910-C7698D0C-4486D7BA
    +    similarity                      2825280A-0E0B333C-08013A31-131D320F
    +    name                            XT0350011.idw
    +   

    Poi in un secondo file di log

        Line 185491: 20210126 10:09:40.535 6760 DBSR   608 SlowRecoverTask::Recover Skipping record (!slowRecoverCheck || !alive). uid:{FAF62CF0-C2D5-4F63-9236-0C466D26DD56}-v668248 name:XT0350011.iam usn:0x10f3750818 csId:{DABB4FF3-935B-4C7E-B3C8-4784F957D3B8}
        Line 185492: 20210126 10:09:40.535 6760 DBSR   608 SlowRecoverTask::Recover Skipping record (!slowRecoverCheck || !alive). uid:{FAF62CF0-C2D5-4F63-9236-0C466D26DD56}-v668252 name:XT0350011.idw.20210112025650.112.erased usn:0x1d30a40b08 csId:{DABB4FF3-935B-4C7E-B3C8-4784F957D3B8}
        Line 185493: 20210126 10:09:40.535 6760 DBSR   608 SlowRecoverTask::Recover Skipping record (!slowRecoverCheck || !alive). uid:{FAF62CF0-C2D5-4F63-9236-0C466D26DD56}-v668260 name:XT0350011.pdf usn:0x10f3755f08 csId:{DABB4FF3-935B-4C7E-B3C8-4784F957D3B8}
        Line 185494: 20210126 10:09:40.535 6760 DBSR   608 SlowRecoverTask::Recover Skipping record (!slowRecoverCheck || !alive). uid:{FAF62CF0-C2D5-4F63-9236-0C466D26DD56}-v668263 name:XT0350011.dxf usn:0x10f3758bc8 csId:{DABB4FF3-935B-4C7E-B3C8-4784F957D3B8}

    Io non so leggere i log del dfsr.

    Possono essere utili? Danno qualche indicazione?


    Gianni

    domenica 31 gennaio 2021 14:08

Risposte

  • Puoi ordinare i riferimenti per forzare l'utilizzo di un determinato server e in qualche modo influenzare la direzione di replica, ma la replica è sempre bidirezionale, per questo il problema potrebbe provenire anche dal 2012.


    giovedì 4 febbraio 2021 14:50
    Moderatore

Tutte le risposte