I need help creating versioning with crypt to dated folders

Howto Guides
103

  1. the log file should be a local drive, perhaps a network drive but not a cloud bucket.
    like so set "logfilepath=c:\rclone\logfiles"

  2. you need to use the --dry-run flag.
    only after the script completes and that there are no errors in the log, then you can remove the flag

1 Like
104

Sure I can update it, but are you sure that is a mistake?
I have been using that format since forever and never had an issue with it. I think if that was incorrect I would have noticed a long time ago. I am pretty sure = is optional for all flag parameters.

@Charles_Hayes It's easy to test though. Care to make the change and see if that does anything different? I don't see why it would, but apparently asdffdsa is seeing something I am not...
There is definitely a simple syntax error here somewhere, but I'm not sure that I see where honestly.
If we find the problem I will update the script of course.

105

as i wrote it is not the cause of the error, but never mind , pretend that i did not write that.

106

Ah ok, re-read and understand now.
I suppose it would be better practice overall to follow that format. The less superfluous spaces in code the better.

But what the heck is causing it to not see the source/dest parameters here? I don't see much obvious...
Could it have something to do with an extra " in the source? I do not see where in the code that would originate from though...

107

the OP is trying to store the logfile in the cloud instead of local storage.
and you do have the line if not exist "%logfilepath%\" mkdir "%logfilepath%"
which will generate an error

108

@Charles_Hayes Hang on a minute... what is "W" in this context? Is it perhance a mounted drive?
Because I see you are running the cmd in elevated mode. This may cause it to be unable to see a drive that was mounted from a non-elevated rclone.

109

Well, true that - but I don't see why this would generate a "you need 2 non flag parameters" error. That can AFAIK only come from incorrect syntax. Can't say I've tried to provoke an error by setting a logfile to a non-extant folder, but it seems like it would be a weird error type to get from that problem.

But logfile should probably be local yea, for many reasons.

110
  1. OP needs to change the log detail from INFO to DEBUG.
  2. OP needs to fix the logfile issue i mentioned and re-run the script to see what happens.
  3. then if there are other errors, we can deal with them.
111

the word spesific should be specific
"image "

112

added for next update. Wanna see if there is more we need to correct tho.

113

agreed,
at some point, you should create a wiki page for it.

1 Like
114

That explains why it saved locally, before, but not in the cloud. I'll change that part.

115

One other thing I had a "weird" issue with.
Can we force the program to save "empty" directories?
I had an issue where 19,879 directories were skipped, due to them being empty.
My friend uses a "template" when he works on jobs, like directories, that might remain empty, during the project, like say, 100 sketch, 200 pdf, 300 2d Rendering, 400 3D rendering, etc.
These folders aka directories, are being skipped, and probably rightfully so, due to them being empty, but when you open up a directory and only 2 or 3 folders, of say 10 show up, people start leaving skid marks in their skivvies.
I spent an hour, using free file sync, to copy close to 20k empty folders, to appease his adhd.

116

I pointed the logfiles to a local location on the c: drive, saved, ran the program, and thus far, no issues.
The only thing I'd like to figure out, is how to copy "empty" directories, per my previous post. It's not a huge deal, but it would save me from having some skid marks in my underoos, thinking something got corrupted during the backup.

117

W: is actually a Synology file share / mounted drive.
I have a link on my desktop to the command prompt, that has the run as admin option, because I'm lazy.
I'll run the program from a regular command prompt.

118

Try to do that.. because in windows it is a known issue that mounted drive mounted in user-space is not visible to SYSTEM account (which is effectively what is used when you run elevated admin).

The reverse works though (mounting in SYSTEM and viewing though any user).

Or mount as user, and view as user (any user I think).
You can simply check if this works in elevated CMD:
cd W:
if it tells you that doesn't exist then that is the issue we are looking at.

119

assuming that you are correct, you have raised a good point, about empty directories.
rclone should copy source to dest, as is.
perhaps you are mistaken, perhaps i am confused
but if true, rclone might a huge bug!

120

You need to use:

      --create-empty-src-dirs   Create empty source dirs on destination after sync

If you want empty directories created.

1 Like
121

yes, just add that to your flags in the settings and you should be good.
It's not default behavior, but I'm honestly not quite sure why. I also generally prefer it on.

1 Like
122

Thanks, to you and to everyone who has contributed to this little thread and this cool bit of code.
It seems to just be evolving into something much better than originally hoped for on my part, and that's a great thing.
Next thing you know, someone will come along with a visual interface, where you just type in your variables, and it will generate the batch file in the background, per your variables, saves it, and then creates a windows scheduled task, per your input, and poof, you're done.