cancel
Showing results for 
Search instead for 
Did you mean: 

FSAUtility - 'already queued'

nathan_trueswif
Level 2
Partner Certified

Hello All,

Currently have EV FSA 10.0.4 running on Windows 2008 R2 archiving files from a Celerra presented via CIFS. We are attempting to recall hundreds of GB / many thousands of placeholders using FSAutility as a test.

The process appears to complete but a closer examination shows that many of the placeholders are not recalled. There does not appear to be any pattern, it can impact small and large files alike and is not confined to one area of the directory structure. If another recall is requested using FSAutility it advises that the recalls are already queued in the XML log:

<ErrorCode>Already queued</ErrorCode>

Even retrying after an extended period of hours / days still results in the same 'already queued' notification. If I manuallyrecall the file by accessing it will retrieve without any apparent issues. The event logs and Dtrace do not suggest any problems.

I wondered if a recall limit was being hit but given this is a Celerra the suggested registry tweaks for Windows based file servers do not apply. Another posting on the forum (http://www.symantec.com/connect/forums/fsa-recalllimitmaxrecalls-emc-celerra) suggests there is no equivlant override for Celerra.

Is there any way to determine what is in the queue FSAUtility is refererring to and is anyone aware of any common causes of the queuing?

 

Thanks,

Nathan

 

3 REPLIES 3

jandersen1
Level 4
Partner Accredited

Hi

Did you ever solve this problem?

VirgilDobos
Moderator
Moderator
Partner    VIP    Accredited Certified

Hi mates,

Have you tried using -f (force) option? This forces FSAUtility to restore the files when placeholders or files of the same name already exist. The utility first deletes the existing placeholders or files and then restores the files.

--Virgil

Hi,

The 'already queued' typically means there is an issue with the restore and the EvFileSvrArcMngr process is not restoring the files.  This usually requires a service restart and a re-submission of the FSAUtility command. Something may have happened in communicating with storage to cause the issue. 

 

Regards,

Patrick