Stalled on Active:Discovering Resources

[Erin1998]

I have a new install of BE 2014 on a 2012 R2 server.

I'm also using a SAS connected Promise eTrak 610s with 24TB of storage.

In doing a BTD job, it keeps stalling about about 1TB with an Active Discovering Resources alert.  I tried repairing the database as suggested in another post with this error message, with no luck.

Any other suggestions.

Thank you

[pkh]

Check that your disk is in the HCL below. http://www.symantec.com/docs/TECH214803 If it is not, test it with the utility below http://www.symantec.com/docs/TECH69107

[Erin1998]

It's not in the HCL, but it did pass all of the tests.

I've used this storage for years with 2010.

How big of a deal is it to not have anything else on the disk?  In 2010 this was never a big deal, but I have been reasding that the disk should only be used soley for the BE storage.  I am not currently doing this.

[pkh]

Other than the dedup folder, there is no requirement to dedicate the entire disk for disk storage.  However, this makes it more difficult to control space usage between the various applications using the disk.

[VJware]

Is this option "Preallocate disk space incrementally..." enabled in the disk storage properties ? If yes, disable it.

Have a look @ this KB - http://www.symantec.com/business/support/index?page=content&id=TECH224045

This usually happens if connection is lost to the storage. Check the event viewer for any relevant errors/warnings.

[Erin1998]

Thanks VJ,

I did find that link yesterday and it's pushing me toward ditching 2014 altogether and going back to 2010.

The preallocate disk space was disabled.

Something to be aware of, I did a successful backup job two weekends ago to this storage, but the Maximum file size was at 50GB.  I've changed it to 1TB to try and reduce the number of .bkf files that get created.  I read some of the pros and cons about going with larger allocation sizes, so decided to go bigger, but not to the max size.

Could the 1TB size be causing the new issues?  I normally have between 7-20TB of data to back up.

[VJware]

Based upon initial investigation, this error occurs if the communcation is lost to the disk storage (i.e. the storage becomes offline). So, moving back to BE 2010 may not really help if the communication between the media server and the storage gets broken.

I am not really sure if the 1TB size could be the issue or not, but definitely a try since you mentioned in the beginning, the backup keeps stalling around the 1TB mark. You could lower this setting and retry.