01-13-2015 02:45 PM
Hello,
So I know you can limit the number of placeholders in and the time interval within the registry but is there a way to limit by size or time out? We had an issue last week where several users recalled placeholders for very large files and it pretty much hammered the network since it is a remote site with limited bandwidth. So I do not know of an option to do this but wanted to see if anyone had any suggestions to help keep a few huge files from crippling our remote sites.
Thanks,
Travis
Solved! Go to Solution.
01-14-2015 10:07 AM
Is the file server in the remote office? I think your only option would be to not archive large files any more in the future and restore the large files so it doesn't happen any more.
01-13-2015 02:55 PM
i dont know if it's exactly what you're looking for but there is a reg key called FileDownloadTimeOut.
from the Registry_Values.pdf that comes with EV:
FileDownloadTimeOut
On a 32-bit installation of Windows:
HKEY_LOCAL_MACHINE
\SOFTWARE
\KVS
\Enterprise Vault
\FSARestore
On a 64-bit installation of Windows:
HKEY_LOCAL_MACHINE
\SOFTWARE
\Wow6432Node
\KVS
\Enterprise Vault
\FSARestore
Location
Content DWORD.
FileDownloadTimeOut lets you change the placeholder recall
mechanism of the FSAUtility -t and -b options from asynchronous to
synchronous, and to specify a timeout, in minutes, for the synchronous
recall of each file.
If FileDownloadTimeOut is set to 0, recall is asynchronous.
If set to any value greater than 0, file recalls happen synchronously
with a timeout of the specified minutes. If the recall operation does not
complete within the specified timeout, FSAUtility moves on to recall the
next file.
For example, if you set the value to 30, FSAUtility adds a file to the
queue for file recall and waits for 30 minutes for the file recall to
complete. If the file is not recalled in 30 minutes, the recall operation
runs in the background, and FSAUtility puts the next file in the queue.
Set this registry value on the computer on which you run FSAUtility.
This registry value does not exist by default. If FileDownloadTimeOut
does not exist, FSAUtility -t and -b options recall files asynchronously.
01-13-2015 02:58 PM
sorry, looks like this applies to FSAUtility
01-13-2015 03:22 PM
Thanks for the info AndrewB!
01-14-2015 09:38 AM
Guess I am hitting the wall on this one, I would think there has to be others running into the same thing and a work around but??? Well if anyone has some thoughts please share. In this case we had two users recall a file each that added up to over 1GB slammed the network pretty hard.
Thanks!
Travis
01-14-2015 10:07 AM
Is the file server in the remote office? I think your only option would be to not archive large files any more in the future and restore the large files so it doesn't happen any more.
01-14-2015 10:38 AM
Travis, Currently there is not a setting to limit the size of the items being downloaded. As Tony stated it would be to not archive those files or alternatively a rule could be put in place to archive files over a certain size (say 100mb), but not replace them with a shortcut for 99 years. This rule would have to be at the top of the rules list.
01-16-2015 10:34 AM
Thanks Guys,
I figured so and actually started writing out a plan to adjust this but need to work it out with the business managers.
Appreciate the replies!
Travis