Better later than never, here is a hack to achieve this :
sudo ifconfig lo0 alias 127.0.0.2/32
Plug your usb drive, then via System Preferences / Sharing add a smb share to a folder time-machine-macbook in the drive time-machine-usb
Then, add a destination backup (Time Machine will see it as a network share)
sudo tmutil setdestination -a "smb://user:[email protected]/time-machine-macbook"
You can see if it's ok with:
tmutil destinationinfo
> ==================================================
Name : time-machine4
Kind : Network
URL : smb://kenji@realserver._smb._tcp.local./time-machine
ID : D820D053-C74A-4A06-A7E1-E60C8EA7934F
====================================================
Name : time-machine-macbook
Kind : Network
URL : smb://[email protected]/time-machine-macbook
Mount Point : /Volumes/time-machine-macbook
ID : F707BD0B-64DF-4DB6-A3B7-824470FB5EB2
Then start a backup with tmutil startbackup and mount will show:
/dev/disk3s1 on /Volumes/time-machine-usb (apfs, local, nodev, nosuid, journaled, noowners)
//[email protected]/time-machine-macbook on /Volumes/time-machine-macbook (smbfs, nobrowse)
You can see detailed progress with tmutil status:
Backup session status:
{
BackupPhase = Copying;
ClientID = "com.apple.backupd";
DateOfStateChange = "2018-06-28 17:38:21 +0000";
DestinationID = "F707BD0B-57DC-4DB6-A3B7-824470FB5EB2";
DestinationMountPoint = "/Volumes/Time Machine Backups";
FirstBackup = 1;
Percent = "0.08711567546702646";
Progress = {
TimeRemaining = 32679;
"_raw_totalBytes" = 355694600192;
bytes = 34429528173;
files = 887351;
totalBytes = 391264060211;
totalFiles = 2922384;
};
Running = 1;
Stopping = 0;
"_raw_Percent" = "0.09679519496336274";
}
In my case, near 1000000 files were done in about two hours (USB2 disk penalty, versus more than 8 hours via Wi-Fi), I calculate percentages with a small script:
tm-progress.sh
Files : 918702 / 2922384 (31.43%) - Bytes : 32.21 GiB / 364.39 GiB (8.84%)
We can here that many files can make Time Machine to progress "slowly" in Bytes, but nearly 1/3 of files have been copied.
Next step, when backup is finished, plug the usb drive to your realserver and copy the sparsebundle over the "uncompleted one" (or in the shared folder). Of course, Time Machine should be disabled during this step to prevent mounting a partially copied sparsebundle (and maybe corrupting it)
I have used an apfs drive to benefit of snapshots (to be able to revert to a previous "backupdb" in case of sparsebundle corruption, not tested yet)
Edit: even faster mode :
Once the backup has reached BackupPhase = Copying to make it faster you can make the backupbundle mount directly (without sending every operation through smb) by canceling the backup, renaming My-Computer.backupbundle to something like 1My-Computer.backupbundle, and creating a symbolic link :
ln -s /Volumes/time-machine-usb/1My-Computer.backupbundle /Volumes/time-machine-macbook/My-Computer.backupbundle
This tricks timemachine into following the link to the backupbundle localy, and not mount it through smb, which speeds up the backup. Make sure you move the backupbundle back when you have finished your local backup.
Answer from ıɾuǝʞ on Stack Exchange
Hi all, does anyone currently use Time Machine but instead of an external drive use a network share and if so, how have you set it up?
Why does Time Machine settings not see a network drive? - Ask Different
Multiple Mac's using time machine to one network drive
Why does Time Machine settings not see a network drive?
macos - Why can't Time Machine see shared drive? - Ask Different
Videos
Better later than never, here is a hack to achieve this :
sudo ifconfig lo0 alias 127.0.0.2/32
Plug your usb drive, then via System Preferences / Sharing add a smb share to a folder time-machine-macbook in the drive time-machine-usb
Then, add a destination backup (Time Machine will see it as a network share)
sudo tmutil setdestination -a "smb://user:[email protected]/time-machine-macbook"
You can see if it's ok with:
tmutil destinationinfo
> ==================================================
Name : time-machine4
Kind : Network
URL : smb://kenji@realserver._smb._tcp.local./time-machine
ID : D820D053-C74A-4A06-A7E1-E60C8EA7934F
====================================================
Name : time-machine-macbook
Kind : Network
URL : smb://[email protected]/time-machine-macbook
Mount Point : /Volumes/time-machine-macbook
ID : F707BD0B-64DF-4DB6-A3B7-824470FB5EB2
Then start a backup with tmutil startbackup and mount will show:
/dev/disk3s1 on /Volumes/time-machine-usb (apfs, local, nodev, nosuid, journaled, noowners)
//[email protected]/time-machine-macbook on /Volumes/time-machine-macbook (smbfs, nobrowse)
You can see detailed progress with tmutil status:
Backup session status:
{
BackupPhase = Copying;
ClientID = "com.apple.backupd";
DateOfStateChange = "2018-06-28 17:38:21 +0000";
DestinationID = "F707BD0B-57DC-4DB6-A3B7-824470FB5EB2";
DestinationMountPoint = "/Volumes/Time Machine Backups";
FirstBackup = 1;
Percent = "0.08711567546702646";
Progress = {
TimeRemaining = 32679;
"_raw_totalBytes" = 355694600192;
bytes = 34429528173;
files = 887351;
totalBytes = 391264060211;
totalFiles = 2922384;
};
Running = 1;
Stopping = 0;
"_raw_Percent" = "0.09679519496336274";
}
In my case, near 1000000 files were done in about two hours (USB2 disk penalty, versus more than 8 hours via Wi-Fi), I calculate percentages with a small script:
tm-progress.sh
Files : 918702 / 2922384 (31.43%) - Bytes : 32.21 GiB / 364.39 GiB (8.84%)
We can here that many files can make Time Machine to progress "slowly" in Bytes, but nearly 1/3 of files have been copied.
Next step, when backup is finished, plug the usb drive to your realserver and copy the sparsebundle over the "uncompleted one" (or in the shared folder). Of course, Time Machine should be disabled during this step to prevent mounting a partially copied sparsebundle (and maybe corrupting it)
I have used an apfs drive to benefit of snapshots (to be able to revert to a previous "backupdb" in case of sparsebundle corruption, not tested yet)
Edit: even faster mode :
Once the backup has reached BackupPhase = Copying to make it faster you can make the backupbundle mount directly (without sending every operation through smb) by canceling the backup, renaming My-Computer.backupbundle to something like 1My-Computer.backupbundle, and creating a symbolic link :
ln -s /Volumes/time-machine-usb/1My-Computer.backupbundle /Volumes/time-machine-macbook/My-Computer.backupbundle
This tricks timemachine into following the link to the backupbundle localy, and not mount it through smb, which speeds up the backup. Make sure you move the backupbundle back when you have finished your local backup.
See my other answer first which is a lot simpler!!
This is Kenji's answer ("ıɾuǝʞ" above), reworked painfully and explained by a complete noob (myself) for other complete noobs. I also added an important workaround in the last step:
Better later than never, here is a hack to achieve this:
Open Terminal.app and enter the following command:
sudo ifconfig lo0 alias 127.0.0.2/32Plug in your usb drive
- Go to
System Preferences/Sharing Open the lock in the bottom-left corner
(Whenever asked for your password, go ahead and enter it)
Tick "File Sharing" on the left pane.
- Tick
Optionsbutton and activate both SMB and AFP - Click the
+sign in the middle pane (titled "Shared Folders") and locate your USB drive. Create a folder (e.g. "time-machine-macbook") and select it to create the shared folder. Then, add a destination backup (Time Machine will see it as a network share), using the following command in Terminal.app:
sudo tmutil setdestination -a "smb://user:[email protected]/time-machine-macbook"(If you get an error that Terminal needs more access rights to your disk, then go ahead and follow the instructions of the error message to give such rights and repeat this step.)
You can check if it's ok with the following Terminal command:
tmutil destinationinfoAnd you will get the following reply on your Terminal window:
================================================== Name : time-machine4 Kind : Network URL : smb://kenji@realserver._smb._tcp.local./time-machine ID : D820D053-C74A-4A06-A7E1-E60C8EA7934F ==================================================== Name : time-machine-macbook Kind : Network URL : smb://[email protected]/time-machine-macbook Mount Point : /Volumes/time-machine-macbook ID : F707BD0B-64DF-4DB6-A3B7-824470FB5EB2Then start a backup with Terminal command:
tmutil startbackupTerminal command
mountwill show (among others) something like:/dev/disk3s1 on /Volumes/time-machine-usb (apfs, local, nodev, nosuid, journaled, noowners) //[email protected]/time-machine-macbook on /Volumes/time-machine-macbook (smbfs, nobrowse)`You can see detailed progress with Terminal command:
tmutil statusWhere you'll get something like:
Backup session status: { BackupPhase = Copying; ClientID = "com.apple.backupd"; DateOfStateChange = "2018-06-28 17:38:21 +0000"; DestinationID = "F707BD0B-57DC-4DB6-A3B7-824470FB5EB2"; DestinationMountPoint = "/Volumes/Time Machine Backups"; FirstBackup = 1; Percent = "0.08711567546702646"; Progress = { TimeRemaining = 32679; "_raw_totalBytes" = 355694600192; bytes = 34429528173; files = 887351; totalBytes = 391264060211; totalFiles = 2922384; }; Running = 1; Stopping = 0; "_raw_Percent" = "0.09679519496336274"; }Of course you can also have a rough idea of the progress by opening Time Machine where you will get the total MB copied as well as a calculation of the time remaining.
In Kenji's case, near 1000000 files were done in about two hours (USB2 disk), versus more than 8 hours necessary via Wi-Fi. My results were quite faster with a USB3 disk. In 2h I had backed-up more than 500MB.
Next step, when backup is finished, plug the usb drive to your realserver and copy the sparsebundle over the "uncompleted one" (or in the shared folder). Of course, Time Machine should be disabled during this step to prevent mounting a partially copied sparsebundle (and maybe corrupting it). I have used an apfs drive to benefit of snapshots (to be able to revert to a previous "backupdb" in case of sparsebundle corruption, not tested yet)
If #12 above doesn't work and Time Machine cannot backup TO the really-networked drive (but may possibly be able to read it), then the workaround is to copy the backup bundle inside a new sparsebundle! Awkwardly, Time Machine can use networked sparsebundles as backup destinations (but not it's own backupbundle!).
Have your drive connected via USB (for speed) and use Disk Utility to create inside it a sparsebundle with the necessary size to fit all your backup. This might take a few hours depending on the size and speed, so choose to do it overnight. If you don't have enough drive space, then unfortunately you should remove your previously created backup and re-create it later on from the beginning inside the new sparsebundle.
To create the new spasebundle, open Disk Utility, click File/New Image/Blank Image and in the pop-up window add a filename (e.g. BackupBundle.dmg), no tags, choose to be inside your USB drive root, choose a volume name (e.g. BackupBundle), size larger than your HD size, format definitely Mac OS Extended (Journaled), no encryption, Single partition - Apple Partition Map, and finally sparse bundle disk image. Check again your selected size (sometimes it gets back to default) and hit save.
Hours later, when it's over, you may test your new sparsebundle over the network. Connect your drive to your router, open Finder, and double click your BackupBundle.sparsebundle. You should see a new disk on the sidebar and on your desktop called BackupBundle. Then open Terminal and see if the sparsebundle can be added as a backup destination. If not, then you can set it manually via Terminal.app:
sudo tmutil setdestination -a "/Volumes/BackupBundle"After all this, you can copy Time Machine's backupbundle inside your BackupBundle.sparsebundle. This will also take hours, so you may want to do it the next night. Alternatively, if you didn't have room in steps 14-15 and you had to delete it, you can set Time Machine to use it as backup destination when connected via USB and then again after the first full backup is completed to select the same destination via network.
Good luck!
Note: This is not a solution to the problem but provides some insight into what is happening.
I followed the instructions for Quick Apple Raspberry Pi Machine and formatted a hard drive to HFS+ and installed netatalk on a Raspberry Pi 3B clone; everything worked fine.
I went into Time Machine settings and the network drive was recognized and added. Since this was over ethernet, the backup took about 13 hours to complete.
I did try connecting the drive to my Archer AX50 and configured the settings for a Time Machine shared drive. Time Machine did not see the drive. This seems logical since the router shares the drive using Samba/SMB, not netatalk.
Conclusion:
A recent update to macOS Sonoma has broken the ability for Time Machine to see a network drive; this is probably somewhere within the Samba/SMB protocols implemented by Apple.
For Posterity, this appears to have been resolved at some point between 14.4.1 and 14.5. But is not in the release notes that I could find. Potentially an unexpected consequence related to another issue.
I am trying to have one drive that a few macs can connect to either by USB or ethernet possibly sharing this drive from another mac's USB port or NAS.
First, is this possible to do? And what connections would be best for each laptop to be connected to the drive using USB I prefer to have multiple macs backing up at the same time, so not sure if a USB hub would work well for this option so my next thought was to connect this external backup drive to a mac using its USB port then within that mac share this drive on the network? Or Nas?
This answer is from 2013. Recent versions of macOS prefer SMB for Time Machine. AFP isn't really used for anything anymore.
For Mac OS X 10.5-11 (before Sierra)
When you click the "Options..." button in the File Sharing preferences, is "Share files and folders using AFP" enabled? Time Machine over the network requires AFP, so it won't work if only SMB is enabled.
You may also need to disable SMB. I am not exactly sure why this is the case, but sometimes the SMB share takes priority and Time Machine can't seem to see the AFP share. Note that this will prevent Windows clients from connecting to file shares.

Because your Shared drive is not a TimeMachine enabled shared volume.
TimeMachine have special requirements using AFP as pointed out by gabedwrds thus thoses (eg. AFP Replay Cache) are not necessarily included with "OSX Client".
You should enable a "TimeMachine Server" in order to share an external disk accross the network.
You may try using the Terminal if you are not prepared to buy "Server.app". But you're talking about data backup therefore you want to be sure about consistency and recoverability ! Other backup solutions such as the excellent "Carbon Copy Cloner can achieve this without the "Server.app" and you may get free of charges similar results by using the rsync command from the terminal or using Automator.app…
If you don't care about using an unsupported solution and you are willing to take the risk of being in the so called "poo" :
• Either show unsupported network volumes :
defaults write com.apple.systempreferences TMShowUnsupportedNetworkVolumes 1
And then have a look in your TimeMachine system preferences…
• Or inputing the shared volume name manually therefore in your case type in the terminal :
sudo tmutil setdestination /Volumes/MBA\ TM
Then start your first backup :
tmutil startbackup
How to make Time Machine backups over network without OS X server?