EDIT: this thread seems to indicate that it will work and that there are additional ways to mount the backup and restore just the data using the migration assistant:
Thanks for your post. However, option-clicking on the time Machine icon allows you to choose a different disk, but nothing is listed in that dialog for me. The current Time Machine destination that I set up on the ReadyNAS already has two different backups: my wife's and mine - they seem to be on the same disk, though. I cannot see her backup from my Mac. So, if I were to replace my Mac, how would I be able to access my current Time Machine backup from the new Mac? Do you think that the Migration Assistant will be able to see those backups on the ReadyNAS?
How would I go about restoring files from a Time Machine backup stored on the ReadyNAS to a Mac different than the one from which the backup was made. For example, if my Mac has died and Apple replaced it with a new machine. How would I get the new Mac to see the old Mac's backup on the ReadyNAS?
OK, let me answer my own question, then. I ended up needing to restore from a Time Machine backup after I had my Macbook sent to an Apple repair depot by the local Apple store, and the Mac came back with the hard drive wiped out. So, I booted up with the installation Mac OS X DVD and chose to restore from a Time Machine backup. When I logged in as ReadyNAS (and the password created for Time Machine in my ReadyNAS), I was able to see every Time Machine sparsebundle that existed on my ReadyNAS. I could have chosen any sparsebundle regardless of my MAC address. In fact, I was connected to the network via Ethernet, whereas Time Machine backups were made over Wi-Fi; therefore, the MAC address of the adapter connected to the network when I was restoring was different than the MAC address that figured in the name of the sparsebundle that contained my Macbook's backups.
It took between three and four hours (according to the Time Machine estimate) to restore my Macbook (about 40 GB of stuff). I went to bed, so I don't know how long it was exactly, but I know for sure it was less than six hours. Once the Time Machine restore finished, and I restarted the Macbook, and everything came up like a charm! So, at this point I am happy to report that it was well worth my time to set up Time Machine on my and my wife's laptops. My Time Machine backups were being made based on the ReadyNAS native Time Machine support, not on the older hack. I did not have to issue any commands to get the Macbook to see the sparsebundles, but I did have to reformat the Mac OS X partition that Apple installed when they wiped out my hard drive. So, I loaded from the Mac OS X DVD twice: The first time to erase the HD, and the second time to restore from the Time Machine backup sparsebundle onto the blank HD. When reformatting the HD, I chose HFS+ non case-sensitive. I was never able to figure out if it was possible to run the Time Machine restore over Wi-Fi, but I had no problem doing it over Ethernet. It was probably good that I did not do this over Wi-Fi anyway because it would have taken way too long if it were possible.
I have an idotic question. following the link's instructions, I copied the hdiutil command with magpie blah blah blah reference. I pressed enter and the image has been created. Despite deleting the incorrect sparsebundle file from Finder, I tried to re-create the sparsebundle file using the correct references but terminal is saying that "Only one image can be created at a time". Please suggest what I can do to fix this?
Is it possible to access a time machine backup on a ReadyNas Duo from a Playstation 3 to show photos?
Don't believe the PS3 would be able to read the sparsebundle. Better to set up sharing of your photos on your NAS in such a way that they can be easily read by the PS3.
Is it possible to access a time machine backup on a ReadyNas Duo from a Playstation 3 to show photos?
Don't believe the PS3 would be able to read the sparsebundle. Better to set up sharing of your photos on your NAS in such a way that they can be easily read by the PS3.
Yes, indeed. Just wondered because it would be great to have a automagic backup with TM and be able to reach the files in my PS3...
I have a brand new 2110 and want to use TM to back up my iMac. Followed the instructions, and it worked like a charm.
Then, I changed the connection from my iMac to the router from ethernet to (very fast) wlan. Since then, the data transfer speed of TM, and TM only, has reduced to bytes per second (has been running for about 15 minutes now and transferred 46KB (!). Other file transfers to the ReadyNAS via finder etc work just fine.
I want to use the backup facility without the ethernet cable, but at this speed it is clearly not an option. Something is wrong. Any suggestions as to what that might be?
Re: what about a case-sensitive file system in .sparebundle?
btaroli wrote:
odysseus wrote:
... it creates a journaled HFS+ *case sensitive* file system. What are the implications of using a .sparebundle file with a presumably case-insensitive file system instead of a case-sensitive one for Time Machine? ...
There may be implications. What this depends upon is how the filesystem of your Mac(s) is configured. If you, for example, back up a Mac with a case-sensitive filesystem to a TimeMachine volume that is case-insensitive, then this can result in situations where files with different names (file vs fiLe) overwrite each other. So, from a TimeMachine perspective it is always safer to use case-sensitive filesystems.
There have been other threads discussing this issue. Do some searching. 🙂 In my case, I always use case-sensitive filesystems. It just avoids any confusion or sloppy behavior.
Hey folks,
I find the whole "case-sensitive (journaled) filesystem on a sparsebundle" aspect quite intriguing as well. Mostly because (as has been noted since 2 years ago): that's what Time Machine seems to *favor*... initially on sparseimages, and then later with sparsebundles. And —on the surface anyway— that fact seems to go against the grain of *non*case-sensitive filesystems, to which the OS (and 3rd-party apps) have defaulted for almost a decade now. Back in that "OLD" thread, i found posts by schalliol and m_stoll (as well as btaroli, toad and pjc) most interesting. [i had intended to use links there, but url tags seem to be prohibited?]
Anyway, i'm not posting to get any deeper into that puzzle... i just wanted to share a little tidbit i discovered. The man page for hdiutil has what i assume are typos in the -fs section. (i'm still on 10.5.8, but the online man page for Snowy shows the same error):
-fs filesystem where filesystem is one of HFS+, HFS+J (JHFS+), HFSX, JHFS+X, MS-DOS, or UDF.
It really bugged me that all of the blogs, articles, hints, threads, etc., all had to spell out "Case-sensitive Journaled HFS+" in qoutes on the command line (or script). Where (or what) is the corresponding acronym? [must be one since Time Machine/Capsule always use them.]
I've checked that with hdiutil imageinfo and diskutil info (and verifyVolume) and Finder. It's right: HFSXJ is indeed the proper shortname for "Case-sensitive Journaled HFS+", and apparently it's fully undocumented (or mis-documented perhaps).
I thought maybe at least btaroli might get a kick out of that. [and it may turn out that Apple always uses case-sensitive sparsebundles with Time Machine/Capsule for special reasons as yet unknown to us... because it sure seems odd otherwise.]
I have a new ReadyNAS Ultra 4 Plus with RADiator 4.2.15. I enabled Time Machine support in Frontview and was able to select it as a backup target in TM on OS X 10.6.5. But when the backup starts, it spins for several minutes "Making backup disk available...". It correctly shows the capacity of the TM space I have allocated (50GB). But after a few minutes it fails with "The file server NAS2 [the name of the NAS] has closed down." This is the same error I got with the NV+ and I have searched this forum for help with this, to no avail. No sparsebundle is created in the share (which I mounted from Finder.) If I try it again, I will sometimes see "Unable to get status of backup disk".
The documentation for this feature suggests it should "just work". How can I fix this?
Hi there. I've got a ReadyNAS Duo with Radiator 4.1.7. I've just replaced both the hard disk with Seagate as the Western digitals failed due to high load cycle count. I’ve rebooted, Raid 0 the volumes and restored my backup files. Problem is I had a to do a few reboots before I got all the setting right for Raid 0 and moving from my previous C and D volume to just a C volume.
Thing is, during one reboot I set up Time Machine in Frontview but forgot to do it this last time, when I set up a back up job to restore the sparsebundle. Now I can’t seem to get the Time Machine function to stay set - it always reverts to the default setting password and 0MBs of space, although Frontview indicates the setting change has been applied.
I've even gone through and deleted and created a new .timemachine folder on the C drive folder of the Duo but it still doesn't want to save the setting and hence the Time Machine volume
Thanks for the advice mdgm - I've done both a firmware reinstall, following the FAQ instructions, and a firmware upgrade (to the same firmware of course)... To no avail.
I think I may have to factory reset again, unless anyone else has some advice.
I updated the Firmware with the beta for Lion, and it seems to be backing up, but in the middle of connecting, on the Time Machine Preferences screen and when it started a back up this message popped up...
Something wrong with the volume's CNID DB, using temporary CNID DB instead.Check server messages for details. Switching to read-only mode.
And now when I connect to the NAS via AFP I don't see my shares, only the Time Machine stuff. I'm able to connect via CIFS, but last night was encouraged that AFP connections to my shares was better. Why did my AFP share connections disappear?
Installed the release version of Lion yesterday (sorry - been on holiday) and downloaded and installed the RAIDiator-4.1.8-T5 beta on my Duo. Works. Not hugely quick but it works! Maybe its because TimeMachine has been caching all the backups onto my internal HD - currently backing up about 40gb - but I did do a clean install of everything so it could have been a lot worse.
I've been using a ReadyNAS Duo to successfully backup my iMac for the last couple of years. Never had to do a restore but nice to know it's there if I needed it. I've been using the old method outlined here before the Time Machine feature was added to ReadyNAS with no issues. Recently updated to Lion and discovered problem with ReadyNAS and Lion and old method. Followed migration steps to move to supported ReadyNAS Timemachine function by moving sparsebundle to ReadyNAS Timemachine directory. After moving the bundle to appropriate directory, is visible if I login as ReadyNAS but not visible as an available backup under Timemachine. What do I need to do to make Timemachine recognize this as a viable backup? I've got a couple years of backups here. Hate to trash and start over.
Also, I'm on the 4.1.8 beta release the support Lion.
I found that OS X 10.6.8 worked flawlessly for months months on end with a ReadyNAS Duo when firmware version 4.1.7 is used. It was servicing two iMacs connected to the Duo via a netgear switch. If the Duo scheduled shutdown happened when Time Machine was running, it didn't seem to cause any trouble. Life was good...
However, updating the Duo firmware to 4.1.8 (how could I have been so foolish?) caused 'verification errors' to happen every few days. Sometimes these could be repaired with fsck, often not. After two weeks of this I reverted to 4.1.7 and all is now well again.
Last straw form me ready NAS Duo is a f*cking piece of sh!t. Time Machine is NOT suitable for a production business environment. It is SLOW.... continually crashes and it TOTALLY unreliable as a backup solution. Netgear should stick to what they are good at which is routers.
Tip on Entering correct information to ensure TM can find your NAS
Just been trying to reconfigure my set up.
I have had a Duo V1 working quite happily backing up via TM however I decided to carry out a bit of housekeeping following the failure of an Ext HDD I was using with my Macbook.
Although you can change your user name and password to anything you like. To login and successfully select your NAS drive, the name used for TM to find your NAS is fixed and you should always enter 'ReadyNAS' and then you should enter the password you used when setting up TM via Raidiator. Otherwise TM will not find your NAS and will give you the OSStatus 2.0 error message.
This seems illogical when you can change your username and password but there it is.
Seems so obvious when the username on the TM setup screen in Raidiator is greyed out so it is always 'ReadyNAS' but this can easily trip you up as it did me for hours.
While this link works, the link to 'Instructions here.' on that page does not:
If you are using RAIDiator 4.1.5+ on the ReadyNAS NV+, NV, Duo, 1100, X6, or 600, or RAIDiator x86 4.2.3+ for the ReadyNAS Pro or NVX, you can use the built-in Time Machine support on the ReadyNAS for a simpler of setting up your backups. Instructions here.
Could you please update that link? I have tried following the instructions in the post that follows this paragraph, but get stuck down on step 9. The NAS share is not visible. I like to think it is mounted, but I'm not sure (I'm very much a mac newbie).
Suffice to say, I'm keen to explore the simpler means of setting up the backup.
