which is really annoying when trying to run backups or file copies taking several hours overnight. Fix it by turning off the "Log out after XXX minutes of inactivity" setting in:
System Preferences -> Security -> Privacy Tab -> Advanced Button
Coffee | Coding | Computers | Church | What does it all mean?
Mac OS X and Windows
which is really annoying when trying to run backups or file copies taking several hours overnight. Fix it by turning off the "Log out after XXX minutes of inactivity" setting in:
System Preferences -> Security -> Privacy Tab -> Advanced Button
It used to be well known that you have to use an Apple formatted disk (HFS+) for Time Machine Backups and you can't use an NTFS formatted disk, or any of the popular *nix disk formats with Time Machine.
Except, you always could.
It's not always a first choice option:
<YourMachineName>.sparsebundle
in the Finder each time you plug the drive in. After that, Time Machine backups will run as normal.Plug in your foreign-formatted disk and get a read/write driver for it.
Save the the script from tmMakeImage script in, for instance, your Downloads directory.
Open a terminal window.
If you saved to Downloads, then something like this should make the script executable and show you command line usage:
cd ~/Downloads
chmod a+x tmMakeImage
mv tmMakeImage /usr/local/bin
tmMakeImage
So if your external drive has a Volume called WinDrive, and your Mac drive is about 250GB then this command should initialise it for Time Machine backups:
tmMakeImage 500GB /Volumes/WinDrive GO
Optionally, follow up with an immediate tmutil startbackup
Opening the Time Machine preferences should now show that you have "Time Machine Backups" selected as your backup drive. Don't forget to double-click the sparsebundle each time you attach the drive, to mount your Backup Volume and allow Time Machine to do its stuff.
Backup to a network drive in a similar way. First mount your smb network fileshare in the Finder, then use the tmMakeImage
script to put the sparsebundle image on the mounted drive.
Reliability is a concern for backing up across a network, or to a removeable in disk. In otherwise, it's always a concern. Especially if you have a laptop which gets plugged in and out. See notes on using time machine backup to a windows share more reliably.
Apple created, it seems, sparse images and sparse bundles to solve the problem of saving backups on a network drive. Time Machine uses and recognises them. It might even auto-mount the sparsebundle disk image when you re-attach the drive in order to start running a backup.
com.apple.TimeMachine.MachineID.plist
file in the package, which contains the UUID of the physical machine it belongs to. This stops you accidentally using backups on the 'wrong' machine. (Time Machine does let you browse and use 'wrong' backups though).man hdiutil
) or specified permanently (man vsdbutil
)tmutil setdestination /Volumes/Volumenameonceitsbeenmounted
. You can mount the image either by double-clicking it in Finder, or with hdiutil attach /path/to/image
.```
man tmutil
man hdiutil
man vsdbutil
```
Most of the things in the tmMakeImage script can be found on the net going back to 2007, but you'll still find answers on the internet saying it can't be done.
I can't believe I've only just discovered the gnu screen
command. You want to kick off a long running command line process and come back to it later? Like so:
Terminal
windowscreen
ls -R /
screen -R
Now that's what I call magic.
It survives logouts and is of course an essential for working with remote or cloud machines over ssh; when your network connection fails you can log back in and carry on. man screen
will tell you more, although so will https://www.bing.com/search?q=linux+screen
I've tried a few solutions for using multiple computers (mostly one MacBook plus one or two Windows machines) simultaneously and I've currently landed on http://synergy-project.org/ as the One for Me.
It's very good. It's pretty seamless (last year less so, this years seems perfect) : put 3 machines next to each other, move your mouse across the 3 screens, and control and type into whichever computer has mouse focus. It's particularly a good solution when some of your machine are laptops and you want to use the laptop screens.
Alternatives I've tried:
ssh
or similar is really good. Even a modest monitor easily has room for multiple console windows. A reminder perhaps that guis are not always the bee's knees.