It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×7,478
×2,352
×1,307

question asked: Mar 02 '22, 11:46 p.m.
question was seen: 1,239 times
last updated: Mar 16 '22, 11:59 p.m.

Related questions

What are the recommended steps to expand a hard disk for ELM?

0
Ian Wark (797●1●35●53) | asked Mar 02 '22, 11:46 p.m.
We have a question about what are the recommended steps to expand a hard disk for ELM without installing ELM again in a new environment. We are especially interested in doing this for the /opt/IBM/JazzTeamServer/server/logs directory, if this does not work for the whole of the JazzTeamServer directory. We know that we can specify a new log path to a different disk, but when we do an upgrade in future we don’t want to complicate things. We would like to just put the logs directory in a different partition of the same disk with the same default path. Does someone have steps, or is there some document that can help us?

These are the kind of steps that we are imagining. We use AWS with RHEL OS.
  1. Add a new disk volume (EBS etc.)
  2. Stop Jazz server.
  3. Backup everything under /opt/IBM/JazzTeamServer
  4. Also stop the underlying EC2 for the Jazz server.
  5. Attach the new EBS to the EC2.
  6. Format the EBS volume.
  7. Start up the EC2 under the Jazz server.
  8. Login to the RHEL OS in the EC2 of the Jazz server and mount the EBS volume to /opt/IBM/JazzTeamServer
  9. Restore the entire contents of the backup in step 3 to the mounted /opt/IBM/JazzTeamServer in step 8.
  10. Set automatic mount.
  11. Start up the Jazz application server again.

Accepted answer

1
permanent link
Richard Rakich (111●3) | answered Mar 16 '22, 11:59 p.m.
JAZZ DEVELOPER
edited Mar 16 '22, 11:59 p.m.

 If you are running on RHEL (or any Linux system) the partitions should be set up using Logical Volumes.  Using the OS tools, you an add physical disks, add them to the volume group, then expand the existing filesystems without having to move any files around.


Here is a tech note from another IBM product that explains the process.

Ian Wark selected this answer as the correct answer

One other answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Ralph Schoon (63.5k●3●36●46) | answered Mar 03 '22, 2:35 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

This is not an ELM question. This is a question how to manage your environment. If the log folders are getting bigger and bigger, implement a maintenance procedure to clean the log folders every so often. The logs and included folders can be deleted when the application server is down. 


The files that could grow over time are the database and the index files. The database maintenance is dependent on the database and not covered by ELM. Index file location can be configured and you can change configurations when the server is down. 

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.