Contents
- Previous
- Next
Profile Settings - File Access
Dabase-Safe Copying: Enforce Exclusive Access
The database-safe mode makes sure that no other application can have a file open with write access while it is being copied. If an application is currently working with the file, the program will try to use volume shadowing, or it can be set up to wait until the file is free. If volume shadowing is not used while it is being copied, an application trying to access the file in read/write mode will fail and issue an error message. As soon as the copying is finished, the file can be used nomally again.
Prior to copying, verify that all files can be copied by opening them
This setting is rarely used. It ensures (as much as possible) that the copying is only done if all files can actually be copied. That way, you will either get all files copied successfully, or none. To make this possible, a separate step (checking all files) is added before the actual copying starts. If any file is not accessible on the source side or is not writeable on the destination, then the profile will be stopped. Usually this setting is used when profiles are run via scheduler, so that another attempt to copy the files will be made at the next scheduled time.
Ignore These Errors:
Some types of errors can be ignored, because they are bound to occur regularly and are not significant. By ignoring these errors, you can avoid emails and result summaries that contain errors. Use only if you need to ignore repeated error conditions. An example of an error that occurs frequently is "Files That No Longer Exist". This can occur if a file is deleted by somebody after Syncovery has built the file list, and before it starts to copy the file.
See also:
Upper Part Of Dialog Box
Advanced Settings