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/16/2011 03:15 PM

Dear SupportI should correct what I said in the earlier ticket about Time Machine crashing. In fact what happened was a loss of contact between Drobo and the computer. I suspect that the cause was my attempt to set up a new share and a new DroboCopy whilst the TimeMachine backup was in progress. Time Machine did not crash.Best wishes


02/17/2011 02:28 AM

Dear Support

Please note that the details of my problem starts with ticket:

AAAAAAA

That problem contrary to the status of that ticket on your system is not solved. I started a new ticket on advice because I could no longer upload attachments. The problem is continued on the tickets below.

BBBBBBBB
CCCCCC

The situation after more than one month has not been resolved despite having been supplied with a new Drobo and a new power supply and having returned two Seagate discs.

Basically the problem is that I cannot complete an initial Time Machine backup for my Power Mac system. My other Macs on the LAN have Time Machine backups but they only have several hundred Giga Bytes of storage. My Power Mac has TBs.

Best wishes


02/17/2011 03:49 AM

Dear Support

Thank you for your advice this morning with respect to my telephone call. I enclose screen shots as requested.

Unfortunately I will have to open another ticket for some of the screen shots as I have once again run out upload capacity on your system


02/18/2011 03:06 AM

Dear Support

After my last failed backup which took days and days as previously reported I decided to start it again. After many hours (~18) of 'Preparing' according to the Time Machine preferences window it started a backup of 2.9GB which indicated that 398GB of the previous backup was still recognized.

The backup continued for a number of hours very slowly but nevertheless it proceeded until it reached 'backing up 2.8GB of 2.9GB' as described in the Time Machine Preferences window. It then stuck! After a few hours I stopped the backup and powered down Drobo and my computer over-night. I felt that no further progress was going to be made with the backup.

Best wishes


02/20/2011 08:13 AM

Response from Drobo Support suggested that if Time Machine backups continue to cause difficulties, I should try following:

1) Stop Time Machine.
2) Delete all in progress folders
3) Empty trash if necessary
4) Start a new Time Machine back up.

Apparently in Progress backups might considerably slow down the backup process, which is a known Time Machine issue, and unfortunately not completely solved as of yet.


02/18/2011 03:16 AM

Just to tick another couple of boxes I have just carried out the process as defined in:
http://support.datarobotics.com/app/answers/detail/a_id/167

I have started Time Machine again with all fingers crossed.

Incidently Spotlight has been prevented from searching any of the Drobo shares.

Best wishes


02/21/2011 03:42 AM

Thank you for your response.

I have done as requested and a Time machine backup has been started again without the old in-progress folder. Trash was emptied.

I will provide an update when Time Machine permits. It is currently 'Preparing'.

Please note that this issue was opened on ticket

XXXXXXX

and was continued on tickets

WWWW
YYYYY
ZZZZZ


02/17/2011 06:59 AM

On this date I was informed through the online Support Facility that a Tier 3 Support Engineer was taking over the case. I had been referred to level 3 support after I had telephonic communication with a very helpful individual who told me that as far as he could see what I was doing should work. He was escalating the issue to a higher level for that reason. That sounded hopeful to me.


02/19/2011 12:08 PM

Dear Support

Ongoing story.

Time Machine took several hours to decide that approx 4GB still had to be backed up. 2GB was backed up with impressive speed then it stalled. It basically looked as though the process was stuck. Looked like lots of incoming data 100sKB from the Drobo but little outgoing data. I stopped the process.

To check if there was an unreadable file on the source drive I transferred all the data from the source drive to an internal drive on my Mac. Not a problem there!

Today I started the process again. After a few hours Time Machine decided that 4GB had to be transferred. Less impressively with respect to speed 2.6GB was transferred. The system now looks to be stuck again. I will leave it for another 2 or 3 hours but if there is no movement I will stop it.

Wastebasket was emptied and Spotlight being managed so that so undue work there.

Current Diagnostics file attached.


02/23/2011 02:11 PM

Having trashed the in-progess file from the last failed update and emptied the trash I restarted the Time Machine backup. 405.9GB to be backed up at this point which represents most of the content of a disc on one of my Sonnet arrays.

I can't remember when I started it. I think it was approx 60 hours ago. At this point only 45.9GB has been backed up. At this speed another 500 hours should complete the process.

Realistically I cannot allow that. If it has not speeded up after another 24 hours I will stop the process and wait for Drobo support advice again. :-(