TM Backup Failed! Sometimes

I just upgraded to Leopard, primarily for the Time Machine function, and usually it works just fine. I am backing up to a 500 gigabyte Maxtor Firewire drive, which is connected to the iMac through an 80 gigabyte Maxtor external drive. About once or twice a day I get the 'Backup Failed' message in the TM preference pane. Has anyone found a fix for this recurring problem? Is this really a problem?
Thanks in advance,
Bob

Time Machine has been running fine on my 10.5.4 system, but today a backup failed
with the message "...error occurred while copying files..." Looking through the
forums, I saw a mention that one should not use iTunes during a backup. In fact,
I was synching my iPhone during the failed backup. Looking at the log using
"sudo grep backupd /var/log/system.log", I saw that it failed to back up
/Users/levoy/Pictures/.DS_Store. My iPhone has lots of photos on it, which are
stored in Pictures/. This comes close to a smoking gun. Lesson: don't synch your
iPhone during a Time Machine backup. Apple should track down and fix this bug.
By the way, my iPhone software is version 2.0.2, and my backup drive is a 1TB WD
drive from Apple. I have disabled sleeping the drive, as suggested elsewhere in
these forums, to avoid hangs.

Similar Messages

  • Time Capsule backup failed, volume read-only, can't delete

    I've only been using Time Machine and Time Capsule for 2 months. This week it stopped working. First error message:
    "Unable to complete backup. An error occurred while copying files to the backup volume."
    Checking the Time Machine preferences, "Last backup" would read "backup failed"
    When I got this error, all the wireless functions went offline, even thought the TC light was still green.
    I would shut down, shut down the Time Capsule, shut off my modem reboot everything in order.
    I would come back online, but after about 20 minutes to 1.5 hours into the next backup, same thing would happen again.
    Next error message:
    "Disk repair. The disk 'Backup of [my computer]' was not repairable by this computer. It is being made available to you with limited functionality. You must backup your data and reformat the drive."
    Then: "Time Machine Error: The backup volume is read only. To select a different volume ... Time Machine preferences ... "
    I spoke to someone at Apple, who sent me the Time Machine Troubleshooting page:
    http://support.apple.com/kb/HT3275?viewlocale=en_US
    Steps I went through:
    1. updated my system software
    2. updated the TC firmware to 7.4.1
    3. dragged the sparsebundle to DiskUtility. It took a while (more than an hour?) but said the disk could not be repaired. When I tried again, the repair function wouldn't run.
    4. tried to delete the sparsebundle, but it would choke at almost the end, sometimes it would just crash the finder, sometimes say "Sorry, an unexpected error occurred," sometimes "Operation cannot be completed because the item 'bands' is in use." I even tried to Stuff the bundle with 'delete original' checked, but the stuffing, after about 15 hours, jammed near the end (stuffed 20 gigs of 35 gigs).
    5. tried to reselect the TC, and run backup anyways ... now it can't find the volume, back to the error messages and crashing Finder
    6. checked password in Keychain, all ok.
    Now what??
    Do I use Airport Utility to erase it? At least TC is still showing up there. Or press the rest button on the back of the Time Capsule to reset to factory defaults?
    I've resigned myself to losing my backups. Now I would just like to get it up and running again.
    In hopes,
    Linda

    Now what??
    Do I use Airport Utility to erase it? At least TC is still showing up there. Or press the rest button on the back of the Time Capsule to reset to factory defaults?
    Yes, open Airport Utility and erase the drive. Once the sparsebundle is corrupted beyond repair there's little more you can do. However, do not reset the TC. Doing so will not erase the drive, but it will remove any custom configurations you may have setup for the router. Only if that part of the TC is also misbehaving should you use the reset button.

  • FCS DB backup failed w/error: "couldn't connect to database "template1"

    Hi,
    I am testing two different FCS systems (on two different machines, the same config).
    I wanted to backup FCS on one machine manually and it was not possible. I tried to do the same on the second machine and it was also not possible. I checked logs for automatic backup on both machines and everything worked until 22nd of April.
    I am not sure if I did download some update, but I am sure I didn't change anything on both machines nor FCS settings.
    I got this error message when I tried to backup:
    *Backup failed: pg_dumpall exited with code 1.*
    *Checking for other backup processes...*
    *Starting database backup to path '/Volumes/ProxyA/FCSBackups/Final Cut Server DB Backup on fcserver-1 at 2009-04-23 0000.zip'...*
    *pg_dumpall: could not connect to database "template1": could not connect to server: Connection refused*
    *Is the server running locally and accepting*
    *connections on Unix domain socket "/tmp/.s.PGSQL.5433"?*
    Both systems work normally. I "just" can't backup the DB.
    What happened ?
    Thank you.

    Hi Sam,
    Sometimes it is only because you have not set the environment correctly (ORACLE_HOME, ORACLE_SID).
    Is your TNSNAMES.ORA correct?
    If you do a "ps -ef |grep oracle" you should get a list of processes. Make sure you see PMON and SMON processes as well as the LSNR processes.
    If you don't see the LSNR processes start the listener.
    If this don't help try to start the DB manually and check with tsnping, otherwise come back again with mor info.
    regards
    Wolfgang

  • 10.5.8 Time Machine  Backup Failed Due to Cookie Not Matching?

    Been using Time Machine with no problems with 10.5.6 and 10.5.8, but have first problems since 10.5.8. After my iMac wakes from sleep, sometimes I get the error message that the external USB drive that I'm using for Time Machine was removed incorrectly, which is not correct. If I do not get this message and everything looks okay, the next Time Machine backup normally fails and if I check the logging in the widget it tells me that backup failed because the cookie didn't match and it may not be the correct drive. If I restart my iMac, Time Machine works again without problem until the next sleep. Before installing 10.5.8 Time Machine was perfect! Any ideas anyone?

    Hi again:
    Not really. A restart can be therapeutic at times as a lot of things are reset. I have worked with computers for over 50 years and there are still some things that happen that defy logical explanation!
    Trashing a preference file sometimes helps things. A corrupt preference file (rare, but it happens) can cause all sorts of odd behavior.
    Barry

  • UCCX Backup failed

    Hi everyone,
    I have a UCCX backup failed issue with one of our clients.
    It's a UCCX 5.0(1)-SR02ES08-Build083. When i tried backup, the bar stopped at 5% and the error message is like this:
    Unable to contact Call Manager. Please make sure that the Call Manager is running and connected to the network com.cisco.archive.impl.component.cluster.ClusterArchiveComponent; nested exception is: com.cisco.archive.ArchiveException: Fail to acquire bootstrap mutex; nested exception is: com.cisco.app.ApplicationException: can not acquire ClusterMutex; nested exception is: com.cisco.config.ConfigException: Get config record - error: catch cisco.config.ConfigException UnmarshalException; nested exception is: javax.xml.bind.UnmarshalException: Premature end of file. - with linked exception: [org.xml.sax.SAXParseException: Premature end of file.], refer to the MCVD logfiles for more details
    Can anyone give me some idea?
    Thanks
    James

    Hi James,
    If backup is still failing after following Hoai's advice; please check to see if a lock has caused an issue with a previous backup. You can open appadmin and go to Tools > Backup and Restore > Status. If the backup has not run for sometime you most likely have a lock. You can do the following
    1. Go to 'C:\program files\wfavvid\ClusterData\Default\' folder on CRS server;
    2. Rename 'com.cisco.crs.cluster.config.LockConfig' folder to 'com.cisco.crs.cluster.config.LockConfig.bak';
    3. Restart nodemanager
    Then try a backup.
    Regards,
    Joe

  • IPad Air Backup Failing...

    Specs:
    iPad Air 32GB Version
    iTunes 11.1.3.8
    Prior to starting a backup, I have about 12GB free space. During the backup process, I get an error message stating that I'm almost out of free space, then I get an error stating that the backup failed in iTunes. I've noticed that prior to the backup, I had about 3GB of "other" used. After the backup fails, it shows over 10GB of 'other" used! I am unable to complete the backup and have no prior backup to restore to. Help!

    OK. I still believe that the bloated "other" is because of a corrupt sync/backup. Quite often that is the cause of the "other" growing in size like that. I also believe that this is the reason why you cannot successfully backup - the bloated "other" issue.
    Sometimes unsyncing and resyncing photos can clean that up. Sometimes you have to restore as new before it will go away. There are a number of "theories" on how to solve that problem.
    I hate to simply point you to a Google search, but start here, take a look at some of these discussions, suggestions, etc. and see if there is something that will work for you.
    https://www.google.com/search?q=how%20to%20rid%20iPad%20of%20%22other%22

  • Backup fails with I/O error unpredictably

    I have a TC running TM backing up two iMacs and a Mac Pro. One of the iMacs, which is connected wirelessly, will sometimes (~ once per day) fail with the following message on TM buddy:
    +Starting standard backup+
    +FSMountServerVolumeSync failed with error: -36 for url: afp://[Username]%20[Username]@Amborella.local/Amborella+
    +Backup failed with error: 19+
    "Amborella" being the name of the TC.
    If, when this occurs, I connect manually to the TC through Apple Talk and start a manual backup, it works fine. I've tried repairing the disk, but Disk Utility doesn't find a problem. The computer has a short, unique name under Sharing settings ("Cakile").
    Any suggestions?

    I probably should have mentioned that, before this problem arose, the hard drive of the computer in question died and was replaced, following which I restored the files from the TC.

  • Time Machine Backup Failed - Copy stage failed with error:11

    My TM backups started to fail on a Mac Book Pro running 10.5.8 a few weeks ago with the 'Copy stage failed with error:11' message. It seemed to happen after coming out of hibernation from clamshelling the laptop.
    This happened a few times before when I had initially set TM up so to 'fix' it I just blew away the TM backups and started fresh. I would rather not do that this time as I have accumulated 3 months worth of backups.
    My TM is on a samba share, I've searched a bit and followed a guide:
    http://blog.robberthamburg.nl/mac-osx-leopard-repair-a-time-machine-error-11-pro blem
    to try and fix the problem by deleting a .inProgress backup but this has not helped. unfortunately this has did not fix it. I had also read that there are sometimes problems with TM and Spotlight indexing so I have turned spotlight off completely. Still no luck.
    Here is a log dump of my latest backup attempt:
    Sep 12 01:31:59 lysithea /System/Library/CoreServices/backupd[763]: Backup requested by user
    Sep 12 01:31:59 lysithea /System/Library/CoreServices/backupd[763]: Starting standard backup
    Sep 12 01:32:04 lysithea /System/Library/CoreServices/backupd[763]: Mounted network destination using URL: smb://mdaemon@io:139/timemachine_lysithea
    Sep 12 01:32:04 lysithea /System/Library/CoreServices/backupd[763]: Backup destination mounted at path: /Volumes/timemachine_lysithea
    Sep 12 01:32:06 lysithea /System/Library/CoreServices/backupd[763]: Disk image /Volumes/timemachinelysithea/lysithea0025bcdeabda.sparsebundle mounted at: /Volumes/lysithea Time Machine
    Sep 12 01:32:06 lysithea /System/Library/CoreServices/backupd[763]: Backing up to: /Volumes/lysithea Time Machine/Backups.backupdb
    Sep 12 01:35:44 lysithea /System/Library/CoreServices/backupd[763]: No pre-backup thinning needed: 7.61 GB requested (including padding), 89.80 GB available
    Sep 12 01:35:44 lysithea /System/Library/CoreServices/backupd[763]: Waiting for index to be ready (-1 < 0)
    Sep 12 01:40:51 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 01:45:49 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 01:50:50 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 01:55:49 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:00:50 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:05:49 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:10:50 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:15:52 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:20:52 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:25:51 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:30:50 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:32:05 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:32:37 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:33:09 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:33:42 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:35:52 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:38:38 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:39:08 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:39:51 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:40:27 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:42:12 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:42:43 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:43:12 lysithea /System/Library/CoreServices/backupd[763]: Stopping backup.
    Sep 12 02:43:12 lysithea /System/Library/CoreServices/backupd[763]: Error: (-43) SrcErr:NO Copying /Users/mdaemon/Library/Preferences/com.apple.DirectoryUtility.plist to /Volumes/lysithea Time Machine/Backups.backupdb/lysithea/2009-09-12-013213.inProgress/466ADDEF-7D04-45 15-B024-C02ADF152EA7/Macintosh HD/Users/mdaemon/Library/Preferences
    Sep 12 02:43:12 lysithea /System/Library/CoreServices/backupd[763]: Copied 16247 files (5.9 GB) from volume Macintosh HD.
    Sep 12 02:43:12 lysithea /System/Library/CoreServices/backupd[763]: Copy stage failed with error:11
    Sep 12 02:43:18 lysithea /System/Library/CoreServices/backupd[763]: Backup failed with error: 11
    Sep 12 02:43:18 lysithea /System/Library/CoreServices/backupd[763]: Restarting backup after linking failure.
    Sep 12 02:43:18 lysithea /System/Library/CoreServices/backupd[763]: Starting standard backup
    Sep 12 02:43:18 lysithea /System/Library/CoreServices/backupd[763]: Backup destination alias resolved to path: /Volumes/timemachine_lysithea
    Sep 12 02:43:18 lysithea /System/Library/CoreServices/backupd[763]: Disk image /Volumes/timemachinelysithea/lysithea0025bcdeabda.sparsebundle mounted at: /Volumes/lysithea Time Machine
    Sep 12 02:43:18 lysithea /System/Library/CoreServices/backupd[763]: Backing up to: /Volumes/lysithea Time Machine/Backups.backupdb
    Sep 12 02:43:42 lysithea /System/Library/CoreServices/backupd[763]: Waiting for index to be ready (-1 < 0)
    Sep 12 02:51:03 lysithea /System/Library/CoreServices/backupd[763]: No pre-backup thinning needed: 509.8 MB requested (including padding), 83.21 GB available
    Sep 12 02:51:03 lysithea /System/Library/CoreServices/backupd[763]: Waiting for index to be ready (-1 < 0)
    Sep 12 02:51:09 lysithea /System/Library/CoreServices/backupd[763]: Indexing a file failed. Returned -12 for: /.DS_Store, /Volumes/lysithea Time Machine/Backups.backupdb/lysithea/2009-09-12-013213.inProgress/AB3F09D7-61EB-4D 9F-B0EF-AC4C1E0712EA/Macintosh HD/.DS_Store
    Sep 12 02:51:09 lysithea /System/Library/CoreServices/backupd[763]: Aborting backup because indexing a file failed.
    Sep 12 02:51:09 lysithea /System/Library/CoreServices/backupd[763]: Stopping backup.
    Sep 12 02:51:09 lysithea /System/Library/CoreServices/backupd[763]: Copied 0 files (0 bytes) from volume Macintosh HD.
    Sep 12 02:51:09 lysithea /System/Library/CoreServices/backupd[763]: Copy stage failed with error:11
    Sep 12 02:51:14 lysithea /System/Library/CoreServices/backupd[763]: Backup failed with error: 11
    Sep 12 02:51:15 lysithea /System/Library/CoreServices/backupd[763]: Ejected Time Machine disk image.
    Sep 12 02:51:18 lysithea /System/Library/CoreServices/backupd[763]: Ejected Time Machine network volume.
    Any help would be greatly appreciated

    mattdaemon wrote:
    My TM is on a samba share
    First problem: this is *not supported by Apple:* http://support.apple.com/kb/HT1733
    to try and fix the problem by deleting a .inProgress backup but this has not helped.
    Second problem: deleting (or changing or moving) things in TM backups via the Finder can hopelessly corrupt them.
    Sep 12 01:35:44 lysithea /System/Library/CoreServices/backupd[763]: Waiting for index to be ready (-1 < 0)
    Sep 12 01:40:51 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    These can usually be stopped by excluding the backups from any anti-virus scanning, and Spotlight indexing, at least on supported volumes. Unless you're sure you have Spotlight off entirely, try excluding your backups via System Preferences > Spotlight > Privacy.
    Sep 12 02:43:12 lysithea /System/Library/CoreServices/backupd[763]: Error: (-43) SrcErr:NO Copying /Users/mdaemon/Library/Preferences/com.apple.DirectoryUtility.plist to /Volumes/lysithea Time Machine/Backups.backupdb/lysithea/2009-09-12-013213.inProgress/466ADDEF-7D04-45 15-B024-C02ADF152EA7/Macintosh HD/Users/mdaemon/Library/Preferences
    Sep 12 02:51:09 lysithea /System/Library/CoreServices/backupd[763]: Indexing a file failed. Returned -12 for: /.DS_Store, /Volumes/lysithea Time Machine/Backups.backupdb/lysithea/2009-09-12-013213.inProgress/AB3F09D7-61EB-4D 9F-B0EF-AC4C1E0712EA/Macintosh HD/.DS_Store
    Sep 12 02:51:09 lysithea /System/Library/CoreServices/backupd[763]: Aborting backup because indexing a file failed.
    Both of these appear to indicate problems on your backup drive, perhaps directory problems. For a supported one, a +*Repair Disk+* (not permissions) will often fix it. If there's a way to run that on your backups, it's worth a try.
    It's also possible there's a problem on your internal HD, so it's worth doing a +*Verify Disk+* (not permissions) on it, too, via Disk Utility. If that shows errors, you'll have to boot from your Install disc and use it's copy of DU to repair them.

  • ACS 5.3.0.40 On-demand Full Backup failed.

    Hi,
    I have ACS 5.3.0.40 Primary Secondary Authenticators , of which the Scheduled backup has stopped.
    When checked the :
    Monitoring Configuration >
    System Operations >
    Data Management >
    Removal and Backup
    > Incremental Backup , it had changed to OFF mode. without any reason.
    The same was observed earlier too.
    I have made the
    Incremental Backup to ON and intiated the
    View Full Database Backup Now. But it wasn't successful and reported an Error:
    FullBackupOnDemand-Job Incremental Backup Utility System Fri Dec 28 11:56:57 IST 2012 Incremental Backup Failed: CARS_APP_BACKUP_FAILED : -404 : Application backup error Failed
    Later i did the acs stop/start  "view-jobmanager" and  initiated the On-demand Full Backup , but no luck, same error reported this time too.
    Has any one faced similar type of error /problem reported , please let me know the solution.
    Thanks & Regards.

    One other thing; if this does end up being an issue with disk space it is worth considering patch 5.3.0.40.6 or later since improves database management processes
    This cumulative patch includes fixes/enhancements related to disk management to avoid following issue
    CSCtz24314: ACS 5.x *still* runs out of disk space
    and also fix for
    CSCua51804: View backup fails   even when there is space in disk
    Following is taken from the readme for this patch
       The Monitoring and Reporting database can increase when as records are collected. There are two mechanisms to reduce this size and prevent it from exceeding the maximum limit.
    1. Purge: In this mechanism the data will be purged based on the configured data retention period or upon reaching the upper limit of the database.
    2. Compress: This mechanism frees up unused space in the database without deleting any records.
    Previously the compress option could only be run manually. In ACS 5.3 Patch 6 there are enhancements so it will run daily at a predefined time, automatically when specific criteria are met. Similarly by default purge job runs every day at 4 AM. In Patch 6 new option provided to do on demand purge as well.
    The new solution is to perform the Monitoring and Reporting database compress automatically.
    2.       New GUI option is provided to enable the Monitoring and Reporting database compress to run on every day at 5 AM. This can be configured under GUI Monitoring And Configuration -> System Operations -> Data Management -> Removal and Backup
    3.       Changed the upper and lower limit of purging of Monitoring and Reporting data. This is to make sure at lower limit itself ACS has enough space to take the backup. The maximum size allocated for monitoring and reporting database is 42% of /opt( 139 GB). The lower Limit at which ACS purges the data by taking the backup is 60% of maximum size Monitoring and Reporting database (83.42 GB). The upper limit at which ACS purges the data without taking backup is 80% of maximum size Monitoring and Reporting database (111.22 GB).
    4. The acsview-database compress operation stops all services till 5.3 patch 5 , now only Monitoring and Reporting related services are stopped during this operation.
    5. Provided “On demand purge” option in Monitoring and Reporting GUI. This option will not try to take any backup, it will purge the data based on window size configured.
    6. Even if the “Enable ACS View Database compress” option is not enabled in GUI then also automatic view database compress will be triggered if the physical size of Monitoring and Reporting database reached to the upper limit of its size.
    7. This automatic database compress takes place only when the “LogRecovery” feature is enabled, this is to make sure that the logging which happens during this operation will be recovered once this operation is completed. ACS generates alert when there is a need to do automatic database compress and also to enable this feature.
    8. Before enabling “LogRecovery” feature configure the Logging Categories in such way that only mandatory data to log into Local Log Target and Remote Log Target as Log collector under System Administration > ... > Configuration > Log Configuration
    This “LogRecovery” feature can recover the logs only if the logs are present under local log target.
    9       This automatic database compress operation also performed only when the difference between actual and physical size of Monitoring and Reporting database size is > 50GB.
    10 The new CLI “acsview” with option “show-dbsize” is provided to show the actual and physical size of the Monitoring and Reporting database. This is available in “acs-config” mode.
               acsview     show-dbsize     Show the actual and physical size of View DB and transaction log file

  • ACS 5.3 Backup fails

    ACS 5.3 on VM- backup fails all the time. I opened several tickets with Cisco, but still no luck.
    Here is one of the log message I got during the backup. Maybe someone can point out what the issue is.
    debugd[2933]: [31965]: config:kron: cs_api.c[1142] [daemon]: occurrence occurrence_backup1 could not be deleted.

    I just did it on my ACS 5.4 patch 6 (running on VMWare) backup to a Windows 2003 FTP server and it works without any issues:
    repository ftp_192.168.1.129
      url ftp://192.168.1.129/
      user Administrator password hash e50ffb9aabc8ccebe066f6239efeaa1ab728a16f2b2
    labacs2/admin# backup labacs2 repository ftp_192.168.1.129
    % Creating backup with timestamped filename: labacs2-140628-2059.tar.gpg
    Calculating disk size for /opt/backup/backup-labacs2-1403989173
    Total size of backup files are 27 M.
    Max Size defined for backup files are 13339 M.
    labacs2/admin#

  • Windows Server 2008 R2 Backup failing with error - 0x8004231F

    Hi,
    I have Windows Server 2008 R2 Web Edition. Everything was working fine until recently. I tried checking for the log files, but I see that there are no log files that are created now in the location C:\Windows\Logs\WindowsServerBackup. The only files that
    are being created recently are of the type mentioned below.
    Wbadmin.1.etl
    WbadminUI.0.etl
    etc.
    I tried removing the old backup and starting a new backup. But, even now it is failing with the same error.
    When running the backup from the PowerShell, the output is as below.
    PS C:\Users\administrator> Wbadmin start backup -backupTarget:\\localhost\E$\WindowsImageBackup\Server01 -systemState -vss
    Copy
    wbadmin 1.0 - Backup command-line tool
    (C) Copyright 2004 Microsoft Corp.
    Note: The backed up data cannot be securely protected at this destination.
    Backups stored on a remote shared folder might be accessible by other
    people on the network. You should only save your backups to a location
    where you trust the other users who have access to the location or on a
    network that has additional security precautions in place.
    Retrieving volume information...
    This will back up volume System Reserved (100.00 MB) (Selected Files),SAN(I:) (Selected Files),Local Disk(C:) (Selected
    Files) to \\localhost\E$\WindowsImageBackup\Server01.
    Do you want to start the backup operation?
    [Y] Yes [N] No y
    The backup operation to \\localhost\E$\WindowsImageBackup\Server01 is starting.
    Starting to back up the system state [12/8/2013 9:29 AM]...
    Creating a shadow copy of the volumes specified for backup...
    Creating a shadow copy of the volumes specified for backup...
    Creating a shadow copy of the volumes specified for backup...
    Summary of the backup operation:
    The backup of the system state failed [12/8/2013 9:30 AM].
    Log of files successfully backed up:
    C:\Windows\Logs\WindowsServerBackup\Backup-08-12-2013_09-29-49.log
    Log of files for which backup failed:
    C:\Windows\Logs\WindowsServerBackup\Backup_Error-08-12-2013_09-29-49.log
    There is not enough disk space to create the volume shadow copy on the storage location. Make sure that, for all volumes
     to be backup up, the minimum required disk space for shadow copy creation is available. This applies to both the backup
     storage destination and volumes included in the backup.
    Minimum requirement: For volumes less than 500 megabytes, the minimum is 50 megabytes of free space. For volumes more th
    an 500 megabytes, the minimum is 320 megabytes of free space.
    Recommended: At least 1 gigabyte of free disk space on each volume if volume size is more than 1 gigabyte.
    ERROR - A Volume Shadow Copy Service operation error has
    occurred: (0x8004231f)
    Insufficient storage available to create either the shadow copy storage file or other shadow copy data.
    If you see the free space available in each of the drives, they are in plenty.
    C:\ 7.5 GB free of 70 GB
    E:\ 250 GB free of 499 GB
    I:\ 86.7 GB free of 350 GB
    I am out of any hints on how I can proceed now. Has any one had similar issues? Can any one give any hint on this? Thanks.
    Thanks.

    Some Additional info.
    Shadow Copy Storage association
       For volume: (\\?\Volume{a9fb0474-f1bd-11e0-b235-806e6f6e6963}\)\\?\Volume{a9f
    b0474-f1bd-11e0-b235-806e6f6e6963}\
       Shadow Copy Storage volume: (\\?\Volume{a9fb0474-f1bd-11e0-b235-806e6f6e6963}
    \)\\?\Volume{a9fb0474-f1bd-11e0-b235-806e6f6e6963}\
       Used Shadow Copy Storage space: 0 B (0%)
       Allocated Shadow Copy Storage space: 0 B (0%)
       Maximum Shadow Copy Storage space: 32 MB (32%)
    Shadow Copy Storage association
       For volume: (I:)\\?\Volume{ddf6a51c-1282-11e3-b291-000c293b01d1}\
       Shadow Copy Storage volume: (I:)\\?\Volume{ddf6a51c-1282-11e3-b291-000c293b01
    d1}\
       Used Shadow Copy Storage space: 0 B (0%)
       Allocated Shadow Copy Storage space: 0 B (0%)
       Maximum Shadow Copy Storage space: 35 GB (10%)
    Shadow Copy Storage association
       For volume: (E:)\\?\Volume{0e3bf713-125d-11e3-b2dd-000c293b01bd}\
       Shadow Copy Storage volume: (E:)\\?\Volume{0e3bf713-125d-11e3-b2dd-000c293b01
    bd}\
       Used Shadow Copy Storage space: 0 B (0%)
       Allocated Shadow Copy Storage space: 0 B (0%)
       Maximum Shadow Copy Storage space: 149.999 GB (30%)
    Shadow Copy Storage association
       For volume: (C:)\\?\Volume{a9fb0475-f1bd-11e0-b235-806e6f6e6963}\
       Shadow Copy Storage volume: (C:)\\?\Volume{a9fb0475-f1bd-11e0-b235-806e6f6e69
    63}\
       Used Shadow Copy Storage space: 0 B (0%)
       Allocated Shadow Copy Storage space: 0 B (0%)
       Maximum Shadow Copy Storage space: 4.99 GB (7%)
    Hope this might also help you experts to get a little more information.

  • ICloud backups failing due to Safari bookmarks DB being locked

    iCloud backups are failing to complete on my iPhone 4 (CDMA), iOS 5.0.1.  I successfully completed a backup on November 9, but haven't been able to get a backup to complete since then.  When I manually invoke the "Back Up Now" function, it starts backing up, then says "There was a problem completing the backup.  Please try again later."
    Looking in the console logs (below), it appears the problem is that the Safari bookmarks DB is locked (corrupted?).  Indeed, I am unable to add additional bookmarks in Safari, I get the message: "Bookmarks are being synced.  Please add the bookmark once syncing has completed."
    I've tried restarting the iPhone to no avail; I've also looked at Apple's iCloud backup troubleshooting doc, and none of the cases there seemed to match this problem.
    Any suggestions ar every much appreciated!
    Here is what the iPhone console says:
    Nov 29 15:47:01 unknown backupd[7416] <Warning>: INFO: SQLite file is locked: /var/mobile/Library/Safari/Bookmarks.db (d1f062e2da26192a6625d968274bfda8d07821e4)
    Nov 29 15:47:02 unknown backupd[7416] <Warning>: WARNING: Error checkpointing copied SQLite file: disk I/O error (10) (MBErrorDomain/16): /var/mobile/Library/AddressBook/AddressBookImages.sqlitedb (cd6702cea29fe89cf280a76794405adb17f9a0ee)
    Nov 29 15:47:04 unknown backupd[7416] <Warning>: INFO: Added batch of 4 files of size 15.2 KB in 2.155 s at 0.01 MB/s (6.6%)
    Nov 29 15:47:04 unknown backupd[7416] <Warning>: INFO: Finished adding files in 7.103 s at 13.20 MB/s
    Nov 29 15:47:05 unknown backupd[7416] <Warning>: WARNING: Retrying after hard error: Files modified while backing up (MBErrorDomain/9)
    Nov 29 15:47:09 unknown backupd[7416] <Warning>: INFO: Snapshot 85 is uncommitted
    Nov 29 15:47:25 unknown atc[7384] <Warning>: ATC|__20-[ATController init]_block_invoke_0831|ATController.m:1164| Checking timeout inactive=0, timeout disabled=1
    Nov 29 15:47:33 unknown lockdownd[21] <Error>: 016b4000 copy_basebandRegionSKU: MobileGestalt failed to provide an BasebandRegionSKU
    Nov 29 15:47:33 unknown lockdownd[21] <Error>: 016b4000 special_case_get_domain: NN: checking BT MAC Address reported back 24:ab:81:ec:bf:37
    Nov 29 15:47:33 unknown kernel[0] <Debug>: lockbot[7436] Builtin profile: gputoolsd (sandbox)
    Nov 29 15:47:36 unknown lockdownd[21] <Error>: 01632000 copy_basebandRegionSKU: MobileGestalt failed to provide an BasebandRegionSKU
    Nov 29 15:47:36 unknown lockdownd[21] <Error>: 01632000 special_case_get_domain: NN: checking BT MAC Address reported back 24:ab:81:ec:bf:37
    Nov 29 15:47:37 unknown DTFetchSymbols[7448] <Notice>: Found paths:
    Nov 29 15:47:37 unknown DTFetchSymbols[7448] <Notice>: /usr/lib/dyld
    Nov 29 15:47:37 unknown DTFetchSymbols[7448] <Notice>: /System/Library/Caches/com.apple.dyld/dyld_shared_cache_armv7
    Nov 29 15:47:37 unknown DTFetchSymbols[7448] <Notice>: /Developer/usr/lib/CFDataFormatters.dylib
    Nov 29 15:47:37 unknown DTFetchSymbols[7448] <Notice>: /Developer/usr/lib/libdebugnub.dylib
    Nov 29 15:47:37 unknown DTFetchSymbols[7448] <Notice>: /Developer/usr/lib/libXcodeDebuggerSupport.dylib
    Nov 29 15:47:37 unknown DTFetchSymbols[7448] <Notice>: /Developer/Library/PrivateFrameworks/GPUTools.framework/libglInterpose.dylib
    Nov 29 15:47:37 unknown DTFetchSymbols[7448] <Notice>: /Developer/Library/PrivateFrameworks/GPUToolsCore.framework/GPUToolsCore
    Nov 29 15:47:37 unknown DTFetchSymbols[7448] <Notice>: /Developer/Library/PrivateFrameworks/DevToolsBundleInjection.framework/DevTools BundleInjection
    Nov 29 15:47:37 unknown DTFetchSymbols[7448] <Notice>: /Developer/Library/Frameworks/SenTestingKit.framework/SenTestingKit
    Nov 29 15:47:56 unknown backupd[7416] <Warning>: INFO: Modified while scanning: /var/mobile/Library/Safari/Bookmarks.db
    Nov 29 15:48:25 unknown atc[7384] <Warning>: ATC|__20-[ATController init]_block_invoke_0831|ATController.m:1164| Checking timeout inactive=0, timeout disabled=1
    Nov 29 15:48:29 unknown backupd[7416] <Warning>: INFO: Scanned in 79.680 s
    Nov 29 15:48:30 unknown backupd[7416] <Warning>: INFO: Found 0 deleted files in 0.995 s
    Nov 29 15:48:33 unknown backupd[7416] <Warning>: INFO: Updated snapshot 85 (added 6 files of size 182.2 MB)
    Nov 29 15:48:33 unknown backupd[7416] <Warning>: INFO: Created backup and snapshot in 2.651 s
    Nov 29 15:48:33 unknown backupd[7416] <Warning>: INFO: Adding 6 files of size 182.2 MB
    Nov 29 15:49:11 unknown backupd[7416] <Warning>: INFO: Added batch of 1 files of size 88.7 MB in 24.837 s at 3.57 MB/s (29.4%)
    Nov 29 15:49:25 unknown atc[7384] <Warning>: ATC|__20-[ATController init]_block_invoke_0831|ATController.m:1164| Checking timeout inactive=0, timeout disabled=1
    Nov 29 15:49:45 unknown backupd[7416] <Warning>: ERROR: Error starting transfer of items with MMCS: Error Domain=com.apple.mmcs Code=30 "The operation couldn’t be completed. (com.apple.mmcs error 30 - All items in the request have failed. Put authorization will not be requested)" UserInfo=0xf9d5bf0 {NSDescription=All items in the request have failed. Put authorization will not be requested}
    Nov 29 15:49:45 unknown backupd[7416] <Warning>: INFO: Not retrying after unrecoverable error: Error putting items into chunk store (MBErrorDomain/400). Underlying error: Error putting items into MMCS (MBErrorDomain/400). Underlying error: The operation couldn’t be completed. (com.apple.mmcs error 30 - All items in the request have failed. Put authorization will not be requested) (com.apple.mmcs/30)..
    Nov 29 15:49:51 unknown backupd[7416] <Warning>: ERROR: Backup failed: Error putting items into chunk store (MBErrorDomain/400). Underlying error: Error putting items into MMCS (MBErrorDomain/400). Underlying error: The operation couldn’t be completed. (com.apple.mmcs error 30 - All items in the request have failed. Put authorization will not be requested) (com.apple.mmcs/30)..
    Nov 29 15:49:52 unknown lockdownd[21] <Error>: libMobileGestalt copyInternationalMobileEquipmentIdentity: No IMEI in CT mobile equipment info dictionary - <CFBasicHash 0x2254b0 [0x3f5f5630]>{type = mutable dict, count = 6,
              entries =>
                        1 : <CFString 0x250530 [0x3f5f5630]>{contents = "kCTMobileEquipmentInfoCurrentSubscriberId"} = <CFString 0x224740 [0x3f5f5630]>{contents = "2062760895"}
                        2 : <CFString 0x225480 [0x3f5f5630]>{contents = "kCTMobileEquipmentInfoCurrentMobileId"} = <CFString 0x24f4d0 [0x3f5f5630]>{contents = "A100001AEF8D32"}
                        3 : <CFString 0x240100 [0x3f5f5630]>{contents = "kCTMobileEquipmentInfoMEID"} = <CFString 0x24f4d0 [0x3f5f5630]>{contents = "A100001AEF8D32"}
                        4 : <CFString 0x255a70 [0x3f5f5630]>{contents = "kCTMobileEquipmentInfoMIN"} = <CFString 0x224740 [0x3f5f5630]>{contents = "2062760895"}
                        7 : <CFString 0x258a10 [0x3f5f5630]>{contents = "kCTMobileEquipmentInfoPRLVersion"} = <CFNumber 0x250de0 [0x3f5f5630]>{value = +52341, type = kCFNumberSInt64Type}
                        8 : <CFString 0x250570 [0x3f5f5630]>{contents = "kCTMobileEquipmentInfoERIVersion"} = <CFNumber 0x240050 [0x3f5f5630]>{value = +6, type = kCFNumberSInt32Type}
    Nov 29 15:49:52 unknown lockdownd[21] <Error>: 01632000 copy_imei: MobileGestalt failed to provide an IMEI
    Nov 29 15:49:52 unknown lockdownd[21] <Error>: 01632000 copy_iccid: invalid ICCID from CT/no ICCID available
    Nov 29 15:49:53 unknown backupd[7416] <Warning>: INFO: Scheduling next backup at 11/29/11 3:50:23 PM
    Nov 29 15:50:25 unknown atc[7384] <Warning>: ATC|__20-[ATController init]_block_invoke_0831|ATController.m:1164| Checking timeout inactive=0, timeout disabled=1
    Nov 29 15:50:26 unknown backupd[7416] <Warning>: INFO: Backup starting
    Nov 29 15:50:26 unknown backupd[7416] <Warning>: INFO: DeviceID="8e00a6a6d8e93337321c17ba679894a5ac80ddb1", DeviceName="Blake Scholl's iPhone", ProductType="iPhone3,3", BuildVersion="9A405"
    Nov 29 15:50:30 unknown profiled[7458] <Notice>: (Note ) profiled: Service starting...
    Nov 29 15:50:32 unknown wifid[25] <Error>: WiFi:[344303432.585437]: Client itunesstored is background application
    Nov 29 15:50:38 unknown backupd[7416] <Warning>: INFO: Refreshed cache in 4.024 s
    Nov 29 15:50:38 unknown backupd[7416] <Warning>: INFO: Snapshot 85 is uncommitted
    Nov 29 15:51:15 unknown backupd[7416] <Warning>: INFO: Modified while scanning: /var/mobile/Library/Safari/Bookmarks.db
    Nov 29 15:51:16 unknown backupd[7416] <Warning>: INFO: Modified while scanning: /var/mobile/Library/Preferences
    Nov 29 15:51:18 unknown backupd[7416] <Warning>: INFO: Modified while scanning: /var/mobile/Library/Preferences/com.apple.itunesstored.plist
    Nov 29 15:51:18 unknown backupd[7416] <Warning>: INFO: Modified while scanning: /var/mobile/Library/Preferences
    Nov 29 15:51:25 unknown atc[7384] <Warning>: ATC|__20-[ATController init]_block_invoke_0831|ATController.m:1164| Checking timeout inactive=0, timeout disabled=1
    Nov 29 15:51:31 unknown profiled[7458] <Notice>: (Note ) profiled: Idled.
    Nov 29 15:51:31 unknown profiled[7458] <Notice>: (Note ) profiled: Service stopping.
    Nov 29 15:51:50 unknown backupd[7416] <Warning>: INFO: Scanned in 71.803 s
    Nov 29 15:51:52 unknown backupd[7416] <Warning>: INFO: Found 1 deleted files in 1.279 s
    Nov 29 15:51:55 unknown backupd[7416] <Warning>: INFO: Updated snapshot 85 (added 11 files of size 93.8 MB)
    Nov 29 15:51:55 unknown backupd[7416] <Warning>: INFO: Created backup and snapshot in 2.424 s
    Nov 29 15:51:55 unknown backupd[7416] <Warning>: INFO: Adding 11 files of size 93.8 MB
    Nov 29 15:51:55 unknown backupd[7416] <Warning>: INFO: SQLite file is locked: /var/mobile/Library/Safari/Bookmarks.db (d1f062e2da26192a6625d968274bfda8d07821e4)
    Nov 29 15:51:56 unknown backupd[7416] <Warning>: WARNING: Error checkpointing copied SQLite file: disk I/O error (10) (MBErrorDomain/16): /var/mobile/Library/AddressBook/AddressBookImages.sqlitedb (cd6702cea29fe89cf280a76794405adb17f9a0ee)
    Nov 29 15:52:00 unknown backupd[7416] <Warning>: INFO: Added batch of 9 files of size 3.8 KB in 4.011 s at 0.00 MB/s (0.0%)
    Nov 29 15:52:01 unknown backupd[7416] <Warning>: INFO: Added batch of 1 files of size 0 B in 0.492 s at 0.00 MB/s (0.0%)
    Nov 29 15:52:01 unknown backupd[7416] <Warning>: INFO: Finished adding files in 6.141 s at 15.27 MB/s
    Nov 29 15:52:03 unknown backupd[7416] <Warning>: WARNING: Retrying after hard error: Files modified while backing up (MBErrorDomain/9)
    Nov 29 15:52:09 unknown backupd[7416] <Warning>: INFO: Snapshot 85 is uncommitted
    Nov 29 15:52:25 unknown atc[7384] <Warning>: ATC|__20-[ATController init]_block_invoke_0831|ATController.m:1164| Checking timeout inactive=0, timeout disabled=1
    Nov 29 15:52:25 unknown atc[7384] <Warning>: ATC|__block_global_22|ATController.m:1182| Assertion check - link <ATLink: 0x1862d0> held: 0, idle: 0
    Nov 29 15:52:46 unknown backupd[7416] <Warning>: INFO: Modified while scanning: /var/mobile/Library/Safari/Bookmarks.db
    Nov 29 15:53:19 unknown backupd[7416] <Warning>: INFO: Scanned in 69.028 s
    Nov 29 15:53:19 unknown backupd[7416] <Warning>: INFO: Found 0 deleted files in 0.693 s
    Nov 29 15:53:24 unknown backupd[7416] <Warning>: INFO: Updated snapshot 85 (added 4 files of size 93.8 MB)
    Nov 29 15:53:24 unknown backupd[7416] <Warning>: INFO: Created backup and snapshot in 3.972 s
    Nov 29 15:53:24 unknown backupd[7416] <Warning>: INFO: Adding 4 files of size 93.8 MB
    Nov 29 15:53:25 unknown backupd[7416] <Warning>: INFO: SQLite file is locked: /var/mobile/Library/Safari/Bookmarks.db (d1f062e2da26192a6625d968274bfda8d07821e4)
    Nov 29 15:53:25 unknown atc[7384] <Warning>: ATC|__20-[ATController init]_block_invoke_0831|ATController.m:1164| Checking timeout inactive=0, timeout disabled=1
    Nov 29 15:53:25 unknown backupd[7416] <Warning>: WARNING: Error checkpointing copied SQLite file: disk I/O error (10) (MBErrorDomain/16): /var/mobile/Library/AddressBook/AddressBookImages.sqlitedb (cd6702cea29fe89cf280a76794405adb17f9a0ee)
    Nov 29 15:53:28 unknown backupd[7416] <Warning>: INFO: Added batch of 2 files of size 1.6 KB in 2.274 s at 0.00 MB/s (0.0%)
    Nov 29 15:53:28 unknown backupd[7416] <Warning>: INFO: Finished adding files in 3.440 s at 27.26 MB/s
    Nov 29 15:53:28 unknown backupd[7416] <Warning>: WARNING: Retrying after hard error: Files modified while backing up (MBErrorDomain/9)
    Nov 29 15:53:34 unknown backupd[7416] <Warning>: INFO: Snapshot 85 is uncommitted
    Nov 29 15:54:18 unknown backupd[7416] <Warning>: INFO: Modified while scanning: /var/mobile/Library/SpringBoard
    Nov 29 15:54:18 unknown backupd[7416] <Warning>: INFO: Modified while scanning: /var/mobile/Library/SpringBoard/applicationstate.plist
    Nov 29 15:54:20 unknown backupd[7416] <Warning>: INFO: Modified while scanning: /var/mobile/Library/SpringBoard
    Nov 29 15:54:20 unknown backupd[7416] <Warning>: INFO: Modified while scanning: /var/mobile/Library/Safari/Bookmarks.db
    Nov 29 15:54:23 unknown backupd[7416] <Warning>: INFO: Modified while scanning: /var/mobile/Library/Mail
    Nov 29 15:54:25 unknown atc[7384] <Warning>: ATC|__20-[ATController init]_block_invoke_0831|ATController.m:1164| Checking timeout inactive=0, timeout disabled=1
    Nov 29 15:54:53 unknown backupd[7416] <Warning>: INFO: Scanned in 78.753 s
    Nov 29 15:54:53 unknown backupd[7416] <Warning>: INFO: Found 0 deleted files in 0.857 s
    Nov 29 15:54:56 unknown backupd[7416] <Warning>: INFO: Updated snapshot 85 (added 9 files of size 182.2 MB)
    Nov 29 15:54:56 unknown backupd[7416] <Warning>: INFO: Created backup and snapshot in 2.897 s
    Nov 29 15:54:56 unknown backupd[7416] <Warning>: INFO: Adding 9 files of size 182.2 MB
    Nov 29 15:55:00 unknown backupd[7416] <Warning>: INFO: Added batch of 2 files of size 31.3 KB in 3.679 s at 0.01 MB/s (0.0%)
    Nov 29 15:55:25 unknown atc[7384] <Warning>: ATC|__20-[ATController init]_block_invoke_0831|ATController.m:1164| Checking timeout inactive=0, timeout disabled=1
    Nov 29 15:55:33 unknown backupd[7416] <Warning>: INFO: Added batch of 1 files of size 88.7 MB in 22.235 s at 3.99 MB/s (24.3%)
    Nov 29 15:56:08 unknown backupd[7416] <Warning>: ERROR: Error starting transfer of items with MMCS: Error Domain=com.apple.mmcs Code=30 "The operation couldn’t be completed. (com.apple.mmcs error 30 - All items in the request have failed. Put authorization will not be requested)" UserInfo=0xf950f60 {NSDescription=All items in the request have failed. Put authorization will not be requested}
    Nov 29 15:56:08 unknown backupd[7416] <Warning>: INFO: Not retrying after unrecoverable error: Error putting items into chunk store (MBErrorDomain/400). Underlying error: Error putting items into MMCS (MBErrorDomain/400). Underlying error: The operation couldn’t be completed. (com.apple.mmcs error 30 - All items in the request have failed. Put authorization will not be requested) (com.apple.mmcs/30)..
    Nov 29 15:56:13 unknown lockdownd[21] <Error>: libMobileGestalt copyInternationalMobileEquipmentIdentity: No IMEI in CT mobile equipment info dictionary - <CFBasicHash 0x255a30 [0x3f5f5630]>{type = mutable dict, count = 6,
              entries =>
                        1 : <CFString 0x250530 [0x3f5f5630]>{contents = "kCTMobileEquipmentInfoCurrentSubscriberId"} = <CFString 0x2439f0 [0x3f5f5630]>{contents = "2062760895"}
                        2 : <CFString 0x227350 [0x3f5f5630]>{contents = "kCTMobileEquipmentInfoCurrentMobileId"} = <CFString 0x2506d0 [0x3f5f5630]>{contents = "A100001AEF8D32"}
                        3 : <CFString 0x258a10 [0x3f5f5630]>{contents = "kCTMobileEquipmentInfoMEID"} = <CFString 0x2506d0 [0x3f5f5630]>{contents = "A100001AEF8D32"}
                        4 : <CFString 0x24ca60 [0x3f5f5630]>{contents = "kCTMobileEquipmentInfoMIN"} = <CFString 0x2439f0 [0x3f5f5630]>{contents = "2062760895"}
                        7 : <CFString 0x225640 [0x3f5f5630]>{contents = "kCTMobileEquipmentInfoPRLVersion"} = <CFNumber 0x255930 [0x3f5f5630]>{value = +52341, type = kCFNumberSInt64Type}
                        8 : <CFString 0x250570 [0x3f5f5630]>{contents = "kCTMobileEquipmentInfoERIVersion"} = <CFNumber 0x240050 [0x3f5f5630]>{value = +6, type = kCFNumberSInt32Type}
    Nov 29 15:56:13 unknown lockdownd[21] <Error>: 01632000 copy_imei: MobileGestalt failed to provide an IMEI
    Nov 29 15:56:13 unknown lockdownd[21] <Error>: 01632000 copy_iccid: invalid ICCID from CT/no ICCID available
    Nov 29 15:56:13 unknown backupd[7416] <Warning>: ERROR: Backup failed: Error putting items into chunk store (MBErrorDomain/400). Underlying error: Error putting items into MMCS (MBErrorDomain/400). Underlying error: The operation couldn’t be completed. (com.apple.mmcs error 30 - All items in the request have failed. Put authorization will not be requested) (com.apple.mmcs/30)..
    Nov 29 15:56:15 unknown backupd[7416] <Warning>: INFO: Scheduling next backup at 11/29/11 7:33:26 PM

    Had same problem, the solution lies with having your original apple ID associated email address "verified".
    I may not have all the steps down correctly, but open your apple ID account manager and go to the your listing for email and "verify" the email address.  This association then seems to allow the use of your email address when you are trying to set up this new apple ID that they are requiring for iCloud.
    Be aware that this new apple ID has a far reach and apparently cannot be undone, that is you can't change the name, characters, numbers or whatever you have for an email address that becomes your apple ID---even if you can no longer use the email address to receive email.
    Lots of luck.
    I have been trying to get the iCloud features to work for over a week now, including a visit to a genius bar, and still not fully functioning.

  • System Image Backup Failed During Backup

    I have a 2 year old HP pavilion g series notebook.  I was doing a system image backup onto dvd+r disks. It was nearly finished when on disk #99 I got this message "The Backup Failed. The system cannot find the path specified (0x80070003)  
    My computer is out of warranty and I'm out $60 in disks if they can't be used.  I need to know it there is a way to salvage what I saved and restart Image backup from where it left off?  
    Product: A6Z59UA #ABA
    Model: g61d60us
    This question was solved.
    View Solution.

    Hi CherylLyme,
    Welcome to the HP Forums!
    I would like to take a moment and thank you for using the forum, it is a great place to find answers.
    For you to have the best experience in the HP forum, I would like to direct your attention to the HP Forums Guide First Time Here? Learn How to Post and More.
    I understand that you were doing an image backup and when it was nearly finished you received  the error (0x80070003).  Here is a link to a Microsoft answer to assist you. Windows backup error 0x80070003 ( Answered by Vinod N)
    I am unsure if you would be able to start again and pick up on disk 99, as once you have repaired it, it will have changed from when you first ran the backup.  The disk you used were not read, writeable, so you would not be able to reuse them.  You may find that an external drive would be a more economical way to do your backups. The data would be in one place and easier to store.  If you decide to use a USB stick it must not be more then 32GB and will not say Windows 8 on it.
    You can most likely purchase an External drive for about the cost of replacing the disks.  Here is a link to HP Shopping External storage , but you can purchase one at many places, computer shops, Staples,Walmart, and Office Depot are just a few.  I hope this helps.
    Sparkles1
    I work on behalf of HP
    Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
    Click the “Kudos, Thumbs Up" on the bottom right to say “Thanks” for helping!

  • System Image Backup failing when trying to write to a Drobo 5N NAS

    I'm trying to make a full system image through file history, and I get part way through the process until I get the following error:
    The backup failed.
    There was a failure in preparing the backup image of one of the volumes in the backup set. (0x807800C5)
    Additional information:
    The process cannot access the file because another process has locked a portion of the file. (0x80070021)
    I've found one other thread where this was an issue and the user said that he had no issues doing it to a USB drive, so I'm assuming it's related to using a network one. I can run file history/recovery (whatever it's called) to the same network attached
    server in the same parent folder so I know it's not a permission issue. Any help would be greatly appreciated.

    Hi,
    In order to know whethr this issue is related with the speicfic NAS, I suggest you try to backup the image to another external drive and check if the error persists.
    Actually, according to the error message, it seems more related with the files which need to be backed up, it is locked\unaccessable. I recommend you temporarily turn off any anti-virus program protection. Stop other running processes including background
    processes, then try to backup again, test the result.
    Regards
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • Windows 2008 R2 backup fails with event 521 error code 2155348001

    Windows Server 2008 R2 SP1.  Hyper-V role installed. 
    OS on drive C.  All VMs stored on Drive D.
    I am attempting to run a Bare Metal backup of the host system to a network share. 
    Drive D is not included in the backup job.  I am getting the following error:
    Log Name:      Application
    Source:        Microsoft-Windows-Backup
    Date:          1/10/2014 11:28:52 PM
    Event ID:      521
    Task Category: None
    Level:         Error
    Keywords:     
    User:          SYSTEM
    Computer:      SHAQTUS.scdl.local
    Description:
    The backup operation that started at '‎2014‎-‎01‎-‎11T04:08:50.683000000Z' has failed because the Volume Shadow Copy Service operation to create a shadow copy of the volumes being backed up failed with following error code '2155348001'. Please review the event
    details for a solution, and then rerun the backup operation once the issue is resolved.
    Reviewing event details, as suggested, does not offer any solution.
    I have tried the suggested solutions in other similar threads of increasing the timeout value with the registry entry. 
    This does not work.
    I have not tried reregistering the VSS writers manually, as the only links I have found are for server 2003/2008 (not R2) and explicitly state that they won’t work on higher versions of the OS, since they now utilize manifests and the manual procedure could
    cause problems for those servers. Haven't found similar procedures for 2008 R2.
    I have been able to narrow this down a bit.
    A Windows 2008 R2 SP1 server with Hyper-V installed – backup to a network share is successful;
    Install the DPM 2012 agent – same backup fails with the 2155348001 error.
    We use DPM 2012 to backup VMs, but DPM cannot perform a bare metal backup/restore of server and the 2012 version no longer has the DPMSRT feature. 
    I prefer to run Bare Metal Backup to a file server share.
    Stuck on this one.
    Rick

    Hi, 
    The issue is related to DPM, I would suggest you ask for help from DPM forums:
    http://social.technet.microsoft.com/Forums/en-US/home?forum=dataprotectionmanager
    Regards, 
    Mandy
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

Maybe you are looking for