Placeholder recall fails after moving Enterprise Vault to a new server with a new name
Article ID: 100010689
Updated On:
Description
.
Cause
When placeholder files are created, metadata containing the recall URL is written to them. This URL contains the name of the EV server at that time. If the name of the EV server later changes, this metadata is not updated. Therefore, the placeholder recalls will attempt to contact the old EV server.
Resolution
A simple solution is to update the hosts file on the file server to redirect requests for the old EV server name to the new EV server.
Another solution, which is more complex, is to recreate all placeholders using FSAUtility's -c option(Refer Additional Information).
Issue/Introduction
After migrating the Enterprise Vault (EV) server to new hardware with a new name and alias, the placeholders that predate the migration cannot be recalled from the file servers.
Additional Information
Recreating placeholders
You can use FSAUtility with the -c parameter to recreate the placeholders for archived files in their original location. This facility may prove useful if you need to restore a file server to its original state or synchronize the file server with the Enterprise Vault archive. If multiple versions of the same file exist in the archive, the utility creates a placeholder for the latest version only.
Note:
Before you use this option with Dell EMC Celerra/VNX placeholders, ensure that FSAUtility is configured to use a suitable method for identifying the placeholders.
See About using FSAUtility with Dell EMC Celerra/VNX placeholders.
FSAUtility -c -s UNC_path [-D mm-dd-yyyy] [-f] [-l log_level] [-r]
Where:
-
-s UNC_path specifies the path to the required folder, volume, or file server.
-
-D mm-dd-yyyy specifies an archive date. FSAUtility recreates placeholders for files archived after the specified date.
-
-f forces FSAUtility to recreate the placeholders when placeholders or files of the same name already exist. The utility first deletes the existing placeholders or files and then creates the new ones.
-
-l log_level specifies whether to log both successful operations and failed operations (0) or failed operations only (1). By default, FSAUtility logs failed operations only.
-
-r specifies report mode. FSAUtility generates a report that outlines the activities that it would perform if you were to run it in normal mode, but without performing those activities.
FSAUtility generates a report named
EV_FILESYSTEM_UTILITY_REPORT_DateTime.txt, in the folderinstallpath\Reports\FSAUtility.If you run -c in normal mode, FSAUtility generates a report named
EV_FILESYSTEM_UTILITY_REPORT_DateTime.xml.
The following command recreates the placeholders for the folder \\myserver\users and generates a log file that lists both successful operations and failed operations. The command runs in report mode.
FSAUtility -c -s \\myserver\users -l 0 -r
The following command recreates the placeholders for those files that were archived after July 10 2005 from the folder \\myserver\users\user1. If any files or placeholders of the same name already exist, the command overwrites them with new placeholders.
FSAUtility -c -f -s \\myserver\users\user1 -D 07-10-2005 -l 0
-
FSAUtility does not support "hard link" files (directory references to files). You cannot recreate any existing placeholders for hard link files. When you perform a recreate operation, FSAUtility recalls any placeholders that are hard link files.
-
When you recreate placeholders with FSAUtility, you may receive the message "Internal Error Moving Placeholders: Archive ID null for folder folder_path" if you subsequently try to move them to another location. To stop this message from appearing, recreate the archive points and then archive the source folder before you try to move the placeholders.
-
Due to a NetApp restriction, FSAUtility does not recreate placeholders if the path to the folder exceeds 512 characters.
