Jump to content

sjmills

Members
  • Content count

    57
  • Joined

  • Last visited

Community Reputation

1 Neutral

About sjmills

  • Rank
    Occasional Forum Poster

Recent Profile Visitors

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

  1. I filed a bug, then I uninstalled and deleted all Retrospect files from my machine after attempting to try 16.5, but was greeted with a stupid Try button that took me to a web page to fill out a form just so I could download it again and get a trial code. No thanks, I'm finished with Retrospect and it's bugs, bad design, and horrendous performance when browsing backups.
  2. The boot volume I'm backing up is on the same machine that Retrospect runs on, so it's not a client. But if I select that boot volume in the Sources, the Options tab is all disabled, then yes, All Volumes is selected.
  3. And setting the "No backup" label on /System/Volumes/Data/Volumes AND each of the external volumes in that folder isn't working. They still get backed up. Great. It's also hard to tell if the correct label is being inspected by Retrospect, since they call it Gray in the Rules editor, even though I've renamed it to "No backup", and there is still a label named Gray that uses the same color.
  4. The problem with just letting Retrospect "handle the rest" is that it will now backup /System/Volumes/Data/Volumes/<all external drives>. That's just wrong and should not happen. Suddenly my full boot volume backup went from 850G to 1.3T because it's also backing up an external drive that I backup in a different set, AND the external drive I used to backup TO. Until they fix this in Retrospect, I'm going to have to mark /System/Volumes/Data/Volumes with my No Backup label so Retrospect will skip it for now. I'll submit a ticket for this, because it needs to be fixed.
  5. Yes, it's my boot drive. Safe boot and regular boot did not make a difference. Same error last night. I wonder if Apple added another level of folders or changed the permissions on Data, since the Retrospect doc lists ~/Library/Containers/com.apple.mail/, but not ~/Library/Containers/com.apple.mail/Data.
  6. I have both RetrospectInstantScan and RetrospectEngine added and turned on in my Privacy prefs. Retrospect runs on the same machine it backs up, so no client needed. After last night's backup I see in the log: While scanning volume TubeDrive, Folder /Volumes/TubeDrive/Users/myname/Library/Containers/com.apple.mail/Data/, Retrospect has detected it is not listed under "Full Disk Access" on the backup source system and cannot access all user data to create a complete backup. Please follow our step-by-step guide: https://www.retrospect.com/kb/macos_full_disk_access Well, it's on, so what's its problem? Retrospect 15.6.0 (125) macOS 10.14.1 (18B75)
  7. No. I was able to prevent it by preventing the external drive that it was backing up to from sleeping. I'll have to stop doing that to see if any release since then has made a difference.
  8. The last full backup for a particular Mac with version 14.x took around 18 hours to complete. The current full backup of the same Mac with maybe 5% more data has taken nearly 25 hours and it's only 1/3 of the way done! WTH? RetrospectEngine is being quite a pig, using 1.66G of RAM. Anybody else seeing 15 being severely slower than 14.x?
  9. It was the media request timeout pref. My guess is that it was always on (not sure when or how it got turned on) and set to 20 minutes, but it never worked before 15, so it wasn't causing a problem. All the email prefs are on and working, except it did not send a waiting for media email. I've been in contact with tech support and have reported that problem.
  10. No, it doesn't have to be erased. Like I said, the previous version properly prompted the user via email when it was to start a new media set. The user would then come to Retrospect, select the current task in the Activities pane, and click the Choose Media (I believe it's called) button down in the Summary pane. Now with 15 it seems like Retrospect is trying to do that on its own, but failing.
  11. I always have the latest version, so the last version was whatever came before 15.0.0. And I was wrong about using file media sets. I'd used them for so many years that I forgot that disk media sets are now the way to go, and that's what I've been using since, I dunno, whenever they appeared and replaced files. After Retrospect tried to backup again, I noticed that there was a new media set "Tube [010]" for this backup in the Media Sets, but it had an empty circle instead of the normal green checkmarked icon, and there was no trace of it on the disk. It's like Retrospect tried to create the set, but failed to add a member to it or even create any part of the file/folder structure.
  12. Every 2 months, my backups switch to a new backup set as part of the schedule. I use file backup sets. Since "upgrading" to 15.0.0, the wait for media step now times out and fails instead of letting the user choose a new backup set when they get around to it. That's really lame. Also, look how long it took to find the files; over 5.5 hours. It never took that long before. + Normal backup using Tube Script at 2018/05/06, 20:00:00 (Activity Thread 1) 2018/05/06 20:00:02: Finished scanning backup set data files To Backup Set Tube [009]... 2018/05/06 20:00:00: Use new Backup Set: Replaced with Tube [010] - 2018/05/06 20:00:00: Copying TubeDrive 2018/05/07 03:35:07: Found: 3436579 files, 770796 folders, 759 GB 2018/05/07 03:35:21: Finished matching 2018/05/07 03:41:23: Copying: 3280991 files (694.9 GB) and 10324 hard links Media request for "1-Tube [010]" timed out after waiting . [*] ArcDisk::arcExportSessionFile: unexpected value of ArcCatalog::m_lastvol 0; can not write session file 2018/05/07 04:01:30: Execution incomplete Remaining: 3,280,991 files, 694.9 GB Completed: 0 files, 0 B Performance: 0 MB/minute Duration: 08:01:29 (08:01:15 idle/loading/preparing) Here's the previous full new-media backup from the previous version of Retrospect: + Normal backup using Tube Script at 2018/03/04, 22:00:01 2018/03/04 22:00:01: Finished scanning backup set data files To Backup Set Tube [008]... 2018/03/04 22:00:01: Use new Backup Set: Replaced with Tube [009] - 2018/03/04 22:00:01: Copying TubeDrive 2018/03/05 00:38:24: Found: 3383778 files, 750859 folders, 733.6 GB 2018/03/05 00:38:37: Finished matching Only just over 2.5 hours. With version 15, a 2nd backup started at 23:00, but it only lasted a few minutes, so that wasn't what caused 15 to be more than twice as slow.
  13. I just contacted support. BTW, isn't this forum supposed to notify me via email of replies? I've received none. If not, that's very annoying and unlike most forums. I see a Notify switch below this edit box that is off. I'll turn it on, but that should be the default behavior!
  14. Since "upgrading" to 15, I get error -1011 often, and the entire backup fails. If I then run the same backup manually the next morning, it works. Bug? (Obviously, since earlier versions never did this.)
  15. Mac Thunderbolt port Firewire 800 adapter hard drive. No hubs, just 3 FireWire 800 drives connected in series to the adapter. No on other cables. They've been working fine for years. Only in the past few months has this problem started. Some problem with permissions or something.
×