that does not look correct:
- not using the vss snapshot for the source?
- the rclone command needs to go inside
exec.cmd
that does not look correct.
that does not look correct:
exec.cmd
that does not look correct.
What should it be? Can you guess how long it should take to backup 380 GB of pictures? I have one that is running 12 hours +, and it has done the backup before. When I was running with the GUI it didn't take any where near that long. It does 50 GB of docs in about an hour, so it should take 7 to 8 hours to do 380 GB.
exactly as i outlined up above.
https://forum.rclone.org/t/trying-to-embed-the-date-into-the-log-file-windows-11/51284/7?u=asdffdsa
what GUI?
to test the vss snapshot, use a small folder
The rclone gui.
sorry, never used it. it is been labeled experimental since it was first introduced and has not been updated in many years.
in any event, most questions can be answered by reading the rclone debug log.
So which file do I run from the scheduler, vs.cmd or exec.cmd, and how does exec.cmd know to look in vs.cmd for vshadow.exe?
vs.cmd
the other way around.
i think the missing link is the contents of setvars.cmd
note: exec.cmd get %shadow_device_1%
from setvars.cmd
here is an example of setvars.cmd
@echo.
@echo [This script is generated by VSHADOW.EXE for the shadow set {136ab646-dc58-45c3-b704-1db0f70d5fdf}]
@echo.
SET SHADOW_SET_ID={136ab646-dc58-45c3-b704-1db0f70d5fdf}
SET SHADOW_ID_1={9a39e590-169f-4291-bee3-c6b85f98f1d2}
SET SHADOW_DEVICE_1=\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy154
note: SHADOW_SET_ID
can found from vshadow.exe -q
SNAPSHOT ID = {9a39e590-169f-4291-bee3-c6b85f98f1d2} ...
- Shadow copy Set: {136ab646-dc58-45c3-b704-1db0f70d5fdf}
- Original count of shadow copies = 1
- Original Volume name: \\?\Volume{49f7c0ee-485f-4a7f-85be-f5a55b15851a}\ [C:\]
- Creation Time: 5/25/2025 5:29:50 PM
- Shadow copy device name: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy154
- Originating machine: EN10
- Service machine: EN10
- Not Exposed
- Provider id: {b5946137-7b9f-4925-af80-51abd60b20d5}
- Attributes: Auto_Release No_Writers Differential
The latest complication in my debugging I ran vs.cmd with a pause command inserted for debugging purposes and I received a response that
MrSpock
yeah, it is convoluted.
well, windows runs on several types of CPU.
in your case, from rclone version
, your cpu type is amd64
, not arm64
How would I go about updating the cpu version? Would updating that increase the speed that it runs at? It seems to take a while to do 380 GB of pictures, with minimal updating between runs.
find the correct executable for your cpu architecture - os/arch: amd64
no need to install the entire 4GB SDK, no need to run WinSDKSetup.exe
installer.
Windows SDK Desktop Tools x64-x86_en-us.msi
which is just 0.5MB.c:\Program Files (x86)\Windows Kits\10\bin\10.0.26100.0\x64\vshadow.exe
in most cases, the answers are in the debug log.
no idea, what version of rclone, what command, no debug log, no internet speed test, ...
mapped drive? how are you mapping, and why map at all, instead of direct copy to pcloud?
I have two backups thats I use, OneDrive and Pcloud. The PCloud is mapped as a network drive. I would like to map oneDrive as a network drive but have not been able to figure out how to map it as a network drive. I tried microsoft tech support but their response is that OneDrive contents is available already. I had OneDrive mapped to the C Drive but that took up space, so I removed the oneDrive mapping and used the RClone Config to so it would be available to RClone. At least RClone has an option through RClone config.
so you can access rclone mount
drive over the LAN or what?
When I access Pcloud I access it as a network drive, and when I do oneDrive I access it it as a remote drive.
Mike
trying to understand what you need help with?
I know the process for the log file naming, will follow through with that on my own. If I understand how RClone works if I back up the same material to OneDrive it should take approximately the same amount of time to back it up to OneCloud. So now it is fine tuning my process.
One item that I don't understand in looking through the log file a common note I am finding is "Need to transfer - File not found at Destination." I would think that using the copy command should copy it if it is not found on the destination?
Mike
correct. two step process.
i was asking about that, what you meant? what you need?
Would you have any idea how to go about mapping OneDrive as a network drive? This would make accessing the material for general purposes much easier. The changes for doing an rclone backup are insignificant, minor syntax change. If you don't know how to map it as a network drive, then I understand, and I can find out the other questions I have by reading the manual. Thank you for your time.
Mike
this uses windows built-in networking to share the rclone mountpoint.
on the server
set root=b:\rclone
rclone mount remote: %root%\remote
net share share=%root%
on the clients
net use z: \\server\share\remote
I have the backup running reliably every other night, one night to OneDrive, and the next night to PCloud. I started taking a look at the VSS and I am confused about the symbolic link, and the SetVars.cmd
The code:
rem Load the the variables created by vshadow.exe
call setvars.cmd
rem Create the symbolic link to the snapshot (the backslash after shadow_device_1 is important!)
mklink /d c:\snapshot\ %shadow_device_1%\
rem Execute rclone with the source as c:\snapshot\data\, not c:\data\
rclone sync c:\snapshot\data\ remote:data
rem Delete the symbolic link
rmdir c:\snapshot\
Mike