From what I'm gathering you want to see if anyone accessed your computer to make a backup of it. I found this thread which might answer your question for how to retrieve the time machine backup logs from your Mac. Run the following command in Terminal
log show --style syslog --predicate 'senderImagePath contains[cd] "TimeMachine"' --info
which will show ...
All relevant UUIDs and other Time Machine metadata are stored in /Library/Preferences/com.apple.TimeMachine.plist on the host side (the Mac to be backed up)! The file contains (probably the old) hostUUID (hardware), destination volume UUID (backup volume) and all IncludedVolumeUUIDs (source volumes). To get your current volume IDs use diskutil info diskXsY ...
If you want a local backup you can run a bash script that creates an archive of your home directory.
zip -r pathToBackup.zip /Users/username
This can be expanded upon with bash to:
Add password protection and encryption with the --encrypt option
Run automatically at certain times with cron
Append timestamps to name of backup file
Keep only a certain ...
I think this might help:
The Time Machine Mechanic (T2M2) – a quick but thorough check of Time Machine backing up
It’s a free tool from Howard Oakley, who describes it this way:
T2M2 analyses your logs to discover whether Time Machine backups have been running normally, reporting any worrying signs or errors. You do not need to be able to read or ...
Building upon the information provided in @klanomath's answer, I was able to figure out a specific solution to my exact case (others may differ).
In my case the problem was the extended attributes attached to the machine directory, for some reason Time Machine didn't like them. However, after forcing the correct values in I was able to sort these out.
For reference, Time Machine now officially supports SMB shares, tho they need special protocol extensions (supported e.g. by Samba >= 4.8). Sources:
Even without having configured Time Machine, you can manually create a localsnapshot with the command tmutil snapshot. So setting up a scheduled task to run this command should be straightforward.
There's no point or need to specify which folders to backup: like TM, snapshots only record the changes made to the disk. So if you work on a handful of files, ...
You could use rsync and append a suffix with the date and time as described in this SO answer Use rsync for backup without overwrite
For example (you would change the source and destination directories)
rsync -aE --backup --suffix=`date +'.%F_%H-%M'` ~/Documents/WantedFiles/ ~/Documents/Backup/
This will copy everything (including extended attributes ...
The good news: your system is working afterwards
The bad news: user installed apps and user data will be deleted
The command rm -rf /* tries to remove all files in the whole root hierarchy. This is done with the privileges of the user executing it.
An admin user will remove all admin user installed apps and his/her/* own files - including files installed ...
The new command to purge snapshots is seriously faster and more well engineered than the previous local store.
It does require a new syntax, so you’re correct, Apple has forced us to learn more and change.
Joshua was in your situation as well and has a very detailed explanation:
How to thin your local Time Machine Snapshots on macOS High Sierra
The first thing to try on Catalina is to tell it not to backup the system files and apps. Since the read only system is split, you will have a larger than normal new backup interval. You shouldn’t have to do this by my math either, but it’s low hanging fruit to try.
Open Time Machine preferences, select options and tick the box labeled Exclude system files ...
I had a similar issue where TimeMachine was complaining about not being able to backup to a USB attached external disk. (Even though there was plenty of space for the backup).
Apparently the connection was in an unexpected error state, so I did the following and all was working afterwards:
Shutdown the Mac
Unplugged the External HD
Unplugged the USB cable