Your milage may vary. If it goes horrifically wrong, I will update the thread. Next step is to create that form of sparsebundle on the drobo, and see if backing up direct is any faster… If not, this is a reasonable hack to get your initial vault on there, and then suffer the minor few MB of photos you do at a time to sync the vault.
Certainly more acceptable than over 24 hours…. OK, Happy to confirm with this that you can backup successfully to a created sparse bundle direct to the Drobo FS. This made a GB Library backup GB Vault that took nearly 30 hours copying direct take just under 3 hours instead. Done that, and initially saw an increase in speed. Save my name, email, and website in this browser for the next time I comment. Open Disk Utility from your Utilities folder. Copy the newly created image to your NAS drive.
Do the same for the sparse bundle disk image from your NAS drive. Leave a Reply Cancel reply Your email address will not be published. It seems to me I took a peek in my Vault a year or so ago and it seemed all the Projects were listed by Import dates only.
Is it easy to locate a particular project in the Vault? As you can see, neither have sensible names! PhotoJoseph — Have you signed up for the mailing list? When I contacted Apple Support back with the merge of the two, they suggested the managed library and vault backups. I rarely if ever use iPhoto. Time Machine backs hourly to the 2TB drive as well.
I had a major problem with OSX the other day, 2 days worth. No issues with opening Aperture Library. Good on the backups but yes offsite cloud is still an important part of that.
Seems simple: I have found a number of pictures scattered throughout my main library which should be in an other library. Moving them one by one is tedious in the extreme. But I cannot see how to move them easily into different projects in another library libraries. Can be done or not?
In the past, there used to be a considerable difference between vault and TimeMachine backups. For instance vaults did not contain previews before Aperture 3 and as a consequence where much smaller then the original library and TimeMachine would backup the entire library every time, even opening a library causes changes to the database files resulting in a flooding of the backup drive.
So why would anyone be using a vault nowadays, where you would have to trigger the update manually each time? This was a feature that was always in iPhoto but as far as I know that never made it to Aperture. If you back up to the Vault, then delete managed files not referenced! Try it out to test it to see for yourself.
Create a new Library, add two managed photos, back up to a Vault, delete one photo be sure to empty the trash , update the Vault, and check it. Great article, thanks. I created the vault as you described above and put it on the same Photo Backup drive. Also, there is no point in having a vault on my main drive same drive as Aperture library right? It seems rather pointless to use Vault. I shall not be bothering with Vault, but continue with backups of my libraries and my master.
Plus, you can have multiple vaults, and update them on a rotating schedule. Or four that you update weekly. Each one is a small delta to update, yet you have an archive that goes back by the day or week or whatever makes sense for you. Mine is a I think quite simple question: in order to have a general backup practice, which involves not only Aperture files, but also any other piece of information accross my Mac hard drive and other external ones, I use an incremental backup tool Carbon Copy Clonner, actually to back up everything to an external USB drive two of them indeed, for backup redudancy.
Am I right? Am I missing something? In the light of this practice, it seems that the Aperture Vault does not has much to offer, is that true? Great article, thank you.
The whole site is phenomenal. I just bought a 1TB gdrive which i am dedicating to vaults. I created a vault, directed it to the 1TB gdrive and then ran the vault to back it up. Everything seemed to be going fine, the progress bar popped up saying it was updating the vault. I assume that means nothing is happening and my vault is not backing up.
What have I done incorrectly? How unfortunate. You will most likely have to start the Vault creating process over again. The actual Library file, not including any unmanaged originals.
And you should have considerably more free space so you have room to grow. Thank you Joseph, yes I did force quit aperture. However now my problem is that when I try to assign the vault location to the new EHD I bought for that purpose it is saying it cannot find it….. Also, how do I find out the size of my library file? I just found my ap lib and it says it is GB so the 1 TB should be plenty thx. Did you reformat your new hard drive before using it? Something went wrong in building the Vault and it sounds like now the drive itself is having issues.
No I did not reformat the new hard drive before using it. I did not know I was supposed to, I just hooked it up. I created a new vault and started to run it a couple of hours ago.
I will let it go and see what happens. If it crashes aperture again or fails to make the vault I will start to learn about reformatting an EHD. Again, thanks for helping. All this seems overwhelming at times for a non- tech person like myself.
So, the vault did not work. I will look into that. I have a more pressing matter. I will give you as much info as I can. My current app lib is stored on a 2 tb gdrive. A few days ago I had a problem with it and it o longer would show up in finder.
They also told me to get everything off of the gdrive, reformat and start over. So I bought a Drobo 5d and all of the drives should arrive today. My BIG question:.
0コメント