japangerma.blogg.se - Wdmycloud unable delete time machine backup mac

#WDMYCLOUD UNABLE DELETE TIME MACHINE BACKUP MAC FOR MAC#
#WDMYCLOUD UNABLE DELETE TIME MACHINE BACKUP MAC PASSWORD#

#WDMYCLOUD UNABLE DELETE TIME MACHINE BACKUP MAC PASSWORD#

Note WD says your admin user must have a password in order to enable TimeMachine restores, so now’s a good time to be sure that’s the case.Īfter I did all that, TimeMachine is working again. On the Mac configure TimeMachine to use that new share.

#WDMYCLOUD UNABLE DELETE TIME MACHINE BACKUP MAC FOR MAC#

Configure your M圜loud: Settings to use the new share for Mac TimeMachine backups.Create a new share to use for TimeMachine backups.But found after a year for it not to be practical as the drive is basically too slow for terabytes of backup, and restoring and backing up take quite some time. I used it for a while for time machine backups for my iMac and MacBook. After you delete that share, all the backups in it are gone. Hi folks I have a 8TB M圜loud home, I’m running the latest firmware and app, and running the latest version of Catalina (10.15.2). Go to Shares, click on the share with the TimeMachine backups, and click on the icon that looks like a paper folder with a minus sign, which means to delete the share.In the Share Access section find the share with the TimeMachine backups, change its permissions so Admin has read/write permission.Log in as admin, go to Users, click on Admin.I discovered a solution that may be helpful and save others a lot of time and aggravation. On the M圜loud the backups were in a share folder with no permissions at all, so no obvious way to delete them. All attempts would look like they were working but ran forever without completion and not actually deleting the files. I tried using finder, of course SUDO via terminal, etc.

I searched and tried everything - there are many questions and answers about this online - but could not delete it. Long story, part of it is that it complained it could not delete the sparsebundle file or folder. I recently had a problem wherein TimeMachine repeatedly failed.