none
"Windows Backup cannot read the backup destination" when trying to backup to Backup Once to Samba share on NAS

    Question

  • Environment:

    Windows Server 2012 R2 Essentials running in VirtualBox in a Windows 7 host. Networking is configured and works fine.

    Background:

    My only backup needs are to copy the contents of two folders to a NAS folder every day at 2 AM.

    I configured a backup schedule in Windows Server Backup (wbadmin) to a network location which is hosted as a Samba share on a Synology NAS.

    For authentication, I created a backup user which has the same username and password as a user on the Samba share, with permission to read and write the backup folder. I added this user to the Backup Operators group.

    Problem:

    When I try to run the Backup Once operation to test my backup, I get the following error message:

    "Windows Backup cannot read the backup destination."

    What I've tried:

    I verified that the location is directly accessible in Windows by copying and pasting the address from the Windows Server Backup destination into explorer. Providing the backup user credentials opened the location and creating/reading files worked fine.

    Adding the backup user to the Administrators group did not have an effect.

    Update 2014-02-18

    I checked the backup destination and was surprised to find that the scheduled backup actually completes successfully. However, Backup Once always results in the above error message. So the problem is confined to the "Backup Once" operation.


    • Edited by Malfunkshon Wednesday, March 12, 2014 4:13 PM
    Thursday, February 13, 2014 10:13 PM

All replies

  • Maybe you can try another software to do this, what about a third-party backup tool like aomei backupper?

    Backup to NAS:http://www.backup-utility.com/features/backup-to-nas.html

    Monday, February 17, 2014 2:49 AM
  • Hi,

    Thanks for posting in Microsoft Technet Forums.

    I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.

    Thank you for your understanding and support.

    Regards,

    Mandy


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

    Monday, February 17, 2014 8:10 AM
    Moderator
  • Hello,

    Please open a command prompt, type the following command and upload the results to this forum.

    Vssadmin list writers

    Vssadmin list Providers

    Vssadmin list shadows

    Vssadmin list shadowstorage

    Vssadmin list volumes


    Best regards,

    Sophia Sun


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Monday, February 24, 2014 11:11 AM
  • Hello,

    Hope everything is going great for you.

    Here are some articles related to this issue. Hope they are helpful.

    Remove backup destination/location

    http://answers.microsoft.com/en-us/windows/forum/windows_7-performance/remove-windows-7-backup-destinationlocation/aac100ff-629a-4148-b18a-a1488f056bad?msgId=dd6a70e3-01f0-4d06-8109-cbbab0713a13

    Error message when you try to add an additional disk to a scheduled backup: "The filename, directory name, or volume label syntax is incorrect"

    http://support.microsoft.com/kb/2009365/en-us

    Windows Backup & Restore Issues-Error message 0x8100002f -now control radio buttons are frozen

    http://answers.microsoft.com/en-us/windows/forum/windows_7-system/windows-backup-restore-issues-error-message/18f5859f-e104-47c6-90da-de330d4386c2

    Best regards,

    Sophia Sun


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    • Marked as answer by Mandy YeModerator Wednesday, March 12, 2014 1:59 AM
    • Unmarked as answer by Malfunkshon Wednesday, March 12, 2014 4:10 PM
    Monday, March 03, 2014 12:30 PM
  • Vssadmin list providers

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

    Provider name: 'Microsoft File Share Shadow Copy provider'
       Provider type: Fileshare
       Provider Id: {89300202-3cec-4981-9171-19f59559e0f2}
       Version: 1.0.0.1

    Provider name: 'Microsoft Software Shadow Copy provider 1.0'
       Provider type: System
       Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
       Version: 1.0.0.7

    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: {5636adcf-668c-4761-9f10-93475904c341}
       Contained 1 shadow copies at creation time: 2/19/2014 7:00:00 AM
          Shadow Copy ID: {4ca86ed5-9da5-49ca-8591-bf56ebd43486}
             Original Volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
             Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1
             Originating Machine: seattle-vm-win.GENE.local
             Service Machine: seattle-vm-win.GENE.local
             Provider: 'Microsoft Software Shadow Copy provider 1.0'
             Type: ClientAccessible
             Attributes: Persistent, Client-accessible, No auto release, No writers, Differential

    Contents of shadow copy set ID: {aa265dab-feaa-49ed-9b0e-7ed39ab7f9d6}
       Contained 1 shadow copies at creation time: 2/19/2014 2:00:00 PM
          Shadow Copy ID: {653a4fa5-4d37-4ea4-9d2a-5710b48cde09}
             Original Volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
             Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy2
             Originating Machine: seattle-vm-win.GENE.local
             Service Machine: seattle-vm-win.GENE.local
             Provider: 'Microsoft Software Shadow Copy provider 1.0'
             Type: ClientAccessible
             Attributes: Persistent, Client-accessible, No auto release, No writers, Differential

    Contents of shadow copy set ID: {9180a420-a6bd-490d-85da-8b81231502b9}
       Contained 1 shadow copies at creation time: 2/20/2014 7:00:00 AM
          Shadow Copy ID: {871d10ee-9034-4269-b841-4aeee9570464}
             Original Volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
             Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy3
             Originating Machine: seattle-vm-win.GENE.local
             Service Machine: seattle-vm-win.GENE.local
             Provider: 'Microsoft Software Shadow Copy provider 1.0'
             Type: ClientAccessible
             Attributes: Persistent, Client-accessible, No auto release, No writers, Differential

    Contents of shadow copy set ID: {d83afc4e-317f-488c-89d5-a0e65844b93e}
       Contained 1 shadow copies at creation time: 2/20/2014 2:00:00 PM
          Shadow Copy ID: {f6fbb4ff-bac8-4a82-88e8-dffba8656424}
             Original Volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
             Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy4
             Originating Machine: seattle-vm-win.GENE.local
             Service Machine: seattle-vm-win.GENE.local
             Provider: 'Microsoft Software Shadow Copy provider 1.0'
             Type: ClientAccessible
             Attributes: Persistent, Client-accessible, No auto release, No writers, Differential

    Contents of shadow copy set ID: {3774a3f2-cd36-4f36-9667-4f96c0dbe0b3}
       Contained 1 shadow copies at creation time: 2/21/2014 7:00:00 AM
          Shadow Copy ID: {91d6c61a-8b39-48dd-811d-e0dcf593c967}
             Original Volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
             Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy5
             Originating Machine: seattle-vm-win.GENE.local
             Service Machine: seattle-vm-win.GENE.local
             Provider: 'Microsoft Software Shadow Copy provider 1.0'
             Type: ClientAccessible
             Attributes: Persistent, Client-accessible, No auto release, No writers, Differential

    Contents of shadow copy set ID: {99be106c-a96d-4488-a9ae-6e92452393ee}
       Contained 1 shadow copies at creation time: 2/21/2014 2:00:00 PM
          Shadow Copy ID: {5bd57dff-0591-4b0f-9ee8-1b8857f59e54}
             Original Volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
             Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy6
             Originating Machine: seattle-vm-win.GENE.local
             Service Machine: seattle-vm-win.GENE.local
             Provider: 'Microsoft Software Shadow Copy provider 1.0'
             Type: ClientAccessible
             Attributes: Persistent, Client-accessible, No auto release, No writers, Differential

    Contents of shadow copy set ID: {299f4ca8-bffa-47b7-9bb2-12358e0282ce}
       Contained 1 shadow copies at creation time: 2/22/2014 7:00:00 AM
          Shadow Copy ID: {90b732ae-7ea8-4457-8a6d-84983e27b120}
             Original Volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
             Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy7
             Originating Machine: seattle-vm-win.GENE.local
             Service Machine: seattle-vm-win.GENE.local
             Provider: 'Microsoft Software Shadow Copy provider 1.0'
             Type: ClientAccessible
             Attributes: Persistent, Client-accessible, No auto release, No writers, Differential

    Contents of shadow copy set ID: {97225977-6687-4538-b627-1b33985c9ac1}
       Contained 1 shadow copies at creation time: 2/22/2014 2:00:00 PM
          Shadow Copy ID: {128d7818-ce91-4d35-ad9e-577856d17374}
             Original Volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
             Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy8
             Originating Machine: seattle-vm-win.GENE.local
             Service Machine: seattle-vm-win.GENE.local
             Provider: 'Microsoft Software Shadow Copy provider 1.0'
             Type: ClientAccessible
             Attributes: Persistent, Client-accessible, No auto release, No writers, Differential

    Contents of shadow copy set ID: {b196f043-a073-46e4-baa4-2eb99969cc7e}
       Contained 1 shadow copies at creation time: 2/23/2014 7:00:00 AM
          Shadow Copy ID: {931780f6-be5e-4ad9-9f4d-151ffd6b1942}
             Original Volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
             Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy9
             Originating Machine: seattle-vm-win.GENE.local
             Service Machine: seattle-vm-win.GENE.local
             Provider: 'Microsoft Software Shadow Copy provider 1.0'
             Type: ClientAccessible
             Attributes: Persistent, Client-accessible, No auto release, No writers, Differential

    Contents of shadow copy set ID: {f24e1101-8505-450c-a802-8ba65e46d8d5}
       Contained 1 shadow copies at creation time: 2/23/2014 2:00:00 PM
          Shadow Copy ID: {815dff7e-92df-449e-a1ed-eb8e5fa3baeb}
             Original Volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
             Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy10
             Originating Machine: seattle-vm-win.GENE.local
             Service Machine: seattle-vm-win.GENE.local
             Provider: 'Microsoft Software Shadow Copy provider 1.0'
             Type: ClientAccessible
             Attributes: Persistent, Client-accessible, No auto release, No writers, Differential

    Contents of shadow copy set ID: {d4213f80-6b73-418c-af73-b704007511ed}
       Contained 1 shadow copies at creation time: 2/24/2014 7:00:00 AM
          Shadow Copy ID: {e3bd9313-e7a3-4972-a138-e298e6c12eff}
             Original Volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
             Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy11
             Originating Machine: seattle-vm-win.GENE.local
             Service Machine: seattle-vm-win.GENE.local
             Provider: 'Microsoft Software Shadow Copy provider 1.0'
             Type: ClientAccessible
             Attributes: Persistent, Client-accessible, No auto release, No writers, Differential

    Contents of shadow copy set ID: {1587431c-1ca9-4276-8d33-dd13ae58a122}
       Contained 1 shadow copies at creation time: 2/24/2014 2:00:00 PM
          Shadow Copy ID: {e4c3e5b4-0314-4496-9215-369b3c973b25}
             Original Volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
             Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy12
             Originating Machine: seattle-vm-win.GENE.local
             Service Machine: seattle-vm-win.GENE.local
             Provider: 'Microsoft Software Shadow Copy provider 1.0'
             Type: ClientAccessible
             Attributes: Persistent, Client-accessible, No auto release, No writers, Differential

    Contents of shadow copy set ID: {b79771fa-666c-40ff-98c2-80580c1fdf85}
       Contained 1 shadow copies at creation time: 2/25/2014 2:00:01 PM
          Shadow Copy ID: {9d23803a-5d4e-4222-a389-ddd1e17b0472}
             Original Volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
             Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy13
             Originating Machine: seattle-vm-win.GENE.local
             Service Machine: seattle-vm-win.GENE.local
             Provider: 'Microsoft Software Shadow Copy provider 1.0'
             Type: ClientAccessible
             Attributes: Persistent, Client-accessible, No auto release, No writers, Differential

    Contents of shadow copy set ID: {5b472176-33e7-447f-aebf-da630cebe01d}
       Contained 1 shadow copies at creation time: 2/26/2014 7:00:01 AM
          Shadow Copy ID: {0d5a5d90-c9e7-42c0-ab0b-accf0d7d7304}
             Original Volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
             Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy14
             Originating Machine: seattle-vm-win.GENE.local
             Service Machine: seattle-vm-win.GENE.local
             Provider: 'Microsoft Software Shadow Copy provider 1.0'
             Type: ClientAccessible
             Attributes: Persistent, Client-accessible, No auto release, No writers, Differential

    Contents of shadow copy set ID: {879a32b4-48f3-434f-8d92-7202a9a25076}
       Contained 1 shadow copies at creation time: 2/26/2014 2:00:00 PM
          Shadow Copy ID: {887d8ff9-db0d-4eaa-9a75-df60015c2bb7}
             Original Volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
             Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy15
             Originating Machine: seattle-vm-win.GENE.local
             Service Machine: seattle-vm-win.GENE.local
             Provider: 'Microsoft Software Shadow Copy provider 1.0'
             Type: ClientAccessible
             Attributes: Persistent, Client-accessible, No auto release, No writers, Differential

    Contents of shadow copy set ID: {fc8d7e9e-c4d4-4010-b603-d88b99435338}
       Contained 1 shadow copies at creation time: 2/27/2014 7:00:00 AM
          Shadow Copy ID: {69ca835d-0130-4435-8621-83a716f1b621}
             Original Volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
             Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy16
             Originating Machine: seattle-vm-win.GENE.local
             Service Machine: seattle-vm-win.GENE.local
             Provider: 'Microsoft Software Shadow Copy provider 1.0'
             Type: ClientAccessible
             Attributes: Persistent, Client-accessible, No auto release, No writers, Differential

    Contents of shadow copy set ID: {7cebbd3b-c599-4800-91f5-da94ca038a42}
       Contained 1 shadow copies at creation time: 2/27/2014 2:00:00 PM
          Shadow Copy ID: {57320a15-e046-4128-8305-661984910fff}
             Original Volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
             Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy17
             Originating Machine: seattle-vm-win.GENE.local
             Service Machine: seattle-vm-win.GENE.local
             Provider: 'Microsoft Software Shadow Copy provider 1.0'
             Type: ClientAccessible
             Attributes: Persistent, Client-accessible, No auto release, No writers, Differential

    Contents of shadow copy set ID: {702d2ca4-3f60-4d64-8578-50d9dd587ba6}
       Contained 1 shadow copies at creation time: 3/12/2014 6:00:01 AM
          Shadow Copy ID: {41c62c15-ad88-4191-8cc8-c2814da9a2f4}
             Original Volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
             Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy18
             Originating Machine: seattle-vm-win.GENE.local
             Service Machine: seattle-vm-win.GENE.local
             Provider: 'Microsoft Software Shadow Copy provider 1.0'
             Type: ClientAccessible
             Attributes: Persistent, Client-accessible, No auto release, No writers, Differential

    Vssadmin list shadowstorage

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

    Shadow Copy Storage association
       For volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
       Shadow Copy Storage volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
       Used Shadow Copy Storage space: 3.47 GB (8%)
       Allocated Shadow Copy Storage space: 3.73 GB (9%)
       Maximum Shadow Copy Storage space: 3.96 GB (10%)

    Vssadmin list volumes

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

    Volume path: \\?\Volume{ca9edd16-98f7-11e3-80b0-806e6f6e6963}\
        Volume name: \\?\Volume{ca9edd16-98f7-11e3-80b0-806e6f6e6963}\
    Volume path: C:\
        Volume name: \\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\

    Vssadmin list writers

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

    Writer name: 'Task Scheduler Writer'
       Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
       Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
       State: [1] Stable
       Last error: No error

    Writer name: 'VSS Metadata Store Writer'
       Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
       Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
       State: [1] Stable
       Last error: No error

    Writer name: 'Performance Counters Writer'
       Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
       Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
       State: [1] Stable
       Last error: No error

    Writer name: 'SqlServerWriter'
       Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
       Writer Instance Id: {004b7983-7f00-4abe-81de-36729db8355f}
       State: [1] Stable
       Last error: No error

    Writer name: 'ASR Writer'
       Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
       Writer Instance Id: {73682cd4-c469-4d00-b9b9-4b64f08af879}
       State: [1] Stable
       Last error: No error

    Writer name: 'COM+ REGDB Writer'
       Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
       Writer Instance Id: {652f9dce-637f-447f-bbde-a16dc119e409}
       State: [1] Stable
       Last error: No error

    Writer name: 'Shadow Copy Optimization Writer'
       Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
       Writer Instance Id: {cd1dab9c-a9cb-4783-aff3-32fa2f9e625f}
       State: [1] Stable
       Last error: No error

    Writer name: 'Registry Writer'
       Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
       Writer Instance Id: {ba4c4bc6-9081-422a-9ed1-647c0eacfe8d}
       State: [1] Stable
       Last error: No error

    Writer name: 'DFS Replication service writer'
       Writer Id: {2707761b-2324-473d-88eb-eb007a359533}
       Writer Instance Id: {4e4ca3e1-c62a-474f-a925-fadc1a534188}
       State: [1] Stable
       Last error: No error

    Writer name: 'Windows Server Storage VSS Writer'
       Writer Id: {e376ebb9-f0fe-4e1a-adaa-bfbdaf3ab488}
       Writer Instance Id: {044b493b-829f-4bcd-9a8f-6d96a9d38daa}
       State: [1] Stable
       Last error: No error

    Writer name: 'WMI Writer'
       Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
       Writer Instance Id: {72c13a8c-4950-4abb-961a-2e0f612ea9b6}
       State: [1] Stable
       Last error: No error

    Writer name: 'System Writer'
       Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
       Writer Instance Id: {da138ec1-764b-4179-b2f4-70e94ac22276}
       State: [1] Stable
       Last error: No error

    Writer name: 'MSSearch Service Writer'
       Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
       Writer Instance Id: {dd729383-00a9-484c-9abc-3de903f5347c}
       State: [1] Stable
       Last error: No error

    Writer name: 'IIS Config Writer'
       Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
       Writer Instance Id: {a7c0287b-0e85-4d37-9649-d79928def55e}
       State: [1] Stable
       Last error: No error

    Writer name: 'NTDS'
       Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
       Writer Instance Id: {aca73317-e7ce-40a0-aac2-548fd6a987c3}
       State: [1] Stable
       Last error: No error

    Writer name: 'IIS Metabase Writer'
       Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
       Writer Instance Id: {d7753d0e-6b3b-4af0-95ea-9aa6733071f4}
       State: [1] Stable
       Last error: No error

    Writer name: 'Certificate Authority'
       Writer Id: {6f5b15b5-da24-4d88-b737-63063e3a1f86}
       Writer Instance Id: {5971db7f-8508-438c-8f62-736f1b07750f}
       State: [1] Stable
       Last error: No error

    Wednesday, March 12, 2014 4:09 PM
  • None of the articles in this answer are related to the problem.
    Wednesday, March 12, 2014 4:12 PM
  • Hello,

    I have checked the VSSAdmin results. As we can see, the result is OK.

    Currently, please initiated a System State Backup. If it failed while listing the files to be backed up, this means that the backup was not able to traverse a path for some service.

    After that, please disable the AV software if you have installed one on the affected machine and test how the issue goes.

    Best regards,

    Sophia Sun


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Tuesday, April 01, 2014 3:04 AM
  • Over a year old, but this info might help someone:

    I have the same issue.
    The suggestions in the post were not helpful and completely unrelated.

    My troubleshooting uncovered a workaround...
    The backup would not run as scheduled due to the error "block level backup engine could not be started"
    If I mapped a drive to the destination, the backup would then run using the 'Backup Once' option.
    It still would not run as scheduled as I received the error "you have multiple connections to the same resource"
    It isn't a permissions issue and the destination is visible on the network as I can map to it.
    Event viewer has no entries relating to this issue other than "block level backup engine could not be started".

    Tuesday, March 17, 2015 12:09 PM
  • Hi Guys,

    Not sure if the OP ever got this resolved but we just ran into the same issue with a clients server. The answer is that "Backup Once" uses the user account that us currently logged on, where the "Backup Schedule" uses a different account

    In our case our NAS was joined to the domain and we where able to see the permission errors so was very quick fgix, added the domain account that is logged in access to the share and it worked.

    Hope this helps.

    • Proposed as answer by Mantybug Wednesday, September 14, 2016 5:07 PM
    Sunday, August 07, 2016 9:55 AM
  • Thank you so much for digging up this old cow. Your answer was spot on!
    Wednesday, September 14, 2016 5:07 PM
  • Thank you for this information!!  Even when selecting to use the scheduled job in the backup once wizard, it does indeed use the locally logged in credentials.  

    +1 to this!

    Thanks!


    Monday, January 16, 2017 5:32 PM
  • Hi Guys,

    Not sure if the OP ever got this resolved but we just ran into the same issue with a clients server. The answer is that "Backup Once" uses the user account that us currently logged on, where the "Backup Schedule" uses a different account

    In our case our NAS was joined to the domain and we where able to see the permission errors so was very quick fgix, added the domain account that is logged in access to the share and it worked.

    Hope this helps.


    It worked like a charm
    Wednesday, May 17, 2017 2:33 PM
  • Using a NAS without joining it to the domain as I dont want or need the overhead added in, I was able to get this same error fixed by adding the folder destination to "network locations" under My Computer. May also worked with a mapped drive but I prefer network location so as to not make ransomeware easily accessible to drive letters, and saving credentials during that wizard. It now works both scheduled and as a run once.

    You have to have an "admin" local user account created on the server though with backup rights for it to authenticate on the NAS assuming you are using "admin" on the NAS as a user. And both the NAS "admin" and the server "admin" have to have the same password. If the server is a DC you will have to create the "admin" user in active directory users and use same password there as it wont let you create local users.


    • Edited by acadmin18 Tuesday, July 10, 2018 8:15 AM
    Tuesday, July 10, 2018 8:12 AM