Forum Discussion
louislo417
2 years agoLevel 3
Hi both,
Thank you for both of your opinions. I have come up an idea of a simplest solution for me, can you give your opinion on this? With this plan, I don't need to do in place upgrade or migrate database. All indexing should re-build in new EV14.
Simply say, I want to separate the old EV12 and new EV14 in complete 2 new sites, and migrate archive one by one using:
- Export and Import .pst
- "Moving Archives" function
Initial plan to do:
- Install new EV14.4 with SQL Server 2019 on new OS Windows Server 2019 in a completed new site.
- Disable archiving tasks on EV12.
- Connect EX16 to EV12 so users on EX16 can still read the archives.
- Move all users from EX13 to EX16. (They should still be able to access the old archives, right???)
- Use "Export and Import .pst" or "Moving archives" move archives from EV12 to EV14 one by one. (It takes time, but our client is accepted long down time not to do new archives)
- Disconnect EX16 with EV12, connect EX16 to EV14.
- Link back all archives with EX16 users, and enable new archive tasks in EV14.
But I wanna know:
- When using "Moving archives" or "Export and Import .pst", do I need to connect EX16 with EV12 and EV14 at the same time? or I should disconnect EX16 with EV12 first, then connect to EV14?
- If need to connect EX16 with EV12 and EV14 at the same time, there are 2 exactly same archives in both EV, how can I control users which archives they should access?
- If disconnect EX16 with EV12, then connect to EV14, can users link back to their archives?
- "Moving Archives" function, after moving to new EV14, will EV12 still keep the archives? or it will delete and unlink automatically?
Many thanks and regards,
Louis
Related Content
- 3 years ago