Syncovery Support Forum

I have a SmartTracking profile between my computer and Google Drive.

• Left-Hand Side = /data/nacho/docs
• Right-Hand Side = ext://Google Drive/docs/current

For deleted files, I have it configured for both sides to put them in a different folder:

• Left-Hand Side = /home/nacho/syncovery/google drive/docs/deleted (notice the root path is different)
• Right-Hand Side = /docs/deleted (which, according to my understanding, translates to ext://Google Drive/docs/deleted)

So far this is all working great. Now I want to do something similar with file versioning. I want it to move files to different folders depending on the left or right side. This is what I want:

• Left-Hand Side = /home/nacho/syncovery/google drive/docs/older (notice the root path is different)
• Right-Hand Side = /docs/older (which, according to my understanding, translates to ext://Google Drive/docs/older)

But in the Versioning tab it does not let me specify left/right paths. How can I achieve my desired result?

Hello,
by default, the versioning folder is in the base folders.

As an alternative, you can specify a folder relative to the base folders. For example:

../older

Unfortunately completely separate paths are not possible.

What happens if I do multiple levels up using ../, more than the folder level?

So, for example, if I have this:

• Left-Hand Side = /data/nacho/docs
• Right-Hand Side = ext://Google Drive/docs/current

If I set the versioning folder to ../../../../../../../../../../../../../../some/completely/different/path?

• For local file systems, does it go up as far as it can and then go down?
• For cloud accounts, does it go up to the root of the bucket or does it go above the bucket?

And what if the versioning folder starts with / like /some/path -- is that relative to the base folder or does / tell it to go the root? If it says to go to the root, where does it go for cloud accounts -- the bucket or above the bucket?

Hello,
I don't think you should put more ../ things there than would logically work.

But yes you can use an absolute path, starting with a slash.

For Google Drive, it will start at the top of the drive.

For storages with bucket or container names, it will start at the top of the bucket. So you can't have the versioning folder in a different bucket.

tobias wrote: Thu Jul 11, 2024 9:09 pm But yes you can use an absolute path, starting with a slash.

For Google Drive, it will start at the top of the drive.

For storages with bucket or container names, it will start at the top of the bucket. So you can't have the versioning folder in a different bucket.

Perfect. I think I can make this work.

If I have this in the sync profile:

• Left-Hand Side = /data/nacho/docs
• Right-Hand Side = ext://Google Drive/docs/current

And I want old versions to go to:

• Left-Hand Side = /home/nacho/syncovery/google drive/docs/older (notice the root path is different)
• Right-Hand Side = /docs/older (which, according to my understanding, translates to ext://Google Drive/docs/older)

Then if I:

1. Set version folder to /docs/older
2. Create a symlink /docs/older on my server that points to /home/nacho/syncovery/google drive/docs/older

Then:

• The versioning folder in Google Drive will become ext://Google Drive/docs/older
• The versioning folder on my computer will become /docs/older but that really points to /home/nacho/syncovery/google drive/docs/older

This should work great for me. Thank you.

I really love this software. It's fantastic. It's so powerful and flexible and does everything I need/want. As a software dev I am very critical of software because I know how they should work, and what they should do. Very rarely do I find software that does everything exactly how it should. Thank you for developing it! It's well, well, well worth the cost.

Doh!

MOVE ERROR 17, Cannot move across volumes, /data/nacho/apps/fbrowse-tray/test.txt -> /apps/older/fbrowse-tray/test.d20240715-u223642.txt

Oh well. Thanks!

tobias wrote: Thu Jul 11, 2024 9:09 pm Hello,
I don't think you should put more ../ things there than would logically work.

But yes you can use an absolute path, starting with a slash.

For Google Drive, it will start at the top of the drive.

For storages with bucket or container names, it will start at the top of the bucket. So you can't have the versioning folder in a different bucket.

What about for network shares? If the left side is \\server\some\folder, and version folder is \data\here\older, then where will it start?

Just checking?

If left is C:\Users\nacho\Documents and right is \\server\nacho\docs, and versioning folder is \path\to\folder, where does it point to for both left and right?

For left I assume it'll point to C:\path\to\folder, right?

What about for right?

If I map a network share to Z:, then I assume \ points to Z:?