Search the Community
Showing results for tags 'repair'.
The search index is currently processing. Current results may not be complete.
So, we now have these storage groups that function like a collection of mini-sets and mini-catalogs, with each client or source getting a mini-set/catalog. When I have to repair or rebuild a set on any of my consulting clients' Retrospect installations (WAY more often than I should if I had a truly reliable backup program IMHO), I see the individual "mini-sets" getting scanned and rebuilt. Is there a way to trigger a repair or rebuild for an individual source in a storage group? Right now I've got a client that isn't backing up due to a "chunk checksum (-641)" error. I'm so tired of rebuilding multi-terabyte backup sets that I really don't want to have to put everything on hold yet again while this 5TB disk is scanned and the catalog rebuilt. Since each source appears to have its own, self-contained catalog and folder of band files on the backup disk, couldn't Retrospect just rebuild the individual source whose catalog has failed? Thx, Fred
I am currently in the middle of rebuilding a number of catalogues for use within the newest retrospect. The system used is a tape based system and now within a certain media set retrospect seems to have skipped over tape 17 of this showing 0GB used. I have continued on with the rebuild but now seem to have no way in going back to tape 17 for it to repair the catalogue and rebuild everything on that tape. My question simply, Is there a way around this other than starting the media set rebuild again? Is there a way to jump back to this individual tape and repair it correctly. Thanks
I am currently going through a rebuild from a number of tapes and unfortunately Restrospect seems to be getting stuck when it comes to a certain file. Is there any way of just skipping this single file on rebuild or can I only skip to the next tape to continue the rebuild? Thanks Mac:Lion Retrospect:10.5.0
Currently running Retrospect 10.5.0 on Snow Leopard Machine: Processor Speed: 2.66 GHz Number Of Processors: 2 Total Number Of Cores: 4 L2 Cache (per processor): 4 MB Memory: 13 GB HDD Capacity: 496 GB Available: 396.91 GB Have been using Retrospect 10 to rebuild catalogues that were previously being used within version 6. The rebuilds have been going fine but lately I have been getting an error of: '!Not enough application memory'. Nothing in my opinion has changed from when we started rebuilding catalogs and in my opinion I would think that the machine being used has plenty of system memory. Has anyone else come across this error on rebuild/repair? Surely there should be an easy solution to this that I'm just missing, or isit simply a bug? Any info would be great. Thanks