I have been using BMFU for a long time without problems. I'm running
BMFU on a Droboshare connected a Drobo v2. The Drobo has 4 x 1 TB
drives and is formated (thin provisioning) as 8TB, one single
partition. I'm backing up a single Mac using TM.
Last night I upgraded to 10.6.3. During the following TimeMachine
backup, the max size of my sparse bundle was changed from 550GB to
8TB.
.....
Attempting to mount network destination using URL:
afp://;AUTH=No%20User%20Authent@DroboCapsule._afpovertcp._tcp.local/DroboCapsule
Mounted network destination using URL:
afp://;AUTH=No%20User%20Authent@DroboCapsule._afpovertcp._tcp.local/DroboCapsule
Warning: Destination /Volumes/DroboCapsule does not support TM Lock
Stealing
Warning: Destination /Volumes/DroboCapsule does not support Server
Reply Cache
Resizing backup disk image from 550.4 GB to 8191.6 GB
QUICKCHECK ONLY; FILESYSTEM CLEAN
Disk image /Volumes/DroboCapsule/MacBook_001f5be7e5f4.sparsebundle
mounted at: /Volumes/Backup of macbook
Backing up to: /Volumes/Backup of macbook/Backups.backupdb
No pre-backup thinning needed: 305.4 MB requested (including padding),
7.05 TB available
Copied 16442 files (222.3 MB) from volume Macintosh HD.
No pre-backup thinning needed: 100.0 MB requested (including padding),
7.05 TB available
........
This is bad because I don't want my TM backups to occupy all space on
my Drobo and it will ultimately fail as my Drobo only has 2.7TB of
disk space when using the 4 x 1TB.
I've then connected the Drobo directly to the Mac and changed back the
max size of the sparse bundle to 550GB with:
hdiutil resize -size 550g /Volumes/Drobo/DroboCapsule/
MacBook_xxxxxxxxxx.sparsebundle
But on the next TM backup, the max size of the sparse bundle is again
changed to 8TB.
Is someone else experimenting the same issue? any solution?
While I don't think the problem is related to BMFU itself, I wonder if
there is something specific about our afp server (not supported by
Apple) which could make TM acts like this.
Thanks for any help.
Cedric
--
You received this message because you are subscribed to the Google Groups "backmyfruitup" group.
To post to this group, send email to backmy...@googlegroups.com.
To unsubscribe from this group, send email to backmyfruitu...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/backmyfruitup?hl=en.
I have recently switched to a Mac MIni server and so now have the
Drobo connected to the Mac Mini (no Droboshare). I kept the
Drobocapsule sparse images as the TM backup.
I have just had a look at the logs and have exactly the same issue.
The sparsebundle was originally set to 750GB. So this looks like a Mac
issue rather than BMFU.
Starting standard backup
Attempting to mount network destination using URL:
afp://office@jamserver._afpovertcp._tcp.local/DroboCapsule
Mounted network destination using URL: afp://office@jamserver._afpovertcp._tcp.local/DroboCapsule
Warning: Destination /Volumes/DroboCapsule does not support TM Lock
Stealing
Running backup verification
QUICKCHECK ONLY; FILESYSTEM CLEAN
Backup verification passed!
Resizing backup disk image from 750.0 GB to 8191.6 GB
QUICKCHECK ONLY; FILESYSTEM CLEAN
Disk image /Volumes/DroboCapsule/Office_d49a20d053b9.sparsebundle
mounted at: /Volumes/Backup of Office
Backing up to: /Volumes/Backup of Office/Backups.backupdb
Ownership is disabled on the backup destination volume. Enabling.
Detected system migration from: /Volumes/Office Clone orig
Backup content size: 199.5 GB excluded items size: 1.4 GB for volume
Office HD
Backup content size: 427.0 MB excluded items size: 480 KB for volume
Office Workspace
No pre-backup thinning needed: 238.21 GB requested (including
padding), 7.71 TB available
Waiting for index to be ready (101)
I tried "hdiutil resize" a 2nd time with more success:
1) connected the Drobo directly to the Mac with the firewire cable
2) ran: "hdiutil resize -size 550g /Volumes/Drobo/DroboCapsule/
MacBook_xxxxxxxxxx.sparsebundle" -> the max size of the sparse bundle
went down from 8TB to 550GB.
3) ran Disk Utility and "verified" Drobo, as well as the sparse bundle
4) reconnected the Drobo to DroboShare
5 days and a lot of TM backups later, the max size of the sparse
bundle is still 550GB.
Comparing with my original attempt, the only extra step I took was
running Disk Utility while the Drobo was connected to the Mac.
Solution or just pure luck? I'd be interested in hearing feedback from
others with the same issue.
Cedric
> > backmyfruitu...@googlegroups.com<backmyfruitup%2Bunsubscribe@goog legroups.com>
I have repeatedly tried the hdiutil resize without success. The
sparsebundle is set to the desired size, but then resized again by TM.
I have now tried your solution with the Disk Util/Verify option but no
success on the first try. I will have another go and report back. Off
to Tango now!
Mike
Yes, horrible, devious, wrong on many levels. But it would be
something I'd love to try if I was home right now just to see how it
breaks.
- Toby
> --
> You received this message because you are subscribed to the Google Groups "backmyfruitup" group.
> To post to this group, send email to backmy...@googlegroups.com.
> To unsubscribe from this group, send email to backmyfruitu...@googlegroups.com.