SChaput Posted July 14, 2009 Report Share Posted July 14, 2009 I have been trying to access a past backup for about the last 30 minutes. This is the third time ive tried, i have restarted the engine, rebooted the machine, and all no luck. Is there a way to check if its really still accessing or if it's never going to access. I did notice that when retrospect backed up this particular folder it took a long time to "match" to my raid. Could this be whats taking so long. 4 Quote Link to comment Share on other sites More sharing options...
Mayoff Posted July 14, 2009 Report Share Posted July 14, 2009 I don't understand. What is the exact symptom you are seeing? At times of matching, Retrospect may not provide much feedback but it will eventually finish. Quote Link to comment Share on other sites More sharing options...
SChaput Posted July 14, 2009 Author Report Share Posted July 14, 2009 Under past backups, i click Browse. A new dialog opens up with a window that says "Accessing Backup" I then sit and wait for that screen for 35 minutes. Quote Link to comment Share on other sites More sharing options...
Mayoff Posted July 14, 2009 Report Share Posted July 14, 2009 Either the software is being really slow because the backup is large or something could be wrong with the catalog, causing a hang. How many backups exist within the set? How many total files? Quote Link to comment Share on other sites More sharing options...
SChaput Posted July 14, 2009 Author Report Share Posted July 14, 2009 Capacity: 4610 GB Used: 934 GB Free: 3675 Backups: 818 Files: 1,833,280 ------- Would rebuilding the catalog maybe speed things up? Quote Link to comment Share on other sites More sharing options...
Mayoff Posted July 14, 2009 Report Share Posted July 14, 2009 I million files is not too big. What type of Mac? Speed? RAM? Free space on the Mac HD startup disk? Quote Link to comment Share on other sites More sharing options...
SChaput Posted July 14, 2009 Author Report Share Posted July 14, 2009 MAC OSX 10.5.7 2x3 Ghz QuadCore Intel Xeon 8 GB Ram. 211GB free on the startup disk. Quote Link to comment Share on other sites More sharing options...
SChaput Posted July 15, 2009 Author Report Share Posted July 15, 2009 Could my matching be taking an extra long time because at the same time im copying the same media set to a tape? Quote Link to comment Share on other sites More sharing options...
rhagengwu Posted July 20, 2009 Report Share Posted July 20, 2009 (edited) I've been having a similar problem. After a while I get an Backup Unavailable error though. Similar setup. Newest gen Mac pro. 8 core 2.66 xeon, 3gigs of ram. 1 drive for system. 3 1.5tb drives in a raid 5 array for my media set. 1.3 mil files. 440Gb used. 227Gb free. No active backups while trying to access backups. Edited July 20, 2009 by Guest Quote Link to comment Share on other sites More sharing options...
hoss Posted February 23, 2012 Report Share Posted February 23, 2012 Any fix for this? Quote Link to comment Share on other sites More sharing options...
YaRU Posted July 14, 2015 Report Share Posted July 14, 2015 Yes, I would like to contribute. Same problem here. I am using: Retrospect 10.5.0 (145) Mac OS X Server 10.6.8 OS X Logs don't report anything. And so far I don't see malfunctioning hardware... Anybody? Quote Link to comment Share on other sites More sharing options...
Daniels Posted July 15, 2015 Report Share Posted July 15, 2015 Do you have any programs that might be accessing the catalog file running when try to access the backup. In my case I have CrashPlan running which causes me to wait about 15 minutes until I can actually see the files. @Steve: Definitely running a copy script would effect the access. Quote Link to comment Share on other sites More sharing options...
YaRU Posted July 16, 2015 Report Share Posted July 16, 2015 I found a solution pretty much: - Make the Retrospec Backup Engine not to start automatically on boot; - Reboot the computer; - Open Disk Utility, Scan and Repair everything on the volume where the Catalogs are stored; - Start the Retrospect Backup Engine; - Start Retrospect, and then it works! It can probably be done faster or easier, but at least this worked for me. (Two times already, since apparently something is corrupted in de Catalog-file... ) Quote Link to comment Share on other sites More sharing options...
bigdizzle Posted October 20, 2015 Report Share Posted October 20, 2015 Is there an official response to this?Rebooting a production server is not going to work for me. Same boat - "Accessing Backup.... this may take a few minutes" hangs forever. no jobs running. 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.