ctsrutland 0 Report post Posted September 7, 2007 I'm using Retrospect 7.0.326 on SBS 2003, update 7.0.6.108 . I have a set of external firewire hard drives, using Proactive backup. My current problem (I have lots of others) is that Retrospect is stuck saying "Waiting for storage media", even though the correct disk is in, and has free space. There are no errors in the SBS event log, or the Retrospect log. There are no pop-up messages with any further error code. In 'backup sets', the current disk is shown as a member, and if I try to add it again it says it already is a member, so at some level it knows it's the right disk. The 'remove' button is greyed out so I can't remove it and add it again. I have removed and re-added the backup set as a destination for the proactive script. I'd try physically reconnecting the disk, but I'm working remotely. I have shut down and restarted Retrospect. After searching these forums I checked file permissions on the disk, and the Retrospect user does have write permission. Yesterday I recycled the set and it worked, but today there's a different external disk, and I have the identical problem. I can't recycle every disk every time they get swapped over. Any ideas - thank you? Share this post Link to post Share on other sites
1sae 0 Report post Posted September 7, 2007 Do you have disk compression turned on in Windows? If so, I have the same problem. The size of the data is 112 GB compressed on disk to 29GB. Retrospect sees the data is 112GB and thinks the disk is full. Haven't exactly found a work around, but I just added a new backup set on the same disk and alternate the sets on the script. Share this post Link to post Share on other sites
ctsrutland 0 Report post Posted September 8, 2007 Fixed it, I think. I recreated the catalogue for the disk. After that was finished, it still didn't back up. I noticed the disk was marked 'read only'. I removed that (it's probably meant to be like that?). Then I noticed the disk had been removed as a destinatino for the script by the process of recreating the catalogue. When I put it back, it started backing up.. at last! Share this post Link to post Share on other sites
Lennart_T 152 Report post Posted September 10, 2007 Quote: Then I noticed the disk had been removed as a destinatino for the script by the process of recreating the catalogue. That's an annoying bug. You have to go through ALL scripts and add the destination again. Share this post Link to post Share on other sites
