Sync won’t work correctly if the external drive becomes inaccessible or disconnected. Your external drive should be permanently attached, as the Sync folder must be available before the Sync app starts. Moving to an external drive: You can move your Sync folder to a USB attached external drive to free up space on your internal drive and/or provide more storage space for the Sync folder. For example, you could move the Sync folder to your Desktop. Moving to the same internal hard drive: Moving the Sync folder to a new location on the same internal hard drive can make your files in Sync easier for you to access. You can move your Sync folder to a new location on your computer, onto an external drive connected to your computer, or to a new computer. Seeing an Agent perform this or that operation help better understand what's going on under the hood and evaluate whether or not the job indeed stuck.įor example, in setup with disabled p2p and only one central server, all other Agents will be discovering files' difference between each other only though the central server, which is expected to be slow.Moving your Sync folder to a new location Look into the Agent's activity tab and see if it's busy reading, hashing the files, or merging folder tree. For pre-seeded folders, the Agent shall merge folder tree. Agents are busy with some other operations on filesīefore transferring files over the network to other Agents, the Agent shall read the files from dis and hash them. decrease folder rescan interval in the Agent profile. increase system notification watchers (see the guide linked above). Perhaps the file system does not support file notifications or the Agent ran out to notify watchers. If these don't sync right after being updated or added to the job folder, most likely the Agent was not notified about them. It refers to file updates or newly added files. If neither of the tips helps, please collect logs from agents and Management Console, and send them to support. See here for more details on job priority. If there's a job with higher priority and its being synced, this one will be waiting for its turn. To fix this problem, make sure that in the Profile assigned to this agent's group the "Overwrite any changed files" option is set to YES. Since this is a read-only share, the updated file will not be uploaded. If a non-synced agent has Read-Only permissions in the job, syncing will stop if a file gets updated on it. Files are currently being in useĬlose all apps that might be keeping the file and preventing other apps from accessing it. Run the command with minimal time lag to get more accurate results for comparing. Windows in Command Prompt: for /f %x in ('wmic path win32_utctime get /format:list ^| findstr "="') do set %x.Check UTC time on all agents and compare results: Time difference between agents is more than 600 secondsĪgents may be located in different timezones so they rely on UTC timestamps - this must be the same on all agents. In job's details check which folders is set up for this agent. Same for destination agents.Ĭheck system permissions and make sure that on this computer the agent has read-write access to the files and all parenting folders. If you see zero files there, agent may be lacking write access in the system, or the job is misconfigured and wrong directory is being used. On source agent(s) check that it indexed the files - see column "Files count" in job details.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |