BE2010 Dedupe to SAN - final error 0x2000040d S_TF_NO_TAPE_PRESENT

[Michael_Gray1]

Running on Windows Server 03 R2 x64 SP2

Started late last week sporadically, now I can't run any backup jobs.

Dedupe runs to a drive that is mapped to the SAN, it's been working for months w/o this error.

Run all available updates.

Any troubleshooting advice would be great.  I'm going to continue to research online.

THANKS!!!!

[Sush---]

May I know what is the exact version of Backup Exec that you are using?? Is it BE 2010 R1 or R2...??

This issue is resolved in Backup Exec 2010 R2 Hotfix 138226.

Refer to the following technote for more details

http://www.symantec.com/docs/TECH138311 : S_TF_NO_TAPE_PRESENT reported on backup to deduplication folder

Thanks,

-Sush...

[Michael_Gray1]

Thanks for the reply.  I think I'm running R1, splash screen and help don't show R2

Version 13.0 Rev 2896(64-bit)

Is there an upgrade path to R2?

-Michael

[Sush---]

You can download Backup Exec 2010 R2 from the following link:

https://www4.symantec.com/Vrt/offer?a_id=93355

Download the 3GB ISO file which has the complete software. After the download run the installation and Backup Exec will upgrade from R1 to R2. Also you do not have to re-enter the license as the same license of BE 2010 R1 will be used and there is no need to new licenses.

After the installation is completed run the Live update so install the SP1 and few Hot fixes released after that.

Refer to technote " http://www.symantec.com/docs/TECH138264 : Step By Step guide to download and Install Backup Exec 2010 R2 "

Thanks,

-Sush...

[Michael_Gray1]

Upgraded to R2 ran live update but still getting the same error. 

[Michael_Gray1 · Accepted solution]

from

http://esd.element5.com/publisher/50364/proxy.cgi/62438//connect/forums/stfnotapepresent-2010-dedupl...

After the issue was escalated to Symantec Level 3 support they were able to quickly establish root cause. 

ROOT CAUSE:  Our configuration was configured to split up the DeDupe folder and DeDupe database onto different volumes.  Although the DeDupe volume had more than 14GB of free space it wasn't enough for the Postgress log files / background operations to perform a specific operation (required temp space margin).  We added another 50GB of space to the volume and backup jobs began working again.