I've created a job to backup a folder on a Windows 2019 Server I have at home. The folder is \\Servername\Financials. The backup job finds the folder and backups up the files as expected. When I create a scheduled job to run at 2 AM each day the scheduled job returns an error that the folder "\\Servername]Financials" cannot be found. 

How can the backup job work but the scheduled job not? I'm confused.

Backups executed manually run in your user session under your user credentials, and therefore they have access to network resources that your user account automatically has access to, as well as any other authenticated network connections opened within that user session.  Backups that run as scheduled tasks by default run under the SYSTEM account, and therefore do not have access to resources that your user account might have access to, and also would not have access to any other network connections you may have opened within your user session.  Even if you set scheduled backups to run under your user account to address the former scenario, scheduled backups still wouldn't have access to other network connections opened in your user session. To address this, you need to add the network path of your backups as well as valid credentials for that path to Reflect.  To do that, go to Edit Default > Network and provide the necessary information.  Scheduled backups will have access to those stored credentials.  Or if your regular user account has "implicit" access to the target folder and is an admin on your system, you can instead configure scheduled backups to run under your own user account under Edit Defaults > Schedule.  It depends on how you authenticate to that network target folder.

Probably because the job you ran interactively ran under your credentials, whereas I'm guessing you're running the scheduled job as the local System account, which doesn't have access to the server.    Go to the Defaults Tab and enter an appropriate system\username and password for Reflect to use to connect to the server.

+x

 

L. W. "Dan" Danz - 24 March 2021 3:40 PM

Probably because the job you ran interactively ran under your credentials, whereas I'm guessing you're running the scheduled job as the local System account, which doesn't have access to the server.    Go to the Defaults Tab and enter an appropriate system\username and password for Reflect to use to connect to the server.

I have a similar problem.
The backups on a Windows 10 PC were being written to a NAS server using scheduled backups.
This was working without any issues UNTILL the latest version of Reflect 7 Home Edition was applied.
The latest version is build 5758.
Now, it will not connect to the NAS server saying that the user is not found.
All that was changed is the upgrade, nothing else was change.

Is the a way to rollback tothe previous version?

I have just re-installed v5321 and connection to the NAS works again.

There's nothing in the Reflect V7 release notes (link) from 5321 to 5758 that sounds like it would cause NAS connectivity issues.  Did you try deleting and recreating the stored credential under Edit Defaults > Network before rolling back?  Did you try anything else?

Reflect does not have an easy rollback mechanism.  Macrium has provided installers for older releases upon request, and of course if you already have a copy of an older installer stashed away, you can use that, but typically only the latest release is available, and there's no rollback mechanism built into the application.

+x

 

jphughan - 29 March 2021 2:17 AM

There's nothing in the Reflect V7 release notes (link) from 5321 to 5758 that sounds like it would cause NAS connectivity issues.  Did you try deleting and recreating the stored credential under Edit Defaults > Network before rolling back?  Did you try anything else?

Reflect does not have an easy rollback mechanism.  Macrium has provided installers for older releases upon request, and of course if you already have a copy of an older installer stashed away, you can use that, but typically only the latest release is available, and there's no rollback mechanism built into the application.

Hi,
As mentioned, I removed the latest version and re-installed the version from when I purchased the product.

Yes, I went through that credential procedure.
It has always worked with the various updates but this latest one failed.

I have raised a Support ticket.

I will try the upgrade again to see if it was just a glitch or not.

Yes, I saw the mention that you had rolled back.  But you didn't specify what if any troubleshooting you attempted before that, and experience has taught me not to assume that all people consistently provide all relevant information upfront.  So I just asked about any troubleshooting steps you performed -- which it turned out included at least some -- while mentioning the contents of the release notes and the general information about rollbacks.

+x

 

jphughan - 29 March 2021 2:33 AM

Yes, I saw the mention that you had rolled back.  But you didn't specify what if any troubleshooting you attempted before that, and experience has taught me not to assume that all people consistently provide all relevant information upfront.  So I just asked about any troubleshooting steps you performed -- which it turned out included at least some -- while mentioning the contents of the release notes and the general information about rollbacks.

I understand, I should have been more descriptive.
But this time it worked after the upgrade.
So now I am happy again.

Thanks for the kick in the head. I knew about the credentials but completely forgot about it. :-)