Jump to content

Recommended Posts

Hi there,

 

Last night all our back ups suddenly stopped, there is a flashing question mark and an error saying waiting for media. The back up thunderbolt drive is connected and visible by retrospect. When you click on the media set it just says busy.

 

The back up is just mirroring another thunderbolt raid attached to the server.

 

Back up drive has 924GB free still.

 

Running of mac mini server running 10.9.2

 

We have restarted the machine and the back up server and still get the same error.

 

Ideas?

post-81208-0-91556000-1393843662_thumb.png

Share this post


Link to post
Share on other sites

We've had the same thing happen here multiple times. The only way to fix has been to rebuild the media set. Retrospect support has been no assistance so far.

 

Anyone else seen this and/or found an easier way to fix? Very frustrating!

 

- John

Share this post


Link to post
Share on other sites

Check disk permissions on Finder level and via the terminal.

I had moved a disk backup set to another drive using a Finder copy and I got the same "waiting for media" error.

After manually setting the ownership of the files via the terminal and setting file ownership in the Finder I was able to get rid of the error.

 

Maybe this info can help in your situation.

Share this post


Link to post
Share on other sites

But I made no changes to disk permissions or anything between the backups working and not working.

 

The fact these steps fixed the problem also point to an issue with Retrospect, not file permissions:

 

1. Media Sets->Choose your media set-->Members->Click the Pencil Icon to edit and rechoose your locatino.

2. Click your media set again.

3. Click repair. For me this took like 5 seconds to run at most, even on large backups(500gb+).

4. Once that is finished click verify. Let the verify finish. Obviously this may take a while depending on the size of your backup and speed of your network. Some of mine took multiple days.

5. BACKUP!! WOOOHOOO

 

- John

Share this post


Link to post
Share on other sites

I know WHY this happens... cos it happened to me. It seems to especially effect NAS disk backups, and it's to do with how Retrospect 'sees' them on the network. What I mean by that is: when you start a backup to a NAS drive, do NOT mount it on your desktop. Retrospect can find and backup to it fine, without mounting it. If you do a backup with the NAS drive mounted, and the 'no media' error appears, you'll have to rebuild the catalogue.

 

Otherwise if it is a normal desktop hard disk (connected via USB/Firewire etc), and it suddenly doesn't recognise the backup, it might be that you've connected the drive through a different type of connector. Just reconnect to the other port on the drive, if it has one. Or, the drive may be developing bad blocks on the disk platters, in which case start another member on the same drive, to bypass them – if you know the drive is good, and Retrospect is just being overly cautious. So long as your member backups are intact, you'll be OK, but a catalogue rebuild may be necessary in future, if the 'no media' error reappears again.

 

Whether it's a bug or not, who knows, but this is the solution.

Share this post


Link to post
Share on other sites

Actually, this occurs for us when using direct attached storage (internal drives, in fact). To fix, I found I just had to repoint the media set member, no need to do any catalog rebuilds, etc.

Share this post


Link to post
Share on other sites

Out of curiousity, how did you do a 'media set member repoint'?

I can't get that to work in Retro 10.5 with favourite folders, as sources, and a folder on a NAS drive as the backup destination - probably doing it wrong.

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

×