Symantec Enterprise Vault for Exchange 2007

I don't think you are going to get away without doing some sort of very brief service restart. I would always advise scheduling plenty of downtime to do this carefully. However if you are feeling gung-ho, read on.

If you want to keep downtime to a minimum, and you do not have the capability to natively replicate storage from one source to another (SRDF for instance) then make sure you have set the environment so that no user changes or collection runs can be made as per the pre-migration steps in the following document:

http://www.symantec.com/docs/TECH141481

Then, create a new partition on the new LUN so that new archived data is going to be going to use this going forwards.

As the old partitions are now effectively read-only because you have

a) disabled user updates and

b) disabled the collections process

(ok items may be extracted from Cabs but this is not an issue)

then you can go ahead and update the vault store partition database. Prepare a script for this so it can be done in ultra-fast time. You *could* even (ultra cowboy mode) do this whilst the environment is still running because the storage would be available in both locations. You would need to restart storage to confirm the new locations were in use though.

For indexes,

set them to read-only.

replicate the data over.

Switch the locations in the database

restart indexing. remove read-only

If the index is out of date it will catch up, so the only thing that could *possibly* happen is that half the files in an index were being updated at the time of a copy, and that isn't going to happen because they were in read-only.

Back out your read-only changes, and you are done.

Regards,

Jeff