cancel
Showing results for 
Search instead for 
Did you mean: 

FSA placeholder migration problem

goatboy
Level 6

Hi

EV9.0.2

Trying to do a placeholder migration:

FSAUtility.exe -pm -s \\server1\share -d \\server2\share  -l 0

The intial migration failed right at the beginning, but the log shows it moved the archive point from server1 to server 2 (no placeholders were migrated)

</ErrorCode>

        </Item>

      </ItemList>

     <Status>Failure</Status>

    </APHeader>

    <APMigHeader>

      <ItemList>

        <Item>

          <Item>\\server2\share</Item>

          <ErrorCode>Create a new archive point on the destination folder - Success</ErrorCode>

        </Item>

        <Item>

          <Item>\\server1\share</Item>

          <ErrorCode>Delete source archive point - Success</ErrorCode>

        </Item>

      </ItemList>

      <APMigStatus>Failure</APMigStatus>

    </APMigHeader>

  </PhMigration>

  <Footer>

    <OperationStatus>Failure</OperationStatus>

  </Footer>

</FSAUtilityLog>

 

When we try the migration again, get this error:

Error: Placeholder migration failed. An error occurred while migrating an archive point from source path

\\server1\share

to destination path \\server2\share

Reason: Copy and delete of source archive point 

\\server1\share

failed.

 

 Symantec suggested re-running the placeholder migration, but reversing source and target, so move the archive point back:

FSAUtility.exe -pm -s \\server2\share -d \\server1\share  -l 0

However, this resulted in in the following error:

 

There are no archive points under the source path \\server2\share

 

Any ideas how we can move the archive point back to try the placeholder migration again?

2 REPLIES 2

EV_Ajay
Level 6
Employee Accredited

Hi,

Please refer following articles which has Hotfix for EV FSA Archiving 9 SP2 for multiple issues which also include the FSAUtility -pm operation failed issue.

Hotfix for Symantec Enterprise Vault (EV) for File System Archiving 9.0 Service Pack 2, Build 1061, multiple issues
http://www.symantec.com/docs/TECH192180
 
 

goatboy
Level 6

Thanks.


We fixed the issue with Symantec help by re-creating the archive point on the source file server (EVArchivePoint.xml) referencing the old ArchiveID and deleting the migrated one on the target.

Any other recommendations before we retry the migration again? I am testing the hotfix in dev and will install it in prod. Besides running a dtrace next time we try the migration, anything else we can do to increase chances of success?