18 Sep 2019 09:28 AM
Hello,
In the process of the automation we are setting up for the purposes of One Agent installation on servers, we are having a little issue here.
The default FS on which ONE AGENT installation is happening is VG00 (APPMON agent used to be on VGDATA).
Now the issue is if VG00 is full we will have to do it manually but when VGDATA is full we can automate an extension too.
What i'm asking here is when are these file systems created ? during the installation ? before the installation ?
and how can we change that ?
Also i have seen the install path documentation and it's not what i'm looking for
Does anyone have an idea about this ?
Solved! Go to Solution.
18 Sep 2019 09:37 AM
I assume this is on Linux.
The Linux OneAgent installer does not create any new filesystems. The default behavior is to install the core files into /opt/dynatrace/oneagent and configs into /var/lib/dynatrace/oneagent. Which physical/virtual filesystems are used depends on how the above paths are mounted at installation time.
18 Sep 2019 09:43 AM
Thank you for your answer.
Yes i'm talking about LINUX.
Maybe i didn't understand you very well but i'm talking about VGs (Volume Groups) we have 2 VGs on our servers VG00 and VGDATA. Now the installation path is created by default on VG00 and we don't know how to change that ?
What do you mean by "depends on how the above paths are mounted at installation time"
Thank you
18 Sep 2019 10:04 AM
With LVM file systems are mounted on logical volumes which in turn are mapped to volume groups (which are mapped onto one or more physical volumes).
You can easily extend a volume group by attaching a new physical disk. The new storage can then be used to extend your logical volume(s) on the fly. How this is done is probably a bit out of scope (Google is your friend).
Besides, you can change the installation path by passing parameter INSTALL_PATH to the installer script.