NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Time Machine ignoring maximum size?
Hi Guys,
I've just installed a 2TB drive into my ReadyNAS Duo v1, replacing a failing 500GB unit. I run as JBOD and all is good as I've no critical data stored. I also recently upgraded my iMac to Mavericks and, thinking I'd take advantage of the extra space, I enabled Time Machine on the ReadyNAS and experienced the failures to connect.
Sooo, reading round this forum, I installed 4.1.13RC and asked for a 1024GB Time Machine in Front View. I rebooted both the NAS and the iMac and lo and behold a Time Machine drive appeared and I kicked off a backup...
What I didn't notice is that it said there was 1.98GB available in the Time Machine Prefs page. I took a look in the Info.plist in the sparsebundle and yep, it seems to show there's 1.98GB available as well.
I don't want all of my new drive taken up with Time Machine (I already have a 2TB Time Machine connected to the iMac itself, this is a secondary backup, so retention time is not so important to me).
I'm in the process of deleting the sparsebundle and starting over again, but I expect the result to be the same - how do I get Time Machine to respect the maximum size limit I set in FrontView? Or have I discovered a bug in the RC?
Thanks for any help!
I've just installed a 2TB drive into my ReadyNAS Duo v1, replacing a failing 500GB unit. I run as JBOD and all is good as I've no critical data stored. I also recently upgraded my iMac to Mavericks and, thinking I'd take advantage of the extra space, I enabled Time Machine on the ReadyNAS and experienced the failures to connect.
Sooo, reading round this forum, I installed 4.1.13RC and asked for a 1024GB Time Machine in Front View. I rebooted both the NAS and the iMac and lo and behold a Time Machine drive appeared and I kicked off a backup...
What I didn't notice is that it said there was 1.98GB available in the Time Machine Prefs page. I took a look in the Info.plist in the sparsebundle and yep, it seems to show there's 1.98GB available as well.
I don't want all of my new drive taken up with Time Machine (I already have a 2TB Time Machine connected to the iMac itself, this is a secondary backup, so retention time is not so important to me).
I'm in the process of deleting the sparsebundle and starting over again, but I expect the result to be the same - how do I get Time Machine to respect the maximum size limit I set in FrontView? Or have I discovered a bug in the RC?
Thanks for any help!
9 Replies
Replies have been turned off for this discussion
- *Sigh*
Ok, so I deleted the sparsebundle and set it up again, this time requesting 900MB for Time Machine. I added the drive to my iMac Time Machine setup, and it says "ReadyNAS 1.98TB of 1.98TB available"
So again, it appears to have let Time Machine have the full 2TB. What is going on? Any thoughts? :( - I am seeing the same issue regarding maximum size. Basically did the same steps you did (delete sparse bundle and recreate) and it still shows all 6GB of my NAS is available for backups.
Any advice anyone? - Do Netgear support read and reply on these forums or is there another route I should go to discuss this issue with Netgear?
Thanks - Don't know if they read or actually respond to these messages. I am having the same issue as you, but I have an Ultra 4 Pro which is an X86 based NAS. After I posted here I went to the beta firmware forum for X86 systems and left a bug report for the firmware developers.
http://www.readynas.com/forum/viewtopic.php?f=51&t=73767
Maybe you can post something on the beta firmware page for your Duo here:
http://www.readynas.com/forum/viewforum.php?f=17
I think the issue is that the commands previously used by Netgear to limit the size of the sparsebundle have changed in Mavericks (or worse yet have been eliminated). Hopefully they can get this sorted out soon. I think they have not heard more complaints about it because it only affects people trying to create a new backup. If people are still using the backup sparsebundle that was created prior to the release of Mavericks the issue probably does not come up.
Here's to hoping that it can be corrected in the near future (or at least Netgear acknowledges it)! - Thanks, yes, certainly seems like you've hit the same problem. I've posted on the beta firmware page so let's see if anything happens :)
- Same here with an ReadyNas NV+ v2 running 5.3.10-T3.
- So I took this up with Netgear, and so far all they've suggested is I re-install the firmware on the unit. I've read too many people having issues after re-installing firmware and to add to this, Netgear will give me no assurance that this will do anything at all - i.e. they're just telling me to effectively turn it off and back on again, in IT Crowd terms :)
If anyone would like to try a firmware reinstall to see if it makes a difference, I'd love to hear about it. Until they actually tell me they've replicated and this would solve the issue, I'm no further along. - Brilliant! Thanks 2Nutz, that has fixed my unit as well!
I pointed the Netgear "support expert" at the thread. Hopefully they'll get the fix rolled into 4.1.14...
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
