Is this procedure recommended or documented?

I have the same problem with a server driven PST migration with EV 8.0.2. So far I have migrated a single PST file which is still in completing status at least 24 hrs after the migration. The temporary copy has been removed fromt he PST Holding folder and the temporary folder allocated to the migrator task. The file still exists on the client PC.

Hacking away at SQL tables is not my idea of a fix (or even a workaround) for this issue - supported or otherwise.

Is this state caused by the EV application waiting for a backup of the client side file before deleting it (in the same manner as Safety copies on mailbox messages)? I think a test is in order.

Cheers

Andy

Hi,

As Andy rightly says this can be caused by backup.

http://support.veritas.com/docs/283580

Also see this technote.

http://support.veritas.com/docs/317553

If neither of the above is applicable, I would recommend you gather the following and log a support case.

1: Open the Vault Administration Console and select Tools from the menu. 
Ensure Advanced Features is checked. 
In the left hand menu expand EV Servers and left click, right click on the Enterprise Vault Server that is experiencing the issue.  Select Deployment Scanner from the menu. 
Follow the wizard through collecting data and email the CAB file. By default this will be located in C:\Program Files\Enterprise Vault.
2. Is the environment that the problem is occurring in new?
3. When did the problem start?
4. Were any changes made to the environment leading up to this problem?
5: Confirm the migration method you are using.

Hello again 'The Don'

Thanks for the heads up but in my case I dont believe that either of the scenarios related in the technotes above are true.

I've just carried out a test to confirm my theories, but I need to repeat it for my mind to be clear. 

I'll be back............

OK Time to eat my words...

The condition I was experiencing was due directly to safety copies being enabled. However in my case, the Migrator task is set to manual and  not normally running. We had another backup last night, so I started the migrator task a short time ago and lo and behold, the status chages to complete after a short interval.

Cheers The Don

Hi Andy,

Glad that helped ;-) and thanks for posting back. 

If you are happy to may be you could vote on my previous post so I can get some more points ;-)
You dont ask you don't get and all that.

Thanks