Moving placeholders and corresponding files

Article:HOWTO57564  |  Created: 2011-08-01  |  Updated: 2013-07-12  |  Article URL
Article Type
How To


Moving placeholders and corresponding files

You can use FSAUtility with the -m parameter to move placeholders and the corresponding archived files. The archive point that applies to the destination folder determines the destination archive. The destination archive can be in a different vault store.

The command moves placeholders in subfolders of the source folder, unless the subfolder has an archive point. The subfolders are created under the destination folder if they do not exist there.

If no archive point exists on the path to the destination folder, the command exits without proceeding.

If the archive point on the destination folder has no archive ID or an invalid archive ID, FSAUtility checks the Directory database records to determine whether the folder path is associated with any archive IDs:

  • If no archive ID is associated with the folder path, FSAUtility creates an archive and assigns the archive ID to the archive point.

  • If one archive ID is associated with the folder path, FSAUtility assigns that archive ID to the archive point.

  • If more than one archive ID is associated with the folder path, FSAUtility does as follows:

    • It assigns the archive ID of the oldest existing archive to the archive point.

    • It generates a warning event with event ID 41484 in the Enterprise Vault event log. The event lists the archive IDs of the multiple archives for the folder path, and indicates that the oldest archive will be used for archiving.

    Note that after FSAUtility has assigned an archive ID to the archive point, no further warnings are issued about the existence of multiple archives for the folder path.

If there is an archive point on the source folder and there are no archive points on any subfolders, then the source folder archive point is deleted if all the placeholders are moved successfully.


Before you use this option with Celerra/VNX placeholders, ensure that FSAUtility is configured to use a suitable method for identifying the placeholders.

See About using FSAUtility with EMC Celerra/VNX placeholders.


FSAUtility -m -s UNC_path -d UNC_path [-l log_level] [-r]


  • -s UNC_path specifies the path to the source folder.

  • -d UNC_path specifies the path to the destination folder.

  • -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 folder installpath\Reports\FSAUtility.

    If you run -m in normal mode, FSAUtility generates a report named EV_FILESYSTEM_UTILITY_REPORT_DateTime.xml.


The following command moves the placeholders from the first folder to the second folder. It also moves the archived files to the corresponding archive location. The log file lists failed operations only.

FSAUtility -m -s \\myserver\users\user1 -d \\sample\share\user1


  • You cannot move placeholders from the root folder of a volume. You can move placeholders from the subfolders of the root folder.

  • FSAUtility does not delete a source folder from which you have moved placeholders after it has completed the operation. The folder may contain other, unarchived files that it would be inappropriate to delete.

  • If you halt an FSAUtility operation to move placeholders before it has finished, then when you next start the utility it prompts you to resume the operation.

  • The volume policy or folder policy that applies to the destination location determines whether Enterprise Vault deletes archived files when their placeholders are deleted. See "Deleting archived files on placeholder deletion" in Setting up File System Archiving.

  • If the source vault store or destination vault store is in backup mode when you try to move placeholders, the utility exits without proceeding.

  • FSAUtility does not support "hard link" files (directory references to files). You cannot move any existing placeholders for hard link files. When you perform a move operation, FSAUtility moves any placeholders that are hard link files.

  • If any of the following becomes unavailable while you move placeholders, FSAUtility does not try to process any outstanding placeholders:

    • Enterprise Vault Directory Service

    • Enterprise Vault File Placeholder Service

    • Enterprise Vault Storage Service

    • The network connection between Enterprise Vault and the file server

    Instead, the utility exits after recording an error message in the event log, DTrace log, and FSAUtility log file.

See also

See Migrating placeholders.

See FSAUtility options

See About FSAUtility

Legacy ID


Article URL

Terms of use for this information are found in Legal Notices