Entervault 2007 sp5 FSA can not retrieve file from nbu to netapp

now i have a problem with EV 2007 and NetApp Filer , my environment as following

EV and NBU install on the same server : Windows 2003 Enterprice (32bit)

Enterprise Vault Version : EV 2007 SP5

NetBackup : NBU 6.5 MP5

NetApp OnTap : 7.2.5

Description :

I use enterprise vault 2007 FSA to archive file on Netapp storage and use NBU to migrate arcived file to Tape , and leave shortcut (placeholder) on the netapp filer . now I try to retrieve files from shortcut but failed , someone can help me ? thanks

is there any errors on the EV Server?
How big is the file? do any files retrieve or do they all fail?
when you say "failed" are you actually seeing any errors? if you wait a while, does the item get retrieved?
Do you see the retrieval request being made in NBU?
has it ever worked?

you may want to get a dtrace of StorageOfflineOpns and see if it gives any clues

But from looking at this log, and then looking at xbsa log i can see that you are creating hundreds of migration jobs. You are migrating lots of cab files after a very short time period, and that has been known to cause resource issues in the past because of the number of jobs backed up. This isn't a very good strategy unless you are never going to recall those files again.

When you look in NBU activity monitor are lots of jobs listed? Can you retry the failed ones?

Does this work correctly when there are a low number of jobs, or does it ALWAYS work with FSAUtility and fail with a shortcut copy?

when I tried to copy the archived file to another location , I can't find any restore job in nbu activity monitor . so i failed with copy short cut to another location .

the log you see is i use fsautiltity to restore archived file and it is strange , When I use fsautility to restore , i can only restore one file in the directoty , but in nbu activity monitor i could find there are restore jobs running , and some job was failed . or you can tell me how to do , thanks !!!

Yes, there were a fair few bugs, but If I recall some of the code to clear up the error code '3' which was due to open file handles was already included by 6.5.5 and the other stuff for the time bracketting appears to be there because the time brackets are fairly small in the logs.

Anyway, Arthur, I think you also need to provide a trace of what happens when you copy a file, but to be honest you are still suffering from the huge amount of activity that you are pushing through to NBU and that is only going to change with a modification to your migration strategy. How many jobs are you seeing queued up at a time?

Can you also find out which version of XBSA.dll and NBUMigrator.dll you are using on the EV server?

You should be raising a support call at this point though - the question is, should that be with EV, or NBU. You need to check your NBU activity monitor and look at the failures (and check if they are persistent failures) to make that decision.

Well the good news is that you are running the versions of XBSA.dll and NBUMigrator.dll which are newer than the ones containing the bugs Rob and myself were talking about. However that doesn't mean you can't exhaust the system of resources.

Fundamentally there shouldn't be any difference between how the items are being recalled via FSAUtility or by the placeholder service. Both methods will be using storageofflineopns to retrieve the file, and in both cases the vault service account should be the account used.

I checked through the traces again to see if there was anything else that could tell us what is going wrong, but all i can see is this:

See if you can restore this backup image - it should give you /H/Enterprise Vault Stores/VT1 Ptn1/2012/08/13/Collection133627.CAB

The same log contains a successful restore (issued on its own), while this failure happens at exactly the same millisecond as another thread, which is also failing to restore. So I can see *some* things are successfully restored.

I think your errors are likely coming from the NBU side though, so this is where you should consider raising the support case.