Forum Discussion
- Add a new server (virtual) with the same EV version but the recent S.O. compatible in the same site
- Moved every service to this server and did an in-place upgrade
- Install the new hardware and repeat step 2
If you have more question don't be affraid to ask
Hi Tonaco_pt,
Thank you for sharing your notes, I wanna confirm if I understand your steps correctly:
1. Add a new EV12.4 server with exact same spec as the old one, and add it to the same site.
2. Move only all services to the new EV12.4, and in-place upgrade to EV14.4;
3. Install new EV14.4 with the new Windows Server 2019 and MSSQL 2019;
4. Migrate the upgraded EV14.4 services to new EV14.4;
I have some questions about the steps' detail:
1. When adding new EV12.4 to same site as old one, can we config using same VaultStore and Indexing?
2. There are 2 EV12.4 server in one site, can I only upgrade one of them to EV14.4? Can different version of EV stay in one site?
3. As my old EV12.4 is using MSSQL 2012, EV14.4 is not support. How can I do the in-place upgrade?
4. After upgrade the EV14.4, will it affect the old EV12.4 server archived data or index? As EV14.4 is using new index system ElasticSearch.
5. When all solved, Install the new EV14.4 with all new spec in a new site, then start to migrate storage, indexing and server setting? What are detail steps for storage and indexing migration?
I might need more details steps to understand better, thank you again for your kindly sharing!
- Tonaco_pt2 years agoModeratorHi,
Hope you can wait until tomorrow, I took a personal day and answer on my phone.
I need to move to an intermidite server because I was in EV11 on a Windows server 2008 R2. If can do an inplace upgrade, you don't need to do this step- louislo4172 years agoLevel 3
Hi Tonaco_pt,
Sure please reply to me at your convenient.
We would like to do the EV upgrade with Windows Server and MSSQL server at the same time.
I think it is better to do a migration upgrade instead of inplace upgrade in order not to affect current data and environment.
- GertjanA2 years agoModerator
I would personally first upgrade/move EV to 14.4, then upgrade to new SQL version. If something goes wrong, it is easier to troubleshoot what is not correct. If you do everything in 1 go, you introduce a risk that Os, or EV, or SQL or all are not ok. Step by step is better way.
I wrote a few articles on moving database, upgrading etc. They can be found under my profile on LinkedIn.
- Tonaco_pt2 years agoModerator
I have some questions about the steps detail:
When adding new EV12.4 to same site as old one, can we config using same VaultStore and Indexing?
- When add a new server to the site and move:
Storage - You need to copy over the Partition to the new server or move the volume (detach\attach) and follow (How to Move a Vault Store Partition or Vault Store to a different location on the same server)
Indexing - This will take more analysis, when you upgrade to 14.4 you will have all index location (Altavista and/or Velocity) closed and a new Elasticsearch index location created. I think you should move the Index to the new engine just at the end. Not sure need more investigation.
There are 2 EV12.4 servers in one site, can I only upgrade one of them to EV14.4? Can different versions of EV stay in one site?
- No, it not possible to have different version of EV server in one site, there can only be one EV EnterpriseVaultDirectory database.
- Yes, can update just to one service, just move the EV Service to that server
As my old EV12.4 is using MSSQL 2012, EV14.4 is not supported. How can I do the in-place upgrade?
- In Enterprise Vault™ Compatibility Charts nor EV 12 or 14 are compatible with SQL Server 2012.
- Yes, it possible to do a SQL in-place upgrade
- We have lots of DBA and I asked for their help. Please refer to GertjanA. In my case I upgraded SQL server 1st because of hardware issue.
After upgrading the EV14.4, will it affect the old EV12.4 server archived data or index? As EV14.4 is using a new index system Elasticsearch.
- The and user will get a still different "Enterprise Vault Search", color more options in the menu. All their archive items are the same.
When all solved, Install the new EV14.4 with all new spec in a new site, then start to migrate storage, indexing and server setting? What are the detailed steps for storage and indexing migration?
- All Step are the same for Storage. Indexing you will have an extras step:
- create snapshot(backup)
- move Index [How to restore Elasticsearch index data in Enterprise Vault 14.2 and later on a different server](https://www.veritas.com/support/en_US/article.100051838)
- Migrate user index to the new Elasticsearch engine
My recommendation to you is:
- Simplify.
The more complex migrate solution more failure points. - Break down steps.
What you need to move and what you can reinstall. My Step where:
SQL Server and Database
EV Server (Configuration, Registry Keys, Licenses, Alias, etc.)
EV Services (Storage, Index, tasks, etc.) - Create a Lab.
The is nothing like testing. - Verify if you are entitled for Veritas Support or other partner support.
Some to fallback in case of problems
- When add a new server to the site and move:
Related Content
- 3 years ago