1/18/2024 0 Comments Ubuntu samba time machineTwo long flat sections correspond with periods during which large single items were being copied. The number of items transferred changed even more erratically, and in quite a different pattern. These periods occurred when two very large files and large apps were being copied, and in the first two cases were followed by periods of reported rapid transfer. Shortly after 2030, there was a period of about 20 minutes during which no data was reported as being transferred at all, followed by a further flat section, and a final period of over 30 minutes with no transfer apparent. But, as shown here, this varied widely during the backup. The backup started copying files at just before 1900, and completed the whole backup of 405,718 files totalling 91.8 GB a little after 2200, a total elapsed time of 11,558 seconds, giving an overall transfer rate of 7.9 MB/s and 35 items/s. Both Macs again connected using Wi-Fi 802.11ac, which is commonly claimed to achieve a maximum data transfer rate of up to 866 MB/s.Ĭopying a standard 10 GB test file using the Finder with SMB took 842 seconds, giving an effective transfer rate of 11.9 MB/s for a normal copy across the same path. Its only exclusion, following the lessons learned last time, is a copy of Xcode, which previously took painfully long to back up. The client is an M1 MacBook Pro, making the first backup of the Data volume from its internal SSD using macOS 11.6. On this occasion, the backup was performed between the same two M1 Macs and the same SSDs as before, with my M1 Mac mini sharing an external SATA SSD as the backup storage using SMB in Monterey beta 10. This article looks at how that may have affected performance. Since then, Time Machine and SMB have both matured. The Time Machine from there on will be auto-mounting the share to perform the backup.Exactly six months ago, when we were running macOS 11.2.3, I looked in detail at the performance of Time Machine making backups to macOS network storage using SMB. Pick the available share from the list (named as configured in nf above). Now that is it mounted, go to Time Machine settings in System Preferences, and click Select Disk.Pick the Time Machine share and press OK.Press Command+K in Finder, type afp://windows-host-name.local, press Enter.Then on macOS, try to connect to it: Connecting from macOS and configuring Time Machine To test the whole thing, including the scheduler item, restart windows host. Enter the administrator account credentials as requested. Add arguments: -ExecutionPolicy Unrestricted -File c:\Scripts\wsl_startup.ps1.Delay the task: 15 seconds (just in case).Security Options: Check Run with highest privileges.Security Options: Select Run whether user is logged on or not.search for Task Scheduler and launch it.Using Task Scheduler, create a new task to launch the script on each Windows start: If logging is not needed and therefore the contents of the script condense to a single line it can be directly scheduled in the Task Scheduler (program name wsl, arguments sudo service netatalk start). To configure firewall to access the WSL instance, we will build on the excellent script shared here: Īdditionally, it may be helpful to start the logging service as well, just to be able to troubleshoot any possible runtime issues with the netatalk in the future.Ĭreate the script somewhere accessible, like c:\Scripts\wsl_startup.ps1, with the following content: Consequently, mDNS/Bonjour won’t work to advertise AFP shares and Time Machine services, but that’s not a big deal: windows host supports mDNS, so we can connect to it directly in the finder via Command+K, afp://windows-host-name.local. Unfortunately, it is not feasible to make it external without breaking everything around it, so we’ll instead create a port mapping. WSL 2 runs in a separate internal network connected to an internal Hyper-V virtual switch named WSL. Netsh advfirewall firewall add rule name = "Allow AFP connections" dir = in action =allow protocol =TCP localport =548 WSL 1 has better performance across file systems, which our use case might benefit from.As a workaround, the amount of memory available to the VM can be limited, as described in the Advanced Configuration WSL 2 consumes massive amounts of RAM and doesn’t return it.While WSL 2 offers better compatibility by means of full Linux kernel running in VM (see ), there are some issue which may make WSL 1 a better choice for our purposes, at least for now: In this article, we’ll document the steps to create a compatible Time Machine target via AFP using netatalk running under Ubuntu in WSL 2 or WSL 1 Selecting WSL version Time Machine on macOS does not like windows hosts as targets, likely due to noncompliance to Time Machine over SMB Specification. Connecting from macOS and configuring Time Machine.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |