Sparse bundle modification date

I have been using time machine with a timecapsule to back up my macbook pro. I have used it for several weeks. I noticed that the sparse bundle file that contains the backup data has a creation date and a modification date that are both the same and match the creation date. This is despite the fact that I believe the file has been updated many times when time machine does its hourly backups. I can go into time machine and see the more recent backups. Can someone with a similar configuration take a quick look at the sparse bundle file creation and modification dates to see if they match? Is this the expected behavior?

tall_dan wrote:Can someone with a similar configuration take a quick look at the sparse bundle file creation and modification dates to see if they match? Is this the expected behavior?
Yep. Same creation and modification date. No problems with a 8 month old sparsebundle.

Similar Messages

  • I get this error message when I try to back up my laptop:  Time machine could not complete the backup.  The backup disc image "/Volumes/Data/Lou Ann Buesing's Mac Book Pro. sparse bundle is already in use.  Anyone know how to fix it?

    I get this error message when I try to back up my laptop:
    ' Time machine could not complete the backup.  The backup disc image "/Volumes/Data/Lou Ann Buesing's Mac Book Pro. sparse bundle' is already in use. "
    Anyone know how to fix it?

    Reboot the TC.. Sometimes you need to reboot the whole network.
    This is what comes of Lion and then made worse in Mountain Lion of Apple not spending enough time to fix the bugs.
    Read C12 in pondini.
    http://pondini.org/TM/Troubleshooting.html
    C17 can be related I think.

  • HT3275 Time machine cannot backup due to "The backup disk image "/Volume/Data/Dave's Macbook Pro."sparse bundle" is already in use." Does anyone know what this means and how to fix it??

    My time machine is sending me a message; "The backup disk image "/Volume/Data/Dave's Macbook Pro "sparse bundle" is already in use". As a result, the time machine cannot complete a backup. Any suggestions?

    Look at the more like this column on the right.. this is the most common problem reported here.
    You need to restart the TC.. that is all..
    Pull out the power cord.. count to 10.. plug in power cord.
    There are a few occasions where this fails.. see C12 http://pondini.org/TM/Troubleshooting.html

  • How do I convert TC sparse bundle to disk image?

    Ok, this question could be cross-listed under a number of threads, so I had to just pick one...
    A few months ago, the HD in my MB was clearly dying, so I replaced it with a larger, faster drive. All good, until I realized I had been close to maxing out my Time Capsule before I upgraded my MB's HD, so I upsized that, too.
    Fast forward 2 months.
    I have a weird problem where iPhoto events start going dark. The database had these previously imported files listed, but the files themselves were nowhere to be found! The event in iPhoto showed black squares where the images used to be, but even looking in finder... No pics!
    I want to go back into my old (saved) HD that I pulled from my Time Capsule. I stuck it in an external USB enclosure, and hooked it up. I told Time Machine to use it as the backup, but after it 'verified' it, it didn't show me the archived files. It does show a 'sparse bundle' in finder, which I understand is similar to a disk image. So is there a way to convert the sparse bundle to a disk image? Do I need to plug my old TC HD back into the TC to get to that archive?
    Help! Among the lost photos are ones from a trip to Australia and my grandmother's memorial service. I need to get these back!
    Thank you in advance.

    tgilk wrote:
    I've already done the TC surgery once before and the hardest thing was loosening the adhesive on the rubber pad / gasket on the bottom of the unit. After that, I completed the HD replacement in about 15 minutes... piece of cake. There's actually a good tutorial on AppleFritter. But I digress...
    It's not too much of a digression. Remember that if you are just firing up the Time Capsule with the old hard drive, you don't have to reassemble it. Just swap out the plugs from the old drive to the new and turn it on. A true PC geek never runs with the cover on.
    However, messing around with adhesives and thermal paste introduces a new element of risk. If you know the dates that have good data, and you are comfortable merging the newer photos back in, accessing the data via the Finder on an external enclosure would be faster and safer.
    So, can I turn the TM backups off and still enter 'TM' to browse through the backups on the drive? I've ID'd the specific dates of my missing photo events, so as long as I can get into the backup, I will know just what folders to search for in the 'Originals' folders in the backup.
    Yes. That is probably one of the most important and least known tips about Time Machine. You can still use it even if the backups are turned off. Furthermore, if you ever start to have problems on your machine, you should turn off Time Machine to avoid further corruption of your backups.

  • How to stop Time Machine from trying to resize a sparse bundle

    With 10.8, I'm backing up wirelessly from my MacBook Pro to a sparse bundle on a Drobo connected to a Mac mini on the same network. I used Drobo's Time Tamer to create the sparse bundle. The sparsebundle is a set size and cannot be resized (this is intentional to avoid filling the Drobo which is mostly used to store non-backed up non-critical data.
    Every step of the backup process works, but Time Machine spends a good 20-30 minutes during each backup "resizing" the disk image. It doesn't actually suceed in resizing the disk image, but it displays "Looking for Backup Disk" in the Time Machine menu while Console reveals that it's resizing the disk image ("Resizing backup disk image from 17.59 TB to 17.59 TB"). It doesn't cause any errors, but it does turn the backup time from a few minutes
    Does anyone know of a workaround to disable this resizing step or to make it fail quickly and proceed with the rest of the backup normally?
    I wasn't using Time Machine before upgrading to 10.8 from 10.7, so I don't know if this is a new issue with Mountain Lion. I suspect that this would happen in earlier OS versions too.

    I'm experiencing it on a Synology NAS. Time Machine always starts by "Resizing backup disk image from 1.07 TB to 1.07 TB." In the status bar, it just displays "looking for backup disk."
    I don't have any solutions yet. Would definitely be interested to hear. I think it might have to do with the fact that I increased the user's disk quota (on the NAS) after doing the initial time machine backup. While Time Machine correctly identified the extra space as available, it somehow can't get over the fact that it changed once.
    Things I have done:
    Manually ran hdiutil resize -size 1000g *.sparseimage. This did change the reported disk size in the disk's Info.plist, but the next backup still did the resize step.

  • How to limiting the size of an existing Sparse Bundle for Time Machine?

    There seems to be a solution for locking the size of a new sparse bundle to be used for Time Machine backups (see https://discussions.apple.com/thread/2383738?tstart=0).  However, I have a Time Machine sparse bundle with a year's worth of history that is getting very large and I would like to limit its size.  Is there a way to constrain the size of an existing sparse bundle without trashing it. 
    Appying the suggested techniques"
    hdiutil resize -size 300g xyz.sparsebundle
    and
    SetFile -a L PATHTOSPARSEBUNDLE/Info.*
    on an existing sparse bundle somehow corrupts it and TM wants to start from scratch. 
    A method for constraining the size of a TM sparse bundle without trashing it would be very appreciated.

    budden10, please try this:
    Disconnect the external drive to simulate it not working or having failed
    Open Time Machine on your Mac and wait a few minutes for your backups to load fully
    Go back in time and select a date when you were backing up the external drive
    Now look at the Finder window and locate your Mac on the left side of the window under DEVICES
    Click on your Mac
    What do you see in the window there just to the right?

  • How do I delete a sparse bundle in Time Machine?

    I backup two computers over a home wireless network to a Time Capsule. But there are three TM sparsebundles on the TC; one is from a computer that is long gone. I need to create space on the TC as I got an error message stating that; I have a new disk and TM is trying to create a new backup for that.
    I read the TM FAQs that are often cited in Discussions but I don't know what vintage those recommendations are; can someone give me an up-to-date proceedure for deleting the uneeded sparsebundle? It is 123 GB and my TC is 500 GB.
    Thansk;
    Bruce

    I tried this:
    If a sparse bundle is very large, and OSX says it will take many hours to delete it, there is a faster, but more tedious, way:
    •Cancel the deletion. 
    •Right-click the sparse bundle in the Finder and select Show Package Contents. 
    •Open the bands folder (it may take a while to show the contents).
    •Select a large number of bands (up to about 8000 at a time), and delete (trash) them.
    •When they’re all deleted, delete the sparse bundle.
    I got an error message:
    "This operation cannot be completed because df4 [one of the bands] is in use."
    Next step?

  • Why is the sparse bundle so much smaller than the backed up computer...can I be confident all files are backed up?

    Hey gang,
    iphoto folder became big so I have moved it to an external drive. I made sure the external disk is not excluded from timemachine backup in tm preferences. Backup seemed to take forever (it actually said "preparing for backup" the whole time with a spinning progress bar) ie 24 hours and still the same pogress bar.
    i stopped the process as i had no confidence anything was actually happening
    When i open up time machine, an earlier version of my imac is there, but the external drive is kind of greyed and i cannot access it.
    When  I check the sparse bundle size, it is under 200 gb, when my imac is around 600 gb, 900 with the external drive.
    Why is the sparse bundle so small relative to the imac? are there hidden data files outside of the sparse bundle? when checking the preferences, it states total included is 921 gb...yet that is not reflected in the sparse bundle size.
    I want to be sure iphoto is actually backed up before deleting it from my imac.
    thanks anyone!

    marten berkman wrote:
    I am wondering whether the "processing" progress bar was due to the time capsule freeing up space for the additional data on the new external drive. When I cancelled it, available space on the tc incresed from 200 to 500 gb.
    Yes, quite possibly.  Especially on Leopard and Snow Leopard, that process on network backups is excruciatingly repetitive and slow.    It's improved greatly in Lion and later, but still isn't exactly quick.
    The backup complete, i checked the contents of the backed up version of the external drive, and the iphoto folder was the same size as original, so I have confidence that iphoto is backed up. Now I could delete the iphoto from the imac, freeing up tons of space.
    Yay! 
    Still curious why the imac sparsebundle is only 160gb, while my macbook pro sparsebundle is about 700 gb...as though they are inversely named from the computers they back up.
    Oh, I didn't realize you had two Macs backing-up to the TC.  Which one is the external HD connected to? 
    Unless you've specifically excluded things, after the initial backup, the sparse bundle should be nearly the size of the data it's backing-up (TM does exclude some things like system work files, most caches and logs, and trash, so the backups are a few GBs smaller).  As you do more backups, of course, it will grow.
    So please clarify how much data is on each drive, Mac, and sparse bundle.
    Also, the 2tb time capsule has 258 gb of 1.8 tb available....am I to suppose that there is hidden backup data not in the sparse bundles?
    Sparse bundles are odd critters.  They don't automatically shrink when things are deleted from them.  Instead, the vacated space is used for new files until it's full, then it begins to grow again.  Time Machine will "compact" them when necessary, to reclaim the empty space, but doesn't take the time to do it unless it's out of room.
    You can do that manually if you want, per the pink box in Time Machine - Frequently Asked Question #12. 
    Message was edited by: Pondini

  • Does Time Machine still ignore mounted disk images? Specifically, encrypted sparse bundle disk images?

    My Time Machine backs up to Time Capsule which cannot be encrypted. I also have confidential data in an encrypted sparse bundle disk image in my home folder. When TM backs up and the encrypted sparse bundle disk image is mounted and I'm accessing the data, does TM back up the data "in the clear" decrypted form or does it exclude the disk image because it's mounted? I've done a little research, but there's conflicting information. Not sure what happens in Lion now...

    Time Machine does not backup mounted disk images! The encrypted sparse bundle disk image was mounted, I updated a doc and did a TM backup - the file was not listed in the TM repository and the doc remained unchanged in the encrypted sparse bundle disk image on TM. Then I ejected the disk image and did a TM backup - the updated doc was backed up in the encrypted sparse bundle disk image! Thank you!

  • Best approach for Time Machine / Entourage / FileVault / sparse bundle disk

    I am looking to set up Time Machine belatedly on my G5 to provide hassle-free backup for me and my family. I use Entourage. I also want to provide a small amount of encrypted storage. I’ve scoured the obvious places which have plenty of ideas, but nothing which pulls it all together.
    My thoughts so far have been:
    1. Time Machine doesn’t work well with Entourage as Entourage uses a monolithic single file (which in my case is several GB big) – backing this up every hour will bring my machine to its knees, fill up the backup disk and will possibly give a corrupt backup as the file could be accessed by Entourage or the MS daemon process during the backup.
    2. I thought of turning FileVault on which would automatically contain the Entourage file. This would mean:
    a) the sparse bundle format (8 MB bands) of FileVault would limit the volume of changed Entourage data which would be backed up each time by Time Machine and
    b) the backup would only occur during logout (which is fine with me) when Entourage and the MS daemon are not running so that the backup won’t be corrupt.
    3. However I am not hearing good things about the reliability of FileVault (comments?) and don’t want all the data in my Home folders lost – I don’t need that much encryption anyway.
    4. So I thought about setting up a couple of encrypted disk images made of sparse bundles – one for the Entourage data (symbolically linked to the right place for Entourage to pick the folder up) and the other for the other small number of files I need encrypted. This could be auto-mounted at login.
    5. However I think that using disk images rather than FileVault loses the automatic backup by Time Machine at logout. Maybe there is a way to get Time Machine to automatically backup these disk images during logout.
    6. Perhaps there is another way to get the disk images backed up at logout other than using Time Machine.
    So my questions are:
    A. What is the best overall approach to providing a low-maintenance reliable backup which deals appropriately with Entourage and provides a small amount of encrypted space?
    B. Can Time Machine be made to backup disk images other than FileVault disk images at logout? (for example is there a particular location / filename format for FileVault images which I could emulate with the other disk images to fool Time Machine into backing them up?)
    C. When Time Machine runs at logout, have MS Entourage and the daemon process already been shut down and the disks unmounted, to prevent corruption?
    D. Is there another way of backing up the sparse image disks at logout?
    C. Is this all going to get magically fixed in Snow Leopard?
    D. Will MS come up with a sensible storage format for Entourage?
    Any thoughts greatly appreciated.

    I don't know if there is a complete solution, but here are some things you could consider.
    1. TM does not run automatically at logout unless FileVault is enabled.
    2. You can change the backup period using third-party utilities like TimeMachineEditor - VersionTracker or MacUpdate.
    3. You can exclude the Microsoft User Data folder from the TM backup and back it up separately using third-party backup software.
    4. You can use third-party backup software instead of TM, such as:
    1. Retrospect Desktop (Commercial - not yet universal binary)
    2. Synchronize! Pro X (Commercial)
    3. Synk (Backup, Standard, or Pro)
    4. Deja Vu (Shareware)
    5. Carbon Copy Cloner (Donationware)
    6. SuperDuper! (Commercial)
    7. Intego Personal Backup (Commercial)
    8. Data Backup (Commercial)
    9. SilverKeeper 2.0 (Freeware)
    10. Tri-Backup (Commercial)
    11. Apple Backup (requires a .Mac account with Apple both to get the software and to use it.)
    Apple's Backup is a full backup tool capable of backing up across multiple media such as CD/DVD. However, it cannot create bootable backups. It is primarily an "archiving" utility.
    Visit The XLab FAQs and read the FAQ on backup and restore. Also read How to Back Up and Restore Your Files.
    Third-party backup utilities can run backups on schedules you set up. Thus, you can schedule your backups to occur at a time when you do not use the machine such as early in the AM for example.

  • Install file(s) action - wrong file's modification date

    Hi,
    here is my problem:
    Files installed by bundle with "Install file(s)" action (or "Install Folder") have wrong "modification date" - actually set to: 17th january 1970.
    Zenworks 11.3, agent 11.3 or 11.2.4 mu1
    Anyone has this problem?
    Regards, ALipiec

    Just for info:
    I am on 11.3 and installed the file upload extension ZENworksFileUploadPlugin.msi with my user.
    I tested the "Install File(s)" function with Firefox 17 ESR:
    I only see the problem with date 12 January 1970 if I upload the file with I select "Do not compress or encrypt uploaded content".
    If I leave that switch unchecked the Creation, Modification, Access -Date are all the same and seem to be the time of the upload into the Repository.
    Even if I upload the file several times into repository it seems that the very first upload date/time is always kept for all following installations.
    Klaus

  • Copying, and using, sparse bundles across OS X systems

    I have a laptop that I use for work, a MacBook Pro 17", on which I have two folders full of data that needs to be secured. I set up two SparseImage files using Disk Utility and copied all data into these file systems, deleting the originals. This worked fine.
    I synchronize my laptop with my home iMac which I use when working at home, I can open these sparse image files, enter the password, and have access to the files as needed. Subsequent synching puts changes back onto the laptop where I can open them at work. All is well.
    This however is suboptimal as both machines use Time Machine and this is best used with Sparse Bundle file systems. Accordingly I created a couple of Sparse Bundle file systems and copied all the Sparse Image files over to the bundles. Again, all worked fine - at least on my laptop where I created them.
    However, when I synch, I get all the bundle files over on my home iMac as I would expect, and the Sparse Bundle files, which is a package and I can open and view the contents - it all looks good. However, when I open the Sparse Bundle on the iMac, instead of getting the password window, I get a little window saying "The following disk images could not be opened, Image: "name.sparsebundle" Reason: "No such file or directory".
    The two file systems, on the iMac and MBP appear identical in all respects, down to the "Open with: DiskImageMounter" app in the GetInfo window. Yet the secured SparseBundle image cannot be opened on my iMac, whereas the SparseImage can. Is there some setting or something that the Bundle needs to work when copied to another machine?
    Thanks - Lawrence

    LawrenceHare wrote:
    I have a laptop that I use for work, a MacBook Pro 17", on which I have two folders full of data that needs to be secured. I set up two SparseImage files using Disk Utility and copied all data into these file systems, deleting the originals. This worked fine.
    I synchronize my laptop with my home iMac which I use when working at home, I can open these sparse image files, enter the password, and have access to the files as needed. Subsequent synching puts changes back onto the laptop where I can open them at work. All is well.
    This however is suboptimal as both machines use Time Machine and this is best used with Sparse Bundle file systems. Accordingly I created a couple of Sparse Bundle file systems and copied all the Sparse Image files over to the bundles. Again, all worked fine - at least on my laptop where I created them.
    However, when I synch, I get all the bundle files over on my home iMac as I would expect, and the Sparse Bundle files, which is a package and I can open and view the contents - it all looks good. However, when I open the Sparse Bundle on the iMac, instead of getting the password window, I get a little window saying "The following disk images could not be opened, Image: "name.sparsebundle" Reason: "No such file or directory".
    The two file systems, on the iMac and MBP appear identical in all respects, down to the "Open with: DiskImageMounter" app in the GetInfo window. Yet the secured SparseBundle image cannot be opened on my iMac, whereas the SparseImage can. Is there some setting or something that the Bundle needs to work when copied to another machine?
    no, there is no special setting. this should work. try deleting the copied sparse bundle and copying it again. also, make sure that you have sufficient privileges to the sparse bundle when you are copying it. how exactly are you syncing the imac with the mbp?

  • Can't share sparse bundle disk image

    I'm trying to create a sparse bundle disk image in /Users/Shared for sharing between two users on the same computer. No matter what I've tried, the disk always mounts as read only for the non-owner user. I've tried creating the disk image in both accounts, adding the non-owner user with "read & write" permissions, changing all permissions (including everyone) to "read & write," but nothing seems to help. Does anyone have any experience sharing sparse bundle disk images using the shared folder?
    Christopher

    I realized after reading the replies above (thank you, A.Carlo and KJK555) that I was only applying permissions to the top level of the sparse bundle image and not to the underlying directories and files in the package. This was what was keeping the second user from making changes to the mounted disk image. After digging a little deeper into possible solutions, following is what I decided to do.
    First, here are the requirements for my sparse bundle disk image:
    1. Full permissions (rwx) for user1 and user2
    2. No permissions (---) for everyone else
    3. Directories and files created by user1 or user2 need to be fully accessible (rwx) by the other user
    In order to block access to the sparse bundle from unwanted users and to allow for inherited permissions for all future directories and files, I took the following steps:
    1. Created a new group (group1) with user1 and user2 as members
    2. Created a new folder (Example) under /Users/Shared
    3. Removed all permissions from the new folder for everyone but user1 (chmod 700 Example)
    4. Added an ACL to prevent group everyone from deleting the new folder (chmod +a "group:everyone deny delete" Example)
    5 Added an ACL to give group1 full permissions (rwx) to the new folder and allow those permissions to be inherited by new directories and files created within that folder (chmod +a "group:christophertemple allow list,addfile,search,add_subdirectory,delete_child,readattr,writeattr,readextattr,writeex tattr,readsecurity,file_inherit,directoryinherit)
    This is what the new folder looks like from Terminal:
    $ ls -le
    total 0
    drwx------+ 4 user1 wheel 136 Sep 18 12:45 Example
    0: group:everyone deny delete
    1: group:group1 allow list,addfile,search,add_subdirectory,delete_child,readattr,writeattr,readextattr,writeex tattr,readsecurity,file_inherit,directoryinherit
    This folder is now accessible only by user1 and user2 and any files or directories created in this folder will be accessible by both users, regardless of which of the two users created them.
    Next, I created an encrypted sparse bundle disk image within the new folder. In Terminal, the disk image looks like this:
    $ ls -le
    total 0
    drwxr-xr-x@ 6 user1 wheel 204 Sep 18 13:03 Example.sparsebundle
    0: group:group1 inherited allow list,addfile,search,add_subdirectory,delete_child,readattr,writeattr,readextattr,writeex tattr,readsecurity,file_inherit,directoryinherit
    As can be seen above, the new sparse bundle has inherited the group permissions from the parent directory, giving user1 and user2 full access to the disk image.
    While I could have added a few extra steps and changed the permissions of the mounted disk image, I decided against doing so; the default permissions were perfect for my use. By default, the mounted disk image is set to "Ignore ownership on this volume."
    When mounted by user1 this is how the disk image looks in Terminal:
    $ ls -le
    total 8
    drwx------ 7 user1 staff 306 Sep 18 13:01 Example Disk Image
    When mounted by user2 this is how the disk image looks in Terminal:
    $ ls -le
    total 8
    drwx------ 7 user2 staff 306 Sep 18 13:01 Example Disk Image
    With these permissions, no user, other than the user that mounted the image, has access to the image while the image is mounted. This is useful from a security standpoint, keeping others from viewing the contents of the disk image, as well as from a data integrity standpoint, allowing only one person to access files on the disk image at a time (important for some of the data base files the image contains).
    Thanks again to those that responded. I hope this post is helpful to others who might have similar requirements as I did.
    Christopher

  • How to delete a sparse bundle

    I have added a new Mini to my network and repurposed a former Mini. I would like to remove the sparse.bundle for the former mini to free up space and start a new TM backup.
    I am unable to delete or mount the former Mini sparse.bundle. Disk Utility doesn't recognize the image for mounting. Trash attempts to delete the item, but after 6 hours with the message Items to Delete: 0, nothing has happened.
    Trying to have Time Machine on the repurposed Mini continue with backups fails as well.
    Is there a way in Terminal or something to delete this file which must be damaged without erasing the whole TC and starting over. I do have other sparse.bundles from other machines on there I would like to keep.
    Thanks in advance for any advice.

    Molson2043 wrote:
    Is there a way in Terminal or something to delete this file which must be damaged without erasing the whole TC and starting over.
    First mount the internal Time Capsule disk, assumed in the example below to have the default name "Data". Launch Terminal, then type these commands:
    cd /Volumes/Data
    ls
    That's a lower-case letter "L" at the beginning of that last command. You should see all your "sparsebundle" volumes.
    Then type this command (including a trailing space) but do not yet press "return":
    sudo rm -rf
    Now open the "Data" volume. Drag the "sparsebundle" file you want to delete from the "Data" volume's Finder window to the Terminal window. This should cause the path and name of the volume you want to delete to be copied into the Terminal window. Now select the Terminal window. Double-check that the correct "sparsebundle" file is in the command, then press "return". You'll be prompted for your administrative password.
    If you're at all unsure that you can do this safely, then you probably shouldn't try it this way.

  • Time machine is giving me this error;sparse bundle could not be access (error-1)

    The time machine is giving me this error; Disk Image"/Volumes/Data/adminstration Mac Book Pro (2).sparse bundle" could not be access (error-1)

    Restart the TC.. ie pull out the power.. count to 10.. plug in power.
    Still have issues restart the whole network in correct order.. modem.. TC.. clients. 2min gap. Any other network clutter.. restart in order it is connected..
    See C17 for more info if you still have issues.
    http://pondini.org/TM/Troubleshooting.html
    C12 is most popular problem.. but C17 is close second.
    I would also read C9 as your naming is perhaps a cause of the problem.

Maybe you are looking for