Time Machine will handle that. You’ll have to manually mount the share the first time probably, but after the first backup is complete you won’t have to worry about it.
Looks like this is a common problem with TimeMachine. Google shows many complaints about this error on various network destinations. It appears some people have been able to resolve it by coping an existing sparsebundle backup to the new destination.
http://time machine the selected backup disk does not support the required capabilities
Just wanted to confirm this is correct-
remote france.privateinternetaccess.com 1198
client
dev tun
proto udp
resolv-retry infinite
nobind
persist-key
cipher aes-128-gcm
auth sha256
ncp-disable
tls-client
remote-cert-tls server
auth-user-pass credentials.conf
comp-lzo
verb 1
crl-verify crl.rsa.2048.pem
ca ca.rsa.2048.crt
disable-occ
@jbrodriguez
I know you’re waiting for 6.7 stable to make modifications. Just wanted to add another item in your radar.
When trying to start, stop, access docker controls I get this-
I notice that this script assumes that the syslog share is "cache only". Mine is located on the array with cache "No". Is there any reason why the share needs to be on cache, or is this just user's choice?
I have been using a script to prevent the .Recycle.Bin folder from being deleted so that I could use it with a couple of dockers.
echo "" > /mnt/user/Media/.Recycle.Bin/placeholder.txt
Does this mean that I no longer need it?