Applying dynaTrace 5.6 Fixpack2
Hi, recently, we are planning to apply fixpack2 but we have some doubt?
- It is advisable to disable virus scanners on the dynaTrace Server and Client side before FixPack installation, so what will happen if we didn't disable vrius?
Release note of 5.6 stated:
FixPacks are now listed separately from Plugins, and we provide a full history of all installed FixPacks. Based on this history you can Activate/Deactivate any FixPack on the dynaTrace Server. It is also now possible to install a FixPack while postponing the FixPack's activation until later (for example, in situations when restart of affected dynaTrace components is only possible from a certain maintenance window). But https://community.compuwareapm.com/community/pages/viewpage.action?spaceKey=DOCDT56&title=FixPack+Installation+and+Removal stated we need to be able to restart dynatrace server and collector before proceed to apply fixpack?
- In this case we only want to restart dynactrace server, client and 1 collector 1 agent, other collector and agent don't restart yet. Is it possible to restart only 1 collector and 1 of its agent to verify first?
- After the we verify that the 1 collector and 1 agent are working correctly then we will restart the remaining collectors & agents. Do we need to restart servers services and the client again?
Will fixpacks modify any windows registry, executables, etc?
When rollback is needed, but the “deactivate” failed, what can we do?
Thanks & Best Regards, Yee Heng
Hi,
Thomas updated the fixpack doc, which answered my queries on 2 - 4.
Any1 have answer to point 1, 5 & 6? Thanks
Best, YH
YH,
as virus scanners could extract (& modify achives) it might lead to an error not installing the fixpack. I have personally nevered encountered any issues though with virus scanners on...
Fixpacks will not modify registry or executables, they usaually are only replacing/updating files in your dynatrace installation.
Reinhard
Reinhard,
Thanks for explaining, will ask system team to disable virus scanners as advised.
Best, YH
Hello Yee Heng,
- In the past we experienced (with McAfee) slowdown (potentially related to zip-scanning) and fixpack installation failure (due to file/directory locking from the AV). The code has since been hardened to deal better with such problems, but we still recommend to add that directory to due exlusion list. (Internally tracked as JLT-47595)
- You can install the fixpack (remember to uncheck the "Activate fixpack after installation" ), which does not perform any changes until Activated. The documentation was unclear regarding that differentiation, I updated the page.
- Yes, after fixpack installation, you will be asked to manually restart these components. After the fixpack was activated (on the server), all (manually) restarted (bootstrapped) components will receive automatically the new version. So to delay the update on those components, delay the restart. Please note that we recommend however that all components be at the same version, so the restarts should not be delayed for too long. But an observation window of a few days (for agents even more) is acceptable.
- No, to restart the remaining collector, select it from Settings -> Server -> Collector -> Restart and for the agents, restart the remaining applications. The already updated components need not be restarted again.
- Nothing outside the dynatrace installation directory will be modified. New agent libraries (*.dll) will be installed into the existing agent installation directory. No registry or windows changes will be performed
- Open a support case, we should analyze the reasons what went wrong and have known manual steps based on the problem that can be performed to roll back fixpacks by hand.
I also want to mention that you might want to consider also upgrading to 6.1. Then, for future fixpack installations, we have streamlined the installation and rollback process and you have more control over the update rollout to agents: FixPacks and of course a lot of new features like web dashboards!
Best regards,
Thomas
Hi Thomas,
We now having a much better understanding on this, thanks for the clear and details explaining.
As for the upgrading to 6.1, won't happen soon but thanks for sharing the info.
TQ & Best Regards,
Yee Heng
