First time upgrading - checking my steps
Hi All Looking to do my first EV upgrade, normally this has been actioned by another colleague who has since retired. Currently we're on EV 12.1.2 and looking to go to 12.5.3. Our environment is: 4...
Forum Discussion
Hi,
I'm not totally agree with your method, please check my update :
Change Day:
- Stop all EV services and put EV admin service set to disable (all of other service depend of this one)
- restart server to free all EV files
- Check all MSMQ other than A3, A5, A7 are empty
-
Copy and backup EV folder for webapp.ini and web.config files
- Make a backup of EV DB with a SQL maintenance plan, like this you don't depend of a backup software ... more easy if you work during week-end or night
- make copy of all .msg files in EV installation folder (not in subfolders), and make a copy of shortcuts.txt.
- Upgrade your first server only in 12.5, like this if you need going back it's more easy with only one server
- Run cmdlet Start-EVDatabaseUpgrade to upgrade SQL db
- Start EV admin and EV directory on your first server, and start Enterprise Vault Admin Console for check if you can access at all (don't start other service at this time) ... if OK, you pass the no going back point
- If last step is OK you can upgrade other server in 12.5
- Start all EV services and check that you can open archive mail
- go back to point 1 for install 12.5.3
Regarding OWA, with Exchange 2016 you just need to upgrade Office Mail App with a PowerShell command on Exchange server
Regarding Outlook Addins, it's not mandatory to upgrade it at the same time, you can upgrade it before or after upgrade of EV server without issue
Regards,
Antoine
Hi Antoine
Thanks for your reply, sorry for the lateness, I didn't see it earlier. Can you clarify what step 6 is as I haven't read about this part. With the DB upgrade, I thought you have to upgrade all servers to new base first before you run the DB command?
I managed to get around to upgrading my dev environment the other day and these are my revised steps:
Confirm SQL backup
Confirm server backups
Confirm AV off
Change Tasks:
SCOM and Tivoli maintenance
- Set Vault Stores to backup mode (with Prod, maybe disable update mode night before?)
- Stop all EV services and set to manual
- Check all MSMQ are empty
- Backup existing Enterprise Vault Folder to a new folder. This will include webapp.ini and web.config.
12.5 Base install
- Upgrade each server
- ensure services are stopped
- Reboot server after each upgrade
- ensure services are stopped
- Check event logs
12.5 DB install
- ensure services are stopped
- upgrade SQL DB (from one server only)
- check DB upgrade log
- Check event logs
Do not upgrade to Enterprise Vault 12.5 and then immediately install Enterprise Vault 12.5.3. After you have upgraded to Enterprise Vault 12.5, use the PowerShell cmdlet Start-EVDatabaseUpgrade to upgrade all Enterprise Vault databases as described in the Enterprise Vault 12.5 Upgrade Instructions, and then install Enterprise Vault 12.5.3.
12.5.3 MR install
- ensure services are stopped
- 12.5.3 install
- Repeat on all servers till all are at 12.5.3
12.5.3 DB install
- ensure services are stopped
- sql db 12.5.3 update (from one server only)
- check DB upgrade log
- Check event logs
- Start EV Admin and EV Directory services
- Check event logs
- reboot servers
Final steps
- check event logs
- start all EV services and set to Automatic start
- check event logs
- Set stores to update mode
Post check on client
Like you stated in step 2 though, I might do the reboot at the start to ensure a cleaner upgrade. Also with the checking with EV Admin and Directory services, so this can be started at any point to check it's ok, I don't have to wait till the very end?
Hello Charlie,
Step 6 (copy msg files) is only necessary if you have customized the shortcut content text. Some companies change the shortcut-text, to (for instance) include a link to a help, or the number of the supportdesk. If you have not changed these, you don't need to back them up. If you have changed them, and you don't backup, they'll be overwritten by the install of 12.5
As for your question related to upgrading 1 server first:
History: up to EV10, you needed to upgrade each server, and first upgrade the directory database (by starting the directory service). Then on each server, you would start the storage service, to upgrade the vault store databases (and the fingerprint ones).
EVDatabaseUpgrader upgrades EACH database from 1 server. Why do this on 1 server? You do the preparations, shut down all services, set admin service to disabled. Upgrade 1 server to 12.5, runevdatabaseupgrader. If this completes succesfully, you can then install 12.5 on the other servers.
If it fails (which is unlikely, but you never know), you only need to restore the databases, reinstall your 11 version ON THIS 1 SERVER, and you are back in business.
If it succeeds, BACKUP the Databases, and if you are confident, you can then perform the install of 12.5.3 on this 1 server, run evdatabaseupgrader, then install 12.5.3 on the other servers.
In short:
Stop EV.
BACKUP databases
Install 12.5 on 1 server, upgrade databases.
BACKUP databases
Install 12.5.3 on this 1 server, upgrade databases
BACKUP databases.
install 12.5 on other servers, then install 12.5.3
Also with the checking with EV Admin and Directory services, so this can be started at any point to check it's ok, I don't have to wait till the very end?
and as for your last question, wait until the databaseupgrade confirms it is finished successfully before starting admin/directory on other servers!
As I described earlier, if you do the upgrade on/from 1 server, if you start services on other servers before they are on the same level as the first, strange things will happen :)
Don't forget Discovery Accelerator/Compliance Accelerator if you have these. Do these before you do EV.
Thanks Gertjan for the clarifications. We don't use DA/CA so I don't have to worry about these ones.
Ok, so long as I don't start services on any of the other servers, then I can upgrade all the way through on the 1 server and when this is completed successfully, I just need to install 12.5 base and 12.5 MR on the remaining servers.
If 2 servers are the task/storage servers and the other 2 are only indexing servers, does this matter? Or can I still follow the process you've outlined?
