Neither quitting and relaunching Retrospect Engine nor rebooting the backup computer made any difference, and when I attempted to rebuild the catalog, I was unable to do so because Retrospect failed to accept the media set's password. In mid-June 2021, shortly after upgrading to 18.0, Terwilliger started getting strange errors for two clients: 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?" He wrote "I really don't want to have to put everything on hold yet again while this 5TB disk is scanned and the catalog rebuilt.
#Retrospect client for windows 10 mac
The motivation for his reporting the deficiency in the Retrospect Mac Forum was that, in order to Rebuild the Catalog File of one particular Media Set that was getting a "chunk checksum (-641)" error because of a particular bad backup script run (probably caused by a hardware failure), the GUI deficiency forced him to Rebuild the entire Storage Group. Obviously I urged the administrator who complained about the half-baked Storage Groups GUI to file a Support Case, with a feature request to allow the kinds of GUI access to the Media Set components of a Storage Group that he would have had if the Media Sets were stand-alone. After running a test in April 2020, I explained their kludginess in a further lengthy up-thread post-enhanced in its 6th and 7th paragraphs with a proof by Retrospect Tech Support of a single Storage Group's ability to be a destination for backing up multiple Sources in parallel. I described Storage Groups at some length in this up-thread post after they were officially released with Retrospect 16 in March 2019. IMHO this situation illuminates several organizational problems at Retrospect "Inc.". On June 28th he wrote "Since the storage group disk media set was failing only with new backups, I decided simply to use it only for restores going forward and to create a new regular disk media set for new backups." Despite my PM'ing him on July 11th with a request that he file a Support Case, Terwilliger hasn't accessed the Retrospect Forums since June 30th and hasn't yet read my PM.
A British backup administrator I'll call Terwilliger had been using an HDD Storage Group for over a year, but encountered several bugs over a month ago soon after upgrading to Retrospect Mac 18.0.
0 kommentar(er)
