Video Screencast Help
Scheduled Maintenance: Symantec Connect is scheduled to be down Saturday, April 19 from 10am to 2pm Pacific Standard Time (GMT: 5pm to 9pm) for server migration and upgrade.
Please accept our apologies in advance for any inconvenience this might cause.

Only one Direction is working when useing the move archive function.

Created: 10 Jan 2013 | 4 comments

My Company has two site running own Enterprise Vault installations. Site A with SEV 9.02 and Site B with SEV8.04.
The move archive function is working from SEV 9.02 to SEV 8.04. Unfortunately that is the wrong direction.
We want to consolidate Exchange and SEV into Site A.
When one starts the the move archive assistent on Server in Site B, it fails at the level where you have to choose a Vault Store in Site A, where the archive is moved to. The tiny window were to choose the vault store on the opposite is gray and nothing is shown.

The funny thing is that the other way round is working but not wanted.

Any Ideas?

Discussion Filed Under:

Comments 4 CommentsJump to latest comment

TonySterling's picture

If your trusts between the sites are ok you might have to upgrade your EV 8 site to EV 9.

There is this note about Trusts:

When move operations cross two Active Directory domains, a one-way trust is required for the moves to proceed. The destination domain must trust the source domain.

Gruber09's picture

Hi Tony,

thanks for answering.

The trusts are OK. There is a two trust between the two domains is place.

According to Symantec Documentation, the move assisten is fully supported between V8 and V9.

Cheers,

George

TonySterling's picture

I understand what the document may say.  You could try a dtrace of the MMC to see if that captures what is failing.

MMcCr's picture

Check your DNS also, make sure your DNS can resolve the FQDN and shortname of your site and the server(s).

I had something similar and DNS was fine, I ended up having to set Host & LMHost files on both servers for the target FQDN and shortname before EV would let me complete a move archive completely.

Aditionally make sure the vault service account for the source has access to the databases in the target.

It still may be an option to look at getting the sites at the same version (even though the docs say different)