|
Group: Forum Members
Posts: 12K,
Visits: 72K
|
Go to Edit Defaults and Settings > Network and make sure you’ve got suitable credentials stored. If you run a backup definition file manually, Reflect will be running in your user session and will therefore be able to piggyback on any authenticated network connections that are already open in your user session, so Reflect doesn’t even need to have stored credentials in that case. A scheduled backup runs as a background scheduled task in a separate context, and as such does not have access to your own user session’s open network connections. This hasn’t changed since V7. That’s just how Windows works. And that’s why Reflect offers that mechanism for storing network credentials.
There is one workaround, which is to run scheduled backups as a user account that has “implicit” access to the network target. (It also has to have admin access on the system where Reflect is installed.) In that case, you don’t have to store credentials in Reflect because the account itself is already granted the necessary access, but that’s more commonly found in Active Directory environments that use centralized user accounts for a larger environment. But Reflect V7 defaults to running scheduled backups as the SYSTEM account, which does not have any implicit access to network resources.
|