Backup vault size

My library seems to be growing larger and more rapidly than I would expect. I have about 28,000 photos. Most D200 jpegs about 5-6 GB, some older and smaller few thousand at 1-2 GB, about half -scanned slides and 35 mm about 8-10 GB. The vault size is 437 GB. Seems that on average I am using about 15 GB per photo. Recently I added 1118 scanned 35 mm avg 7-10 GB. They came on 3 DVDs - 1 about half full - est 11-12 GB of Jpeg data. I loaded them into Aperture and rebacked up vault and it grew by 45 GB - no other changes since last backup. I also back-up to an online archive and it sits on about 75 GB though files somewhat (smaller 3- 8 GB). When it approached my internal 500 GB drive capacity, I got a 750 GB drive added a few thousand images and tried to back up and got warning "insufficient disc space available". I still had about 300 of 698 GB available with vault size of 437 GB. I did determine that if you delete the vault and write a new one it will fit on a 500 or 750 drive. Any Help? Thanks.
MacPro Qaud   Mac OS X (10.4.10)   4GB RAM, 30 CD

I figured it out - thought I might share.
It turns out that the previews generated at the highest quality for the 30" display are Huge Files. They are anywhere from 2-3X larger than the original file. Hard to believe? Original file 5.0 MB creates preview of 17.4 MB. This overall creates a database that is 3-4x larger than the imported images(including other misc control files). This can be fixed easily by reducing the quality of the preview down to 7, which corresponds to a file size of about 850 KB. Then regenerate the previews (control,option together with click, select generate previews). This can be done for batches, or the entire library. The quality changes was not really apparent. Hope this helps others avoid this situation.

Similar Messages

  • Vault size

    I have a large, referenced aperture library.  When I do "update all vaults" the file size is very small.  Is there any way for me to make sure that all of my projects are being backed up in the vault

    I'm guessing that the "Aperture Library" is in your Pictures folder and the Vault (default name: "Untitled Vault") is on a backup device. When you "Add" a vault it goes thru a dialog box where you picked its location. Otherwise, you can open the Vault pane at the lower left of the Aperture window and click the triangle to the left and it will show you the Vault's name and location.
    (Your next reply just popped up.)
    The size of the folder containing your original image files doesn't really matter here. (Bigger does mean a bigger Library and Vault but there is no specific formula I can offer.)
    The Aperture Library is databases with keywords, adjustments, etc., and image previews. Part of its size is determined by the Preferences setting (size and resolution) for your Preview images. They can let you organize but not adjust your images without the Masters being online.
    The Vault size will be similar to your Library size. Over time this relation may change.
    If you had a Managed Library, it would be 233GB plus databases plus previews. And the Vault would be a similar size.

  • Vault size in AP3

    Anybody else seeing Vaults that are as big as their main library ?
    I use a library with referenced masters and the library is around 22GB at the moment (still in the proces, after a whole WEEK, of manually exporting and importing projects from my AP2 library).
    My vault is the exact same size. It seems to copy all the thumbnails as well, they use 20GB out of that 22GB.
    AP2 didn't have huge vaults like that!
    Another issue to add to the list for AP3!

    Firstlaunch, thanks for your reply - sorry for my delayed response; I've been away for a bit.
    Anyway, to respond to yoyur question - it was the error message that appeared which indicated the 14GB size increase. At the time, I couldn't perform the backup as there was not enough space on the drive. Since then, though, I bought a larger external drive and when I ran the Vault on it (having made no changes from the prior situation) the Vault size did not (again, did not) jump in size.
    So, to recap:
    - I use, and always have used, referenced files, and my AP2 vault was 20GB.
    - After I upgraded to AP3, I immediately ran the Vault, whereupon AP3 renamed the original Vault "old" and proceeded to build it's own fresh version - that was 40GB. I.e. - without any alterations to the underlying data set, the Vault doubled in size. In fact, since I only had limited space on the drive I was using, I deleted the old Vault on that external drive (I still had a parallel old vault available just in case) which is what gave me the room to build the AP3 vault.
    - After importing 12GB worth of RAW files, my attempt to update the vault was met with an error message saying I would need an additional 14GB of space. Without enough free drive space, I did not run the vault update.
    - After adding a larger external drive to my system, I ran the Vault from scratch, and it's actual size remains about 40GB.
    So I can only conclude that, as you evidently suspected, the error message was somehow wrong; that I did not in fact require an additional 14GB of space after all.
    Perhaps this falls under the same bug (er, undocumented feature) category as the one where when I attempt to e-mail versions, regardless of what settings I make in preferences, AP3 always generates full-size (i.e. - 14MB apiece) output. When I do a simple export, it works fine; it's only when I try to directly e-mail that it does this - seems to be another case of poor file size handling.
    I am not going to mark this question answered only because the original question remains - why did the error message warn me about a ridiculously large vault size increase when in fact it never happened? I suspect that the Vault warning simply looked blindly at the fact that I imported 12GB worth of images and somehow "assumed" they were managed files, even though they were referenced.

  • Aperture Backup Vault and Library

    My main Library of Aperture on my main HD is 120GB and my backup Vault on my external HD is 116GB. Do I want to "replace the contents of my Vault with the contents of my Library"? Unfortunately I also have on my external HD another another OS with a tiny library that is tiny 2 GB, how do I know which library Aperture is talking about? In the Aperture GUI my Vault show only 22GB. Confused, please help. No libraries show up on my GUI Aperture window so what should I do? and why don't the vaults match in size?
    I'm on a Mac with Snow Leopard 10.6.4 and Aperture 3.0.3

    Hi Joe.
    Every Image has a Master.  The Master is the file that you imported into the Library.  If the Master is stored in the Library, it is a Managed Master.  If the Master is not stored in the Library -- it is stored elsewhere on your system -- it is a Referenced Master.
    You can easily filter for either.  In the Filter HUD, add the Rule "File Status" and select "Managed" or "Referenced" from the drop-down settings.
    (Added the following paragraph.)
    Thus to find all Images which have Managed Masters, use the above filter on your "Photos" container at the top of the Library tab of the Inspector.  To convert them to having Referenced Masters, select them all and execute "File→Relocate Masters".
    New Masters created by Aperture when you use the "Edit with {External Editor}" command or the "Edit with Plug-in" command should be stored in whatever Finder folder holds the Master of the Image.  IOW, when Images with Referenced Masters are edited with the external editor or a plug-in, the new Master should also be Referenced, and should be located in the same Finder folder as the Master of the Image that was selected for editing.  Is your system behaving differently?  This is easily checked by using either of the commands and then using "{right click}→Show in Finder".
    Message was edited by: Kirby Krieger

  • Hard Drive and Time Machine backup Different Sizes

    I had a lot of difficulty getting Time Machine to work with my new Time Capsule. It seems to work now but I noticed that on the initial backup the size of the backup data on Time Capsule was roughly 148 GB and my hard drive size is roughly 159 GB. If I were to do a backup would I discover that some of my data is missing? Or is it normal? I have not excluded anything from the backup. Thanks.

    I sorted out the problem on my end, and perhaps the same thing will you help Gadifer. In my Aperture preferences, Library Location was incorrect - for some reason there are two. In my case it should be ~/Pictures/Aperture Library.aplibrary, whereas it had become ~/Pictures/My Pictures/Aperture Library.aplibrary (I don't recall changing in manually, and wasn't aware that there were two). When I check them in Finder, I see that the former is several GB, and therefore my actual library, while the latter is only 538 KB.

  • IPhone 5 backup file size problem

    Hi,
    On Monday I have upgraded from iPhone 4 to iPhone 5. I have setup the iPhone 5 as old (not new device) and restored all settings and data
    via iCloud from my iPhone4 backup. Everything works just fine , except I have a problem with the size of the new iPhone 5's backup file.
    iPhone 4's backup files , both on iCloud and my laptop, have the size of 236 MB. iPhone 5's backup file size is only 58 MB.
    The backup file size is the same when using OTA iCloud backup or iTunes backup.
    What am I missing ?
    iPhone 5, iOS 6.0.2, iTunes 11.0.1.12, Windows 7 64bit.
    Regards,
    Alex

    Your question is interesting.  I don't really know the answer, but if that happened to me, I'd be delighted!
    After all, you're saying everything is working just fine, and yet your new backup is 25% the size of your old one.  I would view that as the backup is being done a whole lot more efficiently, with old junk having been discarded.
    I would be really upset and concerned if the backup size went the other way -- if the new backup was 4 times the size of the old one.
    Basically, you will find efficiencies in storage used on your iOS device if you restore it.  I suspect you're seeing similar efficiencies here.  Given everything is working fine, it sounds like cause for celebration.
    Enjoy your new iPhone.

  • Vault size smaller than Library

    I have 30k referenced photos (188 gb) with a Library size of 11 gb. The Vault size is only 1.7 gb! This makes me nervous. In the past, both have been about the same size. What is happening?? thank you

    Here is more detail: I started with a 7gb Library, with about 6gb of managed files and limited referenced files. I then brought in all of my old files with Import Folder into Project, which added 28k files. After that, the Library went to 16 gb (seems large!). Next I relocated the managed files out, about 6 gb, and the Library shrunk to 10 gb. I did a new Vault store and the Vault size shrunk from the original 7 gb to 1.7gb. I can also see along side of it the Deleted files, 6gb, of those moved out.
    If I look in the Vault at a given folder (from the Import Folder into Project), its size is 313mb; the same folder in the Library is 2.2 gb. Looking at a given imported project, Library has a folder of 17mb, AP.Minis of 41mb and AP.Thumb of 76mb. The same file in the Vault has a folder of 20 mb and several little 8k things. Clearly thumbnails were generated although Preview was turned off, and tested that I could not drag thumbs out.
    Hope this helps, thanks, gib

  • Library size differs from Vault size

    I just made a new Aperture Vault. My Aperture Library file is 41.66GB. My Vault file is 35.41GB.
    Why are these different?
    I have consolidated the library as well, so I am sure that the issue is not related to referenced files.
    Thanks,
    ~BC

    Thanks for that. Does my vault size (85% of the library size) seem about right to you?
    I only ask because the whole point of the vault is to be sure nothing is lost ... so I want to be sure I have this set up properly.
    Thanks,
    ~BC

  • Unable to allocate Backup Vault in West Europe

    All public documents indicate this is available but everytime I tried to create one, it fails.
    Any ideas or thoughts?
    "The server encountered an internal error. Please retry the request. The long running operation tracking ID was: c712c8bd4b097de8a1a1f8fb1e8ec288."

    Hello Madisher,
    Thanks for posting here!
    The server encountered an internal error. Please retry the request. The long running operation tracking ID was:
    c712c8bd4b097de8a1a1f8fb1e8ec288. This could be because of the region constraints.
    Please try to allocate the backup vault in a different region and see if that works.
    If you're particular about the region, in that case you may have to wait for some time and then try.
    Hope this helps!
    Write back to us if you have any questions.
    Best Regards,
    Sadiqh Ahmed

  • What is the cisco ironport C680 and M680 configuration backup file size?

    what is the cisco ironport C680 and M680 configuration backup file size?

    Size of the XML itself?  That is going to vary based on what you have configured, total lines of code, and # of appliances you may/may not have in cluster.
    M680, based on SMA as stand-alone, should be similar --- you are probably looking @ < 1 MB... 
    Looking @ my test environment, in which I have a nightly cron job set to grab a backup of...
    -rw-rw----  1 robert robert 161115 Sep 26 02:00 C000V-564D1A718795ACFEXXXX-YYYYBAD60A5A-20140926T020002.xml
    So, 161115 bytes = .15 MB
    -Robert

  • Azure recovery Services (Backup Vault)

    Hi
    I'm trying to test Azure Recovery Services and have established a Backup Vault and connected a new server to it using the Azure generated certificate. The set-up seemed to be very simple and the installation of the agent went like a dream.
    Unfortunately it does not work as after I start a backup I get the error "Engine encountered an unexpected error. Please ....." The corresponding event log entry is:
    Faulting application name: cbengine.exe, version: 2.0.8694.0, time stamp: 0x54816461
    Faulting module name: KERNELBASE.dll, version: 6.3.9600.17415, time stamp: 0x54505737
    Exception code: 0xe0434352
    Fault offset: 0x0000000000008b9c
    Faulting process id: 0x12fc
    Faulting application start time: 0x01d03016883f6a46
    Faulting application path: C:\Program Files\Microsoft Azure Recovery Services Agent\bin\cbengine.exe
    Faulting module path: C:\Windows\system32\KERNELBASE.dll
    Report Id: 72d16f21-9c0a-11e4-80e6-00155d800f3f
    Faulting package full name:
    Faulting package-relative application ID:
    The server is a Windows 2012 R2 Domain controller and is patched with all latest Windows Updates. The latest Azure agent was installed from the web site
    I have tried it on a second server built at the same time and it fails there with the same error

    Please find the note on the supported drives by Azure Backup.
    https://msdn.microsoft.com/en-us/library/azure/jj573031.aspx?f=255&MSPPError=-2147217396#BKMK_faq_4

  • Vault Size/contents ZERO

    I created a vault on an external drive, of my 89G Aperture Library.
    After it created the vault...the contents and size equaled that of the actual library.
    Start and restart Aperture and the Vault status icon is yellow, telling me there has been changes in my library, which there hasn't. So i go and check Vault size, and much to my dismay it says Zero bytes on disk and no package contents.
    I click update vault in aperture, does it's comparing for a bit, then finishes with no errors.
    Vault status icon is black (stating everything is up to date) but Vault is still Zero Bytes and no contents.
    Any ideas!?
    Thanks.
    kevin

    The vault should be smaller: no previews or thumbnails are stored in a vault. So that is odd.
    How are you measuring the size of the vault and library?
    How is your external drive formatted? If it is not HFS+ case insensitive then all bets are off. That is also called Mac OS Extended case insensitive.

  • HT1338 Error preparing Time Machine backup disc- size error usually not being multiples of 512, encryption

    Trying to encrypt Time Machine backup disc getting message  - Error preparing Time Machine backup disc- size error usually not being multiples of 512, encryption.

    I got the same problem.
    But I think it cannot be related to not being a multiple of 512.
    As when I devide the number of bytes 3.000.592.982.016 by 512 is equals 5860533168.
    3.000.592.982.016 / 512 = 5860533168.
    So what could be the real problem?
    With kind Regards

  • VAULT size is smaller than the LIBRARY

    my vault size is smaller than the aperture library.  is it saving everything?  it seems like the two should be the same size or at least close to the same size.  i regularly update my vault so that it is current with the library.  VAULT = 168 GB | LIBRARY = 262 GB

    what is the consequence if i totally turn previews off?
    The major consequence is that you will not be able to share images from your library through the media browser. So if you want to email an image for example or add an image to a document you will need to export the image first rather then be able to get the preview from the library.
    Also if you have referenced originals and the originals go off-line nothing will appear in the library. If you had previews for those images you would still see them and be able to do tasks like rate them.
    Finally some operations might appear slower as you won;t see anything on the scree until the image you are looking at is rendered. With previews while Aperture is rendering the image in the background it will display the preview.
    It is possible to selectively maintain previews for some projects and not for others. This might be a comprise position between having previews for al images and having no previews at all.

  • Backup vault always smaller than the library...?

    My backup vault is alvays about 1 GB smaller than the original Aperture Library. How come? Is this right?

    Thanks Now I can sleep well again.

Maybe you are looking for