Symantec Sytem Recovery 2011

Her's a partinfo from the APP.
partinfo.txt

Are these volumes GPT or MBR?

So this is a dell, right??   Make sure your RAID controller is supported, and if so, your device drivers are loaded properly.

Here is the process
http://www.symantec.com/connect/forums/raid-drivers-and-system-recovery-server-2011

could you be more specific please?
When you say it 'cant see local drives' do you mean they are not available to be backed up, or are do you mean they don't appear as a backup destination?

MBR

Not showing up as being available for backup in the define backup wizard,

The OS sees all the local disks fine ,but the APP does not.

The 2010 version of this product worked ,but I upgraded to the 2011 version and it doesn't see the local drive (C).

RAID 5 ,4X250 GB SATA ,Poweredge 840 ,PERC 5(not PERC 6) all firmware and drivers up to date.

I can see why some folks hate Symantec.

Going from one version to another on a supported OS shouldn't be such a pain in the @.

uninstall and potentially run the SRS removal tool from Symantec.  Re-install and try again, I've seen the Symantec dll files get messed up after an upgrade.

I've seen this too,but don't see any errors in the partinfo log.

http://www.symantec.com/business/support/index?page=content&id=TECH68773

There are two hidden partitions (one for Dell and another 2gb).both FAT.

I just wondering if those could be causing issues.

Well, everything appears to be done right, since you confirmed the drivers and supported O/S.  

Unless there is something buried in release notes saying FAT32 isn't supported ... then I would log this as a bug with symantec and get them to resolve the issue or ask for your money back, since this isn't operator error and you have a supported platform.

Looks like the SRS sees an invalid partition table, follow the KB listed, if it doesn't work I'd uninstall and re-install as this is what Symantec Tier 1 support will request

http://www.symantec.com/business/support/index?page=content&id=TECH68773

Looks like you've already seen the KB.  If the previous version was seeing the partitions and this one is not you may want to uninstall and ind install the latest version which I believe is 2013.

Don't suppose you've used a 3rd party tool to resize your partitions have you? (eg paragon, easus)

These servers often come with odd partitions and many resort to resizing, which can have effects on the partition tables etc, especially if the software you use is an older version that isn't officially compatible with the newer versions of Windows Server.

I suspect this may relate to the well known issue of partitions extending a little further than the BESR system expects, which normally results in having to reduce the partition size a little (as shown in the KBs noted above)
It's not really an option with the C drive however, as system drives don't link being messed around with so you're stuck trying to avoid a rebuild.

I actually shrank  the C part by 260 gigs and still no joy.

I have a copy of Retrospect that I had laying around as an eval and am testing it.

The head honcho of Symantec has said they've "stubbed their toe" on the newer releases of their BE products lately and this seems to be just another shining example.

The buy a good company like Powerquest and screw the product up.

Symantec probably did you a favor.  4K sectored drives aren't qualified for your RAID controller either (nor will they be).  Your data is at risk because of this, and it is causing you performance issues.

That's what Dell shipped from the factory.
They are even Dell branded.
WD RE 2's.

I did the fsutil thing and they popped up as 512e with 4096 physical sector.

Found the answer myself.

Just another reason to dislike Symantec!

How could they ship a product labeled 2011 when 4 k sector drives have been shipping for many years now?