Exact Mirror with large files

[bmcgin1]

I have Syncovery set to do an Exact Mirror with Real Time Sync checked. The left side is where I backup a database. The right side is amazon s3.

As the database is creating a backup file, I notice that Syncovery will start to copy the file before the database is finished creating the file. So if the db has created 100M of the file, this get copied. Then a few moments later, the db has added another 300M to the file so Syncovery then sends 400M to AWS. Then when the file is 1G, Syncovery copies 1G of data.

How to I ask Syncovery to wait until the file has been fully created before copying?

[superflexible]

On the File Access tab sheet, please turn off Volume Shadowing, and choose "Database-safe mode".

[bmcgin]

When this is enabled, it works great. Syncovery waits until the file is completely created before copying. The only problem is I get an email every few seconds saying:

Short Results: INCOMPLETE: 0 copied of 1
Detailed Results
-----------------------
Errors with 1 File(s).

Errors / Access problems with :

C:\_xxx.file (32:The process cannot access the file because it is being used by another process.)

When the database safe is enabled, this is technically not an error as it is what I am asking it to do. Is there a setting which will cure this?

[descargasOPS]

I have the same problem when I try to move a huge file and I am interesting in avoid the message (32:The process cannot access the file because it is being used by another process).

Like a idea: Can I change the name of the file temporarily adding a suffix (.tmp for example) till the file is ready? During this time I will have a mask for *.tmp files for not to be moved.

[superflexible]

You could increase the "Wait Up To" time in the profile under "Access & Retries" -> "Waiting and Retrying", so that the job as a whole succeeds because it waits long enough until the file is ready.