Deleting old backup files

I backup to an external HD weekly using Backup (the little umbrella.) This 250 GB HD is almost filled. Can I delete older backups to make more room?

I assume it would depend on how you use backups. If you need to have old versions of your files available to retrieve, then you might want to burn some older backups to dvd before deleting them. I just need one daily and one weekly backup , so I overwrite the backup each time. In case of hardware failure or corruption, I can always retrieve a file from either one day or one week (at most) prior. Files which need to be permanently archived go onto DVD. In that scenario there's no need for multiple backups of the same files at all.

Similar Messages

  • Ola Hallengren maintenance solution TSQL script not deleting old backup files from my local SQL server

    I have looked on Ola's site (https://ola.hallengren.com/frequently-asked-questions.html) and I did see this:
    DatabaseBackup is not deleting old backup files. What could the problem be?
    Verify that the SQL Server and SQL Server Agent service accounts have full control of the backup directory.
    If that directory is a network share, verify that the SQL Server and SQL Server Agent service accounts have full control of the network share.
    If you are using a proxy account, verify that the account is a member of the sysadmin server role and that it has full control of the backup directory and network share.
    Verify that the file is not locked in the file system; for example, a backup or antivirus software could be locking the file.
    DatabaseBackup has been designed not to delete transaction log backups that are newer than the most recent full or differential backup. This could explain why transaction log backups are not being deleted.
    I followed these instructions and then I right clicked the "sp_delete_backuphistory" job under "SQL Server Agent > Jobs" folder and clicked the "Start job at step ..." option. The job successfully ran, but my .bak backup
    files were still on located on my separate drive partition I use specifically for these backups. 
    The SQL Server and the SQL Server Agent are both using the same AD account. 
    Would any of you SQL gurus out there know how to resolve this?
    Thank you 

    The sp_delete_backuphistory job only deletes the historical info from the backup & restore tables in the msdb database. It does not do anything to the files on disk.
    https://msdn.microsoft.com/en-us/library/ms188328.aspx
    The code to actually purge the backup files from disk is inside the DatabaseBackup stored procedure. It is controlled by using the @CleanupTime parameter for that stored proc. Verify the value for that parameter is low enough to delete your files on disk. The
    value is in hours, and I believe the default is 48 hours. The SQL agent job name usually starts with "DatabaseBackup...".

  • HT5925 deleting old backup files from icloud ?

    How can we view and delete backup files on icloud?

    You can do that e.g. on your iOS device in "Settings > iCloud > Storage & Backup > Manage Storage"
    or on your Mac: System Preferences > iCloud > Manage... .

  • Can you remove Old Backup files from Time Machine sooner?

    So I'm aware that the default settings state that Time Machine will start to delete old backup files from your saved destination once that destination starts to approach full storage capacity. But what if you are not looking to fill up most of your storage capacity with Time Machine backups? Is there a way where you can cut the delete threshold in half and have Time Machine delete old backup files sooner rather than later?

    See Pondini's TM FAQs, for starters.

  • I backup to an external hdd with Time Machine, when it ran out of space it did not delete old backups, now my internal hdd says its full when before it had heaps of space. I have searched for extra files but cant find any. Can anyone help, please.

    I backup to an external hdd with Time Machine, when it ran out of space it did not delete old backups, now my internal hdd says its full when before it had heaps of space. I have searched for extra files but cant find any. Can anyone help, please.

    First, empty the Trash if you haven't already done so. Then reboot. That will temporarily free up some space.
    To locate large files, you can use Spotlight as described here. That method may not find large folders that contain a lot of small files.
    You can also use a tool such as OmniDiskSweeper (ODS) to explore your volume and find out what's taking up the space. You can delete files with it, but don't do that unless you're sure that you know what you're deleting and that all data is safely backed up. That means you have multiple backups, not just one.
    Proceed further only if the problem hasn't been solved.
    ODS can't see the whole filesystem when you run it just by double-clicking; it only sees files that you have permission to read. To see everything, you have to run it as root.
    Back up all data now.
    Install ODS in the Applications folder as usual.
    Triple-click the line of text below to select it, then copy the selected text to the Clipboard (command-C):sudo /Applications/OmniDiskSweeper.app/Contents/MacOS/OmniDiskSweeper
    Launch the Terminal application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
    Paste into the Terminal window (command-V). You'll be prompted for your login password, which won't be displayed when you type it. You may get a one-time warning not to screw up. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.
    I don't recommend that you make a habit of doing this. Don't delete anything while running ODS as root. If something needs to be deleted, make sure you know what it is and how it got there, and then delete it by other, safer, means.
    When you're done with ODS, quit it and also quit Terminal.

  • Are old backup files saved or deleted in iTunes

    I had to restore my Iphone back to factory. The backup file I created was too big to restore and the Verizon tech (who I foolishly let take over my computer) backed up the empty phone over the old backup file. I found a program to restore the original backup data, but it's been overwritten by the recent backup. Does iTunes delete the the old backup files or store them in a different folder?

    iTunes only keeps one normal backup, per iOS device. As you've found out, its an incremental backup in that data that has changed or deleted is added or removed from the backup. Unless you backup your computer, your data is gone.

  • How to remove old backup files from time machine? Lion OSx

    Hi everyone,
    I am just wondering how to efficiently and safely remove the old backup files from time machine? I tried once with command, but it damaged my extra-disk... Does Lion OSx have fixed that?
    Many thanks
    Hong

    Blue-
    Time Machine will automatically delete back-ups as the need for space arises. If you want to delete a certain file (application, document, whatever) and have it gone for good you can do that as well.
    The best place on the web for information about Time Machine is...
    http://pondini.org/TM/Home.html
    ...it covers everything!
    Clinton

  • When Time Machine deletes old backups......

    My Time Machine disk is about to be full. I realize that when the disk becomes full, Time Machine will delete old backups.
    I am not clear, however, exactly what this means.
    Is what are deleted:
    1. older disk pseudo-images?
    2. files which no longer are on the computer?
    Or is Time Machine actually deleting files which are still on the computer (but were in the old now-being-deleted backup)?
    I suspect it is #1 and #2. So if you had a computer where files are added over time (without meaningful deletions), this strategy will not help a lot---you just need to get a new disk.
    Is another option to just make a complete new full Time Machine backup (losing all the intermediate backups)? How is this done?

    Jeffrey Folinus1 wrote:
    Is what are deleted:
    1. older disk pseudo-images?
    I have no idea what that is.
    2. files which no longer are on the computer?
    Yes. More to the point, files that were changed or deleted long ago.
    Or is Time Machine actually deleting files which are still on the computer (but were in the old now-being-deleted backup)?
    No.
    When Time Machine does it's first, Full backup, it of course copies every file and folder on your system. It also makes a folder in your backups, named with the date and time of the backup. This folder appears to contain all those copied items.
    But it doesn't. It contains "hard links" to the backup copies. Think of these as extra-fancy aliases.
    Thereafter, TM does "incremental" backups. It copies only the files and folders that were added or changed, and makes another dated folder for that backup. In that folder are links to the new items, plus links to the items that didn't change: so they're cleverly named "multi-links." This is how TM appears to have many full, complete backups of your system when it obviously doesn't.
    When TM deletes a backup, all that's really deleted are the folder and the links.
    Consider what happens when you do a normal (not secure) deletion of a normal file: OSX basically "forgets" where it was, so the space can be re-used. TM is a little fancier: as long as there's even one link to a file, it isn't forgotten, so it's available to be recovered from any backup that has a link to it, and the space isn't re-used. When the last link is deleted, the copied file is forgotten.
    Thus, when you delete a backup, the only actual backup copies that are deleted are the ones that have links in no other backup. So, for example, once you've done a Full backup and a single Incremental, you (or TM) can delete the Full without losing it's copy of anything current.
    Another way to look at it is, *each backup is, in effect, a full, complete copy of your entire system the way it was at the time of that backup.*
    So much for "fancy." The "extra" fancy part is, TM doesn't necessarily make another link for every single file and folder that didn't change. Instead, if a folder wasn't changed, and nothing in it was changed, TM makes only a single link, to the folder. When you consider that your System folder, for example, contains many tens of thousands of sub-folders and files that rarely change, you see how efficient this is.
    For more details: http://www.appleinsider.com/articles/07/10/12/roadto_mac_os_x_leopard_timemachine.html
    and: http://arstechnica.com/apple/reviews/2007/10/mac-os-x-10-5.ars/14

  • Time Machine delete old backups

    My wife has a MacBook Pro and uses Time Machine on a 500 GB external drive. She is using about 160 GB on her MacBook Pro, but the Time Machine drive is now full and is not backing up current files. The Time Machine backups go back to 2010 and two or three versions of the operating system. I would like to delete old backups from Time Machine, as I understand that only files no longer needed in other backups will be deleted. Is there any reason this approach should be avoided? Are there instructions on the best way to do this? Thanks.

    tomarm wrote:as I understand that only files no longer needed in other backups will be deleted. Is there any reason this approach should be avoided? Are there instructions on the best way to do this? Thanks.
    yes, your wife ..
    A: needs a MINIMUM of a second HD to archive data on
    B: Yes, time machine "throws data out the window" when full
    C: HD clones are more important.
    https://discussions.apple.com/docs/DOC-6031
    Methodology to protect your data. Backups vs. Archives. Long-term data protection
    Time Machine / Time Capsule
    Drawbacks:
    1. Time Machine is not bootable, if your internal drive fails, you cannot access files or boot from TM directly from the dead computer.
    2. Time machine is controlled by complex software, and while you can delve into the TM backup database for specific file(s) extraction, this is not ideal or desirable.
    3. Time machine can and does have the potential for many error codes in which data corruption can occur and your important backup files may not be saved correctly, at all, or even damaged. This extra link of failure in placing software between your data and its recovery is a point of risk and failure. A HD clone is not subject to these errors.
    4. Time machine mirrors your internal HD, in which cases of data corruption, this corruption can immediately spread to the backup as the two are linked. TM is perpetually connected (or often) to your computer, and corruption spread to corruption, without isolation, which TM lacks (usually), migrating errors or corruption is either automatic or extremely easy to unwittingly do.
    5. Time Machine does not keep endless copies of changed or deleted data, and you are often not notified when it deletes them; likewise you may accidently delete files off your computer and this accident is mirrored on TM.
    6. Restoring from TM is quite time intensive.
    7. TM is a backup and not a data archive, and therefore by definition a low-level security of vital/important data.
    8. TM working premise is a “black box” backup of OS, APPS, settings, and vital data that nearly 100% of users never verify until an emergency hits or their computers internal SSD or HD that is corrupt or dead and this is an extremely bad working premise on vital data.
    9. Given that data created and stored is growing exponentially, the fact that TM operates as a “store-it-all” backup nexus makes TM inherently incapable to easily backup massive amounts of data, nor is doing so a good idea.
    10. TM working premise is a backup of a users system and active working data, and NOT massive amounts of static data, yet most users never take this into consideration, making TM a high-risk locus of data “bloat”.
    11. In the case of Time Capsule, wifi data storage is a less than ideal premise given possible wireless data corruption.
    12. TM like all HD-based data is subject to ferromagnetic and mechanical failure.
    13. *Level-1 security of your vital data.
    Advantages:
    1. TM is very easy to use either in automatic mode or in 1-click backups.
    2. TM is a perfect novice level simplex backup single-layer security save against internal HD failure or corruption.
    3. TM can easily provide a seamless no-gap policy of active data that is often not easily capable in HD clones or HD archives (only if the user is lazy is making data saves).
    HD clones (see below for full advantages / drawbacks)
    Drawbacks:
    1. HD clones can be incrementally updated to hourly or daily, however this is time consuming and HD clones are, often, a week or more old, in which case data between today and the most fresh HD clone can and would be lost (however this gap is filled by use of HD archives listed above or by a TM backup).
    2. Like all HD-based data is subject to ferromagnetic and mechanical failure.
    Advantages:
    1. HD clones are the best, quickest way to get back to 100% full operation in mere seconds.
    2. Once a HD clone is created, the creation software (Carbon Copy Cloner or SuperDuper) is no longer needed whatsoever, and unlike TM, which requires complex software for its operational transference of data, a HD clone is its own bootable entity.
    3. HD clones are unconnected and isolated from recent corruption.
    4. HD clones allow a “portable copy” of your computer that you can likewise connect to another same Mac and have all your APPS and data at hand, which is extremely useful.
    5. Rather than, as many users do, thinking of a HD clone as a “complimentary backup” to the use of TM, a HD clone is superior to TM both in ease of returning to 100% quickly, and its autonomous nature; while each has its place, TM can and does fill the gap in, say, a 2 week old clone. As an analogy, the HD clone itself is the brick wall of protection, whereas TM can be thought of as the mortar, which will fill any cracks in data on a week, 2-week, or 1-month old HD clone.
    6. Best-idealized 2nd platform redundancy for data protection, and 1st level for system restore of your computers internal HD. (Time machine being 2nd level for system restore of the computer’s internal HD).
    7. *Level-2 security of your vital data.
    HD cloning software options:
    1. SuperDuper HD cloning software APP (free)
    2. Carbon Copy Cloner APP (will copy the recovery partition as well)
    3. Disk utility HD bootable clone.

  • Time Machine Deletes Old Backups without warning!!

    I have just lost loads of pictures and emails when my Timemachine deleted old backups. I was so happy to have an easy way to keep my iPhoto cleaned up while keeping all the photos for the future. I would load my all the photos from my camera, backup with TimeMachine and delete the "bad" unwanted photos, confident in the knowledge that these pictures are still there on my external. I looked forward to some future date when someone would write an easy piece of software to consolidate old iPhoto libraries and even go through TimeMachine and consolidate those photos too. But until that fantasy event, my pictures, even though not wanted were still there.
    Not any more!!
    I replaced my hard drive and reloaded my laptop from Timemachine and I think that was the event that sparked the dump.
    There should be a special check box to make sure that NO backups are automatically deleted, EVER. They should be a way to make them Sacred!!
    There should be a way to create a separate backup just for iPhoto because right now, there are no good ways to easily break apart or merge iPhoto libraries. At least what I was doing worked, (well.... until it didn't).
    Any ideas??

    nerowolfe wrote:
    True, TM is not a classic archival system, but until the drive is full, the difference is moot.
    No, the difference isn't moot.
    I still have on my TM HD every file I ever had because it's only 1/2 full.
    No, you don't. Read on...
    Time machine has three levels of backups:
    1) hourly - deleted after 24 hours
    2) daily - deleted after a week
    3) weekly - deleted only when the disk is full - these are the only deletions you will be warned about
    Time machine is always deleting files. Every time it backs up, it deletes files.
    But the OP's real question is why he was never warned about the old backups being deleted, as TM says it will do, archival stuff notwithstanding. Apparently TM simply ignores the user's request to be warned.
    No, it doesn't.
    That being said, as I asked in a post not too long ago, "how many have had a warning from TM that old backups are being deleted?" as one would expect when the TM preference box, "Warn when old backups are deleted" is checked.
    It appears to me to be a bug.
    I ask again if anyone has gotten this warning.
    Nobody answered my previous post with a yes.
    Yes.
    Because Time Machine continually cleans up behind itself, it tries very hard to ever delete the weekly backups. The only time I've gotten the deletion warning was when my disk was full. I think I just avoided the problem by removing my old Parallels images from Time Machine and got back an extra 70 gig or so - good for another six months.
    This is not a bug. This is how Time Machine works. It is unfortunate that the original poster did not fully understand this. The fact is that Time Machine backs everything up. If you create 100 files, it backs up the folder with 100 new files. If you delete 100 files, it backs up the folder with 100 less files. Then, the next day, it deletes old backups. The only one it keeps is the last one, with 100 less files.
    It is correct to say that Time Machine is not an archival system. It is a backup system. If you want to save your files forever, you need to copy them to a location that isn't under the control of any sort of automatic software.

  • Time Machine incorrectly deleting old backups

    Hi
    I have a Macbook Air with a 128Gb SSD and I am using Time Machine to back up to an external 500Gb USB2.0 drive connected to my Airport Extreme.
    The drive is formatted as Mac OS extended Journaled and is dedicated to Time Machine backups only. The problem is that Time Machine reports that the disk has run out of space and has deleted old backups. This can't be true as the Sparsebundle file is only about 70Gb and the drive has over 400Gb of capacity.
    I have tried reformatting the disk and starting over but the problem keeps returning. When I enter time machine it has deleted all the old back ups and I can only go back in time a few days.
    Any help appreciated!

    Thanks for the reponse.
    I checked and there are no other sparsebundles on the drive and there have been no changes made to the hardware.
    Time machine seems to be working correctly as it successfully makes and completes teh back ups at regular intervals throughout the day. The message that there is no space available comes around every couple of weeks, which I'm guessing is based on the fact it keeps deleting all the recent backups except the last one and then the cycle repeats.
    My own 'limited' opinion is that TM is having difficulty resizing the sparsebundle in some way and therefore can only maintain the backup within the initial size of the first backup. (e.g. the Macbook AIR SSD reports approx 113Gb of space and I am currently using 82.07Gb. The sparsebundle is currently sized at 75.66Gb on Disk (81.16Gb)
    I checked the permissions of the sparse file and they are set to R&W for everyone so there shouldn't be an access problem.
    I have only recently moved to the Mac environment and the Macbook air is my first apple computer so I am not very familiar with the environment, but this is an extremely annoying problem and renders TM vitually useless.

  • Time capsule and deleting old backups

    Hi after performing a recent backup to an external drive I don't have much space left on the disk. It says that time capsule will delete old backups. Does this mean that any movies backed up in these early back ups will be deleted as I no longer have them on my MacBook due to the amount of space they take up?

    Time Machine is not an archive, it is a rolling backup.
    If you want to keep files permanently, you must not store them only in Time Machine. If you don't have space for the movies on your main drive, buy a drive to use as an archive, put those movies on it, and make sure that disk is backed up too, since if data exists in only one place it is vulnerable.
    My family digital archive doesn't fit on my internal drive so it is on an external drive. I also maintain two exact backup copies of that external drive. One is in the fire safe at home, the other is in a safe deposit box, and those two backups are rotated periodically. If the original and the backup are lost due to fire, burglary, etc., the off-site backup means there is still a safe copy somewhere. Because I can't afford to lose those photos, movies, and financial records. Online backup is another option for making sure you won't ever lose data you need to keep.

  • Since Mavericks upgrade, Time Capsule stuck deleting old backups ... for days

    I have a previous generation 2TB Time Capsule shared by three of us, each with separate accounts.
    I know there's not much space left on the Time Capsule and that it's therefore expected that Time Machine would make room by deleting old backups. But my account seems stuck forever on these deletions (for over 72 hours now), while the other two accounts on the Time Capsule are working just fine.
    I've been through Pondini's recommendations for (a) patience and (b) finally resetting Time Machine, but on it goes.
    Here is the last couple of hours of the log (filtered for this problem).  The entire log for the last 72 hours is too long to post -- but the pattern is the same, with the constant deletions barely making a dent, and sometimes in fact the space available decreases.
    I'd cheerfully give up on the oldest backups, but meanwhile it's been 8 days since TC has been able to complete a backup.  (I have been cloning the drive daily with SuperDuper just to make sure I have a fallback until this is figured out.)
    Hoping one of you can recommend a course of action.
    Thanks in advance for any help...
    10/28/13 8:06:51.276 PM com.apple.backupd[758]: Found 1022200 files (58.34 GB) needing backup
    10/28/13 8:07:01.173 PM com.apple.backupd[758]: 75.13 GB required (including padding), 16.43 GB available
    10/28/13 8:07:05.162 PM com.apple.backupd[758]: Ejected Time Machine disk image: /Volumes/edbern/EB’s MacBook Air.sparsebundle
    10/28/13 8:07:05.162 PM com.apple.backupd[758]: Compacting backup disk image to recover free space
    10/28/13 8:25:44.384 PM com.apple.backupd[758]: Completed backup disk image compaction
    10/28/13 8:25:44.388 PM com.apple.backupd[758]: Starting manual backup
    10/28/13 8:25:44.915 PM com.apple.backupd[758]: Network destination already mounted at: /Volumes/edbern
    10/28/13 8:26:04.847 PM com.apple.backupd[758]: Disk image /Volumes/edbern/EB’s MacBook Air.sparsebundle mounted at: /Volumes/Time Machine Backups 1
    10/28/13 8:26:05.230 PM com.apple.backupd[758]: Backing up to /dev/disk3s2: /Volumes/Time Machine Backups 1/Backups.backupdb
    10/28/13 8:26:31.228 PM com.apple.backupd[758]: Event store UUIDs don't match for volume: Macintosh HD
    10/28/13 8:26:31.546 PM com.apple.backupd[758]: Waiting for index to be ready (100)
    10/28/13 8:27:25.289 PM com.apple.backupd-helper[112]: Not starting scheduled Time Machine backup: Backup already running
    10/28/13 8:27:31.784 PM com.apple.backupd[758]: Waiting for index to be ready (100)
    10/28/13 8:27:56.892 PM com.apple.backupd[758]: Deep event scan at path:/ reason:must scan subdirs|new event db|
    10/28/13 8:35:43.224 PM com.apple.backupd[758]: Finished scan
    10/28/13 8:35:43.241 PM com.apple.backupd[758]: Not using file event preflight for Macintosh HD
    10/28/13 9:05:03.078 PM com.apple.backupd[758]: Found 1022200 files (58.34 GB) needing backup
    10/28/13 9:05:16.881 PM com.apple.backupd[758]: 75.13 GB required (including padding), 31.85 GB available
    10/28/13 9:05:17.689 PM com.apple.backupd[758]: Deleted backup /Volumes/Time Machine Backups 1/Backups.backupdb/EB’s MacBook Air/2013-10-28-202628.inProgress/03624AE5-22CE-463C-9265-CE6A8826C535 containing 4 KB; 31.85 GB now available, 75.13 GB required
    10/28/13 9:05:17.700 PM com.apple.backupd[758]: Deleted backup /Volumes/Time Machine Backups 1/Backups.backupdb/EB’s MacBook Air/2013-10-28-202628.inProgress/7503F996-8E27-4558-9308-15FC60270865 containing 4 KB; 31.85 GB now available, 75.13 GB required
    10/28/13 9:23:23.471 PM com.apple.backupd[758]: Deleted backup /Volumes/Time Machine Backups 1/Backups.backupdb/EB’s MacBook Air/2013-10-28-202628.inProgress/C424E6F6-EFBE-4154-A543-375E805E68C8 containing 8.3 MB; 31.86 GB now available, 75.13 GB required
    10/28/13 9:28:36.239 PM com.apple.backupd-helper[112]: Not starting scheduled Time Machine backup: Backup already running
    10/28/13 9:55:03.037 PM com.apple.backupd[758]: Error: Error Domain=NSOSStatusErrorDomain Code=-36 "The operation couldn’t be completed. (OSStatus error -36.)" (ioErr: I/O error (bummers)) deleting backup: /Volumes/Time Machine Backups 1/Backups.backupdb/EB’s MacBook Air/2013-10-28-202628.inProgress/C434BAEA-946E-4531-BA61-74DD5A34EFF2
    10/28/13 9:55:03.037 PM com.apple.backupd[758]: Deleted 3 backups containing 8.3 MB total; 31.86 GB now available, 75.13 GB required
    10/28/13 9:55:03.321 PM com.apple.backupd[758]: Error writing to backup log.  NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Not a directory
    10/28/13 9:55:03.579 PM com.apple.backupd[758]: Error writing to backup log.  NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Not a directory
    10/28/13 9:55:03.580 PM com.apple.backupd[758]: Error writing to backup log.  NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Not a directory
    10/28/13 9:55:03.582 PM com.apple.backupd[758]: Error writing to backup log.  NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Not a directory
    10/28/13 9:55:03.702 PM com.apple.backupd[758]: Backup canceled.
    10/28/13 9:55:11.830 PM com.apple.backupd[758]: [SnapshotUtilities mountPointForVolumeRef] FSGetVolumeInfo returned: -35
    10/28/13 9:55:11.831 PM com.apple.backupd[758]: Failed to eject volume (null) (FSVolumeRefNum: -110; status: -35; dissenting pid: 0)
    10/28/13 9:55:11.832 PM com.apple.backupd[758]: Failed to eject Time Machine disk image: /Volumes/edbern/EB’s MacBook Air.sparsebundle

    Alas, it spent the night fruitlessly.   I think I need to find a way to kill the existing backup or dismount the disk first.  Sorry I'm a bit thick about all this.
    10/29/13 12:39:06.822 AM com.apple.backupd[1628]: Starting automatic backup
    10/29/13 12:39:07.028 AM com.apple.backupd[1628]: Attempting to mount network destination URL: afp://edbern;AUTH=SRP@TC._afpovertcp._tcp.local/edbern
    10/29/13 12:39:07.995 AM com.apple.backupd[1628]: Mounted network destination at mount point: /Volumes/edbern-1 using URL: afp://edbern;AUTH=SRP@TC._afpovertcp._tcp.local/edbern
    10/29/13 12:39:11.397 AM com.apple.backupd[1628]: Disk image already attached: /Volumes/edbern-1/EB’s MacBook Air.sparsebundle, DIHLDiskImageAttach returned: 35
    10/29/13 12:39:12.969 AM com.apple.backupd[1628]: Failed to mount disk image: Error Domain=com.apple.backupd.ErrorDomain Code=31 "The operation couldn’t be completed. (com.apple.backupd.ErrorDomain error 31.)" UserInfo=0x7ffdc243f1c0 {MessageParameters=(
        "/Volumes/edbern-1/EB\U2019s MacBook Air.sparsebundle"
    10/29/13 12:39:13.059 AM com.apple.backupd[1628]: Ejected Time Machine network volume.
    10/29/13 12:39:13.060 AM com.apple.backupd[1628]: Waiting 60 seconds and trying again.
    10/29/13 12:40:24.403 AM com.apple.backupd[1628]: Attempting to mount network destination URL: afp://edbern;AUTH=SRP@TC._afpovertcp._tcp.local/edbern
    10/29/13 12:40:24.792 AM com.apple.backupd[1628]: Mounted network destination at mount point: /Volumes/edbern-1 using URL: afp://edbern;AUTH=SRP@TC._afpovertcp._tcp.local/edbern
    10/29/13 12:40:27.642 AM com.apple.backupd[1628]: Disk image already attached: /Volumes/edbern-1/EB’s MacBook Air.sparsebundle, DIHLDiskImageAttach returned: 35
    10/29/13 12:40:29.209 AM com.apple.backupd[1628]: Failed to mount disk image: Error Domain=com.apple.backupd.ErrorDomain Code=31 "The operation couldn’t be completed. (com.apple.backupd.ErrorDomain error 31.)" UserInfo=0x7ffdc27275c0 {MessageParameters=(
        "/Volumes/edbern-1/EB\U2019s MacBook Air.sparsebundle"
    10/29/13 12:40:29.324 AM com.apple.backupd[1628]: Ejected Time Machine network volume.
    10/29/13 12:40:29.325 AM com.apple.backupd[1628]: Waiting 60 seconds and trying again.
    10/29/13 12:41:40.533 AM com.apple.backupd[1628]: Attempting to mount network destination URL: afp://edbern;AUTH=SRP@TC._afpovertcp._tcp.local/edbern
    10/29/13 12:41:41.252 AM com.apple.backupd[1628]: Mounted network destination at mount point: /Volumes/edbern-1 using URL: afp://edbern;AUTH=SRP@TC._afpovertcp._tcp.local/edbern
    10/29/13 12:41:44.549 AM com.apple.backupd[1628]: Disk image already attached: /Volumes/edbern-1/EB’s MacBook Air.sparsebundle, DIHLDiskImageAttach returned: 35
    10/29/13 12:41:46.208 AM com.apple.backupd[1628]: Failed to mount disk image: Error Domain=com.apple.backupd.ErrorDomain Code=31 "The operation couldn’t be completed. (com.apple.backupd.ErrorDomain error 31.)" UserInfo=0x7ffdc26090d0 {MessageParameters=(
        "/Volumes/edbern-1/EB\U2019s MacBook Air.sparsebundle"
    10/29/13 12:41:46.309 AM com.apple.backupd[1628]: Ejected Time Machine network volume.
    10/29/13 12:41:46.310 AM com.apple.backupd[1628]: Giving up after 3 retries.
    10/29/13 12:41:46.350 AM com.apple.backupd[1628]: Backup failed with error 31: 31
    10/29/13 1:44:01.616 AM com.apple.backupd[1768]: Starting automatic backup
    10/29/13 1:44:01.649 AM com.apple.backupd[1768]: Attempting to mount network destination URL: afp://edbern;AUTH=SRP@TC._afpovertcp._tcp.local/edbern
    10/29/13 1:44:02.604 AM com.apple.backupd[1768]: Mounted network destination at mount point: /Volumes/edbern-1 using URL: afp://edbern;AUTH=SRP@TC._afpovertcp._tcp.local/edbern
    10/29/13 1:44:07.254 AM com.apple.backupd[1768]: Disk image already attached: /Volumes/edbern-1/EB’s MacBook Air.sparsebundle, DIHLDiskImageAttach returned: 35
    10/29/13 1:44:08.881 AM com.apple.backupd[1768]: Failed to mount disk image: Error Domain=com.apple.backupd.ErrorDomain Code=31 "The operation couldn’t be completed. (com.apple.backupd.ErrorDomain error 31.)" UserInfo=0x7f9af9531a70 {MessageParameters=(
        "/Volumes/edbern-1/EB\U2019s MacBook Air.sparsebundle"
    10/29/13 1:44:08.962 AM com.apple.backupd[1768]: Ejected Time Machine network volume.
    10/29/13 1:44:08.962 AM com.apple.backupd[1768]: Waiting 60 seconds and trying again.
    10/29/13 1:45:20.105 AM com.apple.backupd[1768]: Attempting to mount network destination URL: afp://edbern;AUTH=SRP@TC._afpovertcp._tcp.local/edbern
    10/29/13 1:45:20.536 AM com.apple.backupd[1768]: Mounted network destination at mount point: /Volumes/edbern-1 using URL: afp://edbern;AUTH=SRP@TC._afpovertcp._tcp.local/edbern
    10/29/13 1:45:23.526 AM com.apple.backupd[1768]: Disk image already attached: /Volumes/edbern-1/EB’s MacBook Air.sparsebundle, DIHLDiskImageAttach returned: 35
    10/29/13 1:45:25.145 AM com.apple.backupd[1768]: Failed to mount disk image: Error Domain=com.apple.backupd.ErrorDomain Code=31 "The operation couldn’t be completed. (com.apple.backupd.ErrorDomain error 31.)" UserInfo=0x7f9af97030e0 {MessageParameters=(
        "/Volumes/edbern-1/EB\U2019s MacBook Air.sparsebundle"
    10/29/13 1:45:25.280 AM com.apple.backupd[1768]: Ejected Time Machine network volume.
    10/29/13 1:45:25.280 AM com.apple.backupd[1768]: Waiting 60 seconds and trying again.
    10/29/13 1:46:36.511 AM com.apple.backupd[1768]: Attempting to mount network destination URL: afp://edbern;AUTH=SRP@TC._afpovertcp._tcp.local/edbern
    10/29/13 1:46:37.340 AM com.apple.backupd[1768]: Mounted network destination at mount point: /Volumes/edbern-1 using URL: afp://edbern;AUTH=SRP@TC._afpovertcp._tcp.local/edbern
    10/29/13 1:46:40.510 AM com.apple.backupd[1768]: Disk image already attached: /Volumes/edbern-1/EB’s MacBook Air.sparsebundle, DIHLDiskImageAttach returned: 35
    10/29/13 1:46:42.150 AM com.apple.backupd[1768]: Failed to mount disk image: Error Domain=com.apple.backupd.ErrorDomain Code=31 "The operation couldn’t be completed. (com.apple.backupd.ErrorDomain error 31.)" UserInfo=0x7f9af9608030 {MessageParameters=(
        "/Volumes/edbern-1/EB\U2019s MacBook Air.sparsebundle"
    10/29/13 1:46:42.195 AM com.apple.backupd[1768]: Ejected Time Machine network volume.
    10/29/13 1:46:42.195 AM com.apple.backupd[1768]: Giving up after 3 retries.
    10/29/13 1:46:42.198 AM com.apple.backupd[1768]: Backup failed with error 31: 31
    10/29/13 2:49:46.227 AM com.apple.backupd[1880]: Starting automatic backup
    10/29/13 2:49:46.301 AM com.apple.backupd[1880]: Attempting to mount network destination URL: afp://edbern;AUTH=SRP@TC._afpovertcp._tcp.local/edbern
    10/29/13 2:49:47.381 AM com.apple.backupd[1880]: Mounted network destination at mount point: /Volumes/edbern-1 using URL: afp://edbern;AUTH=SRP@TC._afpovertcp._tcp.local/edbern
    10/29/13 2:49:50.418 AM com.apple.backupd[1880]: Disk image already attached: /Volumes/edbern-1/EB’s MacBook Air.sparsebundle, DIHLDiskImageAttach returned: 35

  • Time capsule won't delete old backups

    Time capsule working fine since months ago. After snow leopard upgrade started to give warning that not enough space is available. Delete old backup's option is on.

    The Time Capsule was designed to work with Time Machine for backups. That doesn't mean you can't use other backup software to do the job, but Time Capsule is "relying" on Time Machine to perform backup maintenance ... like deleting the oldest files.
    Because you are using a Mac with an non-Leopard OS, you will have to either rely on the backup program that you are using or self-maintenance. I would suspect that in order to delete the current backups, you would need to access the Time Capsule's hard drive directly through the Finder. You mention the connection fails. What exactly is the error you are seeing when attempting to access the Time Capsule?

  • HT4847 How can I delete old backups on my iCloud so that I can just backup my latest things?

    How can i delete old backups on my iCloud so that I can jsut backup what is on my device now, and not from a year ago

    Welcome to the Apple Support Communities
    All backups made on iCloud overwrite the old one, so you have only the latest backup with your most recent files. If you have a backup of an old device, open Settings > iCloud > Storage and Backup > Manage Storage, select the backup and delete that backup

Maybe you are looking for

  • SharePoint Designer 2013 cannot access workflows in Office 365 Site

    I have an Office 365 SharePoint site with a number of workflows that I have created on my machine with SPD 2013. After a number of weeks I was unable to access the workflows from my machine through SPD (while still being able to access pages, site as

  • The attempt to burn a disc failed. An unknown error occurred (-50)

    Hey Guys, Got the error message "The attempt to burn a disc failed. An unknown error occurred (-50) in iTunes. I'm just trying to burn a few audio CDs. Running most current verison of Mavericks, all software up to date. I've tried changing the burnin

  • P2 Users might like to take a look at this .... (P2 Forge)

    I have just purchased this after a short trial and it is a very comprehensive application that does a lot more than P2 stuff.... Two main components (loaded with tools) P2 Viewer , P2 Ingest. Will playback what ever Codecs you have loaded in your sys

  • Error reading SMTP packet

    Hi all, Can anybody point me to the right direction? I keep getting this error once in a while. Is it a network or mail server problem? --- mail.log_current output 11-Sep-2009 18:03:00.75 tcp_local tcp_intranet VES 0 [email protected] rfc822;[email protected] @m

  • Alphanumeric counter

    Hi, I need to write a query / function for an alphanumeric counter that would work as below: A000 A001 A002 A003 A004 A005 A006 A007 A008 A009 A00A A00B A00C A00Y A00Z A010 A011 A019 A01A A01B This would mean that the next value after Z999 would be Z