Adding metadata to my initial backup files

I have a hard drive on my PC exclusively for image backup and I 'copy' all my pictures there automatically, when I first download them from the camera, using Adobe Bridge. In theory at least, this set should never be needed. All my subsequent processing takes place on the prime set in the 'C' drive, using Photoshop CS4. Short of completely overwriting and replacing all my backups, is there any easy way of just appending my keywords and rankings to all the untouched files on my second drive?
Note.. All images retain their original ID numbers exactly as shot and I do not use Lightroom.
Best regards,
BRB (in the UK)

BRB.UK wrote:
Hi RWSP and thanks,
So...
If I understand you correctly, with 'raw files' I can now select and copy (Ctrl+Drag&Drop) just, all the small hidden sidecar.xmp files, from my C drive over to my camera-raw backups on the second drive. This will non-destructively update everything, the keywords, ratings and the ARC processing data, without touching the raw files them selves in any way?
But for .jpg's I will have to copy-and-replace things with the processed picture files in order to add the key words etc.? In effect overwriting my camera copies with the Photoshop-processed.jpg versions. ...
Right.  You can copy the xmp sidecar files to your backup.  This will back up the keywords, ratings, acr edit data and (assuming no file name changes) will associate the metadata with the original unchanged raw file.*  SFAIK there is no way to have metadata for jpeg files written to sidecar files; so you're right: you would need to  backup your updated jpegs to preserve the metadata you applied.  But if you're shooting raw, would you have many jpegs files from camera?
* Note:  The above applies for camera-native raw format files; may or may not be true for DNG native format camera raw files.  Since DNG is designed to be updated with added metadata, it may be that ratings and acr metadata would be written to the original dng files.

Similar Messages

  • Adding Metadata to mp4 files to load as "TV Shows"

    I am looking for some help in adding metadata to mp4/m4v files so that they autoload as "TV SHOWS" when imported into iTunes. I have several files so it would be helpful if anyone knows of a way to do batches of files.
    Thanks to the Mac world out there for anyone's help.

    You can set a whole batch of files to "TV Show," but bring them into iTunes first. This is as easy to selecting the batch and running any kind of plug-in on them.
    Videos all go to the Movies category by default, but that's only temporary. Right after you drop them into your library, find them under Recently Added or Movies. Select them all, and press Ctrl-I to Get Info. Change the video kind to "TV Show." Now all of these files will appear in the TV library, but of course you'll have to fill in the series name and season. Those can also be filled in as a batch.

  • Adding metadata to mp4 files to show as "TV Show"

    I am looking for some help in adding metadata to mp4/m4v files so that they autoload as "TV SHOWS" when imported into iTunes. I have several files so it would be helpful if anyone knows of a way to do batches of files.
    Thanks to the Mac world out there for anyone's help.

    You can set a whole batch of files to "TV Show," but bring them into iTunes first. This is as easy to selecting the batch and running any kind of plug-in on them.
    Videos all go to the Movies category by default, but that's only temporary. Right after you drop them into your library, find them under Recently Added or Movies. Select them all, and press Ctrl-I to Get Info. Change the video kind to "TV Show." Now all of these files will appear in the TV library, but of course you'll have to fill in the series name and season. Those can also be filled in as a batch.

  • Bridge CS5 - Adding metadata to RAW files is hit and miss

    Can someone help me??? Bridge CS5 will only add the metadata I enter to the files it feels like doing. It is hit and miss. Some files will add it, and other files will get the message "There was an error writing metadata to 100824_Banks_06.NEF". It will go through my whole folder of RAW files, then other times it will allow one or two of the files to get the information. I am going crazy! Is this a preference setting issue, or what?

    Tai Lao wrote:
    Bridge is the weakest of all Adobe applications I use.  It suffers from the same issues since its first release, when we were told to forgive the teething problems of any version 1 application.  Now it's in version 4.x.
    I actually spent most of the last two days wrestling with Bridge, and getty pretty annoyed with it. The "Error writing metadata" bug caused me no end of problems in trying to reorganise my keywording of 20,000 photos, and turning the air blue in the process.
    I agree that Bridge seems to be the poor relation in the Creative Suite. I call it the Less Glamourous Sister. It needs to be 64-bit to host 64-bit Camera Raw, and it needs to manage resources faster and more efficiently.
    I've spent a fair amount of time watching Bridge's activity with a resources monitor utility, and it's a very busy lady. It seems to poll several drives every second or two, accessing the registry, disk-based settings and library files regularly too, even when it appears to be doing nothing. And, even though I had indexed and cached my whole 20,000 photo collection, Bridge insists on recreating some thumbnails and previews at random intervals.*
    I decided that the anti-virus software suggestion was a red herring in my case (I now realise this is the Mac forum anyway). Photos which gave an error became subsequently locked for several minutes, and I had to edit the sidecar files by hand. In the end, I worked out that, even though there is no on-screen indication of activity, Bridge is quietly working its way through every item in the Content pane, and it is this action which seems to coincide with the Metadata Error. Wait for it to end, and chances are much reduced, but not fully removed.
    Oh, and Adobe's customer treatment might be debatable, but that helpful customer you quoted was a regular abuser of other forum users, so I like to see a silver lining from that post.
    * Prefer Embedded thumbnails was also selected.
    Message was edited by: Yammer P

  • Why would an iCloud backup file be grayed out on an initial iPhone 5s setup screen?

    I have a 4s with the latest update and recently upgraded to a 5s. I backed everything up in iCloud on the 4s before setting up the 5s. After everything is done, I stated the 5s setup. However, after I select 'restore from iCloud,' the backup file I need from my 4s is grayed out (no error message) and is not selectable.
    My first thought was that the new 5s didn't have the latest update. So I started the phone, updated it, and then followed the recommended instructions on how to restore a backup file. The restoration seemes to wipe the ios update and the backup file is still gray.
    Scoured the forums and google for an answer and came up with nothing. So I pose it to the group.

    UPDATE (13-Jan 2015): Took my phone do a different AppleStore and had an appointment with a Genius. The Genius hinted that I should call AppleCare (1-800-APL-CARE) and tell them my story. He said that it was not possible for him to do it, but that by escalating the problem to AppleCare that they may help. I was on the phone with a rep and his supervisor for about an hour before they told the Genius to replace my phone as a one-time out-of-warranty replacement. They stated that because the phone was working fine before the update, and showed no damage, that they would grant my request. Yay Apple for making this right!
    This is a known bug, error 101 or something.  Only solution they have at the moment is warranty replacement.

  • Time Machine wants 16 days to do an initial backup.  ps shows PRI = 33 with NI = 0.   But I can not get sudo renice to set PRI less than 15.  And renice sets NI directly with strange behavior for PRI. Any suggestions?

    Time Machine said it would take 16 days to do an initial backup, and indeed, after many days it is less than a quarter done.   (The problem started when I put in a new bank disk for Time Machine to write to for its backup file.)
    Activity Monitor shows that the process name is   backups   with Process ID   6060.
    Then putting this PID in Terminal UNIX command ps gave:
    EdsMacPro-1:~ ed$ ps -l -p 6060
      UID   PID  PPID        F CPU PRI NI       SZ    RSS ...
        0  6060     1  1004004   0  33  0  2556488  29040 ...
    Wow!  A priority of 33! 
    Don't know how that happened, but the way to fix that (I thought) is with renice. 
    But renice doesn't work.
    After a lot of playing with renice and ps, it looks as though renice can not make the priority better than (no less than) 15.
    And the parameter you put in, that according to the man page that is supposed to be priority, turns out to be "nice index", with priority changed by sometimes subtracting or sometimes adding either this number or twice this number - down to a limit of priority no less than 15.
    EdsMacPro-1:~ ed$ ps -l -p 6060
      UID   PID  PPID        F CPU PRI NI       SZ    RSS ...
        0  6060     1  1004004   0  33  0  2556488  29040 ...
    EdsMacPro-1:~ ed$ sudo renice 5 -p 6060
    EdsMacPro-1:~ ed$ ps -l -p 6060
      UID   PID  PPID        F CPU PRI NI       SZ    RSS  ...
        0  6060     1  1004004   0  28  5  2555964  29028  ...
    EdsMacPro-1:~ ed$ sudo renice -5 -p 6060
    EdsMacPro-1:~ ed$ ps -l -p 6060
      UID   PID  PPID        F CPU PRI NI       SZ    RSS  ...
        0  6060     1  1004004   0  38 -5  2555964  29028  ...
    EdsMacPro-1:~ ed$ sudo renice -15 -p 6060
    EdsMacPro-1:~ ed$ ps -l -p 6060
      UID   PID  PPID        F CPU PRI NI       SZ    RSS  ...
        0  6060     1  1004004   0  48 -15  2555964  29028 ...
    EdsMacPro-1:~ ed$ ps -l -p 6060
      UID   PID  PPID        F CPU PRI NI       SZ    RSS  ...
        0  6060     1  1004004   0  48 -15  2555964  29028 ...
    EdsMacPro-1:~ ed$ sudo renice -n -5 -p 6060
    EdsMacPro-1:~ ed$ ps -l -p 6060
      UID   PID  PPID        F CPU PRI NI       SZ    RSS  ...
        0  6060     1  1004004   0  53 -20  2555964  29028 ...
    EdsMacPro-1:~ ed$
    This is with OSX 10.7.5 and Terminal 2.2.3 on an early 2009 Mac Pro with lots of memory.
    What am I dong wrong, and any suggestions for how to fix my Time Machine process?

    The backup file size is 1.67 TB.*
    That's across the internal bus of a 2009 quad-core Mac Pro - which is pretty fast.
    Copying an hour's worth of MPEG-2 HD takes about a minute.
    I do a fresh backup from scratch about once a year, and the last time it finished over night.
    This time the first Time Machine backup is only about 1/5 complete after many days, and Activity Monitor shows essentially no use of disk drives or of CPU.  And in the first note I pointed out what is gleaned by using Terminal to execute the UNIX ps command. The priority of the running Time Machine process looks incorrect to me. 
    I could be wrong, but I think the problem is process priority, not file size.
    I am unable to set priority to 0 or a negative number.  Can someone straighten me out on how to do that?
    [*The machine has four 1.5 TB disk drives in it plus lots of memory.  Two of the physical drives are configured as one 3 TB backup drive (RAID concatanated).]

  • Initial Backup with Time Machine Stalls

    I bought a brand new high end external hard drive so that I could use time machine. When I first hooked it, it went through the usual problems, so I came to the forum and reformatted and partitioned my hard drive according to those threads. I tried to do a new initial backup and the backup stalled at 12.87gb of 46gb total. I tried to use the disk repair utility to repair any problems on my original hard drive and it reported nothing wrong. All night, though, time machine would try to make that initial backup and stall at the exact same point.
    Thoughts?

    This was happening to me too. It would get to a certain point and just stall there forever until I manually quit the process using the Activity Monitor. For me, it turned out to be that a certain set of files on my drive had their group set to "nogroup" (these were files generated by an Apache process with MAMP Pro if that makes any difference) and this was causing the backup to fail.
    Basically, what I'd do is try to narrow down where the backup is failing by adding folder to the Exclude list until you get a successful backup, then open up the last folder that it failed with, and start excluding folders in there until you get another successful backup, etc. Basically you're just trying to find the set of files that is causing Time Machine to choke. This is how I ended up finally finding these files with bad owner attributes. Correct the file's attributes and you should be able to do a successful backup. The actual problem in my case was due to the use of MAMP Pro. If that means anything to you, I posted more info here:
    http://mirthlab.com/2008/04/05/mamp-might-break-your-time-machine-backups/
    Hope that helps.
    P.s. Repair permissions is useless in this case.

  • TC initial Backup: 46GB System: 53GB Problem?

    I did not exclude anything. But still there is gap between the size of my system and the initial backup.sparesbundle. 53Gb:46Gb.
    How can this be?

    That seems somewhat odd to me. Based on my stats, my initial backup was just a little over 88 GB, and right now, having added some files there is a 88.28 GB on my Mini's physical HD.

  • Time Machine 108GB initial backup about 2.5 hours

    I had a few issues getting Time Machine to do it's initial backup.
    Here are some tips that might help you.
    1) In System Preferences, Spotlight, Privacy, add the external drive so it will not be indexed (included in Spotlight searches). I would assume it's okay to remove that setting after the initial backup.
    2) Before doing the first Time Machine backup, do a Shut Down... and then press the power button to boot up.
    3) During the initial backup. Do not open the Finder. At least, don't open the Finder for the backup drive. When I did that, the drive would start thrashing and the data transfer would slow to a crawl. Not sure what the heck the drive was doing.
    4) With a WD My Book Premium 320GB Drive, connected via FireWire, I got about 0.7 - 0.8GB copied per minute. When the backup was running too slow, it was about 30 - 40MB per minute (that would have taken forever.)
    Here's the whole story:
    I turned Time Machine on in the System Preferences and selected my Western Digital My Book Premium 320GB drive(connected via FireWire 400). I was already doing backups to this drive with ChronoSync, but there was enough room for it to do the backup of my system with room to spare. (I will free up more space by deleting that backup after I'm sure Time Machine is good.) Time Machine started doing it's initial backup and I noticed that it was going very slow... about 25GB after about 3 hours, which is pretty pathetic. I stopped it because the drive was thrashing like crazy and it didn't seem to make sense that it was doing that. It seemed like Spotlight might be trying to simultaneously index the drive, thus slowing things down. I added the drive to the Privacy setting on Spotlight, so it is now excluded. Then, I deleted the Backups.backupdb folder and emptied the Trash. After that, I rebooted. I then started the whole Time Machine initial backup again and it seemed to run much faster, so I let it go for a bit. I had about 25GB copied after about 30 minutes. Much faster. However, I decided to open up Finder and take a look at the Backups.backupdb folder to see what it looked like. After doing that and seeing the *.inprogress file, the drive started thrashing again and the copy slowed down. I stopped it again, deleted the folder again and rebooted. Started Time Machine initial copy again. Very slow this time. So, again, I stopped it, deleted the backup folder and this time, I shut the computer down. I let it sit for 10 seconds or so, then started it back up. Started the Time Machine initial copy again and it was going fast again. I think the shutdown cleared out something. ( a cache maybe?) Anyway, I made sure not to open Finder again during the initial backup and left it running. After about 2 - 2.5 hours, the initial backup of 108GB was complete. I just heard it do it's first hourly backup, which was basically nothing, because I haven't made any changes to anything yet.

    Time Machine backups to AirDisks (e.g. USB HDD attached to Extreme) is unsupported, but has been successful by some. As well, once you decide to move any old TM backups (HDD connected directly to the Mac) to an AirDisk, you cannot continue backing up to your previous TM backup. The format it saves to vs. a local HDD is different. The folder structure you see becomes a sparsebundle/disk image via the AirDisk.
    If you are interested in proceeding with your plan, check these links out:
    http://discussions.apple.com/thread.jspa?messageID=8225748&#8225748
    http://discussions.apple.com/thread.jspa?messageID=8650723&#8650723
    http://jamesshore.com/Blog/How-to-Accelerate-Time-Machine.html

  • Restore to factory, failed backups, files can't be found etc etc - Win7?

    Multiple probs...
    have got to the point that wondering if there is an iTunes/Win7 issue...
    Apple product: iPhone 3Gs 32GB*
    Computer OS: Win7
    +* NB: Throughout all of these issues iTunes repeatedly showed capacity as only 4GB, then at some point would switch to partially showing correct capacity (ie. had diff information between.. capacity shown in summary details, and that shown in used/free space status bar), OR would switch to fully showing correct capacity info (ie. summary details and used/free status bar info would agree).+
    *ISSUE 1*
    Orig issue - stopped being able to add music/video. Error message something like found folder where expected file.
    *ISSUE 2*
    Backed up iPhone (backup appeared successful.
    Restored phone to factory settings (appeared successful)
    Tried to restore backup > iTunes error message "iTunes could not... because the backup session failed" *NB: Searched computer, found the location that iTunes saves backup, files ARE there, and checked all photos and contacts are there (just in format that will need to translate if need to access via non-iTunes means)*
    *ISSUE 3*
    (Considered that might have been something wrong with my orig files, I decided to test with newly reset iPhone.)
    Set up as new phone (as no choice).
    Set up new music and added to phone (appeared successful; music visible on phone).
    Repeated with more music; then started to get error message (for tracks that had orig been added successfully "The iPhone cannot be synced. The required file could not be found"
    *ISSUE 4*
    Tried to reset again to factory.
    Had to use the Hard Reset method (simultaneously hold power button & home button, til slide bar for power off. Powered off. With iTunes running, hold down home button as plug into computer. iTunes recognises, asks if wish to reset device. Say yes, proceed through entire process, including entering simcard lock code, looks successful. Phone then has the "connect to iTunes"image.
    Did this repeatedly without success (always returned to be frozen on the connect to iTunes image. Tried all sorts of combinations - unplugging, rebooting pc, nothing worked... once phone got to this point every time it was plugged in iTunes froze, as soon as unplugged iTunes fully functional. Considered that iTunes might be processing slowly, so searched again... found webpage said to "Keep your device connected until the Connect to iTunes screen goes away or you see iPhone is activated." ref http://support.apple.com/kb/HT1414
    So repeated factory restore, and at end left phone connected overnight and still no change (still displaying connect to iTunes image). In morning, still no progress (still showing connect to iTunes image).
    *ISSUE 5*
    Happened to unplug phone, and replug into computer (not holding down home button or anything). iTunes then finally recognised phone. However, when tried to restore backup repeatedly still get error message "iTunes could not... because the backup session failed"
    So unless set up as new phone again, am stuck.
    Back to ISSUE 2/3 status.
    Expect that if go ahead with setting up as new phone again, will not be able to backup phone successfully, and at some stage will stop being able to add music etc.
    *ISSUE 6*
    Have tried to go ahead with setting up new phone. Still no success.
    Multiple error messages, most recent being
    "The iPhone X cannot be synced. A folder was specified instead of a file."
    Are there known problems with Windows 7? Or is this apple software issue? Apple hardware?<</div>
    At this stage I no longer have a phone (it my phone for everywhere), or sanity buster for 15-20 hours/week commuting. Not particularly comfortable with that...
    Message was edited by: RainingOutside
    Message was edited by: RainingOutside

    Hi, thanks for your feedback.
    No. None of music in iTunes synced. By "none of them showing probs"... Meant that iTunes can see all of those files, so no prob of that type; HOWEVER those files cannot be synced to iPhone. This is current status. Previously files HAD synced to iPhone.
    Ie one of first things that did was to reset all to ensure that working with only small test sample to minimize room for corrupted files.
    So situation is phone reset to factory; newly installed iTunes on new laptop, with new iPhone profile. In iTunes only small number of music files, that I've newly added to reduce chance that those files corrupted.
    From all that reading, and from discussions having with few fellow developers/analysts at work, thoughts are that iTunes not playing nice with 62bit Win7.
    Does anyone have contact with apple to have confirmed?
    There are number threads even just in this forum, reflecting same thoughts
    Cheers

  • Time Machine "cleaning up" in the middle of my initial backup

    I am trying to backup using time machine to a brand new external firewire drive that I've just formatted. The initial backup is about 150GB and about 20GB of the way into the backup time machine stops copying and the status window says "cleaning up" and then things seem to hang indefinitely. I've already tried deleting time machine preferences, what's going on here and how can I fix?
    Message was edited by: Jensen Gelfond

    Well deleting stuff won't help in the middle of a backup. Cancel the backup and re-prep the backup drive as follows:
    Drive Preparation
    1. Open Disk Utility in your Utilities folder.
    2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Click on the Partition tab in the DU main window.
    3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, set the partition scheme to GUID then click on the OK button. Click on the Partition button and wait until the process has completed.
    4. Select the volume you just created (this is the sub-entry under the drive entry) from the left side list. Click on the Erase tab in the DU main window.
    5. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, check the button for Zero Data and click on OK to return to the Erase window.
    6. Click on the Erase button. The format process can take up to several hours depending upon the drive size.
    Reconfigure TM preferences to select the backup drive and configure your backup preferences, then let TM do its work.
    Note that before performing a backup you should be sure that the system you are backing up is clean. So I would consider some basic things:
    A. Repair the Hard Drive and Permissions
    Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer. Now restart normally.
    If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
    B. Kappy's Personal Suggestions for OS X Maintenance
    For disk repairs use Disk Utility. For situations DU cannot handle the best third-party utilities are: Disk Warrior; DW only fixes problems with the disk directory, but most disk problems are caused by directory corruption; Disk Warrior 4.x is now Intel Mac compatible. TechTool Pro provides additional repair options including file repair and recovery, system diagnostics, and disk defragmentation. TechTool Pro 4.5.1 or higher are Intel Mac compatible; Drive Genius is similar to TechTool Pro in terms of the various repair services provided. Versions 1.5.1 or later are Intel Mac compatible.
    OS X performs certain maintenance functions that are scheduled to occur on a daily, weekly, or monthly period. The maintenance scripts run in the early AM only if the computer is turned on 24/7 (no sleep.) If this isn't the case, then an excellent solution is to download and install a shareware utility such as Macaroni, JAW PseudoAnacron, or Anacron that will automate the maintenance activity regardless of whether the computer is turned off or asleep. Dependence upon third-party utilities to run the periodic maintenance scripts had been significantly reduced in Tiger and Leopard. These utilities have limited or no functionality with Snow Leopard and should not be installed.
    OS X automatically defrags files less than 20 MBs in size, so unless you have a disk full of very large files there's little need for defragmenting the hard drive. As for virus protection there are few if any such animals affecting OS X. You can protect the computer easily using the freeware Open Source virus protection software ClamXAV. Personally I would avoid most commercial anti-virus software because of their potential for causing problems.
    I would also recommend downloading the shareware utility TinkerTool System that you can use for periodic maintenance such as removing old logfiles and archives, clearing caches, etc. Other utilities are also available such as Onyx, Leopard Cache Cleaner, CockTail, and Xupport, for example.
    For emergency repairs install the freeware utility Applejack. If you cannot start up in OS X, you may be able to start in single-user mode from which you can run Applejack to do a whole set of repair and maintenance routines from the commandline. Note that AppleJack 1.5 is required for Leopard. AppleJack 1.6 is compatible with Snow Leopard.
    When you install any new system software or updates be sure to repair the hard drive and permissions beforehand. I also recommend booting into safe mode before doing system software updates.
    Get an external Firewire drive at least equal in size to the internal hard drive and make (and maintain) a bootable clone/backup. You can make a bootable clone using the Restore option of Disk Utility. You can also make and maintain clones with good backup software. My personal recommendations are (order is not significant):
    Backuplist
    Carbon Copy Cloner
    Data Backup
    Deja Vu
    iBackup
    JaBack
    Silver Keeper
    MimMac
    Retrospect
    Super Flexible File Synchronizer
    ynchronizer
    SuperDuper!
    Synchronize Pro! X
    SyncTwoFolders
    Synk Pro
    Synk Standard
    Tri-Backup
    Visit The XLab FAQs and read the FAQs on maintenance, optimization, virus protection, and backup and restore.
    Additional suggestions will be found in Mac Maintenance Quick Assist.
    Referenced software can be found at CNet Downloads or MacUpdate.
    Message was edited by: Kappy

  • Is Time Machine under Snow Leopard faster only for the initial backup?

    A few days ago, I upgraded to Snow Leopard -- via clean install, manual reinstallation of apps, etc. So understandably, the first Time Machine backup to a preexisting store on an original 500 GB Time Capsule is going to be huge and take a long time. Apple claims that TM is 40% faster on the initial backup, but are there speed improvements as well? I was surprised by the slowness; I started it before going to bed, and it wasn't nearly done when I woke up:
    http://support.apple.com/kb/HT1770
    Jan 6 01:29:52 Musa com.apple.backupd[438]: Copied 8.3 GB of 59.3 GB, 9299 of 250057 items
    Jan 6 02:29:52 Musa com.apple.backupd[438]: Copied 9.6 GB of 59.3 GB, 35209 of 250057 items
    Jan 6 03:29:52 Musa com.apple.backupd[438]: Copied 11.5 GB of 59.3 GB, 48441 of 250057 items
    Jan 6 04:29:52 Musa com.apple.backupd[438]: Copied 12.9 GB of 59.3 GB, 109846 of 250057 items
    Jan 6 05:29:53 Musa com.apple.backupd[438]: Copied 17.4 GB of 59.3 GB, 140388 of 250057 items
    Jan 6 06:29:54 Musa com.apple.backupd[438]: Copied 26.1 GB of 59.3 GB, 151723 of 250057 items
    Jan 6 07:29:54 Musa com.apple.backupd[438]: Copied 36.9 GB of 59.3 GB, 167431 of 250057 items
    Jan 6 08:20:04 Musa com.apple.backupd[438]: Copied 219433 files (38.0 GB) from volume Gigas.
    The throughput rate is quite variable, but at its best, it's only about 2.7 MB/sec. Is that to be expected, or would I have to start a new backup to see speed improvements?

    Kappy wrote:
    i'd say you are concerned over nothing.
    Not sure I agree. Look at this system.log output:
    Jan 6 19:54:22 Musa com.apple.backupd[7571]: Starting standard backup
    Jan 6 19:54:22 Musa com.apple.backupd[7571]: Attempting to mount network destination using URL: afp://odysseus@Time%20Capsule.afpovertcp.tcp.local/odysseus
    Jan 6 19:54:30 Musa com.apple.backupd[7571]: Mounted network destination using URL: afp://odysseus@Time%20Capsule.afpovertcp.tcp.local/odysseus
    Jan 6 19:54:33 Musa com.apple.backupd[7571]: Disk image /Volumes/odysseus/Musa_002332d5c37e.sparsebundle mounted at: /Volumes/Backup of Musa
    Jan 6 19:54:33 Musa com.apple.backupd[7571]: Backing up to: /Volumes/Backup of Musa/Backups.backupdb
    Jan 6 19:54:42 Musa com.apple.backupd[7571]: Node requires deep traversal:/ reason:must scan subdirs|
    Jan 6 20:00:50 Musa com.apple.backupd[7571]: Compacting storage: 72.07 GB requested (including padding), 58.36 GB available before compacting
    Jan 6 20:00:50 Musa com.apple.backupd[7571]: Stopping backup.
    Jan 6 20:00:50 Musa com.apple.backupd[7571]: Backup canceled.
    Jan 6 20:00:53 Musa com.apple.backupd[7571]: Ejected Time Machine disk image.
    Jan 6 20:00:53 Musa com.apple.backupd[7571]: Compacting backup disk image to recover free space
    Jan 6 20:01:12 Musa com.apple.backupd[7571]: Completed backup disk image compaction
    Jan 6 20:01:12 Musa com.apple.backupd[7571]: Starting standard backup
    Jan 6 20:01:12 Musa com.apple.backupd[7571]: Network destination already mounted at: /Volumes/odysseus
    Jan 6 20:01:14 Musa com.apple.backupd[7571]: Disk image /Volumes/odysseus/Musa_002332d5c37e.sparsebundle mounted at: /Volumes/Backup of Musa
    Jan 6 20:01:14 Musa com.apple.backupd[7571]: Backing up to: /Volumes/Backup of Musa/Backups.backupdb
    Jan 6 20:01:20 Musa com.apple.backupd[7571]: Node requires deep traversal:/ reason:must scan subdirs|
    Jan 6 20:07:26 Musa com.apple.backupd[7571]: Starting pre-backup thinning: 72.07 GB requested (including padding), 58.36 GB available
    Jan 6 20:10:46 Musa com.apple.backupd[7571]: Deleted backup /Volumes/Backup of Musa/Backups.backupdb/Musa/2010-01-03-131536: 58.42 GB now available
    Jan 6 20:12:10 Musa com.apple.backupd[7571]: Deleted backup /Volumes/Backup of Musa/Backups.backupdb/Musa/2010-01-04-094152: 58.52 GB now available
    Jan 6 20:13:02 Musa com.apple.backupd[7571]: Deleted backup /Volumes/Backup of Musa/Backups.backupdb/Musa/2010-01-04-073331: 58.57 GB now available
    Jan 6 20:13:02 Musa com.apple.backupd[7571]: Stopping backup.
    Jan 6 20:13:02 Musa com.apple.backupd[7571]: Backup canceled.
    Jan 6 20:13:08 Musa com.apple.backupd[7571]: Ejected Time Machine disk image.
    Jan 6 20:13:08 Musa com.apple.backupd[7571]: Compacting backup disk image to recover free space
    Jan 6 20:13:30 Musa com.apple.backupd[7571]: Completed backup disk image compaction
    Jan 6 20:13:30 Musa com.apple.backupd[7571]: Starting standard backup
    Jan 6 20:13:30 Musa com.apple.backupd[7571]: Network destination already mounted at: /Volumes/odysseus
    Jan 6 20:13:33 Musa com.apple.backupd[7571]: Disk image /Volumes/odysseus/Musa_002332d5c37e.sparsebundle mounted at: /Volumes/Backup of Musa
    Jan 6 20:13:33 Musa com.apple.backupd[7571]: Backing up to: /Volumes/Backup of Musa/Backups.backupdb
    Jan 6 20:13:41 Musa com.apple.backupd[7571]: Node requires deep traversal:/ reason:must scan subdirs|
    Jan 6 20:19:36 Musa com.apple.backupd[7571]: Starting pre-backup thinning: 72.07 GB requested (including padding), 58.57 GB available
    Jan 6 20:20:38 Musa com.apple.backupd[7571]: Deleted backup /Volumes/Backup of Musa/Backups.backupdb/Musa/2010-01-04-071252: 58.58 GB now available
    Jan 6 20:20:38 Musa com.apple.backupd[7571]: Removed all 1 expired backups, more space is needed - deleting oldest backups to make room
    Jan 6 20:25:17 Musa com.apple.backupd[7571]: Deleted backup /Volumes/Backup of Musa/Backups.backupdb/Musa/2009-07-31-231155: 60.81 GB now available
    Jan 6 20:25:17 Musa com.apple.backupd[7571]: Deleted 2 backups: oldest backup is now Aug 15, 2009
    Jan 6 20:25:17 Musa com.apple.backupd[7571]: Stopping backup.
    Jan 6 20:25:20 Musa com.apple.backupd[7571]: Backup canceled.
    Jan 6 20:25:24 Musa com.apple.backupd[7571]: Ejected Time Machine disk image.
    Jan 6 20:25:24 Musa com.apple.backupd[7571]: Compacting backup disk image to recover free space
    Jan 6 20:26:39 Musa com.apple.backupd[7571]: Completed backup disk image compaction
    Jan 6 20:26:39 Musa com.apple.backupd[7571]: Starting standard backup
    Jan 6 20:26:39 Musa com.apple.backupd[7571]: Network destination already mounted at: /Volumes/odysseus
    Jan 6 20:26:41 Musa com.apple.backupd[7571]: Disk image /Volumes/odysseus/Musa_002332d5c37e.sparsebundle mounted at: /Volumes/Backup of Musa
    Jan 6 20:26:41 Musa com.apple.backupd[7571]: Backing up to: /Volumes/Backup of Musa/Backups.backupdb
    Jan 6 20:26:49 Musa com.apple.backupd[7571]: Node requires deep traversal:/ reason:must scan subdirs|
    Jan 6 20:32:46 Musa com.apple.backupd[7571]: Starting pre-backup thinning: 72.07 GB requested (including padding), 60.81 GB available
    Jan 6 20:32:46 Musa com.apple.backupd[7571]: No expired backups exist - deleting oldest backups to make room
    Jan 6 20:47:38 Musa com.apple.backupd[7571]: Deleted backup /Volumes/Backup of Musa/Backups.backupdb/Musa/2009-08-15-182619: 65.12 GB now available
    Jan 6 20:47:38 Musa com.apple.backupd[7571]: Deleted 1 backups: oldest backup is now Aug 25, 2009
    Jan 6 20:47:38 Musa com.apple.backupd[7571]: Stopping backup.
    Jan 6 20:47:41 Musa com.apple.backupd[7571]: Backup canceled.
    Jan 6 20:47:47 Musa com.apple.backupd[7571]: Ejected Time Machine disk image.
    Jan 6 20:47:47 Musa com.apple.backupd[7571]: Compacting backup disk image to recover free space
    Jan 6 20:49:36 Musa com.apple.backupd[7571]: Completed backup disk image compaction
    Jan 6 20:49:36 Musa com.apple.backupd[7571]: Starting standard backup
    Jan 6 20:49:36 Musa com.apple.backupd[7571]: Network destination already mounted at: /Volumes/odysseus
    Jan 6 20:49:38 Musa com.apple.backupd[7571]: Disk image /Volumes/odysseus/Musa_002332d5c37e.sparsebundle mounted at: /Volumes/Backup of Musa
    Jan 6 20:49:38 Musa com.apple.backupd[7571]: Backing up to: /Volumes/Backup of Musa/Backups.backupdb
    Jan 6 20:49:46 Musa com.apple.backupd[7571]: Node requires deep traversal:/ reason:must scan subdirs|
    Jan 6 20:55:48 Musa com.apple.backupd[7571]: Starting pre-backup thinning: 72.06 GB requested (including padding), 65.12 GB available
    Jan 6 20:55:48 Musa com.apple.backupd[7571]: No expired backups exist - deleting oldest backups to make room
    Jan 6 21:05:11 Musa com.apple.backupd[7571]: Deleted backup /Volumes/Backup of Musa/Backups.backupdb/Musa/2009-08-25-185228: 67.32 GB now available
    Jan 6 21:05:11 Musa com.apple.backupd[7571]: Deleted 1 backups: oldest backup is now Sep 1, 2009
    Jan 6 21:05:11 Musa com.apple.backupd[7571]: Stopping backup.
    Jan 6 21:05:13 Musa com.apple.backupd[7571]: Backup canceled.
    Jan 6 21:05:22 Musa com.apple.backupd[7571]: Ejected Time Machine disk image.
    Jan 6 21:05:22 Musa com.apple.backupd[7571]: Compacting backup disk image to recover free space
    Jan 6 21:06:45 Musa com.apple.backupd[7571]: Completed backup disk image compaction
    Jan 6 21:06:45 Musa com.apple.backupd[7571]: Starting standard backup
    Jan 6 21:06:45 Musa com.apple.backupd[7571]: Network destination already mounted at: /Volumes/odysseus
    Jan 6 21:06:48 Musa com.apple.backupd[7571]: Disk image /Volumes/odysseus/Musa_002332d5c37e.sparsebundle mounted at: /Volumes/Backup of Musa
    Jan 6 21:06:48 Musa com.apple.backupd[7571]: Backing up to: /Volumes/Backup of Musa/Backups.backupdb
    Jan 6 21:06:57 Musa com.apple.backupd[7571]: Node requires deep traversal:/ reason:must scan subdirs|
    Jan 6 21:12:57 Musa com.apple.backupd[7571]: Starting pre-backup thinning: 72.06 GB requested (including padding), 67.32 GB available
    Jan 6 21:12:57 Musa com.apple.backupd[7571]: No expired backups exist - deleting oldest backups to make room
    Jan 6 21:25:51 Musa com.apple.backupd[7571]: Deleted backup /Volumes/Backup of Musa/Backups.backupdb/Musa/2009-09-01-060212: 69.89 GB now available
    Jan 6 21:25:51 Musa com.apple.backupd[7571]: Deleted 1 backups: oldest backup is now Sep 8, 2009
    Jan 6 21:25:51 Musa com.apple.backupd[7571]: Stopping backup.
    Jan 6 21:25:53 Musa com.apple.backupd[7571]: Backup canceled.
    Jan 6 21:26:00 Musa com.apple.backupd[7571]: Ejected Time Machine disk image.
    Jan 6 21:26:00 Musa com.apple.backupd[7571]: Compacting backup disk image to recover free space
    Jan 6 21:27:30 Musa com.apple.backupd[7571]: Completed backup disk image compaction
    Jan 6 21:27:30 Musa com.apple.backupd[7571]: Starting standard backup
    Jan 6 21:27:30 Musa com.apple.backupd[7571]: Network destination already mounted at: /Volumes/odysseus
    Jan 6 21:27:33 Musa com.apple.backupd[7571]: Disk image /Volumes/odysseus/Musa_002332d5c37e.sparsebundle mounted at: /Volumes/Backup of Musa
    Jan 6 21:27:33 Musa com.apple.backupd[7571]: Backing up to: /Volumes/Backup of Musa/Backups.backupdb
    Jan 6 21:27:41 Musa com.apple.backupd[7571]: Node requires deep traversal:/ reason:must scan subdirs|
    Jan 6 21:33:37 Musa com.apple.backupd[7571]: Starting pre-backup thinning: 72.06 GB requested (including padding), 69.89 GB available
    Jan 6 21:33:37 Musa com.apple.backupd[7571]: No expired backups exist - deleting oldest backups to make room
    Jan 6 21:45:33 Musa com.apple.backupd[7571]: Deleted backup /Volumes/Backup of Musa/Backups.backupdb/Musa/2009-09-08-081225: 72.34 GB now available
    Jan 6 21:45:33 Musa com.apple.backupd[7571]: Pre-backup thinning completed successfully: 1 backups were deleted
    Jan 6 21:45:33 Musa com.apple.backupd[7571]: Backup date range was shortened: oldest backup is now Sep 15, 2009

  • Adding Metadata to folders/ Searching Drive for Keywords not just one folder -  Bridge CC 2014

    Hello Adobe world,
    I'm trying to add Metadata to folders not the files. The files in the folders already have metadata and in one folder we have 360 images of the same thing. When I do a keyword search I don't want to go though 20+ sets of 360 duplicate files. I need to do keyword searching for folders. When I have tried adding keywords to the folders I get "the file cannot store xmp metadata" warning. I tried clearing the cache on the file because it said that would help in another forum but it did not help. Does any one know how to fix this? I don't know why we could not assign descriptions or keywords to folders. It would be very useful!!  Some one please help!
    as of 2/24/2015 -  This is still unanswered. I want to be able to find files throughout my whole drive based on the metadata tags I put on all my 100,000+ images. These 100,000+ images are dispersed thought out multiple folders. I need to be able to find all the files with specific Metadata tags in common but bridge will not let me search outside of one defined folder? HELP!
    Message was edited by: Jazmyn W

    Hi, Im going through a similar problem. Did you find a solution?? I need to find my files in Windows search bar.

  • Adding Metadata to PDF Form

    Hi, I'm trying to add some metadata to a pdf. I have the follow script in the form initialize event:
    if (form1.desc.nodes.namedItem("metadata") == null) then
    var oNode=xfa.form.createNode("text", "metadata")
    form1.desc.nodes.append(oNode)
    endif
    I receive the error message:
    Argument mismatch in property or function argument
    I also tried this code:
    if (form1.desc.nodes.namedItem("metadata") == null) then
    var oNode=xfa.form.createNode("text", "metadata")
    oNode.value = "Test Data"
    form1.desc.nodes.append(oNode)
    endif
    Which gave me this error:
    accessor "oNode.value" is unknown
    It appears that the oNode object is not being created.
    Any suggesting how I can add Metadata to the PDF?

    Hi,
    This is the code I use to place metadata into the pdf file. If you open
    the resulting pdf file using Notepad, the metadata is visible as readable
    text in the file. I'm not sure the same approach can be used to add
    metadata as viewed under Document Properties. We are not using it that
    way. Maybe by changing the node name?
    if ((EMAIL_SUBJECT1.rawValue != "")&&(EMAIL_SUBJECT1.rawValue != null))
            var vDesc=xfa.template.data.desc;
            var oNode1=xfa.template.createNode("text", "EMAIL_SUBJECT1");
            vDesc.nodes.append(oNode1);
    vDesc.nodes.namedItem("EMAIL_SUBJECT1").value=EMAIL_SUBJECT1.rawValue;
    Andrew Zwickl | Worldwide Information Systems |
    Eastman Kodak Company | 1669 Lake Ave | Rochester, NY 14652-4455 |
    VOX: 585-477-1402
    FAX: 585-588-4123
    EMail: [email protected]
    www.kodak.com
    From:
    SI_MSD7 <[email protected]>
    To:
    zwickl <[email protected]>
    Date:
    08/10/2012 06:18 PM
    Subject:
    Adding Metadata to PDF Form
    Re: Adding Metadata to PDF Form
    created by SI_MSD7 in LiveCycle Designer - View the full discussion
    Bruce / Zwicki - or anyone who can assit...
    How did you get this to work? I
    I'm looking for a way to add/inject values (keywords) into the form's
    meta-data by retrieving the info/values from user input.
    To test the above solution, I added the following script to the initialize
    event as referenced, but I'm not sure what is happening:
    if (form1.desc.nodes.namedItem("metadata") == null)
    var oNode=xfa.form.createNode("text", "metadata")
    form1.desc.nodes.append(oNode)
    1. Do I need a field on the page?
    2. What part of the above script affects the meta-data?
    Thanks!
    Replies to this message go to everyone subscribed to this thread, not
    directly to the person who posted the message. To post a reply, either
    reply to this email or visit the message page: [
    http://forums.adobe.com/message/4613534#4613534]
    To unsubscribe from this thread, please visit the message page at [
    http://forums.adobe.com/message/4613534#4613534]. In the Actions box on
    the right, click the Stop Email Notifications link.
    Start a new discussion in LiveCycle Designer by email or at Adobe Forums
    For more information about maintaining your forum email notifications
    please go to http://forums.adobe.com/message/2936746#2936746.

  • Initial Backups Failing

    I've tried to research the answer to this problem, but have found only advice for people who have had Time Machine work correctly for them before, and suddenly stop backing up correctly after a while.
    +My problem is that Time Machine will not complete the initial backup.+ When I set it to backup from my MacBook Pro running 10.5.5 (just upgraded from Tiger a week ago, woo-hoo!) to my FireWire 500GB WD drive, the backup starts correctly. All is fine until it gets to a certain point, typically in the 6-10 GB area of backing up (that is, after backing up about 6-10 GB of data). At that point, an error message pops up, saying the backup could not be completed. If I tell it to do it again, it might back up an additional 4 or 5 GB, but then it stops again, and after that it only gets about 100 MB of additional data backed up before it just stops.
    I have 80 GB of data on my internal drive, and hundreds of gigs free on the external drive, so space is not an issue. When I first encountered this problem, I did some research and found an article on this website by Apple to reformat the external drive. I did so, but it seems to have made no difference. I also later found some advice to, after a failed backup, drag the incomplete backup file from the TM disk to the trash and then start the backup over again, but that did not work either.
    Does anyone know why this will not work for me? I can't even get passed the initial backup, and for me that is a little concerning.

    UPDATE:
    I have been playing around (frustratedly) and I do not think the problem lies in the external hard-drive, but in the internal one. The reason why TM won't back up seems to be because of the files on my computer. I look through the console to find out what files TM stumbled over, and I've begun excluding them as they come up. First it was the system folders, then it was my Aperture library, and now it's my iPhoto library. More specifically, there are data files for specific photos in my iPhoto library that seem to be corrupt. The console tells me that TM stumbled on them, and when I locate the corrupt files in the Finder to delete them, Finder crashes before I can do so.
    I'm becoming very irritated with Time Machine and my computer. Please help me get this to "just work", I know it's probably something I did accidentally that's causing this but I don't know what or how to remedy it.

Maybe you are looking for