Hi Nitin, John gave you a good primer, for almost all of the rest I'll point to the fine documentation again. Look at a diff between your current installation and the plain vanilla download of the tomcat version that you're running.
What I want to comment on is this: On 20.02.19 15:33, Nitin Kadam wrote: > I need to know below details. > 1 How to take a backup before the upgrade (Main files). My standard recommendation to this is: Do not specifically back up your production system, do not plan to "maybe" go back. Rather *take your existing backup* and *restore* it to a new system. Perform a disaster recovery, as if your production server failed hard and you can't recover the data. This will make sure that you have a proper system running until you switch over to the new system. This way of working has the nice benefit that you'll prove that your backup is worth its name. If you don't have a backup: You know what to do. If you follow this advice, you don't need a specific backup before the migration. Of course, you'll need to make sure that the applications that you're running on the new and restored server use their backend storage properly - but as we don't have a clue what applications you're running (and the tomcat list is a bad place to get support for random applications anyway), this exercise is left for you. In conclusion: Make sure that your existing backup is worth its name. Then think further. Operate on a restored server, 100% separate of the production server that continues to run. And inspect your installation's diff, read the fine documentation Olaf --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
