Video Screencast Help
Protect Your POS Environment Against Retail Data Breaches. Learn More.

Moving Vaulted files (FSA)

Created: 21 Apr 2006 • Updated: 25 Nov 2012 | 11 comments
This issue has been solved. See solution.

I have had to move a large number of files from one location to another, a lot of the files are vaulted and when i move them it works for about 10-15 secs than stops with a "cannot copy register: Cannot read from the source file or disk".

I then have to restart the Placeholder service and try again, same thing happens. I've done this now for at least 50 times and am getting a bit hacked off. Does any one else have to put up with this "feature" from symantec?

regards

Discussion Filed Under:

Comments 11 CommentsJump to latest comment

Jason Szeto's picture

Since you are moving the files, the placeholder service has to recall all those files before it can be copied and by default there is a limit to the number of files you can recall. Set either one of these 2 reg keys and you should be able to move the files you need. You can either increase the number of recalls or set it so anyone who has admin access can bypass the recall limit.


RecallLimitMaxRecalls
Location
HKEY_LOCAL_MACHINE
\SOFTWARE
\KVS
\Enterprise Vault
\FSA
\PlaceholderService
Content
DWORD. Initial value 20

Description
You can specify a maximum rate of recall on each computer that runs a Placeholder Service, thus controlling the rate at which an individual user can recall files. By doing this you also prevent any applications that do not honor the file system offline attribute from recalling all files that had been archived from a volume.

The default maximum rate is 20 recalls in 10 seconds. This recall limit applies to all users except, by default, members of the local Administrators group.

If the recall limit is exceeded, the application receives an Access Denied status. Just how this is displayed to the user depends on each individual application.

RecallLimitMaxRecalls specifies the maximum number of items that a user is allowed to recall in RecallLimitTimeInterval seconds.

Withdrawn
Withdrawn in Enterprise Vault 6.0 for NetApp File System Archiving. Still valid for Windows File System Archiving.



BypassRecallLimitsForAdmins
Location
HKEY_LOCAL_MACHINE
\SOFTWARE
\KVS
\Enterprise Vault
\FSA
\PlaceholderService
Content
DWORD

0 - (Default) Recall limits apply to administrators

1 - There are no recall limits for administrators

Description
You can specify a maximum rate of recall on each computer that runs a Placeholder Service, thus controlling the rate at which an individual user can recall files. By doing this you also prevent any applications do not honor the file system offline attribute from recalling all files that had been archived from a volume.

This recall limit applies to all users except, by default, members of the local Administrators group.

BypassRecallLimitsForAdmins controls whether the recall limits apply to members of the local Administrators group on the server that is running the Placeholder Service.

See Also
RecallLimitMaxRecalls

Introduced
5.0 SP3

Withdrawn
Withdrawn in Enterprise Vault 6.0 for NetApp File System Archiving. Still valid for Windows File System Archiving.

Richard ware's picture

Jason

Thanks, you gave me this answer yesterday, but i made no difference, I still get access errors and have to restrt the placeholder service between operations.

Regards

Jason Szeto's picture

Hmm...your issue definitely sounds like the recall limit is being hit. You set the reg keys on your file server, correct?

Another suggestion would be do a backup and then restore the files into the new location.

Brit Stock's picture

Not sure what method you are using to copy the files, but I have this same problem. I have been using ROBOCOPY and simply set the retry timeout to 15 seconds and normally the system catches up. I certainly wish there was a better way to move the data.

Richard ware's picture

Cheers Brit

Glad i'm not the only one, i'll have a look at ROBOCOPY

thanks

Richard

C H's picture

You should try using the evfsabackupmode.exe to put the service into read only mode. Make sure the user that is performing the backup/move is in the Enterprise Vault Backup Operators Group (a local group you have to create i believe) and you shouldn't have a problem with the recall limits

Jeffrey Piersol's picture

I was having the same problem, moving large amounts of data that had been archived. Veritas had me set my registry values on the file server to the following:

RecallLimitMaxRecalls to 512
RecallLimitTimeInterval to 1


So far, it seems to be working fine.

Also, here's a link to the documentation on their FTP site (includes FSA)...

http://ftp.support.veritas.com/pub/support/product...

C H's picture

Better to use evfsabackupmode.

If you raise the no of max recalls for all users, then you could seriously lower performance for recalls

Michael Folks's picture

I am wanting to move a file server from local storage to the SAN and several of the folders are archived. Currently we have about 70GB archived on the Centera. Is there no way to just copy the short-cuts without having to restore the items for moving? I would think that FSA doesn't care where the short-cut lies because it is only a pointer to where the archived file is. So why couldn't I add the copy utility I am using to the exclude list for archive retrieval and just copy the stubs to the new location? Another reason for doing it this way, is this volume is 900GB and I was wanting to cut down on the amount of time it would take to move the data to the SAN by archiving more data and just moving the stubs. If this is not the best way or even feasible, please let me know.

Thanks,

Michael

TonySterling's picture

If you can wait til EV 7 there will be a move utility for placeholders and archivepoints that will make this easier for you.

SOLUTION