Hot answers tagged

6

This is going to be a throughly unsatisfying answer, but it comes down to the fact that random network drives were not meant to be used as time machine backup targets. I'd wager one of the things you did in your guide was to run a terminal command along the lines of: defaults write com.apple.systempreferences TMShowUnsupportedNetworkVolumes 1 Unsupported ...


3

Below is a network diagram based on what I have read thus far. I have made some assumptions about the IP numbering conventions, but that will have no effect on the overall scenario. I am assuming that you are using two different subnets rather than 2 different classes of networks. But, either way, you have two very different network IP addressing schemes ...


2

Attached to an OS X Server you can use the RAID-volume formatted to HFS+ or ExFAT to create shares for Windows clients. After enabling the share it is accessible via AFP and SMB by default: Example screenshot OS X Server 3.2.2 Mavericks: Example screenshot OS X Server 5.0.15 El Capitan HFS+: Example screenshot OS X Server 5.0.15 El Capitan ExFAT: ...


2

Properly done you can achieve this by prioritizing one interface over the other. Prerequisites: two different networks (physically and logically) e.g. Ethernet: 192.168.0.0/24 and Wi-Fi 192.168.1.0/24 assign static IPs to the ethernet adapters on the source(s) and the target(s) with a proper net mask. A default gateway is not needed. In System ...


1

I ran into this problem a few years back and I found the cleanest way was to install Samba (which still supports the older protocols) via Homebrew and use that instead of the version built by Apple. I used these instructions, which are for Mavericks but I think they should still work for newer versions of OS X.


1

You should avoid using SMB on OS X (IMHO) as it has been buggy since the days of Snow Leopard (10.6), for me at least. A quick Google search limited to this year alone brings up a myriad of issues regarding OS X and slow SMB implementations. There are a few things you can try: Use the SMB2 protocol by mounting your share cifs://<whatever your share ...


1

Prior to Mac OS X Lion, Mac OS X Client came with SAMBA Server and Client and what you defined to share was all that was shared. Since Mac OS X Lion, and continuing with OS X Mountain Lion and other releases of OS X, SAMBA has been replaced with SAMBX due to SAMBA moving to GPLv3. As a result SAMBA is basically broken in the OS since 10.7. The Mac OS X 10.7 ...


1

The problem is caused by Apples home made implementation of the smb protocol. Using smb3 won't make a difference. Server-Side Fix If you have control of the smb server (Samba?) then you can fix this issue by enabling the vfs_fruit module. If you are not using Samba then you'll need to find another way to enable "Alternate Data Streams" (ADS) and ...


1

The problem is caused by Apples home made implementation of the smb protocol. Using smb3 won't make a difference. Server-Side Fix If you have control of the smb server (Samba?) then you can fix this issue by enabling the vfs_fruit module. If you are not using Samba then you'll need to find another way to enable "Alternate Data Streams" (ADS) and ...


1

In case you haven't found a solution yet, in the guide I was following it never mentioned to run the tmutil utility to set the backup drive via command shell, so just run the following command on a Terminal and you will have the disk selected on Time Machine Preferences: sudo tmutil setdestination "/Volumes/Time Machine Backups/" Remember to change the ...


1

Most of the problems I seem to have with this kind of thing come from the ACL rather than the basic permissions. Usually what I end up doing to fix the problem is to format another drive to get the default permissions and ACLs then use these commands to copy them to my old drive: chown $(stat -f%u:%g "$srcdir") "$dstdir" # Copy owner and group chmod $(stat ...


1

It is an issue with Apples smb implementation. They used to use Samba but because of licensing issues they have now created their own smb client. There are two solutions you can choose from: Configure the server to play nice with Apple's smb (if you have access to the server). You can do this by enabling the vfs_fruit module in samba. Replace Apple's ...



Only top voted, non community-wiki answers of a minimum length are eligible