Jump to content
fmarkey

Scheduled backup not starting in Windows 7

Recommended Posts

I have used Retrospect Express 7.6 on Windows XPfor a couple of years with no problems, but now I have transferred to Windows 7 and cannot get scheduled backups to run properly.

I am using an extrenal hard disk which is not switched on at all times. If my XP computer was off at the scheduled backup time, the backup was deferred and Retrospect would come up automatically next time I switched on, reminding me to turn on the hard disk. But execution seems to be silent and invisible in Windows 7, and if I do not have the hard disk turned on when backup is due, it is logged in Retrospect as "Execution stopped by operator", although I have not stopped anything knowingly.

Grateful for any help that can get my backups working properly, so that scheduled backups are deferred until computer and external hard disk are both turned on.

Share this post


Link to post
Share on other sites

Retrospect autolaunches under the system account while you are logged in as yourself. Under Windows 7, this prevents you from seeing the interface. You would need to leave Retrospect running and minimized to see what the backup looks like.

Share this post


Link to post
Share on other sites

Also 7.6 express can not properly backup the system state of the machine, if the drive fails or the system crashes you will be able to restore data only. The only version that fully supports windows 7 at the moment is 7.7 professional.

Share this post


Link to post
Share on other sites

Thanks so far - but neither of you have addressed the central issue of why deferred backups are logged as "stopped by operator" instead of being executed (or re-deferred).

Share this post


Link to post
Share on other sites

Stopped by operator means just that, if there is a media request Retrospect will stay open asking for the media until it is told to stop the operation or until it gets the media it is asking for. Unless there is a media request time out set it will stay there indefinitely. Since Retrospect is running in a separate session are you killing the Retrospect process or using the activity monitor to stop the program?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×