Jump to content

MikeHutch

Members
  • Posts

    102
  • Joined

  • Last visited

  • Days Won

    1

MikeHutch last won the day on December 16 2023

MikeHutch had the most liked content!

Profile Information

  • Gender
    Male
  • Location
    England

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

MikeHutch's Achievements

Rookie

Rookie (2/14)

  • First Post Rare
  • Collaborator Rare
  • Conversation Starter Rare
  • Week One Done Rare
  • One Month Later Rare

Recent Badges

3

Reputation

  1. First of all, yes, it should show the internal drive as a Source device by default, and any other storage devices that are connected. So something is wrong there. Next, I'd check that you have successfully 'activated' the licence for Retrospect, by checking in preferences, and the licence section. If the licence number is there along with several entries for stuff that you've paid for. If that is the case, that rules out the possibility that the program is in demo mode. [I starting to think there is something wrong with the storage drives...] After that, do a test; setup some favourite folders, and a backup Script, using the favourites as the files/folders to backup, then select a new Media Set to backup to – onto whatever drive you see fit. Of course this is assuming you CAN see your internal drive as a Source to backup. If that works, then there is something wrong with one of your drives, as described by the error message "RefBackujpsetsContainer::CreateBackupset: volRef invalid". If that fails, I suspect there is a drive error either the internal SSD or the drive you're backing up to. You need to check and repair each drive you're using. Then try launching Retrospect again, and see if it recognises your internal SSD drive as a Source, and then backs up the files properly. Let me know what happens. Then we can narrow it down some more.
  2. Thanks for the update. Sorry I think I got the wrong end of the stick there. However, yeh, that is strange being so slow. Seems to be some kind of bottleneck going on with your backup, somewhere. Of course it all depends on how much data is being backed up. For instance my backup is usually around 1-6GB, which takes about 5-10min, backing up my internal SSD to a NAS over 100Gbit network.
  3. Well there's your problem, 10Mbit network. That is slow. You need a minimum of 100Mbit or more. I'd check your network switch box or router, is probably set at 10Mbit - which is likely the bottleneck of your network. If it is, you need to replace it with a faster unit. BTW, it doesn't matter if your oldest computer has a slower network speed, as the extra bandwidth (100 or 1000Mbit) caters for all speeds.
  4. Looks like you have corrupt files, Retrospect is trying and failing to backup. As you can see via the '(corrupt persistent data)' bit in the log text. To find out what is corrupted, as the log doesn't say specific filenames, I suggest you backup a few folders at a time, as a test backup, until you come across this error, so you can narrow it down. Just look at the log everytime it completes a test backup. Once you've hit on the problem, you'll have to backup 1 folder at a time, you narrow it further, OR, manually check the files in those folders, to see if they open up OK, or not, or just resave them. RHL, I suspect the corrupt file may have gotten corrupted before or after the backup - either way, a file or two are definitely damaged. See above solution for those effected Macs. It's a pain, but that's all I can suggest.
  5. It's rare to have corruption with compressed catalogs - from my 10 years of experience with Retrospect. So I'd say you're pretty safe! Even if the file does go wrong, you can rebuild it no problem - it just takes a bit of time, depending on number of files you've backed up. Regarding the max usage of the drive, just up the amount by 100-200GB in the 'Use at most' box, eg 7353, while leaving room for other files you may want to put on the drive. See if that makes a difference - I believe the app calculates disk space a little differently than straight forward Gigabytes.
  6. Thanks for the extensive list of actions you've done, that helps rule out a few things. The basic problem you have, is the catalog file, more over, its location could cause problems (see 1st screen shot). I don't think putting the catalog file in the Retrospect backup folder is a good idea, this an area where Retrospect app has full control over. I'd move the file out of that main folder, and create a new folder on the root of the drive, then move the catalog file into that folder. Obviously you'll have to tell Retrospect its new location. This should solve that issue. The other issue, is that the catalog file may be damaged, in which case you'll have to repair or rebuild it. Also, question: Is the catalog file compressed - see; Media Sets / [catalog selected] / Options? This should reduce the size of it considerably.
  7. Sorry, I just realised that you could try an even simpler solution... Before you do that, I'd try creating a catalog file from the backup disks with your latest version of Retrospect. I think you'll have a good chance of doing that. To do that, go into the Media Sets panel, and click on the Rebuild icon near the top of that window. It will ask for the the backup disks, everyone of them in sequence, and will proceed to build the catalog. Obviously this will take some time. Then you can restore whatever files/folders you want. Without the need to get an old version of Retrospect.
  8. This sounds more like network bandwidth has been throttled down from your highest to the lowest one available. There are a few reasons why this could happen; a) the Macs are using WiFi, not Ethernet; b) the switcher box or router is using a lower bandwidth setting; c) there is heavy traffic on the network, ie backing up too many computers at once; d) the Mac's network settings are not setup to use their full bandwidth, usually 1000BaseT, and it's not full Duplex. I'd look into that first, and see if anything is not right. Then move onto other areas that may affect it.
  9. No doubt a very late reply, but anyway... Retrospect v6.1 came out in 2005 and wasn't updated until 2010, to v8.2. So it's most likely a v6.1 backup. Not sure if the latest Retrospect version can read such an old backup format? Try it... you can download your last licensed software from Retrospect's 'Archives' - just do a search on their website. Assuming you know what your license code is. If not, email Retrospect team. Otherwise, you'll need to get an old enough computer to run v6.1, v8.2 or v9 of Retrospect, and it's compatible MacOS version – I think they will probably be backward compatible.
  10. SOLUTION: Yes it's an annoying, and a seemingly random problem. And, I know what the solution is for this problem... Go to your Media Sets, and select the one giving you the problem, then click on Rebuild button (at the top of this section). It will ask you for the location of the Retrospect backup files for that Media Set. You only need to select just the Retrospect folder on the drive it is stored on - the program will find the files for you. Then it'll ask where to save the updated catalogue file - I usually replace the old one on my drive. It wil proceed to rebuild the media set. That's it, it'll work now (99.9% of the time). Hope this helps.
  11. Has anyone tried to use Retrospect 18.5.x with Mac OS Sonoma? If you have got it to work, and is it even useable? Otherwise I'll have to upgrade, when I install Sonoma. Thanks either way.
  12. Alex, did you make sure that the RetrospectEngine and RetrospectInstantScan items in the Full Disk Access pane (Sys Prefs: Security & Privacy > Full Access) are actually ticked? This is important, as you, the user have to manually authorise those programs to start using full access. If unticked, it's just a provisional level of access. Assuming this has now been done, any further errors should go away.
  13. Thanks for the info David - very in-depth. By the way, my [Retrospect] folder structure is in the standard configuration you've described in your second paragraph. Anyway, I'm good now, so no problems.
  14. Good news. I've just discovered something surprising about the NAS members problem, relating to editing, rebuilding or repairing the set! I have a Media Set that lost it's connection to Member Set 1, on my NAS. So I decided to repair it. I then decided to repair it... got to the 'Add Member' dialogue window showing your available storage devices, and selected the Retrospect folder on my NAS drive. I thought, OK lets see what happens, so I clicked on Retrospect folder, and pressed 'Next...'. Low and behold, the program found the members itself, after a few seconds. Clicked on the correct backup set, and pressed Next.. again, and it repaired the Media Set. It seemed to have worked! I always thought that you have to find the member folders your self (I'm using Retrospect 16.6 (114)) manually - or at least, that's what I had to do in older versions. Of course the user guide wasn't helpful in giving any further instructions on exactly how you are suppose to find the members in a media set. 😞
×
×
  • Create New...