Can't use network folder as source

[Daniel English]

The following works greatly because the source (C:\foo) is a local folder.

shadowspawn C:\foo X: robocopy X:\ C:\path\to\backup /mir

However, when I specify the source as a network path, shadowspawn fails with the error "There was a COM failture 0x80042308 - ShadowSpawn.cpp (301)"

shadowspawn \\RemoteServer1\foo X: robocopy X:\ \\RemoteServer2\backup /mir

I tried to map \\RemoteServer1\foo as a network drive and assign it a drive letter Y, and run:

shadowspawn Y:\ X: robocopy X:\ \\RemoteServer2\backup /mir

It still failed.

Are there any workarounds for specifying source as a network path?

Thank you very much!

[Craig Andera]

Hi Daniel. Using a network folder as a source is not possible due to
limitations of the Volume Shadow Service, the Windows feature that
shadowspawn makes use of. The only "workaround" is to run shadowspawn
on the remote machine.

Using a remote folder as a destination is supported.

> --
> You received this message because you are subscribed to the Google Groups
> "ShadowSpawn Support" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to shadowspawn-to...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Daniel English]

Hi Craig,

Thank you for the reply.

Anyway, thanks so much for creating such an awesome tool! It's so powerful and convenient.

 

Craig Andera於 2016年6月27日星期一 UTC+8上午10時51分12秒寫道：

[Saood Usmani]

Hi Craig Andera,

I'm facing a similar issue as Daniel English above. Can you please provide details on how I can use a remote server?

I would like to copy locked files from Server A to Server B. Everytime I run the ShadowSpawn command on Server A or Server B I get the following:

"There was a COM failture 0x80042308 - ShadowSpawn.cpp (301)"

Thank you,
-Saood

------------------------------

[Craig Andera]

How are you running it? If you try to use a network drive as a source,
it will fail. You will need to run shadowspawn on the remote machine
somehow, like with whatever the Windows equivalent of ssh is.

[Saood Usmani]

Thank you Craig for the quick reply!

This is what I'm doing:

- Running ShadowSpawn on Server A (On-Perm) F: drive
- Trying to Copy 1 locked files (mail.txt) to

- Server B (On AWS Cloud) J: drive

So I guess I'm using ShadowSpawn on a server drive. I also tried a 3rd machine (Server C) to move the same files from Server A to Server B, still no luck. Tested both option with simple mail.txt file:

> email to shadowspawn-tool+unsubscribe@googlegroups.com.

[Craig Andera]

Yeah, you can't do that. That first argument must be a local path. So you'd have to somehow run shadowspawn on ms240mf01q.na.sysco.net. This is a limitation of the Windows Volume Shadow Service.

[Saood Usmani]

Thanks Craig!

So if I run the first copy leg locally...what do I do next to move the locked file over to the other server?

-Saood

---------------------------------------------

[Craig Andera]

Let's say you have a locked file on machine A. You go to machine A and run "shadowspawn C:\path\somewhere Q: robocopy Q:\locked-file.foo \\serverB\share\path\to\wherever" and now there will be a copy of locked-file.foo at \\serverB\share\path\to\wherever.

But I'm not totally sure I understand your question.

Shadowspawn makes a "shadow copy" of a *local* disk and mounts it on a drive letter, which is essentially an unlocked view of some folder on your machine. Then it runs a command that can do whatever it wants with that view.