Backup of JBOSS required

[ran_sushmi]

I had a doubt that should the backup of JBOSS be taken as we are going to swap our server to a new one with better congifuration. I will explain the environment of our system a little

1) Application server- JBOSS
2) Web server- Apache & tomcat
3) Application details- Java(1.4.2)

Actually, I had taken the backup of JBOSS around a week back in preparation of the swap for migration. But, one change is going to happen in our application in the form of a hotfix tomorrow and our migration is scheduled for day after. So, should a backup of JBOSS be taken after our application hotfix is applied. Also, should a back of java($JAVA_HOME) and ant($ANT_HOME) be taken, we use j2sdk1.4.x for java and apache-ant-1.6.1 for ant.

I hope, my question is clear.

Please, help in solving the doubt.

regards

[peterj]

Yes, you should backup JBoss AS after you apply the hotfix, unless you want to reapply the hotfix on the new hardware. Either way is OK.

Another option is if you have a synchronization utility - it should be able to copy changed files from the old hardware to the new, provided both are available.

[ran_sushmi]

thanks, for your answer. But, do we need to backup as JBOSS is a AS and not our application code? I was just getting a bit specific that why we need latest copy of JBOSS AS to swap to our new server.

regards

[peterj]

I do not understand the question.

[ran_sushmi]

I mean to say is that if the hotfix is going to change our java application, why need to copy $JBOSS_HOME again as it was copied only around a week back.

I hope, my question is clear.

Please, help in solving the doubt.

regards

[peterj]

I already answered that question. You will note that in my original answer I gave three possible solutions:

1) Copy JBoss AS again
2) Apply the fix to the new JBoss AS installation
3) Use a tools to sync the changes from the old, hotfixed, JBoss AS to the new one

Use whichever method you are most comfortable with, or is the easiest for you.

I am making that assumption that your application is deployed in the JBoss AS directory structure.

Another thought - does your application use the hsqldb database? I hope not, but if it does, options 1 or 3 are the best bets.

[ran_sushmi]

thanks, for your answer. But, your answer suggests that any hotfix to the application can affect the JBOSS so a fresh copy of JBOSS will be required to swap.

regards

[peterj]

No, by "new JBoss AS installation" I was referring to this statement you made "I had taken the backup of JBOSS around a week back in preparation of the swap for migration." I assumed that you had placed that backup on the new hardware, and thus referred to it as the new JBoss AS installation.