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.

03/29/2011 12:20 PM

Thanks for that link

I have however looked in great detail at the Pondini posts and i have the Buddy widget installed. it is useful.

Pondini seems to be the Time Machine guru but of course with little experience of Time Machine operating with Drobo.

I have wired connections not wireless from the PowerMac. The wireless connection does however work just as well are the wired connection for my laptop for Time Machine backups to Drobo.

My own feeling is that the problem is related to the number of files within one Time Machine backup BUT it is not a Time Machine issue - rather it is a Drobo issue. BUT of course I am probably wrong. It is, however, strange that the stall always occurs around the point - the same file capacity on the Drobo - the same stage in the process - towards the end of the backup.

Questions I ask myself include: Is the Drobo indexing as well as Time Machine? How does it deal with duplicate files? Is there a process in place to deal with duplicates which is self defeating - causing too much analysis of the content? Of course these could be ridiculous thoughts.

Something eventually causes the whole system (Time Machine/Drobo/PowerMac/ MacOS) to move at a snails pace. Activity Monitor would suggest that it isn't processor activity, nor is it disc activity nor network activity. What I ask is going on inside the Drobo? It would appear also not to be Spotlight. It is most strange. Unfortunately I don't have the diagnostic software to do an objective analysis.

Let me asure you, however, I do want it to work. As far as I am concerned Drobo is a good concept - but I may just have to give up eventually as I have no more ideas.

Best wishes


04/07/2011 02:44 AM

It seems that I have exhausted all sources of help on this issue and so I have been forced to assume that the Drobo FS does not work properly with Time Machine and my system configuration, the details of which are reported elsewhere.

As I have said before, Time Machine works perfectly with my configuration which includes two Sonnet Fusion Fusion D500P arrays each populated with 5 x 1TB enterprise quality Seagate drives. They have been used without issue now for two years. Time Machine backs up onto one of the Sonnet Fusion Fusion D500P systems exactly what I have been trying for nearly 3 months to back up onto the Drobo FS - with no success.

Using my system, Time Machine thus backs up to the Sonnet array, but it does not back up to the Drobo FS. This would suggest to me that the Drobo FS, the discs contained within the Drobo, or the LAN including the switch/router is the issue. Alternatively there is some Time Machine/Drobo FS/Mac OS 10.5.8 incompatibility which has not been identified yet by anyone anywhere.

The LAN/switch/router seems to work with everything else including to backup other smaller capacity computers onto the Drobo using Time Machine. The LAN/switch/router seems thus to be working.

I have tested the discs and they seem to pass the tests. Drobo Dashboard also indicates that the Drobo FS is healthy.

I have spent three months on this process and my conclusion is that Time Machine does not work with Drobo FS for all systems.

I have given up with Time Machine to Drobo for my system. It just does not work! I am now in the process of using SuperDuper and DroboCopy to provide me with a different form of backup on the Drobo FS for my data from what I required. I will continue to deploy the Sonnet array for my Time Machine backups.

For large quantities of data DroboCopy is very slow but it gets there. SuperDuper is perhaps faster but of course with a different file format outcome on the Drobo FS.

Buying the Drobo FS has been an expensive mistake for me but I will continue to deploy it as and how it seems capable.


04/11/2011 08:37 AM

Update

I have now made either DroboCopy backups or SuperDuper copies on the Drobo FS of all five discs of one of my Sonnet arrays. It is slow and so I am only updating on a monthly schedule. Slowness must be due to the huge number of files.

I have also created a Time Machine backup on the Drobo FS for an iMac, a MacBook Pro and my PowerMac albeit for my PowerMac it is a very selective subset of the data. The backup process has failed consistently in the past on the PowerMac when I have backed up several TB using Time Machine.

That is where I am leaving it at the moment. I won't stress the Drobo any further so that I can remain unstressed with it.

Best wishes


04/11/2011 08:41 AM

Dear Support

I have, however, one other question.

SInce I obtained the Drobo FS Mail Alerts have not worked on my PowerMac. I have not tried it on my laptop or iMac. When I set up Mail Alerts and 'Send a Test Email' I get the test email but thereafter no email alerts. When of course I disable email alerts I get the normal alerts on my screen.

Thought I would 'alert' you to another possible problem with Drobo and my PowerMac. :-(

Best wishes


04/17/2011 09:38 AM

Dear Support

The backup I made using Time Machine for the selective subset of data on my Power Mac worked well up until yesterday. It has failed now and the sparse bundle won't mount. Clearly another issue with Time Machine, the Drobo FS or some other element in the system equation. Time Machine cannot mount the backup and I cannot get access to it. Any help would be appreciated.

I include diagnostics file DroboDiag_20110417_1737.log

Best wishes


04/17/2011 12:17 PM

Update

A restart of the Drobo FS fixed the Time Machine backup which wasn't mounting.


04/20/2011 09:51 AM

Communication from Drobo Support asking if the slowness issue had been resolved.


4/29/2011 05:33 AM

As explained previously, the issue was not resolved. I just had to give up with regard to using Time Machine to create the backup I required. Drobo Support couldn't help and there was nothing else recorded anywhere on the online forums which resolved the issue.

I am now using Drobo successfully with the same computers but I am not requiring as demanding a Time Machine backup. Clearly the Drobo or Time Machine couldn't deal with my requirements and so I just had to request what was possible.

I am using a mix of Time Machine, DroboCopy and SuperDuper backups to achieve approximately what I desired. It is disappointing but I cannot afford to spend any more time on a problem for which no solutions are forthcoming.

Best wishes


04/29/2011 09:51 AM

Drobo Support advised me to update firmware and dashboard - which I of course had already done and reported. I was advised that I should apply these updates although they did not address Time Machine issues because Drobo Support had not experienced any problems with Time Machine.

I was advised that my cases would now be closed.


04/29/2011 12:12 PM

Thank you for your comments and suggestions.

I had already updated all related firmware and software when released.

Regretfully, I find your comment "we have not experienced any problems" leaves me perplexed as I have been reporting problems for three months. Believe me they do exist in my case. I do perceive it to be a rather unfortunate and mildly patronising comment on the closure of what has to be classed as an unsuccessful support request from my perspective.

Thank you for whatever effort you have put in on my behalf.

Best wishes