Hotfix for Symantec Enterprise Vault (EV) 2007 Service Pack 4 (SP4), Build 2534, Archiving Files through Enterprise Vault (EV) File System Archiving (FSA) alters the last access time.
| Article:TECH65461 | | | Created: 2008-01-24 | | | Updated: 2009-01-09 | | | Article URL http://www.symantec.com/docs/TECH65461 |
Problem
Hotfix for Symantec Enterprise Vault (EV) 2007 Service Pack 4 (SP4), Build 2534, Archiving Files through Enterprise Vault (EV) File System Archiving (FSA) alters the last access time.
Solution
Note:
A Workaround section has been added at the end of the document which can be used instead of the hotfix
To which versions of Symantec Enterprise Vault can this hotfix be applied?
A Workaround section has been added at the end of the document which can be used instead of the hotfix
To which versions of Symantec Enterprise Vault can this hotfix be applied?
This hotfix can only be applied
to the following versions of Enterprise Vault:
Enterprise Vault 2007 Service
Pack 4 (SP4) Build RG2534
What issues
does this hotfix resolve?
1. EV FSA modifies the
last access time of the files being archived to the time at which the archiving
was run.
This will affect the conversion
of archived files to placeholders if:
- Archiving strategy is based on 'last access date'
- Remove safety copies set to 'After backup'
2. EV uses SetFileTime API
to reset last access time with opening file handle with FILE_WRITE_ATTRIBUTES,
but in some cases on NTFS the time does not reset even though the API returns
success.
This is due to oplocks not being
released properly.
3. The hotfix uses
FILE_GENERIC_WRITE to open file handles for resetting last access time
Which file does the hotfix replaced?
EVFileServerArchiveWrapper.dll 7.5.4.2562
How to install this hotfix?
As best practices, make sure to have a backup of the system before making any changes.
As best practices, make sure to have a backup of the system before making any changes.
1. Stop Enterprise Vault
Services on all EV Servers.
2. On all EV Servers, take a
copy of the EVFileServerArchiveWrapper.dll file that currently exist in the EV
installation directory.
3. Copy the file from the hotfix
to EV installation folder on each EV Server:
EVFileServerArchiveWrapper.dll
4. Restart all services on all
EV Servers
How to uninstall this hotfix?
1. Stop all Enterprise Vault
services
2. Copy the original modules
back to the Enterprise Vault installation directory and over write the existing
files.
3. Start the Enterprise Vault
services.
Workaround
A workaround is available from Microsoft to fix this issue without the need of installing the hotfix.
This involves setting the 'CachedOpenLimit' registry key to 0 on each file server.
Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application.
1. In Registry Editor, locate the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Lanmanserver\Parameters
2. Under the Parameters registry subkey, click Edit, click New, click DWORD Value, type CachedOpenLimit, and then press ENTER.
3. Set the decimal value of the Cachedopenlimit registry entry to 0.
4. Restart the Server service.
When you set the value to 0 , file handles of all the shared files are not cached by the system. This can cause a performance issue when you are accessing shared files in the system.
A workaround is available from Microsoft to fix this issue without the need of installing the hotfix.
This involves setting the 'CachedOpenLimit' registry key to 0 on each file server.
Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application.
1. In Registry Editor, locate the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Lanmanserver\Parameters
2. Under the Parameters registry subkey, click Edit, click New, click DWORD Value, type CachedOpenLimit, and then press ENTER.
3. Set the decimal value of the Cachedopenlimit registry entry to 0.
4. Restart the Server service.
When you set the value to 0 , file handles of all the shared files are not cached by the system. This can cause a performance issue when you are accessing shared files in the system.
Attachments
|
|
|
| Source | ETrack |
| Value | 1431837 |
| Description | last access date etrack |
Legacy ID
315315
Article URL http://www.symantec.com/docs/TECH65461
Terms of use for this information are found in Legal Notices









Thank you.