To troubleshoot TSM Errors and Codes started with RC= and ANS/ANE ?

I am looking for best practice to be followed  to understand TSM -Server/Client Error Messages and RC Codes

Like ANS4174E and RC=-1 or RC=4379..there are many messages and code needs to be looked further for appropriate solution /fixed @ Windows/VMware level

Recently error i am facing is  VM Backup is failed due to
ANS4174E Full VM backup of VMware Virtual Machine 'VMName' failed with RC=4379 mode=Incremental Forever - Incremental, target node name='nodename', data mover node name='movername

So how can we fix such issues by following best practise  and check marks.
patronTechnical consultant Asked:
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.

Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization ConsultantCommented:
Discuss the error messages with the back vendor.
those code errors are produced by TSM client, which uses vmware API to talk to vCenter.
RC=-1 and RC=4379 are among the most recurrent errors but their correnspondence is not unique (it may depend by many factors).

You should look deeper into the error log, which by default (unless changed into dsm_xxx.opt file) is in  path:
C:\Program files\tivoli\tsm\baclient

You need to understand that while TSM is alerting those errors it may not be itself the cause of the problem: it is usually something wrong either on vmware environment or the guest VM itself.
So I usually track the error by looking at error and see explanation into dsmxxx.log.

Then I go an check if:
1. datastore has sufficient space to place the snapshot (make enough space to place the temporary snapshot and pay attention for bigger VM)
2. guest vm partition disk is not full (free space on C:\ partition)
3. guest vm has got no windows update pending (reboot vm guest)

90% of issues are above the 3 mentioned.

 hope this helps

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
patronTechnical consultant Author Commented:
Great help -Thanks, yes , we are following the same and further looking more into dsmsched and dsmerror file

need to understand if there are any more best practise  like for service   to be verified  or any more prechecks as you mentioned above and further vendor can be involved
Get Blueprints for Increased Customer Retention

The IT Service Excellence Tool Kit has best practices to keep your clients happy and business booming. Inside, you’ll find everything you need to increase client satisfaction and retention, become more competitive, and increase your overall success.

you may want to read this:

although please note that it is not very accurate (diagnoses as i said are not always unique but might depends on something else): you need to map it nto your environment.

My answer was helpful
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
TSM Tivoli Storage Manager

From novice to tech pro — start learning today.