You do not need to restore your whole machine. You need to restore only one folder. Time machine is much faster than I assume. Seems like a big deal to me since I've been trained never to relay on backup.
Just crank up Time Machine and copy the folder, in which you deleted all the content, back to where ever you had it. I had to go back a level in ...
I used to make the same mistake frequently with rm -rf at my last job. One technique that I learned from another engineer was to, instead of navigating the the directory you want to empty, navigate to the parent directory, and use the command rm -rf directory-to-clear/* instead. This isn't foolproof either, but you're much less likely to make the same ...
You cannot partition a volume. You must partition a drive (device). To do so, click on the drive itself, located just above the partition you selected on the sidebar ("Samsung Portable...").
Then, you can partition the disk.
Edit: Back all data you want to keep up and Erase the disk as GPT (GUID Partition Table). Newer versions of DU for some reason don't ...
Actually that is, in most cases just fine.
I've been restoring my user profile on an older Mac to a newer Mac since the Migration Assistant was available on OSX. And I always do what you just did, restore everything.
That said, if you were having issues with your networking on the old Mac then it might carry over to the new Mac. But I have never seen ...
There is a preference setting for that. All you need to do is specify, in megabytes, your desired maximum space limit. In Terminal, enter the following command and replace xxx with your desired size limit.
sudo defaults write /Library/Preferences/com.apple.TimeMachine MaxSize xxx
Everything in /private is excluded by rule - including /var/log/system.log
tmutil isexcluded /private/var/log/*
More details on this are at On OS X, what files are excluded by rule from a Time Machine backup?
You would need another tool to back these up as I’ve not had luck using the tmutil removeexclusion /var/log/system.log command which might have ...
Time Machine does not backup deleted files. The whole point of maintaining a backup is to make copies before files are deleted -- so that if you want to restore them after deletion, you can do so.
It is not useful to think of deleted files as merely 'marked for deletion but still there'.
Having said that, the APFS format does make 'local snapshots', ...
No. Time Machine only backs up files present on the filesystem and furthermore, only those not excluded by a rule or explicit exception.
On OS X, what files are excluded by rule from a Time Machine backup?
What does Time Machine back up?
Copying from a backup is much more efficient than anything. If you want to take the hard route, stop using your operating system immediately and look into using testdisk on it from an external OS installation.
For backing up from your time machine drive do the following:
Plug in your time machine backup, and then open up terminal.
Open up two finder ...
From man tmutil:
A directory inside a machine directory that represents a single initial or
incremental backup of one computer. The word "snapshot", in most contexts, is a
generic term and is not to be confused with a "local Time Machine snapshot",
which is simply a snapshot stored locally on the computer. E.g.,
diskutil list seemed to be the answer I was looking for.
$ diskutil list
/dev/disk0 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: FDisk_partition_scheme *512.1 GB disk0
1: Apple_HFS SSD 512.1 GB disk0s1
/dev/disk1 (external, ...
Rsync, with the -E option, will copy the extended attributes and ACL of a file. The man page for rsync states:
-E, --extended-attributes copy extended attributes, resource forks
Apple-specific option to copy extended attributes,
resource forks, and ACLs. Requires at least Mac ...
I found an answer over at superuser.com: https://superuser.com/a/1148703
But it seems there were some changes in MacOS so it did not work. But with this as a starting point I found a solution:
Format the new drive (Or in my case the corrupted drive) with Disk Utility. Give it the same name as the old one. In my example "Daten"
Go to the System Preferences -...
I've just experienced this same issue after the latest supplementary update. I rebooted my Mac and still the same error. I Googled and there are literally two topics on the Internet about this issue with that exact phrase (this topic and one on Apple's website). After some investigating I've managed to resolve this issue.
Turns out my previous backup left a ...
To restore from a Time Machine backup on SynologyRouter, and probably any other Time Machine network drive, selecting the 'Other Server' option in the 'Select A Restore Source' screen will allow one to enter the proper network drive URL.
What is important, though, to enter the full URL, including the actually shared network folder name, not just the URL for ...
I think it is possible for your situation.
(but before the reading: all writeup here is valid only for Mojave and Catalina, I cannot tell about other versions, it may or not be the same for other versions)
Historically time machine backups evolved into various kind of "marks" to determine which item is included or excluded. For the recent version I think ...
The Fusion Drive is significantly slower than the SSD on a MacBook Air. There is a portion of SSD on the Fusion Drive, but after copying all of your files over from your old Mac, it will take the operating system quite a while to determine which are the files/programs you use the most in order to "optimize" (i.e. put on the SSD portion of the Fusion Drive).
I ran into this same issue trying the same thing on Mojave. It appears that ACLs on symlinks just aren't supported when working within the confines of disk images. I did come up with this workaround though:
Create a blank sparse image that's big enough to hold the backup.
ditto the backup directory into the mounted sparse image. It will make the same ...
Please note that although both outcomes are the same whether encrypting with Disk Utility or Time Machine, Disk Utility takes significantly longer.
Perhaps this is because it is encrypting the unused free space and TM is not.
Can anyone else corroborate?
Also, in Terminal you can simply use this command to show TM volumes & status:
diskutil cs list
Unlike some installations of some operating systems there is no OS level uninstall feature in macOS.
That is true for applications, though some do have uninstallers available.
That is true for minor OS version upgrades, EG 10.14.1 to 10.14.2
That is especially true for full versions, EG 10.14 to 10.15
What that means is that if you install an OS update ...
I love having two destinations and the best way to check is to force two backups, rotating between them each. You’ll know if the file system are clean, the metadata correct and be able to see the actual timing needed to back up to each.
tmutil startbackup --rotation --block && tmutil startbackup --rotation --block
You will get timing on the backup ...
macOS progress and completion estimates are often based on the number of bytes transferred. But one large file will usually transfer much faster than many small files even if they add up to the same size. What may be happening here is that the transfer started with some large files, went quickly, and resulted in an optimistic estimate. But now it is into ...
I've recently had the same experience. Netatalk exported a volume with time machine set to yes, I could mount the volume, but it would not show up in the Time Machine preferences panel.
From the Finder I tried to create a new file/folder and realized that I didn't have write permissions. Granting read/write permissions on the underlying volume on the file ...
If you're sure this is something that you want to do, I think the best way to try it is to use the tmutil (Time Machine utility).
Quoting man tmutil
Begin a backup if one is not already running.
--auto Run the backup in a mode similar to system-scheduled backups.
--block Wait (block) until the ...
Just spent quite a bit of time researching how to perform this stuff via Terminal one-liners, and, this is what I came up with.
You still need to disable SIP (boot into Recovery Mode by pressing CMD+R at boot, opening Terminal there (from the Utilities Tab at the top) and running csrutil disable and then reboot)
Back in the main os, the file of interest is ...