Search found 1670 matches
- Tue Apr 09, 2024 1:47 pm
- Forum: Syncovery on Linux, FreeBSD and NAS Devices
- Topic: Syncovery remote service on linux - issues
- Replies: 1
- Views: 100
Re: Syncovery remote service on linux - issues
Hello, what's the name of the folder it created? Concerning the operation, it is usually very reliable. Please visit the remote service configuration page at port 8949. You can see which folders it is active on and also a history of operations. The port is not needed for communication with Syncovery...
- Sun Apr 07, 2024 11:00 am
- Forum: Windows Topics
- Topic: Error creating folder on target
- Replies: 7
- Views: 982
Re: Error creating folder on target
Thanks, I will consider it!
- Sat Apr 06, 2024 8:42 am
- Forum: Windows Topics
- Topic: Error creating folder on target
- Replies: 7
- Views: 982
Re: Error creating folder on target
Hi,
yes that's true, you need a standalone FTP client for that (aka FileZilla).
Syncovery is more like an automation tool. Of course it can delete folders too, if you use an Exact Mirror job from a source to a destination, and the destination contains a folder that the source does not.
yes that's true, you need a standalone FTP client for that (aka FileZilla).
Syncovery is more like an automation tool. Of course it can delete folders too, if you use an Exact Mirror job from a source to a destination, and the destination contains a folder that the source does not.
- Thu Apr 04, 2024 8:37 am
- Forum: Windows Topics
- Topic: Timeout in "Execute before / after"
- Replies: 7
- Views: 172
Re: Timeout in "Execute before / after"
It kills only the process that it started, based on the handle that was returned by Windows when the process was created.
- Wed Apr 03, 2024 11:57 pm
- Forum: Syncovery für Windows
- Topic: [10.13.8] Einstellung für Kompression wird nicht gespeichert
- Replies: 2
- Views: 116
Re: [10.13.8] Einstellung für Kompression wird nicht gespeichert
Das sollte nun in Version 10.13.9 behoben sein.
- Wed Apr 03, 2024 11:56 pm
- Forum: Windows Topics
- Topic: Timeout in "Execute before / after"
- Replies: 7
- Views: 172
Re: Timeout in "Execute before / after"
Hello,
the new version 10.13.9 will now allow long timeouts like
$1800$
You can also let Syncovery kill the exe if it still runs after the timeout. For that, prepend the line with the @ sign:
@$1800$
the new version 10.13.9 will now allow long timeouts like
$1800$
You can also let Syncovery kill the exe if it still runs after the timeout. For that, prepend the line with the @ sign:
@$1800$
- Wed Apr 03, 2024 11:55 pm
- Forum: Syncovery für Windows
- Topic: Access denied
- Replies: 6
- Views: 212
Re: Access denied
Danke! Es ist jetzt in Version 10.13.9 behoben.
Das Problem war wirklich sehr selten und tauchte nur bei der Kombination einiger Einstellungen auf.
Das Problem war wirklich sehr selten und tauchte nur bei der Kombination einiger Einstellungen auf.
- Wed Apr 03, 2024 5:26 pm
- Forum: Syncovery für Windows
- Topic: Access denied
- Replies: 6
- Views: 212
Re: Access denied
Danke, ich werde das testen. Ich müsste noch wissen, ob das Ziel ein lokales Laufwerk ist oder eine Cloud?
Und die Quelle, ist das lokal oder im Netzwerk?
Und die Quelle, ist das lokal oder im Netzwerk?
- Wed Apr 03, 2024 2:37 pm
- Forum: Syncovery für Windows
- Topic: Access denied
- Replies: 6
- Views: 212
Re: Access denied
Hi, vor kurzem wurde ein ähnlicher Fehler behoben, welche Syncovery-Version wurde hier verwendet? Falls es mit der neuesten Version passiert, wäre ich dankbar für eine möglichst vollständige Logdatei, gerne auch per Mail an support@syncovery.com. Das würde die Reproduktion und Behebung des Fehlers v...
- Wed Apr 03, 2024 8:27 am
- Forum: Windows Topics
- Topic: Timeout in "Execute before / after"
- Replies: 7
- Views: 172
Re: Timeout in "Execute before / after"
Hello,
great, I have added the ability to specify a four digit timeout, and also to kill the process if it times out. That kill would happen before the job runs. Alternatively, you can use your own taskkill command in the "after" command line.
great, I have added the ability to specify a four digit timeout, and also to kill the process if it times out. That kill would happen before the job runs. Alternatively, you can use your own taskkill command in the "after" command line.