Syncovery Support Forum

Understood.
With due respect, this seems like a very crazy default. I cannot imagine circumstances under which anyone would ask for everything to be synchronized, then want a result of "all files deleted except a random single file". The same applies to deleting a "percentage of the files". This ...

I am using the commandline to perform a backup operation and noticing some peculiar behavior.....the command line being used is:

"c:\program files\syncovery\syncoverycl.exe" /INI="<MyPath>\Syncovery Profiles\JobBackupProfiles_1.ini" /RUNX="Sam_SingleSourceBackup_Profile_1" /P /M /EXCL=".AppleDouble ...

Testing reveals that this is working as discussed. Thank you again!

Tobias,
The changes you made seems to work as you said.
I am conducting some testing but so far everything looks very good and consistent with the descriptions.
Thank you very much for implementing the additional features!

I will elaborate further:

-When *truly* performing a sync or backup, the option of "create a destination folder" makes sense, as does making all other changes to the file system.

-When performing a "preview only", it is implied that it is a preview, and therefore will make no changes to any file ...

Thank you.
Technically, I suppose it could be argued that it is not truly a 'preview' if if is making changes to the file system of any type.
Is it possible to disable "root check creation" as you suggest from the command line so that the same profile can still be used, or must one profile be used ...

It appears that when using preview mode, the operation still creates a root folder. I.e....
(one argument per line for clarity)

"c:\program files\syncovery\syncoverycl.exe"
/INI="<MyPathToProfiles>\Syncovery Profiles\JobBackupProfile_1.ini"
/RUNX="Sam_SingleSourceBackupProfile"
/PREVIEWONLY
/P
/M ...

Thank you for looking into it.
Would you please reply to this thread or email me directly once that has been completed?

Ideally, I would like to do the following, purely from the command line and without the application gui....

Preview the sync operation with potential changes to the command line and have the application stop.
Then, once the user has verified that the changes to be made are accepatble (by scrolling ...

Understood.
So in summary, if we use INI files they cannot be edited. They can be run using a combination of /INI= and RUNX in a single commandline.
If we use XML, they can be edited, but must be imported in one commandline and RUNX executed in a second commandline.

Is there a flag for the ...