Migrating placeholders

Article:HOWTO57565  |  Created: 2011-08-01  |  Updated: 2013-07-12  |  Article URL http://www.symantec.com/docs/HOWTO57565
Article Type
How To


Subject


Migrating placeholders

Note:

Before you migrate placeholders, make sure that you have a backup of the Directory database, the vault store databases, and the folder hierarchy under the source path. Back up the folder hierarchy under the destination path also, if it contains archived files.

You can use FSAUtility with the -pm parameter to migrate placeholders and archive points from a source folder structure to a destination folder structure, for example on another volume or file server.

This option moves the placeholders and archive points, but it does not move any files in the archives. The migrated placeholders retain their links to the archived files in their original locations. This option therefore provides a faster solution for moving placeholders than the FSAUtility move (-m) option. Use the -m option if you want to move archives, consolidate vault stores, or align archives with file servers.

This option always migrates placeholders in subfolders recursively, provided that they reside under a valid archive point. The option creates the destination subfolders, if necessary.

Before performing a placeholder migration, FSAUtility checks for any conflicts between the archive points at the source location and the destination location. It then performs the following actions, in the order listed:

  • Moves the placeholders. FSAUtility creates the placeholders on the destination location and then deletes the placeholders at the source location. The migration retains the placeholder file's security descriptor, which contains information about the ownership and NTFS permissions for the file. The migration also retains any alternate data streams associated with the placeholder file.

  • Moves the archive points to the destination location.

  • Updates the Directory database with the new folder paths.

Note the following requirements for placeholder migration:

  • The source volume and destination volume must both be specified as FSA targets in the Administration Console.

  • The same Enterprise Vault server must manage the source volume's vault store and the destination volume's vault store. If FSAUtility cannot confirm that the same Storage service computer manages both vault stores, it quits with an explanatory message.

  • If the destination volume is on a NetApp file server, you must run the FSAUtility command from an Enterprise Vault server that is registered with the destination file server's FPolicy. For example, to migrate placeholders from NetAppFiler1\volumeA to NetAppFiler2\volumeB, you must run FSAUtility from an Enterprise Vault server that is registered with NetAppFiler2.

  • If any folders with archive points are missing from the source folder structure, FSAUtility does not proceed with the migration.

  • You cannot migrate placeholders to a subfolder of the source folder.

Note that FSAUtility does not proceed with a migration if the destination path already contains an archive for a folder that matches the folder hierarchy on the source path. This restriction prevents a split archive, where the files with the migrated placeholders are in a different vault store from the other archived files. You must specify a destination path that has not been archived from, or one that contains no folders with archived files in the same folder structure as the source path. For example, consider the example source folder structure and destination folder structure shown in Figure: FSAUtility placeholder migration: example folder structures:

Figure: FSAUtility placeholder migration: example folder structures

FSAUtility placeholder migration: example folder structures

FSAUtility does not proceed with the migration if either of the following applies:

  • An archive point with archived files exists at the root level, for both the source volume and the destination volume.

  • An archive point with archived files exists in both of the folder structures, on any of the following folders:

    • Folder1

    • Subfolder1

    • Folder2

FSAUtility can migrate the placeholders if there is no clash of archive points that have archived files. For example, the migration is not prevented if either of the following applies:

  • On the destination folder structure, only Folder5 and Folder 6 have archive points with archived files.

  • Folder2 in the source folder structure has an archive point with archived files, but Folder2 in the destination folder structure does not.

FSAUtility records the following events in the event log:

  • The start of a placeholder migration

  • Whether a migration completes without errors, or with errors.

Additionally, during a placeholder migration FSAUtility displays appropriate messages on the console, and records detailed entries including errors in the Dtrace logs and in the Reports\FSAUtility\EV_FILESYSTEM_UTILITY_LOG_DateTime.xml file.

If a placeholder migration fails, do not archive files on the destination path. Otherwise the archived data for that path may become split across multiple archives. Retry the placeholder migration to see whether it can complete successfully.

Note:

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.

Syntax

FSAUtility -pm -s UNC_path -d UNC_path [-cs] [-csf] [-f] [-l log_level] [-i]

Where:

  • -s UNC_path specifies the path to the source folder. The path must specify the volume in the format that you used when you added the volume target in the Administration Console.

  • -d UNC_path specifies the path to the destination folder. This path to the folder must already exist. The path must specify the volume in the format that you used when you added the volume target in the Administration Console.

  • -cs copies folder security descriptors to new folders at the destination. Security descriptors of existing folders at the destination are not overwritten. This option cannot be used with -csf. If you do not specify -cs or -csf, no folder security descriptors are copied.

  • -csf copies folder security descriptors from source folders to destination folders, overwriting the security descriptors of destination folders that already exist. This option cannot be used with -cs. If you do not specify -cs or -csf, no folder security descriptors are copied.

  • -f forces the migration of placeholders when placeholders or files of the same name already exist at the destination. The utility first deletes the existing placeholders or files at the destination 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.

  • -i causes FSAUtility to ignore any errors that occur when it moves the placeholders, such as:

    • Failure to determine whether a file is a placeholder.

    • Failure to create placeholders at the destination location, for example as a result of permission issues or insufficient disk space.

    • Failure to delete placeholders from the source location.

    If you omit the -i parameter and any placeholder move errors occur, FSAUtility logs the errors and stops when it has finished attempting to move all the placeholders. It does not go on to move the archive points or update the Directory database. In this case you may need to rerun FSAUtility -pm when you have fixed the causes of the placeholder move failures.

    If you specify the -i parameter and any placeholder move errors occur, FSAUtility logs the errors but it continues with the remaining steps of the migration: it goes on to move the archive points and update the Directory database. Errors that occur during the archive point migration or the database update are not ignored. FSAUtility continues to log all errors in the log file Reports\FSAUtility\EV_FILESYSTEM_UTILITY_LOG_DateTime.xml.

    If you specify -i and any placeholder move errors occur, you can correct these errors when the command has completed, if you want. For example, you can:

    • Delete placeholders at the source location.

    • Recreate unmigrated placeholders at the destination location, using the FSAUtility -c option.

      See Recreating placeholders.

    • Or use Archive Explorer to restore files with unmigrated placeholders to the file server. The files are restored to the new location, and placeholders are created on the next archiving run.

    Note however that recreating unmigrated placeholders using these methods does not retain the security descriptors of the original placeholders, nor does it recreate any alternate data streams that were associated with the original placeholders.

    Note:

    We recommend that on the first run of a placeholder migration you omit the -i parameter. If the migration fails and the report indicates that the failure was due to errors when moving some placeholders, you can rerun the command with the -i parameter if you want FSAUtility to ignore those errors.

Examples

The following command migrates the placeholders along with the archive points from the first folder structure to the second folder structure. The command copies the security descriptors for newly-created folders from the source folders. If any files or placeholders of the same name already exist, the command overwrites them with new placeholders. FSAUtility does not ignore errors when it moves the placeholders.

FSAUtility -pm -s \\myserver\users\user1 -d \\server2\share\user1 -cs -f

Notes

  • You cannot run -pm in report mode.

  • After a placeholder migration, other FSAUtility options do not work on the destination folder until File System Archiving task has processed the folder at least once.

  • The migration migrates any placeholders in the source folder tree, including placeholders that were cut and pasted into it. However, if the archived files associated with cut and pasted placeholders are not available in the source tree's archives before the migration occurs, the files will not be in the archives afterwards.

  • If a source folder has an archive point and the names of the source folder and destination folder differ, then after a placeholder migration the archive's name does not change to match the destination folder until the File System Archiving task has processed the volume.

  • If a vault store already contains an archive with the same name as a destination folder name, then after the migration you see a second archive with the same name. There is no consolidation of the archives.

See also

See Moving placeholders and corresponding files.

See FSAUtility options

See About FSAUtility


Legacy ID



v40198744_v41328148


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


Terms of use for this information are found in Legal Notices