At this point it will move the information from memory to an internal database (generally stored on the local drive) and use that. It will use memory (RAM) to store file information until memory runs low or the number of files approaches 200,000. SyncBackPro, however, is not limited by the amount of free memory (*). The following article has details on the memory usage of SyncBackSE: Modified on: Mon, 28 Nov, 2022 at 2:55 PMįor SyncBackSE/ Free the maximum number of files depends upon the amount of free memory (RAM) available (and also the amount of memory fragmentation). See this article for more details how to do this, and also to change the logging settings (highly recommended).Solution home Technical Articles Common Questions and Solutions The maximum number of files for a profile SyncBack V8 (or newer) introduced the ability to store your profiles settings in a path you choose. On Windows Vista and newer, a regular user will not have write access to the installation folder. The users must have write access to the folder SyncBack is installed in, typically a folder in Program Files. In SyncBackPro/SE* you can share profiles between all users if the profile is stored in the same folder as SyncBack itself. The location SyncBack will look in for profiles when the Scheduler calls it is dictated by which user is running SyncBack, so if you change the credentials in a Scheduled Task, the Task will run as 'him', as will SyncBack, and SyncBack will thus look in 'his' location for the named profile instead, which may not exist there. Profiles are by default user-specific, as they are stored in user-specific locations by user-name (for security reasons). I cannot get SyncBack to run under another users account, e.g.

Modified on: Thu, 30 May, 2019 at 3:11 PM Solution home Technical Articles Task Scheduler SyncBack will not run with Scheduler

Syncbackpro v8