Drobo updating boot support partitions

I believe this was due to a system reinstall and not the fault of the Drobo.Prior to reinstalling I was made aware of the fact that the Drobo, like virtually all expandable mass-storage devices, "lies" to the computer about its disk size.In my case, Time Machine would be led to believe I have a 2.0 TB disk even though my current Drobo configuration is only 1.35 TB.Once Time Machine had dumped 1.35 TB of data on my disk, it would not know to start pruning old backups to make room for new ones because it would believe that it still has another 650 GB of free space!

If you create a volume that's larger than your "actual" storage space3, you'll get one volume that reports this increased size to the Finder and everything else. 24, 2008: I've long since repurposed my Drobo after running into the same problem a commenter below had: the data backs up but doesn't show itself as a backup in Time Machine.There's a work-around, but it isn't a case of "it just works" at all, so you may want to avoid using your Drobo for Time Machine backups at all. A few days ago I reformatted my Drobo because it was acting up.The easiest way to create a sparseimage that will work with Time Machine is to use an Automator script called Time Tamer.Time Tamer will create a sparseimage file on your Drobo sized that's twice as large as your boot disk. If you're comfortable using the Terminal, and you'd like to customize the size of your sparseimage file (as well as the name), you can do so (originally posted in my comment below) with this command: In this script, "1024g" is the maximum file size (1024g = 1024 GB = 1.0 TB), "Time Machine Backup" is the name of the disk as it will appear when mounted during backups, "/Volumes/Mimzy/" is the path to my Drobo, "Bunny" is the name of my computer ( or via the System Profiler application.

Leave a Reply