The support forum

Shadow copying is not supported for clustered file shares (v78.18)

phistrom :

Jan 21, 2018

I have two file servers "fs1" and "fs2" in a failover cluster called "onealfs". I am running Bvckup2 78.18 on a separate server as domain administrator. If I try to require a snapshot for the share at "\\onealfs\Accounting", I get a "Failed to create snapshot of source location" message. All servers involved are running Windows Server 2016 Datacenter.

I can use "diskshadow.exe" to create a snapshot of \\onealfs\Accounting. The required "Microsoft File Server Shadow Copy Agent Service" is running on both cluster nodes.

The following is the output of diskshadow.exe after I took a snapshot of the share myself:

DISKSHADOW> list shadows all

Querying all shadow copies on the computer ...

        * Shadow copy ID = {6be0a30e-8942-4a83-a754-5a54eee087bd}               <No Alias>
                - Shadow copy set: {01426c22-46c5-4b34-ad4f-1abf7587e97f}       <No Alias>
                - Original count of shadow copies = 1
                - Original volume name: \\ONEALFS\ACCOUNTING\ [volume not on this machine]
                - Creation time: 1/20/2018 9:44:05 PM
                - Shadow copy device name: \\FS1\ACCOUNTING@{48608060-1FBB-49B5-9E06-7EF26CC3E728}
                - Originating machine: FS1
                - Service machine: core2016.***.biz
                - Not exposed
                - Provider ID: {89300202-3cec-4981-9171-19f59559e0f2}
                - Attributes:  No_Auto_Release Persistent FileShare

Number of shadow copies listed: 1


I'm going to make a wild guess that perhaps Bvckup2 does not see that while the original volume name is \\onealfs\accounting, the shadow copy device name is \\fs1\Accounting@... and maybe that interrupts it somehow?

phistrom :

Jan 21, 2018

The log output is here:

https://pastebin.com/wr1Fs4j6

Alex Pankratov :

Jan 21, 2018

Can I have a look at your

        %LocalAppData%\Bvckup2\bvckup2-vss.log        or
        %ProgramData%\Bvckup2\bvckup2-vss.log

depending if you are running bvckup2 is desktop or service mode?

On the surface, the log shows VSS rejecting AddToSnapshot request with VSS_E_VOLUME_NOT_SUPPORTED, which means what it says.

phistrom :

Feb 12, 2018

Sorry for the enormous delay in getting back to you. Some things came up and that cluster was destroyed. I've built a new cluster and am still having the same issue. Here are the logs you requested.

bvckup2-vss.log
https://pastebin.com/cy8JY0dy

backup-0003\backup.log
https://pastebin.com/2WXckY6w

The cluster name is onealfs1. There are two servers that are nodes in this cluster. One is named onealfsnode1 and the other is onealfsnode2. If I use the name of the currently active node as the share name instead,  (\\onealfsnode2\E$\a instead of \\onealfs1\E$\a) it still does not work.

I know that shadow copies are being performed on a schedule for this volume because there are folders listed in the "Previous Versions" dialog and in the Failover Cluster Manager, Shadow Copies are enabled for that clustered disk and it is following the schedule I specified.

Failover Cluster Manager GUI
https://i.imgur.com/wq2zcoJ.jpg

phistrom :

Feb 12, 2018

I created a volume shadow copy from a client computer using these instructions:
https://blogs.technet.microsoft.com/clausjor/2012/06/14/vss-for-smb-file-shares/
(it's way down the page where the "DISKSHADOW" part starts.

This is what my command line looked like:
https://pastebin.com/JNNu1eva

Just in case any of that output helps. Thank you for your time.

Alex Pankratov :

Feb 13, 2018

Thanks a bunch. From what I see the recommended request sequence in the Technet article is more or less the same what Bvckup 2 uses.

Can you redo the diskshadow test with "set verbose on" added at the beginning?

phistrom :

Feb 13, 2018

Same diskshadow.exe procedure but with "set verbose on"
https://pastebin.com/Yfh06PGg

Alex Pankratov :

Feb 13, 2018

Thanks.

I think I got it. Stand by for a custom build... :)

New topic

Create
Made by Pipemetrics in Switzerland
Support


Follow
Twitter
Blog / RSS
Miscellanea Press resources
Testimonials
On robocopy
Company
Imprint

Legal Terms
Privacy