Error Message

 

Considering the logic used with the Placeholder Migration process workflow, after the paths used in the syntax including the Source and Destination volumes are fully validated against the target references in the Directory database, the next step is to walk the file system structure at source, validate the existing Placeholders and, where needed, recreate the folder structure at the destination in preparation for the Placeholders that will be created at the destination target.

Thinking ahead, assuming the initial processing of all Placeholder validations and the creation of the folder structure at the destination path goes without errors, towards the end the references in the database will be updated to reflect the destination FolderPaths, and that would be for the all the folders that exist in the database for that Archive. That means that all Savesets that are linked to VaultIdentity values for all the FolderPaths under the Archive will now be associated with the folder structure at the destination.

The complication starts when, within the source path for the Archive Point, some folders contain only recalled Placeholders.

In this case, as the file system walker thread does not find any Placeholders to validate, it does not add this corresponding folder to the list of folders to be created at the destination path; no placeholders will be created as none exist at source.

Technically, from a migration viewpoint, the items in the Archive associated with that skipped folder have been migrated without question, but from a user experience, as the folder was not created at the destination, the user may perceive it as the migration did not process the entire Archive.

 

 

Here, the rescue towards sanity is found by running FSAUtility -c -s -r  in report mode to generate an output of all the content (Placeholders) that would exist should the same syntax be executed in normal mode.

One could go straight into running the -c in normal mode, but the report mode log would provide means of capturing evidence of all the content that would not have been migrated at the time.

Essentially, the migration does work, as long as no errors are reported, but depending on the state of the source items what is effectively created at the destination may vary.

 

 

 

 

 

After performing a migration with FSAUtility -pm, the migration of the Archive is reported to have completed successfully, the FSAUtilityOperations table does not show the syntax for the applicable migration, and all the Database tables appear to have the correct destination path associated with the content under the migrated Archive Point. The above checks suggest that the Migration was indeed successful, however some folders appear to be missing at the destination path, whereas they are still available at the source including files. When looking at the content in the Archive from AEUI or EVS, the content listed seems to match the folders and files listed at the source, as when looking at the destination file system some folders do not exist. This leads to the suspicion that something with the migration did not go according to plan.