Re: Getting time machine to backup a drive image
On 2017-09-27, at 7:14 AM, LuKreme wrote: > On Sep 26, 2017, at 12:00, Michael wrote: >> Last restore, I found that backblaze does not save the executable bit for >> any data file -- broke shell scripts, etc. With a sparse bundle to fix that, >> the next question is keeping local backups meaningful. > > Backblaze also doesn’t backup any files in /usr/local/ Oh? (checks ... ) Ok, the oddballs are "/usr" -- in it's entirety -- and "/private" that includes some machine-specific config files. Time to file a bug report -- /usr/local is kinda important. /private/var/mail -- really important /private/var/spool ... not sure about /private/var/db /private/etc has a BUNCH of machine-specific configs -- all the SSH keys, rc.local, various config files, etc. Thank you for pointing that out. ___ MacOSX-talk mailing list MacOSX-talk@omnigroup.com http://www.omnigroup.com/mailman/listinfo/macosx-talk
Re: Getting time machine to backup a drive image
On Sep 26, 2017, at 12:00, Michael wrote: > Last restore, I found that backblaze does not save the executable bit for any > data file -- broke shell scripts, etc. With a sparse bundle to fix that, the > next question is keeping local backups meaningful. Backblaze also doesn’t backup any files in /usr/local/ -- This is my signature. There are many like it, but this one is mine. ___ MacOSX-talk mailing list MacOSX-talk@omnigroup.com http://www.omnigroup.com/mailman/listinfo/macosx-talk
Re: Getting time machine to backup a drive image
On Sep 26, 2017, at 21:43, Michael_google gmail_Gersten wrote: > > New drive has 2 extra TB, so I figure I'm at least a year before that happens > again :-). Your TM disk should have at least double the space that your entire backup will take up. -- This is my signature. There are many like it, but this one is mine. ___ MacOSX-talk mailing list MacOSX-talk@omnigroup.com http://www.omnigroup.com/mailman/listinfo/macosx-talk
Re: Getting time machine to backup a drive image
So as much as people say “Time Machine won’t do this because the bundle might not be mounted next time, and then it has to back up the whole thing again”: Time Machine is happy to back up my USB sticks without any issues. Whether they are there or not on a given backup. > On Sep 26, 2017, at 12:52 PM, Arno Hautala wrote: > > On Tue, Sep 26, 2017 at 2:00 PM, Michael wrote: >> >> Hmm. Diskutil info reports that it is backed by a sparse bundle. So the >> system does track that, and time machine could see that. What I need is a >> block device loopback device, and a way to feed that sparse bundle to that >> block loopback, so it would look like it was on a block device instead of an >> image file. >> >> Any idea how to do that? > > lolwut!? But seriously, no idea. You could probably do something like > that by implementing your own FUSE plugin, but I'd be surprised if > anything like that exists. Sparsebundles are already mountable and I > doubt many people are going to take the time to re-implement it. This > is about the time that some pops in with a link to exactly such a > working project. I’m looking for a block device loopback. Give it a mountable disk image, it behaves like you’re reading a real block device, without the system seeing that there’s a file image behind it. Can’t be that hard. If I knew Fuse, I could probably write it -- it sounds like a "hello world" level of program for it. >> The point of putting this file system in a sparse bundle was to make sure >> that the next time it dies / needs to be recovered from an online backup >> (backblaze) was to ensure that file meta-data is saved properly. At the same >> time, I want to have a local history backup so that I don't have to worry >> about downloading if I don't have to. (2/3rd of the disk is for time >> machine, and 1/3rd is for this stuff). > > So, my reading is that you're backing up to a sparsebundle because > that that will preserve the metadata you care about. I think I'd look > instead at to another backup tool. Backblaze has the best online backup available. And nothing beats the whole "In the event of a whole drive failure, we'll ship you a drive that you can restore from". I was previously putting my time machine onto a sparse bundle, and that was being backed up, so that if my drive died, I could restore from that. Sadly, the backup performance of the sparse bundle went downhill so badly that I had to abandon that. How does the whole "network time machine into a sparse bundle" system manage to work, or is it always going to be slow? Or is it just hidden by the network speed? (And in fairness, it would not have helped. The drive that died? This stuff had grown too big to fit on the time machine with the backup of the internal. New drive has 2 extra TB, so I figure I'm at least a year before that happens again :-). ___ MacOSX-talk mailing list MacOSX-talk@omnigroup.com http://www.omnigroup.com/mailman/listinfo/macosx-talk
Re: Getting time machine to backup a drive image
On Tue, Sep 26, 2017 at 2:00 PM, Michael wrote: > > Hmm. Diskutil info reports that it is backed by a sparse bundle. So the > system does track that, and time machine could see that. What I need is a > block device loopback device, and a way to feed that sparse bundle to that > block loopback, so it would look like it was on a block device instead of an > image file. > > Any idea how to do that? lolwut!? But seriously, no idea. You could probably do something like that by implementing your own FUSE plugin, but I'd be surprised if anything like that exists. Sparsebundles are already mountable and I doubt many people are going to take the time to re-implement it. This is about the time that some pops in with a link to exactly such a working project. > The point of putting this file system in a sparse bundle was to make sure > that the next time it dies / needs to be recovered from an online backup > (backblaze) was to ensure that file meta-data is saved properly. At the same > time, I want to have a local history backup so that I don't have to worry > about downloading if I don't have to. (2/3rd of the disk is for time machine, > and 1/3rd is for this stuff). So, my reading is that you're backing up to a sparsebundle because that that will preserve the metadata you care about. I think I'd look instead at to another backup tool. In the wake of Crashplan shutting down their unlimited, multi-user plan, I've been evaluating Duplicacy backing up to B2. Duplicacy does handle some metadata, but it's not a perfect score in BackupBouncer. Duplicacy does handle multiple backup destinations (ie. local and cloud). Have you considered other tools? Arq is probably a good option for you here. -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ MacOSX-talk mailing list MacOSX-talk@omnigroup.com http://www.omnigroup.com/mailman/listinfo/macosx-talk
Re: Getting time machine to backup a drive image
On 2017-09-26, at 9:07 AM, Arno Hautala wrote: > On Mon, Sep 25, 2017 at 11:52 AM, Michael wrote: >> >> I'm not going to a sparse image (which worked fine to start, but became >> horribly slow), I'm talking about taking something that is currently an >> image, and turning it into a normal directory in the time machine (right now >> it is only backed up as a disk image, not as the contents). > > I can see how to exclude volumes, but no way to explicitly include a volume. > > Looks like this isn't supported. > > https://superuser.com/questions/148849/backup-mounted-drive-of-an-image-in-time-machine Aha! Searching (ok, reading article after article), I found this: https://superuser.com/questions/285225/how-to-make-timemachine-back-up-contents-of-any-path-or-mounted-volume?noredirect=1&lq=1 The trick: That sparsebundle mounted looks like a removable disk, like a floppy/cd/USB stick. So, you have to make it look like a fixed hard drive. Applescript: do shell script "hdiutil attach /path/to/your.sparsebundle -notremovable" with administrator privileges Make that an automator script and put it in your startup items, or put the bash equivalent into rc.local, etc -- either way, it becomes time machine-able. Now, the big caveat. If it's missing in one backup, and present the next backup, time machine might decide to back up the entire drive from scratch. ... Ahh, FOO. The comments there says it was tested and working in 10.7 and 10.8, but I can now confirm it fails to work in 10.9. Gaaa grumble grumble grumble The point of putting this file system in a sparse bundle was to make sure that the next time it dies / needs to be recovered from an online backup (backblaze) was to ensure that file meta-data is saved properly. At the same time, I want to have a local history backup so that I don't have to worry about downloading if I don't have to. (2/3rd of the disk is for time machine, and 1/3rd is for this stuff). Last restore, I found that backblaze does not save the executable bit for any data file -- broke shell scripts, etc. With a sparse bundle to fix that, the next question is keeping local backups meaningful. ... I guess the only answer is to toss the sparsebundle/bands into time machine and mount/search all the images when I need to try to find something. Hmm. Diskutil info reports that it is backed by a sparse bundle. So the system does track that, and time machine could see that. What I need is a block device loopback device, and a way to feed that sparse bundle to that block loopback, so it would look like it was on a block device instead of an image file. Any idea how to do that? ___ MacOSX-talk mailing list MacOSX-talk@omnigroup.com http://www.omnigroup.com/mailman/listinfo/macosx-talk
Re: Getting time machine to backup a drive image
On Mon, Sep 25, 2017 at 11:52 AM, Michael wrote: > > I'm not going to a sparse image (which worked fine to start, but became > horribly slow), I'm talking about taking something that is currently an > image, and turning it into a normal directory in the time machine (right now > it is only backed up as a disk image, not as the contents). I can see how to exclude volumes, but no way to explicitly include a volume. Looks like this isn't supported. https://superuser.com/questions/148849/backup-mounted-drive-of-an-image-in-time-machine -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ MacOSX-talk mailing list MacOSX-talk@omnigroup.com http://www.omnigroup.com/mailman/listinfo/macosx-talk
Re: Getting time machine to backup a drive image
On 2017-09-25, at 9:03 AM, Arno Hautala wrote: > On Mon, Sep 25, 2017 at 11:52 AM, Michael wrote: >> >> I'm not going to a sparse image (which worked fine to start, but became >> horribly slow), I'm talking about taking something that is currently an >> image, and turning it into a normal directory in the time machine (right now >> it is only backed up as a disk image, not as the contents). > > Ah, got it. > > Are you able to select the mounted volume as a backup source? > Is the mounted volume silently skipped? > Are there any error messages from backupd? I am not able to select it. It does not show up. It is silently skipped. No error messages. 10.9.5 (Got a 64 GB partition to install 10.12.6 in for testing.) > > -- > arno s hautala/-| a...@alum.wpi.edu > > pgp b2c9d448 --- Entertaining minecraft videos http://YouTube.com/keybounce ___ MacOSX-talk mailing list MacOSX-talk@omnigroup.com http://www.omnigroup.com/mailman/listinfo/macosx-talk
Re: Getting time machine to backup a drive image
On Mon, Sep 25, 2017 at 11:52 AM, Michael wrote: > > I'm not going to a sparse image (which worked fine to start, but became > horribly slow), I'm talking about taking something that is currently an > image, and turning it into a normal directory in the time machine (right now > it is only backed up as a disk image, not as the contents). Ah, got it. Are you able to select the mounted volume as a backup source? Is the mounted volume silently skipped? Are there any error messages from backupd? -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ MacOSX-talk mailing list MacOSX-talk@omnigroup.com http://www.omnigroup.com/mailman/listinfo/macosx-talk
Re: Getting time machine to backup a drive image
On 2017-09-25, at 6:28 AM, Arno Hautala wrote: > On Sun, Sep 24, 2017 at 10:40 PM, Michael wrote: >> So if a hard drive is backed by a physical disk, time machine will back it >> up just fine. >> If it's backed up by an hdiutil mounted image, then it seems to refuse to >> back it up. > > I haven't used TimeMachine in a while, but this previously worked just > fine. I had a sparse bundle image on an AFP share. Every hour TM would > invisibly mount the share, then mount the image, perform the backup, > and finally unmount the image and share. Wrong direction. I'm not going to a sparse image (which worked fine to start, but became horribly slow), I'm talking about taking something that is currently an image, and turning it into a normal directory in the time machine (right now it is only backed up as a disk image, not as the contents). ___ MacOSX-talk mailing list MacOSX-talk@omnigroup.com http://www.omnigroup.com/mailman/listinfo/macosx-talk
Re: Getting time machine to backup a drive image
On 2017-09-25, at 6:28 AM, Arno Hautala wrote: > On Sun, Sep 24, 2017 at 10:40 PM, Michael wrote: >> So if a hard drive is backed by a physical disk, time machine will back it >> up just fine. >> If it's backed up by an hdiutil mounted image, then it seems to refuse to >> back it up. > > I haven't used TimeMachine in a while, but this previously worked just > fine. I had a sparse bundle image on an AFP share. Every hour TM would > invisibly mount the share, then mount the image, perform the backup, > and finally unmount the image and share. Wrong direction. I'm not going to a sparse image (which worked fine to start, but became horribly slow), I'm talking about taking something that is currently an image, and turning it into a normal directory in the time machine (right now it is only backed up as a disk image, not as the contents). ___ MacOSX-talk mailing list MacOSX-talk@omnigroup.com http://www.omnigroup.com/mailman/listinfo/macosx-talk
Re: Getting time machine to backup a drive image
On Sun, Sep 24, 2017 at 10:40 PM, Michael wrote: > So if a hard drive is backed by a physical disk, time machine will back it up > just fine. > If it's backed up by an hdiutil mounted image, then it seems to refuse to > back it up. I haven't used TimeMachine in a while, but this previously worked just fine. I had a sparse bundle image on an AFP share. Every hour TM would invisibly mount the share, then mount the image, perform the backup, and finally unmount the image and share. Do you have any error messages in Console.app from backupd? Or are you unable to even select the mounted image volume as the destination? ___ MacOSX-talk mailing list MacOSX-talk@omnigroup.com http://www.omnigroup.com/mailman/listinfo/macosx-talk
Getting time machine to backup a drive image
So if a hard drive is backed by a physical disk, time machine will back it up just fine. If it's backed up by an hdiutil mounted image, then it seems to refuse to back it up. In both cases, a /dev/*disk* entry has it, and it's an HFS+J drive. /dev/disk0 #: TYPE NAMESIZE IDENTIFIER 0: GUID_partition_scheme*1.0 TB disk0 1:EFI EFI 209.7 MB disk0s1 2: Apple_HFS Macintosh HD40.0 GBdisk0s2 3: Apple_Boot Recovery HD 650.0 MB disk0s3 4: Apple_HFS UserData832.8 GB disk0s4 5: Apple_HFS New Main126.1 GB disk0s5 6: Apple_Boot Recovery HD 650.0 MB disk0s6 /dev/disk1 #: TYPE NAMESIZE IDENTIFIER 0: GUID_partition_scheme*64.0 GBdisk1 1:EFI EFI 209.7 MB disk1s1 2: Apple_HFS DataDrive 63.7 GBdisk1s2 /dev/disk2 #: TYPE NAMESIZE IDENTIFIER 0: GUID_partition_scheme*6.0 TB disk2 1:EFI EFI 209.7 MB disk2s1 2: Apple_HFS rawKleimanMovies2.3 TB disk2s2 3: Apple_HFS TimeMachine 3.7 TB disk2s3 /dev/disk3 #: TYPE NAMESIZE IDENTIFIER 0: GUID_partition_scheme*5.8 GB disk3 1:EFI EFI 209.7 MB disk3s1 2: Apple_HFS OS X Install ESD5.5 GB disk3s2 /dev/disk4 #: TYPE NAMESIZE IDENTIFIER 0: GUID_partition_scheme*2.3 TB disk4 1:EFI EFI 209.7 MB disk4s1 2: Apple_HFS Kleiman Movies 2.3 TB disk4s2 /dev/disk6 #: TYPE NAMESIZE IDENTIFIER 0: GUID_partition_scheme*64.0 GBdisk6 1:EFI EFI 209.7 MB disk6s1 2: Apple_HFS Sierra10-12test 63.7 GBdisk6s2 Time machine has no trouble with the USB sticks, or the USB attached real drives. But it refuses to read from the image drive. Is there any way to make an image look "real enough" for time machine? --- Entertaining minecraft videos http://YouTube.com/keybounce ___ MacOSX-talk mailing list MacOSX-talk@omnigroup.com http://www.omnigroup.com/mailman/listinfo/macosx-talk
Getting time machine to backup a drive image
So if a hard drive is backed by a physical disk, time machine will back it up just fine. If it's backed up by an hdiutil mounted image, then it seems to refuse to back it up. In both cases, a /dev/*disk* entry has it, and it's an HFS+J drive. /dev/disk0 #: TYPE NAMESIZE IDENTIFIER 0: GUID_partition_scheme*1.0 TB disk0 1:EFI EFI 209.7 MB disk0s1 2: Apple_HFS Macintosh HD40.0 GBdisk0s2 3: Apple_Boot Recovery HD 650.0 MB disk0s3 4: Apple_HFS UserData832.8 GB disk0s4 5: Apple_HFS New Main126.1 GB disk0s5 6: Apple_Boot Recovery HD 650.0 MB disk0s6 /dev/disk1 #: TYPE NAMESIZE IDENTIFIER 0: GUID_partition_scheme*64.0 GBdisk1 1:EFI EFI 209.7 MB disk1s1 2: Apple_HFS DataDrive 63.7 GBdisk1s2 /dev/disk2 #: TYPE NAMESIZE IDENTIFIER 0: GUID_partition_scheme*6.0 TB disk2 1:EFI EFI 209.7 MB disk2s1 2: Apple_HFS rawKleimanMovies2.3 TB disk2s2 3: Apple_HFS TimeMachine 3.7 TB disk2s3 /dev/disk3 #: TYPE NAMESIZE IDENTIFIER 0: GUID_partition_scheme*5.8 GB disk3 1:EFI EFI 209.7 MB disk3s1 2: Apple_HFS OS X Install ESD5.5 GB disk3s2 /dev/disk4 #: TYPE NAMESIZE IDENTIFIER 0: GUID_partition_scheme*2.3 TB disk4 1:EFI EFI 209.7 MB disk4s1 2: Apple_HFS Kleiman Movies 2.3 TB disk4s2 /dev/disk6 #: TYPE NAMESIZE IDENTIFIER 0: GUID_partition_scheme*64.0 GBdisk6 1:EFI EFI 209.7 MB disk6s1 2: Apple_HFS Sierra10-12test 63.7 GBdisk6s2 Time machine has no trouble with the USB sticks, or the USB attached real drives. But it refuses to read from the image drive. Is there any way to make an image look "real enough" for time machine? --- Entertaining minecraft videos http://YouTube.com/keybounce ___ MacOSX-talk mailing list MacOSX-talk@omnigroup.com http://www.omnigroup.com/mailman/listinfo/macosx-talk
