Posts Related to Use of Drobo FS in my Personal Context

  • : Function ereg() is deprecated in /home/terry/public_html/includes/file.inc on line 647.
  • : Function ereg() is deprecated in /home/terry/public_html/includes/file.inc on line 647.
  • : Function ereg() is deprecated in /home/terry/public_html/includes/file.inc on line 647.
  • : Function ereg() is deprecated in /home/terry/public_html/includes/file.inc on line 647.
  • : Function ereg() is deprecated in /home/terry/public_html/includes/file.inc on line 647.
  • : Function ereg() is deprecated in /home/terry/public_html/includes/file.inc on line 647.
  • : Function ereg() is deprecated in /home/terry/public_html/includes/file.inc on line 647.
  • : Function ereg() is deprecated in /home/terry/public_html/includes/file.inc on line 647.
  • : Function ereg() is deprecated in /home/terry/public_html/includes/file.inc on line 647.
  • : Function ereg() is deprecated in /home/terry/public_html/includes/file.inc on line 647.
  • warning: Parameter 1 to theme_field() expected to be a reference, value given in /home/terry/public_html/includes/theme.inc on line 170.
  • warning: Parameter 1 to theme_field() expected to be a reference, value given in /home/terry/public_html/includes/theme.inc on line 170.
  • warning: Parameter 1 to theme_field() expected to be a reference, value given in /home/terry/public_html/includes/theme.inc on line 170.
  • warning: Parameter 1 to theme_field() expected to be a reference, value given in /home/terry/public_html/includes/theme.inc on line 170.
  • warning: Parameter 1 to theme_field() expected to be a reference, value given in /home/terry/public_html/includes/theme.inc on line 170.
  • warning: Parameter 1 to theme_field() expected to be a reference, value given in /home/terry/public_html/includes/theme.inc on line 170.
  • warning: Parameter 1 to theme_field() expected to be a reference, value given in /home/terry/public_html/includes/theme.inc on line 170.
  • warning: Parameter 1 to theme_field() expected to be a reference, value given in /home/terry/public_html/includes/theme.inc on line 170.
  • warning: Parameter 1 to theme_field() expected to be a reference, value given in /home/terry/public_html/includes/theme.inc on line 170.
  • warning: Parameter 1 to theme_field() expected to be a reference, value given in /home/terry/public_html/includes/theme.inc on line 170.

02/24/2011 02:51 AM

12 hours later (approx) and Time machine has backed up 53.9GB of 405.9GB. Less than 1GB per hour.


02/24/2011 02:55 AM

I have also stopped my automatic mobileme sync process from happening until I restart the process again manually.


02/24/2011 02:56 AM

All drives attached to my computer and the Drobo drives are now set never to spin down.


02/24/2011 09:39 AM

Response from Drobo Tier 3 Support requested that I clarify the version of Drobo Dashboard I am using.

Also I was asked:

if another backup app exhibited the same problem (eg SuperDuper, DroboCopy, etc)

if this same problem occurred if I directly connected Drobo to my Mac. Apparently the diagnostics did not indicate a problem with the switch.

To try running Time Machine from an Intel based Mac


02/24/2011 11:11 AM

Many thanks for your attention

I must say I will be very grateful for your assistance as this problem is causing me more than a little frustration.

All the notes in the earlier tickets contain information pertinent to this case not just the attachments. The reason I had to open additional tickets was due to the limitation on space for more attachments.

In relation to your questions I provide the following information.

"Can you clarify the version of Drobo Dashboard you are using" 1.7.3 [1.7.30095]

" Does another backup app exhibit the same problem (superduper, carbon copy cloner, drobocopy)" I use both SupeDuper and DroboCopy but I only use DroboCopy to back-up to the Drobo. There is not an issue with it. Backup with DroboCopy is suitably fast and effective. You will see from the attachment (DroboCopy.jpg) that I have 10 DroboCopy processes scheduled. They work perfectly.

"Does this same problem occur if you directly connect Drobo to your Mac ( the diags did not indicate a problem with the switch, I would just like to eliminate some of these other variables)." I did have the Drobo attached directly initially but the speed is perfectly satisfactory through the switch for straight transfers from my computer to the Drobo. It is only through Time Machine that the transfer speed is desperately slow. I have done various tests transferring several hundred gigabytes and the transfer rate is OK through the switch. I am really quite confident about that.

"Can you try running Time Machine from an Intel based Mac" Time Machine is running from my iMac which is a 2.66GHz Intel Core 2 Duo running under 10.6.6. The Time Machine backup is not a problem there. It also runs well from my MacBook Pro which is Intel-based. BUT Time Machine ran well enough on my machine when I was hitting it with large quantities of data on earlier iterations of the backup process. As you can see from earlier notes I started with a backup of some of one disc, then added another disc, then another, then another and so on. My PewerMac is used as a server as well and so it has 2 x 5TB Sonnet arrays attached. The problem has arisen twice after approximately 2.5TB was on the Drobo. I have started the whole process twice and that takes a long time. Not a day but many days each time. I cannot tell how an Intel-based system would change the situation without attaching one of my Sonnet arrays to my MacBook Pro and starting the whole process again - many days of work - as the problem only arises when TBs of data are transferred. The Intel Macs I have which are using TimeMachine are only transferring 100s of GigaBytes at the moment.

Thank you

I hope the above helps - it is a bit of a ramble.


02/24/2011 02:26 PM

The time stamp on this message will show that the backup has almost stalled now. 54.8GB of 405.9GB has been backed up. Only 0.9GB backed up since I last reported. I will leave it running for another 12 hours with fingers crossed.


02/25/2011 01:30 AM

Dear Drobo Support

In the last 10 hours a further 0.9GB has been added to the backup. I think that is is reasonable to state that the backup has stalled. I will now stop the process with 55.7GB of 405.9GB backed up from the disc last added to the backup process (R4 Video 2).

I have a diagnostics file (DroboDiag_20110225_0926.log) which unfortunately I cannot add to this ticket due to space considerations again. Let me know if it is required.

The Drobo Dashboard indicates that there is 3.09TB of used space and 4.12TB of Free Space.

Best wishes


02/25/2011 02:12 AM

02/25/2011 02:12 AM
I know from previous experience that stopping Time Machine after a stall takes either many hours or for ever and so through Time Machine preferences I selected 'stop backing up' but then after a few minutes I restarted the Drobo from the Drobo Dashboard.

The Drobo did not like that. It did not come up again automatically. As I have the Drobo in my loft I then had to scale the heights and check to see what had happened. All lights were yellow down the side and along the bottom all the lights were blue. I toggled the on/off switch and after quite a few minutes it resolved its issue and it reached its normal stable state with green lights all down the side and the blue lights reflecting the disc capacity used/available.

I have another diagnostic file which I can supply taken just after the restart. (DroboDiag_20110225_0954.log) which I can supply if required.

The Drobo is now backing up the Intel iMac and it is available to the PowerMac.

I have given up on the Drobo for backing up my Power Mac and I have reverted to my former Time machine backup process for the Power Mac whereby the backup is made on another 5TB Sonnet array. There are no issues with that software/hardware combination and there are also many fewer exclusions on that backup process than with what I am trying to do with the Drobo. ie much more is being backed up to the Sonnet than to the Drobo.

The fundamental difference may of course be that being network based the backup is in sparsebundle format whereas on the Sonnet it is not.

I hope that helps.

Best wishes

Terry


03/01/2011 01:54 PM

I have deleted the Time Machine Share on the Drobo for the Power Mac and I have created a new one. I started the whole backup again 24 hours ago but this time not one disc at a time. The whole backup is being created in one step. Should take days.


03/02/2011 04:21 PM

In a response from Drobo Support I was given a few pointers based on what others had reported on the Internet. For example:

- quitting the finder
- deleting the "in progress" folder
- time machine switched to OFF before launching interface (i.e.: before entering time machine)
- unmount all other external volumes that are not participating in Time Machine