Synchronising Aperture Libraries (.aplibrary files)

[flitter2009]

Hi,

Is there something specific that needs to be set to sync Aperture libraries (it's a .aplibrary) on SFFS latest (5.43a) to an SMB share (or anything else)?

When I try to sync my 20+Gb Aperture library it's only seeing 23.8Mb of it and not syncing properly.

Thanks!

[superflexible]

A profile should see all folders and files by default, with the exception of the Global Exclusion Masks. These are on the Preferences dialog, last tab sheet.

If the Global Exclusions don't cause this, can you look into the library and find some specific files or folders that are missing and give us some examples?

[flitter2009]

Hi,

It looks like I put the wrong filter in and it wasn't picking up everything. I am still having a problem with the Aperture library as it's got over 300,000 files below it and it seems to take ages to scan it when it's scheduled (24 hours instead of 6 when it's run interactive).

Thanks

[superflexible]

The speed probably depends on the storage that you sync with, or the connection. What type of storage is it?

[flitter2009]

Thanks - good thought. It was over a remote SMB connection to a NAS. I've changed the connection type to SFTP now and it's much much much faster! Thanks!

[flitter2009]

Well, not exactly working. It works fine in attended mode, but when I run it via the scheduler i'm getting this error during the SFTP setup...

Short Results: No access to sftp://server/Volumes/DroboPro/Aperture Backup
sftp://server/Volumes/DroboPro/Aperture Backup: Cannot access sftp://server/Volumes/DroboPro/Aperture Backup
(Connection lost (error code is 0) at 006BD024)
No access to sftp://server/Volumes/DroboPro/Aperture Backup, preparation not OK

I'm using username/password authentication here not certificates... anything I should be looking for?

[superflexible]

I don't know, maybe the NAS was in sleep mode or a Firewall or other security software interfered. Try to do a manual run, then cancel it and schedule a run for immediately so you know the situation is the same, as opposed to a few hours later where a lot of things may be different.

[flitter2009]

Looks like it just needed the scheduler restarted and it's great now!