Scheduled backup fails with error -1101

[drmrbrewer]

Hi

 

My backup script was all set to run at a certain time, but this failed to happen.  Within the event log, there is a related event that says "Can't access Backup Set XXX, error -1101".

 

This was when I didn't actually have the Retrospect application open... I was testing to see whether it needed to be open, but despite not being open it seems that there *was* an attempt to run the script, but it failed.  There is no problem with the destination drive not being available: it is.  And running the same script manually from within Retrospect works fine.

 

What is likely to be the issue?  I note that when I fire up Retrospect, UAC kicks in each time and asks me to confirm opening the app.  Could that be an issue when Retrospect tries to run a scheduled backup in the background... it tries but fails due to lack of UAC permissions?

 

I see that there may also be a requirement to set the Log On As for the Retrospect Launcher service?  What about the Retrospect Instant Scan and Helper services... those too?

 

I'm on Windows 8, 64 bit.

 

Thanks,

 

Mike

[Scillonian]

Hi

 

The Retrospect error -1101 is "file/directory not found". How is your destination drive connected to the backup server? (eg internal disk, external USB or eSATA, NAS, etc.) Are there any user access restrictions in place on the destination drive?

 

If I remember correctly that under a default setup when the script is run by the Lancher Service it is run under the credentials of the 'SYSTEM' user account and under the credentials of the logged-on user when the Retrospect application is open.

[drmrbrewer]

OK thanks.  I'll see if changing the "Log On As" user for the Retrospect Launcher service will help.  The destination (or perhaps it was the source) is a NAS share, with access rights only to me... I guess that the System user won't have access to the share.

 

http://kb.retrospect.com/articles/en_US/Retrospect_Article/What-causes-error-1101-file-or-folder-not-found-on-an-unattended-backup-of-a-Microsoft-networking-volume/?q=error+-1101&l=en_US&fs=Search&pn=1

 

Update: that seems to do it.  The scheduled backup script launches fine even when Retrospect is not open.

 

I note that there are other Retrospect services.... what about the Retrospect Instant Scan and Helper services... do those need to be logged on as me too?

 

Thanks,

 

Mike

[Scillonian]

Sorry for the late reply. It is only the Launcher service that needs to be run as you so that when it launches the main Retrospect application it has the required access permissions.