![]() ![]() I know it is tempting to think Apple simply felt like ripping people off when they took away the promised Time Machine functionality of the AEBS, but the reason it was turned off is because it just does not work 100%. You can have it work the way you're expecting by using an actual supported configuration, and buy a Time Capsule, or share a drive from a 10.5 or 10.6 system for use as a backup destination. At worst it might start a new backup to the reconfigured image (especially if you alter the "computer name"), but i'd also expect it would stay married to it this time. Then once the renaming is complete, again use (System Prefs) Time Machine options to choose the newly renamed sparsebundle.Īs stated, i can't guarantee how 10.6 will react (as i still run 10.5). Probably best to have backups totally disabled during all this (not just turned off but use the options to tell TM to stop backing up to the current destination). while the mounted image should be named: Ifconfig en0 ether |sed '2!d s/^*// s///g'Īrmed with those 2 strings then, the sparsebundle should be named: But that article does include some steps needed to form the proper 10.5 filnames (for both the sparsebundle and its mounted image).īriefly, use Terminal to run the blue commands. Most of those steps you don't need of course, since your image already exists and works (mostly). Making Time Machine work with the ReadyNAS The full procedure is posted all over the net, with this page being (possibly) the original and (undoubtedly) the most well-known: Of course, i have no idea if 10.6 will actually play along with this or not. another component of that convention decrees that the *mounted image* has a name something like this: I also subscribe to the belief that things 'flow' better when the computer name isn't the default, which usually contains spaces and punctuation (e.g., "John Doe's iMac"). ![]() Whither collision avoidance for Time Machine?Ĭlick to expand.If all else fails, then renaming the items to adhere to (regular) Leopard's convention might be worth a shot. I believe Time Machine should be more elegant in its awareness of absent backup volumes. Third-party Windows apps like Nero could, of course, manage volume allowances correctly, despite the native Windows OS peculiarities. I'm not sure and don't care enough to boot into Windows to test.) Classic Windows would allow you to start writing the 1.5 MB file to the too-small volume, and then send back notice of the collision when capacity was reached, leaving the user to figure out how to recover the wasted time. Windows OS', on the other hand, have historically used "collision response". For example, the OS wouldn't allow you to attempt writing a 1.5 MB file to a 1.44 MB floppy. Macs have, historically, used "collision avoidance" to query a volume, determine its availability and capacity, and only allow valid events. In a very un-Mac-like way, Time Machine appears to employ "collision response" to tell itself "Fail! Couldn't complete.". How the hell can I prevent this situation from repeating itself?Īpparently, Time Machine does not query volumes to ensure their availability prior to starting a backup. which is where it should have been writing in the first damn place. the backup proceeds, correctly, to the original sparsebundle. delete the new sparsebundle and the TMP file, So, I stop the in progress backup by halting Time Machine, When the machine returns to range, Time Machine will eventually start the (timed interval) process of backing up, but will create a NEW sparsebundle - starting back at zero, attempting to back up the full contents of the relevant drive, despite the fact that there's a valid sparsebundle already present on the drive. They are used here only to demonstrate the problem case. NOTE: The above images belong to someone else.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |