Backing up - Vaults vs CCC

Hello all,
I run Aperture on a referenced master basis. So far my Aperture backup system, as everything else, relies on bootable clones and, subsequently, incremental backups to two external HDs using Carbon Copy Cloner.
At this stage I do not use Aperture's Vaults. Is this a mistake? From my understanding they both work in the same way updating the library with the latest snapshot of changes (except that Vaults can do it continuously if the external is connected). But I tend to only connect for daily/weekly backups and don't delete compact flash cards until the daily backup has been done.
However, I was also considering preserved snapshots at particular moments in time (also onto my externals and DVDs) in case my existing library got corrupted but this went unnoticed and got transferred to my external HDs too. Again copying the aplibrary with CCC or finder seems to be the obvious choice.
Do I have any need for vaults?
Ross

In your case, if you accidentally delete files or corrupt your library, you could be in a pickle. Because CCC will "clone" the source to the target. If you delete some files (or somehow accidentally delete an entire project), and then don't notice it immediately and "clone" to your backups, you will delete it from all your backups as well. There's no real "last chance" backup.
With Vaults, if you delete projects or files, the next time you update the vault they will be removed from the vault, but all deleted files will actually be moved to an "Aperture delete files" folder on the vault volume. Where you can recover (or clean house) at some later time. IMO, having this sort of backup (which protects against user error, until you tell it you REALLY REALLY wanted to delete some files), is crucial.
So yes, there are definite advantages to Vaults over a simple cloning scenario as you're currently using.

Similar Messages

Need help in distributing Master Folder (all my original pics), Aperture Library, Aperture Back-up, Vault and Time Machine

I have a desktop iMac and three external HDs. One HD called Aperture Library (2T) now has Aperture Library, Time Machine backups and Master Folder, which is where I put my RAW files of pictures I want to keep. A second HD called Aperture back-up (1T) has another large Master Folder. This was created a long time ago when I was using Lightroom. I plan to transfer pictures on to HD Aperture Library > Master Folder so I will have 1 Master Folder. A third external HD called Vault (1T) now only contains my Quicken b/u.
I have not made a vault yet for Aperture, because I am in the process of exporting files from Lightroom and bringing them into Aperture 3. What a mess, especially because I was not able to use my photo apps (Lightroom or Aperture) for a few months and forgot the do's and don'ts. Please help me organize this stuff while I have the time and motivation. Greatly appreciated.

Note that Masters need only be backed up once (but to multiple backup locations) and that backup should happen immediately after copying to the hard drive from the camera card, before involving Aperture or any other images management app.
Time Capsule is an ongoing regular-routine backup process. Image originals instead need irregularly timed backup, once.
IMO referenced Masters make far more sense than building huge managed-Masters Libraries.
• Hard disk speed. Drives slow as they fill so making a drive more full (which managed Masters always does) will slow down drive operation.
• Database size. Larger databases are by definition more prone to "issues" than smaller databases are.
• Vaults. Larger Library means larger Vaults, and Vaults are an incremental repetitive backup process, so again larger Vaults are by definition more prone to "issues" than smaller Vaults are. One-time backup of Referenced Masters (each file small, unlike a huge managed-Masters DB) is neither incremental nor ongoing; which is by definition a more stable process.
Managed-Masters Libraries can work, but they cannot avoid the basic database physics.
HTH
-Allen Wicks

Backing up Vaults slow

Using Aperture 3.4.5 on a Mac Pro with 10GB Ram, updating a vault takes hours. Activity Monitor indicates "Not Responding" in red. When it is not marked "Not Responding", Aperture is using 0nly 1.2% of CPU, even with no other application running. Eventually it completes the update. Is there a way to force Aperture to use more of the CPU capacity so that this process would go faster? I have two libraries, one 301 GB and the other 1.67 GB, and this problem occurs with both libraries. Each library has two vaults, one on a Drobo and one on an internal drive in the Mac Pro.

Frank, I did a Photo Library Repair Permissions, then Repair Database. Now the Vault updates take only minutes!
Ok that's good. As I wrote I found that doing a repair before vaulting seems to help especially if the library has had a lot of changes to it or its been a while since a repair or a vault operation.
Even though much improved, I am still puzzled by the Activity Monitor showing the red " Aperture not responding" message, sometimes but not always
That is deceiving and not always helpful. An application can be non-responsive to the outside world but it doesn't necessarily mean the app is hung. It just means it is doing some intensive task at that moment. This cause a lot of problems as user see this and think the app is hung and then force quit it.
Especially in this case where it is going in and out of the not responding state everything is OK.
Further, I don't understand why Aperture is using only 2% of CPU during these vault updates. Why not use more CPU and speed things up?
Updating a vault is just not very CPU intensive, not a lot of computation going on. The bottleneck is really the I/O, reading the library and writing to the vault. More CPU really wouldn't help in this case.
There are other threads discussing this QTKitServer issue--see my last post.
Yeah I've seen those too, not sure what is going on with that. Seems to be a fairly recent thing, I'll have a look at the other thread..
regards

Rsync used STRICTLY for "photos and video" library back-up

Hi,
I'm hoping to get some guidance from some experienced users of rsync.
I'm new to rsync, but have been learning about it.   I'm also new to Terminal.
.....**For full system back-ups, I use CCC (Carbon Copy Cloner)....clean and simple.**
However, for my large "photo & video library" (over 1 TB on an external drive), I found that CCC, while essentially doing the same as rsync, seems to take MUCH longer. Rsync, on the other hand, is very fast.
This leads me to FIVE questions.
Q1: Is this because CCC (which uses the rsync command, albeit modified), is doing a check-sum or sometime else behind the scenes?
Also, looking through the various command lines that other contributors have suggested when using rsync, I am a little confused as to which optional commands are necessary for a PURELY "photo and video" library.
For the optional commands, I think the ones that are a MUST for me are:
-a - "archive" rsync, includes ownership info and extended attributes extremely useful for moving large volumes of data and keeping AD/OD/POSIX permissions intact
-v - "verbose" gives the user more information on the rsync display
-x - prevents crossing filesystem boundaries
-t - preserves modified time
--delete
This tells rsync to delete any files on the receiving side that aren't on the sending side. Files that are excluded from transfer are excluded from being deleted
....Optionally, I could add the following to view the progress:
--stats
This tells rsync to print a verbose set of statistics on the file transfer, allowing you to tell how effective the rsync algorithm is for your data.
Q2: Is there anything else I should be adding?
Q3: Also, I saw that one contributor used "bash" at the start of the command line. Is this necessary for my specific purpose?
Q4: Snow Leopard comes with rsync version 2.6.9 version 29.   I know that version 3.1.0 is already out, but this would require an installation step (possibly using come Terminal commands, or something like "MacPort"), then adding patches, and perhaps some steps that I haven't mentioned. Is version 3.1.0 really necessary, and in what way? Much faster? Better Integrity of the back-up? Other? (o.k., that was more than one question)
Q5: Is there a command to preserve the "CREATED" time of the photo? Is this taken care of by the " -a " or the " -t "?
Thanks,
Sam

sling74 wrote:
sling74 wrote:
Hi Tony,
Thanks for your quick reply.
A few other questions:
1.     What is the -N command for? I could not see it on the rsync.samba.org website.
2.     My friend does not have CCC. She's also using Snow Leopard 10.6.8. What are the steps to properly install the newest version of rsync?
3.    For myself, what would be the disadvantage of using CCC directly rather than accessing it via Terminal? When running CCC, what are the default commands being used?
Thanks,
Sam
Hi Tony,
Thanks for your quick reply.
A few other questions:
1.     What is the -N command for? I could not see it on the rsync.samba.org website.
That's added with the crtimes patch:
     -N, --crtimes               preserve create times (newness)
2.     My friend does not have CCC. She's also using Snow Leopard 10.6.8. What are the steps to properly install the newest version of rsync?
Here's what I do:
1. Download and unarchive rsync and its patches
    a. Move patches directory to rsync-3.1.0
    b. cd rsync-3.1.0
2. Apply patches relevant to preserving Mac OS X metadata
       patch -p1 <patches/fileflags.diff
       patch -p1 <patches/crtimes.diff
3. Apply patch relevant to preserving Mac OS X hfs+compression
      patch -p1 <patches/hfs-compression.diff
4. Configure, make, install
        ./prepare-source
        ./configure
        make
        sudo make install
5. Verify your installation
      rsync --version
By default, rsync will be installed in /usr/local/bin.
If that isn't in your path, you will need to call
your new version of rsync by its absolute
path in /usr/local/bin (you will most likely need to do this
and --version will verify that you have the right version)
(from: Configuring Mac OS X for Unattended Backup Using rsync and updated for hfs+compression patch)
3.    For myself, what would be the disadvantage of using CCC directly rather than accessing it via Terminal? When running CCC, what are the default commands being used?
No disadvantages that I'm aware of.
I'm not sure what defaults that Mike is using now, but most of the the flags that I use and posted are from the link above from Mike a few years ago.

Vault restoration with referenced images - SEEKING HELP

Long story short: I have, had, a library that contained both managed and referenced images. 2 vaults set up for managed images, RAID system set up for referenced images.
Rebuilt library the other day because Aperture was moving kinda slowly. Followed the typical protocol of backing up first then rebuilding and to later back up again. In the middle of rebuilding, Aperture froze (Activity Monitor said Aperture was using only .50% of resources) and hung there for over 8 hours. Force quite wouldn't work. Had to hard restart.
Problems surface with the primary library. Decide to restore from recently backed up vault. Worked for only 13 projects but hung/froze again on the 14th project for another 8 hours.
Freaking out that my redundant back up system completely doesn't work, I put the managed projects back together in a new library by going into "show contents" of the vault and importing projects individually. This took another day of work. Managed projects are working just fine now and are backed up once again.
Referenced projects will not import at all. I can not reconnect them to their referenced images in any reasonable manor. The only way I've figured out how to do this is by hand, placing the referenced master image file into the "show package" content file of the said image. This is a daunting task for the 7 weddings of 700-1000 image each. Even if I do this, there is no guarantee that the project will import with out issue.
Anyone know how to do this? Does anyone know what happened here? Any thoughts would be greatly helpful.
Thanks in advance,
cd
Mac Pro 2x2.66GHz, 4 GB RAM, duel HD displays Mac OS X (10.4.10) MacBook Pro 17" 2.33 GHz 3 GB RAM

Andreas Yankopolus wrote:
Dudley,
I'm experiencing the same problem on my MacBook Pro: Aperture will periodically show all of my reference masters as being disconnected. They're on the laptop's internal HD, which is the only one connected to it. Quitting and restarting Aperture usually reconnects them temporarily.
My main piece of advice is to not install Leopard. It's been nothing but trouble for me, my wife, and a friend that's done so. If there was an easy way to drop back to 10.4.11, I'd do so in a heartbeat.
Hi, Andreas
I think there is something else going on. (would like to know what it is). We've been on Leopard/Aperture combo since day one and running without any hickups on PPC, Intels and Laptops.
Is there anything that seems to trigger this disconnect?
victor

Vault - POINTLESS (!) ?

I have been running Aperture quite happily for a very long time.
- have another (2nd) external hard drive running just Time Machine;
- have another (3rd) external hard drive Just for Aperture VAULT.
have been making lots of projects, and when finished duitifully hit the 'back up vault' button, it spins all done, and thought nothing more of it (safe ! in the knowledge that Vault had run and gone green, all backed up)
I recently 'cleaned up' my main MAC desktop, and started another few Aperture projects and kept VAULT backing up, same as before.
*TO MY UTTER DISMAY* all the previous projects have 'gone' from the vault (3rd external drive), and only the most recent (post Mac DESKTOP clean up) are there.. the VAULT is virtually EMPTY !
Where have they all gone ?
*what is the POINT of VAULT* if it is not a true back up (like Time machine?) !!
- is there 'anywhere' else on the historic 'desktop' time machine that they MIGHT be stored (perhaps a hidden folder) if i go Back through my Time Machine drive?
PLEASE HELP !!

Not sure on the vault issue as I don't currently use it.
If you did not specifically exclude the Aperture Library in the Time Machine preferences, then you should have that package available in the Time Machine interface.
It should be in whatever location you keep the library (default being '~/Pictures' folder). You need to run Time Machine from that location and you can restore the library.
Note - I would recommend renaming your current library and moving it to another location (to prevent issues during restore). Then run the Time Machine restore from the historical date you know will contain all your images.

Vault has 50 gigs free space but Aperture will not backup?

My external HD that stores my Vault has 50 gigs of free space. Aperture is telling me that there is not enough space to backup to the Vault.
What gives?
Thanks in advance for any help with this!

How much GB is your library?
I had an issue with Aperture 1.5 not backing up because it needed about twice the space of the library to be backed up. So now I use big drives with room to spare and backing up vaults works fine.
Marius

Error code -36 trying to copy from iPhoto library

Hi all,
A friend has just brought me his 17" Mac Book Pro which refuses to boot. I started in target mode connected to a Mac Pro to see if I could rescue his data, (no backup as usual). The first thing that I see is that he has 2.3Gb of space left which tells me what the problem is so I want to copy some of his data of the laptop. As he has a lot of photo's (60 Gb) I thought that I would copy a chunk of them and delete them from his library just to get space but I keep getting a message that says "Some data in IMG_xxxx.jpg can't be read ot written. error Code -36". Any ideas how to get round this.

Thanks for your response. I have just tried Carbon Copy Cloner, I thought I would try this on the documents folderbut I am still errors. CCC gave this.
CCC will proceed with the backup task, copying as many files as possible. Please note:
• The first error occurred while trying to access:
"/Volumes/System X/Users/john/Documents/Final Cut Pro Documents/Autosave Vault/1.shingaanie.fcp/1.shingaanie_01-10-12_1534"
• CCC will make two attempts to back up damaged files
• CCC's log file contains more specific information about the affected files or folders.
• Physical errors may cause the backup task to take longer than normal.
• You can stop the backup task at any time. CCC will pick up where it left off the next time you run this task.
Please click on the "?" button below to learn more about resolving media errors.

Error code -51 (try to copy from win to mac)

Hi,
I have a problem with copying files FROM Windows to my Mac. I am connected through the VPN, I can see files on Windows server, I can copy TO server, I can create folders etc (on Win), but if I try to copy from Windows I always get "errorr code -51". I have MacBook Pro with Snow Leopard 10.6.8.
Does anyone know what is going on? Thankx a lot, Lukas

Thanks for your response. I have just tried Carbon Copy Cloner, I thought I would try this on the documents folderbut I am still errors. CCC gave this.
CCC will proceed with the backup task, copying as many files as possible. Please note:
• The first error occurred while trying to access:
"/Volumes/System X/Users/john/Documents/Final Cut Pro Documents/Autosave Vault/1.shingaanie.fcp/1.shingaanie_01-10-12_1534"
• CCC will make two attempts to back up damaged files
• CCC's log file contains more specific information about the affected files or folders.
• Physical errors may cause the backup task to take longer than normal.
• You can stop the backup task at any time. CCC will pick up where it left off the next time you run this task.
Please click on the "?" button below to learn more about resolving media errors.

Used Relocate Masters to new g-drive. Lost Aperature Library and meta data

how i crashed aperature
1.56 aperature
all updates current
tiger 10.4.11
all updates current
Goal was to move Aperature Library from MBP to g-drive.
what i did:
1. "Relocate Master" to g-drive. Success. Aperature still viewed all Files with all Meta Data normally.
2. Collapsed "Library" in Projects Panel. Did not delete Projects. Did not delete any Photos.
3. Preferences > Image Management > set new Aperature Library on g-drive.
4. Uploaded new photos from a Canon and viewed them successfully.
5. Ejected g-drive correctly.
what Aperature is not doing now:
1. no Projects show up.
2. no Referenced Photos show up.
3. no Vaults show up. Note: the Vault was originally on MBP, but I foolishly did not set one up on g-drive before moving. I also have a back up Vault on a different g-drive that is, unfortunately, not up to date with all current photos before move.
4. Aperature Library on g-drive is there but can not open any files in it. [note: item 3 above]
5. Image files listed in g-drive but won't open in Aperature but do open in Preview or Gimp, etc.
6. Aperature does not show any Vaults nor does it access Referenced Files.
*Can you help ?*
*I guess these would be the questions:*
1. How can I get the pics from the g-drive back into an Aperature Library with all the previous Meta Data attached to each Version?
2. How do I get the Aperature Library - I put on the g-drive - to open in Aperature?
3. If #1 is impossible - I guess I set up a Vault on the g-drive and move what I have from the back up Vault mentioned above.
*Thanks for any advice !!!*

If I an not mistaken, I may have read through your pdf's quite a while ago. I am still trying to digest them and then apply them to my needs. If I had known that small projects may be faster and easier to manage than larger ones I would have done my imports quite differently. I chose to use Aperture in the first place to organize and add information to photos. I archive old photos. In particularly from 350th Fighter Group, WWII in the Mediterranean. So one "Project" of mine is =/-5000 images in the form of TIFF scans. I imported all of these into 1 project. Then I started applying metadata and keywwords like crazy. This allowed me to start to sort the photos into categories and find multiple version of the same image. I started making stacks of all the multiples. Then with smart albums and smart web sites I was able to create what might now be smaller projects. Since I gather information from others by sharing these photos on a website, You are able to see the smart websites here.
http://web.me.com/vizcarraguitars/350thFighter_Group_Blog/350th_FG_Blog/350th_FGBlog.html
One cool thing is that various images reside in multiple smart webs based on common keyword. But now that I have all this organization, it seems it is time to put all my originals in a similar order via Aperture.
By the way, my files are reference files unless I make the mistake of importing them without leaving them in there original location.
I am thinking of starting over with blue folders. But I can't seem to get my head around it.

Image cannot be rendered because Aperture does not support image format

Dear all,
I have installed apple Aperture 3.03 and the complete Nick software plug-in selection:
• Dfine 2.0 for Aperture
• Color Efex Pro 3.0 Complete for Aperture
• Silver Efex Pro for Aperture
• Sharpener Pro 3.0 for Aperture
• Viveza 2 for Aperture
History
Until a few days ago the system was running ok / no notable issues on performance. / all pug in seem to run good / no issues. Also
• I Run OSX10.4/ Aperture 3.03 ( 32Bit mode)
• My library contains just over 10000 images / approximately 140GB
• I have recently updated the OSX software update including the security update 2010-005
• as well as the Snow leopard graphic update 1.0
• As far as I am aware all updates where automatically recommended by OSX Software update ( no manual intervention).
• As far as I remember after update the system still was running ok but honestly I can not tell you how many times the Nick Plug in started out of Aperture.
After all, Several times I continued using the system / still no noticeable problem until the following was happening:
Problem:
After creating with "PT gui" a panoramic image File type: "TIF" Pixel size: 5112 × 2556 (13,1 MP) I imputed this file in to Aperture (drag and drop). During the attempt to eddied this file with "Nick Define 2.0" the system was hamming up No response for several minutes from Dfine 2.0 / Aperture" At the end I had to "force quit" the applications.
After the consequential reopening of Aperture I tried again to eddied images with any Nick software Plug-In but each time Aperture prepares any image previously stored in my Library ti open the Pug in the following Error message appears:
*"This image cannot be rendered for editing because Aperture does not support the image format"*
Currently non of my previously in the library safed images can be opened in a Nick software Plug-In this applies to all file types I have tied " Raw, tif, jpg"
• I am still able to eddied normally with Aperture ( so far I do not find any other issue)
• A newly imported Raw image after being taken with my EOS 5D can be edited in the completed Nick software Plug-In selection ( so far I do not find any other issue)
The following actions have been taken to overcome the issue (all not successful):
• I restored my Library out of my back Up ( to previous time of event ( no Time machine back up)
• Uninstallation of all Nick software Plug-In selection
• Uninstallation Aperture Reinstallation Aperture / Nick software Plug-In selection
• Repairing the library ( all three possibilities)
• installation of latest EOS utilitys
Questions
• Can you support me to overcome this issue?
• Have you heard similar issues of Nick user Running the Aperture plug-ins?
For me it is really strange that even after replacing the the library in my normally not connect back up the problem still exists (this should be not affected by the event as the back up was not done any more) / new imported images are editable with the Plug-In.
I would be happy if you could support me in this issue.
Best regards,
Matthias
PS: I have reported this issue to Apple (via Aperture feedback) as well as contacted the Nick software support and currently waiting for feedback.
Harware:
Modellname: MacBook Pro
Modell-Identifizierung: MacBookPro5,1
Prozessortyp: Intel Core 2 Duo
Prozessorgeschwindigkeit: 2,66 GHz
Anzahl der Prozessoren: 1
Gesamtzahl der Kerne: 2
L2-Cache: 6 MB
Speicher: 4 GB
Busgeschwindigkeit: 1,07 GHz
Boot-ROM-Version: MBP51.007E.B05
SMC-Version (System): 1.41f2

Dear Ma-Le / All
I have just had the same problem
I use
• Aperture 3.03 with a iMac 2.8 Intel Core 2 Duo with all files on external hard disks (mac extended fomat as apple suggests) with referenced masters.
• Camera Nikon D300, with probably 75,000+ images on 2 hard drives
• Photoshop CS2 with PhotoTools 2.5 plugin
This has been working perfectly until yesterday when the system froze when I was using PhotoTools 2.5 with Photoshop CS2 - as a result of which I resorted to a force quit.
Since then on most of my files it has not been possible to use an external editor.
A message appears saying: *Editing Error - This image cannot be rendered for editing because Aperture does not support image format*.
The problem seems to apply to the attempted use of any external editor (including Noise Ninja)
The following have each been tried, all unsuccessfully:
- Using each of Aperture's library 3 first aid options
- Rebuilding directory using Diskwarrior
- Checking for virus using Virus Barrier X4
- Defragmenting library hard disk using TechTool pro
- Changing permissions settings
- Using Disk Utility first aid to repair permissions and checking main disk
- Removing some plist elements when open 'show package contents' of library
- Setting up a(n almost clean) new system, with newly loaded version of Aperture, with a new library from a vault saved prior to the crash when the problem first occured
Several things seem to me to be totally bizarre:
1 - The problem is the same on the other library hard disk which was not in use at the time
2 - The problem still occurs when a back up vault saved prior to this problem is loaded - using a new hard disk with a new system and a newly reloaded and upgraded Aperture software
3- The problem seems inconsistent. It appears to affect some photos but not all. Even from the same shoot, some photos can be edited using an external editor, whilst others cannot (but as far as i can tell most of the photos in a particular album seem to be consistently affected)
4- The only way around it seems to be if I import a new (copy image) from the original master. Then everything works ok, and I can successfully edit that copy image in photoshop / phototools plug-in.
I am beginning to wonder whether what has been corrupted is Aperture's ability to make copies from the master file which it then uses with the external editor (I have no real idea whether this is correct)
Does anyone have any ideas or solutions - or has anyone else been suffering a similar problem?
Eric
PS: As a professional photographer this problem is a really serious issue for me - and I really don't really want to go to Lightroom or Capture One

Looking for a new work flow...

I am about to get a new macbook 13inch (at the moment i use a 1st gen 17inch intel) I will get a new monitor for the home but want something very portable.
Right, at the moment i store all my Aperture files on an external firewire drive and back up the vaults on another hard drive (this used to be connected via my time capsule and worked fine till recently and I now can only back up vaults by connecting it directly to the computer)
The new macbook will have a much bigger drive so I am thinking current projects could reside on it and and less current work on the firewire, and vaults as before on the large powered hard drive at home.
The problem is should i go back to referenced files for the non current projects, or is there another route worth trying, as I had some issues with ref'ed files, and if i remember rightly, they can't be backed up to vaults.
The reason i am thinking of this workflow is that having current work on the computer may avoid any problems with using USB as a way to connect to the external hard drive. so making aperture more agile (it can be dog slow even with firewire). Also it means i can avoid having the hard drive with me when travelling.
Does this make sense? will I have to turn the current library location (on ext FW drive into a referenced volume?) and then need some way to back that up to the other hardrive?
Could I use time machine now it is supposedly more stable?

It sounds as though you are far ahead of me on working with Aperture and setting up Aperture workflow, so I hope you can help me with a bit of problem-solving of my own.
Problem 1: I am using Aperture with two cameras (photographers) at sporting events. The CF cards are given to me with about 300 RAW images (each) at 20 minute intervals. My problem is getting that many RAW images QUICKLY into Aperture and then exported again as small jpgs for sporting participants to view. After about an hour, I am getting quite a backlog of cards to import.
Problem 2: Then the greater problem...after about 5 or 6 (300 image) albums inside of a project, I begin to get the message from Aperture that I am seriously low on disk space and at risk of damage in Aperture. I have been exporting the project to an external hard drive at this point, but that brings the problem of getting the images back to the computer if someone wants to print it at the sporting event.
From your post, it sounds to me like I might have some options on where I can have Aperture save which might be helpful in my case??
Problem 3: One more issue I have with it is that even after I export that project, it still doesn't have much availability. After I import about 300 images, into the 2nd project, I begin to have "space" problems again. I am not sure why the 2nd project doesn't have as much "space" as the first one did (that is now out on the external hard drive.)
I am using a MacBook Pro 2.2 GHz Intel Core 2 Duo, with 2 GB RAM, running OS 10.5.5 I copied the following information from my Apple menu which (I think) describes my current hard drive situation (I still have the 2nd project on computer.)
Macintosh HD:
Capacity: 111.47 GB
Available: 800.4 MB
Thanks for any advice from anyone!
Pk

Best setup for external drives and backup

I'm using Aperture to organize several thousand photos. I've gotten good advice her before about how to get started on this. I'm not a professional and I'm not an experienced user of Aperture, so don't assume a lot of knowledge when you answer. I'm wondering what the best way to set up the file storage would be. I use a MacBook Pro, so obviously that's out for storage, and financially, purchasing a more powerful desktop is out for the time being. I was thinking of purchasing a mirror drive system, like this: http://www.newertech.com/products/gmax.php
But then, there still remains the problem of backing up the photos in case of a fire or theft, etc. I have many of them on DVD, but not with all the metadata that I've added. Can I back the external drives up to a cloud-based storage system through the wireless on the MacBook?
Or, is the answer none of the above? What recommendations do you folks have for managing this?

more:
Paula-
Mirror drives are very much less than ideal for images backup. Mirroring occurs in real-time, so errors, breaks, etc. simply get copied. With images work (unlike fanancial work, for instance) we do not need real-time backup we just need regular accurate backup. Just have 2-3 external drives and rotate them regularly, always having one drive off-site (could be in your car or whatever). Back up manually rather than automatically so that you can be reasonably certain that the backup is not backing up something that just broke.
I suggest the below workflow. Note that most important is that original images from the camera card are copied to two locations before reformatting the card and before importing into Aperture or any other images management application.
Original images never change, so I prefer to manually copy them to two locations asap after capture: one location is the computer drive and the other is an external backup HD that itself gets backed up off site regularly. That assures me that "the pic is in the can." Until two digital files exist on different media I do not consider the pic in the can.
Then reformat the card in-camera, not before.
The Masters then get imported into Aperture from the Mac internal drive by reference (i.e. "Storing Files: in their current location" on the Mac internal drive). After editing is complete (may take weeks or months), from within Aperture I relocate the referenced Masters to an external hard drive for long-term storage.
I do use Time Machine routinely on the MBP, but for the daily-volatile activities going of the MBP. I prefer not to have TM be my backup-of-originals protocol. Instead TM backs up the Mac internal drive on the TM schedule and I back up original images asap based on my shooting schedule. Also the TM drive is a different drive than the drives used for long-term original image files archiving.
TM does back up my Library because the Library lives on the Mac internal drive but I do not assume that TM works for Library backup. I back the Library up to Vaults (on the same drives I put archives of Masters on) independent of TM. IMO one should back up image files and back up Vaults manually after verifying that what is being backed up is not broken, because automatic backup will just back up a broken Library or whatever.
Note that Masters need only be backed up once (but to multiple backup locations) and that backup should happen immediately after copying to the hard drive from the camera card, before involving Aperture or any other images management app.
Sorry for the redundant verbosity above but some was copied from previous posts. Also, I reinforce what Léonie said about DVDs. DVDs are way too slow, unreliable, etc. Instead rotate multiple hard drives to achieve redundancy.
HTH
-Allen

Macbook Air and Aperture SSD storage space?

I recently purchased the new Macbook Air 13" i5 with 128 GB SSD and 4GB of Ram. I have 50Gb of photos.
1.) Can I store these photos on a Time Machien and file share?
2.) Should I purchased a gigabit ethernet NAS drive like a DROBO?
3.) Should I go with an attached Thunderbolt NAS drive?
4.) What is the best way to manage the photos on a an external drive basically?
Thanks

By all means test as Kirby recommended.
Most important is that image originals should be backed up in multiple locations prior to import into Aperture or any other images management application. Yes there are printed workflows that fail to note that critical step. Such manuals, tutorials, etc. are incompetent in that regard.
As you start out with Aperture learn what referenced Masters are, and always use a Referenced-Masters Library. If you screw up and some images get "managed" instead of "referenced" that is no big deal because from within Aperture Masters can easily be relocated.
Managed masters or mixed managed and referenced masters are fine in the beginning with few images; the reason for always using a Referenced-Masters Library even in the beginning with only 50 GB of image files is for consistency. Consistency reduces the likelihood of error, and later as Library size grows having Masters referenced on external drives will be far superior.
IMO referenced Masters make far more sense than building huge managed-Masters Libraries.
• Hard disk speed. Drives slow as they fill so making a drive more full (which managed Masters always does) will slow down drive operation.
• Database size. Larger databases are by definition more prone to "issues" than smaller databases are.
• Vaults. Larger Library means larger Vaults, and Vaults are an incremental repetitive backup process, so again larger Vaults are by definition more prone to "issues" than smaller Vaults are. One-time backup of Referenced Masters (each file small, unlike a huge managed-Masters DB) is neither incremental nor ongoing; which is by definition a more stable process.
Managed-Masters Libraries can work, but they cannot avoid the basic database physics.
Like you I work from a 128 GB boot SSD, and I suggest this workflow:
Original images never change, so I prefer to manually copy them to two locations asap after capture: one location is the MBP SSD and the other is an external backup HD that itself gets backed up off site regularly. That assures me that "the pic is in the can." Until two digital files exist on different media I do not consider the pic in the can.
Then I reformat the card in-camera.
The Masters then get imported into Aperture from the SSD by reference (i.e. "Storing Files: in their current location" on the SSD). After editing is complete (may take weeks or months), from within Aperture I relocate the referenced Masters to an external hard drive for long-term storage.
I do use Time Machine routinely on the MBP, but for the daily-volatile activities going of the MBP. I prefer not to have TM be my backup-of-originals protocol. Instead TM backs up the SSD on the TM schedule and I back up original images asap based on my shooting schedule. Also the TM drive is a different drive than the drives used for long-term original image files archiving.
TM does back up my Library because the Library lives on the SSD but I do not assume that TM works for Library backup. I back the Library up to Vaults (on the same drives I put archives of Masters on) independent of TM. IMO one should back up image files and back up Vaults manually after verifying that what is being backed up is not broken, because automatic backup will just back up a broken Library or whatever.
Note that Masters need only be backed up once (but to multiple backup locations) and that backup should happen immediately after copying to the hard drive from the camera card, before involving Aperture or any other images management app.
Time Capsule is an ongoing regular-routine backup process. Image originals instead need irregularly timed backup, once, before import.
I recommend directly-attached external hard drive(s) rather than NAS for your situation. Sometimes NAS setups have a tendency to break with OS version changes or app version changes.
Sorry for the redundant verbosity above but some was copied from previous posts.
HTH
-Allen Wicks

Azure virtual machine not discovering

We created our back-up vault yesterday. Agents have been installed without any problems. Vault/Virtual machine/storage is all in the same region but it doesn't seem to find any azure virtual machines.
Regards,

Hi PCSKnokke,
Are the VMs in a healthy state? If yes, I can look up in the backend to see what is going on. If you can share some information about the VM (name, region) then I can look this up. If you cannot share this information on a public forum, please direct-message
me on Twitter (@AzureBackup).
Meanwhile, there are issues that we are fixing and perhaps the problem you are facing will get resolved in one of the hotfixes that we will do. Let's investigate anyhow.
Regards,
Aashish
Added everything to the same subsription and tried it again. Now it seems to work. Could it be that if you use multiple subscriptions (VM on one subscription, backup vault on other subscription) that this doesn't work?

Backing up - Vaults vs CCC

Similar Messages

Maybe you are looking for