d2e301c1-f62b-4374-94a4-db0352c4e2ba Posted September 10, 2011 Report Share Posted September 10, 2011 Running Retrospect 8.2.0 build 399 on Mac OS X 10.6.8 with client and server software running on same machine. I've been running the same jobs backing up my precious data for several years without issue, copying data from Mac to a SAN mounted across my network. Last weekend the job failed for the first time, asking me for media. I've clicked on "Choose Media" and get the eternally frustrating "This disk is already a member of this media set". When I look at the media set (it is noted as busy), there are no members shown. I've tried adding a Firewire 800 connected external drive using Choose Media but the job never starts - it just stays saying Needs Media. The job has now hung, and I can't stop it, pause it or now run any backups. I've killed the server, I've rebooted, I've sworn, cussed and cursed. I've now downloaded Chronosync and about to trash several years of backups. Anyone have any ideas before I hit the del button on several Tb of rdb files that are worthless? Thanks Sam. Quote Link to comment Share on other sites More sharing options...
twickland Posted September 12, 2011 Report Share Posted September 12, 2011 Running Retrospect 8.2.0 build 399 on Mac OS X 10.6.8 with client and server software running on same machine. This it not normal practice. Do you perhaps mean you are running the console and engine on the same machine? Last weekend the job failed for the first time, asking me for media. I've clicked on "Choose Media" and get the eternally frustrating "This disk is already a member of this media set". Retrospect should be looking for a specifically-numbered member. If the disk volume is full, it should be looking for a member one number higher in the sequence. What are these member numbers? When I look at the media set (it is noted as busy), there are no members shown. This is normal behavior when the media set is in use. The job has now hung, and I can't stop it, pause it or now run any backups. I've killed the server, I've rebooted, I've sworn, cussed and cursed. Try stopping the engine and dragging the Retrospect folder from /Library/Application Support to the desktop; then restart the engine and console. You will need to re-enter your license code, but Retrospect should now have forgotten whatever activities it was previously trying to perform. Double click on your media set catalog(s) to tell Retrospect where they're located. Can you now view the members? Is there any space shown as available on the last member? Quote Link to comment Share on other sites More sharing options...
d2e301c1-f62b-4374-94a4-db0352c4e2ba Posted September 24, 2011 Author Report Share Posted September 24, 2011 Try stopping the engine and dragging the Retrospect folder from /Library/Application Support to the desktop; then restart the engine and console. You will need to re-enter your license code, but Retrospect should now have forgotten whatever activities it was previously trying to perform. Double click on your media set catalog(s) to tell Retrospect where they're located. Can you now view the members? Is there any space shown as available on the last member? Thanks twickland. This at least got my console back. I did have to put the engine package back into that folder to get it re-running. Added my media sets back, and am now attempting a backup. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.