Restore from TimeMachine-Backup failed
Today I needed a restore from a backup from my TimeMachine. After a few hours and over 55 Gb were copied to my Macbook again TimeMachine stoped. There is a file which cannot be copied: ...2BUABC452.com.agilebits/AppStore Receipts/receipts.
Do you have a solution? I am very surprised about it! For what I make the Backups and if I need one I am not able to use it?
1Password Version: 7
Extension Version: Not Provided
OS Version: 10.14.5
Sync Type: Not Provided
Comments
-
@Silvermoon: Thanks for reaching out. I’m sorry for the difficulty. Others that encountered a similar permissions issue with App Store receipts have found that excluding or deleting the problem files from the backup works:
~/Library/Group Containers/2BUA8C4S2C.com.agilebits/App Store ReceiptsI hope this helps. Be sure to let me know if you have any other questions! :)
ref: apple-3062
0 -
And where I can delete or exclude it? To do it before the backup starts it is too late now. This file is already included in the sparsebundle-file from my backup. Now I need the restore from this back-file!
0 -
@Silvermoon: You'd need to mount the drive and delete that folder manually. Someone wrote a blog post about a similar issue with a Time Machine restore that might help:
https://www.harryfear.co.uk/blog/time-machine-error-while-restoring-from-backup
Excluding it from future backups should help you going forward though.
0 -
It doesn't work for me. I only reached the point "Operation not permitted". All further suggestions don't work for me.
What makes me wonder is why you don't place a warning in bold red letters on your homepage or in the app where everybody can read it and avoid a bad surprise? Now it is to late for me to exclude the mentioned folder from my backups and I have more of one for nothing now!
0 -
What makes me wonder is why you don't place a warning in bold red letters on your homepage or in the app where everybody can read it and avoid a bad surprise? Now it is to late for me to exclude the mentioned folder from my backups and I have more of one for nothing now!
Considering there are millions of 1Password users and this situation affects only a handful... putting a big red banner on the front door doesn't seem like the most appropriate course of action. I don't mean to downplay the situation and how it may be affecting you, but I think it is important to keep perspective. Scaring away potential and existing customers with a big red banner warning of an issue that is extremely unlikely to have any implication or impact for them is just bad business. We certainly aren't ignoring the problem though. We have released an update which we are hopeful will fix this problem for any backups made after the update has been applied. Unfortunately we have no way of retroactively modifying previously created backups. The best I can suggest if you need to restore a backup from prior to the fix would be to use the instructions brenty linked. If you're having trouble with that:
It doesn't work for me. I only reached the point "Operation not permitted". All further suggestions don't work for me.
Could you please let me know exactly which step you're having trouble with? Where do things fall apart? What action are you taking, what do you expect to happen, and what happens instead? The more detail you can provide the more likely it is that we'll be able to quickly assist you.
Thank you.
Ben
0 -
Seems that the chance to have this problem is similar to win in a lottery? Latter I prefer!
What I did first is to copy and paste the commands Brenty recommends in terminal.app. But not without adapting it to make it working on my time capsule. Because I am not so firm with Unix it needs some experiments. What I am missing in the solution of brenty are the responds of the commands. One thing was clear for me I should be asked for the passwords of the drive and the backup-file. As this happens I made a copy of the successful commands and the including path because I expected to go the same way for the other users of the MacBook again.
And the last step then fails with the mentioned respond „operation not permitted“. The solution for this case was to enter the same command without „sudo“ in the terminal.app in the recovery mode. But nothing happened in this step so I gave up and started a fresh installation of my MacBook from zero.
0 -
I'd have to agree winning the lottery seems much more appealing. And I do apologize that you ran into this issue. One thing that is important when working in Terminal is that spaces in file paths need to be "escaped" with a
\. So, for example, if I need to talk about a file at/Volumes/Ben's Drive/My Files/Important Stuff/1Password.opvault
I would have to enter/Volumes/Ben\'s\ Drive/My\ Files/Important\ Stuff/1Password.opvault
in Terminal. Otherwise it assumes when you put a space that you're moving on to the next part of the command.it sounds like you've found another way around this (starting over), but if you decide to give it another try I hope that helps.
Ben
0 -
I think the problems are how to enter the passwords for the TimeCapsule Drive and the password for the decryption of the sparsebundle file.
By the way the backslash is even necessary for the apostrophe not only spaces: /Volumes/Ben\'s\ Drive/...
0 -
By the way the backslash is even necessary for the apostrophe not only spaces: /Volumes/Ben\'s\ Drive/...
Good catch. I've updated my post.
I think the problems are how to enter the passwords for the TimeCapsule Drive and the password for the decryption of the sparsebundle file.
Okay. What seems to be the difficulty with that?
Ben
0 -
In the recovery mode I was faced with the problem how to get access to my password secured drive in the TimeCapsule?
0 -
@Silvermoon: You'd need to mount it, just as if you weren't in Recovery Mode. Both Terminal and Disk Utility should be available there.
0
