NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
time machine
360 TopicsBacking up Time Machine to ReadyNas202 - Error
Sorry folks if this post has come up a few times...I"ve tried to post this question, and I don't see it showing up on the board...so not sure if I'm doing something wrong, or against rules. Anyway, here goes... When I try to connect my Time Machine to my ReadyNas 202, I get this error: "TIme Machine can't connect to the backup disk. The operation couldn't be completed (OSStatus error -1073741275.)" Any idea what I should do? [Screen shot attached] Thx!Solved5.2KViews0likes11CommentsTime Machine Constantly Failing After A Few Seconds - 6.9.4 (Hotfix 1) - MacOS High Sierra (10.13.6)
Recently, after several months of sucessful Time Machine backups, I received a Mac system error that there was something wrong with my Time Machine backup, and the system would need to create a new one. I clicked on OK, and the system did what it had to do. Since then however, I have been unable to get the first (new) backup to be successful to the ReadyNas 214. I have been able to make Time Machine backups to an external 2TB drive, without any issues. When backing up to the RN disk , the backup goes through the Preparing backup... stage, then copies less than 1 GB of 523 GB (the most recent test got to about 300MB, and the one before, 74MB, and the one before that, about 118 MB), only to begin the Stopping...process without any other error. On the RN itself, I have: removed any Private TIme Machines, rebooted, and added them again. removed the Public Time Machine, rebooted, and added them again. rebooted the machine for the sake of rebooting. confirmed there is ample space for the drive, both in relation to available space on the HD and in relation to the required space for the first backup. On my Mac, I have: removed any Private TIme Machines, rebooted, and added them again. removed the Public Time Machine, rebooted, and added them again. rebooted the machine for the sake of rebooting. In the HD, I have confirmed that the SparseBundle files are deleted for the drives I was removing, and created when a drive is created on the RN (image attached). As already written, I have been able to successfully backup to an external drive without any issues. Thanks for any insight you can provide. 6.9.4 (Hotfix 1) - MacOS High Sierra (10.13.6)1.3KViews0likes1CommentReadyNAS 6.9.4 breaks timemachine backup
Upgrading to 6.9.4 on RN314 has broken Mac timemachine backups using AFP on High Sierra. It also fails on El Capitan which worked previously. Failure mode is OSStatus 89 on the timemachine setup dialogue. I know that the Mac is seeing the timemachine volume and it fails as expected with an invalid logon. It makes no difference if a private timemachine is used, tried turning timemachine off and then on, change password, tried to use SMB, reboot ReadyNAS etc. etc. Downgrade to 6.9.3 and everything works, creates new sparsebundle and then backs up. This looks like an OS bug in 6.9.4.1.5KViews1like3CommentsMac Restore from Time Machine from ReadyNAS fail.
Hi all I have recently changed the HDD of a Mac of mine and put a new SSD. After the OS installation, El Capitan, it asked as usual if I wanted to restore all the files from a Time Machine Backup. The problem is when it started searching in the network, the Mac couldn't find the time machine backup located in the readynas, which was in the same network and active. It has been the only moment that I needed my readynas and it failed... I tried to put manually the server address, afp://...etc.etc., that I have found on the properties of the backup folder in the ready nas, but it couldn't access it too, as if it wasn't visible. Luckily I have managed to do it another way using the old HDD, but what about a real failing of the whole HD happened? Can you suggest me the proper how-to in case it should happen in the future? Thanks a lot. Giovanni1.2KViews0likes2CommentsX-RAID with one disk offsite?
For 8 years with my predecessor RND210, used soley for Mac's TimeMachine, I have successfully stored one disk offsite, then periodially returned it to resync, then returned it to offsite. Of course, I fully understand and accept I'm without current redundancy during periods of storage. But I always have at least one current disk at ALL times, don't I? This protects my offsite disc, only since last sync, from a NAS theft and fire. To me, this is a reasonable value compromise. Now that I've upgraded to a RN212, I'm reevaluating my strategy. I like even better the idea of rotating a 3rd disk, as proposed in this post. But I don't buy the reasons for abandoning either strategy, often pitched by NAS purisits and NETGEAR Techs who want me to acquire more equipment. I don't care how long the resync takes or lack of current redundancy. Do backups pause while resyncing? Does this cause more drive thrashing than it would otherwise? I welcome your facts as well as your opinion. Here are the logs for one cycle (in reverse chronology): Volume: Volume data health changed from Degraded to Redundant. Volume: Volume data is resynced. [took 4 hours after 26 hour disk separation] Volume: Resyncing started for Volume data. Disk: ... was added to Channel 2 of the head unit. Volume: Volume data health changed from Redundant to Degraded. Disk: ... was removed from Channel 2 of the head unit.Solved2.2KViews0likes5CommentsCannot connect Time Machine to my NAS
Have been using Time Machine to back up my MAC to my NAS without issue until recently. Now the NAS shows up in the Time Machine but when I try and connect get an alert that tells me there is a problem connecting to the NAS: "The server may not exist or it is unavailable at this time. Check the server name or IP address, check your network connection and then try again." I can see the NAS in Finder and log in through Safari (just completed a NAS firmware update). Any help greatly appreciated.1.3KViews0likes1CommentCannot connect Time Machine with SMB only AFP
I have a MB PRO running El Capitan - v10.11.6 and ReadyNAS 212 with firmware 6.9.3. If this matters, NightHawk R7000 router. I'm trying to back up multiple MacOS devices using private Time Machine. By default, Netgear OS is set to SMB (and warns if switching to AFP). I am unable to see any partition or share under Time Machine for ReadyNAS user when set to SMB. I see the ReadyNAS device under the finder and can access the directories. But, my Time Machine can not see any partitions; no matter what user i login to the volume as. I enabled AFP on the ReadyNAS and logged-in with admin. That seems to bring up a Private Time Machine partition that is usable. 1. Does anyone have a solution to using SMB for Time Machine instead of AFP? 2. How do I remotely backup a MacOS computer to Time Machine on ReadyNAS? Do I really need to setup a VPN or is there another way to see the remote user's Time Machine partition? Thanks in advanceSolved2.6KViews0likes1CommentBest (and easiest?) way to transfer Time Machine backups from Drobo to new ReadyNAS
Hi- After enough issues with my Mac recognizing a Drobo or Drobo disconnecting itself, I purchased a ReadyNAS. On the Drobo, I have Time Machine backups from various computers, as well as other files (not in a .sparsebundle or backupsdb format) that I want to copy over to the ReadyNAS. Ideally, backing up my Mac would continue to use the same TM folder that was created on the Drobo. What is the best way to do this? I've considered simply copying directories over via SMB, but I also noticed that ReadyNAS hides the .sparsebundle . It surely couldn't be as simple as removing the hard drives from the Drobo and putting them into the ReadyNAS, could it? Thanks for ideas.3.1KViews0likes7CommentsTimemachine not seeing ReadyNAS
I'm missing something here. Just upgraded my 6350 to (3) 4TB drives, no prob. Upgraded firmware to v 6.9.3. Backed up my iMac with no problem. Now trying to backup my daughter's macbookPro to it as well but her computer does not see the NAS in timemachine. If I go to Finder, it sees it and accesses it. But it doesn't see it in Timemachine to schedule auto backups. What am I missing here? I can log in to the NAS just fine through the admin page and it sees it. Just timemachine on the laptop doesn't see it.1.3KViews0likes3Commentsremote Time Machine via VPN
If you want to initiate a Time Machine Backup of your Mac remotely via VPN the discovery of the Time Machine volume fails because Time Machine Volumes are propagated vie Bonjour and this uses a Broadcast IP-Adress wich is of cause not routed via a VPM. Setting up a DNS-Server to establisch Wide-Area-Bonjour causes to much effort. This can be done more easily via a Mac shell command. If you have assigned personal Time Machine volumes the Mac Shell command is used ass follows: sudo tmutil setdestination -p smb://user@host-IP/user\'s%20timemachine Whereas user is the user name on the NAS, host-IP the IP-Adress of the NAS. After that you are asked to enter first the password of the MAC administrator, then the password of the NAS-user. Make sure you use the IP-Adress of the NAS and the IP-Address is set fix ore assigned permanently to the MAC-Adress of the NAS by your router. If your VPN-Connection is stable the command shoud end without enny error message. I have personally tried that with a Fritz!Box VPN. I have a 500 Mbit/s down and a 50 Mbit/s Upstream. When the network connection on your remote site is fast enoungh, this should work fine.2.9KViews0likes1Comment