extern/rclone
1
0
Fork 0
mirror of https://github.com/rclone/rclone.git synced 2025-08-07 21:18:43 +02:00
Code Issues Packages Projects Releases Wiki Activity

Updated How to enable VSS for rclone (markdown)

asdffdsa6131
2019-09-08 10:20:01 -04:00
parent 72805f7437
commit 6f897430f6
1 changed files with 24 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files

49
How-to-enable-VSS-for-rclone.md

@ -10,39 +10,38 @@ If Veeam backup software would run again while rclone is still uploading, Veeam
So I create a VSS read-only point-in-time snapshot and have rclone use that as the source. So I create a VSS read-only point-in-time snapshot and have rclone use that as the source.
Now rclone can takes its time, upload, sync, check or whatever and not be concerned that the data will be modified. Now rclone can takes its time, upload, sync, check or whatever and not be concerned that the data will be modified.
Yeah, you want that, you know you need that, and you can have it with 3 lines of code. Yeah, you want that, you know you need that, and you can have it with a few lines of code.
Let's say that I want to sync c:\data\ to the cloud.
The following example is the bare minimum, just enough code to create a snapshot but not useful yet. 1 - Create a file named vs.cmd:
1 - Create a file named vs.cmd, with 1 line of code.
vshadow.exe -nw -script=setvar-vshadow.cmd -exec=exec.cmd c: vshadow.exe -nw -script=setvar-vshadow.cmd -exec=exec.cmd c:
2 - Create a file named exec.cmd file with 2 lines of code. 2 - Create a file named exec.cmd file:
call setvar-vshadow.cmd call setvar-vshadow.cmd
mklink /d c:\snapshot\ %shadow_device_1%\ mklink /d c:\snapshot\ %shadow_device_1%\
rclone sync c:\snapshot\data\ dest:data
rmdir c:\snapshot\ /q
Execute vs.cmd and that is all it takes to create a shadow mount. Execute vs.cmd and that is all it takes to create a shadow mount.
When vs.cmd is run, it will execute vshadow.exe. When vs.cmd is run, it will execute vshadow.exe.
vshadow.exe will do two things: vshadow.exe will:
1. Create a file named setvar-vshadow.cmd will some variables that needs to be passed to exec.cmd 1. Create a file named setvar-vshadow.cmd will some variables that needs to be passed to exec.cmd.
2. Execute exec.cmd 2. Create the snapshot.
3. Execute exec.cmd.
exec.cmd will do two things: exec.cmd will:
1. Call setvar-vshadow.cmd 1. Call setvar-vshadow.cmd, to load the variiables created by vshadow.exe.
2. Create a temporary shadow mount point. To be clear the shadow point will only exist will exec.cmd is running. When exec.cmd is done running, that mount point is no longer valid. 2. Create a symbolc link to the snapshot.
3. Run rclone with the source as c:\snapshot\data\, not c:\data\.
4. Delete the symbolc link.
Note that:
1. c:\snapshot is read-only, trying to delete a file will generate an error.
2. All the files are readable, you will not get errors about in-use or locked files.
3. c:\snapshot is a temporaty link only accessible while exec.cmd is running. when exec.cmd exits, the link is removed by Windows operating system.
To make it useful for rclone, change exec.cmd to the 4 lines of code below and then execute vs.cmd. I find it confusing, that c:\snapshot\ is a mirror image of c:\; when writing more complex scripts, this confusion was leading to errors.
call setvar-vshadow.cmd
mklink /d c:\snapshot\ %shadow_device_1%\
rclone sync c:\snapshot\ dest:snapshot
rmdir c:\snapshot\ /q
I find it confusing, that c:\snapshot\ is a mirror image of c:\.
I found that when writing more complex scripts, this confusion was leading to errors.
So I will give you 3 workarounds for clear code for exec.cmd. So I will give you 3 workarounds for clear code for exec.cmd.
--- Use SUBST command. --- Use SUBST command.
@ -50,8 +49,8 @@ So I will give you 3 workarounds for clear code for exec.cmd.
call setvar-vshadow.cmd call setvar-vshadow.cmd
mklink /d c:\snapshot\ %shadow_device_1%\ mklink /d c:\snapshot\ %shadow_device_1%\
subst t: c:\ subst t: c:\
rclone sync t:\snapshot\ dest:snapshot rclone sync t:\snapshot\data\ dest:data
subst t: /delete subst t: /d
rmdir c:\snapshot\ /q rmdir c:\snapshot\ /q
--- Use NET USE command --- Use NET USE command
@ -59,7 +58,7 @@ So I will give you 3 workarounds for clear code for exec.cmd.
call setvar-vshadow.cmd call setvar-vshadow.cmd
mklink /d c:\snapshot\ %shadow_device_1%\ mklink /d c:\snapshot\ %shadow_device_1%\
net share snapshot=c:\ net share snapshot=c:\
rclone sync \\localhost\snapshot\ dest:snapshot rclone sync \\localhost\snapshot\data\ dest:data
net share snapshot /delete net share snapshot /delete
rmdir c:\snapshot\ /q rmdir c:\snapshot\ /q
@ -69,7 +68,7 @@ Most Windows computer hard drives will not have free space to create a new drive
call setvar-vshadow.cmd call setvar-vshadow.cmd
mklink /d b:\snapshot\ %shadow_device_1%\ mklink /d b:\snapshot\ %shadow_device_1%\
rclone sync b:\snapshot\ dest:snapshot rclone sync b:\snapshot\data\ dest:data
rmdir b:\snapshot\ /q rmdir b:\snapshot\ /q
Good luck and if you have any questions or comments, please do not hesitate to contact me. Good luck and if you have any questions or comments, please do not hesitate to contact me.