Server Settings Migration Wizard 14.0
New version of Server Settings Migration Wizard (SSMW) is now available. The latest versions supports: Migration from 12.x to 12.5 Migration from 12.x to 14.0 Migration from Win 2012/2016 to Win 2019 For more information refer to the below links https://www.veritas.com/content/support/en_US/downloads/update.UPD397880 https://esd.veritas.com/378349/Veritas_Product_Files/EV/EV_Migrating_Using_Server_Settings_Wizard.pdf?authparam=1608196826_0c3a4c5cf52c11b085fa4ae5d7a2bdd4 Regards Amol
Enterprise Vault Database Migration from MS SQL 2012 Standalone to MS SQL 2016 AlwaysOn
Dear Experts, We are planning to move Enterprise Vault 12.3 Database from MS SQL 2012 R2 SP3 standalone to MS SQL 2016 AlwaysOn. Also AlwaysOn listener will use the custom port 49540. Below is the setup and steps I am considering to migrate the database. Appreciate if you can review the steps and give your expert advise if anything I need to consider during the migration process. Current Setup: Enterprise Vault 12.3 running on Two Node Veritas Cluster on Windows 2012 R2 Discovery Accelerator stanadlone server configured. Steps I am considering to migrate: 1) Stop all EV Services on all Servers 2) Change the Database Instance name using SetEVDatabase 3) Detach EV Database from SQL 2012 and Attach EV Database in SQL 2016 4) Backup the Database and Configure AAG with Listener with 49540 Port 5) Wait for complete sync to happen 6) Change EV Registry Entry for Directory Service (Kindly suggest if I need to mention the Port Number in registry. E.g. AAG_LISTENER_NAME,49540 OR or AAG_LISTENER_NAME Should be fine) 7) Change FingePrint Database Entry using SQL Query (Suggest whether I need to use AAG_Listener,Port_Number OR just AAG_Listener is fine) 8) Start EV Directory Service & Admin Service, Change the Vault Store Group Database entries (suggest whether I neeed to specify the Server with port name as mentioned in previous steps?) 9) Start All remaining Services 10) Wait for completely startup 11) Modify the EV Monitoring Database (Suggest need to specify portnumber along with AAG-Listener_name 12) Test Search and Archives 13) Modify the Config File for DA Server (Suppose I need to modify Server Name with Port number in config files? Suggestions please) 14) Start EVAMS 15) Login to EVDAAdmin portal, reflect change for EV DA database with appropriate portnumber AAG_LIS_Name,PortNumber 16) Retstart EVAMS Really appreciate your feedback and suggestions. Thanks,
Enterprise Vault 10.0.4 to Enterprise Vault 12.1.3 Migration
Dear Experts, I need your suggestion regarding the migration process for EV 10.0.4 to EV 12.1.3 which is running on VCS 6.0 Current setup: 6 Node VCS cluster running in single cluster and in which two nodes hosting EV mailbox archiving, two nodes Journal Archive and two nodes FSA archiving. Also we have single DA Server We are planning to migrate to 12.1.3 and we have planned as below. You suggestions will be highly appreicated. Step 1: Migrate EV Databas, the MS SQL 2008 to MS SQL 2012 (failover cluster) as well DA Database Step 2: Upgrade existing DA 10.0.4 Server to 11.0.1 and then Upgrade all EV Servers to 11.0.1 Step 3: Setup new 6 nodes VCS 7.2 cluster. Two node each for MBX archiving, Journal Archive and FSA Archive Step 4: Install EV 12.0 on all cluster Nodes (no configuration) & Configure disk Group for MSMQ & RegReplication Step 5: Export Configuration from Old EV Servers (Need a clarification here. Whether we need to Export Configuration for each MBX, Jounral and FAS archive cluster or exporting for all nodes at a time should suffice. MBX cluster resource group has its own disk and other resources, so does the Journal Archive cluster and FSA archiving) Step 5: Install DA nodes 12.0 standalone & upgrade the configurations Step 6: deport disks and import disks in new cluster nodes Step 7: Configure VCS EV resource configuration Wizard Step 8: Configure EV VCS Configuration Wizard Step 9: Import EV Configuration (Again the same question. Do we need to import configuration for each cluster separately or we can do it in one go) Step 10: Bring the cluster services up for EV and test archive, retreive and search. Thanks in advance for your suggestions. Rgds, Rane
Migrate from MessageOne to Veritas EV.cloud
I've read quite a few articles about migration from other solutions into EV, including exporting to PST, and importing back into EV, and the use of third-party apps to migrate to EV. Has anyone migrated from MessageOne to EV? We are looking for an idea of how long the process may take us. We have around 400 users, 1.6TB in storage, and total aggregate is 2.3TB. Any info is helpful. Thanks, Jess
Migration and Multiple servers
Hi, Customer is moving away from v11 fo v12 and also migrating his AD and Exchange. What doe is means? All the small AD domain will be merged in the actual AD Forest and under just one name. All the existing mailboxes will be migrated to the actual Exchange cluster. It also means that there will be some GB or TB in PST to import (O Joy)! I have some questions as my head is a little bit empty and doubting about some of these things. As far as I can remember, I can move the archives from one VS to another (the from the cluster). They are in sharing within the VSG. SHould not be too much of a problem, right? I do not need to move/recreate the tasks from the old server to the new one, I can leave them there, right again, no? Is the shopping service still needed in v12? Was not starting and deleted it (probably a wrong move). If I need to recreate it, how can I do it. Can I leave all to task there to lighten the Cluster that will be just there for consulting? Can I use the old server just for PST import and archiving? When moving an archive, I get this:Entered a sleep state for 30 minutes. Reason: The source archive is delete-protected. What does it exactly means as I do not have that for other archives. I know this is a lots of questions but I have some doubts and my head is empty (starting back EV after some months of calm). Thansk in advance
