Forum Discussion

rafanto's avatar
rafanto
Level 5
3 years ago

Linux File System for OST Media Server

Hi, Please your help with this question, we are going to implement a Linux RHEL 8 NBU 9.x Media Server with OST Plugin for integrate a HPE StoreOnce (with Catalyst as dedupe pool), what is the recommended linux file system structure (LVM) in your experience?

Thank you and regards!

Rafael

8 Replies

  • Red Hat has different file system layout depending on the hardening requirements. Use LVM for volume management so it's easier to extend file systems. Do go with "hole filesystem layouts".

    For /usr/openv I would go with a 60 GB Volume

    For /usr/openv/netbackup/logs and /usr/openv/logs I would go for around 20 GB each to hold debug logs (if enabled).

    • rafanto's avatar
      rafanto
      Level 5

      Hi Nicolai, thank you for your response, but the question was focused to the media server (with Linux) that we need install and configure, the StoreOnce has its own operating system and it don't enter in this discussion.

      This new linux media server will have RHEL 8.3 and we must install the HPE NBU OST plugin to integrate with de StoreOnce appliance, so, the question was what is the recommended filesystem structure for the linux RHEL media server, for example:

      Create various mount points under LVM physical volumen(pv)/vg/lv:

      / 50GB

      /usr/openv/ 100GB

      /home 50GB

      etc...

      Thank you for your help.

      Rafael

      • jnardello's avatar
        jnardello
        Moderator

        While 200 GB might be a bit much as has been mentioned by others, definitely give yourself some elbow room and don't trim it down too much.

        Maybe 50 GB for / and another 50-75 GB for /usr/openv/ . Remember it's not just about storage for the binaries and such, at some point in the future you're going to want to crank logging up all the way, maybe for several days running (long weekend?), to troubleshoot some problem. Depending on the issue that could generate some decent-sized NBU logs and it'd be nice not to fill up the entire filesystem with them & crash your other backups. =)

        Likewise, core dumps are useful troubleshooting tools on occasion and it's nice to have room to generate them.

        Food for thought.