Symantec system recovery - i get the same error in so many servers: A test that safeguards the integrity...

Hi, This is my scenario:
 
1. i have so many customers with symantec system recovery 2011 or 2013
 
2. so many of my customers are experiencing that issue. the error message is the same ever:
 
A test that safeguards the integrity of the program failed unexpectedly. PRECONDITION failed, UMResourcewin::GetLoad:
 
.\UmResourceWin.cpp(347): mResourceHandle !=NULL
 
 
 
3. i've asked into forums, symantec enterprise support, i've reinstalled, deleted and recreate the jobs, defrag my partitions, chkdsk my disks, but nothing works
 
 
 
4. i think that can be something with vss, but i don't know!
 
 
 
please, help me, so many of my customer have not backup, i'm responsible for that information.
IMG-19092013-113451.png
controlitAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Haresh NikumbhSr. Tech leadCommented:
I don't think so its VSS errors cause VSS errors event can be found on the Application event logs..

anyway you if you still want to verify status for vss writers then run below command

vssadmin list writers ( need to run on command prompt)

if you see all writers in the stable state that means your Writers are healthy ..

the error message which you getting for this i will suggest first verify if you have file system corruption on the disk

that can be verify running check disk command chkdsk c:\

if any corruption found then need to fix that before executing backup job

2nd check is verify if this server has shadow copies configure..

right click on the volume and verify shadow coies enable .. if yes then that need to disable too
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Paul SolovyovskySenior IT AdvisorCommented:
what block size are the drives?  Keep in mind that SRS doesn't support 4k block size so something to check
0
pgm554Commented:
2013 should support 4k.but anything below just won't.

It can be checked by doing a fsuitl

http://www.symantec.com/business/support/index?page=content&id=TECH143704
0
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

Paul SolovyovskySenior IT AdvisorCommented:
If you take a look at the technote it not supported by even 2013 as a source

s seen in the example above, the BYTES PER SECTOR is 4096, or 4kb. The current versions of Backup Exec System Recovery (BESR) or Symantec System Recovery (SSR) do not support 4096 (4kb) sector size disks as a backup source (i.e. the drive being backed up). These drives can be used as a backup destination (note limitations mentioned below).
0
pgm554Commented:
Really?

Why would they ship a product that won't support 99.9% of all the drives shipping these days?

That's moronic,but then again it is Symantec.
0
Paul SolovyovskySenior IT AdvisorCommented:
Don't shoot the messenger..
0
pgm554Commented:
I actually just had the 4k issue about 2 weeks ago on a server 2008 Poweredge system.

Have switched over to Retrospect 8.2 and am testing.

Not quite as pretty a GUI,but it seems to work.

Unfortunately,between backup software and AV,the QA just sucks!
0
controlitAuthor Commented:
Hi,
thanks for the replies
i have some customers working good with symantec system recovery, the backups jobs works good, all of it customer have in their disks, the cluster size 4kb.
so, i don't think that is the main cause for this issue.

anything help?

thanks.
0
pgm554Commented:
The head honcho of Symantec openly admitted they "stubbed their toe" on the latest releases of their product,but they were gonna do better.

http://www.theregister.co.uk/2013/05/09/symantec_q4_fy2013/

And I'm from the government and I'm here to help!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Server Software

From novice to tech pro — start learning today.