Add new Journal server to existing site move journal task and new journal storeage to the new server
We currently run 2 identical EV servers on a single site for journal and exchange archiving on version 9.02. The journal server also hosts SQL and indexes for both journal and arhive systems. Both servers are 5 years old and have direct attached storeage boxes, we have the capacity to maintain both for several years but don’t wish to add any additional storeage
The journal server storage is now reaching capacity.
We wish to introduce a new EV server on a virtual 64 bit platform and move the journal task and new storage to this. Reading various articles i am listing below what i consider to be the steps and would appreciate confirmation it will work or feedback on any improvements that could be made
- Build new hardware in accordance with the requirements stated in the installation and configuration guide for EV v9.02
- Install software accordance with the requirements stated in the installation and configuration guide for EV v9.02
- Create DNS entry
- When EV is installed on the new server run the configuration wizard and join the existing EV site
- In the admin programme\vault storage groups, run the new partition wizard on the journal to close the vault partition on the current journal server and create new partition on new server
- Stop journal task on current server but don’t delete until quesues have cleared
- Create journal task on new server copy settings from existing task on current journal server
- When journaling is working and tested on new server and queues have emptied on current server delete old journal task
Hi, Not quite. What you will
Not quite. What you will end up with, is the journal task on one server and the storage on another server. You want to keep the two together.
You have a couple of options. The first is that you join the new server to the new site, create a vault store database for the new server, create a journal archive in this new vault store database, create a task on the new server and start archiving the journal mailbox with this task. Leave the old server essentially doing nothing but maintaining the old vault store database (not really an efficient use of resources)
The second is that you migrate the vault store database and associated vault store partitions/indexes etc to the new virtual server using something like the following guide http://www.symantec.com/docs/TECH141481 or the migration wizard http://www.symantec.com/docs/HOWTO42445