In many of the articles, videos, blogs and forum comments that I’ve done I have more than likely referred to my ‘simple’ Virtual Machine environments which I have used for the last 6 years both at Symantec and now outside of Symantec. All the time the storage has been local storage. A drive letter directly on the Enterprise Vault server. Of course many people run environments like that out in the real world too, but many if not most won’t run environments quite like that. In this article I will explain how to configure Enterprise Vault to connect to storage which is remote, and to use it for storage of archived items.
Decide where your remote storage is going to be
.. not too far away.
.. EV will do a ping test when adding the storage. Strictly speaking not the best test in the world, but it’s a good start.
.. reliable link between the EV server and the storage. This is a MUST.
Create a new partition
Locate the Vault Store that you want to switch to using remote storage, and then start to create a new partition by right clicking it in the VAC and choosing ‘New’, then ‘Partition’. The default storage type is NTFS Volume:
You need to change that to ‘Network Share’, before clicking on next:
On the next page of the wizard you then simply enter the UNC path you want to host the storage, or browse to it. You need to actually specify a folder below the main share location. For example if the share is \fs01st, then specify \fs01stpartition1, and that folder needs to exist. On the page after that the connectivity test can be run:
Rollover to the new partition
You can then rollover to the new partition using either PowerShell:
start-partitionrollover -EvServerName xyz -VaultStore NameOfVaultStore
Or you can close the current open partition in the VAC and rollover to the new location that way.