Jump to content

Recommended Posts

We are running Retrospect 11.5.3 on Mac OSX 8.x

 

Everything has always worked fine and I have automatic backups set for two disks, a data disk and a boot disk. The boot disk ran fine until the end of February, then it stopped working.

 

Now, it will not back up at all. I have created new scripts, tried every kind of manual backup, created new media sets to start from scratch--nothing works. The data disk still backs up fine, as usual, on a scheduled script. The boot disk backup just stops right after it is started. There are no error messages. The past backup window states that it was "stopped," no further log entrees. 

 

The computer is fine, no problems at all with it. Very clean and fast running.I have excluded Retrospect and its client from Norton Firewall in case there was interference, but to  no avail.

 

1. How do I find out what is wrong?

 

2. How do I get the disk to back up?

 

 

And a third unrelated question, why don't you add a search function to the forum? There may be an answer in here somewhere, but there is no way to find it.

 

I hope you can help.

 

Thanks.

 

- Michael

  • Like 2

Share this post


Link to post
Share on other sites

I would try to disable/uninstall Norton and see if that works.

For search, try the search window on top of the retrospect page once your in the forum.

Share this post


Link to post
Share on other sites

More information is helpful if the lurkers on this forum are to be helpful.

 

Have you run a check on the disk using Disk Utility to make sure the filesystem is OK?

 

Have you posted the text of the log of the "stuck" operation?

 

When you say the "data backs up fine", but the boot disk "just stops"… what does that mean, exactly. Do you get the spinning pizza and the machine freezes, or does the backup operation stop making progress once it starts on the boot disk? What phase of the backup is it in when it stops making progress?

 

What have you done to "free up" that process? If you stop the "stuck' backup with the stop button from the console, does it stop, or do you have to restart the machine?

 

Are you patient enough? Sometimes the scan phase can take a while (minutes+) Is it actually doing its job, but you're not giving it enough time?

 

Many questions to be answered. This could be operator error, or a bad disk, or a Retro bug, but I'm betting one of the first two. More information would help to pinpoint your problem. Post more precise information about what hangs and how, and then add logs and screenshots for starters.

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

×