Question

  • Creator
    Topic
  • #2211731

    Archive Bits vs. DFS

    Locked

    by otaku_lord ·

    We have a master DFS share which is backed up to tape. I have just begun monitoring the DFS traffic and THINK that I see something which may explain the lag in replication time which we have been experiencing. Would someone please tell me if I can correct in this supposition?

    Does Backup Exec change the archive bit on ALL files that are backed up even if those files were not altered? Also, does that change cause the DFS service to replicate those changes across the network?

All Answers

  • Author
    Replies
    • #2814248

      Clarifications

      by otaku_lord ·

      In reply to Archive Bits vs. DFS

      Clarifications

    • #2814232

      One Example of the information I am reviewing…

      by otaku_lord ·

      In reply to Archive Bits vs. DFS

      The log file is 4500+ pages and the share has been active for less than one month.

      Table Type: Outbound Log Table for DFS (5)
      SequenceNumber : 0011a26d
      Flags : 01040008 Flags [Locn VVjoinToOrig CmpresStage ]
      IFlags : 00000001 Flags [IFlagVVRetireExec ]
      State : 00000014 CO STATE: IBCO_OUTBOUND_REQUEST
      ContentCmd : 00000000 Flags []
      Lcmd : 00000000 D/F 0 Create
      FileAttributes : 00000020 Flags [ARCHIVE ]
      FileVersionNumber : 00000002
      PartnerAckSeqNumber : 000cd06c
      FileSize : 00000000 00001000
      FileOffset : 00000000 00000000
      FrsVsn : 01caec50 51f9fc47
      FileUsn : 00000001 07444420
      JrnlUsn : 00000000 00000000
      JrnlFirstUsn : 00000000 00000000
      OriginalReplica : 5 [???]
      NewReplica : 5 [???]
      ChangeOrderGuid : 80c0bb81-d9a2-44f6-b9e968068a9bc8cb
      OriginatorGuid : 02bec8bf-7e57-4e08-a900ce6ade5db890
      FileGuid : b0df07ba-63a4-4335-9be09efba01d2326
      OldParentGuid : 9c36be3c-48e6-42f6-80899b99c40203f1
      NewParentGuid : 9c36be3c-48e6-42f6-80899b99c40203f1
      CxtionGuid : baf05a4c-5dde-4bc1-b959dd480f24b4e0
      Spare1Ull : Sun May 30, 2010 10:25:28
      MD5CheckSum : MD5: 5262a5fb ef77ad0c 3f20fd76 b44d008d
      RetryCount : 0
      FirstTryTime : Sun May 30, 2010 18:27:25
      EventTime : Fri May 14, 2010 09:56:50
      FileNameLength : 10
      FileName : I.MC7
      Cxtion Name : {A5F1889C-E69C-466B-899D-4EEA83E6423B} <- \\
      Cxtion State : Joined

Viewing 1 reply thread