I’m a new user of a WD EX2 Ultra. I setup a Time Machine share, configure it in the NAS Settings, tell my Big Sur laptop to backup there, and it runs for 100 GB then stops. When I try to tell the backup to recommence, Time Machine reports “Looking for backup disk…” and never finds it. I get an error to try again when the NAS is available.
If I go into “select disk,” my Time Machine share shows up twice, once with “_smb_tcp” appended to the device name, and the user/pass prepended.
I’ve tried this several times, deleting and recreating the share. I’ve tried it logging into the NAS with my username/password, and also with the NAS configured to be public and logging in as Guest. I get the same thing every time.
I having an issue connecting getting my Time machine to connect after grading to WD OS5. The machine is currently indexing (21%) - is that why I cannot use my TM to connect because of the indexing? Any ideas?
Sort of the same here.
Time Machine well set up with SMB on TimeMachineBackup share (as public share, so with “guest” access).
First back up went fine.
Now TM says it can’t find the share.
Private shares are accessible from Finder (as a logged users) but TimeMachineBackup share won’t load (despite being public). It makes an error and the Finder’s windows crashed with an error (“can’t fond the element…” here in French.
If you follow KBA, you should use Time Machine as Guest user.
However, it seems that if you are logged into your Shares as a private user then Time Machine will not start the backup. In this article below, WD even tells you to unlog from your private shares for Time Machine to work. How seamless…
But, then I tried to set up Time Machine with your private credentials. However, it seems in this case that Time Machine reverts to AFP as a guest user, whereas I want to use it with SMB.
@WDStaff Can you confirm? AND tell us how to both use Time Machine and private shares concurrentlyover SMB.
Nevertheless, it looks broken either from Finder or Terminal:
For this, one needs to remove the network share destination from the Time Machine preference panel and then add it again. It will silently fail on SMB and then offer to put credentials (choose guest) again but this time with AFP. It should then work.
How good for an update that is supposed to bring Time Machine over SMB for better reliability.
I’m having the same issue! I’m on a 3TB MyCloud trying to get my time machine backups to work again, before os5 I was able to backup no problem (using afp over a vpn too!) now I can’t even get it to work locally
Similar Guest Account authentication issues in setting up Time machine – Mac OSX 12.3.1 Monterey, My Cloud EX2 Ultra 16TB with OS 5.21.104.
Time Machine worked in 2020 and 2021 and then in March 2022 with the OS 5 firmware update, TM stopped working.
In the WD docs I found “Apple File Protocol (AFP) is no longer supported on My Cloud OS 5 firmware 5.19.197 and higher.”. I think their switch back to using SMB for TimeMachine has led to lots of unresolved issues.
Anyone know if it is possible to downgrade the firmware to an OS 5 version before 5.19.197 ?
I will post a new question in a few days with more details and the specific steps I have tried to resolve this.