This article contains explanations for the various status messages that can be displayed in Detailed or Enterprise Status in SureSync MFT.
Initializing Hub Service...
The Hub service is in the process of starting and no jobs are being processed yet.
Initializing Job...
The job or a Root Path is initializing or being refreshed.
Job is Disabled
The job is fully disabled and will not process any actions, scan, for changes.
File Actions Blocked by Job
The job is partially disabled, allowing scans and changes to be processed, but actions will not be executed. This updates the database with the current status of files but does not execute any actions to synchronize the files until you fully enable the job.
Job is between intervals. Actions and scans suspended.
The job uses intervals and is currently in a gap between intervals. The job allows scans and changes to be processed, but actions will not be executed. This updates the database with the current status of files but does not execute any actions to synchronize the files until the next interval starts.
Disabled Machines:
If machines used by your job are disabled, they will be listed in this message. No scans, changes, or actions will be processed for the machine until it is enabled.
Unlicensed Machines:
Any machine that lacks an activated product license and referenced by the job will be listed in this message. No scans, changes, or actions will be processed for the machine until licenses have been updated.
Disabled Root Paths:
If root paths used by your job are disabled, they will be listed in this message. No scans, changes, or actions will be processed for the root paths until they are enabled.
Thinning archive.
If your job performs any archiving, this message may be reported to indicate that a background process is thinning the archive to remove obsolete entries. This is simply to make you aware of the automatic background activity. This usually only runs with the job would otherwise be idle and the Hub has low activity.
Initializing: [volume list]
The job is in the process of collecting to the volume listed. No scanning or actions can be performed on these volumes until this initialization is complete.
Initializing Roots:
The job is in the process of connecting to these root paths and preparing them for processing. No scanning or actions can be performed on these Root Paths until this initialization is complete.
Initializing x Roots.
If more than 2 root paths are in the process of initializing, this message displays. The job is in the process of connecting to these root paths and preparing them for processing. No scanning or actions can be performed on these Root Paths until this initialization is complete.
Unexpected volume changes:
This reports that the volume serial number on a volume changed and the volume has been taken offline. This normally would only be reported for an external drive that changed while a job was running.
Actions Blocked:
This lists root paths that are partially enabled, allowing scans and changes, but where actions are not started. When the Root Paths are fully enabled, delayed actions will start.
The Schedule is Held
The job is associated with a schedule that has been held. The job will not start any scans, monitor changes, or perform any actions. You must manually remote the Hold status from the job or manually start the job for it to run.
Waiting for the next scheduled start time of x
The job uses a schedule and is waiting for its next scheduled start time. The job will not start any scans or perform any actions, however journal monitoring will be active. This allows actions to be computed so they can immediately start when the schedule is started again.
x Roots are waiting for their schedule to start and xx are between Intervals
This message displays if you have Root Paths that are on Schedules or Intervals and are not currently running. Each root will start it processing of scans and actions when the next schedule or interval starts. Changes are processed and actions are queued while waiting.
x Roots have Schedules that are Held
This indicates that one or more Root Paths used by the job use a Schedule and that schedule is Held. The root path cannot process scans, changes, or actions until the Hold state is removed from the Root Path.
x Roots are between Intervals
This indicates that one or more Root Paths used by the job use Intervals and no interval is currently active. The root paths cannot process scans, or actions until the next interval is started. File changes will be processed and actions will be computed while in this state.
Offline Volumes:
This lists any volumes referenced by the job that cannot be accessed. No scans, changes, or actions can be processed for the volume.
Background database thinning is active.
This message may appear when the Hub service is mostly idle to alert you that a background process is running to remove obsolete history from the database. No user action is necessary.
Background cleanup of deleted root paths is active.
A root path has been deleted or had its path changed. This message indicates that a background task is removing obsolete history from the database.
Background thinning of logs is active.
This message appears where the system is busy removing obsolete job log records from the database. No user action is needed.
[Scan Reason]
If a scan is active, this message may report why the scan is occurring. There are numerous reasons. Many folder scans will display the folders being scanned without adding any special message.
x folder loads active.
This message is added to a folder scan message to report how many folder reads are active on agents. Scan requests are sent to agents to read the contents of a folder. The agent returns a list of the folder contents, which can take a few seconds for large or very remote servers.
Processing x of y folder records.
When scanning, this may report a backlog of folder data received from agents that has not been fully processed. Each data item for a file must be compared with the database value to detect any change. When there is a heavy load on the system, this message can be displayed to let you know it is busy processing the changes. New folder data can arrive before the current queue is emptied, so both numbers in the message might change on each refresh of the display.
Processing x of y changes from state scans
State Scans are generated after a folder scan has completed. It compares the file states stored in the database and computes any needed actions. This message report how many state records are waiting for compares against the number of records loaded from the database. Both number usually change quickly and independently.
Processing file changes from state scans
File state data is being processed, comparing the file states for files and computing actions.
Draining journal
The job is processing change journal entries and updating the database with current file states. When this message is displayed, the job has not caught up with the current journal position. Scans and actions are delayed until the initial reading of journal entries has been processed.
Processing x file changes
Where there is a large backlog of journal changes to process, this message is displayed with the current count of pending changes that need to be compared against their database values.
Processing file changes
When there is a small backlog of journal changes to process, this message is displayed to indicate that changes are being compared against their database values.
Folder scan is waiting on a State Scan
Folder scans and State scans need to coordinate their executions to avoid unnecessary processing. This message indicates that the next folder scan for the job is waiting because a State scan is active that conflicts with the folder scan. The folder scan will start automatically when the blocking scan completes.
Folder scan is waiting on a Folder Scan in another job
The database does not hold duplicate data. A folder scan updates data for a path, but that path may be shared with multiple jobs. This message indicates that a folder scan executing in another job is blocking a folder scan in the current job. The blocked scan will start automatically when the blocking scan completes.
Folder scan is waiting on an Action
An action is busy in the job that conflicts with the next folder scan queued for processing. The folder scan will start automatically when the blocking action completes.
Waiting on a folder rename or delete
Processing is being delayed while waiting for a folder rename or a folder delete to finish process. Folder renames and deletes can alter many records in the database. Other actions that might be affected must pause until the rename or delete completes.
State scan is waiting on a folder scan
When a state scan is queued to process the same folder as a folder scan, the State scan may be required to wait for the folder scan to complete.
Waiting on an inactive state scan
A state scan is being blocked by another State scan that is not currently executing. The blocking State scan is likely waiting on another blocking action or scan. The blocking scan will eventually be executed, allowing other scans to run.
Waiting on x renames
A number of rename events have been received and are being processing. Actions and scans are suspended until the job can determine what actions and scans might be affected by the pending rename actions.
Updating history for deleted folders
When a folder is deleted, history for all items in the folder and subfolder must be updated. If this is in a large folder structure, the process of updating the database could take minutes. This message lets you know that processing of new actions has been suspected for the job until the database has been brought current.
Updating history for renamed folders
When a folder is renamed, history for all items in the folder and subfolder must be updated. If this is in a large folder structure, the process of updating the database could take minutes. This message lets you know that processing of new actions has been suspected for the job until the database has been brought current.
Waiting for file changes
The job is idle and waiting for any changes from the change journals it is monitoring.
Scan maintenance may delay scans
A new scan has triggered the removal of duplicate scans. New scans may be delayed while this message is displayed.