Basic mirroring errors are written to the system log of the Cumulus Server (e.g. when mirroring could not be started.) Errors that occur while mirroring is running are logged as configured in the log4j.xml file, which is found in the conf folder in the Cumulus Server installation folder. Canto recommends you have one log file for all mirroring events and set up email notification for all errors that occur while mirroring.
If the SQL database addressed by mirroring is not available, an error will be logged and the Cumulus Server will try to process the current task again and again. As soon as SQL database is available again, the process is resumed automatically. However, if it cannot be resumed, the size of the task queue will grow with any change performed on the catalog.
TIP: Finding the Short ID of a Field
To find out the IDs of a field you can have them displayed in the list of fields in the Record Fields tab or the Category Fields tab of the Catalog Settings (Edit > Preferences > Catalog Settings).
BACKGROUND INFO: Performance
The performance depends on the SQL database system in use. During normal runtime testing, Canto did not experience performance delays or differences between different SQL database systems. The time needed for the initial process, however, depends on the SQL database in use. The time needed for the initial process is also influenced by the cache size available for the Cumulus Server (can be configured in the Server Console: Remote Admin > Settings > Optimization.)