The File System Archiving Checkpoint feature is not processing through sub-folders alphabetically, which can cause the re-processing of some folders

Article:TECH163368  |  Created: 2011-06-27  |  Updated: 2014-12-04  |  Article URL http://www.symantec.com/docs/TECH163368
NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.
Article Type
Technical Solution


Issue



The File System Archiving Checkpoint feature is designed to process through the sub-folders of a partially processed Volume target in an alphabetical manner.  However, when the sub-folders are presented from the file system in non-alphabetical order some folders may be processed during multiple archiving runs.


Cause



Enterprise Vault will check each sub-folder of the volume target and determine whether the previous checkpoint folder has been reached.  Enterprise Vault checkpointing assumes that the sub-folders are presented in an alphabetical manner.  However in certain environments, such as Netapp, folders may be presented to Enterprise Vault out of alphabetical order.  When this occurs a DTrace of the 'EvFsaArchivingTask' will show similar entries to the following:

{FILESYSTEMFOLDERWALKER.EN_US} Folder: \\?\UNC\eafas02.bcnet.capbluecross.com\useradmin$\Users, currentRootFolder: \\?\UNC\FileServer.organization.local\sharename$\Volume
{FILESYSTEMARCHIVINGCHECKPOINT.EN_US} Folder to be checked for FSA checkpoint skipping : \\?\UNC\FileServer.organization.local\sharename$\Volume
{FILESYSTEMARCHIVINGCHECKPOINT.EN_US} Skipping folder \\?\UNC\FileServer.organization.local\sharename$\Volume from processing as we are in one of the sub-paths of last run folder \\?\UNC\FileServer.organization.local\sharename$\Volume\GGG\subfolder1\1234\
{FILESYSTEMFOLDERWALKER.EN_US} Folder: \\?\UNC\FileServer.organization.local\sharename$\Volume\AAA, currentRootFolder: \\?\UNC\FileServer.organization.local\sharename$\Volume
{FILESYSTEMARCHIVINGCHECKPOINT.EN_US} Folder to be checked for FSA checkpoint skipping : \\?\UNC\FileServer.organization.local\sharename$\Volume\AAA
{FILESYSTEMARCHIVINGCHECKPOINT.EN_US} Skipping folder \\?\UNC\FileServer.organization.local\sharename$\Volume\AAA from crawling as the last run folder \\?\UNC\FileServer.organization.local\sharename$\Volume\GGG\subfolder1\1234\ is yet to be reached
{FILESYSTEMFOLDERWALKER.EN_US} Folder: \\?\UNC\FileServer.organization.local\sharename$\Volume\DDB, currentRootFolder: \\?\UNC\FileServer.organization.local\sharename$\Volume
{FILESYSTEMARCHIVINGCHECKPOINT.EN_US} Folder to be checked for FSA checkpoint skipping : \\?\UNC\FileServer.organization.local\sharename$\Volume\DDB
{FILESYSTEMARCHIVINGCHECKPOINT.EN_US} Skipping folder \\?\UNC\FileServer.organization.local\sharename$\Volume\DDB from crawling as the last run folder \\?\UNC\FileServer.organization.local\sharename$\Volume\GGG\subfolder1\1234\ is yet to be reached
{FILESYSTEMFOLDERWALKER.EN_US} Folder: \\?\UNC\FileServer.organization.local\sharename$\Volume\AAB, currentRootFolder: \\?\UNC\FileServer.organization.local\sharename$\Volume
{FILESYSTEMARCHIVINGCHECKPOINT.EN_US} Folder to be checked for FSA checkpoint skipping : \\?\UNC\FileServer.organization.local\sharename$\Volume\AAB
{FILESYSTEMARCHIVINGCHECKPOINT.EN_US} Skipping folder \\?\UNC\FileServer.organization.local\sharename$\Volume\AAB from crawling as the last run folder \\?\UNC\FileServer.organization.local\sharename$\Volume\GGG\subfolder1\1234\ is yet to be reached
{FILESYSTEMFOLDERWALKER.EN_US} Folder: \\?\UNC\FileServer.organization.local\sharename$\Volume\HHH, currentRootFolder: \\?\UNC\FileServer.organization.local\sharename$\Volume
{FILESYSTEMARCHIVINGCHECKPOINT.EN_US} Folder to be checked for FSA checkpoint skipping : \\?\UNC\FileServer.organization.local\sharename$\Volume\HHH
{FILESYSTEMARCHIVINGCHECKPOINT.EN_US} We have hit the folder from as the last run: \\?\UNC\FileServer.organization.local\sharename$\Volume\HHH
{FILESYSTEMFOLDERWALKER.EN_US} Queueing folder: \\?\UNC\FileServer.organization.local\sharename$\Volume\HHH for processing
{FILESYSTEMFOLDERWALKER.EN_US} On volume 123456789012345678901234567890123456789012evserver, enqueueing folder \\?\UNC\FileServer.organization.local\sharename$\Volume\HHH for archiving
{FILESYSTEMFOLDERWALKER.EN_US} Folder: \\?\UNC\FileServer.organization.local\sharename$\Volume\ABC, currentRootFolder: \\?\UNC\FileServer.organization.local\sharename$\Volume
{FILESYSTEMARCHIVINGCHECKPOINT.EN_US} Folder to be checked for FSA checkpoint skipping : \\?\UNC\FileServer.organization.local\sharename$\Volume\ABC
{FILESYSTEMFOLDERWALKER.EN_US} Queueing folder: \\?\UNC\FileServer.organization.local\sharename$\Volume\ABC for processing

Observe in the above DTrace entries that Enterprise Vault started processing a sub-folder 'AAA' which is not greater than the checkpoint sub-folder 'GGG', however Enterprise Vault is processing the sub-folders as they are presented from the file system which may be out of alphabetical order.  When Enterprise Vault reachs the sub-folder 'HHH' this is greater than the 'GGG' folder and thus checkpointing begins to process the volume for archiving from this point.


Solution



This issue has been addressed as part of the following release:

Enterprise Vault 9.0.3 - Release Details
http://www.symantec.com/docs/TECH147782

Enterprise Vault 10.0.1 - Release Details
http://www.symantec.com/docs/TECH147787


Supplemental Materials

SourceETrack
Value2420371
Description

FSA Checkpointing does not function properly when the folder list is not alphabetical




Article URL http://www.symantec.com/docs/TECH163368


Terms of use for this information are found in Legal Notices