locked
Azure File Sync - Daily ShadowCopy Snaphot RRS feed

  • Question

  • We are currently testing Azure File Sync and noticed that the client creates a ShadowCopy snapshot every day at 00:00.

    Which is fine, but it doesn't remove the snapshot after it is done.

    Is this intended behavior or does the cleanup not work correctly?

    From eventlog:
    Log Name:      Microsoft-FileSync-Agent/Operational
    Source:        Microsoft-FileSync-Agent
    Date:          23.03.2018 00.00.00
    Event ID:      8000
    Task Category: None
    Level:         Information
    Keywords:      
    User:          SYSTEM
    Computer:      ...
    Description:
    Client begun sync from VSS snapshot, id: 4; replica groups: All

    Log Name:      Microsoft-FileSync-Agent/Operational
    Source:        Microsoft-FileSync-Agent
    Date:          23.03.2018 00.00.16
    Event ID:      8011
    Task Category: None
    Level:         Information
    Keywords:      
    User:          SYSTEM
    Computer:      ...
    Description:
    Ended sync from VSS snapshot workflow, id: 4; error: 0x00000000 - The operation completed successfully.

    vssadmin list shadows
    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001-2013 Microsoft Corp.

    Contents of shadow copy set ID: {243d8099-3742-49c7-bc63-07a34f4a96e0}
       Contained 1 shadow copies at creation time: 23.03.2018 00.00.12
          Shadow Copy ID: {1c2f503f-7ac8-4443-9410-427371a7e7c8}
             Original Volume: (D:)\\?\Volume{79c02a48-30c6-4e84-ad42-8c32ce46848d}\
             Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy4
             Originating Machine: ...
             Service Machine: ...
             Provider: 'Microsoft Software Shadow Copy provider 1.0'
             Type: Backup
             Attributes: Differential

    Friday, March 23, 2018 9:25 AM

Answers

  • To close the loop: we did find that we hold onto the VSS snapshot that we take for 24 hours when we should only hold it for the time it takes to complete our usage of it.  Fixing this.

    klaas [Principal PM Manager @Microsoft]

    • Proposed as answer by klaas langhout Thursday, April 5, 2018 4:37 PM
    • Marked as answer by joakim lemb Friday, April 6, 2018 8:25 AM
    Thursday, April 5, 2018 4:37 PM

All replies

  • Hi, this should not be the case.  Following up with the engineers that own this portion but in parallel, can you send the output from an administrative command prompt  c:\vssadmin list shadows <enter> to the alias azurefiles at microsoft dot com ?  We are looking into this.

    Thanks


    klaas L Principle PM Manager @Microsoft

    Friday, March 23, 2018 7:21 PM
  • Thanks, an email has been sent to that address with the information you requested.
    Monday, March 26, 2018 11:20 AM
  • To close the loop: we did find that we hold onto the VSS snapshot that we take for 24 hours when we should only hold it for the time it takes to complete our usage of it.  Fixing this.

    klaas [Principal PM Manager @Microsoft]

    • Proposed as answer by klaas langhout Thursday, April 5, 2018 4:37 PM
    • Marked as answer by joakim lemb Friday, April 6, 2018 8:25 AM
    Thursday, April 5, 2018 4:37 PM