Forum Discussion

AWMorris's avatar
AWMorris
Level 4
13 years ago

FSAUtility -pm

Hi All,

 

I am working with a customer and we are currently running FSAUtility -pm to migrate placeholders from a Windows to Celerra box.  I have run this before and seen upwards of 50K/hour.  The following article indicates that Symantec was migrating at a rate at 100K/hour.

 

https://www-secure.symantec.com/connect/blogs/file-system-archiving-enterprise-vault-v9-placeholder-migration

 

We have set the following registry key

 

HKLM\Software\KVS\Enterprise Vault\FSA

DWORD – FSAUtilityFolderProcesThreads

DECIMAL - 20

 

But we are only seeing 18K to 20K/hour.  Are there any additional performance tweaks to speed up this process?  Additionally, we we see this error on occasion and it looks as if there might be some resource issues when querying the ArchiveFolder table.  Any ideas?

 

8390 FSAUtility Tool

 

Event Type: Error
Event Source: Enterprise Vault
Event Category: FSAUtility Tool
Event ID: 8390
Date:  5/9/2012
Time:  8:52:50 PM
User:  N/A
Computer: WMSIEVFSA
Description:
The EnterpriseVault.DirectoryConnection object reported an error.
 
Ran out of memory

Internal references:
Error 0x8007000e
CDirectoryConnectionObject::GetArchiveFoldersByArchive .\DirectoryConnectionObject.cpp [lines {3091,3099,3102}], built Mar 14 10:55:02 2011

For more information, see Help and Support Center at http://evevent.symantec.com/rosetta/showevent.asp

  • So I just saw FSAUtility.exe use about 1.7 GB of RAM and then die........

  • You will want to call that one into support. '

    There is some investigation into improving GetArchiveFoldersByArchive and how it utilizes memory.

  • Hi Jim.  I have opened a case with support and it is being investigated.  I was given ETrack 2729682 as a reference.

  • That is what I was referring to. You have it assigned and can work directly with the support rep. Rob and Patrick on this. I was chatting to them about it earlier. I think we can close this discussion at this point.

  • I took credit for this one Jim.  Sorry ol buddy... LOL.  Guess you better post the ETrack number next time :)

  • I probably can't post the etrack #'s unless there is an associated tech note.