What are the recommended steps to expand a hard disk for ELM?
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.
- Add a new disk volume (EBS etc.)
- Stop Jazz server.
- Backup everything under /opt/IBM/JazzTeamServer
- Also stop the underlying EC2 for the Jazz server.
- Attach the new EBS to the EC2.
- Format the EBS volume.
- Start up the EC2 under the Jazz server.
- Login to the RHEL OS in the EC2 of the Jazz server and mount the EBS volume to /opt/IBM/JazzTeamServer
- Restore the entire contents of the backup in step 3 to the mounted /opt/IBM/JazzTeamServer in step 8.
- Set automatic mount.
- Start up the Jazz application server again.
Accepted answer
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.
One other answer
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.