Aperture doesn't recognise network backup disk

I use Aperture (2.1.4) for processing pictures and back up the vault periodically (learned the hard way) to an external drive connected to my Time Machine. Set up fine under Leopard, the drive was recognised and I could update the vaults using Aperture from time to time. It was necessary to open the external disk via Network before Aperture 'saw' the vault, but that was no problem.
Upgrade to Snow Leopard and Aperture says no vault is connected (even when I have opened the disk using network even though the icon for the disk appears on my desktop).
Do I need to reformat the drive under SL (via a USB connection), reconnect the disk to Time Machine and then re-establish the vault?
Help - as it stands I cannot back up any photographs.

What is the file system on the remote drive?
I am using an Infrant ReadyNAS to hold a vault, but I created a Mac OS X "sparse image" with an HFS+ disk image on it. It continues to work fine on Snow Leopard (I mount the network share, and then double click the .dmg file which then mounts it on my host, and I vault to it). If you have some sort of network drive on something like a LaCie or Infrant or anything that's not formatted as HFS+, I would anticipate problems at some point, as the file system just won't properly handle the names that Aperture uses within its vault.

Similar Messages

HT3275 Since updating OS to Mountain Lion from leopard, I get the following error message when trying to backup with time machine on external drive. Could not complete backup to media share. The network backup disk does not support the required AFP feat

Since updating OS to Mountain Lion from leopard, I get the following error message when trying to backup with time machine on external drive. "Could not complete backup to media share. The network backup disk does not support the required AFP features." What are AFP features and how do I get Time Machine to backup to my current external backup?

This means that your NAS does not support the required encryption. Update your NAS to the latest firmware or ditch it and buy a Time Capsule (they are the most reliable when using TM).

My Macbook doesn't recognise the startup disk

I started having problems with Yosemite and lion (installed in the same hard drive, different partitions) so i erase all and instal mavericks, the macbook is late 2009 stock but i don't have startup disk, when i install mavericks it tells me that wont boot and it went an error trying to install, so i am able to boot with the alt key but my mac doesn't recognise de boot disk, when i try to select the startup disk on preferences it tells me: "You can’t change the startup disk to the selected disk. The bless tool was unable to set the current boot disk.", what i can do, i can boot with the alt key but it doesn't boot automatically.

If you erase a drive, then in order to install Lion or later you must first install Snow Leopard 10.6.8. You can install Snow Leopard using the installer discs that came with your computer when it was new. You can then update the version of Snow Leopard to 10.6.8 by downloading the combo updater.

While trying to setup a time capsule backup to my MyBookLive external drive, I got the following error message: The network backup disk does not support the required AFP features. What's up with this?

While trying to setup a time capsule backup to my MyBookLive external drive, I got the following error message: The network backup disk does not support the required AFP features. What's up with this?

This means that your NAS does not support the required encryption. Update your NAS to the latest firmware or ditch it and buy a Time Capsule (they are the most reliable when using TM).

Network backup disk does not support the required AFP features

I have a mac mini with two (4T) hard disks each set as target in TimeMachine. Backups have been made on both for some time. This afternoon one of the disks is being rejected as target volume, with the "network backup disk does not support the required AFP features" error.
The sparse image on the disk that is the actual time machine target shows a modification tim of 13:09, time machine reports the last backup on that volume as made on 13:08. It seems the last successful backup was made at that time. The other TimeMachine target volume on the same min reports a last backup at 15:28
So why an error now? What has happend in the last hour, or so, to cause the disk to no longer be suitable? Why only on one virtual disk?
The mac mini runs OS X 10.9.4 (13E28), the disk with the failing backup volume is formatted with Case-Sensitive Journaled HFS+, the still working disk Journaled HFS+.
This may be related: A couple of month ago I lost the complete backup on that disk, when time machine conclude that the contents of the target volume was corrupt. At the time I blamed that at a failed backup when I had accessed the mini over ssh using SLINK when traveling. Maybe that conclusion is wrong and this is part of the same problem.
Any pointers on how to get my second backup disk working again would be much appreciated.
Eduard de Jong

The error message has disappeared!
Earlier this morning the disk has been used as target for a backup by time machine without triggering the error message. A backup 8 hours earlier has also been made to the same sparse image (looking at the folder names).

The network backup disk does not support the required AFP features.

I am trying to set up timeMachine on my new mac book pro over a regular home network on a shared network drive. I have tried everything but I keep getting "The network backup disk does not support the required AFP features." I am on lion with the lateset unpdate (10.7.4). I have even tried creating sparebundles on from tutorial that I have found online, but non of the hacks that I have tried seemed to work. Have anyone figured out a way around this? If so, can you share, it will be greatful. I could just buy the time capsule that apple sells but I already have a 2TB internal HDD in an old pc that's hosting my file server so no need for the time capsule hardware. Let me know if there is a way around this thank.

ookakaa wrote:
1) Apple time capsule
Or USB drive connected to a Time Capsule
2) NAS with the latest firmware
Not just any NAS. It has to support the communications protocols used by Time Machine (some involving security, some about error detection and handling). Some NASs never supported TM; some that worked on Leopard never got updated for Snow Leopard; and some that worked on Snow Leopard still haven't been updated for Lion.
4) Another networked mac (not a pc)
A Mac running Leopard 10.5.6 or later.
Are these the only options?
Those are the only options supported by Apple. Some other destinations may work, to some degree, in some circumstances. Some require "hacks" or other workarounds. Most are somewhat unreliable, and, may stop working at all on the next OSX upgrade.
Side note. I've been seeing some online post of how some people are setting up TM on a networked PC drive by setting up a sparsebundle like this site:
Any thoughts? I have tried some of these examples and it don't seem to work...
Some of those may have worked at one time, in some circumstances (2 are dated before Lion was released, the other is undated).
Wireless backups are tricky enough to a supported destination, with all the security and error detection and handling Apple has been able to employ. If your backups are important to you, don't trust them to a marginal scheme.
And, in any event, don't trust your backups to a single piece of hardware or software. See Time Machine - Frequently Asked Question #27 for an explanation and some suggestions.

AFP error for new hard drive for time machine The network backup disk does not support the required AFP features.

Purchased Seagate network drive, ethernet attached to wireless router, set up went well but attempts at backup with Time Machine failed. "Do I need to erase disk and reformat or is this error message "The network backup disk does not support the required AFP features" indicating some other error?

That means the NAS drive's OS isn't compatible with the version of OSX you're running. See if the maker has an update.
See #C16 in Time Machine - Troubleshooting.

Can anyone tell me what this Time Machine error means? The network backup disk does not support the required AFP features?

Can anyone tell me what this Time Machine error means? The network backup disk does not support the required AFP features?

AFP - Apple Filing Protocol
The Network Attached Storage (NAS) that you are pointing Time Machine at does not have the features needed by Time Machine in order to do its Thing. Time Machine needs some specific features that are not typically available on generic networked storage devices.
There are manufactures that support the Mac OS X HFS+ file system formats and implement all the needed AFP protocol packets necessary so that they can be used with Time Machine, but apparently yours does not.
If you are not using a networked mounted volume for Time Machine, then more information will be needed about your Time Machine setup.

HT3275 Time Machine gave me this message after updating to Mountion Lion "The network backup disk does not support the required AFP features."

After upgrading to Mountain lion, I got this message when it tried to backup to "MybookLive" network disk.
"The network backup disk does not support the required AFP features."
What are AFP features and why can I now not back up to my network disk?

I had a similar issue when I tried to do a network-share backup w Time machine when the share was on a Leopard OSX G5 Power PC.
I think Time Machine looks for a minimum feature set support from the afp mounted drives so they can be used with Time Machine.
Western Digital may have to update the firmware on your device to support the new afp features.
Hope this helps.

The network backup disk could not be accessed because there was a problem with the network username or password.

Hardware Information:
          MacBook Pro - model: MacBookPro6,2
          1 2.66 GHz Intel Core i7 CPU: 2 cores
          4 GB RAM
Video Information:
          NVIDIA GeForce GT 330M - VRAM: 512 MB
          Intel HD Graphics - VRAM: 288 MB
Startup Items:
          HP Trap Monitor - Path: /Library/StartupItems/HP Trap Monitor
System Software:
          Mac OS X 10.6.8 (10K549) - Uptime: up 0:0:48:37
Disk Information:
          TOSHIBA MK5055GSXF disk0 : (465.76 GB)
                    (null) (disk0s1) <not mounted>: 200 MB
MacBook Pro HD (disk0s2) /: 465.44 GB (440.47 GB free)
          MATSHITADVD-R   UJ-898
Have tried…
re-setting Time Capsule (soft and hard) and power disconnect
re-setting modem
changing passwords in all relative locations
deleteing file://localhost/Library/Preferences/com.apple.TimeMachine.plist
deleteing all mention of Time Capsule in Keychain Access
running KeyChain First Aid (no problem found)
Restarting computer
Time Capsule has a green light, other MacBook Pro backs up OK but this machine continues to receive above error message and will not Enter Time Machine producing the error message Your Time Machine backup disk can’t be found. Maybe I need to do something over or in a particular order? All help is appreciated!

With the TC plugged by ethernet into the computer.. still in full isolation to the network and with factory reset.. you can do another to be sure.
Please open the network preferences.. and check the IP the ethernet is getting from the TC.
It should be 10.0.1.2
I set it to this manually
Don't worry about all the rest.
If you open airport utility can it see the TC?
YES
If not then I think you have a major network issue on the computer.
Assuming you can see the TC in airport utility.. go to manual setup and the disk tab. Does the disk register any issues.. SMART should show it has verified.
Shows verified
Now go to finder..
Mount the drive manually via the top menu.. Go.. Connect to server.
And type in the address.. SMB://10.0.1.1
Did NOT work, however 10.0.1.2 did
That should discover the drive and ask you for credentials which after a factory reset will just be public as the password. The drive should mount and you can then see it in finder.
Yes, but I have been able to do this with the IP address being set automatically
I would deliberately use SMB. The other alternative is AFP://10.0.1.1 but that seems to be more problematic at times..
Once mounted point TM to the drive and see if it can find it and start the backup.. if it fails I think you have need to use the A5 in pondini's troubleshooting and see what you can do.
It failed and A5 makes NO difference.
A drive that won't mount is obviously not going to work.
Pondini is welcome to make comments... sometimes my Mac terminology gets a bit loose.. !! My recent convert status is visible .. !!
My other solutions.. since these are fairly old products.. the TC is more than 3years in all likelihood so outside warranty.. get a USB drive and plug it into the Mac and use TM to backup to that. If that works.. I would erase the hard disk in the TC and start over with both computers.. you will need to backup the other computer before you erase of course. Erasing and starting over does seem to help.
If there are no other suggestions, I guess I will try erasing and starting over. Thank you both for ALL your advice.

After motherboard swap, Time Machine doesn't recognise older backups

Hello,
After I had my motherboard replaced on my MacBook Pro, my older backups are not recognised. Is there any way to access this data?
Many thanks in advance.

Hello,
Time machine uses the MAC address to identify each computer and as your logic board now sports a new MAC address TM can't see it.
I haven't tried this but Barry Sharp, posting on macosxhints suggests:
If you attempt to backup after the MAC address has been changed the TM backup will indeed fail and report it cannot found the TM backup volume. This is because the hidden file with the name of the MAC address (minus the colons) does not match the new MAC address.
All that is required here is to goto TM Pref panel and click on the "Change Disk..." button and reselect the TM backup disk and then manually force a backup via the Dock's TM icon "Back Up Now". The backup will now run and the new MAC address will be created as a hidden file alongside the old one. You can use sudo to remove this old one.
TM backup will proceed as it would have normally done without the MAC address change and without a deep traversal of all volumes that have not been excluded ...
from:
http://www.macosxhints.com/article.php?story=20080128003716101
Note: he points out the original suggestion at the start of that hint is unnecessary.

ML loses network backup disk after reboot or sleep

I have two laptops using time machine to backup over the local network to a disk directly connected to a desktop mac. The desktop also backs up to the same disk quite successfully. Since upgradeing everything to Mountain Lion (10.8.1) the laptops keep losing access to the backup disk after sleeping or rebooting. Interestingly, they can autmatically find the backup IF I "enter time machine". But they never find it unless, after sleeping, I reselect the disk in the time machine preferences.
Any ideas?

I have two laptops using time machine to backup over the local network to a disk directly connected to a desktop mac. The desktop also backs up to the same disk quite successfully. Since upgradeing everything to Mountain Lion (10.8.1) the laptops keep losing access to the backup disk after sleeping or rebooting. Interestingly, they can autmatically find the backup IF I "enter time machine". But they never find it unless, after sleeping, I reselect the disk in the time machine preferences.
Any ideas?

Started slowly, doesn't recognise network, wrong date

started up my macbook and it started really slowly showing clank screens I hadn't seen before then once it had started up, it had not recognised my chosen network, the date and tme were incorrect and safari repeatedly keeps closing. I have tried updating the software but still the same problems.
Need Help!!

More than likely the PRAM battery is failing. I have the same problem and am contemplating changing it myself, not an easy task, or taking it to the Apple Store to see how much they would charge to change it. Actually my problems are worse than yours, if I sleep or shut down my MacBook it won't restart without trying about 50 times. As it is right now I never let it sleep and everything works fine.

IMac doesn't recognise the internal hard disk (intermittent)

Hi, I was wondering if anyone could give me an advice on this problem.
Background: A few days ago my iMac (20-inch MA877LL) would not boot up, it would sit on the gray screen with the wheel spinning for ever. I thought the OS might have got corrupted so I tried to re-install Snow Leopard from the CD. Installation fails with a message like 'the content of HD can not be changed'. I then went to Disk Utilities trying to repair the disk but had no luck with the repair so I decided to format the disk. I managed to get into my hard disk using the cmd R key combination at power up and backed up my essential files onto a external hard disk. I formatted/erase the hard disk (zeroed out) and tried to reinstall the Snow Leopard again. The installation failed again. Rebooted the system again and tried to re instal again but this time I got as far as the 'select the disk where you want to install Mac OS' but my Hard Disk is not listed, it's a blank list! Rebooted the maching again, tried the installation, this time it sees the hard disk but the installation fails again.
I have tried to change the boot source by hodling the 'alt' key down at power up, but I am only given the option of the CD drive with installation disk as the boot source i.e. no Har Disk. It appears that the Hard Disk is intermittently recognised and hence my problem with booting the maching when the problem started.
I am happy to purchase an internal disk to replace the existing one, but I have a feeling the actual Disk it's OK, after all I managed to access my data to back up and then format it with no problem. I just think there's a problem somewhere that intemittently doesn't recognise the Hard Disk.
Any suggestions will be much appreciated.

You need to have the hard drive replaced. The one that is currently installed has failed.

TimeMachine network backup crashing my computer

I have a USB drive attached to my router and available via samba. I've followed the instructions available from multiple sources online on how to set this drive up as a TM backup, and it works fine. However, every so often, I will notice that fsck_hfs is running, eating up 20% or more CPU, with kernel_task taking another 10-15%. When I disable TM or turn off airport, this problem ceases. If I leave fsck_hfs go long enough, my system locks up and I need to hard reboot.
Two questions: a) is this a known bug, and if so is there a workaround? b) can I tell my system not to run fsck_hfs on remote drives? I consider (b) a viable option and I really don't care about the consequences - I would much rather rebuild my TM sparsebundle every month then have my computer crash every day.

jdidion wrote:
BTW, are you saying that if I instead attach this drive to my linux server and attach TM via AFP that Apple will support this in the event that the fsck_hfs problem still occurs?
If it meets this criteria: +*If your backup disk is on a network, the network server must use Apple File Protocol (AFP) file sharing, and both your computer, and the networked backup disk, should have Mac OS X 10.5.6 or later.+*
It's way beyond my level of expertise, but this post in another forum may contain the key:
The technical reason why Apple limits Time Machine to 10.5 AFP volumes appears to be to prevent disk image corruption. There were additional features added to AFP in 10.5 to support Time Machine. These presumably allow the disk image engine to force disk image journal data to write out all the way to the disk. Without such features, a network interruption can result in a corrupted filesystem on the disk image despite journaling. Remember, journaling relies on the journal being written all the way to disk before the changes take place. If you can't guarantee that (e.g., because of network/NAS buffering) then the journal is useless. Time Machine appears to rely heavily on disk journaling to deal with network drop-outs, interrupted backups, and the like. Take this away and your data is at risk.
If the NAS you are using supports these features it should report them to the OS and you should natively be able to choose that volume. If you have to trick the OS to use the volume it means the NAS does not support it.
To summarize: if you care about your backup data you should avoid using non-natively supported AFP servers.

Aperture doesn't recognise network backup disk

Similar Messages

Maybe you are looking for